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
i wiped my cache partition on my gnex in cwm... which then got me into a bootloop. now whenever i hit recovery it goes to twrp and i accidently wiped my system on it. now it cant connect to the computer, my nexus rootkit doesnt detect an adb device and i do not have a backup or rom on my sdcard. my fastboot is working and whenever i boot it normally it is stuck at the google screen with an unlocked bootloader symbol. PLS HELP! thx in advance.
use the adb sideload option in twrp to put a rom into your storage via adb, so you can flash it. dont use the toolkit, use adb from your computer. the command is shown on the screen when you enable the adb sideload option.
my phone is rooted for a few months and now i decided to reset my device after restart i am stuck in cwm recovery loop.
cwm recovery is working and is displayed every time i restart
odin is not detecting my device
usb debugging is off as it has been reset
please help
used pdanet+ from http://forum.xda-developers.com/show....php?t=1983470
and minimal adb from http://forum.xda-developers.com/show....php?t=2317790
tried some commands like restart bootloader
dont know what to do ahead
any commands to flash stock recovery or delete cwm recovery from phone using adb or cwm
EncryptedWonderkid said:
my phone is rooted for a few months and now i decided to reset my device after restart i am stuck in cwm recovery loop.
cwm recovery is working and is displayed every time i restart
odin is not detecting my device
usb debugging is off as it has been reset
please help
used pdanet+ from http://forum.xda-developers.com/show....php?t=1983470
and minimal adb from http://forum.xda-developers.com/show....php?t=2317790
tried some commands like restart bootloader
dont know what to do ahead
any commands to flash stock recovery or delete cwm recovery from phone using adb or cwm
Click to expand...
Click to collapse
As far as CWM works properly, connect phone to your computer and "mount usb storage" you can install a recovery that provides "reboot to download mode"
In case you have Samsung i8552 as i read in your profile info this --> CWM 6.0.4.7 flashable ZIP is the latest recovery for your phone.
Question: Have you tried entering "DOWNLOAD" mode manually by pressing "Vol down + home + power" while device is turned off?
in download mode my phone is not recognised because usb debugging is off after reset
used samsung driver and pdanet+ driver
only in cwm recovery is phone detected
using cwm recovery installed custom rom even after that phone enters cwm recovery loop
i had deleted cache partition and followed instructions for the rom
update:
after using kies,odin detected my phone
after that successfully flashed stock recovery
all is well now
I wasn't able to adb sideload from recovery though I could when the phone was on. so i tried clearing cache from stock recovery and it got interrupted. Now when i start the phone, boot loops and i can't even enter recovery. Any help please!
Update
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
AnudeepS said:
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
Click to expand...
Click to collapse
Where are you getting your adb/fastboot toolkit? If using the ones your Linux distro (Debian, Ubuntu, etc) provided, then consider them out of date. I had the same problem with fastboot recognizing my phone...once I downloaded fresh ones from Google's SDK, I was back in business!
Am on windows and i had fastboot_adb(1.0.32) already installed.
Update
I could update by flashing through Kernel Adiutor app (needs root permission & Busybox). Root lost when flashed complete firmware and root remained when flashed just the update file.zip.
what i did was-
I put zip file (completely downloaded firmware from ASUS website-also tried OTA downloaded and updated the phone) on MicroSD card, renamed the file MOFD_SDUPDATE.zip. This flashed through Kernel Adiutor app- recovery- cwm-flash.
Re-reooted the phone with 1 click method (method #3) when flashed the complete rom. If you just flash the update zip root remained.
All working fine for now.
PS: I use Z008 2gb model.
I hope all of you would be fine.
I was trying to install a custom ROM in my HTC one X via CWM recovery. I formatted the system partition (ROM) and tried to flash the new ROM. I ended up soft bricking my phone as the ROM file was corrupt. I tried to push another ROM.zip file into the phone memory via adb. My phone shows up in fastboot devices when it's turned on but it's not detected as adb device. When I turn it off then it shows up in the attached adb devices list. I used the adb push command to transfer the ROM file into the phone memory and cmd tells me it's done as it shows the transfer speed and the size of ROM file. Now the issue is that when I try to search for that ROM file in CMW recovery, it's not there in the memory.
It's been three days since I have been trying to make my phone alive but nothing seems to work.
Any help from you guys would really be appreciated
*My phone shows up in abd devices only when it's turned off.
*The adb pushed ROM.zip file is not present in the phone memory.
*All the drivers are correctly installed and my phone is listed as 'My HTC' in device manager.
Hey there, sorry for a late answer, but right now I have some town-wide internet problems, so...
Back to your problem then, if you cant have any result with adb push, try to use another method:
1. Complete steps at this link https://twrp.me/htc/htconexinternational.html to install twrp
2. Reboot to your twrp recovery
3. Choose "Mount" option and mount any partition you need(depending on your layout), after this step, you can access you phone storage with you pc.
4. Now you can wipe everything you want, do not reboot, and go to "install" option.
5. Just copy/paste you ROM, install it, reboot to fastboot, flash boot.img
Done.
Have a nice day.