Database Info

idea for dualbooting android builds... somewhat

alrighty, basically im lazy and want someone else to do this for me.
heres my idea:
you install rc33 or whatever you want, make a nandroid backup of it, rename the folder to OS1. this folder contains your boot.img data.img and so on
then install or place a nandroid backup of another build into a folder called OS2..
then you would be able to boot into the modified recovery mode, which would have the selection to run a script, which then asks which OS to flash, 1 or 2, you press 1 or 2 wait for it to flash and reboot, a little hacky way to get a dual boot...
now who wants to repack a recovery image for me?

good idea would be worth a try , too bad im not up to par for the job , but id like to see it done

i'll give this a shot tomorrow and see what happens, not really feeling like doing it now. and i'm not gonna do it via rebuilding the recovery.img, just gonna make a script that does it for me from the recovery terminal. i'm quite lazy as well and i already have a script that runs the fastboot commands from my computer script to flash from one build to another, in theory it shouldn't be too hard to get the script terminal reaady and do that.

tubaking182 said:
i'll give this a shot tomorrow and see what happens, not really feeling like doing it now. and i'm not gonna do it via rebuilding the recovery.img, just gonna make a script that does it for me from the recovery terminal. i'm quite lazy as well and i already have a script that runs the fastboot commands from my computer script to flash from one build to another, in theory it shouldn't be too hard to get the script terminal reaady and do that.
Click to expand...
Click to collapse
I have a .bat file that I use to flash back and forth from Windows.
To RC33
cd C:\Android\
@echo off
echo :::Instructions:::
echo You must have:
echo system.img
echo data.img
echo boot.img
echo installed in the "C:\Android" directory
echo then enable fastboot on device before proceeding
pause
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
To 502H
cd C:\Android\502H\
@echo off
echo :::Instructions:::
echo You must have:
echo system.img
echo data.img
echo boot.img
echo installed in the "C:\Android\502H" directory
echo then enable fastboot on device before proceeding
pause
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Pretty simple. I have them stored to my desktop. I save my nandroid backups to the appropriate file and just double click. No problem. I just wish there was a script that I can use to reboot into HARDSPL mode (someone tell me if there is).

keatonreckard:
This is the worst idea i've heard so far...
FLASH has a limited life-time, and rewriting the whole system at every boot is a BAD idea.
If you want to dual-boot, you should look into making your own init-system, adding the ability to load another system (From SD).
Binary100100:
"adb reboot bootloader"

there might be a simpler way: change the kernel command so it mounts somewhere in sdcard as root. not sure how to do this without a computer though.

Hey binary, with your phone plugged into your comp pull up you cmd and type adb shell reboot bootloader, the phone will boot right into fastboot mode making it easy to continue the script

just to clarify...i meant a script that is store locally on the device in the recovery image... so then you dont need a computer at all... you can already do this, you just have to type in the commands from the recovery console...i just wanted an easier way to do it

Binary100100 said:
I have a .bat file that I use to flash back and forth from Windows.
To RC33
To 502H
Pretty simple. I have them stored to my desktop. I save my nandroid backups to the appropriate file and just double click. No problem. I just wish there was a script that I can use to reboot into HARDSPL mode (someone tell me if there is).
Click to expand...
Click to collapse
To flash back and forth from windows? You've been running Windows Mobile on the Dream? I must be missing something.

Joushou said:
keatonreckard:
This is the worst idea i've heard so far...
FLASH has a limited life-time, and rewriting the whole system at every boot is a BAD idea.
If you want to dual-boot, you should look into making your own init-system, adding the ability to load another system (From SD).
Binary100100:
"adb reboot bootloader"
Click to expand...
Click to collapse
not flash at every boot...just so you can text out a build and if you dont like it go back to a stable one on the go....
again, im taking the lazy way out

Disregard! - My mind ran ahead of what this post was about and I posted something regarding a slightly different idea!
I don't know about re-installing Nandroid backups...
But, if one wanted to be able to run two different installs...
Seems to me an easier way about doing this would be to have a modified SPL. It could have the option of selecting an update file...
For example, one could put two files on their sd card - update1.zip and update2.zip. The SPL could have one of the following options:
1) reboot into recovery mode - select "alt-s" - then you would have an option to select 1 or 2.
2) have an additional "Alt- " option.
"Alt-s" - runs update1.zip
"Alt-?" - runs update2.zip. (dev could pick the additional letter)
I think this would be great! No reteaching of anyone how to use the process. And, one could leave the primary use-able update.zip as "update1.zip" and use the other as the version being tried out. It wouldn't be a Nandroid back up... But, with the new "nowipe" builds it should work well.
My $.02 worth.

Joushou said:
keatonreckard:
This is the worst idea i've heard so far...
FLASH has a limited life-time, and rewriting the whole system at every boot is a BAD idea.
If you want to dual-boot, you should look into making your own init-system, adding the ability to load another system (From SD).
Binary100100:
"adb reboot bootloader"
Click to expand...
Click to collapse
To be fair, that limited life-time is something like 1,000,000 writes, which would take about... oh... a year straight of constantly rebooting your phone(assuming it takes 30 seconds per reboot)
EDIT: and that assumes re-writing the whole system every time you boot, which I don't think he means since he's saying its in the recovery image.

