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.
Related
Hey guys, I flashed SmoothRom via that app goo.im, and when I did it, it said that I needed a compatible recovery, so I flashed the one that it recomended. Well I flashed the rom, and now my Tablet won't boot properly. I can get it to fastboot, but even when I try to flash a recovery from fastboot, it gets stuck at the boot screen (Yes my bootloader is unlocked). I've been trying to use the Nexus 7 toolkit to flash the recovery,and it is saying that it is flashing successfully, but I still cannot boot into recovery. Any ideas? I know I'm not totally bricked cause I can still get into fastboot, I just need recovery to work so that I can flash a new rom and fix this issue!
Fixed it! Just flashed the stock recovery, wen't back into fastboot and flashed CWM. Mod's you can delete this thread now
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.
Hi, I just tried Modding on Android for the first time. I went about this using adb commands in Ubuntu Terminal. I unlocked my bootloader then (I think) I flashed twrp recovery onto my Nexus 4 (Build Number LMY470.) When I went to check if my flashing of twrp was successful, it brought me stock recovery. I saw online that someone was in the same situation and they used the
Code:
fastboot erase cache
so I tried the same. In the terminal it looked like it was successful but as soon as I went to recovery mode it brought me to stock recovery again. In the recovery menu it said something about failing unmount or something. After this I tried turning my phone on and it has been stuck in the boot animation for the past 50 minutes. What should I do? Thanks!
EDIT: I factory reset my device after an hour and a half of not knowing you could get out of the boot animation. Now my recovery works. No replies needed.
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Just restore the last stable nandroid you made.
What about fastboot
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Are you using the new SuperSU beta? The play store / alpha version of supersu is not compatible with MM. I suggest more reading, specifically this thread: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page425
Also, because you did not fastboot flash the LP modem after returning to stock, your radio/wifi will not work. It's not an issue with the phone, but rather user-error. Fortunatally, it is a simple matter of getting you working again.
My advice is: Flash the stock unrooted MM TWRP backup (you should already be on the MM modem) and you should be able to start over. Just be sure to use the appropriate supersu beta, and DO NOT modify the boot image.
I got my Mi A1 today and it came with Android 7 installed, so I decided to install LOS. I unlocked the bootloader and then I booted into TWRP using fastboot (I didn't flash it), it gave that "system is read-only" warning. I tried to reboot to system without doing anything and it was stuck in a boot loop. Then I booted into TWRP again and flashed LOS sucessfully. When I tried to flash gapps, however, it failed claiming I was still running Android 7. I rebooted and it booted sucessfully into LOS, but that was the last time the phone ever booted. Now it shows the unlocked bootloader message and then gets stuck in a blinking black screen. I can't even boot into recovery or fastboot anymore.
iamleobn said:
I got my Mi A1 today and it came with Android 7 installed, so I decided to install LOS. I unlocked the bootloader and then I booted into TWRP using fastboot (I didn't flash it), it gave that "system is read-only" warning. I tried to reboot to system without doing anything and it was stuck in a boot loop. Then I booted into TWRP again and flashed LOS sucessfully. When I tried to flash gapps, however, it failed claiming I was still running Android 7. I rebooted and it booted sucessfully into LOS, but that was the last time the phone ever booted. Now it shows the unlocked bootloader message and then gets stuck in a blinking black screen. I can't even boot into recovery or fastboot anymore.
Click to expand...
Click to collapse
It seems you will have to flash stock ROM using Mi Flash (no idea how to use it so search it) and, once is done, flash LOS again.
EDG_ said:
It seems you will have to flash stock ROM using Mi Flash (no idea how to use it so search it) and, once is done, flash LOS again.
Click to expand...
Click to collapse
I somehow managed to get to fastboot and then I used MiFlash to flash the stock rom. I'm back to the bootloop, which is an improvement, because at least I can consistently get into recovery and fastboot.
The phone got stuck in that black screen after I tried to flash LOS, should I actually do it again?
EDIT: I flashed the stock rom a second time and it's working again. I don't know why, but I'll take it.
iamleobn said:
I somehow managed to get to fastboot and then I used MiFlash to flash the stock rom. I'm back to the bootloop, which is an improvement, because at least I can consistently get into recovery and fastboot.
The phone got stuck in that black screen after I tried to flash LOS, should I actually do it again?
EDIT: I flashed the stock rom a second time and it's working again. I don't know why, but I'll take it.
Click to expand...
Click to collapse
Update to stock Pie before trying to reinstall LOS again. Hope this time works.
AA
You should install 1.0.8.0firmware first before install 9 ROM!?