Database Users

[GUIDE] Install ClockworkMod Recovery image after updated to 2.3.4 (GRJ22).

Not applicable
Delete this thread

Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!

Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.

Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.

bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?

Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse

andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?

This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App

bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore

zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers

andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist

16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist

Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S

No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk

nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?

I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.

dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?

I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?

hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....

just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

[Q] Tried to update ATT G2 booted into TWRP, unable leave TWRP or go to Download mode

When I got my ATT G2 I rooted it, and installed TWRP custom Recovery. A week ago I got a system update notification, without thinking I updated the phone. It rebooted into TWRP recovery, and all I can do is navigate around the Recovery. I factory restored my phone, so I don't have SU, and I can't enter download mode. Any ideas on how I can fix my phone, or go about getting it replace?

SpectralFlames said:
When I got my ATT G2 I rooted it, and installed TWRP custom Recovery. A week ago I got a system update notification, without thinking I updated the phone. It rebooted into TWRP recovery, and all I can do is navigate around the Recovery. I factory restored my phone, so I don't have SU, and I can't enter download mode. Any ideas on how I can fix my phone, or go about getting it replace?
Click to expand...
Click to collapse
You could try pushing a rom to twrp from adb if your PC doesn't recognize try Koush universal drivers to make it recognize

RubbleTea said:
You could try pushing a rom to twrp from adb if your PC doesn't recognize try Koush universal drivers to make it recognize
Click to expand...
Click to collapse
Could you give me instructinos on how I would do that?

I was having the same issue after accidentally installing an update on my VZW G2. I tried evey solution for 9 hours with no luck including the Koush universal drivers. The only way I could get the phone to be recognized by any computer was to use ubuntu. Once I had the JDK and SDK installed I ran the commands from this tutorial - http://forum.xda-developers.com/showthread.php?t=2451696
I hope this helps someone out
if you dont have ubuntu installed on a computer you could always make a live cd and run it from that

CoryFNM said:
I was having the same issue after accidentally installing an update on my VZW G2. I tried evey solution for 9 hours with no luck including the Koush universal drivers. The only way I could get the phone to be recognized by any computer was to use ubuntu. Once I had the JDK and SDK installed I ran the commands from this tutorial - http://forum.xda-developers.com/showthread.php?t=2451696
I hope this helps someone out
if you dont have ubuntu installed on a computer you could always make a live cd and run it from that
Click to expand...
Click to collapse
MATE you saved my day...thanks so much....got the stock image back working again with the help of the command in the thread you where mentioning.
thanks once more.
best.
upage

back to square 1

So I completely wiped my LG G2 ATT D800 via twrp after the OTA update made me bootloop. i am running TWRP 2.6.3.3. I would try and get back to stock via the flash tool but my PC wont read the phone. Device Manager Says LG-D800 but has the happy little triangle next to it! I don't have ADB on my pc so i think the sideload option is out.
right now i will try and learn anything to fix this phone. so please give me some feed back. Right now all i can do is boot to TWRP. I can not get to download mode. so please give me some options where or how to get ADB and what to do with it. I have installed every driver available but no dice. Maybe because it in TWRP. idk. Thanks guys.

bump

rawb123456 said:
bump
Click to expand...
Click to collapse
Try installing adb from android SDK...very simple and sideload a ROM...my guess would be easiest....for your PC recognizing your phone do you have the drivers installed? Try koush universal drivers?...or try going to download mode and flash to stock ....hope this helps

[Q] No noob, Recovery problems.

So i got my brand new verizon Lg G2 Yesterday, straight from verizon. It came stock Running VS98012B, Build number JDQ39B, Android 4.2.2.
I ran it completely stock for a little bit, and loved it. But ima crack flasher, and cant run stock for long. So i decided to root. I Used ioroot24 With a few hiccups(ADB drivers wouldnt install with windows 7, So i had to boot into windows xp and do the process).
So im now running the same software with a completely functioning and full root. Next step was to install TWRP or Cwm(philz). I followed WACOmalts Guide.... with no success.
(http://forum.xda-developers.com/showthread.php?t=2449670) This one.
Option 1 Goes good until this step
"./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img"
It always says something failed (Not sure about the message Because i cant repeat it now) Or it gives me a list of commands, as if i typed "adb"
Option 2 I can follow completely through with no errors, But rebooting into recovery always brings me to a black screen.
Ive tried the 2.6.3.1 and the 2.6.3.2 .img files with so success. So i downloaded both 2.6.3.3 and 2.7.0.0 zips and extracted the recovery img and tried using those files. Still a black screen.
Option 3 Just dont work for me.
Has anyone Had his trouble before? Im not a huge noob, Ive had a optimus l9, galaxy nexus, and htc incredible 4g, All with working recoverys So im sure i have enough knowledge. Please Help!

s-chassis said:
So i got my brand new verizon Lg G2 Yesterday, straight from verizon. It came stock Running VS98012B, Build number JDQ39B, Android 4.2.2.
I ran it completely stock for a little bit, and loved it. But ima crack flasher, and cant run stock for long. So i decided to root. I Used ioroot24 With a few hiccups(ADB drivers wouldnt install with windows 7, So i had to boot into windows xp and do the process).
So im now running the same software with a completely functioning and full root. Next step was to install TWRP or Cwm(philz). I followed WACOmalts Guide.... with no success.
(http://forum.xda-developers.com/showthread.php?t=2449670) This one.
Option 1 Goes good until this step
"./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img"
It always says something failed (Not sure about the message Because i cant repeat it now) Or it gives me a list of commands, as if i typed "adb"
Option 2 I can follow completely through with no errors, But rebooting into recovery always brings me to a black screen.
Ive tried the 2.6.3.1 and the 2.6.3.2 .img files with so success. So i downloaded both 2.6.3.3 and 2.7.0.0 zips and extracted the recovery img and tried using those files. Still a black screen.
Option 3 Just dont work for me.
Has anyone Had his trouble before? Im not a huge noob, Ive had a optimus l9, galaxy nexus, and htc incredible 4g, All with working recoverys So im sure i have enough knowledge. Please Help!
Click to expand...
Click to collapse
Just ran into the same issue it doesn't seem like anyone has an answer for this yet, some from this thread http://forum.xda-developers.com/showthread.php?t=2584052
said they were able to just flash back to stock and do everything over and it worked but I was looking into to that but the KDZ method is apparently broken at the time and for the TOT method to restore I can't find a VS98012B (latest VZ firmware so far) TOT file to use for the restore so I don't break anything else.
I'll see what I can find and let me know if you find anything :good:

try Flashify app from the store :good:

Ok so "s-chassis" so being as persistent as I am:laugh:, I was able to find the stock recovery for VS98012B in another thread you can download it here:
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=193184686
Look at post #10
Then I used the dd method to flash the recovery, here it is if you forgot
adb push recovery_vs98012b.img /data/local/tmp/recovery_vs98012b.img
adb shell
(IF YOU DONT SEE A # prompt, type su to get it.)
cd /data/local/tmp
dd if=/data/local/tmp/recovery_vs98012b.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
I got back to the stock recovery but the android has a red exclamation mark on it not sure why but if you have any ideas let me know