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)

recovery verified failed-ICS

hello
i want to change my OTA rom to some other rom and when i reboot into recovery i get the red "recovery verified failed"
how to fix it?
i'm with ics ..
thanks

Fix Ya!
I7210I said:
hello
i want to change my OTA rom to some other rom and when i reboot into recovery i get the red "recovery verified failed"
how to fix it?
i'm with ics ..
thanks
Click to expand...
Click to collapse
Download Acer Recovery Instaler From Tha Play Store And Flash Stock Recovery
Cheers

ok...now how i'm changing the rom to Lightspeed_4.8(for example)...
i just that my hdd will work with that(something that worked in 3.2.1 and now doesn't work)

I7210I said:
ok...now how i'm changing the rom to Lightspeed_4.8(for example)...
i just that my hdd will work with that(something that worked in 3.2.1 and now doesn't work)
Click to expand...
Click to collapse
Look [root] Ntfs Mounter In The Play Store
If I Helped Please Press Thanks Button.

these thing doesn't work by the way at 4.XX hdd's suppose to work without any app
but both the app and the ics doesn't read the hdd and the hdd is formatted.
so i thought it will be better to install costum rom but i need an recovery for that right now,there i'm stuck

I7210I said:
hello
i want to change my OTA rom to some other rom and when i reboot into recovery i get the red "recovery verified failed"
how to fix it?
i'm with ics ..
thanks
Click to expand...
Click to collapse
THIS IS FROM EAZYTERRYS
The real answer is if you have ICS, to install a custom recover or custom kernel you must have an unlocked bootloader.
The following resources are related to the new bootloader, a quick read of the OPs of the first two are highly recommended, even if you install with the third link. (This is to have a highlevel idea of what you are changing on your device, as it will help you find what you need to look closer at in future if something goes wrong, or possibly prevent a problem in the first case) bootloader thread civato's guide Afterota tool (windows users bootloader install tool)
If you already have the unlocked bootloader installed, but can't boot into recovery:
This is likely because you have a stock ICS rom overwritting recovery with the stock recovery in every boot; either use fastboot or (if you have root) a program such as acer recovery installer to force the install of a recovery and immediately reboot into it. (Most bootloader installers will also install a recovery that you can immediately boot into)
Once in recovery you can backup/restore/or install a rom modified to prevent the overwrite of recovery. (More advanced users can stop this from adb by removing some files)
Personally I use a lightly modified version of the stock rom you are using now: http://forum.xda-developers.com/show....php?t=1661492
it ought to be safe to do a no wipe update to that and receive a more expected environment with a custom recovery, optional custom OC kernel, and busybox support.
However if you explore the dev section, many other (both more and less modified) versions of ICS roms exist. Themed and otherwise. So feel free to explore.

jancarlos1597 said:
Download Acer Recovery Instaler From Tha Play Store And Flash Stock Recovery
Cheers
Click to expand...
Click to collapse
I had the same problem. After I have done this I still can't boot into recovery. I only see a dead Android guy. What should I do now? I really need help.
----
I just used my brain and figured out by myself.
A brain is such a useful thing.

ok
i try to mount these hdd
http://wdc.com/en/products/products.aspx?id=430
the 750GB
and with these rom
http://forum.xda-developers.com/showthread.php?t=1661492
also with these rom
http://forum.xda-developers.com/showthread.php?t=1520299
and it doesn't go ,with 3.2.1 it goes what can be the problem?

[Q] Corrupt boot partition aka aboot

Hi all,
I want to install custom kernel on SHV-E330L, if custom kernel malfunction then phone will not boot. So i want to confirm in which state phone will be, on galaxy s4 startup logo or will not power on at all?
I think aboot and recovery both are bootable partition so it is possible is aboot is does not work then phone can boot into recovery through recovery partition or start in download mode?

Can you still access recovery and download mode?

knuckles1978 said:
Can you still access recovery and download mode?
Click to expand...
Click to collapse
I think didn't understand, i haven't done it. Before playing and bricking phone i am asking what will happen in case of boot partition not able to boot?

galliard said:
I think didn't understand, i haven't done it. Before playing and bricking phone i am asking what will happen in case of boot partition not able to boot?
Click to expand...
Click to collapse
Ahh, okay I see now. If there's a problem with your custom kernel then all you need to do is boot back into download mode which will still work, and then flash the kernel that you were using before again.
So basically, have a copy of a kernel which you know works on your PC ready, in case you have a problem and need to put it back to the way it was.
You shouldn't have a problem though, as long as the custom kernel which you want to install is for the correct android version etc, it should work fine. I've never had such a problem.

knuckles1978 said:
Ahh, okay I see now. If there's a problem with your custom kernel then all you need to do is boot back into download mode which will still work, and then flash the kernel that you were using before again.
So basically, have a copy of a kernel which you know works on your PC ready, in case you have a problem and need to put it back to the way it was.
You shouldn't have a problem though, as long as the custom kernel which you want to install is for the correct android version etc, it should work fine. I've never had such a problem.
Click to expand...
Click to collapse
Thanks for clarification, please tell me that recovery partition is also bootable so if phone can't boot from 'boot' partition so is it possible to phone to boot direct from recovery?
Also please give me an idea if you u don't mind what will b consequences if i try to install GT-I9506 kernel and modem on SHV-E330L?

galliard said:
Thanks for clarification, please tell me that recovery partition is also bootable so if phone can't boot from 'boot' partition so is it possible to phone to boot direct from recovery?
Also please give me an idea if you u don't mind what will b consequences if i try to install GT-I9506 kernel and modem on SHV-E330L?
Click to expand...
Click to collapse
You can only restart the phone from recovery, not boot from recovery. But as I mentioned above, as long as you've got download mode your phone isn't broken. You can mess up anything on your phone, as long as you don't break download mode it's recoverable. You pretty much need to do something really stupid to lose download mode.
Stupid things that could make you lose download mode and completely brick your phone include, but are not limited to: flashing a kernel made for a completely different device Or selecting repartition in Odin but not adding a PIT file.
Never install anything that isn't made for your exact device! There are exceptions, but if you don't know exactly what you're doing then you're just asking for your phone to be bricked. So don't.

PLEASE HELP!!! Phone stuck in bootloop, will not boot. Will not boot into recovery.

I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Edit: I fixed it. had to manually extract and reflash some files from a very useful restore to stock tool.
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
Thank you for all of the help so quickly.

kagarii said:
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Click to expand...
Click to collapse
If your able to boot into bootloader you can try to reflashTWRP or flash the original recovery and the original system files.

kagarii said:
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Click to expand...
Click to collapse
Can you get it into fastboot mode? If you can, it sounds like somehow the recovery is corrupt and you would need to use 'fastboot erase recovery' first, and then 'fastboot flash recovery recovery.img' (using the twrp .img flashable file of course)
I hope that does the trick. Only think I can think of other than that is look for the automated return to stock tool for the moto x 2015 and use that.

thanks
[email protected] said:
If your able to boot into bootloader you can try to reflashTWRP or flash the original recovery and the original system files.
Click to expand...
Click to collapse
fixed it thank you!

thanks
benjmiester said:
Can you get it into fastboot mode? If you can, it sounds like somehow the recovery is corrupt and you would need to use 'fastboot erase recovery' first, and then 'fastboot flash recovery recovery.img' (using the twrp .img flashable file of course)
I hope that does the trick. Only think I can think of other than that is look for the automated return to stock tool for the moto x 2015 and use that.
Click to expand...
Click to collapse
fixed it thank you!

kagarii said:
fixed it thank you!
Click to expand...
Click to collapse
Great news! You're very welcome. I was in that exact same situation with my old Xperia Z2. It's pretty scary.

kagarii said:
fixed it thank you!
Click to expand...
Click to collapse
Can you tell us what fixed it? Do you know if it was firmware related? Was it the recovery? I have multiple people on this device all on custom software, always interested to find the cause of these types of issues for future reference. And most importantly, glad you got it resolved!
Sent from my XT1575 using Tapatalk

DonKilluminati23 said:
Can you tell us what fixed it? Do you know if it was firmware related? Was it the recovery? I have multiple people on this device all on custom software, always interested to find the cause of these types of issues for future reference. And most importantly, glad you got it resolved!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I honestly have no idea what the problem was. But i downloaded and used someones lollipop restore to stock tool, literally restoring to the original state you got the phone in, and it worked. I believe it had something to do with the rom, and possibly some xposed modules i had installed, but there was nothing that actually messed around with the phone's system files. I couldn't access recovery in anyway whatsoever, but my advice to you is that if you ever need help because the phone is potentially hard-bricked, see if it connects to PC and if it does use the restore to stock tool.

kagarii said:
I honestly have no idea what the problem was. But i downloaded and used someones lollipop restore to stock tool, literally restoring to the original state you got the phone in, and it worked. I believe it had something to do with the rom, and possibly some xposed modules i had installed, but there was nothing that actually messed around with the phone's system files. I couldn't access recovery in anyway whatsoever, but my advice to you is that if you ever need help because the phone is potentially hard-bricked, see if it connects to PC and if it does use the restore to stock tool.
Click to expand...
Click to collapse
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.

jDally987 said:
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
Click to expand...
Click to collapse
It's possible, through tools like this. I don't know too much of the topic.

jDally987 said:
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
Click to expand...
Click to collapse
Mine wouldnt let me factory reset in twrp to flash something else while on cr droid it jist vibrates now it wont even boot into cr droid ive try to flash another rom but nothing since recovery suddenly wont let me wipe. Any advice on whats causing this i have a 64 gb adopted sd catd also i think i accidently repartitioned sd card in twrp.

Sherrillface said:
Mine wouldnt let me factory reset in twrp to flash something else while on cr droid it jist vibrates now it wont even boot into cr droid ive try to flash another rom but nothing since recovery suddenly wont let me wipe. Any advice on whats causing this i have a 64 gb adopted sd catd also i think i accidently repartitioned sd card in twrp.
Click to expand...
Click to collapse
Old thread. But can you at least get into TWRP recovery? Why won't it let you wipe? Like what does it say?

jDally987 said:
Old thread. But can you at least get into TWRP recovery? Why won't it let you wipe? Like what does it say?
Click to expand...
Click to collapse
Nothing it just vibrates as soon as i hit factory reset then bootloops now it wont even go into recovery just fastboot screen but cant get fastboot to work at all and have all drivers android studio etc. Nothing will work need a new solution

It was hash kernel it corrupted all 64 gigs of storage and music etc. Had to return to stock via auto flash firmware.

Mine is XT1572 device. Since the mentioned tool was not available for this model, I took the chance with XT1575 tool. It did all the steps but the issue has become worse. Now, my device is automatically getting On and OFF in seconds and does not boot beyond the bootloader 'unlocked' warning screen. Please please please help !!!!

Help needed. Urgently

I had installed cm 13 and tried installing a new kernel but i guess since i was on a old version it didn't work out. So i proceeded with putting the old kernel back *sandy kernel* however now when the phone opens up i put my pass code it shows the background for a split second with a system ui crashed error and back to lock screen. hence i tried installing a recovery again (twrp hybrid) since the latest roms use that and I wanted a new rom anyway. But i thought id back my stuff up but alas the system ui error doesn't allow me to do so. Finally i ended up by using fastboot to flash the new recovery but even after it said OK ! my phone won't boot into recovery.
So now i am stuck with a OP2 that boots into cm13 but cant get past the lockscreen, a recovery that won't load and a fastboot mode that is the only working thing.
God I really shouldve backed it up i know. But is there a way I can resolve this without losing my data?
I have an exam and the notes are in them.
Help is appreciated !

rogermax said:
I had installed cm 13 and tried installing a new kernel but i guess since i was on a old version it didn't work out. So i proceeded with putting the old kernel back *sandy kernel* however now when the phone opens up i put my pass code it shows the background for a split second with a system ui crashed error and back to lock screen. hence i tried installing a recovery again (twrp hybrid) since the latest roms use that and I wanted a new rom anyway. But i thought id back my stuff up but alas the system ui error doesn't allow me to do so. Finally i ended up by using fastboot to flash the new recovery but even after it said OK ! my phone won't boot into recovery.
So now i am stuck with a OP2 that boots into cm13 but cant get past the lockscreen, a recovery that won't load and a fastboot mode that is the only working thing.
God I really shouldve backed it up i know. But is there a way I can resolve this without losing my data?
I have an exam and the notes are in them.
Help is appreciated !
Click to expand...
Click to collapse
Please use the following Guide. Method 1 should be your answer. https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

toxicore said:
Please use the following Guide. Method 1 should be your answer. https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
sir thats a 1gb file and im on data net right now. I'll download it but are you sure it will resolve my issue ?

Just download latest oxygen or cyanogenmod recovery and flash in fastboot it will sure boot to recovery

paradise220 said:
Just download latest oxygen or cyanogenmod recovery and flash in fastboot it will sure boot to recovery
Click to expand...
Click to collapse
thank you for your help sir, even though i tried flashing all kinds of recoveries via fastboot, it says the flash was successful but it still doesn't boot into recovery. Any other suggestions ?

rogermax said:
thank you for your help sir, even though i tried flashing all kinds of recoveries via fastboot, it says the flash was successful but it still doesn't boot into recovery. Any other suggestions ?
Click to expand...
Click to collapse
As I said. the method i showed you is most certainly the solution. But you need a Computer and yes, 1gb is propably too much for mobile data
Maybe, just maybe if you flash OOS-Firmware it might help. But i dont know for sure.

So i finally managed to get into twrp 2.8.7 (lollipop)by this http://forum.xda-developers.com/devdb/project/dl/?id=16684
thanks a lot for all your hard work guys ! (cant boot into os still but twrp will help atleast)