[Q] Recovery and System kill each other? - Nexus 7 (2013) Q&A

OK, so maybe I've missed a step in the process... I have TWRP and CM12.1 running on my first Nexus 7 2013 WiFi (FLO) no problem...
Today, I unlocked the bootloader (OEM UNLOCK from Minimal ADB and Fastboot) and immediately fastboot flash recovery twrp-2.8.6.0-flo.img
Reboot into recovery, somehow the entire system is wiped out... only thing that works is TWRP.
I go through the process to restore back to Stock 5.1.0 (LMY47O) from https://developers.google.com/android/nexus/images
Now the system boots again, but when attempting to access recovery I just get the dead android with the red exclamation mark.
I fastboot flash recovery twrp-2.8.6.0-flo.img again, and again the system is wiped out. So this time I go in and fastboot flash system system.img from the stock image zip. Now the system boots and Recovery gives me a red exclamation mark again...
It's as if TWRP and Stock Android 5.1 are somehow incompatible and eating each other?! Except this doesn't explain why after doing the flash-all.bat that somehow the stock recovery doesn't work even with the stock ROM.
AND I JUST DID THIS A WEEK AGO ON ANOTHER DEVICE!
Another thing I'm struggling with is that when I'm in TWRP I can't get it to mount to the PC properly (I've done every driver combination imaginable). It'll show up in the "My Computer" list but no sub-folders show up (maybe this is because the entire "SDCard" has been wiped and there's no system structure?) and it won't let me copy files (like the Cyanogenmod zip to be installed).
Surely I'm missing something stupidly simple here. Please help me out!
MODERATOR: I accidentally created this thread in the other N7 forum, if someone can delete it please? It's at http://forum.xda-developers.com/nexus-7/help/recovery-kill-t3091308
Thanks!

So, with stock 5.1 booting and running fine, I just went through and did a fastboot flash recovery recovery.img using the recovery extracted from the android developers website (factory image), and I still get the little dead android with the red exclamation mark.
/edit apparently ^^^^ is expected behavior, just never saw it before... still doesn't explain why when I fastboot flash recovery twrp.img and reboot into twrp, the entire system has been wiped out and I can't mount or adb sideload to get CM.zip onto the device.

OK - this FIXED IT ALL: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
Apparently can't use TWRP from their website on the new hardware revision of the Nexus 7 (my other device is a few rev older)... you'd think they'd update that on their website?

Related

[Q] Only boot into CWM recovery mode

