On a Nexus 4 16GB, I've received OTA 4.3 update today and applied it successfully.
Then I `fastboot flash recovery` TWRP recovery and rooted Android 4.3 with latest SuperSU from chainfire. Everything is well here.
After that, when I decided to go back to stock recovery image (so that I can get the next OTA), it fails to boot the stock recovery (not the system).
I've extracted from 'occam-jwr66v-factory-08d2b697.tgz' (hopefully this is for Nexus 4 if I'm not woefully mistaken) the `recovery.img` and tried `fastboot flash recovery recovery.img`. It writes into the devices successfully, but booting into recovery gives me "no command" error message.
During the process, I have accidentally flashed twrp-2.6.00-flo onto the devices which refuses to boot (as expected). Then now it just refuses to boot the stock recovery image as well. (So I hope it's just a silly mistake of misreading the tag but "occam" is for Nexus 4 isn't it...
===============
And yeah, according to MD5 checksum I did download 'occam-jwr66v-factory-08d2b697.tgz' as it is on the server.
Related
SOLVED!
Well, after installing 4.2 OTA update on my Nexus 7 everything went fine until I installed Franco's kernel from his app.
Then I got stuck on an infinite booting process. I tried to re-flash the OTA .zip but I got an error because of the modified kernel I had just installed.
In Franco's official thread I read that the problem got solved by flashing the boot.img included in the OTA update, so I extracted the "boot.img.p" in the zip, renamed it to "boot.img", turned the tablet in fastboot mode, connected it to my PC, in which I'm running the "Google Nexus 7 Toolkit", and flashed that boot.img. Instead of solving the problem, I've got a beautiful "Booting Failed" line in the fastboot mode.
I decided to go further and do a fresh install. I downloaded the 4.2 factory image directly from Google, and flashed it using "Google Nexus 7 Toolkit". Now I can't even access the recovery mode.
Is this toolkit what is messing things up? What would you recommend??
EDIT:
I re-downloaded the factory image, and re-flashed using the Toolkit. Now the process ended pretty well, but now I'm on a boot loop (the X has been glowing for 15 minutes and counting). Then, rebooted into bootloader mode and Installed the CWM recovery using the Toolkit. Rebooted into the new recovery, and after a full wipe, solved!
Hope this helps to someone someday.
I had my Nexus 7 unlocked bootloader Rooted with Stock 4.2.2 with TWRP. Tried to go back to stock factory unrooted 4.2.2 using nexus 7 toolkit so I can update to 4.3.
The factory restored failed with Nexus 7 toolkit and I was stuck at fastboot and was not able to do anything but fastboot. I managed to flash the bootloader again with TWRP and install cm10.1 and it worked and boots normally into cm10.1 but when I try to reboot into recovery I get an android with a red exclamation and cannot go into recovery unless I flash the bootloader again and then it go into recovery.
If I try to manually download 4.3 or 4.2.2 stock images from google and try to flash with "flash-all.bat" it starts and then fails
Any ideas on how I can flash stock 4.2.2 or 4.3 or how I can get the bootloader to work again?
P.S I have tried to flash the latest TWRP an CMW bootloaders and they will work the first time installed but will not reboot back into them once I'm in cm10.1
Cheers
On my Note 1 I tried to update CWM-Recovery with the cwm app - and I never sticked to the device.
When installing and booting into recovery though cwm-app it worked once, but then on next reboot it got reverted to the old version again.
Later then I found out that on the galaxy devices the recovery can only be hard-flashed with odin or similar method, but not through the cwm-app.
BUT the cwm-app used install-recovery.sh or some other method to start the new recovery at least once after the first reboot.
Couldn't we maybe get a custom recovery running on our devices while still having knox untouched?
Just as a temporary boot I mean, but if that would work over adb for example, we wouldnt need to flash a recovery on the phone but instead boot the recovery over adb.
Anyone know more maybe? How does install-recovery.sh actually work, or how ccan it be used to boot a custom recovery?
Hello,
there seems to be an issue with my nexus 10 after having installed a rom which failed. The rom itself does not boot up, so i have no recovery/alternative roms in my storage. so im stuck on the google logo, whereupon it will book back into recover.
How can I send a a rom to my storage in nexus 10 through my pc; keeping in mind that my nexus 10 is stuck in recovery mode.. cwm recovery 6.0.3.1.
My vote is to flash the stock image available here and start again -
Or if you can get to cmw you can "adb push rom.zip /sdcard/download" and then attempt to flash from recovery the newly pushed file
Hello, I could us a little assistance. I was trying to install CM on my new Verizon LG G2 (VS980). I was able to root using ioroot, dump aboot.img, lokify CWM 6.0.4.4, loki_flash the recovery, and boot into CWM. When I tried to sideload the CM 10.2 image, I got some error about unable to lokify boot (it was missing /system/bin/loki.sh). It looks like the problem is that the pre CM 11 images have an old version of loki that fails regularly. It said it had aborted the installation, but something got totally hosed, as when I attempted to reboot, I got into a "secure boot unsuccessful" loop. I've made a verison of the CM 10.2 zip with the latest version of loki_patch and loki_flash from github, but I can't seem to get into recovery using the buttons (might be doing it wrong as the only time I went into recovery I just did adb reboot recovery) to try flashing another rom or return to stock. I can get in to download mode by holding up during boot, but I don't have easy access to a non-linux machine to use the lg mobile support tool. Is there any way to return to stock without a windows computer?
Edit:
Update, I was able to get back into recovery by unplugging the USB (apparently it doesn't like to boot into recovery if the USB cable is connected). Installed my patched CM 10.2 and everything worked like a champ.
DRayX said:
Hello, I could us a little assistance. I was trying to install CM on my new Verizon LG G2 (VS980). I was able to root using ioroot, dump aboot.img, lokify CWM 6.0.4.4, loki_flash the recovery, and boot into CWM. When I tried to sideload the CM 10.2 image, I got some error about unable to lokify boot (it was missing /system/bin/loki.sh). It looks like the problem is that the pre CM 11 images have an old version of loki that fails regularly. It said it had aborted the installation, but something got totally hosed, as when I attempted to reboot, I got into a "secure boot unsuccessful" loop. I've made a verison of the CM 10.2 zip with the latest version of loki_patch and loki_flash from github, but I can't seem to get into recovery using the buttons (might be doing it wrong as the only time I went into recovery I just did adb reboot recovery) to try flashing another rom or return to stock. I can get in to download mode by holding up during boot, but I don't have easy access to a non-linux machine to use the lg mobile support tool. Is there any way to return to stock without a windows computer?
Edit:
Update, I was able to get back into recovery by unplugging the USB (apparently it doesn't like to boot into recovery if the USB cable is connected). Installed my patched CM 10.2 and everything worked like a champ.
Click to expand...
Click to collapse
how did you patch cm 10.2