Database Users

FRF91 Stock for custom recovery with optional root - From lox at htcpedia

http://htcpedia.com/forum/showthread.php?t=3033
Thank you lox, you truely are an Android ninja...

man you guys work fast..

And it works too. (Like there was any doubt...)

b0dge said:
And it works too. (Like there was any doubt...)
Click to expand...
Click to collapse
Hiya mate, im on build FRF83 at the moment, can i upgrade straight to this build using this link?
Also, whats the order i flash stuff, that link confused me abit.
Im rooted and running a custom recovery, (RA 1.6.2)
Cheers!

jimbob_me said:
Hiya mate, im on build FRF83 at the moment, can i upgrade straight to this build using this link?
Also, whats the order i flash stuff, that link confused me abit.
Im rooted and running a custom recovery, (RA 1.6.2)
Cheers!
Click to expand...
Click to collapse
Yep, just put them both on /sdcard/ and flash away.
It tells you at the end of the post what order to do them in:
The three updates can be flashed at the same time (I mean without rebooting between the flashes), just flash it in this order: base system, root then addons and reboot
Click to expand...
Click to collapse

WTF? What's the diff? Anyone know?

I have uploaded all three files in one zip file : http://rapidshare.com/files/404395384/Froyo_FRF91.zip.html
I enabled trafficshare for everyone, finally I could give something back to the community!

b0dge said:
Yep, just put them both on /sdcard/ and flash away.
It tells you at the end of the post what order to do them in:
Click to expand...
Click to collapse
Just tried this, installation started and then stalled half way through. A few seconds later is aborted. Heres what it said:
E: No space left on device
E: Error writing BOOT
E: Failure at line 72
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted
Is this simply a case of me needing to free up space on my phones memory?
Any help would be wicked.
Jim

I receive the exact same error unfortunately... I've tried going from tock FRF50 as well as Cyanogen 5.0.8 with no avail.
Decided to try fastboot to run "fastboot erase boot" and see if I could get any luck there, but I was met with another problem:
"erasing 'boot'... FAILED (remote: not allowed)"

May I ask what is the function of replacing the boot.img in the root update.zip? Aren't su and Superuser.apk sufficient for root?

I was on FRF85B, invisible root!
I applied the three files in the order suggested, boom it works like a charm.
I see no visible changes, but Froyo rocks!

cmstlist said:
May I ask what is the function of replacing the boot.img in the root update.zip? Aren't su and Superuser.apk sufficient for root?
Click to expand...
Click to collapse
I see recovery-from-boot.p and install-recovery.sh in there, I'm worried about replacing those files with my bootloader still locked.
Can I just manually delete those files from the zip and then install?
kkiran said:
I was on FRF85B, invisible root!
I applied the three files in the order suggested, boom it works like a charm.
I see no visible changes, but Froyo rocks!
Click to expand...
Click to collapse
Can you still see your phone with adb while it's in recovery?

This does not work, it says signature aborted.

kkiran said:
I have uploaded all three files in one zip file : http://rapidshare.com/files/404395384/Froyo_FRF91.zip.html
I enabled trafficshare for everyone, finally I could give something back to the community!
Click to expand...
Click to collapse
Dude, you are awesome!!! I just installed all three updates and all worked perfectly . Again Thanks for the hard work!!!

kkiran said:
I have uploaded all three files in one zip file : http://rapidshare.com/files/404395384/Froyo_FRF91.zip.html
I enabled trafficshare for everyone, finally I could give something back to the community!
Click to expand...
Click to collapse
tks, try it now
edit: works fine.

Thanks!!!! Updated straight away....wouldn't know what to do updating wise without your versions of the Roms!!

I have been having the same problem when installations are flashing boot.img for awhile now. That said, the installation gave me the same error, I flashed the other two files, and it appears to be working okay. The only thing I can't do is use ADB, which isn't as much of a big deal for me.
What I LOVE about this flash is that it's using the Cyanogen kernel which has the audio values tweaked for louder earpiece volume, something that was a huge problem with Froyo. I'm much happier with this fixed now.

Am I understanding this correctly,
I'm running stock unrooted FRF91,
If I flash the second update.zip file I will be rooted and then flash the third update.zip file I will be rocking the cyanogenmod 6.0 kernel?
Eager to try, but a bit apprehensive.

tibere86 said:
Am I understanding this correctly,
I'm running stock unrooted FRF91,
If I flash the second update.zip file I will be rooted and then flash the third update.zip file I will be rocking the cyanogenmod 6.0 kernel?
Eager to try, but a bit apprehensive.
Click to expand...
Click to collapse
Yes, provided you're flashing with a 3rd party recovery like Amon_Ra's or similar.