My nexus is LTE version, and had stock 4.0.2. I unlocked the boot loader, and rooted successfully, using "Galaxy Nexus Root Toolkit v1.3". I can see that the boot loader is unlocked in FASTBOOT screen.
My computer recognizes both ADB mode and FASTBOOT mode.
Then I did "Temporary Flashing" of ClockworkMod 5.5.0.4 to "Boot" partition, and installed 4.0.4 successfully. And applied the new "su.zip" as well.
After doing this, I could see that the phone boots okay, and everything was perfect, including the root permission.
The problem starts from here.
Since it was temporary flashing of CWM, I wanted CWM to be permanent. So I first erased "/system/recovery-from-boot.p". And then used the toolkit again, but this time I selected "Permanent Flashing" of Clockwork Mod 5.5.0.4 to "Boot" partition.
Now, when I turn on the phone, it boots into CWM recovery(!). Furthermore, if I select "reboot system now", it reboots, but it boots into CWM recovery again(!). I can't get into Android anymore.
I don't know if it is a good thing or not, but when I'm in CWM recovery mode (when booted), my computer recognizes the phone as "ADB mode - recovery".
Oh, and when turning on the phone with VOLUP+VOLDOWN+POWER, it still shows FASTBOOT screen (and yes, the computer still recognizes it as FASTBOOT mode), but when I select "recovery", there's an Android with a red warning sign on it, and system halts. I should do a battery pull.
What should I do??? Help
PS1. I downloaded "mysid-icl53f-factory-blahblah.tgz" from google's depository and extracted "recovery.img". And used the toolkit to "Temp Flashing" to "Boot" partition, but it ends up in the android with the red warning.
If you're using Galaxy Nexus Toolkit v5.4 from mskip, you don't need to extract anything, just copy .tgz file into the appropriate folder and the toolkit will do the rest for you.
Try reflashing the stock image from google again (make sure you choose the one for CDMA version).
After that, use toolkit to flash CWM, and the touch version is fun.
highmoon said:
My nexus is LTE version, and had stock 4.0.2. I unlocked the boot loader, and rooted successfully, using "Galaxy Nexus Root Toolkit v1.3". I can see that the boot loader is unlocked in FASTBOOT screen.
My computer recognizes both ADB mode and FASTBOOT mode.
Then I did "Temporary Flashing" of ClockworkMod 5.5.0.4 to "Boot" partition, and installed 4.0.4 successfully. And applied the new "su.zip" as well.
After doing this, I could see that the phone boots okay, and everything was perfect, including the root permission.
The problem starts from here.
Since it was temporary flashing of CWM, I wanted CWM to be permanent. So I first erased "/system/recovery-from-boot.p". And then used the toolkit again, but this time I selected "Permanent Flashing" of Clockwork Mod 5.5.0.4 to "Boot" partition.
Now, when I turn on the phone, it boots into CWM recovery(!). Furthermore, if I select "reboot system now", it reboots, but it boots into CWM recovery again(!). I can't get into Android anymore.
I don't know if it is a good thing or not, but when I'm in CWM recovery mode (when booted), my computer recognizes the phone as "ADB mode - recovery".
Oh, and when turning on the phone with VOLUP+VOLDOWN+POWER, it still shows FASTBOOT screen (and yes, the computer still recognizes it as FASTBOOT mode), but when I select "recovery", there's an Android with a red warning sign on it, and system halts. I should do a battery pull.
What should I do??? Help
PS1. I downloaded "mysid-icl53f-factory-blahblah.tgz" from google's depository and extracted "recovery.img". And used the toolkit to "Temp Flashing" to "Boot" partition, but it ends up in the android with the red warning.
Click to expand...
Click to collapse
If you're using Windows. You can be saved at this point. The good thing is that your device is being recognized by ADB in recovery.
The toolkit installed the SDK onto your computer
Here is what you do to go save yourself
Download a Galaxy Nexus LTE ROM as well as the Gapps package for it. (AOKP as an example)
go to C:\Android-sdk-windows\platform-tools and put the ROM and Gapps in there
Now, with your phone plugged into computer and in recovery, open up a command prompt
In recovery, navigate to "Mounts and Storage" and be sure to select MOUNT DATA
type
cd c:\android-sdk-windows\platform-tools
adb push EXACTNAMEOFROM.ZIP /data/media
(depending on the file size, it will take about a minute or two)
adb push EXACTNAMEOFGAPPS.ZIP /data/media
adb reboot recovery
------
Okay, now that you have rebooted recovery , go to "install zip from sd card" and MAKE SURE you see the ROM and Gapps package, but DON'T flash them yet.
Go back,
Wipe data
Wipe Cache
Go to advanced and select Wipe Dalvik Cache (ignore the SD-EXT error that's normal)
Go to Mounts and Storage - and select Format System
Go back
Go to install zip from sd card, flash ROM, then slect install zip from sd card again and flash Gapps
REBOOT
Enjoy
Again...
Samsuck said:
Download a Galaxy Nexus LTE ROM as well as the Gapps package for it. (AOKP as an example)
Click to expand...
Click to collapse
I'm wondering, as heo_con184 said above, if I can flash the stock ROM? (instead of other ROMs)
Must it be other ROM to make it work?
Thanks in advance.
Up to you, you can also just flash stock images and start over.
My method should work too, and leave you with root
Your choice
highmoon said:
I'm wondering, as heo_con184 said above, if I can flash the stock ROM? (instead of other ROMs)
Must it be other ROM to make it work?
Thanks in advance.
Click to expand...
Click to collapse
You could do it either way.
Okay, I found a solution without wiping everything.
(Flashing a stock ROM image, or other ROMs would wipe your everything...)
But thanks people!
For those of you, who would encounter something like this (including me again), I'm leaving a note.
0) This problem happens because your Boot partition, overwritten by ClockworkMod recovery image, is no longer compatible with the rest 4.0.4 image. So you need not only "recovery.img", but also "boot.img". Unfortunately, boot.img is not there in the 4.0.4 ROM. But luckily, someone else extracted it.
1) Get the 4.0.4 stock image from here
(android.clients.google.com/packages/ota/verizon_prime/659e0a8f24b4.signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip)
2) Extract "recovery.img" from the file above.
3) Get "boot.img" in here (aospdev.com/rhcp/dev/404boot_root.img)
4) Get into FASTBOOT mode
5) fastboot flash boot boot.img (if not renamed, "404boot_root.img" above)
6) fastboot flash recovery recovery.img
6) Enjoy