hmmm....
I know that from the alt+x console you can do this....
mount sdcard
echo "boot-recovery
--update_package=SDCARD:build1/update.zip" > /cache/recovery/command
reboot recovery
so if you wanted 2 builds available (I would think you would need a wipe for 2 completely different builds) but....
make 2 folders in on your sdcard
build1
build2
place a copy of the update.zip from each build you want to boot in the folder
make a script like this
Code:
echo "boot-recovery
--update_package=SDCARD:"$"/update.zip" > /cache/recovery/command
reboot recovery
save the script to the sdcard directory
then when you start your phone you could
1. type "mount sdcard" (no quotes)
2. type "sh sdcard/script.sh build1" (for build 1 located in /sdcard/build1/update.zip)
3. type "sh sdcard/script.sh build2" (for build 2 located in /sdcard/build2/update.zip)
problem would be when wipes are needed. But if you have 2 solid builds and don't need to wipe when swapping it should work.
Just need a way to make a script or bootloader that could run either one of these.
Cannot see another way around it since the OS is loaded into phone ROM/RAM
of course if your build supports the reboot command from the OS then you could just make a script to run when you want to reload the other build. Then you could skip the recovery console.

@beagz - Ha, forgot about that script. Yes, to switch between say, the DudesG build and Haykuro's H build one could write a script like that in Gscript and change back and forth when a new build comes out.
Like now... One could run Dudes G build and try out Haykuro's new ADP1.5 build.
But, I do believe your right about going back to a JF33 build - would need to wipe...

Gimpeh said:
To flash back and forth from windows? You've been running Windows Mobile on the Dream? I must be missing something.
Click to expand...
Click to collapse
Nah.. I was referring to using a bat file on my Windows computer to switch between 1.1 to 1.5 back to 1.1 by just executing the bat.
Now that i know that "adb reboot bootloader" will work it can be completely automated!
... but will it default to fastboot? Hmmm...

tubaking182 said:
Hey binary, with your phone plugged into your comp pull up you cmd and type adb shell reboot bootloader, the phone will boot right into fastboot mode making it easy to continue the script
Click to expand...
Click to collapse
Thanks! But is this going to put the phone in FASTBOOT mode? I'm trying to make this completely automatic if it's possible. Simply keep your latest and greatest backup .img's in a certain directory on your computer and EXECUTE!
Take a shower or whatever... come back and VOILA! Your previous backup.
The method that I've come up with thus far is pretty simple... but you just can't execute and walk away. You still need to enable FASTBOOT at the least on the bootloader. Although I haven't tried messing with it lately. I have my phone just like I want it.
Now that the Official ADP1.5 is out let's get to work on Mulitouch, themes, etc!

Wow this seems crazy but it just might work. Lol.

bat file to automatically restore backups using Windows!
So all you need to do is...
Open notepad, copy and paste the quoted text below, edit the top line of this bat file to the directory of your backups (I used "c:\android" for an example), save as .bat and double click. Wait and your done. Just watch it happen automatically.
Also if you decide to change that directory on the top line also use the directory on the 14th line. Your done. Easy restore to a backup.
HINT! Make a couple of these with a variety of directories on the top to change what backup your want to flash back to.
Example: c:\android\rc33; c:\android\501h; c:\android\adp15; etc
cd C:\android
color A
cls
@echo off
echo.
echo :::Instructions:::
echo.
echo You must have:
echo.
echo system.img
echo data.img
echo boot.img
echo.
echo installed in the "c:\android" directory
echo.
pause
cls
color b
echo.
echo.
echo.
echo Now restoring:
echo.
echo system.img
echo data.img
echo boot.img
echo.
echo to your device.
color c
echo.
echo DO NOT TURN OFF OR UNPLUG YOUR DEVICE DURING THIS PROCESS!!!
@adb shell reboot bootloader
@fastboot flash system system.img
@fastboot flash userdata data.img
@fastboot flash boot boot.img
@fastboot reboot
Click to expand...
Click to collapse
I've tested it and it works beautifully!
Hope it helps!
Thanks to everyone that pointed out the command "adb shell reboot bootloader"
This post is noob friendly.
OR
Use this script below for it to prompt for the location of your backups.
color A
cls
@echo off
echo.
echo :::Instructions:::
echo.
echo Enter directory of nandroid backups that you would like to restore...
set /p flash=path:
cd %flash%
cls
color b
echo.
echo.
echo.
echo Now restoring:
echo.
echo system.img
echo data.img
echo boot.img
echo.
echo to your device.
color c
echo.
echo DO NOT TURN OFF OR UNPLUG YOUR DEVICE DURING THIS PROCESS!!!
@adb shell reboot bootloader
@fastboot flash system system.img
@fastboot flash userdata data.img
@fastboot flash boot boot.img
@fastboot reboot
Click to expand...
Click to collapse
This one is even more noob friendly... but it's not as fast because it requires you to enter the location of your backups.
I hope it helps someone out there. It helps me.

[email protected]:
The average lifetime of flash is 100.000 writes, and flash isn't delivered 100% intact, they're usually delivered with faulty blocks (Depending on where you get it, blah blah blah).
That should change your numbers a bit (A month i believe?)
And, sure, he is using the update-zip, so it's not written to the same pages every time.
But still, it's a bad idea (Other than wearing stuff down, it will also be very slow ).
To dual-boot, modifying the init-system so it could choose from different android-runtimes would be way faster/cooler...

If possible, this would be pretty damn useful. Using a stable build while being able to tinker with experimental builds. Would definitly cut down on the constant flashing back and forth.

