I spent two days faffing with putting files into the dload folder and flashing before ota options appeared, and now I'm on 585. I've found the battery life to be pretty poor compared to 193 which is where I was before, and I've messed around with all the battery life increasing options.. Really not fussed with what version I'm on as long as I get a good battery life - used to get up to two days - now, after coming off the charger at 6 am, I'm lucky if it's got power left at 10 pm! Any thoughts as to which 636 rom might be best for battery life?
Thanks!
I'm using b585 as well and the battery life is really the worst among all the roms so far. The best battery life I think is still b211 but that would mean change back to marshmallow.
plain_white said:
I'm using b585 as well and the battery life is really the worst among all the roms so far. The best battery life I think is still b211 but that would mean change back to marshmallow.
Click to expand...
Click to collapse
I can live with that!
Now trying to downgrade using the info and file found on here: http://consumer.huawei.com/sg/support/mobile-phones/mate8-sg-sup.htm
I have put the rollback update.app file in and flashed it from powered off, leaving my phone now saying it is on NXT-L29C636B500 as expected, but then when copying over and trying to flash NXT-L29C636B211 - or any other emui 4 rom - the update fails and the build number now shows as NXT-L29C900B500. I wonder if there is there a stable rollback rom from B585?
EDIT: I'm currently installing B330 - so it seems you can't just flash any old thing.. maybe I can go back to 211 from this?
EDIT: BALLS. Seems that downgrading to B330 ends up with an eRecovery screen where it tries to download a new recovery.. hmm - what to do next.
EDIT: Factory reset and back on B330! Now trying the rollback from there to 211
EDIT: Oh. I think that kills it. Now not booting at all and none of the button combinations do anything.. Don't use the rollback when you are on B330 guys
There is a glimmer of hope..
I had a very similar problem... It seems that Rollback patch only works if you install it from Nougat...
If you try to install from any other version, It'll brick your phone.
So, once you install a downgraded version, you cannot downgrade it more.. until you reach Nougat again.
I bricked my phone, and I tried a lot of things to unbrick it, flashed many roms (FYI: I even not had the bootloader unlocked, on fastboot FRP locked and Phone Locked).
And the unique thing that worked for me is there:
https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
When you unbrick your phone with the "Factory Firmware", I recommend you to flash using the B330 build.
I made my account just for helping you.
Don Kronos said:
I had a very similar problem... It seems that Rollback patch only works if you install it from Nougat...
If you try to install from any other version, It'll brick your phone.
So, once you install a downgraded version, you cannot downgrade it more.. until you reach Nougat again.
I bricked my phone, and I tried a lot of things to unbrick it, flashed many roms (FYI: I even not had the bootloader unlocked, on fastboot FRP locked and Phone Locked).
And the unique thing that worked for me is there:
https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
When you unbrick your phone with the "Factory Firmware", I recommend you to flash using the B330 build.
I made my account just for helping you.
Click to expand...
Click to collapse
Wow. Thanks! I'll try this tomorrow when I have all the tools on my work pc!
Don Kronos said:
I had a very similar problem... It seems that Rollback patch only works if you install it from Nougat...
If you try to install from any other version, It'll brick your phone.
So, once you install a downgraded version, you cannot downgrade it more.. until you reach Nougat again.
I bricked my phone, and I tried a lot of things to unbrick it, flashed many roms (FYI: I even not had the bootloader unlocked, on fastboot FRP locked and Phone Locked).
And the unique thing that worked for me is there:
https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
When you unbrick your phone with the "Factory Firmware", I recommend you to flash using the B330 build.
I made my account just for helping you.
Click to expand...
Click to collapse
After first trying several other things like the Knife tool, or just flashing over extracted Nougat images, I used the DC Phoenix tool v39 using B585.
It failed.
Then I tried it using B330.
That failed too...
Then I tried v35 using B330. It mostly worked, and I started getting excited.. but on rebooting, it tried and failed to download the eRecovery.
At that point I then put in the SD card with B330 in the dload folder, held in all the buttons and the updater appeared.
It seemed to get stuck at 5% but carried on,
It seemed to get stuck at 19%.. but carried on,
It got all the way to 99%..
And failed.
But then it rebooted - the animated logo popped up and it booted through into B330!!! :laugh: Thank you so much!!
Phew. Now not really wanting to go through all that again, but at the same time not wanting to be on EMUI 4.1 or 5 for the sake of a better battery life!
Post #3 in https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775 indicates that the NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0_DC_UNL.dgtks linked to the post will set the phone back to an android 4.3 base? Would it be possible do we think, to flash that through DC, and then be able to put an EMUI 4 rom like B211 on it?
Or should I do the sensible thing and leave it well alone now!
Bearded_1 said:
Phew. Now not really wanting to go through all that again, but at the same time not wanting to be on EMUI 4.1 or 5 for the sake of a better battery life!
Post #3 in https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775 indicates that the NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0_DC_UNL.dgtks linked to the post will set the phone back to an android 4.3 base? Would it be possible do we think, to flash that through DC, and then be able to put an EMUI 4 rom like B211 on it?
Or should I do the sensible thing and leave it well alone now!
Click to expand...
Click to collapse
You're supposed to do it first, with DC phoenix install first the NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0_DC_UNL.dgtks, it will rebuild all partitions and basic configurations that were lost and tried to recover flashing with other stock roms, and finally unbrick the phone..
And you start with android 4.3, but it is apparently of internal use by Huawei technicians. It has apps for testing many things like sound, processor, memory, storage, display, etc. And after that, you can now flash any stock rom without any problems...
FOR THE RECORD, my phone is almost 2 years old and since the upgrades of EMUI 4.1, it had a very high battery consumption. When I upgraded to EMUI 5, the thing was worse, in 5 or 6 hours of inactivity, the battery drained from 100% to 0%. As the problems started after the updates, I did not think it was related to a hardware problem.
But now that I unbricked my phone, and installed EMUI 4.1; my phone lasted only 4 hours ... from 100% to 70% in four hours and the battery was sometimes drained from 70% to 0% in seconds. So, I replaced the battery, when I opened the phone I realized that the battery was badly damaged. Now my phone (in EMUI 4.1 B330) lasts two days of inactivity and up to six hours of screen, like when I bought it.
Don Kronos said:
You're supposed to do it first, with DC phoenix install first the NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0_DC_UNL.dgtks, it will rebuild all partitions and basic configurations that were lost and tried to recover flashing with other stock roms, and finally unbrick the phone..
And you start with android 4.3, but it is apparently of internal use by Huawei technicians. It has apps for testing many things like sound, processor, memory, storage, display, etc. And after that, you can now flash any stock rom without any problems...
FOR THE RECORD, my phone is almost 2 years old and since the upgrades of EMUI 4.1, it had a very high battery consumption. When I upgraded to EMUI 5, the thing was worse, in 5 or 6 hours of inactivity, the battery drained from 100% to 0%. As the problems started after the updates, I did not think it was related to a hardware problem.
But now that I unbricked my phone, and installed EMUI 4.1; my phone lasted only 4 hours ... from 100% to 70% in four hours and the battery was sometimes drained from 70% to 0% in seconds. So, I replaced the battery, when I opened the phone I realized that the battery was badly damaged. Now my phone (in EMUI 4.1 B330) lasts two days of inactivity and up to six hours of screen, like when I bought it.
Click to expand...
Click to collapse
Huh. I've only had mine since Christmas - still, something to consider for the future. I have all the tools if it comes to that. Thanks for the advice!
Hello again
I was just looking around and came across this poster.
They claim to that B585 could give really good battery life.
This is person only loses about 20% battery in over two hours of heavy usage. @•XPLOITZ•
What's interesting is that unlike some other nougat users, he doesn't have test keys present anyway in the about phone menu.
https://forum.xda-developers.com/showpost.php?p=72852397&postcount=2402
Related
Hello.. I'm sorry for my bad English grammar, if you don't understand, please ask me.
I don't think I understand my phone well so I'll just tell you what happened then.
My note 4 is 1 year old. I think it is Thailand's model as I checked the model number when I'm rooting it.The battery life is long lasting when the first time I got it, I'm not sure when the battery life start to get worse. I'm pretty sure it is happening after Lolipop update, not sure if happens before that. I do not install much games, I do have like 5 or below games from playstore, small sized one. I do installed Clean Master to clear junks when I started feel lagging.
Until recently, because I needed root access to backup my game app data so I went root my note 4 using the odin method. I'm still in my stock firmware. I did faced a problem when Security & Policy update pop out , I did update and it went bootloop(I think it's called that) until I can't access into my phone, I did pull out battery then insert back few times and seems like it rolled back. These few days I was researching how to extend my battery life, I read lots of post said some apps is draining apps as it still not yet adapt to lolipop update? also saying Clock apps draining apps, not even wakelock detector able to detect it. I tried SetCPU and set my CPU below 800 Mhz and even 400min 500max(Just a question, why I didn't see On Demand ? Only Interactive, Performance & userspace) , I did not see any obvious results after doing all these things. Oh , I even went uninstall some bloatwares, I did download Greenify and hibernate some apps.
Now, I'm trying this method to see if it solves the problem. http://forum.xda-developers.com/andr...-life-t3095884
When I was about to Nandroid Backup my datas, to confirm it is it
1. Boot into recovery mode
2. Backup?
But then I couldn't boot into Recovery Mode( Volume Up + Home + Power ) just now, It stucks at boot screen, before the animated samsung appears, just Note 4 with model names something. There's no blue text above, and it just stucked there. The only way to exit from there is pull out battery and insert back again. I'm planning to download QuickBoot and try if can access to Recovery Mode.
Seriously, I don't know much about mobile technology, I just wanted a smooth phone with great battery life. I suggest to stay with the stock firmware, I'm still considering flash it to CM12.1 , people said it help with the performance and battery life, I do not like the interface of it, unless it solves all problems if not I'll not choose to flash into that. (Oh, can I use Odin3 to flash this? Can I use Odin3 to flash every rom? I don't really understand about rooting, is there any newbie guide for these kind of things?)
My questions are:
Can you suggest me few ways to solve this problem?
Is the method does help to my phone?
Why I can't boot into Recovery Mode?
What happened actually?
Edit: Or even factory reset or wipe partition(if I'm able to boot into recovery mode) helps? i did not try it yet.
Thank you for reading this even you can't help me.
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
I accidentally posted in Android development. so sorry
I've seen this issue on my friend's tab s. The screen would freeze then it would reboot. This got worse as the battery power doped to the point that swiping to unlock would cause a reboot. The problem turned out to be the battery. It may be worth buying a new battery for very little money to see if this fixes it.
Dr.DL said:
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Did you try a Factory Reset?
Sent From My SM-N910W8 Running CMRemix 6.01
fatboyinlycra said:
I've seen this issue on my friend's tab s. The screen would freeze then it would reboot. This got worse as the battery power doped to the point that swiping to unlock would cause a reboot. The problem turned out to be the battery. It may be worth buying a new battery for very little money to see if this fixes it.
Click to expand...
Click to collapse
I'm in a doubt about the battery, I think it's slightly swollen.
I guess I'll give it a try.
shaggyskunk said:
Did you try a Factory Reset?
Sent From My SM-N910W8 Running CMRemix 6.01
Click to expand...
Click to collapse
First thing I did.
Dr.DL said:
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Install Custom recovery thro' ODIN (philz_touch)
Flash Nameless Kernel v 6 thro custom recovery.
And I think you are done.
If you tried factory reset and flashed a fresh stock rom and its still happening, the battery is the problem and also check if there is a micro sd inserted. If so, remove the card and check.
No custom rom or kernal will be better since they come with thier own bugs and not as stable as official firmware period!
dineshh said:
Install Custom recovery thro' ODIN (philz_touch)
Flash Nameless Kernel v 6 thro custom recovery.
And I think you are done.
Click to expand...
Click to collapse
Battery issue, solved with replacement
jetbruceli said:
If you tried factory reset and flashed a fresh stock rom and its still happening, the battery is the problem and also check if there is a micro sd inserted. If so, remove the card and check.
No custom rom or kernal will be better since they come with thier own bugs and not as stable as official firmware period!
Click to expand...
Click to collapse
Solved with battery replacement
huge thanx
Dear Experts,
I just got a brand new Note 3 with Android 5. I started encrypting the phone as brand
new, so that it would contain as less data as possible. It rebooted, then it showed the
picture with percentage. After reaching 100%, it rebooted again and is now for almost 1 hour showing the SAMSUNG logo with some stars flying around it.
Please kindly let me know if this is normal ? I think that when the stars are moving on the screen, the CPU must be working in order to display that...
Also, the blue LED is flashing... Please kindly advise on what to do.
Thank you!
It's flashing blue because the phone is trying to boot but it's not having any luck. You may have to boot into recovery, perform a factory wipe, and start over.
Personally, I do not encrypt my phone because it becomes a pain to get data off the phone if the data is encrypted.
Thank you. So you think it makes no sense to wait any longer ?
But how can this happen with a brand new phone ????
Btw. this is why it's being encrypted - to not be able to get the data out of it
You could wait but the flashing blue led means the phone is in the process of loading the ROM with the associated apps and data partitions. If it can't load the data, it will hang the phone.
OK, THANK GOD I was able to reset it and it finally booted! I had been doing a few little things with the phone, just the few minutes after I started using it. Maybe this made the encryption fail.
I am relaunching the whole process once again and we'll see. If it fails again. I'll have to be using it unencrypted :-/
Unless someone has a better idea...
Nope, still the same !!! What to do ??????? Please advise...
Come on, anyone, anything, PLEASE ???
Is the phone running a pure stock ROM, including recovery?
I always avoid encrypting phones. Too many risks and issues. I recommend just having a strong password lock.
Sent from my LG-D801 with CM13 using Tapatalk
darkman088 said:
Come on, anyone, anything, PLEASE ???
Click to expand...
Click to collapse
Simplest solution. Is to try to boot into recovery. Perform data wipe. Do a clean boot
If that fails.
Try to go into download mode. Flash stock rom. Clean boot.
If that fails.
Do emergency recovery in kies or smart switch. After that clean boot
After that. Disable encryption. Yeah it's more secure but also as you experience now. When it fails a pain to solve.
Sent from my SM-G935F using Tapatalk
@audit13 - yes, it was running stock Android 5.0, which btw. looks much nicer than 6.0.
Today I have flashed Marshmallow on it and it looks TERRIBLE :-/ I'm sooooo unhappy with the design!
Perhaps I should find a Jelly Bean ROM to flash to my phone :-/
@aquatarkus - why ? You don't think that anyone will unsolder the chips from your phone in order to read them out ? Is the screen lock really so strong ? No way to go around it through some USB attacks ?
And what about your SD card ?
@Michel - it's more or less what I did, but still no solution for that stock ROM that the phone came with.
Thank you for answering!
darkman088 said:
@audit13 - yes, it was running stock Android 5.0, which btw. looks much nicer than 6.0.
Today I have flashed Marshmallow on it and it looks TERRIBLE :-/ I'm sooooo unhappy with the design!
Perhaps I should find a Jelly Bean ROM to flash to my phone :-/
@aquatarkus - why ? You don't think that anyone will unsolder the chips from your phone in order to read them out ? Is the screen lock really so strong ? No way to go around it through some USB attacks ?
And what about your SD card ?
@Michel - it's more or less what I did, but still no solution for that stock ROM that the phone came with.
Thank you for answering!
Click to expand...
Click to collapse
So could you please state the current problem again? Because if I'm correctly you van boot into the rom atm, but encryption fails? Or you are still stuck in the boot process?
What is it exactly what you want right now?
Sent from my SM-G935F using Tapatalk
I no longer have the note 3 but I have the Nexus 5 running stock MM and it looks fine to me.
Maybe encryption needs a stock ROM with stock recovery? I never use encryption on any phone as I don't have anything that is that confidential on my phone.
OK, let me put this together very quickly:
2 days ago I got my brand new Note 3. I played with it a little and said - let's encrypt the phone, till I didn't put much stuff on it, so it will be faster. Once it got to 100%, it rebooted and stayed at the SAMSUNG logo with stars flashing around it and the diode flashing blue. I was waiting and waiting and waiting and nothing! I reset it to factory settings from the original recover, repeated the process - the same! I also tried the fast encryption option - again the same!
Then I have flashed the latest TWRP recovery and tried:
1. The VisionX ROM - Android 5. When I selected encrypt, the screen went completely black. I went to sleep. The next morning it was only showing the SAMSUNG logo in fire and that kept on for another couple of hours till I decided to kill it by taking out the battery.
2. The Slim ROM Android 5.0 - when I select encrypt, it immediately reboots. It kept showing just circles for 2.5 hours with no change. Then I decided that it makes no point to wait longer and I killed it by taking out the battery.
3. The TouchWiz Marshmallow for Note 3 ROM - SUCCESS !!!
The question is - why all the Android 5 ROMs are failing to encrypt the phone ? I prefer to stay on Android 5, as Android 6 is extremely ugly, I can't stand its looks with all the white background and round icons. Perhaps I should flash a ROM with Jelly Bean 4.3, just don't know how it looks with encryption there - pretty miserable I guess...
Thank you!
darkman088 said:
OK, let me put this together very quickly:
2 days ago I got my brand new Note 3. I played with it a little and said - let's encrypt the phone, till I didn't put much stuff on it, so it will be faster. Once it got to 100%, it rebooted and stayed at the SAMSUNG logo with stars flashing around it and the diode flashing blue. I was waiting and waiting and waiting and nothing! I reset it to factory settings from the original recover, repeated the process - the same! I also tried the fast encryption option - again the same!
Then I have flashed the latest TWRP recovery and tried:
1. The VisionX ROM - Android 5. When I selected encrypt, the screen went completely black. I went to sleep. The next morning it was only showing the SAMSUNG logo in fire and that kept on for another couple of hours till I decided to kill it by taking out the battery.
2. The Slim ROM Android 5.0 - when I select encrypt, it immediately reboots. It kept showing just circles for 2.5 hours with no change. Then I decided that it makes no point to wait longer and I killed it by taking out the battery.
3. The TouchWiz Marshmallow for Note 3 ROM - SUCCESS !!!
The question is - why all the Android 5 ROMs are failing to encrypt the phone ? I prefer to stay on Android 5, as Android 6 is extremely ugly, I can't stand its looks with all the white background and round icons. Perhaps I should flash a ROM with Jelly Bean 4.3, just don't know how it looks with encryption there - pretty miserable I guess...
Thank you!
Click to expand...
Click to collapse
I can't answer the question why the encryption keeps failing. What I do know is that marshmallow offers a lot more then lollipop. And that with the option of the theme store and or a custom launcher and icons packs. You can customize the white background and icons to your liking.
Sent from my SM-G935F using Tapatalk
There is no stock mm rom for this phone so we are stuck with LP for a stock rom.
Michel, as you started the topic about themes - can you pls briefly describe how that works ?
I googled it a bit, but didn't find a simple method. Many thanks!
darkman088 said:
Michel, as you started the topic about themes - can you pls briefly describe how that works ?
I googled it a bit, but didn't find a simple method. Many thanks!
Click to expand...
Click to collapse
Samsung included the home store for later end flagships.
I know that through the use of the phoenix rom the galaxy S5 which didn't had support for the theme store got access to it.
You should check with the developer of the rom. Or the Op of the rom if the mm rom available on here comes with support for the theme store.
If it includes that.
You can access the Samsung theme store from touchwiz and download another skin for touchwiz.
This will affect the icon set, notification / dialer and contacts page.
Sent from my SM-G935F using Tapatalk
Good day everyone, i am going to report my delicate and infuriating problem that has been haunting my head for two months
I'll describe my problem in extreme detail, hoping you guys able to identify this disaster.
My android phone is Lenovo A6000 Plus, i've bought it 2 years ago and it's running on latest Lollipop version 5.1.1 I never alter the system files, since i only use my phone for games and communications, and i'm not really into tinkering android's software. so i use my phone like a normal person, do the updates when the settings asked me, update the apps, etc. and this phone running smoothly in my service. i wanted to ask both WISDOM and HELP in this thread.
1. The Bootloop disaster symptoms started on april 2018, when the phone boot SLOWLY AS HELL, seriously.. it took about 1-2 hours to boot, and it also shows the (ANDROID IS UPGRADING 0/132 apps) like wtf? , i haven't update or install any new android apps before this symptom happened. So i leave my phone plugged in and wait it to complete the upgrade; then it worked normally as it should. Unfortunately, it happened EVERYTIME i turn my phone on, EVERY SINGLE TIME.. T_T. so i struggled to avoid my phone from running out from battery as i can. This symptom happened for 3 weeks and it got from bad to worse. I wonder what kind of problem is this?
2. The worse part came when my phone is running at high RAM usage, let's say, i game on my phone alot in my spare time, using the ram up to 1800mb everytime i play game or open chrome browser (Lenovo A6000 plus have 2GB ram). When i close/task manager the apps, my phone launcher wont appear normally as it should (long pressing bottom left button) and it FORCED me to restart the phone and suffer the 1-2 hour LONG BOOT. That's unusual, i cleaned my phone regularly (using cleanmaster) and preserve both of my internal and external storage with 3-4GB free space. I wonder what kind of curse is this?
3. So the bootloop disaster finally got me this May when i turn my phone off and tried to reboot. And... no Android is upgrading 0/132 showed up, i waited for 4 hours and reboot my phone again and again and again. And its finally STRANDED on BOOTLOOP :crying:
Im on panic mode when problem 3 happened, then i searched the almighty Google for help, and found that i can backup my data with TWRP recovery, so i do as it said, followed the guides and BACKED UP all of my data.
For once i felt relieved my data is now saved. Now onto the main problem.
I've had enough of this problem so i format the phone into factory reset, wipe the Dalvik ****s, cache, system and data. All of it. thus, making my phone virgin again.
4. Now im trying to resurrect my phone, and tried my effort by downloading Stock Lollipop 5.1.1 OS again along with its prerequisites. I tried to zip-install it using TWRP but it said that "has not switched carriers and cannot be upgraded" i scratched my head and searched almighty Google again then found that i need to do ####6430### thingy before doing that. umm.. so my phone domain need to be changed, how can i do that with a phone who can't boot? (I'm from Singapore btw). What did i do wrong?? did my phone just turned into useless BRICK? but i've read that bricked phone can't even start the recovery, yet my phone still able to start either with Lollipop stock recovery or TWRP (if i adb fastboot it with adb tools from .cmd), so it's not totally fuc.. uh., BRICKED and i got the chance to fix it.
TL;DR
So, Guys.. i desperately need help. i'm a peon both in work and college, and a dead phone will not make a great company for a person like me.
I searched for enlightments and breakthroughs but always ended up failed resurrecting my phone, can you guys PLEASE :crying: tell/give me a SAFE and WORKING walkthrough to re-install my Lenovo A6000 Plus with Lollipop 5.1.1? And does it running a custom OS like those Cynadrogen thingy is good and worthy enough to speed up my phone? is the chances of getting bricked is unavoidable when running custom OS? I thought its going to be easy like reinstalling Windows, but i was wrong.
FYI, my phone now is UNROOTED and running on TWRP 3.0.2 and i can easily revert it back to Lollipop stock recovery if needed (does it considered rooting if i install custom recovery?) I also need a valid info if my phone would never turn like this again if i resurrect it again.
PLEASE HELP ME PEOPLE
THANK YOU.. ! :highfive:
sevenvoldizm said:
Good day everyone, i am going to report my delicate and infuriating problem that has been haunting my head for two months
I'll describe my problem in extreme detail, hoping you guys able to identify this disaster.
My android phone is Lenovo A6000 Plus, i've bought it 2 years ago and it's running on latest Lollipop version 5.1.1 I never alter the system files, since i only use my phone for games and communications, and i'm not really into tinkering android's software. so i use my phone like a normal person, do the updates when the settings asked me, update the apps, etc. and this phone running smoothly in my service. i wanted to ask both WISDOM and HELP in this thread.
1. The Bootloop disaster symptoms started on april 2018, when the phone boot SLOWLY AS HELL, seriously.. it took about 1-2 hours to boot, and it also shows the (ANDROID IS UPGRADING 0/132 apps) like wtf? , i haven't update or install any new android apps before this symptom happened. So i leave my phone plugged in and wait it to complete the upgrade; then it worked normally as it should. Unfortunately, it happened EVERYTIME i turn my phone on, EVERY SINGLE TIME.. T_T. so i struggled to avoid my phone from running out from battery as i can. This symptom happened for 3 weeks and it got from bad to worse. I wonder what kind of problem is this?
2. The worse part came when my phone is running at high RAM usage, let's say, i game on my phone alot in my spare time, using the ram up to 1800mb everytime i play game or open chrome browser (Lenovo A6000 plus have 2GB ram). When i close/task manager the apps, my phone launcher wont appear normally as it should (long pressing bottom left button) and it FORCED me to restart the phone and suffer the 1-2 hour LONG BOOT. That's unusual, i cleaned my phone regularly (using cleanmaster) and preserve both of my internal and external storage with 3-4GB free space. I wonder what kind of curse is this?
3. So the bootloop disaster finally got me this May when i turn my phone off and tried to reboot. And... no Android is upgrading 0/132 showed up, i waited for 4 hours and reboot my phone again and again and again. And its finally STRANDED on BOOTLOOP :crying:
Im on panic mode when problem 3 happened, then i searched the almighty Google for help, and found that i can backup my data with TWRP recovery, so i do as it said, followed the guides and BACKED UP all of my data.
For once i felt relieved my data is now saved. Now onto the main problem.
I've had enough of this problem so i format the phone into factory reset, wipe the Dalvik ****s, cache, system and data. All of it. thus, making my phone virgin again.
4. Now im trying to resurrect my phone, and tried my effort by downloading Stock Lollipop 5.1.1 OS again along with its prerequisites. I tried to zip-install it using TWRP but it said that "has not switched carriers and cannot be upgraded" i scratched my head and searched almighty Google again then found that i need to do ####6430### thingy before doing that. umm.. so my phone domain need to be changed, how can i do that with a phone who can't boot? (I'm from Singapore btw). What did i do wrong?? did my phone just turned into useless BRICK? but i've read that bricked phone can't even start the recovery, yet my phone still able to start either with Lollipop stock recovery or TWRP (if i adb fastboot it with adb tools from .cmd), so it's not totally fuc.. uh., BRICKED and i got the chance to fix it.
TL;DR
So, Guys.. i desperately need help. i'm a peon both in work and college, and a dead phone will not make a great company for a person like me.
I searched for enlightments and breakthroughs but always ended up failed resurrecting my phone, can you guys PLEASE :crying: tell/give me a SAFE and WORKING walkthrough to re-install my Lenovo A6000 Plus with Lollipop 5.1.1? And does it running a custom OS like those Cynadrogen thingy is good and worthy enough to speed up my phone? is the chances of getting bricked is unavoidable when running custom OS? I thought its going to be easy like reinstalling Windows, but i was wrong.
FYI, my phone now is UNROOTED and running on TWRP 3.0.2 and i can easily revert it back to Lollipop stock recovery if needed (does it considered rooting if i install custom recovery?) I also need a valid info if my phone would never turn like this again if i resurrect it again.
PLEASE HELP ME PEOPLE
THANK YOU.. ! :highfive:
Click to expand...
Click to collapse
When 5.1.1 update arrived?
Okay lets get to the point. Just don't panic. You have the stock rom file, extract a file named 'system.zip'. Now go to TWRP, perform advance wipe (wipe dalvik, data, system and cache partitions) and flash that file from TWRP. You'll be on stock rom with a fresh new experience.
---------- Post added at 10:38 PM ---------- Previous post was at 10:33 PM ----------
Custom ROMs are amazing and far better than the stock lenovo rom. Believe me, no one here is using that crap stock rom. You just need some instructions to flash and your phone will get a new life. We are here to assist you.
For no reason my phone just restarted. It used to restart from time to time and all was fine but this time its in bootloop. I currently don't have any recovery installed on it but I can enter in download mode. Is there any way to fix it without losing any data? I have some pretty valuable stuff that I can't really afford to lose
Its the LTE version and its running stock kitkat
I had different roms before but in the end I came back to this as everything else had bugs and wasn't stable
Also lately my battery life went to ****. From an average of 5hours SOT I can barely have a bit over 2 hours, sometimes not even 2. And I changed the battery with a new one and still no change. For some reason bellow screen I have android system as 2nd main consumer but I have no idea what could be using it. Could it be hardware??
Suggest flash custom recovery via Odin if you have no backup .
You may then be able to recover data .