Related
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)
Good morning guys,
I see a lot of threads here about rooting 4.2.2, but in all of them it is recommended to root the phone by installing zip archive from a custom recovery.
I don't want to change stock recovery - is there any way to root it by flashing img from adb? I did it in this way on 4.2.1, by installing CF-Auto-Root-mako-occam-nexus4.img file from adb.
Can anyone advice how to get root without flashing custom recovery?
I have to ask,....why would you NOT want a custom recovery? What is the point in using a crippled stick recovery?
From my Evo LTE, yup.
Look at this How to thread in the general section, I copied and pasted relevant information. I kept a custom recovery and didn't try this method, but it says it will not flash a custom recovery.
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
2) Rename the file to customrecovery.img, and make sure it is in the same directory as your fastboot.exe file;
3) Download (to /sdcard on your device) the latest version of either ChainsDD's Superuser (not currently working), or Chainfire's SuperSU;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img
6) Wait for it to boot;
7) Navigate the menus the recovery menu on your device and select an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
8) Reboot. Done.
You can flash custom recovery via fastboot, use it to install su.zip and when you will choose restart after that, you will have question about you want custom recovery permanently or not, if you choose no then after restart you will have stock recovery
scottspa74 said:
I have to ask,....why would you NOT want a custom recovery? What is the point in using a crippled stick recovery?
From my Evo LTE, yup.
Click to expand...
Click to collapse
I want to make installing of future OTA as simple as possible. So I will get root and freeze all the system apps i don't want to be run, but when OTA comes I will be able to install it and will not receive any error messages which i had during this OTA.
It seems like this is a good solution:
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img
Click to expand...
Click to collapse
Do i understand correctly that this boots customer recovery on my phone from PC hard drive, but doesn't flash it to the phone? So, I'm able to install root.zip from it, but when i reboot the phone I don't have a custom recovery.
You can do as i mentioned in my post before or you can use as well command mentioned by ketjr81: fastboot boot nameofrecovery.img in both cases you will have had stock recovery after restart
Thank you guys, you have solved my issue. Now i have to find a ZIP with root to flash.
fatum2002 said:
Thank you guys, you have solved my issue. Now i have to find a ZIP with root to flash.
Click to expand...
Click to collapse
you find it in thread mentioned by ketjr81
Greetings, folks,
I just picked up the LG G2 for Verizon yesterday. Now I'm having an issue trying to root, or it may have to do with recovery.
I follow this method:
www.youtube.com/watch?v=HKuedInhdjU
I get my device rooted. I use Root Checker to verify. The next step is unlocking the boot loader (or bypass it), because when I try to boot into recovery, I get the triangle.
I attempt the Loki method, but I eventually get "this is not a flash" message near the end (wording is something to that effect).
http://forum.xda-developers.com/showthread.php?p=45715059
I try flashing the recovery image via Google app like Goomanager, but it doesn't seem to work (doesn't put me in recovery, or hangs up on the process message).
What am I doing wrong?
Wildcat3699 said:
Greetings, folks,
I just picked up the LG G2 for Verizon yesterday. Now I'm having an issue trying to root, or it may have to do with recovery.
I follow this method:
www.youtube.com/watch?v=HKuedInhdjU
I get my device rooted. I use Root Checker to verify. The next step is unlocking the boot loader (or bypass it), because when I try to boot into recovery, I get the triangle.
I attempt the Loki method, but I eventually get "this is not a flash" message near the end (wording is something to that effect).
http://forum.xda-developers.com/showthread.php?p=45715059
I try flashing the recovery image via Google app like Goomanager, but it doesn't seem to work (doesn't put me in recovery, or hangs up on the process message).
What am I doing wrong?
Click to expand...
Click to collapse
Get the recovery .img from this thread: http://forum.xda-developers.com/showthread.php?t=2449670
Get the free app from the appstore "flashify" and flash the recovery, then boot into recovery. The triangle is the stock recovery. You need to flash a recovery that is "lokified" then backup and flash away.
Mandelbrot.Benoit said:
Get the recovery .img from this thread: http://forum.xda-developers.com/showthread.php?t=2449670
Get the free app from the appstore "flashify" and flash the recovery, then boot into recovery. The triangle is the stock recovery. You need to flash a recovery that is "lokified" then backup and flash away.
Click to expand...
Click to collapse
The message I get at the last step of the thread you and I linked is: "sh: loki_flash: not found."
I get this after I go through the process described in the steps to that thread. I also tried flashing the image directly with Flashify, but that didn't work. I assume because it's not lokiified.
Is there a place I can get a lokiified image?
Wildcat3699 said:
The message I get at the last step of the thread you and I linked is: "sh: loki_flash: not found."
I get this after I go through the process described in the steps to that thread. I also tried flashing the image directly with Flashify, but that didn't work. I assume because it's not lokiified.
Is there a place I can get a lokiified image?
Click to expand...
Click to collapse
Why didn't flashify work? What error it give?
I've rooted my phone...not a problem.When I try to boot into recovery mode using and app like TWRP or ROM Manager premium, I get past the LG G2 splash screen, then I get the belly-up android guy with a red asterisk...how can i get around this to flash my ROM? What am I doing wrong?
HeatM1ser said:
I've rooted my phone...not a problem.When I try to boot into recovery mode using and app like TWRP or ROM Manager premium, I get past the LG G2 splash screen, then I get the belly-up android guy with a red asterisk...how can i get around this to flash my ROM? What am I doing wrong?
Click to expand...
Click to collapse
if I remember correctly that means your recovery did not flash correctly so I recommend using either flashify or freegee from playstore and retrying
It is actually the stock recovery. Try again flashing TWRP or CWM
Sent from my LG-VS980 using Tapatalk
XxZombiePikachu said:
if I remember correctly that means your recovery did not flash correctly so I recommend using either flashify or freegee from playstore and retrying
Click to expand...
Click to collapse
I installed Flashify, rebooted the phone...now its stuck in fastboot mode....what can I do?
HeatM1ser said:
I installed Flashify, rebooted the phone...now its stuck in fastboot mode....what can I do?
Click to expand...
Click to collapse
ok there is a guide here somewhere which explains that if you were trying to install recovery and then go stcuck in fastboot mode you have to get the stock recovery back let mee if I can find the guide and i'll report back
re-edit: try this thread http://forum.xda-developers.com/showthread.php?t=2477595 also you can find needed files here http://downloads.codefi.re/autoprime/LG/LG_G2/VS980/Stock_Firmware make sure you download correct files for your firmware
25536955 22
XxZombiePikachu said:
ok there is a guide here somewhere which explains that if you were trying to install recovery and then go stcuck in fastboot mode you have to get the stock recovery back let mee if I can find the guide and i'll report back
re-edit: try this thread http://forum.xda-developers.com/showthread.php?t=2477595 also you can find needed files here http://downloads.codefi.re/autoprime/LG/LG_G2/VS980/Stock_Firmware make sure you download correct files for your firmware
Click to expand...
Click to collapse
Thanks a lot! I followed that guide, and afterwards I was no longer even able to get into recovery/download mode....so I though I was even worse trouble....since one the the instructions was to erase the LAF file and flash it again with a downloaded LAF image, I decided to go to the link with all the files you provided and flash each of them....rebooted, and the phone was able to get into recovery mode again...Then I pushed the file for my phone ( http://downloads.codefi.re/autoprime/LG/LG_G2/VS980/Stock_Firmware) using Uptest (R&D Tool), rebooted and the phone worked.
I'm trying to flash the Black YouTube from TBO but I can't figure how.
Tried to flash from stock recovery but I think I'm doing something wrong, because it didn't worked.
Can someone tell me the steps to flash this? Do I need a custom recovery or not?
flatex said:
I'm trying to flash the Black YouTube from TBO but I can't figure how.
Tried to flash from stock recovery but I think I'm doing something wrong, because it didn't worked.
Can someone tell me the steps to flash this? Do I need a custom recovery or not?
Click to expand...
Click to collapse
Yes, you need.
flatex said:
I'm trying to flash the Black YouTube from TBO but I can't figure how.
Tried to flash from stock recovery but I think I'm doing something wrong, because it didn't worked.
Can someone tell me the steps to flash this? Do I need a custom recovery or not?
Click to expand...
Click to collapse
Yes you need custom recovery.
Just download the TWRP 3.0.M2-0 and flash it via adb by using this command in cmd window -
fastboot flash recovery <filename.img>
Whereas, the <filename.img> is the filename of your twrp recovery which you will download.
For example -
If you have downloaded the custom recovery with the filename "twrp 3.0.x.x" then you have to type the following code -
fastboot flash recovery twrp 3.0.x.x.img
After flashing the twrp, now reboot to recovery.
Once you are in recovery, go to install section and locate the zip file (your black YouTube zip file), select it and then swipe to flash.
After flashing, just reboot the system. That's it.
juyel92 said:
Yes you need custom recovery.
Just download the TWRP 3.0.M2-0 and flash it via adb by using this command in cmd window -
fastboot flash recovery <filename.img>
Whereas, the <filename.img> is the filename of your twrp recovery which you will download.
For example -
If you have downloaded the custom recovery with the filename "twrp 3.0.x.x" then you have to type the following code -
fastboot flash recovery twrp 3.0.x.x.img
After flashing the twrp, now reboot to recovery.
Once you are in recovery, go to install section and locate the zip file (your black YouTube zip file), select it and then swipe to flash.
After flashing, just reboot the system. That's it.
Click to expand...
Click to collapse
Thanks man.
flatex said:
Thanks man.
Click to expand...
Click to collapse
It's my pleasure to help you. ?
juyel92 said:
It's my pleasure to help you.
Click to expand...
Click to collapse
I forgot to say that I'm using KK v2.22.40.54
Can I install the TWRP 3.0.M2-0 in this version?
flatex said:
I forgot to say that I'm using KK v2.22.40.54
Can I install the TWRP 3.0.M2-0 in this version?
Click to expand...
Click to collapse
First unlock your device bootloader and then flash the TWRP 3.0M2-0 recovery.