www.chinaphonearena.com

Full Version: Marshallow 6.0.1 is here
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10
I have a chinese phone and i managed to update to 6.0.1 from european 2.6. However, i had the twrp 5.1.1 and had to flash the zip from there.The zip has been flashed successfully, i wiped all the caches but after reset the phone stucked at the innos logo.After a long tine i did a reset by holding the power button and after that the phone started with 6.0.1.
But when i want to go to recovery by pressing vol up and power after a reset i see a dead android robot with red exlamation mark.Does it mean that the recovery image has not been flashed well?
Can i flash the 5.1.1 twrp again or i have to wait for a new 6.0.1 twrp?
Hello, in this thread, have already indicated that the boot recovery has disappeared. But they have commented that TWRP 5.1.1 can be installed
Then look at the previous comments where you indicate versions of supersu, xposed, etc.
And how to install a zip, downloading an application from the play store
(2016-12-22, 18:38)solim Wrote: [ -> ]I have a chinese phone and i managed to update to 6.0.1 .

But when i want to go to recovery by pressing vol up and power after a reset i see a dead android robot with red exlamation mark.Does it mean that the recovery image has not been flashed well?
Can i flash the 5.1.1 twrp again or i have to wait for a new 6.0.1 twrp?

The recouvery has been correctly flashed but doesn't work ! But you can flash the old 5.1.1 TWRP recovery.
2 methods are working :
With ADB in bootloader mode you can flash the permanent TWRP like before.
Command is : fastboot flash recovery recovery.img
Where recovery.img is the TWRP
With this method you can get root even after a factory reset by flashing SuperSU.zip with TWRP


Or you can do it with the app flashify from the play store.

Tomorrow I will do a complete guide with all the links to get 6.0.1
Hello, I have already installed the android 6, that fear, that palpitations.
I've updated with TWRP, since 2.6, I've done dalvik wipe and cache, I've updated the android 6, and then I've installed the SuperSu without rebooting, and again the dalvik wipes and cache.
I have rebooted, and it has been optimizing applications, so far so good. But once it was in progress, the message "Grant storage permissions to this application so that it can work" could not stop, but contiguously, I do not know what serious application, I have gone to adjustments, applications, advanced and on storage permissions , I have put to give permissions to any application. At last the error has ceased to appear.
But I get out when I'm going to type "has stopped the google keyboard application", and that's what I use the swiftkey, and still I do not know what it can be.
I installed TWRP 5.1.1 with flashify, and it took a while, and I left the reboot, I gave it, and what a fright, I thought I had already loaded it, since it has not restarted, the doll has come out Of dead android. Although I have given the power button for a while, and has rebooted well, but I have not tried yet to see if the boot recovery with the TWRP works.

The TWRP I should have installed it badly with flashify. It does not start in TWRP, only the dead android comes out.
Someone who has installed the TWRP with the flashify, please pass a screenshot to see the options that are.
I have installed V3.2 successfully.
Method was install European ROM 2.6, and then update as per the instructions on the page where you download the ROM.
It6 did have some problems starting the first time, with a lot of reboots. After an hour it started properly.
It looks like it fixed my random reboots when I use a Tracker (Orux maps)
I also had a swollen battery due to gas build up in plastic envelope. As the function of the plastic envelope is to keep moisture away from the lithium inside, I peeled back the sticker on the battery for about 25% and where the plastic had lifted (pulling up) I made a small hole with a needle. This let the gas out and when I put the sticky label back all is sealed again. The internal battery was working good and still does.
Pity they are decommissioning GSM in Australia (Telstra this month, Optus next April and Vodafone next September) so my phone will be single SIM next April. Time for a Xiaomi RedMi Note 4 I think.
Regards,
Martin
I noticed that since the update the phone stays kind of warm for a long period of time, so I installed AIDA64 to chek the CPU load. I saw that the CPU was working on 800MHz in idle all the time and didn't go back to 200MHz. I then installed EX Kernel Manager and set the min. Frequency to 200MHz but it didn't help. The CPU stayed at 800MHz. Then I changed the CPU governor from interactive to ondemand and after that the CPU went to 200MHz in Idle and the phone cooled down.
Can it be that the stock CPU governor of android 6.0.1 is not well optimized?

I also got random reboots, especially when the external battery is at 5% and the internal goes to low (at ca. 20%). I charged it to 100%, deleted the batterystats.bin file, rebooted and I observe now the behaviour.
I'm using kernel aduitor : no problem to set 200 MHz.
(2016-12-25, 23:10)stevejc Wrote: [ -> ]I'm using kernel aduitor : no problem to set 200 MHz.

Hey there, how you save settings after applying them they always come back
Mine also reports the lowest frequency of 960Mhz core 1-4 and 800 Mhz core 5-8.
It does not seem to be over heating, but battery drain is higher than it was on previous ROM.
As it does not fix my reboot problem, I will probably go back to the 2.6 EU ROM
I keep reading annoying reports, anyone else get these bugs? Until it is clarified, I will stay with 2.6 multi.
Pages: 1 2 3 4 5 6 7 8 9 10