www.chinaphonearena.com

Found a bug in marshmallow:
They reintroduced the bug with the front camera taking inverted selfies...
They had fixed it in the last multi 5.1 lolipop version, now it is wrong again, the front camera takes mirror pictures!

Damn, how difficult is this for them to do it right, the front camera is also used to take pictures, it is not a mirror!

Hi I'm using Open Camera app and it's working ok and you have an option to take a mirror image if you want.

(2017-04-16, 17:02)stevejc Wrote: [ -> ]Hi I'm using Open Camera app and it's working ok and you have an option to take a mirror image if you want.

Hi Stevejc, yeah I know about open Camera, I wanna use the default app, it is fast and accomodating, you can use the extra button with it, you can double click to open it etc... It is just they had corrected it in previous version and it is here again!
I know you will tell me to root and use 3rd party software, but we are back in the very same problem where I want it unrooted...

If only we had a lineageOS version of our beloved phone, I could root on-the-fly :-(

Ok, it has been a while, please help me out my friends:

Bought a new innos d6000 from innos.com, it came with 2_3 firmware (5.1.1 lolipop).
In innos site they removed marshmallow, only have 2_6 version. So after updating to that, I did an update of 3_2 marshmallow.
And then, I found out that the recovery presents the dead android figure, you press power and vol+ and get into android 6 recovery. But then, I cannot load the temp TWRP, no commands work after i press reboot to bootloader...

How do I install the permanent TWRP??

Hi, yeah it's quite a long time. In the Innos site the 3.2 version is only available with the Russian language !

For TWRP, you need to have enabled USB debugging.

And at first when you plug your phone to your PC, you need to accept when a security screen opens up.

Do you see the phone with the ADB command : adb devices.

Hi, wating for device and it just reboots and enters android...
adb devices shows the device just fine.
Tried from boot loader (managed to overgo dead android bootlogo) same thing: It reboots!

your Run_Permanent.bat is what i run...

When I reboot to bootloader in bootloader marshmallow screen, it reboots. It does not enter bootloader.
Whenever I try to go to bootloader, the phone just reboots.

Perhaps i must say that I had installed pemanent TWRP 5.1.1 before while in 5.1.1 and it worked...
Then updated to 3.2 from update menu. I now tried your modified TWRP but cannot go to bootloader, so it sais waiting for device when going to bootloader. It does not show the android screen that stais there (bootloader) it shows innos screen and boots...
Did I break the bootloader completely?

Maybe, you to set OEM unlocking on developer options. I will look tomorrow to remember !

(2018-07-25, 04:51)stevejc Wrote: [ -> ]Maybe, you to set OEM unlocking on developer options. I will look tomorrow to remember !

Did that too. No luck!

Something else that may help:
While the older innos of mine that is ok with bootloader, loads first presenting the powered by android logo and then innos circling, the damaged bootloader innos just presents the innos logo and then the innos circing logo. No powered by android logo...

What's happening when you start your phone with power and Vol + and Vol - pressed ?

(2018-07-25, 15:44)stevejc Wrote: [ -> ]What's happening when you start your phone with power and Vol + and Vol - pressed ?

Just tried it. Nothing much, it vibrates for a sec but shows absolutely nothing.

EDIT: I have a backup from original rom in internal storage. Made it with 5.1.1 TWRP that was working while in 5.1.1 But without been able to boot into recovery, I simply cannot restore it...

Also, trying to reset phone from inside android does nothing, only reboots the phone. It obviously cannot go into recovery and reset. I can reset only from volume + plus power, then power plus volume + to go into marshmallow bootloader. But from there there is little I can do since I cannot restore previous backup or install TWRP. Should I try updating to 2.3 and hope the bootloader will be fixed?