[Q] Stuck in bootloop Jellybean

Hello All, I flashed the V2 version of the JB Rom on my CDMA GNex and it was working great until I rebooted my phone. Now It is bootlooping.
I can boot into recovery
This is what I have done:
Battery/Sim Card Pull
Catch Wipe/Factory data reset
Tried to Nanodroid back to an older rom
Tried to install AOKP back
All lead to bootlooping
I am sorry if this is has been addressed but any help would be greatly appreciated.
I got it to boot. After many tries it just turned on. Go figure.
How did you exactly get it to work. You said after many tries it just worked. What kind of "tries" did you do because I'm having the same issue? I tried nandroid restore, full system wipe, reinstall of AOKP build40, etc. It keeps bootlooping. Help
If all else fails, Nexus Factory Images will always be available.
Its been so long since I done the fastboot and stock 4.0.4. I'm afraid I have forgotten. I looked at that page and downloaded the stock image but I'm not sure how to use the fastboot and adb commands anymore.
elusiveaura said:
Its been so long since I done the fastboot and stock 4.0.4. I'm afraid I have forgotten. I looked at that page and downloaded the stock image but I'm not sure how to use the fastboot and adb commands anymore.
Click to expand...
Click to collapse
Well, if you have ADB and fastboot installed, that's a good start. All you need to do is unzip the file and place it where your terminal will recognize it. Then turn on USB debugging on in developer settings, then boot into your boot loader (Power + Volume Up + Volume Down) and type in "sh flash-all.sh" or you can do it manually, "fastboot flash recovery recovery.img, fastboot flash bootloader bootloader.img" etc... This will wipe all your data, including your SD card.

[Q] Am I bricked?