jimbob_me said:
Just tried this, installation started and then stalled half way through. A few seconds later is aborted. Heres what it said:
E: No space left on device
E: Error writing BOOT
E: Failure at line 72
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted
Is this simply a case of me needing to free up space on my phones memory?
Any help would be wicked.
Jim
Click to expand...
Click to collapse
I get this same error, anyone find a fix?

Noob trying to learn how to flash roms

Ok guys, not sure if this should be in General or in here...
I am very new to Android but I'm loving it so far. I have my Epic rooted and I have the clockworkmod installed. I have download Tha Boss Rom V.02 to try out as my first ROM.
I just a few questions?
I have the ROM on my sd card and I renamed to update.zip(not sure if I needed to do that)... I then open up clockwork and hit update ROM from SD Card, point it at the update.zip.
It reboot and goes into the Android system recovery screen and starts to install the package. It gets to Verifying update package and stops and say:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
What am I doing wrong. Do I just have a bad file and maybe redownload it? I think I may try Andromeda Galaxy v1.0.3 next just to see if it's a file issue...
Thanks if you took the time to read this.
Solstone

Boot ypur phnoe into clockwork recovery (vol. down + camera + power) then select "install zip from SDcard". then "choose zip from SDcard" then select the update.zip file.

solstone said:
Ok guys, not sure if this should be in General or in here...
I am very new to Android but I'm loving it so far. I have my Epic rooted and I have the clockworkmod installed. I have download Tha Boss Rom V.02 to try out as my first ROM.
I just a few questions?
I have the ROM on my sd card and I renamed to update.zip(not sure if I needed to do that)... I then open up clockwork and hit update ROM from SD Card, point it at the update.zip.
It reboot and goes into the Android system recovery screen and starts to install the package. It gets to Verifying update package and stops and say:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
What am I doing wrong. Do I just have a bad file and maybe redownload it? I think I may try Andromeda Galaxy v1.0.3 next just to see if it's a file issue...
Thanks if you took the time to read this.
Solstone
Click to expand...
Click to collapse
This should be in the general forum- but are you sure you are getting the clockwork recovery- the screen should be green not blue- you can pm me for step by step help

jimmyz said:
This should be in the general forum- but are you sure you are getting the clockwork recovery- the screen should be green not blue- you can pm me for step by step help
Click to expand...
Click to collapse
ah the screen is blue... so maybe my clockworkmod is not working... i'll PM you... thx

please post everything you learned i cant boot to clockwork either.

I was able to get into the loading screen but I am getting the same error that it cant be verified

Did you use the voodoo touch wiz file?

Himmad said:
Did you use the voodoo touch wiz file?
Click to expand...
Click to collapse
i did use the vodoo touch... maybe i'll try the non touch one.

it seems like you guys dont have clockmod installed correctly. are you guys doing the one click method for root and clockmod? do any rooted apps work? dl rom manager from the market. use that to install the newest clockmod recovery. make sure you selet the samsung epic. use rom manger to boot into recovery? it should be green not blue

I was having a similar problem booting to cwm from rom manager. Rooted with one click 2.2.4 then one click clockwork final then installed rom manager. RM would not boot into cwm. Dled and flashed cwm from inside RM and still didn't work. I could get to it via the 3 button method. Next I flashed Mixup kernel and still had the same issue. Went back into RM and clicked DL Clockwork again and it instantly says its successful and now I can boot into cwm from RM.

Could somebody please make (or HAS somebody made) a guide that addresses the following two scenarios? I think it would go a LONG way towards encouraging others to experiment with the ROMs that are available now
1. My phone's rooted. I want to experiment and try out the available ROMs... but first, I want my phone backed up verbatim, so I can put everything back the way it was if things don't work out. What do I need to do?
2. I had fun trying out other ROMs, but for now I just want to put everything back the way it was before I started. I followed the instructions for #1. What do I need to do NOW?

Ok all this what I found was my problem. I believe it was Windows 7 64 bit. I tried to get clockworkmod running on my work machine that is windows 7 32bit and it worked like a champ. I actually decided to start from scratch and unrooted my phone, reapplied the DI07 update then rooted again, did the clockworkmod first try... then I did the last try.bat and rebooted and that seemed to work. I am doing a ROM back as I type this.
There is a good thread on it in the Epic Android Development forum called:
[TUTORIAL] Updating to DI07, Obtaining Root, and Flashing Custom Recovery [FIX]
I'd post a link, but I am a new user... and so no links in post
Hope this helps everyone.

Can someone post a link? I did use search, turned up a million (yes, I am exaggerating) threads but can't find this one.
Thanks.

