Database Info

cant load recovery

Hey guys..
I just today rooted my lovely Nexus S, 9023 or what its called (non branded or nothing)
But i cant load recovery.. went fine when i rooted it, but now that i want to load an custom rom it fails.. i followed this guide to root: http://forum.xda-developers.com/showthread.php?t=883032
Anyone have some ideas??
I just get a android logo and triangle + ! in it.. as error.. (
Best regrads
n0ta

Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.

n0ta said:
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
Click to expand...
Click to collapse
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App

I have had this happen on my NS4G. I know they are a little different, but it seems like you are having the same thing happen that I did and to solve it, I open Windows command prompt(or terminal depending on you OS) and fastboot flash recovery (insert recovery.img name here) and reflashed the recovery partition with clockwork. Very easy fix. Just make sure you boot straight into recovery after flashing and flash the Rom you want to flash before booting back into stock(also make a nandroid before that). After that you shouldn't have any more problems unless you unroot. There must be a small glitch somewhere when flashing the clockwork doesn't fully erase stock recovery partition.

krohnjw said:
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Works now thanks all to both of you.

n0ta said:
Works now thanks all to both of you.
Click to expand...
Click to collapse
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...

bender_123 said:
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
Click to expand...
Click to collapse
The Nexus one did the same thing. Most OTAs verify / replace this file. It's easy enough to deal with if you're unlocked and rooted.
Sent from my Nexus S 4G using XDA Premium App

This is about the third or fourth time this question has come up over the past week...

bender_123 said:
This is about the third or fourth time this question has come up over the past week...
Click to expand...
Click to collapse
I assure you it won't be the last.
Sent from my Nexus S 4G using XDA Premium App

I can no longer get into clockwork recovery...

I am on brainmasters miui rom, and whenever I try to go into recovery the phone just gets stuck on the Google logo and doesn't move, forcing me to pull the battery. I have tried reflashing the recovery numerous times and idk what to do from here. Any help would be greatly appreciated.
Sent from my Nexus S

Tried flashing another version of the recovery?

The K-Zoo Kid said:
I am on brainmasters miui rom, and whenever I try to go into recovery the phone just gets stuck on the Google logo and doesn't move, forcing me to pull the battery. I have tried reflashing the recovery numerous times and idk what to do from here. Any help would be greatly appreciated.
Sent from my Nexus S
Click to expand...
Click to collapse
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.

simms22 said:
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
Click to expand...
Click to collapse
+1
I also made the experience that flashing recovery through rom manager doesn't always work...had the same problem, also using brainmaster's MIUI rom.

simms22 said:
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
Click to expand...
Click to collapse
How would i go about doing this?

Check the rooting guides for the directions.
Sent from my Nexus S 4G using xda premium

I tried looking for directions on how to do it and for some reason I can't seem to find them.
Sent from my Nexus S

You obviously didn't try very hard
http://forum.xda-developers.com/showthread.php?t=1067813
[REF] Complete List of Roms | Kernels | Rooting/Other Guides for Nexus S (GSM)
I am not linking you to the direct directions, but I hope you will find your answer by finding a root guide from the first post.................
Sent from my Nexus S 4G using xda premium

I got the same problem after flashing the Clockworkmod 5.0. Then I flashed the 4.0x version (found in the rooting guide on XDA) and it's now working smoothly

zenithz said:
I got the same problem after flashing the Clockworkmod 5.0. Then I flashed the 4.0x version (found in the rooting guide on XDA) and it's now working smoothly
Click to expand...
Click to collapse
You should make sure you are erasing the old recovery before flashing a new one. This can be done as a fastboot command or through the advanced options in rom manager.
Sent from my Nexus S 4G using xda premium

[Q] Completely awkward behaving Nexus S

I just bought this phone yesterday and it is the i9020t (AWS version). The phone function works fine but every so often every application fails and gives an error asking to report it. I cannot manage to change the screen lock, it just comes back after reset. I only managed to remove it once. Also I cannot reset it no matter what I do, whether it is from settings or from the recovery menu. All data seems impossible to remove. How is this happening?
So Far:
-I got the boot loader unlocked (does this mean it is rooted yet?), failed to install superboot.zip
-Got the adb setup with using only part of the sdk files
(http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/)
Now I have tried this:
http://forum.xda-developers.com/showthread.php?t=884093
I can't get clockworkmod on here, I don't even know what it is exactly.
I believe I need to flash the phone onto stock firmware, the current seems corrupt as I can't do any changes such as password or wipe data.
More info on phone:
Android version: 2.3.4; Baseband version: I9020XXKD1; Kernel version: 2.6.35.7-ge382d80 [email protected]#1; Build number: GRJ22;
BTW I am on Mac OS X but can access a PC if I really have to.
Anything else I need to provide?

Doesn't sound like an odd behaving phone, just that you weren't very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium

He said weeny hah but other than that he's right
Rem3Dy said:
Doesn't sound like an odd behaving phone, just that you weeny very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms

sinik420 said:
He said weeny hah but other than that he's right
sent from my nexus s on a kang from simms
Click to expand...
Click to collapse
Owned by auto correct
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
Doesn't sound like an odd behaving phone, just that you weren't very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It was a messed up phone. Returned it. Nothing would write onto sdcard. Which explains why it would not allow many functions that require data retention.

G2X can't load custom roms, freezes at flash screen

No matter what custom rom I try to load on my G2X, it will go through, install the rom, and then when it reboots past the LG screen, it gets to whatever custom boot screen in on the rom, and just locks up. The only way I can get it to boot after that point is to NVFlash back to stock.
Tried searching through this site and google, but can't find a solution.

You need to say what the process is that you attempted to do. Wipes and what not.
Sent from my SGH-T999 using xda premium

mt3g said:
You need to say what the process is that you attempted to do. Wipes and what not.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Rooted phone, added Clockwork, booted into CW recovery, did data and cache wipes, installed CM7 from SD card, rebooted, phone froze at custom boot screen. Reboot, still frozen. Would not boot at all.
Used NVFlash to reinstall stock image on phone, rooted phone, CW recovery, data and cache wipes, installed a different rom for my phone model, same result. Back to stock using same process, tried a third rom using same process, same result, frozen phone that won't go beyond boot screen.
Using this same process on my old T-Mobile Samsung Vibrant, it worked perfectly on several different roms.

It sounds like you may have a ROM for a different model phone. Can you send a link to the ROM that you downloaded for us to see?
Also, is your phone a T-Mobile G2x or an LG Optimus 2x (O2x).

cyansky_1 said:
It sounds like you may have a ROM for a different model phone. Can you send a link to the ROM that you downloaded for us to see?
Also, is your phone a T-Mobile G2x or an LG Optimus 2x (O2x).
Click to expand...
Click to collapse
It is a T-mobile G2X, LG-P999DW.
The CM7 link was straight from the CM7 site, it wasn't an experimental mod or anything, it was the stable one listed under the G2X.
http://www.cyanogenmod.com/devices/t-mobile-g2x
ParanoidAndroid via this thread on here: http://forum.xda-developers.com/showthread.php?t=1762647
Domination via this thread: http://forum.xda-developers.com/showthread.php?t=1570017&highlight=domination

Considering cm roms are supposed to wipe system prior to flash, I couldn't imagine what is going on. Try wiping system just in case and after that, try installing from internal as well. Other options would be download other ways, like on PC or from phone transfer the files differently. Other then that can't really help you.
Sent from my SGH-T999 using xda premium

mt3g said:
Considering cm roms are supposed to wipe system prior to flash, I couldn't imagine what is going on. Try wiping system just in case and after that, try installing from internal as well. Other options would be download other ways, like on PC or from phone transfer the files differently. Other then that can't really help you.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
The last time I pulled it directly on my phone, the other times I downloaded via my PC and then copied the file. Had been via external so I tried internal that last time too. I'm close to madness, but I'm also too stubborn to give up.
I was thinking maybe I need to replace the kernel, but I'm not sure whether that's the problem or which Kernel to try if I did need to.

I had a similar issue on a tablet of mine. What version of CWM are you using? Are you using the touch version? The touch version has had some boot problems. Did you try partition the SDCard in the advanced settings? I forget which I used on my phone. Has anyone else partitioned theirs?

Well, not knowing which peice is broken let me just recap my process for you and see how it works:
1. Use OneClick NVFlash from http://forum.xda-developers.com/showthread.php?t=1056847 and select Flash CWM 5.0.2.0
2. Boot to CWM
3. format cache
4. format data
5. format system
6. format Dalvik cache
7. flash ROM from external/internal memory
8. flash kernel (optional, not required unless doing kernel testing)
9. flash gapps-package
10. fix permissions
11. reboot
I have not had this process screw up once for me so far. If this process does not work for you then you leave me really be scratching my skull...

Sooper1138 said:
Rooted phone, added Clockwork, booted into CW recovery, did data and cache wipes, installed CM7 from SD card, rebooted, phone froze at custom boot screen. Reboot, still frozen. Would not boot at all.
Used NVFlash to reinstall stock image on phone, rooted phone, CW recovery, data and cache wipes, installed a different rom for my phone model, same result. Back to stock using same process, tried a third rom using same process, same result, frozen phone that won't go beyond boot screen.
Using this same process on my old T-Mobile Samsung Vibrant, it worked perfectly on several different roms.
Click to expand...
Click to collapse
don't root and then try. mostly roms come with super user access so try without rooting it manually.
Sent from my LG-P999

cyansky_1 said:
Well, not knowing which peice is broken let me just recap my process for you and see how it works:
1. Use OneClick NVFlash from http://forum.xda-developers.com/showthread.php?t=1056847 and select Flash CWM 5.0.2.0
2. Boot to CWM
3. format cache
4. format data
5. format system
6. format Dalvik cache
7. flash ROM from external/internal memory
8. flash kernel (optional, not required unless doing kernel testing)
9. flash gapps-package
10. fix permissions
11. reboot
I have not had this process screw up once for me so far. If this process does not work for you then you leave me really be scratching my skull...
Click to expand...
Click to collapse
Using this method in exactly this order worked perfectly. Thank you very much.

Sooper1138 said:
Using this method in exactly this order worked perfectly. Thank you very much.
Click to expand...
Click to collapse
Did you notice what he didn't do.
Sent from my LG-P999

[Q] HTC One S S4, Verified everything still unable to install custom ROMS

OK so I have a One S Verified the bootloader was unlocked in bootloader, CWM is installed, verified that the device is in fact rooted using Root Checker.
When I'm in CWM and I wipe data/factory reset, wipe cache, then I wipe dalvik, then format system, data, and boot. When I try to install a ROM it says something about Symlink Error unable to do something I have no clue, anyone know what I should do......

Use TWRP 2.x - it's much better and probably won't have that error message
Sent from my HTC One S using xda premium

KACE321 said:
Use TWRP 2.x - it's much better and probably won't have that error message
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
OK I'll try that.......

ok that did the job but now it's stuck on the CM10 bootscreen and the animation is stuck on the screen, if I hold down the power button to try and reset the softkeys flash.......

fallendown said:
ok that did the job but now it's stuck on the CM10 bootscreen and the animation is stuck on the screen, if I hold down the power button to try and reset the softkeys flash.......
Click to expand...
Click to collapse
Fastboot boot.img.

Darknites said:
Fastboot boot.img.
Click to expand...
Click to collapse
Yes, with many custom roms you need to also extract the boot.img from the zip file and flash it seperately using fastboot in the bootloader.
In your command prompt you would type fastboot flash boot boot.img <--- assuming you place the boot.img in the same folder as fastboot.
You need to do this especially if you are coming from SENSE base to AOSP (ie CM10). AOSP needs a different kernel.
AKToronto

Thanks for everyone's help. This is my brother's phone, while I'm used to unlocking HTC devices with Revolutionary, this was my first attempt on a newer device.