110 Error RUU 1.56 Fix - 100% unroot too!

Update - 2/21/2011
If you have bricked an HTC EVO this will likely NOT work for you and this is the wrong info to be reading. I have gotten a few emails from this link about EVO 110 errors.
12/26/2010 - This thread is super old now:
If you ran the 1.56 RUU and your phone no longer turns on visit htc.com, go to support, choose Hero (Sprint) and download the 2.1 system update.
Remove battery from your phone and start it up again, then run the exe file that you just downloaded -
http://member.america.htc.com/downlo...2.27.651.6.exe
------All the info below is kept for reference -------
(As of 3/31/2010 - I am 10 for 10 for getting these back and working!! 3/3 of going back to 100% stock)
Edit: I have no longer kept track... its been over a month and I know personally I've done about 15 more of these... with about half being return to stock.
If you need to contact me, PLEASE EMAIL instead of using private messages, it'll probably turn into a google talk chat anyways, so add me on there, [email protected] (Its just easier than having to log in here and reply to private messages, since I get emails on the go as well.)
So you just ran the 1.56 RUU and got a 110 error. Now your screen turns on and stays black and if you plug the phone into USB you see the HTC logo. Unplug it and see the RUU menu.
Like you, I decided to attempt to roll back using the RUU 1.56. I was hit with the 110 error, and nothing but fastboot would work, I was able to launch ./fastboot-mac oem boot to get into the system.
I tried ./fastboot-mac boot image/bootname.img and a billion other things like everyone else who is having the issue, but just like them I had no success. In the second post below are the steps to resolve this issue. This will either take you to your first Nandroid backup or to whatever ROM you choose to flash once you get recovery back. I have not found a way to get back to 100% stock, but at least your phone wont be a brick.
EDIT:As of 3/30/2010 @ 8:30 PM I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. See Post number 2 for the right way to do this.?
I've helped a few people over log me in now.
I'm willing to continue doing this but it is cutting into my family time, I will do this for a "respectable" amount of money.
Feel like I've helped you??
Buy me some coffee!

(Zip attached includes fix and stock folders. Use the fix folder FIRST to get completely booted. You can use the stock folder if you want to get 100% stock after you have a running unrooted system but have RA recovery.)
Steps to resolve:
(You SHOULD have a Nandroid backup of some sort, if not download a ROM... Fresh1.1??)
1) Boot the phone to black screen
2) Plug phone into PC/MAC - The HTC logo should appear at this point
---- If you've been doing anything else, rerun the RUU and let it fail and reboot to the HTC logo.
3) PC - fastboot oem boot | MAC - ./fastboot oem boot
(Make sure you turn on USB Debugging under Settings --> Applications --> Developer)
4) Root your phone using asroot2
Code:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
5) This is where your Nandroid backup comes into play.
(Browse to your nandroid folder, find your first backup and copy all of the .img files except system and cache to your SD card root directory)
NOTE: At this point you should dismount the SD card if you mounted inside of Android OS(Sense/Launcher)
6) run adb shell (PC - adb shell | Mac - ./adb shell)
7) type su
8) Run the following commands (if you get out of memory errors, type su again and try once more)
NOTE: Do not copy the "#"'s in the commands, the # just means you are running as SU, as opposed to the "$"
Code:
# flash_image recovery /sdcard/recovery.img
# flash_image boot /sdcard/boot.img
# flash_image misc /sdcard/misc.img
9) now... type reboot recovery
This time you should get your recovery menu, should have been RA or whatever you used... from there I did a complete nandroid restore and my system booted.
Also, after I did this I did try to let it boot without doing a recovery and it wouldnt go anywhere... but I'm fairly impatient... it may have wanted to load. I figured it best to do an entire Nandroid restore though.
-------------------------------------------------------------
100% Stock Configuration Work Around
-------------------------------------------------------------
Non-Rooted Nandroid Backup:
nandroid.7z
I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. I'm not sure how to go about posting a 127MB file, what do you think it the best place?
After restoring the Nandroid backup I tried this:
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
$ su
su: permission denied
Then I rebooted to recovery (I used RA 1.5.2)
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb remount
remount succeeded
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
/ # cd /sdcard
/sdcard # flash_image recovery /sdcard/Stock/recovery.img
flashing recovery from /sdcard/Stock/recovery.img
/sdcard # reboot recovery
I was booted to the Triangle and exclamation mark... I pulled the battery and booted up normally.
Stock Kernel - 2.6.27-533ce29d [email protected] )
Stock Build - 1.56.651.2 CL85027 release-keys

Other things that should be mentioned:
If you used RA 1.6.2 - I was unable to get my boot.img or the stock boot.img from the RUU's rom.zip to flash back to the recovery partition. I had to use the RA 1.6.2.img and "flash_image recovery /sdcard/recoverynamegoeshere.img"
It seems that if you've flashed the radio update, the RUU does not write the radio back successfully. Others have had issues going back to the stock radio using the upgrade.zip option as well.
I attempted to use the boot.img, recovery.img, from the RUU's rom.zip with no success. I might try it again. I was able to get to stock recovery (Triangle and exclamation) and to the Hboot menu... but from hboot I had to run the RUU and rebrick the device cause I couldnt get anything at that point, even fastboot oem boot wouldnt load.
There have been times when I get weird issues writing the flash recovery, boot, or misc and when you reboot and load "fastboot oem boot" it wont look like it goes anywhere.... check "adb devices" and your device should be listed. From there do an "adb remount" and then "adb shell" and reflash once more and then "reboot recovery".
If all else fails, I'm available for a small fee.
[email protected]