Please help! I am new to this and am worried I bricked my phone.
I successfully rooted my Verizon Samsung Galaxy Nexus using a toolkit. It was then working fine with 4.2.2. I wanted to install Shiny Rom 4.4.2. I thought I successfully backed up apps and data using Titanium Backup.
I successfully moved the correct zip files to my phone, and realized I needed Clockworkmod recovery. I followed a procedure to get this on my phone by using my computer's command prompt. I successfully booted into Clockworkmod recovery and followed the process of wiping data/factory reset, successfully installed radio and bootloader recommended to install with ShinyROM but got stuck and could not install the ShinyROM itself. I think it is because it requires a later version of Clockworkmod. The one I downloaded using the procedure was 5.5.0.4, but I think I need a later version. I tried following the same procedure using my computer's command prompt and it got stuck at "waiting for device". I cannot get out of Clockworkmod recovery now (even battery pull, etc.). I then found some threads saying I need to restore my old ROM first. (I think) the only ROM on my phone is ShinyROM. I am stuck and stressed out because I do not know of a way of "pushing" the new version of Clockworkmod to my phone.
Can I fix this, or do I need to start shopping?
[email protected] said:
Please help! I am new to this and am worried I bricked my phone.
Can I fix this, or do I need to start shopping?
Click to expand...
Click to collapse
i think u already wiped data partition at first, that why your Rom installation aborted bcoz recovery cant mount any partition.
still got your old system partition here.
from recovery ~ try adb sideload your shinyRom. can your pc detected bootloader (fastboot)/recovery?
memaro_maro said:
i think u already wiped data partition at first, that why your Rom installation aborted bcoz recovery cant mount any partition.
still got your old system partition here.
from recovery ~ try adb sideload your shinyRom. can your pc detected bootloader (fastboot)/recovery?
Click to expand...
Click to collapse
Regarding partition, I have an option to wipe cache partition. Should I do this?
Update
Well, I went ahead and tried this, and still could not install ShinyROM.
I tried to follow a procedure in the link to use ADB sideload.
I downloaded (full) SDK and updates and updated the drivers. When I get to the following steps from the procedure...
-Boot your device in recovery mode (Android logo with a exclamation mark) and connect your device to PC
-Hold down "power" button first, followed quickly by "volume up" button. You should now see the recovery menu
I only boot to CWM and there is no Android with Exclamation mark. Holding down power button only selects whichever option is highlighted within CWM.
Also, it seems within CWM, there is supposed to be an option to sideload a zip file. This option does not exist in my version of CWM.
[email protected] said:
Regarding partition, I have an option to wipe cache partition. Should I do this?
Update
Well, I went ahead and tried this, and still could not install ShinyROM.
I tried to follow a procedure in the link to use ADB sideload.
I downloaded (full) SDK and updates and updated the drivers. When I get to the following steps from the procedure...
-Boot your device in recovery mode (Android logo with a exclamation mark) and connect your device to PC
-Hold down "power" button first, followed quickly by "volume up" button. You should now see the recovery menu
I only boot to CWM and there is no Android with Exclamation mark. Holding down power button only selects whichever option is highlighted within CWM.
Also, it seems within CWM, there is supposed to be an option to sideload a zip file. This option does not exist in my version of CWM.
Click to expand...
Click to collapse
set up fastboot and flash twrp then.
xzilem said:
set up fastboot and flash twrp then.
Click to expand...
Click to collapse
Thanks. I found another thread that led me to the same conclusion, except I was able to do it with CWM and fastboot the latest version using ADB sideload. I still haven't posted enough to link, but here were the details from user camblue.
"
If you know how to use ADB you can always fastboot a recovery.img,,,,this thing is almost impossible to truly brick. IN order to get into fastboot just connect to your computer and run adb with these commands
adb reboot bootloader
once in fastboot mode write this
fastboot devices
that will tell you if your device is connected and reading in fastboot mode if it is you will see something like fastboot and some numbers next to it. If nothing you do not" have the fastboot drivers installed.
then to fastboot flash a recovery.img write this
fastboot flash recovery r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever recovery.img you are using or have in your tools folder of you SDK location).
and in order to get right into CWM if you cant boot write this
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img
hope that helps
"

Nexus 7 - 2nd gen: update failed to Lollipop 5.1

