Database Users

Stock vibrant upgrade from T959UVJ16 - ECLAIR 2.1 to T959UVKA6 FROYO 2.2

I upgraded my vibrant 959UVJ16 - ECLAIR 2.1 to T959UVKA6 FROYO 2.2.
i had a very difficult time rooting it however it is rooted now.
i installed CWM and it will not boot into CWM recovery. it does not have permission
i have tried several different ways.
i have also tried busybox 1.17.1 and it says there is no space on the location to install /system/bin or /system/xbin
i would like to flash a custom rom and i can't get it into the CWM recovery or get the BusyBox Installed.
any help would be greatly appreciated.
i think it is a permission issue. (i could be wrong) i just don't know how to fix it. i have been at it for more than 5 hours and i am giving up at this point and desperately asking for help.
From: Samsung Recovery Utils
when trying to do a reinstall packages (30X) it says
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted

Just use this for the entire process. Restore back to default and start the process over.
http://forum.xda-developers.com/showthread.php?t=954509

treleung said:
Just use this for the entire process. Restore back to default and start the process over.
http://forum.xda-developers.com/showthread.php?t=954509
Click to expand...
Click to collapse
Also, look up untermensch 3e recovery fix thread you may need to install this as well.

root:superoneclick
CWM recovery:http://forum.xda-developers.com/showthread.php?t=870480

Your issue is the stock recovery (3e).
Use the modified 3e, oka1 referenced it.
Like others said though, you could just go back to 2.1, root, flash cwr, flash custom rom.
Your choice, the stock froyo over mini kies was crap in my opinion.

treleung said:
Just use this for the entire process. Restore back to default and start the process over.
http://forum.xda-developers.com/showthread.php?t=954509
Click to expand...
Click to collapse
i did that and it did not work. I also tried the AIO toolbox with no progress.
Permissions still blocked

I was having the same issue. After rebooting about 8 times and running Superoneclick several times, it suddenly worked.
Sent from my SGH-T959 using XDA Premium App

Try using the modified 3e recovery fix like others have mentioned. It worked for me.

s15274n said:
Your issue is the stock recovery (3e).
Use the modified 3e, oka1 referenced it.
Like others said though, you could just go back to 2.1, root, flash cwr, flash custom rom.
Your choice, the stock froyo over mini kies was crap in my opinion.
Click to expand...
Click to collapse
I believe you are absolutely correct.
I also tried the AIO toolbox with no progress.
Permissions still blocked
I will revert back to stock with the modified 3e that oka1 mentioned.
thanks for pointing me in the right direction. i will give it a try and see what happens as soon as i make it home after work today.

update
tried to revert to stock and get the same error
i tried many different ones using Odin and it will not revert back.
its still on froyo.
don;t know what to do at this point. this suks
i will try again tomorrow

[Q] Anyone else use Cyanogen's Nexus One guide to run stock GRI40 with root?

Hey everyone
I have a stock unrooted Nexus One running 2.3, and finally want to root. I want to root but stay on stock 2.3, is this possible?
From what I've been reading, many suggested just using this guide, but leaving out the last step:
http://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide
So basically do everything except flashing the cyanogen update zip file.
But will following this result in having root on GRI40? Didn't see the guide mention anything about rooting.
Appreciate any advice for this root noob
Thanks!

Steps 1, 2 & 3, then flash su.zip from recovery to root your current system...
Use the Froyo version of the su.zip found at the bottom of the first post in this thread:
http://forum.xda-developers.com/showthread.php?t=682828
Sent from my Nexus One using XDA Premium App

danger-rat said:
Steps 1, 2 & 3, then flash su.zip from recovery to root your current system...
Use the Froyo version of the su.zip found at the bottom of the first post in this thread:
http://forum.xda-developers.com/showthread.php?t=682828
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Mucho thanks! I wasn't sure if I had to flash my radio, but yeah I guess that's specific for CM. Will give this a go tonight.