nmoreman said:
Can someone post a link? I did use search, turned up a million (yes, I am exaggerating) threads but can't find this one.
Thanks.
Click to expand...
Click to collapse
Try this
should be it.

[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...

Little bit confused

I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?

dccxviii said:
I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?
Click to expand...
Click to collapse
You cannot get root back without a custom recovery. OTA will not relock the bootloader, you'll just lose root and custom recovery.
You need to flash custom recovery using fastboot, then flash superuser to get root back. There are plenty of guides in the stickies describing the process.

Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused

The superuser app checks to see if you have the latest superuser binary and will download and instalk it. Or download superuser from within rom manager.
Sent from my Nexus S 4G using xda premium

Ok..the binary update fails (because i don't have root) so it's chicken and egg as far as I can tell.

You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.

dccxviii said:
Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused
Click to expand...
Click to collapse
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.

albundy2010 said:
You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.
Click to expand...
Click to collapse
You've misunderstood what i'm after. Thanks for trying to help tho
irishrally said:
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.
Click to expand...
Click to collapse
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<

dccxviii said:
You've misunderstood what i'm after. Thanks for trying to help tho
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<
Click to expand...
Click to collapse
Turn off signature verification in CWM and try again.

irishrally said:
Turn off signature verification in CWM and try again.
Click to expand...
Click to collapse
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*

dccxviii said:
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*
Click to expand...
Click to collapse
You're welcome.
If you stick with a stock ROM then recovery will reflash every time you reboot. To prevent this you can go to system>etc, and change the file install-recovery.init to something else like install-recovery.init.bak.

[Q] trying to upgrade to 4.1.2 - failed to verify whole-file signature

Running 4.1.1 at the moment and rooted / unlocked using a toolkit.
Trying to update to 4.2.2 ota but when the nexus reboots I get that error.
What do I do?

Foxman2k said:
Running 4.1.1 at the moment and rooted / unlocked using a toolkit.
Trying to update to 4.2.2 ota but when the nexus reboots I get that error.
What do I do?
Click to expand...
Click to collapse
See thread:
http://forum.xda-developers.com/showthread.php?t=1764794
seems to be due to custom kernel

flyi said:
I think I have the same problem, mine says "Verifying current system..." then says "assert failed: apply_patch_check ..."
I'm currently running 4.1.1 stock rom rooted and custom kernel.
Also, I think you mean 'trying to update to 4.1.2 ota'.
Click to expand...
Click to collapse
Flash the stock kernel. You can do it a number of ways. You can find a cwm zip file with it, use the toolkit to do it, or get the IMG yourself and flash it via fast boot. I had this error earlier.

Install a custom recovery and use it to run the update. If you already have a custom recovery, then that's why you can't run the ota via google possibly.

flyi said:
See thread:
http://forum.xda-developers.com/showthread.php?t=1764794
seems to be due to custom kernel
Click to expand...
Click to collapse
But I don't have a custom kernel. Just rooted and unlocked.

mustbepbs said:
Flash the stock kernel. You can do it a number of ways. You can find a cwm zip file with it, use the toolkit to do it, or get the IMG yourself and flash it via fast boot. I had this error earlier.
Click to expand...
Click to collapse
Any guides on this? Pretty new to android.

Anyone have any thoughts on what I should do?

Did you touch any of your system apps?
Seems more likely your update didn't download fully and it failed and md5 checksum. Just try again next time.

I don't think I touched any of the system apps. I did download Adblock and six axis tool. Anything else to look for?

I've downloaded the update probably 4 different times now and same thing each time.

Anything else I can try?

Foxman2k said:
Anything else I can try?
Click to expand...
Click to collapse
Any other options besides resetting? has no one else who only rooted and unlocked run into this problem???
I didn't change any system apps, and for rooting purposes the only apps I downloaded where Titanium Backup, Sixaxis and Stickmount. Should I remove those?
and OT Rootkeeper. Do I remove root first?

flyi said:
See thread:
http://forum.xda-developers.com/showthread.php?t=1764794
seems to be due to custom kernel
Click to expand...
Click to collapse
I was getting exactly the same as you Foxman2k, about the unverified whole-file signature when trying the OTA way. I've just followed the advice of the above linked thread and it worked fine. I had to install Quick Boot (Reboot) to get in to Recovery, then update from SD Card, then ensure signature verification is disabled, then select the downloaded .zip file. I did have RootKeeper active, but I don't really understand what that does so not sure if it made any difference.
HTH

I finally managed to get mine to go through, am rooted but running stock and was getting the error with build.prop.
Then it hit me, I am in tablet mode with my screen at 160, so I set it back to 213 and boom it went through.
HTH