HI everyone,
I updated "successfully" from Kitkat to 5.0.2 on my rooted (stock ROM) Nexus 7 second gen.
Unfortunately, when I tried to upgrade to 5.1 everything seem to be normal until the device rebooted and it went through the "update process". 3/4 the way through, the green droid went on his back and the "ERROR" message appeared.
I wiped the cache partition but that doesn't help. I tried to download the update in safe mode, but no success. I also find it odd that each time I reboot my device, I get a message from Android that it is "updating my apps".
If I didn't have any apps and a lot of data on my Nexus, I would wipe the device clean but I'd rather avoid this, if at all possible.
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Thanks
Michael Carleone said:
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Click to expand...
Click to collapse
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
k23m said:
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
Click to expand...
Click to collapse
Hi,
Thanks for the reply. I rooted with Kingroot. I don't believe I have a custom recovery. The bootloader is locked as shown when I boot into recovery mode.
I want to avoid transferring my data and APK files to my PC.
Should I assume there is no way of reinstalling the OS without wiping out the device?Also, there is no link in the above quote: fastboot boot twrp-3.0.2-0-flo.img
Since I got no other replies, I went and restored to factory image. I do have another question. I hope I get a better response there: http://forum.xda-developers.com/nex...a/nexus-7-2013-wifi-root-marshmallow-t3515072
Thanks for the reply.
Can we compare using fastboot flashing TWRP vs Nexus Root Tool Kit: http://www.wugfresh.com/nrt/? I ended up using this utility instead because it was pretty much one click and it didn't require command lines and for whatever reason, I found instructions using fastboot a bit confusing. Which method is better or has more advantages? I left my bootloader unlocked.
Incidentally, I think there was something wrong with my Nexus image. As a result, I did use Google's instructions on how to flash etc. the OEM image. Instructions weren't ideal but I managed to figure things out: https://developers.google.com/android/images
The instructions are here which I assume would be similar if I wanted to fastboot TWRP?
To flash a system image:
Download the appropriate system image for your device below, then unzip it to a safe directory.
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
Using the adb tool: With the device powered on, execute:
adb reboot bootloader
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device. For example, to put a Nexus 5 ("hammerhead") into fastboot mode, press and hold Volume Up + Volume Down + Power as the device begins booting up.
If necessary, unlock the device's bootloader by running:
fastboot flashing unlock
or, for older devices, run:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Also, I could've sworn that when I rooted KitKat on my Nexus, my data wasn't wiped out. I don't recall doing anything to the bootloader. I can't recall which method I used, but I know for certain I didn't use the Nexus Root Toolkit. I should've recorded my steps when I rooted.
i rooted my nexus 7 using towel root on kitkat .. i unrooted using supersu... and ota untill marhsmallow with out a problem never use kingroot as its so un stable.

Help, possibly bricked phone

Hello, I am currently rooted and on stock on pixel xl. I am trying to flash the pure nexus rom. I downloaded through the link in the op, factory reset and flashed through twrp (3.0.2rc1). When I went to reboot, it said OS not installed. Can anyone offer any assistance with this? Needless to say, I didn't reboot with that. I did however do a backup (of stock) prior to this. I decided to restore my backup but when it rebooted it said something about the vender image is not right with this system and to flash the correct image. This is exactly what its saying : Your vendor image does not match the system. Please flash the NOF27C vendor image for your device. I have managed to move the correct image file to the internal storage but from what i read, can only install through twrp.
And when it finished rebooting, now 90% of my apps are crashing, no fingerprint hardware, developer options are not available and I had to reboot back into recovery but its like twrp is gone, it looks like the stock recovery. Somehow it appears there are parts of my stock rom and pure nexus rom combined which is understandbly causing my issues. Right now I am trying to get back to having twrp but am stuck.
I have since tried to reinstall twrp but when I plug my xl into my pc, the pc recognizes it but no storage. I cant move a file from pc to xl because its saying disconnected or not responding. Tried to get a command prompt and when I shift/right click, there is no option. I don't know what else to do.
If anyone has any suggestions, please help. I am freaking over this. Can't use my phone in the state its in.
Sounds far from bricked.
Just entirely screwed up.
FASTboot the latest factory image and then refrain from tinkering for the weekend.
These are the steps i use.
I think a new ADB/FastBoot package was released yesterday you might want to install that.
Execute fastboot commands (assuming the bin is on your PATH)
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
To add TWRP and Root:
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip

Categories

Resources