[Q] Gingerbreak, ROM Manager, Recovery, and Cyanogen 7 - General Questions and Answers

Nexus One 2.3.3 rooting:
I used the Gingerbreak App, which has the added benefit of leaving the bootloader alone and locked. The app Root Checker confirms root access and busy box (which I installed separately), and SuperUser is installed.
I've got 2 issues:
1. Titanium Backup claims I'm not rooted. I don't know if what it checks amounts to searching for an unlocked bootloader or not.
2. ROM Manager, while working fine mostly (I was able to make a nandroid backup i think), does not reboot into Clockworkmod Recovery, either by selecting the option, or choosing a .zip file with CyanogenMod 7 (stable). I just get the Android-with-exclamation-triangle screen, and either pull the battery or try to access standard recovery mode via Vol Up + Power (hit or miss). I've tried renaming a recovery flash file to "update.zip" and manually installing it, but the process always aborts (I've tried Recovery Zero and Clockworkmod).
CWM 3.0.0.5 is what ROMM shows, but I should note it did not work downloading the first time. (I got an error that I clicked out of by mistake, and when I tried again to see it, it said it was successful, and I've heard sometimes it takes a few tries).
I've also read something (link omitted since I'm a new user):
If after the "Reboot and Install" step, you immediately get a picture of Android with a big exclamation point, most likely it means the ROM image you downloaded was not cryptographically signed by the developer (which happens if they were in a hurry to release or simply don’t use encryption).
That’s OK – you can fix this by:
-clicking the exclamation point screen, which goes to the ClockworkMod recovery menu or simply rebooting into recovery manually (that’s one of the options in the ROM Manager). Alternatively, you can boot into recovery by holding Power and Home buttons together while powering up your phone
-selecting the option that says "install zip from sdcard"
-toggling the "toggle signature verification" option to turn the verification off (it should say "Signature Check: Disabled")
-giving flashing another try by selecting "choose zip from sdcard" and selecting the right ROM, just like before
However, I can't "click" anything, and I'm unsure of what the first bullet point means. I've tried reinstalling ROMM, but CWM doesn't uninstall (I don't know how to remove it since it arrived via ROMM).
I also tried the Amon RA route, but the bootloader method fails, the ROMM method is pay only (and no guarantee at that), and the terminal method needs a root password (su), which I've not activated and know nothing about, so it can't continue.
Anyone out there know what I can try? FWIW I'm on OS X 10.6.7.

Related

[Q] Stuck in Stock Recovery

After successfully flashing ClockWork RecoveryMod, I placed SU on the root of my SNS, powered it off, went into fastboot, but when I went into Recovery, it just went to Stock Recovery, the Exclamation Mark inside the Triangle with the Android next to it appeared, but no text or anything else is on the screen. I've let it sit for about 15 minutes, and nothing. I also can't do anything by clicking the volume buttons, or the power buttons. I've also unplugged the Phone, held the power button to try to reboot it, held volume-up and power to try to go back into fastboot, but nothing. Should I pull the battery? Why didn't it go into ClockWork RecoveryMod? Command Prompt gave me the whole " sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s" thing...
What do I do? I can't just leave it sitting like this forever.
Edit: I unplugged and replugged it a few times, and it rebooted. But I've tried going back to fastboot and going into Recovery, and I get the same screen, over and over. I've even tried flashing CWRM again, and nothing. I'm using 3.0.2.4. Should I just use 3.0.0.5?
When you are in the stock recovery mode and you see the exclamation mark inside the triangle: Just hold the power button and hit volume up and you will get into stock recovery where you can perform a reboot etc.
Just try 3.0.0.5. There is something wrong with clokwork mod it you just went into stock recovery. You should be fine if you follow one of the guides on this forum.
If you still are using the stock rom. This only applies of on stock root rom because the custom rom have the edited already. You must do this. If you don't then you will have to flash clockwork ever time you reboot.
Reboot your Nexus S
Download and install Root Explorer app from Android Market
Open Root Explorer and navigate to etc directory
Tap on the gray box that says Mount R/W
Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
Once renamed, download and install the app called ROM Manager from Android Market
Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Hawky_ said:
When you are in the stock recovery mode and you see the exclamation mark inside the triangle: Just hold the power button and hit volume up and you will get into stock recovery where you can perform a reboot etc.
Just try 3.0.0.5. There is something wrong with clokwork mod it you just went into stock recovery. You should be fine if you follow one of the guides on this forum.
Click to expand...
Click to collapse
I tried it again with 3.0.2.5 from http://forum.xda-developers.com/showthread.php?t=988686. Did not work. Went again into Stock Recovery.
jerrycycle said:
If you still are using the stock rom. This only applies of on stock root rom because the custom rom have the edited already. You must do this. If you don't then you will have to flash clockwork ever time you reboot.
Reboot your Nexus S
Download and install Root Explorer app from Android Market
Open Root Explorer and navigate to etc directory
Tap on the gray box that says Mount R/W
Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
Once renamed, download and install the app called ROM Manager from Android Market
Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Click to expand...
Click to collapse
I'm a bit confused with your post.
I am still using the Stock Rom, but I don't have root access.
I've tried, after unlocking the Bootloader, going into Rom Manager and Flashing ClockWork, but it tells me first:
"You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin.su". (...)"
Then, when I still attempt to flash ClockworkMod, it tells me:
"An error occurred while attempting to run priviliged commands!"
I should have told the full story first.
I was once rooted, but it was through ROM Manager and flashing Clockwork from there. But then I had a few issues with my Wifi, and I decided to flash back Stock Rom. I still had an unlocked Bootloader though, so I thought that just redownloading Rom Manager and flashing CWRM and having Superuser installed would work. It didn't. So I attempted to root all over again, this time, manually.
But, I always go back to square one, it seems, when I try to get into Recovery.
What up with that?
After you flash CWM recovery, go straight into recovery from the fastboot menu. Do not reboot. Do not power off. Flash CWM and when it finishes immediately press volume down to select recovery and then press power to go in.
The Nexus S will overwrite CWM with stock recovery every time the phone boots by default. This could be what is giving you trouble.
Sent from my Nexus S using XDA App
matt2053 said:
After you flash CWM recovery, go straight into recovery from the fastboot menu. Do not reboot. Do not power off. Flash CWM and when it finishes immediately press volume down to select recovery and then press power to go in.
The Nexus S will overwrite CWM with stock recovery every time the phone boots by default. This could be what is giving you trouble.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
EonHawk said:
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
Click to expand...
Click to collapse
No problem.
There is a script located in the /etc folder called install-recovery.sh. it runs every time you boot and installs stock recovery. You have two choices: always use rom manager to flash CWM every time you need to access recovery, or use root explorer to rename install-recovery.sh to install-recovery.sh.bak so that it will not run and will leave CWM installed.
Glad you got it figured out!
Sent from my Nexus S using XDA App
Or a third choice of course would be to install a custom ROM because they tend to not include that script
Sent from my Nexus S using XDA App
EonHawk said:
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
Click to expand...
Click to collapse
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
buachaille said:
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Actually I think that guide does have two unnecessary steps that cause confusion. After flashing CWM, the guide instructs the user to power off, power on, and then to access recovery. The user should just access recovery immediately after flashing.
EDIT: I guess the problem is just that the bolded part should be added:
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS while holding volume up
buachaille said:
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
That's partly my fault, I never went down to the 2nd Post and saw those Notes, but what's the point of not including that already in the steps in the main Post? He could have just told to go straight from Recovery after flashing CWRM, but decided not to.
matt2053 said:
Actually I think that guide does have two unnecessary steps that cause confusion. After flashing CWM, the guide instructs the user to power off, power on, and then to access recovery. The user should just access recovery immediately after flashing.
EDIT: I guess the problem is just that the bolded part should be added:
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS while holding volume up
Click to expand...
Click to collapse
I think he should just have instructed to place the SU zip on the root of the SD card before flashing CWRM. That way, there wouldn't be a need to reboot to mount the SD to place SU, that way potentially losing the CWRM.

[Q] failbooted recovery from CWM ROM Manager stuck

Dear people of awesomeness,
The story: I was following the exciting thread about the new CWM support for SGS4G by krylon360 and team, followed the directions (overwriting the recovery file WITH R/W enabled, placing update.zip into the root of my SD card...), and got stuck. Didn't know what to do exactly after that, other than try to use ROM Manager to backup my phone. Saw the "Reboot into recovery" option in the ROM manager menu and thought hey, let's see what this does. Most careless, stupidest thing I've done this year. fail.
The question: What is/are the way/s to boot into stock recovery mode? I can't seem to find a definitive method for booting into "stock recovery mode", though I've found plenty of ways to boot into download mode (a whole thread of them lol). I managed to find ONE method after reading through hundreds (honest) of posts in dozens of threads here and elsewhere: Hold vol+ Vol- and Power simultaneously from a powered off state.
The secondary fail: Obviously this didn't work for me, and although I'm near certain I'm going to have to do the "Odin" thing, I just wanted to ask if anyone could clearly explain the method to boot into stock recovery?
The shameless 2nd question: This question may have been asked elsewhere, shame on me, but... the .tar I'm downloading ([ROM-ODIN]T959VUVKB5 Stock + Root -- (hxxp://forum.xda-developers.com/showthread.php?t=978836)) will it wipe my phone?
akira6968 said:
Dear people of awesomeness,
The story: I was following the exciting thread about the new CWM support for SGS4G by krylon360 and team, followed the directions (overwriting the recovery file WITH R/W enabled, placing update.zip into the root of my SD card...), and got stuck. Didn't know what to do exactly after that, other than try to use ROM Manager to backup my phone. Saw the "Reboot into recovery" option in the ROM manager menu and thought hey, let's see what this does. Most careless, stupidest thing I've done this year. fail.
The question: What is/are the way/s to boot into stock recovery mode? I can't seem to find a definitive method for booting into "stock recovery mode", though I've found plenty of ways to boot into download mode (a whole thread of them lol). I managed to find ONE method after reading through hundreds (honest) of posts in dozens of threads here and elsewhere: Hold vol+ Vol- and Power simultaneously from a powered off state.
The secondary fail: Obviously this didn't work for me, and although I'm near certain I'm going to have to do the "Odin" thing, I just wanted to ask if anyone could clearly explain the method to boot into stock recovery?
The shameless 2nd question: This question may have been asked elsewhere, shame on me, but... the .tar I'm downloading ([ROM-ODIN]T959VUVKB5 Stock + Root -- (hxxp://forum.xda-developers.com/showthread.php?t=978836)) will it wipe my phone?
Click to expand...
Click to collapse
does your phone still boot up normally?
also when you get to the recovery menu it should be blue. scroll down to reinstall packages, and that will get you to CWM recovery
Ok first, Rom Manager should not be used until Koush incorporates our device in it.
Your findings are correct, the vol+,vol-, + the power button should get you into recovery, besides that the only other way is to use an app/power menu mod but that requires the phone to be on.
It sounds like the next thing for you is Odin. From your phones current state you can, hold vol+, vol- and then plug USB Cable into phone (Brings you into download mode), ive read some users pull battery and put it back in, but the first way i explained it should get you into download mode. From there, choose Roms KB5, KC1, or KD1, and yes your device will be factory reset. Your documents should be on your SD. I dont know if you have Titanium Backup to restore your apps, if not, you will have to manually install them after your odin session.
hope this helps
E:signature verification failed
chris.... said:
also when you get to the recovery menu it should be blue. scroll down to reinstall packages, and that will get you to CWM recovery
Click to expand...
Click to collapse
When I boot into recovery mode and select reinstall packages it starts out:
install from SD card
Finding update package
Opening update package
verifying update package...
E:signature verification failed
installation aborted
I have downloaded krylon360's cwm final update.zip and put it in my root directory.
The only posibility I can think of was a friend rooted my phone with an older update.zip file and i am trying to put the new one on. I deleted the old update.zip and copied over the new one.
i then downloaded odin and followed the instructions on a post to flash my rom with the t959+root from krylon360 as well. I believe that worked, because a lot of the apps that came with the phone are back now.
i tried reinstalling packages after this and still the verification error.
i have been doing a lot of browsing, searching and reading tons of posts on here... cant seem to figure this one out. any ideas?
Thanks
If you successfully flashed your phone and have root access, double check the update.zip is in the root and make sure its the latest one. Another thing is to make sure you copied over the Recovery file and pushed (Copied) it over to System/bin folder. Once you have those two in place you can reboot into stock recovery then "re-install packages" to get to CWM Recovery.
Hooray!
I did the ODIN thing, according to the post mentioned in my OP, and it fixed everything My custom shutdown vid, startup/shutdown sounds were gone, but my apps were still there, even paid apps. No titanium backup.... guess I got lucky lol. Scared the crap outta me when it wouldn't load past the T-Mobile startup image.
I knew not to use CWM yet, was following the thread about imminent implementation of sgs4g support for CWM, but just didn't really think that booting into recovery mode from CWM would get me stuck like that. Didn't even try to install recovery for CWM, knowing that "Epic 4G" and "Vibrant", etc were not the right choice despite the seeming similarities.
I had been keeping up with moving all apps i could to SD, so maybe that saved me, I dunno.
Followed pixelbrains post to use odin and worked perfect. Thank you all!!
glad you got your phone back. \m/
fknfocused said:
If you successfully flashed your phone and have root access, double check the update.zip is in the root and make sure its the latest one. Another thing is to make sure you copied over the Recovery file and pushed (Copied) it over to System/bin folder. Once you have those two in place you can reboot into stock recovery then "re-install packages" to get to CWM Recovery.
Click to expand...
Click to collapse
Thank you for that info.... I actually finally figured it out, but it took me forever. the key kind of is what i thought, that i did not have the recovery file in the right spot. I finally found a free file manager, super manager (recommonded on one of theses posts, i read so many cant remember which one ) after fiddiling with that for like 30-40 mins i finally figured the correct procedure to allow me to paste that recovery file and once i did that, bam, cwm recovery worked fine.
so, the fact that i am able to get to that screen and the latest update.zip file is in my external sd cards root dir. i am all goo there right?
i also used odin to flash "PDA_KD1.tar.md5" my phone after i got that recovery file in the correct place, and then when that was done i booted into the cwm recovery after i downloaded "Bali_SGS4G_v1.4UV.zip" and then i hit install zip from SD card, and i selected choose zip file and selected that bali one, and then i had to scroll down like 7 spots to hit yes to install and it went for a few seconds and then acted like it was done, so i just hit back and then reboot. how do i know if that worked? cuz i dont see anything saying bali at all on my phone...
does it sound like i did that right?
thanks again
edge228 said:
Thank you for that info.... I actually finally figured it out, but it took me forever. the key kind of is what i thought, that i did not have the recovery file in the right spot. I finally found a free file manager, super manager (recommonded on one of theses posts, i read so many cant remember which one ) after fiddiling with that for like 30-40 mins i finally figured the correct procedure to allow me to paste that recovery file and once i did that, bam, cwm recovery worked fine.
so, the fact that i am able to get to that screen and the latest update.zip file is in my external sd cards root dir. i am all goo there right?
i also used odin to flash "PDA_KD1.tar.md5" my phone after i got that recovery file in the correct place, and then when that was done i booted into the cwm recovery after i downloaded "Bali_SGS4G_v1.4UV.zip" and then i hit install zip from SD card, and i selected choose zip file and selected that bali one, and then i had to scroll down like 7 spots to hit yes to install and it went for a few seconds and then acted like it was done, so i just hit back and then reboot. how do i know if that worked? cuz i dont see anything saying bali at all on my phone...
does it sound like i did that right?
thanks again
Click to expand...
Click to collapse
settings menu then go to about phone and check the kernel
Sent from my SGH-T959V using XDA Premium App
thank you, it shows the bali as kernel... so glad to see i did it correctly

[Q] Help, please. Stuck mid-root!

I was following the directions seen here for rooting from stock EE4.
CWM install via Odin seemed to work fine but when I booted into recovery mode, I did not see the option "install zip from sdcard" (from which point I would have navigated to my kernel.zip file). Instead, I selected "update from.sdcard.zip" or something to that effect. The result is an exclamation point in a triangle and zero responsiveness.
What now? Thanks.
Can you reboot into recovery? If yes, then select update from sdcard this time and you should be good to go.
If no, the do an ODIN flash of CWM again, then select update from sdcard this time and you should be good to go.
Yes, elucid, I did get booted into recovery. I have the same options as before including the one you suggest I execute (and which froze me last time) "apply sdcard:update.zip."
Is the absence of ""install zip from sdcard"" from the menu evidence that I somehow screwed up the CWM installation?
It sounds like you may have the stock recovery instead of CWM. The second option should be:
Apply update from sdcard
It should also say ClockworkMod Recovery (not Samsung Recovery). What color is the screen in recovery?
Try using ODIN to flash CWM again.
Uncheck auto-reboot when flashing CWM and boot direct to recovery when it is finished and flash the rooted kernel. Booting the phone w/ the stock kernel overwrites the recovery you just flashed.
Yep, I'm in (blue) Samsung recovery. I had reboot unchecked but may have mindlessly rebooted normally post-Odin.
1. Make sure you have the latest ZIP file for CWM on your SD Card.
2. Make sure you have the zip for the kernel you want on your SD Card.
Then try the following...
What I would try is to download the third package from this post.
1. Use Odin to flash this package.
2. Disconnect the phone from the computer, put in the battery and try to boot up. It will usually boot into recovery after an Odin flash. No worries if it does or does not. This particular package will probably have yellow text when in CWM.
3. Either let the phone boot normally if it does it, or select reboot now from CWM.
4. Once the phone boots up (confirming that it works, in other words, not soft bricked) shut it down.
5. Reboot into recovery (3 button combo).
6. Install the updated CWM from the SD Card.
7. Reboot the phone back into recovery.
8. Install the new kernel you want.
9. Reboot the phone to the OS and make sure the Superuser App works.
10. Reboot into recovery and install whatever ROM you want.
And now you should be golden.
The instructions that you linked to in your OP are good. I read through them and its a solid guide.

[Q] OTA 2.3.7 update lost SU permissions

Nexus S 4g
I did the one click root month or 2 ago and gained unlock and SU permissions. My phone updated to 2.3.7, last week. I decided to load CWM today and discovered I no longer had permissions. I've tried several things and am stuck.
Nothing in ROM manager will work properly. I get message: "error occured while attempting to run priviledged commands" for fix permissions, or load other CWMR (that worked in the past I had to put an earlier one in to be able to access recovery in bootloader). If I try to backup, apply .zip, etc it just never reboots.
If I go to bootloader and go into recovery, each time it shows unlock, then the triangle with an exclamation point (so I can't backup, restore previous backup, anything)
I managed to grab SU 3.0 and force it to install over my existing 2.3.6, it did, sees my su (which is in system/bin which I've read is a problem ) as being outdated and wants to update it, fails each time.
So someone smarter than me please advise. My phone is functioning nicely without FCs or other issues, a normal boot or reboot goes fine, but I fear for the day I really need my backup. Not to mention frustrating that I seem to be locked out from making any changes now.
Thanks, Travis
sobamaflyer said:
Nexus S 4g
I did the one click root month or 2 ago and gained unlock and SU permissions. My phone updated to 2.3.7, last week. I decided to load CWM today and discovered I no longer had permissions. I've tried several things and am stuck.
Nothing in ROM manager will work properly. I get message: "error occured while attempting to run priviledged commands" for fix permissions, or load other CWMR (that worked in the past I had to put an earlier one in to be able to access recovery in bootloader). If I try to backup, apply .zip, etc it just never reboots.
If I go to bootloader and go into recovery, each time it shows unlock, then the triangle with an exclamation point (so I can't backup, restore previous backup, anything)
I managed to grab SU 3.0 and force it to install over my existing 2.3.6, it did, sees my su (which is in system/bin which I've read is a problem ) as being outdated and wants to update it, fails each time.
So someone smarter than me please advise. My phone is functioning nicely without FCs or other issues, a normal boot or reboot goes fine, but I fear for the day I really need my backup. Not to mention frustrating that I seem to be locked out from making any changes now.
Thanks, Travis
Click to expand...
Click to collapse
You're "locked out" because you don't actually have root access. The OTA update chmods /system recursively (and as a result /system/bin and /system/xbin).
The triangle with the exclamation mark is the stock recovery (applied with the OTA update).
I'm not entirely sure what you've tried as it's a very easy process.
-Download CWM for your device - flash it using fastboot.
-Boot into recovery and flash the su binary via recovery. This will place the binary appropriately as well as chmod it.
-Done
-Profit?
krohnjw said:
You're "locked out" because you don't actually have root access. The OTA update chmods /system recursively (and as a result /system/bin and /system/xbin).
The triangle with the exclamation mark is the stock recovery (applied with the OTA update).
I'm not entirely sure what you've tried as it's a very easy process.
-Download CWM for your device - flash it using fastboot.
-Boot into recovery and flash the su binary via recovery. This will place the binary appropriately as well as chmod it.
-Done
-Profit?
Click to expand...
Click to collapse
Oddly I was getting the triangle intermittently from the get go, but I had been able to get around it by applying an earlier clockworkmod version in Rom Manager. I'm not able to do that now.
My whole problem is I'm unable to do anything at all in Fastboot. If I go to "recovery" to try and apply anything I get the triangle.
Am I missing something?
It does say "Lock State - Unlocked" in fastboot if that means anything.
sobamaflyer said:
Oddly I was getting the triangle intermittently from the get go, but I had been able to get around it by applying an earlier clockworkmod version in Rom Manager. I'm not able to do that now.
My whole problem is I'm unable to do anything at all in Fastboot. If I go to "recovery" to try and apply anything I get the triangle.
Am I missing something?
It does say "Lock State - Unlocked" in fastboot if that means anything.
Click to expand...
Click to collapse
Yeah, you have the stock recovery. You can't apply a new recovery through rom manager because the su binary doesn't have the appropriate permissions since the update.
Boot into the boot loader (Vol up and pwr). Don't go into recovery. Use fastboot from the boot loader to load CWM. Boot into CWM after flashed and flash the SU binary (mount /system first). After this boot up and delete/rename /etc/install-recovery.sh so that it won't overwrite CWM on each reboot. Install CWM again from Rom Manager or via fastboot (as it was overwritten on boot). Done.
Since you are being nice enough to try and help an id10t (apparently) and others may have the same issue and search this I'll ask the dumb questions. (I did a bit of googling a min. ago and found others with the same things I see but didn't get any further...).
When you say "go into Fastboot" you mean opening SDK Manager on my PC while I'm in the Boot Loader Screen?
At the bottom of the screen I see:
USB Control Init
USB Control Init End
[plug in usb get:]
STANDARD_SET_CONFIGURATION
Nothing shows up in SDK, I have the black CMD screen up but can't type anything at all in it?
......I did try loading pda_net (not sure what to do with that? but it was mentioned elsewhere) and I get a grey message at the bottom of the screen that says "FASTBOOT STATUS - FAILinvalid Command"
sobamaflyer said:
Since you are being nice enough to try and help an id10t (apparently) and others may have the same issue and search this I'll ask the dumb questions. (I did a bit of googling a min. ago and found others with the same things I see but didn't get any further...).
When you say "go into Fastboot" you mean opening SDK Manager on my PC while I'm in the Boot Loader Screen?
At the bottom of the screen I see:
USB Control Init
USB Control Init End
[plug in usb get:]
STANDARD_SET_CONFIGURATION
Nothing shows up in SDK, I have the black CMD screen up but can't type anything at all in it?
......I did try loading pda_net (not sure what to do with that? but it was mentioned elsewhere) and I get a grey message at the bottom of the screen that says "FASTBOOT STATUS - FAILinvalid Command"
Click to expand...
Click to collapse
Fastboot is merely a command line tool used for various operations on the device. Mainly though you'll use it to flash an image to a specific partition.
You'll need to boot the device into the boot loader (hold Vol up and power on).
Plug the device in via USB.
Open a command windows in the tools or platform-tools folder of the SDK (depending on your version of the SDK, where the fastboot.exe can be found) and issue the fasboot devices commmand. This should display the serial of any connected devices. If this comes back blank there is an issue with the installed driver. Reinstall the USB driver for the device using the supplied driver from an updated SDK.
Assuming fastboot devices shows one device you now can flash a recovery to the device. Download the appropriate recovery for your device (i9020(a), i9203 or NS 4G) http://mirror.sea.tdrevolution.net/cm/recoveries/. Place this file in the same directory for simplicity.
At this point you can flash your recovery.
fastboot flash recovery file.name.you.downloaded.img
If it is not in the same directory you can alternatively pass the full path to the image.
You now have a custom recovery installed. Select Recovery from the bootloader menu to now boot into this recovery.
Assuming you've already downloaded the su binary and it is on your SD card, mount /system from within CWM and then chose to install zip and select this from the SD card. You now have root access.
Now that a panic attack is settling...
I think I'm getting somewhere but not yet where I want to be. I go to Bootloader, I connect my USB and don't get anything different than above from my sdk tools menu (unusable cmd screen, fail showing on my phone). What does [eventually] work is going back to my "nexus S one click root" folder and clicking run.bat (as fastboot.exe and adb.exe in that folder also do the nothing).
This run.bat reads some sort of fail and boots my phone telling me that debugging is not checked (which it is) and takes me directly to there, then the cmd screen tells me to press enter when I've turned on the [already checked] usb debugging toggle.....what the hell I press enter. Now it goes into the old beautiful CWMR (3.0.xxxx) screen where I'm able to apply .zips, backup etc.
(luckily I think ahead and do a backup right this min.)
Then I go from that screen and decide to apply my new CM7.zip that started all this, I apply that and get a bootloop on the CM7 boot screen.......crap......I go clear my davlik and cache and install CM7 again. Same thing.....crap......
I try restoring my original backup from 9/5/11 I made right after first unlocking my phone.......CM7 bootloop screen.....dammmmiiiiit
I try restoring backup from 9/12 I made after getting everything just like I wanted it.......CM7 bootloop screen.......uh oh, panic beginning.
I restore the backup from a few lines ago, my phone comes back (thank god)
So:
-I have to have the right USB driver in my laptop because something from sdk ultimately talked to my phone?!
-Clockworkmod recovery 5.xxxx has never worked quite right for me, apparently 3.xxxx is still my magic answer?!
-Now that I've gotten this far should I try the same process to get back to my CWMR 3.xxxx screen and put some different files in my root to use than what I've done to this point?
....again, I apologize if I'm being myopic or asking dumb questions. I often say I only know just enough to be dangerous.
[SOLVED] - maybe/sort of
Between reading (and re-reading) the help above and continued research on my own I [think] I solved my problem.
I found the following 2 links:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
And basically started over from scratch, I deleted what I'd put in my pc and re-loaded using those instructions (in the right place, the right way). Doing this I was able to pull up a cmd window and this time it properly accessed my phone. I got it to fastboot recovery - load CWM 5.0... and from there got into my recovery menus on my phone this time.
One curious thing....I tried the part VI in "how to root the samsung" ...""stop the phone uninstalling the custom recovery image"...... I've tried several things there but still get an error that it is read only.
....I went on to install CM7, and it consequently updated right after to the latest CM7, At this moment I have full permissions, superuser access, was able to make a backup of yesterday, the CM7 this morning and then CM7.1.0.1 that loaded.
Will I ultimately have the same issue as before? But be able to overcome it in the same manner when I want to?
Thanks for the help
This is why one click methods are bad. When a problem arises you have no clue what to do because a software did it for you the first time. Glad you got it figured out.
Sent from my Nexus S 4G using xda premium

[Q] Photon Q can't get root

hi guys, my photon q (unlocked bootloader) running on Jelly Bean can't root. I follow step by step from this . When I flash CWMrecovery I get "variable not supported" in the middle on my screen and then every into recovery there's triangle red (above android logo). I also can't find back-up and restore option in my recovery. And when I tried flash SuperSU via recovery I got this:
-- Install /sdcard/Root...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
So I used another method, I used motofail2go to get root. but the problem goes to this: Always exploit failed, already factory reset (wipe data/cache) and push volume up + button power but nothing (exploid failed again)
Any ideas guys?
First, if your bootloader is unlocked you do NOT need to do motofail2go or any of that other nonsense.
Second, I recommend you try searching before posting.
If you search for "variable not supported" there is a treasure trove of information.
Take this thread for example. Seems stock recovery is playing tricks on you, unfortunately. It is curable tho.
Edit - this guy solved it by using TWRP...
I wonder if there's some file that just needs to be removed before flashing recovery? I'm not sure, but give TWRP a shot. It will root the device for you as well
Yeah I got rooted, I suggest to prefer TWRP than CWM. big thanks guys
How to install TWRP with JB OTA running
Here is a step-by-step for anyone who stumbles here looking for an answer. I had to remember how I forced it through the first time, so I could install TWRP on my second PQ. GOO manager doesn't install TWRP, despite offering to. I believe this is due to JB.
1. Download TWRP recovery file & save to "platform-tools" folder
2. Start command prompt in platform-tools folder
3. ~type "adb reboot-bootloader" (phone will boot into bootloader)
4. ~type "fastboot flash recovery openrecovery-twrp-2.5.0.0-asanti_c.img" (when that is the name of the TWRP recovery file in platform tools)
5. unplug USB, push power button - phone will turn off
6. Hold "vol-up" button in and press power button, release "vol-up" when screen turns on, phone will boot TWRP.
7. NAND backup, Flash rom or other.
Do it in this exact order & it will work. (should)
Enjoy *****es!

Categories

Resources