NOOB ALERT!
I had ParanoidAndroid installed on my N7 when I decided to go back to the stock rom. I tried installing 4.3.0 but it didn't work and I have no OS installed. All I can get into is the bootloader mode and TWRP.
I used NRT 1.7.1 and ended up with error - Device version-bootloader is '4.18' Update requires '4.23' or something on those lines.
Have no idea now what to do... tried a few things that I googled but still stuck.
Please help.
Thanks.
Download original factory image 4.2.2 for your n7, boot n7 into boot loader mode, and flash-all.
Optionally you can then do the same with 4.3 image.
Then you can begin with others ROMs again.
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 was booting up after flashing Modaco 4.2 and I was on SmoothROM 4.1.2. The tablet would not boot so I assume I flashed the ROM incorrectly.
I turn off the device and then boot into FastBoot. After selecting Recovery from FastBoot, it gets stuck on the Google Image.
Please help. Thanks!
Hey all,
I just got my nexus 7 wifi, rooted using Wug's tool kit, installed TWR latest version and installed CM Rom.
The problem I'm facing is that when I want to boot into recovery mannually, i.e. powering on the device with holding volume down and up, I succeed into booting to the bootloader. However, when I choose the reovery Mode option, the nexus enters into a boot loop [ if that's what you call it ].
Yet if I use the toolkit, or use the commands in software like goo or ROM managers to boot to recovery, the phone does boot into recovery.
So I'm fine for now, but if anything goes wrong in future, I will get stuck. I tried, but Even the toolkit couldn't get the nexus into the recovery mode when it's in bootloader. It has to be open, and Not in File transfer mode.
I'm very noob in these things, so I would really appreciate you explaining in simple terms.
Thanks in advance.
Update to latest bootloader version 4.23 then erase and reinstall TWRP.
Thanks, I did update I can boot via bootloader now.
I recently just picked up a nexus 4 and i'm trying to get a custom ROM on it. I updated it to 4.3 and that was fine. Went to install custom recovery and every since it will not boot! I've reverted to factory 4.3 using fastboot, and relocked it and locked it but still will not boot. It gets stuck at the X logo. Left it for an hour and won't get past it. If i install a custom recovery, it'll boot into the custom recovery no problem, but won't install root as it can't mount the SD card. I can get to fastboot mode no problem and flash stuff in fastboot but will never boot up. I'm puzzled as to what to do. I'm going to try 4.2.2 factory image here shortly and see if i can get it to take. I forgot to enable USB debugging so i think thats why i can't get custom recoveries to work. I tried pushing a ROM using ADB push but it wouldn't get there. Maybe it did as it said it did on the computer but the recovery won't read the memory. Any ideas as to what to do
UPDATE: Ok after flashing stock 4.2.2 from fastboot it boots.
UPDATE: turns out just having USB debugging was the culprit of everything. So make sure USB debugging is enabled before starting the whole process!
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