Hmm no luck. I loaded the
When I go to recovery and try to flash su.zip I get the message:
--Install /sdcard
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Click to expand...
Click to collapse
Another odd behaviour, after I reboot and choose "Bootloader" it takes me to the next screen (still with the 3 Androids on skateboards).
It pauses (can't select anything), then briefly displays this, before letting me proceed. This text only appears for a second, I had to use a camera to capture the text.
SD Checking...
Loading...[PASSDIAG.zip]
No image!
Loading...[PASSDIAG.nbh]
No image or wrong image!
Loading...[PASSDIMG.zip]
No image!
Loading...[PASSIMG.nbh]
No image or wrong image!
Click to expand...
Click to collapse
Then after that it takes me to the screen where I can select recovery.
Oy.. anybody have an idea what's going on?
Going to retry the steps...

danger-rat said:
Steps 1, 2 & 3, then flash su.zip from recovery to root your current system...
Use the Froyo version of the su.zip found at the bottom of the first post in this thread:
http://forum.xda-developers.com/showthread.php?t=682828
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Question.
In order to preserve my locked bootloader can I passimg back to 2.2.2 or 2.2.1 and superoneclick root and flash a stock but rooted 2.3.3 rom over it?
Or would that not work because with my locked bootloader I would be unable to flash an unsigned rom?

xanatos00 said:
Hmm no luck. I loaded the
When I go to recovery and try to flash su.zip I get the message:
Another odd behaviour, after I reboot and choose "Bootloader" it takes me to the next screen (still with the 3 Androids on skateboards).
It pauses (can't select anything), then briefly displays this, before letting me proceed. This text only appears for a second, I had to use a camera to capture the text.
Then after that it takes me to the screen where I can select recovery.
Oy.. anybody have an idea what's going on?
Going to retry the steps...
Click to expand...
Click to collapse
I'm guessing you're using Amon Ra, in which case, you need to turn off signature verification...
Everything else is normal...
Sent from my Nexus One using XDA Premium App

sarshadd said:
Question.
In order to preserve my locked bootloader can I passimg back to 2.2.2 or 2.2.1 and superoneclick root and flash a stock but rooted 2.3.3 rom over it?
Or would that not work because with my locked bootloader I would be unable to flash an unsigned rom?
Click to expand...
Click to collapse
Yes, that should work also...
Sent from my Nexus One using XDA Premium App

danger-rat said:
I'm guessing you're using Amon Ra, in which case, you need to turn off signature verification...
Everything else is normal...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Thanks Danger Rat, I got it working.
Where I had gone wrong, was after putting on the recovery image, I was booting into the default Android recovery mode, not Amon Ra's one (I had to hold down volume down on the boot).
Then I could turn off signature verification and flash the su.zip.
Rooted, thanks!
I... like... your... use... of... ellipsis...

can't install roms on droid x

Hey, I'm helping my friend install a new rom on his Droid X because the GB update messed his phone up. The Recovery version is 2.xxxx. I have Team Liquid's rom which won't install and it says
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted."
I thought maybe the download was bad so I downloaded OMGB and the same thing happens.
I can install roms without a problem on my Thunderbolt but I know nothing about this phone. It took me a bit just to figure out how to get into Recovery. No longer can I get into Recovery with Rom Manager or Quick Boot. If I tried to use those apps it just ends up rebooting the phone.
Any ideas why this is happening? Should I install the latest version of Recovery (CWM)? I downgraded the Recovery because I thought the new version was preventing Rom Manager and Quick Boot from booting into Recovery mode. Thanks in advance!!
Edit: I downloaded the Droid 2 Bootstrap app and now I managed to get into Recovery but installation failed again. It says
"Installing update..."
"assert failed: run_program("/tmp/check_kernel")"
"==0"
"E: Error in /sdcard/update.zip"
"(Status 7)"
"Installation aborted."
Any ideas?

Sbf and try from there
Sent from my DROIDX using XDA App

Sbf to. 602 and root using petes root tools, goolge will help since I can't post links
Sent from my DROIDX using XDA App

I'm a lil confused as what you mean when you say the GB update messed his phone up. If it was a OTA update that messed the phone up, then i would simply suggest getting rid of root and going back to Verizon because it could be an issue with that phone in itself.
Now if the GB update was caused by you guys trying to do certain things than follow directions of above poster StayFrosty777 (Cool name btw dude lol).
Also make sure that you download a custom rom that is on the build. I'm unsure of whether he actually has GB or if still on Froyo. If he is still on Froyo you will need to flash a Froyo rom, flashing a rom such as Liquid 3.0 which is based on GB, will not work on Froyo.

Update to ei22 from any rom with root, cwm, and modem without a pc

This will work without a pc only if you are on ec05 modem, if not get your ass there
So since I'm in the process of moving without my desktop and have no acess to a pc. I updated to gb fairly easily with cwm and root.
This can be done with any rom.
if you mess up and let it boot at the 2 points I tell you not to, then you can get stuck with stock GB without root or cwm.
You will have the modem on the bright side!
I stated off with RandomRom, but you can be on any as long as you have the ec05 modem.
1. Download what you are goingto need,(the acs cwm is your choice.) Thanks to thoes who orginaly posted these files.
1a. the stock ec05 rom with the green cwm 3.1.0.1 found here: http://forum.xda-developers.com/showthread.php?t=1027904
1b. EXTtoRFS found here: http://dl.dropbox.com/u/9992367/gotorfs.zip
1c. The ec05 to ei22 update zip found here: http://android.clients.google.com/p...a5ff039a0c97.SPH-D700_update_EC05_to_EI22.zip
1d. Su.zip found here: http://downloads.androidsu.com/superuser/su-3.0-efgh-signed.zip
1e. Acs cwm (optional) found here: http://chris41g.devphone.org/index.php?dir=Epic/ACSRecovery/
2. After the files are on your phone make sure your on ec05 modem.
3. Boot into cwm doesn't matter I believe what one you have I started with acs's cwm.
4. if you are not on Rfs flash the zip to get there.
5. wipe everything 3x.
6. Flash the stock rfs ec05 rom.
7. Once finished reboot, as soon as you select reboot use the 3 finger to get back to recovery (do not let it fully boot). You should be back to the green cwm 3.1.0.1
8. Install the ec05 to ei22 zip just like any rom, I didn't wipe **** this time.
9. When finished flash the acs cwm or any flashable version you want.
Rebot the phone in cwm while holding the 3 buttons to go back to cwm(do not let it fully boot).
10. Once in cwm either acs's or any you flashed, flash the su.zip to obtain root.
11. Reboot and let your phone power up. You should now have ei22 with modem, cwm, and root.
Hope this helps somene or makes updating easier for you!
Sent from my Rooted, ACS CWM, stock EI22 Epic using XDA App

Most clear and concise guide so far. Well done!

Thanks I live in B.F.E. Ohio and didn't want to wait to have GB with root and cwm, and without a pc I was lucky it worked!

404 error on acs cwm link
Sent from my SPH-D700 using Tapatalk

**** thanks let me find another flashable link, or if anyone can share I would be thankful.
Edit: updated the link for the acs cwm

toypaj said:
**** thanks let me find another flashable link, or if anyone can share I would be thankful.
Click to expand...
Click to collapse
http://chris41g.devphone.org/index.php?dir=Epic/ACSRecovery/

Thank you very much.
tmspyder said:
http://chris41g.devphone.org/index.php?dir=Epic/ACSRecovery/
Click to expand...
Click to collapse

perfect guide, thanks so much

Lol answered all my questions. Great guide!
Sent from my SPH-D700 using XDA Premium App

No problem just thought id share.
Sent from my SPH-D700 using XDA App

Crap... i rebooted my phone after the update and now im unrooted >_>

Yeah, I'm a retard. Rebooted without installing su. Now I have stock recovery and can't root.
Tried renaming su to update.zip but it failed.
Am I out-of-luck until I can get to a pc? Maybe I'll go home "sick"...
Sent from my SPH-D700 using Tapatalk

I would assume so. I ll update main post warning a little more about not letting it fuly reboot at the 2 points.
Sent from my SPH-D700 using XDA App

I tried gingerbreak on the nanoid version of ei22 yesterday and couldn't get it to root. Might be my phone, but that's the only other way I know to root then use cwm app to install cwm 3.1.0.1
Worth a try
Sent from my SPH-D700 using XDA App

Man, thank you soooo much for taking the time to do this write up! The instructions worked perfectly for me.

No problem
Smuuv said:
Man, thank you soooo much for taking the time to do this write up! The instructions worked perfectly for me.
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA App

toypaj said:
I tried gingerbreak on the nanoid version of ei22 yesterday and couldn't get it to root. Might be my phone, but that's the only other way I know to root then use cwm app to install cwm 3.1.0.1
Worth a try
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Gingerbreak's exploit apparently has been blocked since 2.3.3, so it isn't your phone, it's the rom. You'll have to odin cwm when you can get to your pc, then boot into recovery and flash nubernel or a comparable slightly modified custom kernel *before* normal booting for the first time - otherwise, you'll lose cwm due to a script in the stock kernel that reflashes stock recovery.
For root, I'd recommend flashing the su zip in recovery, may as well do that after flashing the custom kernel. You can find the necessary downloads in one of the how-to threads that have popped up today, I'm sure they'll be easy to find for at least a few weeks
I hope this helps clear up some confusion
Sent from my SPH-D700 using XDA App

Just realized cwm is gone after first boot, that blows
Sent from my SPH-D700 using XDA App

This worked for the ROM and root, but now all I have is stock recovery. Can someone point me in the right direction on how to get CWM back?

Ok, after a subsequent battery pull, I lost root. It was all an easy fix after doing some research. Basically, I used ODIN to flash the keyfix kernel. After a re-boot, I used ODIN to flash the ACS recovery. After booting into recovery, I flashed the su.zip. I now have root and ACS recovery. I even did a battery pull and it still works.

[Q] Booting into recovery shows "no command"

Hi there,
yesterday succesfully rooted my device using the insecure boot image.
Today booted and also flashed the new CWM recovery image but now, when booting into recovery only get an android logo and the text "no command" ?
Any ideas ? Flashed back to original recovery image but no change either ?
Root remains though and working fine.
Thanks

CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app

n7of9 said:
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Not true read here again :
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
Click to expand...
Click to collapse

has anyone reported it working?
Sent from my Nexus 7 using xda app-developers app

It seems tonight clockwork will release a new version with bugfixes which should make recovery working when flashed also.
Sent from my Nexus 4 using xda app-developers app

New clockworkmod recovery 6.0.1.8 had been released and I can confirm myself that it is working perfectly and stays when flashed !
You can download it here and follow the instructions as written here.
Good luck !

excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)

n7of9 said:
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
Click to expand...
Click to collapse
Meanwhile a newer 6.0.1.9 is released as well, which will hopefully also fix the backup being in the wrong location and not usable

CWM is fixed. Read this thread: http://forum.xda-developers.com/showthread.php?t=1995440

6.0.1.9 is the one i flashed and I'm still looking for my backup :s
n7'd from my n7

Disregard this post! It was meant for LBE which is a Virus or acts like one (Newest version that was translated)

I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?

k3nav7 said:
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
Click to expand...
Click to collapse
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD

El Daddy said:
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.

k3nav7 said:
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
Click to expand...
Click to collapse
No problem! Glad to help!
Sent from my Nexus 7 using Tapatalk HD

No Command recovery problem
Hello im using a Canvas Magnus A117 its an amazing phone i rooted it but wanted to install chainfire 3D on it but it didnt work and now my phone is bricked. I tried flashing a custom rom but in recovery when i click on apply update from sdcard it says No command. with a dead android and a red triangle with !. So i cant use any feature in the Recovery mode and my phone is bricked. What do i do?