I was on 4.1.1 (rooted and CWM installed, no custom rom), I heard that the update was out so got the 31 MB update and installed it through CWM. At the time of rebooting system by CWM, I disabled the recovery flash. It rebooted normally.
But after I tried to reboot it into recovery, it just get into a double loop of google logo and then reboot in ADB. I flashed the recovery again using Google Nexus Toolkit 2.0.0 but had no luck on rebooting in recovery.
I flashed the recovery with clean update of 4.1.2 full new but no luck on recovery flashing after that too. Can anybody help or is there any other way to install recovery on 4.1.2??
Have you tried installing CWM with ROM Manager? That worked for me.
tariq_devil said:
I was on 4.1.1 (rooted and CWM installed, no custom rom), I heard that the update was out so got the 31 MB update and installed it through CWM. At the time of rebooting system by CWM, I disabled the recovery flash. It rebooted normally.
But after I tried to reboot it into recovery, it just get into a double loop of google logo and then reboot in ADB. I flashed the recovery again using Google Nexus Toolkit 2.0.0 but had no luck on rebooting in recovery.
I flashed the recovery with clean update of 4.1.2 full new but no luck on recovery flashing after that too. Can anybody help or is there any other way to install recovery on 4.1.2??
Click to expand...
Click to collapse
There are quite a few users experiencing the same problem...myself as well. There doesn't seem to be a fix for this issue. There are a couple of threads in the Q&A sub forum on the issue. Last I check no one has found a solution.
I have this exact issue as well.
This is a temporary fix: http://forum.xda-developers.com/showpost.php?p=32680976&postcount=10
Related
Before the problem, I had a 4.1.1 rooted unlocked N7 with original ROM. I decided to apply the OTA update (03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip) from TWRP recovery using the option to manually install zip updates.
The tablet rebooted, and I used Voodoo OTA RootKeeper to regain root access. Everything worked fine, I had no error messages at any moment during the procedure and the 4.1.2 update was applied successfully, as I could verify in the info section and by testing the landscape mode.
But, when I try to reboot in recovery using the option in ROM Manager, all I get is the little robot on his back image without any message. The only way to get out of this screen is to press the power button for a few seconds until it reboots into Android. Everything is fine except the recovery mode.
I tried to reflash the recovery image using Wug's Toolkit to no avail. I tried CWM, TWRP and stock recoveries but none worked. I always get the same screen with the robot on his back when I try to boot into recovery. Booting normally is always fine, only recovery seems to be affected. If I use Wug's toolkit to boot a temporary TWRP recovery image, it works but I want to be able to boot as before, with ROM Manager.
Any ideas? Is there a solution other the wipe it all and restart from scratch?
[edit] I can start into Fastboot but if I try to go to recovery from there, the same thing happens...
I fixed it by flashing the older 3.34 bootloader. So something is wrong with the new 3.41 bootloader.
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. I flashed the update through cwm and everything went fine. When you reboot the system, cwm asks if you want to flash recovery and keep root. I denied to flash the stock recovery and I kept the root. After that you can't get into recovery at all (stock or cwm or whatever). but if I downgrade my bootloader to 3.34 everything is ok. I also installed new bootloader through cwm manually again and after that I can't boot into recovery.
Btw... How to flash bootloader.raw with fast boot???
Sent from my Nexus 7 using Tapatalk 2
sikagoon7 said:
I think you are a bit misinformed. When you flash the OTA the recovery-from-boot.p is installed by default. It resets the recovery to stock every time you reboot. CWM does nothing to remedy this. The only way to fix it is to remove or rename the file to disable its function. After and ONLY after this will you be able to flash recoveries by choice and boot into them.
And while it is your choice to use whatever recovery you desire I personnaly think using stock recovery and adb sideload is the safest when it comes to signed stock OTA.zips. After that you can root and flash your recovery of choice as if you have a brand new device.
When it comes to the bootloader. Stock system, boot, and recovery verify which bootloader you are using. JRO03D looks for 3.34 and JZO54K looks for 3.41. I don't know the implications of switching them but I don't think I will test that. I've already had a bad experience with dismantling a bootloader. The bootloader is an IMG file. Download the JRO03D factory image from Google's website and extract it. Inside will be a file named bootloader-grouper-3.34.img. THAT is the stock JRO03D bootloader and that is what you need to flash using: fastboot flash bootloader bootloader-grouper-3.34.img.
Click to expand...
Click to collapse
Yes I know that and did that from the beginning (renamed the file) but the point is that you can't boot into recovery (stock or whatever). It tries to boot into recovery I think but it reboots again and loads the OS. I'm using 3.34 booatloader with 4.12 and haven't got any probs yet.
Finally Got it Working
I tried one last thing yesterday. I got into ROM Manager and used the option to flash CWM Recovery. Then I rebooted in CWM (using the ROM Manager option). All was fine and when I chose the option to reboot, CWM asked me if I would like to make the custom recovery permanent because it would otherwise be rewritten at boot (this is what caused my problems, I believe). I choose to do so and it worked normally after that.
I then downloaded the TWRP recovery (http://www.teamw.in/project/twrp2/103) and installed it with Wug's Toolkit using the option to flash a permanent Recovery from a file. I didn't modify the "recovery-from-boot.p" file because I thought that CWM already did that. Tested booting into recovery again and all is finally OK with TWRP.
One of the benefits of the 4.1.2 update is that I can now boot into recovery from the Fastboot menu.
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
diomark said:
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
Click to expand...
Click to collapse
There are mixed reports on bootloader 3.41 and booting recovery. I have not been able to properly boot recovery from 3.41 under any circumstances. If you have this issue as well, flash the 3.34 bootloader from JRO03D. Doing this has allowed me to use recovery again.
I was running 4.1.2 with old bootloader 3.34 and had a SOD while my Nexus was charging last night.
In Faux123's kernel thread, he told me:
You should use the new boot loader and stick with CWM for now until TWRP get their stuff compatible with 4.1.2. Boot loader initialize the power regulators to some know state for the machine to boot until the kernel takes over.. and the new kernel is expecting it to be initialize certain ways... This was the biggest difference between 4.1.1 and 4.1.2... so I HIGHLY recommend using the matching bootloader...
Click to expand...
Click to collapse
Steps I had to take to get 4.1.2 (rooted, stock rom, custom kernel):
flash stock 4.1.1 boot.img and recovery.img
flash 4.1.1 bootloader 3.34
flash recovery TRWP recovery
flash SuperSU (regain root)
flash CWM lastest recovery 6.0.1.5 (beta) based on Faux123 advice above
flash 4.1.2 bootloader 3.41
No problems so far. This whole process has taken days...
I'm finally where I want to be.
Oops, wrong thread...
Hi,
I'm on stock Rom with a rooted Nexus 7.
I just did the OTA update from 4.2 to 4.2.1 and I did not loose root in the process.
However, I now have a new problem I didn't have before when I was in 4.2.
Since the upgrade to 4.2.1, CWM recovery cannot be flashed permanently. Everytime I reboot my Nexus, I loose custom recovery and then when trying to reboot into recovery I end-up with a red triangle...
The only way to boot in recovery is to flash CWM recovery from Rom Manager just prior to rebooting into recovery, but the custom recovery is just temporary... I loose it at the next reboot...
I also tried to flash CWM recovery image using the Nexus Root Toolkit, but it doesn't work... I still get the red triangle...
I didn't had such an issue when my Nexus was in 4.2... CWM recovery was permanent then...
What can I do to restore a permanent CWM recovery ?
Thanks in advance for your help
After rooting my N7 a few weeks back, I have tried flashing at least 3 different grouper custom roms through TWRP 2.4.2.
After flashing the rom, when I reboot from TWRP, the N7 gets stuck on bootscreen logo of the respective rom. I have to use Nexus Toolkit 1.6.3 to reboot into TWRP and restore from nanroid backup of stock rom, and everything works fine.
Why are Custom ROMs not being able to boot past the bootscreen logo?
I would appreciate help.
Thanks in advance.
You should give us more info... What's your device, which rom you want to try, what steps did you do to flash the rom in recovery?
Nico_60 said:
You should give us more info... What's your device, which rom you want to try, what steps did you do to flash the rom in recovery?
Click to expand...
Click to collapse
Nexus 7, I have tried flashing simbean 4.2.2, latest XenonHD and another which i have forgotten the name (all latest grouper versions).
I downloaded ROMs on my PC from XDA.
Copied zip file into nexus 7 via USB cable.
Rebooted into TWRP 2.4.2.0
Wipe System/ cache/ dalvic cache
flashed Rom (indicated flash was successful)
Rebooted from TWRP
bootloop (getting stuck at the bootanimation of the custom rom)
Used Nexus Toolkit 3.6.1 to reboot into TWRP
Restored my stock rom from backup.
Stock Rom working fine.
Ive tried flashing faux kernel and an aroma installer for boot animation change, which has worked fine both times.
When you are in recovery, first go in wipe menu and do a factory reset, wipe system (optional), install the ROM and reboot and all should be fine.
Maybe try flashing with a more recent version of TWRP, 2.4.4.0
http://forum.xda-developers.com/showthread.php?t=1779092
http://www.teamw.in/project/twrp2/103
--------
Fastboot flash the latest recovery image from here...
http://techerrata.com/browse/twrp2/grouper
...and then try again, flashing your preferred ROM in recovery.
--------
Don't know if it will work... but it's got to be worth a shot.
What is odd, is you seem to have no problem NANDROID restoring back to stock...
Anyway, hope you get it sorted.
Rgrds,
Ged.
Nico_60 said:
When you are in recovery, first go in wipe menu and do a factory reset, wipe system (optional), install the ROM and reboot and all should be fine.
Click to expand...
Click to collapse
thanks , problem solved
fslnwz101 said:
thanks , problem solved
Click to expand...
Click to collapse
After installing the update every time I try rebooting the phone it reboots into recovery mode and there is nothing to my knowladge that I can do. I saw the solutions for TWRP, but unfortunately I have installed CWM. My phone is only rooted and I haven't flashed any custom ROM.
PLEASE HELP!
My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick
lukke04 said:
My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick
Click to expand...
Click to collapse
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk
timberwolf60 said:
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk
Click to expand...
Click to collapse
i saw the request of the message but i am not using a custom recovery on my phone,i use a custom dev rom made by miui france.
i think some china dev rom comes rooted by default with custom installer updater and gapps like mine.
i think twrp is not fully compatible with this device yet.
Have you try with sp flash tool method ?
http :// en.miui.com/forum.php?mod=viewthread&tid=156838&extra=page%3D4&mobile=2
I just installed TWRP for the first time ever. I used the Flashify App from the Play Store, installed it and gave it root permissions and just selected the TWRP image on the phones internal store. Seemed to work just fine and did not have to plug my phone into a computer