I installed the TWRP Backup of Lollipop 5.0 when it came out on these forums, and later i flashed Phils CWM Recovery to flash the zip back to stock 4.4.4
Now i just flashed stock recovery so i can finally install the OTA for Lollipop 5.0.2 that just came out.
It flashed ok, without errors, but when i select to open recovery (Vol UP), it just gets stuck on the little robot with a red triangle on it, like it usually does before entering recovery, but it just stays there and eventually reboot into system normally.
Any ideas why that might be happening? I already had noticed that issue after i installed the TWRP backup, but since i flashed Phils CWM and it was working perfectly, i never bothered checking that out.
Its the final step so i can install the so long awaited OTA.
Any help would be greatly appreciated.
Thanks in advance.
guguts said:
I installed the TWRP Backup of Lollipop 5.0 when it came out on these forums, and later i flashed Phils CWM Recovery to flash the zip back to stock 4.4.4
Now i just flashed stock recovery so i can finally install the OTA for Lollipop 5.0.2 that just came out.
It flashed ok, without errors, but when i select to open recovery (Vol UP), it just gets stuck on the little robot with a red triangle on it, like it usually does before entering recovery, but it just stays there and eventually reboot into system normally.
Any ideas why that might be happening? I already had noticed that issue after i installed the TWRP backup, but since i flashed Phils CWM and it was working perfectly, i never bothered checking that out.
Its the final step so i can install the so long awaited OTA.
Any help would be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
at robot with triangle
in 4.4.4 recovery hold vol up and tap power
in 5.0.x recovery hold power and tap vol up
should enter to stock recovery
Related
Hello! I received the 1.29.1540.16 update today. I have the Team Win's recovery flashed on my Dev Edition. When I try to update, TWRP starts and no update happens.
How should the OTA updates be addressed with custom recoveries?
Same here... I have a rooted Dev Edition with CWM Touch recovery. Got prompted to update to 1.29.1540.16 (currently on 1.29.1540.3). Tried to install a couple of times, but, it just reboots without installing the update.
mrcobain said:
Hello! I received the 1.29.1540.16 update today. I have the Team Win's recovery flashed on my Dev Edition. When I try to update, TWRP starts and no update happens.
How should the OTA updates be addressed with custom recoveries?
Click to expand...
Click to collapse
Flash stock recovery first.
MediocreFred said:
Same here... I have a rooted Dev Edition with CWM Touch recovery. Got prompted to update to 1.29.1540.16 (currently on 1.29.1540.3). Tried to install a couple of times, but, it just reboots without installing the update.
Click to expand...
Click to collapse
i think you have to install stock recovery and maybe relock bootloader
skinsfanbdh said:
i think you have to install stock recovery and maybe relock bootloader
Click to expand...
Click to collapse
%$($*&%(@%... I was too hasty. Rebooted to recovery, wiped cache and tried to flash the downloaded OTA update zip (named OTA_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16_R-1.29.1540.3_release_318620_signednimix5ealszkrygs.zip) which I found in the downloads folder.
It started the installation, and is now hung at the "Running bug-fix1 tool..." step.
Not sure how long I should wait before aborting it. Am concerned that aborting (forcing a reboot) will cause more damage.
MediocreFred said:
%$($*&%(@%... I was too hasty. Rebooted to recovery, wiped cache and tried to flash the downloaded OTA update zip (named OTA_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16_R-1.29.1540.3_release_318620_signednimix5ealszkrygs.zip) which I found in the downloads folder.
It started the installation, and is now hung at the "Running bug-fix1 tool..." step.
Not sure how long I should wait before aborting it. Am concerned that aborting (forcing a reboot) will cause more damage.
Click to expand...
Click to collapse
abort and restore you backup
Aborted... rebooted... looks OK. Still on 1.29.1540.3. Still prompted to update. So, basically, status quo.
Looked around for stock recovery - the only ones I find are the 401 (instead of 1540) - which, if I understand, is from the international version and NOT the Dev Edition. Can anybody please help me get the stock recovery for the Dev Edition. (My first nandroid backup was *after* installing CWM and rooting.)
MediocreFred said:
Aborted... rebooted... looks OK. Still on 1.29.1540.3. Still prompted to update. So, basically, status quo.
Looked around for stock recovery - the only ones I find are the 401 (instead of 1540) - which, if I understand, is from the international version and NOT the Dev Edition. Can anybody please help me get the stock recovery for the Dev Edition. (My first nandroid backup was *after* installing CWM and rooting.)
Click to expand...
Click to collapse
you may be able to get it to install if your on a stock rom but im not sure about it
Yeah, I have stock ROM. Looks like I have to do what this person has done here.
Has to wait until I get home this evening.
MediocreFred said:
Yeah, I have stock ROM. Looks like I have to do what this person has done here.
Has to wait until I get home this evening.
Click to expand...
Click to collapse
or just flash the ruu for your phone
But, doesn't flashing the RUU wipe apps/data? I'd like to do this in the least destructive way possible. If I can get away with just flashing original recovery, installing the OTA update and flashing CWM back, I'll be happy.
yes it will. if you can get away with that then go for it
I have cwm installed on my htc one and I couldn't ruu my one back to a stock image. It would freeze up during the flash image process in the beginning.
No harm in trying the 401 or 707 recoveries ... if OTA doesnt work, just hard reboot and flash another
AND REMEMBER - NO NEED TO RELOCK FOR OTA UPDATES !
Ok got this to work and here's how, it goes without saying that this was my experience and the steps I used and I by no means accept any responsibility for any of these steps functioning on any other device...
I was using TWRP 2.5 and was rooted but otherwise was still on the stock rom that my developer edition shipped with.
I went here and downloaded the stock recovery for .16.
I opened the rar file which included other bat files to push the recovery but I didn't use that. I went to the fastboot folder and pulled the recovery.img file and dropped it in my M7 all in one tool kit folder under data and recoveries.
I then plugged in the phone and opened the toolkit and flashed my own recovery and followed the directions in the toolkit. After reboot the device came up and wanted to load the update which I let it do.
It went through and loaded and the scroll bar went all the way to the end and stuck. I waiting ten minutes and when it didn't restart I held the power button for about 15 seconds (until buttons stopped flashing) and the device screen went blank and I let go of the power button.
At this point it went through a couple screens where it appeared to be loading the update. Scroll bar went to the end and the device restarted and did that again. On the third restart it did a full boot and was good.
I then went back to the toolkit and flashed the TWRP recovery and then after reboot I went into recovery and flashed supersu to get root back.
Not sure if this helps anyone but wanted to share my experience...
MG
I currently have PacMan rom 4.4.4 KitKat installed on my Moto X and when I went to update to a new rom I found that TWRP didn't work. I can boot into recovery mode, but the splash screen just displays and never actually enters the recovery. I have to hold the power button down until the phone reboots to get out of it. I currently have TWRP v2.8.7.0 installed. I tried some of the older versions of TWRP and none worked. I also tried updating to the unoffical TWRP 3.0.2 and that behaved the same. Lastly, I tried Philz CWM recovery v6.57.9. That loaded and I was able to navigate the menu but once I selected a option that performed a task, it would freeze. If anyone can help me out it'd be greatly appreciated. Thanks
frew415 said:
I currently have PacMan rom 4.4.4 KitKat installed on my Moto X and when I went to update to a new rom I found that TWRP didn't work. I can boot into recovery mode, but the splash screen just displays and never actually enters the recovery. I have to hold the power button down until the phone reboots to get out of it. I currently have TWRP v2.8.7.0 installed. I tried some of the older versions of TWRP and none worked. I also tried updating to the unoffical TWRP 3.0.2 and that behaved the same. Lastly, I tried Philz CWM recovery v6.57.9. That loaded and I was able to navigate the menu but once I selected a option that performed a task, it would freeze. If anyone can help me out it'd be greatly appreciated. Thanks
Click to expand...
Click to collapse
Had a similar problem on my XT1060 Dev Ed., lost all my data coz of it. Only method which worked was to flash a stock firmware via RSDlite or manually through mfastboot.
Try option 5 from here with complete data wipe.
Try to go to bootloader first and load it from there. Already saw this working some times.
Sent from my XT1052 using XDA Free mobile app
varunpilankar said:
Had a similar problem on my XT1060 Dev Ed., lost all my data coz of it. Only method which worked was to flash a stock firmware via RSDlite or manually through mfastboot.
Try option 5 from here with complete data wipe.
Click to expand...
Click to collapse
This worked perfectly, thanks.
My lenovo a-7000 boot into cwm recovery mode
Last time when I restarted my phone it's goes direct into recovery mode after then whenever,i reboot my system it's get back into recovery mode.
I tried power off and manually power on by power button and factory reset but it's not fixed.
Help me to get back my a-7000
I tried key test so it's confirm that my volume buttons are working fine
Am using cwm recovery and AOSP stallion mod custom rom
installed miui 7.0 also
I installed miui 7.0 custom rom also but it's not working either
When I power on my phone it's shows miui 7 logo and the enter into cwm recovery direct
Can I reset my bootloader? Please help me someone ????
I've update on OTA with S149 firmware, but after reboot, my phone's always shows "Lenovo-Recovery" screen. I can't boot into Android OS.
Help, please.
problem solved
Download stock recovery.zip of lenovo a7000 from xda and install it via cwm and my phone remove cwm recovery from system and add stock recovery after that I downloaded original marshmallow stock rom of a7000 put it in SF card ,rename stockrom.zip to update.zip and put a card in phone
Open stock recovery click on install updates and hurray phone automatically detect update.zip and installed
After reboot my phone got a new life it's back with pure stock rom marshmallow
baby1982 said:
I've update on OTA with S149 firmware, but after reboot, my phone's always shows "Lenovo-Recovery" screen. I can't boot into Android OS.
Help, please.
Click to expand...
Click to collapse
Download original marshmallow stock rom of a7000 and put it in Sd card rename it to update.zip and install it via recovery 'install update'
Hope it'll help you
baby1982 said:
I've update on OTA with S149 firmware, but after reboot, my phone's always shows "Lenovo-Recovery" screen. I can't boot into Android OS.
Help, please.
Click to expand...
Click to collapse
http://forum.xda-developers.com/lenovo-a7000/development/stock-firmware-lenovo-a7000-t3205505link of OTA stock rom and other files
I flashed TWRP via Odin without problems. After that, I booted into TWRP and selected no-verity-no-encrypt_ashyx and then added SR3-SuperSU-v2.78-SR3-20161103171345.zip to the queue. When flashing them there was an error that the SuperSU package was unavailable and in my panic decided to reboot. Now the tablet seems to be stuck in a bootloop. How do I get out of there? Do I really have to wait for the battery to be depleted, recharge the tablet and then boot into recovery?
Thanks in advance
Philipp
phisama said:
I flashed TWRP via Odin without problems. After that, I booted into TWRP and selected no-verity-no-encrypt_ashyx and then added SR3-SuperSU-v2.78-SR3-20161103171345.zip to the queue. When flashing them there was an error that the SuperSU package was unavailable and in my panic decided to reboot. Now the tablet seems to be stuck in a bootloop. How do I get out of there? Do I really have to wait for the battery to be depleted, recharge the tablet and then boot into recovery?
Thanks in advance
Philipp
Click to expand...
Click to collapse
You will have to reflash stock rom
phisama said:
I flashed TWRP via Odin without problems. After that, I booted into TWRP and selected no-verity-no-encrypt_ashyx and then added SR3-SuperSU-v2.78-SR3-20161103171345.zip to the queue. When flashing them there was an error that the SuperSU package was unavailable and in my panic decided to reboot. Now the tablet seems to be stuck in a bootloop. How do I get out of there? Do I really have to wait for the battery to be depleted, recharge the tablet and then boot into recovery?
Thanks in advance
Philipp
Click to expand...
Click to collapse
You can use the button combo while it's in the bootloop to get back to recovery. I think it's home + power + volume up? Did you manage to flash the no-encrypt zip before? If so, I think the phone should have booted up properly. But you can boot back and flash it and should be fine.
YrrchSebor said:
You can use the button combo while it's in the bootloop to get back to recovery.
Click to expand...
Click to collapse
That did it, thanks. Seems like I didn't press long enough. From recovery I flashed a newly downloaded copy of SuperSU after that it booted normally.
Philipp
Few weeks back had updated to the latest OTA update. Yesterday, I just rebooted my phone as it was little lagging.
To my surprise it just booted into recovery mode!!.
My details:- Stock ROM and Stock recovery, not rooted. Everything is stock.
Things I tried::
1. In recovery mode tried clearing only the cache. Did not help.
2. Download latest official full ROM(1.6GB) and adb sideloaded through the recovery( the option is "Install from ADB->Upgrade android from USB"). ROM get side loaded successfully, but when I try to boot it is the same, the device first asks android pattern, once unlocked it tried to boot the system, but fails and lastly vibrates before rebooting to recovery mode.
Please help me as I have very important files and folders on it. I am completely terrified at this point.
Please advice. Note that I can access fast boot mode and recovery mode.
I resolved it myself by resetting only the "system apps and data" from recovery. Thats a nice option which I never knew it existed!