Anxiously waiting your news. Just encountered this problem today.

Updated ...
imekul said:
Anxiously waiting your news. Just encountered this problem today.
Click to expand...
Click to collapse

Wow! If you've fixed this, I think you're everyone's hero now. We won't have to worry about using the RUU now

I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..
I was reading over the forum post in http://forum.xda-developers.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!

I attempted flashing a new recovery image this way with no avail... I also attempted only
Code:
flash_image recovery /sdcard/recovery.img
and still was unable to boot the phone into recovery. I think it had to have been something with doing boot.img and recovery.img at the same time... I dont know what the misc.img does and I'm assuming data.img is userdata... but I did them all and then it worked...
Other users also tried flashrec and with no success... right track though.
chavo2005 said:
I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..
I was reading over the forum post in http://forum.xda-developers.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!
Click to expand...
Click to collapse

What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?

blankd3ckskat3r said:
What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?
Click to expand...
Click to collapse
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot

This!
Thanks Regaw
regaw_leinad said:
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot
Click to expand...
Click to collapse

Trying this right now.
So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?

If you get errors like...
adb shell
su
flash_image recovery .........
(out of memory... etc)
Then...
just su again... so you really su twice
its what I had to do.
imekul said:
Trying this right now.
So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?
Click to expand...
Click to collapse

Trying it a second time, and so far am getting a bunch of Out of memory errors. After the first one "finished," I did as you recommended and typed "su" a second time, and then typed the "flash_image recovery /sdcard/recovery.img" command.
So far, looks like it's giving the same errors the second time around.

This second attempt, it ended with "error writing recovery: No space left on device."
Just to be sure, I checked the SD card, and that has over 1 GB of free space.

If you're willing to allow something like logmein.com or some way for me to remote assist you, I would like to try. [email protected] if you're in.
imekul said:
This second attempt, it ended with "error writing recovery: No space left on device."
Just to be sure, I checked the SD card, and that has over 1 GB of free space.
Click to expand...
Click to collapse

Sounds awesome. Thanks. I'll e-mail you now.

Dun Dun Dun... The results are in!
imekul said:
Sounds awesome. Thanks. I'll e-mail you now.
Click to expand...
Click to collapse

dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!

imekul said:
dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!
Click to expand...
Click to collapse
We ended up just needing to run
Code:
adb shell
reboot
fastboot oem boot
adb shell
su
//flash commands here
that seemed to do it. so make sure if you're having issues to restart the device and try again!
Edit: Also, we didnt get data.img to work so we only did boot, recovery, and misc.img's

[Q] Rooting phone, Ace Hack Kit

Hello, I have been following the Ace Hack Kit. I got up to "3 S-OFF, SuperCID and More" and then the phone just shows a red triangle with an ! in the middle and a phone in the background. What do i do please help.

Scanlia said:
Hello, I have been following the Ace Hack Kit. I got up to "3 S-OFF, SuperCID and More" and then the phone just shows a red triangle with an ! in the middle and a phone in the background. What do i do please help.
Click to expand...
Click to collapse
Just a couple questions that might help someone fix your problem....
Are you using windows or mac?
Are you using the hack-ace.cmd that came in the zip or did you replace that one with the V11b cmd?

Im using win 7 64bit and i just used the cmd that was there. I searched the forum and came to one that told me to press vol up and power, and then the phone turned off and now im back. I'm still up to step three on the ace hack kit but my phone is still the same as before, i dont know what has changed.

Scanlia said:
Im using win 7 64bit and i just used the cmd that was there. I searched the forum and came to one that told me to press vol up and power, and then the phone turned off and now im back. I'm still up to step three on the ace hack kit but my phone is still the same as before, i dont know what has changed.
Click to expand...
Click to collapse
Well to be honest with you, anytime someone has trouble with the hack kit....attn1 always tells people to use v11b (all you do is download it from the forum, delete that one, that is in the file you created after unzipping and replace it with the new one, then rerun the hack kit....
Unless someone else has a better idea....

Hello, I tried to turn the phone on in "hboot" using vol up and power and it worked. Then I put the Android Revolution 4G ROM on it along with the EXT4 data partion thing. Now when I come to the hboot again, it doesnt give me the option to install zip from sd card. What do I do?

Scanlia said:
Hello, I tried to turn the phone on in "hboot" using vol up and power and it worked. Then I put the Android Revolution 4G ROM on it along with the EXT4 data partion thing. Now when I come to the hboot again, it doesnt give me the option to install zip from sd card. What do I do?
Click to expand...
Click to collapse
That rom needs to be flashed in recovery, and I assume you allready have rom manager installed and flashed clockworkmod recovery....
Then to get into recovery you turn on the phone using power and volume "down" (not volume up) and then scroll down to recovery...
Also when you get to hboot...does you phone say S-off at the top?

I don't have rom manager or clockwork recovery mod, and my phone hasn't even been rooted yet? I will try the process again but with 11b.
Also: My mistake, when i press "vol down and power" it goes into hboot, and vol up doesn't do anything.
And from hboot, i choose recovery, and then i get a phone with a red triangle exclamation mark. I think that is recovery. Then it still doesn't give me any option to install any roms or zips. It just has:
Reboot system now
Apply sdcard: update.zip
Wipe data/factory reset
Wipe cache partion
theres also an Error: Can't open /cache/recovery/command
Thanks.

Scanlia said:
I don't have rom manager or clockwork recovery mod, and my phone hasn't even been rooted yet? I will try the process again but with 11b.
Also: My mistake, when i press "vol down and power" it goes into hboot, and vol up doesn't do anything.
And from hboot, i choose recovery, and then i get a phone with a red triangle exclamation mark. I think that is recovery. Then it still doesn't give me any option to install any roms or zips. It just has:
Reboot system now
Apply sdcard: update.zip
Wipe data/factory reset
Wipe cache partion
theres also an Error: Can't open /cache/recovery/command
Thanks.
Click to expand...
Click to collapse
Yeah, you definitely need to get it rooted before you can start flashing any roms....and recovery wont give you the option to flash the zip because clockworkmod hasn't been flashed yet....and in order to flash clockworkmod you need rom manager, which requires root.....
Once you get all that done, when you go into recovery you will have a lot more options....
So just need to work on getting you phone to that root, s-off point.....

Thanks for your help, I re-did the a whole ace hack kit thing and it did the same thing as before. It would be going on its way, then, during part 3, the phone would go into recovery and then the cmd would flash: Error: device not found about 10 times then go back to the main menu. I dont know what to do, is this an error on my part?
Was the ace hack kit supposed to do anything? because my phone is still excactly the same, except for the fact that you can boot into hboot and recovery.

Scanlia said:
Thanks for your help, I re-did the a whole ace hack kit thing and it did the same thing as before. It would be going on its way, then, during part 3, the phone would go into recovery and then the cmd would flash: Error: device not found about 10 times then go back to the main menu. I dont know what to do, is this an error on my part?
Was the ace hack kit supposed to do anything? because my phone is still excactly the same, except for the fact that you can boot into hboot and recovery.
Click to expand...
Click to collapse
No it basically just downgrades your radio so that it can be to rooted, shouldn't really change your phone much yet....usually the problem is one of two things...
-bad gold card...something wasn't copied correctly, next time you try again you might try to get another gold card file...
-or something wrong with your SD card....you may try to format your SD card and try again...
Also....Did you miss or skip any of these steps.....
-do you have htc sync installed, and then uninstalled just leaving the drivers
-is your phone in charge only mode
-is usb debugging enabled
-is fast boot turned off
-all virus protection off (anti virus, windows defender, firewall)
All prior to downloading
Then are you you....
Downloading ace-hack-kit-v11a.zip...then unzipping to a folder of your choice....go in to that folder and delete....hack-ace.cmd.....then go back to this thread, download hack-ace.cmd v11b and stick that in your newly unzipped file...then of course run as administrator (windows..right click, run as administrator)
EDIT: You will know your successful when you get into hboot and see that s-off at the top of your screen.
EDIT2: there is also a link in the OP of the hack kit thread, that will give you the newest htc drivers for your computer that are a little more reliable....

Here just for future Reference, if you are able to get root/s-0ff.....here is a good path to follow
Download this
http://forum.xda-developers.com/showthread.php?t=1058042
(either the side loading or no side loading one, it wont matter since you plan on flashing a custom rom)
-Rename the zip to PD98IMG.zip (it has to be named exactly that)
-place it in the root of your SD card
-reboot to hboot (power volume down)
-dont press anything, it will find the zip, after 3 attempts and ask you if you want to update, volume up to update.
This rom will give you the newest updated radio and OTA updates...that way you have the fast download speeds.
Then download rom manager from the market, go into rom manager and flash clockworkmod recovery...reboot your phone (optional, but I've found it helps)...go back into rom manger and reboot into recovery....From there you can (wipe data/facory reset, wipe cache, dalvik cache, and start flashing your android revolution rom.
Definitely not the only path to follow, but its a nice safe one that will get you what you need. Hope this helps, and Good luck

Thanks.
I tried it again, making sure I did all those things bit it still stopped.
I opened the cmd file and in the section that it got stuffed up:
:soff
tools\win\adb kill-server
tools\win\adb devices >nul
tools\win\adb push tools/soff/gfree /data/local
tools\win\adb push tools/soff/flash_image /data/local
tools\win\adb push tools/soff/recovery.img /data/local/tmp
tools\win\adb push tools/dngrd/psneuter /data/local/tmp
tools\win\adb shell chmod 0755 /data/local/tmp/*
tools\win\adb shell chmod 777 /data/local/gfree
tools\win\adb shell chmod 777 /data/local/flash_image
tools\win\adb shell /data/local/tmp/psneuter
cls
tools\dngrd\sleep 2
tools\win\adb kill-server
tools\win\adb devices >nul
tools\win\adb shell /data/local/gfree -f
tools\win\adb shell sync
tools\win\adb shell /data/local/flash_image recovery /data/local/tmp/recovery.img
echo. please wait - booting recovery to patch downgrade ROM Root/Sound/Locale
tools\win\adb reboot recovery
echo
tools\dngrd\sleep 10
echo please wait [[THIS IS WHERE THE PHONE SHOWS THE PHONE WITH A RED ! TRIANGLE]]
tools\dngrd\sleep 10
tools\win\adb kill-server [[THE COMMANDS AFTER THIS JUST SHOW ERRORS]]
tools\win\adb devices >nul
tools\win\adb push tools/afr/boot.img /tmp
tools\win\adb shell flash_image boot /tmp/boot.img
tools\win\adb shell mount -o rw /dev/block/mmcblk0p25
tools\win\adb shell mount -o rw /dev/block/mmcblk0p26
tools\win\adb shell rm -R /data/*
tools\win\adb shell rm -R /system/customize
tools\win\adb push tools/afr/system /system
tools\win\adb shell chmod 06755 /system/bin/su
tools\win\adb shell chmod 0644 /system/lib/modules/bcm4329.ko
tools\win\adb shell chmod 0644 /system/app/RomManager.apk
tools\win\adb shell chmod 0644 /system/app/Superuser.apk
tools\win\adb shell sync
tools\win\adb reboot
goto :EOF
And then it goes back to the main menu.
EDIT1: vol down + power goes into hboot, and then at the top it shows:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0019
MICROP-0438
RADIO-(some other number)
eMMC-boot
Dec 27 2010,14:47:30
HBOOT USB PLUG
FASTBOOT
RECOVERY
RACTORY RESET
SIMLOCK
IMAGE CRC

Did you try formatting your SD card first, not a quick format, but a full format..I know it takes like a half hour or so to format....If so, then you will probably need to get help from attn1.....Here is the link for his irc channel, but he probably wont be there till tomorrow....also try posting your problem in the hack kit thread in the dev forum....
Hopefully someone else can step in and fix your problem.....

Hello, I ended up using Bubby's One Click GUI, and it is great, I'm in the process of rooting and its working well. After this would I be able to flash Android Revolution 4G and some themes?

Scanlia said:
Hello, I ended up using Bubby's One Click GUI, and it is great, I'm in the process of rooting and its working well. After this would I be able to flash Android Revolution 4G and some themes?
Click to expand...
Click to collapse
Yes you can...you should be all set to go!!

Scanlia said:
...Was the ace hack kit supposed to do anything? because my phone is still exactly the same, except for the fact that you can boot into hboot and recovery.
Click to expand...
Click to collapse
S.Reno9 said:
No it basically just downgrades your radio so that it can be rooted, shouldn't really change your phone much yet....
Click to expand...
Click to collapse
So does that mean I don't need to load a rom into the romzip folder of the ace hack kit before I start this process?
I plan on going with the LeeDrOiD rom, but do I put it in the ace kit? Or flash it from the sdcard after I finish the ace hack kit?
My romzip folder in the ace kit just has the text file saying "put-rom.zip-here.txt"
I have my goldcard img in the gcimg folder.
I have been reading thru numerous threads in preparation for the process, but the more I read the more intense it gets. It went from "just rooting and flashing a rom" to now trying to figure out the whole rom/radio/Ril/kernel upgrade/compatibility mix...

The ace hack kit is very straight forward. load the rom afterwards with cwm. make sure your SD card is formatted the right way. Then run the cmd program and follow the instructions via the effen manual.
Sent from my Inspire 4G using XDA Premium App

fireproof69 said:
So does that mean I don't need to load a rom into the romzip folder of the ace hack kit before I start this process?
I plan on going with the LeeDrOiD rom, but do I put it in the ace kit? Or flash it from the sdcard after I finish the ace hack kit?
My romzip folder in the ace kit just has the text file saying "put-rom.zip-here.txt"
I have my goldcard img in the gcimg folder.
I have been reading thru numerous threads in preparation for the process, but the more I read the more intense it gets. It went from "just rooting and flashing a rom" to now trying to figure out the whole rom/radio/Ril/kernel upgrade/compatibility mix...
Click to expand...
Click to collapse
You can put the LeeDroid rom in the romzip folder or flash it in recovery after you finish the hack kit. I tend to go the simple route and flash a new rom in recovery after it's rooted.

fireproof69 said:
So does that mean I don't need to load a rom into the romzip folder of the ace hack kit before I start this process?
I plan on going with the LeeDrOiD rom, but do I put it in the ace kit? Or flash it from the sdcard after I finish the ace hack kit?
My romzip folder in the ace kit just has the text file saying "put-rom.zip-here.txt"
I have my goldcard img in the gcimg folder.
I have been reading thru numerous threads in preparation for the process, but the more I read the more intense it gets. It went from "just rooting and flashing a rom" to now trying to figure out the whole rom/radio/Ril/kernel upgrade/compatibility mix...
Click to expand...
Click to collapse
No, you don't need to load the rom there. You need to downgrade first. Then after that you can flash a rom

[Q] ClockworkModRecovery (Only wants to wipe data) [SOLVED - Read / Scroll Down]

Ok, so i have a fresh new stock of 21e flashed onto my phone. Rooted with no errors, and I have Clockwork ROM Manager installed.
If I use the app to boot into recovery my phone just automatically Wipes all data then loads back up as if a fresh install was done, so I thought I would check the problem out myself (Power and vol.down), and the only options I have in the Clockwork Boot Menu are as follows:
Android system recovery <3e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes -- delete all user data
No
No
No
Click to expand...
Click to collapse
If I go back one page the only options I have are as follows:
Android system recovery <3e>
Android system recovery utility
reboot system now
wipe data/factory reset
wipe cache partition
wipe cache partition and package recovery
wipe nv dynamic partition
Click to expand...
Click to collapse
I can not go back any further, they are my only options in boot recovery of which I find extremely odd. (Until this is sorted I can not install a new ROM/Kernel and fix my network)
Any help would be much appreciated.
Kind Regards.

Loopy Frog said:
Ok, so i have a fresh new stock of 21e flashed onto my phone. Rooted with no errors, and I have Clockwork ROM Manager installed.
If I use the app to boot into recovery my phone just automatically Wipes all data then loads back up as if a fresh install was done, so I thought I would check the problem out myself, and the only options I have in the Clockwork Boot Menu are as follows:
If I go back one page the only options I have are as follows:
I can not go back any further, they are my only options in boot recovery of which I find extremely odd. (Until this is sorted I can not install a new ROM/Kernel and fix my network)
Any help would be much appreciated.
Kind Regards.
Click to expand...
Click to collapse
That's not ClockworkMod.
That's the stock Android recovery.

ah lol (embarrassing)
Thanks though... ok so it seems that my problem is that the copious amount of things that I try to install clockwork boot, it just wont happen. Any ideas?
Regards

Loopy Frog said:
ah lol (embarrassing)
Thanks though... ok so it seems that my problem is that the copious amount of things that I try to install clockwork boot, it just wont happen. Any ideas?
I am just about to see if I can do something with the LGDP2 V36 UMTS.
Regards
Click to expand...
Click to collapse
You can flash ClockworkMod Recovery with this.
[GUIDES/TOOLS]Making Developing/Flashing/Returning to Stock Easier
The Dark Lestat said:
1. Recovery Manager
This is a flashing tool that will let you install:
Stock Recovery
ClockworkMod Recovery
Touch ClockworkMod Recovery
Requirement:
You'll need to have the LG Thrill / Optimus 3D
You'll need to be rooted.
Superuser and SU have to be updated to the latest app and binary
Update Superuser in the market
Open Superuser app and go to the options
Scroll to the bottom and click "Su binary"
DOWNLOAD LINK: Recovery Manager - 18 MB
How To Use:
Extract the files with WinRar or 7zip
Launch "Recovery Manager.bat"
Make sure your phone is in "USB Debugging Mode" and is plugged in
Choose your option
Wait for the screen to refresh
Boot into recovery to verify it was flashed successfully
Click to expand...
Click to collapse

No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?

Loopy Frog said:
No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?
Click to expand...
Click to collapse
Try: 3d+volume down+power button
hold til 3 sec after seeing the logo.

Loopy Frog said:
No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?
Click to expand...
Click to collapse
You can also use the ROM Manager app to boot into recovery.

p-vlad said:
Try: 3d+volume down+power button
hold til 3 sec after seeing the logo.
Click to expand...
Click to collapse
Nope doesn't work. >_<
The Dark Lestat said:
You can also use the ROM Manager app to boot into recovery.
Click to expand...
Click to collapse
Yeah that's what I was using when it used to work, however now when I do it, It just "deletes all user data". Obviously because it is not having any response from the Clockwork recovery boot, and goes straight into:
Android system recovery <3e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes -- delete all user data
No
No
No
Click to expand...
Click to collapse
I just don't understand why My boot wont change from android to the clockwork boot. >_<

Is it being flashed properly?
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
(I took the commands from The Dark Lestat's batch file, props go to him. I was too lazy to search for it Don't judge me, it's 12.30am here)

pandaball said:
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
Click to expand...
Click to collapse
Thanks Panda, I'll give it ago later when I have time, and let ya know how I go.

Loopy Frog said:
Thanks Panda, I'll give it ago later when I have time, and let ya know how I go.
Click to expand...
Click to collapse
Also, I'll update the scripts with a newer version, so that it's simplified.

Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!

JastaPein said:
Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!
Click to expand...
Click to collapse
It's not using ROM Manager to BOOT into recovery.
It's using ROM Manager to install ClockworkMod that was the issue.

Very weird indeed. I also have flashed yhe 21E rom from LG. Next I rooted the phone and installed CWM touch. I have no problems with it.

JastaPein said:
Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!
Click to expand...
Click to collapse
Thanks, either/or this doesn't matter at this stage, I need to able to boot into recover for this or even clockwork to do it anyway. I'll keep this in mind nonetheless.
pandaball said:
Is it being flashed properly?
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
(I took the commands from The Dark Lestat's batch file, props go to him. I was too lazy to search for it Don't judge me, it's 12.30am here)
Click to expand...
Click to collapse
All went well, expect for the last string, see below;
I renamed "recovery-clockwork-touch-5.8.1.5-p920" - "x"
C:\Users\Astro\ADB>adb push x.img /data/local/tmp
3204 KB/s (5995063 bytes in 1.827s)
C:\Users\Astro\ADB>adb shell su -c "dd if=/data/local/tmp/x.img of=/dev/block/mmcblk0p6 bs=4096"
1463+1 records in
1463+1 records out
5995063 bytes transferred in 0.992 secs (6043410 bytes/sec)
C:\Users\Astro\ADB>adb shell "rm/data/local/tmp/x.img"
rm failed for /data/local/tmp/x.img, No such file or directory
Click to expand...
Click to collapse

Loopy Frog said:
All went well, expect for the last string, see below;
I renamed "recovery-clockwork-touch-5.8.1.5-p920" - "x"
Click to expand...
Click to collapse
I'm about to upload a newer version of it. Let me know if it works.

Alright.
Here's the new Recovery Manager with updated scripts. It should be a lot cleaner now.
Recovery Manager

The Dark Lestat said:
Alright.
Here's the new Recovery Manager with updated scripts. It should be a lot cleaner now.
Recovery Manager
Click to expand...
Click to collapse
You my friend, are truly amazing!! what ever your alterations were; it worked!
Thank you.

Loopy Frog said:
You my friend, are truly amazing!! what ever your alterations were; it worked!
Thank you.
Click to expand...
Click to collapse
I think it's because my scripts were thrown together in the previous one.
Anyways, it's cleaned up.
Glad it worked!

[Q] Manually backup EFS

I don't want to install a custom recovery, but I want a backup of the EFS, one can never be to careful. Could I just copy modemst1 and modemst2 with root explorer or something else to a secure location and be done with it or is there something else to be done?

Itsukki said:
I don't want to install a custom recovery, but I want a backup of the EFS, one can never be to careful. Could I just copy modemst1 and modemst2 with root explorer to a secure location and be done with it or is there something else to be done?
Click to expand...
Click to collapse
Turn this into a .sh and execute (requires busybox):
Code:
echo "";
echo "Creating backup directory: /storage/sdcard0/EFS Backup.";
mkdir -p "/storage/sdcard0/EFS Backup/temp/";
cd "/storage/sdcard0/EFS Backup/temp/";
echo "Commencing backup...";
echo "Copying modemst1";
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=modemst1.img;
echo "Copying modemst2";
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=modemst2.img;
datetime=$(date +'%Y%m%d_%H%M');
echo "Compressing backup (efsbackup_$datetime.tar.gz)...";
tar -chzf "/storage/sdcard0/EFS Backup/efsbackup_$datetime.tar.gz" *;
echo "Cleaning up...";
rm -rf "/storage/sdcard0/EFS Backup/temp/";
echo "Backup complete!";
echo "";

Aerowinder said:
Turn this into a .sh and execute (requires busybox):
Code:
echo "";
echo "Creating backup directory: /storage/sdcard0/EFS Backup.";
mkdir -p "/storage/sdcard0/EFS Backup/temp/";
cd "/storage/sdcard0/EFS Backup/temp/";
echo "Commencing backup...";
echo "Copying modemst1";
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=modemst1.img;
echo "Copying modemst2";
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=modemst2.img;
datetime=$(date +'%Y%m%d_%H%M');
echo "Compressing backup (efsbackup_$datetime.tar.gz)...";
tar -chzf "/storage/sdcard0/EFS Backup/efsbackup_$datetime.tar.gz" *;
echo "Cleaning up...";
rm -rf "/storage/sdcard0/EFS Backup/temp/";
echo "Backup complete!";
echo "";
Click to expand...
Click to collapse
That was fast, thanks!

If you're rooted and doing things that concern you about your efs, you definitely should have a custom recovery
Sent from my Nexus 5 using Tapatalk

Nah, I don't think that i'm going to do anything that could damage the EFS but if my knowledge and experience with digital systems shows me something, is that some times things get damaged by themselves. A bad reboot, a rom update fails, a mysterious software bug that affect only 1% of it's users... totally unexpected things that no one saw coming. Thats why its better to have backup of those unrecoverable things, I might never use it, but better have it than not...

well theres no better way to recover than using recovery. If you're rooted, use a recovery
Sent from my Nexus 5 using Tapatalk

Wait, you're not rooted? You need root to execute that script.

Aerowinder said:
Wait, you're not rooted? You need root to execute that script.
Click to expand...
Click to collapse
Think he is rooted
Sent from my Nexus 5 using Tapatalk

Additionally you can run a recovery image without having to install it if you wish.
From the bootloader (which must be unlocked) and connected to your computer, you can run the fastboot command:
fastboot boot /path_to_recovery_image/recovery.img
That way you can try out the different recoveries to see which is your preference or if you don't want to install either.

I do have root, a custom kernel and some xposed modules.
The thing is that I got the nexus 5 because I was tired of android and flashing custom roms. I told myself that I would get a nexus or an iphone and, since I live in Venezuela (with an economy in the brink of collapse where I could sell this phone cheap for about 15 times what it costed me, I would be afraid of having a 600$+ iphone on my pocket), I decided for the nexus. You could say my faith was restored for I would choose the nexus over the iphone given the chance...
I don't want a custom recovery because I would be constantly tempted on a custom rom, I already got the kernel because it uses fastboot

Itsukki said:
I do have root, a custom kernel and some xposed modules.
The thing is that I got the nexus 5 because I was tired of android and flashing custom roms. I told myself that I would get a nexus or an iphone and, since I live in Venezuela (with an economy in the brink of collapse where I could sell this phone cheap for about 15 times what it costed me, I would be afraid of having a 600$+ iphone on my pocket), I decided for the nexus. You could say my faith was restored for I would choose the nexus over the iphone given the chance...
I don't want a custom recovery because I would be constantly tempted on a custom rom, I already got the kernel because it uses fastboot
Click to expand...
Click to collapse
Haha. I can't begin to describe how weird I think you are
Sent from my Nexus 5 using Tapatalk

rootSU said:
Haha. I can't begin to describe how weird I think you are
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I know!, I had to read that several times myself.
My idea was to leave the phone completely stock but here I am with xposed and a custom kernel. I know I'll end up using custom roms but I want to delay it much as possible. Most of the apps I use are cloud based because I used to wipe my phone like twice a week.
Sent from my Nexus 5 using XDA Free mobile app