[GUIDE] Official HBOOT v2.xx Downgrade to OLD HBOOT

[GUIDE] Official HBOOT v2.xx Downgrade to OLD HBOOT - HTC Desire S

UPDATED as of 18 DEC 2012 clarified and fixed some things..
Worldwide disclaimer not held responsible if something went wrong blah blah blah goes here..
Click to expand...
Click to collapse
THIS GUIDE WILL VOID YOUR WARRANTY BECAUSE OF THE HTC-DEV UNLOCK METHOD!!! And you can only use this guide if you are on HBOOT v2.xx
Click to expand...
Click to collapse
This guide may also be used for DEBRANDING your phone..
Click to expand...
Click to collapse
Check my sig first, then these for proper and additional information:
[GUIDE] Possible FIX for the infamous eMMC problem..
[Q] Bricked my phone?
NOTE:
RUUs with v1.xxx have HBOOTs with v0.98.000, while v2.xxx have HBOOTs with 2.00.002, and the ICS RUU has the only HBOOT v2.02.002
Click to expand...
Click to collapse
I will not supply the necessary files that is needed, you MUST know how to use SEARCH. I also suggest to give THANKS to those who originally made/uploaded the files.
Requirements:
Common Sense
- it helps A LOT
HTC Sync for Desire S - Installed
- for its drivers and such, or you may just install the "naked" drivers
Android Windows Tools - Installed
- for adb, fastboot commands
HTC-Dev unlocked
- to change recovery and ROM
Custom recovery
- to flash Root Access
SuperSU or SuperUser flashable zip
- to have Root Access
Root Access
- to change phone version
misc_version file (attached)
- file needed to change phone version
GoldCard
- to flash any version of RUUs
RUU executable file
- to DOWN/UPgrade
Click to expand...
Click to collapse
Quick tip:
Copy-Paste the cmd codes for you to not have any problem. 1 typo error (extra digit on misc_version) will render your phone unable to RUU.
Click to expand...
Click to collapse
Preparations
a. Create a folder "downsaga" on your C:
b. Copy misc_version, recovery.img(custom) on that folder.
c. Copy SuperSU's or SuperUser's flashable zip to your SD card.
Click to expand...
Click to collapse
Creating a Gold Card (use below or attn1's GoldCard Method)
a. Install Goldcard Helper from the market on your phone
b. Run it and copy the CID for MMC2, or email the info to yours
c. This number has already been reversed so go to http://psas.revskills.de/?q=goldcard, fill out the required fields.
d. Download the image file that was emailed to you.
e. Connect phone as a "Disk drive" using USB cable.
f. Use Gold Card Tool to flash your image file to your phone's SD card. (you might need to reformat it first with Panasonic's SD Formatter)
g. Disconnect safely from the PC.
NOTE:Your sd card is now a GoldCard unless you reformat it again. You should now be able to RUU to any version you would like given that the bootloader is LOCKED.
Click to expand...
Click to collapse
Unlocking the bootloader
a. Go to htcdev.com/bootloader
b. Proceed and follow every step on the guide
c. You just need to install Android Windows Tools files for it. No need to download the SDK and JAVA.
d. Once done, boot on bootloader and you should be able to notice if its UNLOCKED.
Click to expand...
Click to collapse
Flashing Custom Recovery
a. The phone must be on bootloader, then go to fastboot
b. Open up command prompt then type:
Code:
fastboot flash recovery C:\downsaga\recovery.img
fastboot reboot-bootloader
d. Access recovery
Click to expand...
Click to collapse
Flashing Root Access
a. Flash SuperSU or SuperUser
b. Reboot the phone normally
Click to expand...
Click to collapse
Modifying the version of your phone
a. Connect the phone using USB cable using "Charge ONLY" and USB Debugging is ON.
b. Open command prompt and input these codes:
Code:
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
adb reboot-bootloader
c. Your phone should now be read as the version you've placed there (but not visible to settings)
Click to expand...
Click to collapse
Locking the bootloader
a. You should be on fastboot
c. In cmd use this command to lock the bootloader:
Code:
fastboot oem lock
c. You might receive an error message on your CMD but don't mind it. The phone should restart itself automatically on bootloader, and you should be able to notice at the top saying "***RE-LOCKED***", and might also has *Security Warning*. Just ignore.
Click to expand...
Click to collapse
Downgrading
a. Make sure you are still on fastboot with the above message.
b. Open the RUU that you've chosen to install on your phone
c. The RUU must detect your phone version as 1.27.405.6
d. If you have received errors, then you've done something wrong. Review everything that you've done and check the guide again.
Click to expand...
Click to collapse
If everything went well, you should have successfully downgraded your phone and your HBOOT.

Hey man it seems you did it! So HTC official unlocker can be handy after all.
Great job! I assume that now you will use Revolutionary to gain S-OFF and back to flashing?

amidabuddha said:
Hey man it seems you did it! So HTC official unlocker can be handy after all.
Great job! I assume that now you will use Revolutionary to gain S-OFF and back to flashing?
Click to expand...
Click to collapse
yes sir'ree!

And howto flash your hboot in recoverymode
Use flash_image to flash your hboot to older version.
flash_image /dev/block/mmcblk0p18 )(path to an older hboot file)

NikMel said:
Use flash_image to flash your hboot to older version.
flash_image /dev/block/mmcblk0p18 )(path to an older hboot file)
Click to expand...
Click to collapse
You wouldn't be able to do that on an official, latest S-ON HBOOT. I have already tried that but will just give you an INFOsignature error.

Skanob said:
Step 1: Creating a Gold Card
a. Install Goldcard Helper from the market
b. Run it and copy the CID for MMC2, or email the info to yours
c. This number has already been reversed so go to http://psas.revskills.de/?q=goldcard, fill out the required fields.
d. Download the image file that was emailed to you.
e. Connect phone as a "Disk drive" using USB cable.
f. Use Gold Card Tool to flash your image file to your phone's SD card. (you might need to reformat it first with Panasonic's SD Formatter and then format it with the Gold Card Tool again)
g. Disconnect safely from the PC, and disconnect the cable.
Click to expand...
Click to collapse
Why would you use such an obsolete method to make a gold card?
after temproot,
windows batch script ( example filename: gc.cmd ):
Code:
adb push goldcard /data/local/tmp/
adb shell chmod 777 /data/local/tmp/goldcard
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid > tcid
set/p cid= < tcid
del tcid
adb shell /data/local/tmp/goldcard -c %cid% -o /data/local/tmp/goldcard.img
adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
Linux shell script (example filename: gc.sh ):
Code:
adb push goldcard /data/local/tmp/
adb shell chmod 777 /data/local/tmp/goldcard
cid=`adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid`
adb shell /data/local/tmp/goldcard -c $cid -o /data/local/tmp/goldcard.img
adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
get the android goldcard binary here:
Thanks to Revskills for the algorythm and to GenePoole for the Android binary.
With this, the entire process can be scripted.

Skanob said:
You wouldn't be able to do that on an official, latest S-ON HBOOT. I have already tried that but will just give you an INFOsignature error.
Click to expand...
Click to collapse
You can do that in recoverymode within adb shell #
I use 4ext recoverymode

attn1 said:
Why would you use such an obsolete method to make a gold card?
after temproot,
windows batch:
Code:
adb push goldcard /data/local/tmp/
adb shell chmod 777 /data/local/tmp/goldcard
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid > tcid
set/p cid= < tcid
del tcid
adb shell /data/local/tmp/goldcard -c %cid% -o /data/local/tmp/goldcard.img
adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
Linux Shell:
Code:
adb push goldcard /data/local/tmp/
adb shell chmod 777 /data/local/tmp/goldcard
cid=`adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid`
adb shell /data/local/tmp/goldcard -c $cid -o /data/local/tmp/goldcard.img
adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
get the android goldcard binary here:
Thanks to Revskills for the algorythm and to GenePoole for the Android binary.
With this, the entire process can be scripted.
Click to expand...
Click to collapse
well, that obsolete-method for me is a hell-of-a-lot easier and noob-proof. no code needed. and also leaves you a copy of your goldcard.img

NikMel said:
You can do that in recoverymode within adb shell #
I use 4ext recoverymode
Click to expand...
Click to collapse
That didn't worked for me. Prior to downgrading, check my sig. I'm using the official S-ON, not the ENG S-OFF leaked.

Skanob said:
well, that obsolete-method for me is a hell-of-a-lot easier and noob-proof. no code needed. and also leaves you a copy of your goldcard.img
Click to expand...
Click to collapse
No way is it easier or noob proof. When I used this method on the Ace Hack Kit goldcard errors dropped to none. Since you are already running adb commands and pushing crap to the phone, what's the big deal with this?
With this, there is no need for hacky tools, not mounting/dismounting the sdcard (risking corruption from unflushed write buffers and improper dismounts), and no need to go to the revskills website.
This runs in about a second and it's done.

attn1 said:
No way is it easier or noob proof. When I used this method on the Ace Hack Kit goldcard errors dropped to none. Since you are already running adb commands and pushing crap to the phone, what's the big deal with this?
With this, there is no need for hacky tools, not mounting/dismounting the sdcard, and no need to go to the revskills website or copy files back from email. This runs in about second and it's done.
Click to expand...
Click to collapse
I believe that that is based on your preference. Which I observed really knows a lot about adb.
And what is in the guide is based on my own preference. Which for me does not know much about adb.
They still can follow which ever method they would like.
Well, it would still give us the same result. Having a GoldCard.

Skanob said:
I believe that that is based on your preference. Which I observed really knows a lot about adb.
And what is in the guide is based on my own preference. Which for me does not know much about adb.
They still can follow which ever method they would like.
Well, it would still give us the same result. Having a GoldCard.
Click to expand...
Click to collapse
Mine is based on real results after thousands of uses of the Ace Hack Kit, which formerly did things the obsolete way.
Yours is based on preference.
But you are right, either way will result in a goldcard if executed properly.

attn1 said:
Mine is based on real results after thousands of uses of the Ace Hack Kit, which formerly did things the obsolete way.
Yours is based on preference.
But you are right, either way will result in a goldcard if executed properly.
Click to expand...
Click to collapse
yeah. I'll update the guide with your method aswell. Thanks aswell!
High five!

Skanob said:
yeah. I'll update the guide with your method aswell. Thanks aswell!
High five!
Click to expand...
Click to collapse
You're welcome.
Make a note that those are the contents of a script - .cmd or .sh.
FYI, if you try this to make the goldcard image, the one generated should match the md5 of one you got from Revskills.
Once you do it this way, you will never go back.

@Scanob
Since you change your guide in step 6 to run RUU instead of PG88IMG.zip than the Goldcard is no longer needed isn't it?

misc_version not found error....

I don't know how to find this official recovery.img. (Yes I try to find it...)
Step 4: Flashing official recovery.img

amidabuddha said:
@Scanob
Since you change your guide in step 6 to run RUU instead of PG88IMG.zip than the Goldcard is no longer needed isn't it?
Click to expand...
Click to collapse
You will still need it. Even the PG88IMG.zip method uses checks as exactly the same as doing an RUU.

hekermeker said:
misc_version not found error....
Click to expand...
Click to collapse
barthdvs said:
I don't know how to find this official recovery.img. (Yes I try to find it...)
Step 4: Flashing official recovery.img
Click to expand...
Click to collapse
Re-check the guide after a few

@barthdvs
Getting the Official files
a. Download the HTC_EUROPE_2.10.401.5 RUU file.
b. Run the file and do not close
c. Go to your temp folder on your computer and find the rom.zip file.
d. Copy it somewhere else.
e. Extract the rom.zip and you should now have the official .img files from the RUU.
f. Use the respective files needed for the guide.
or the files is here (files exrtract from HTC_EUROPE_2.10.401.5 RUU file)
Boot.img : http://www.multiupload.com/JME2WRDQEQ
recovery.img : http://www.multiupload.com/MX64VDUICI

Related

[GUIDE] How to downgrade 1.7x/1.8x/2.x to 1.32.405.6

DO NOT USE THIS IF YOUR PHONE CAME WITH GINGERBREAD Or newer Software. Use the Ace Hack Kit for DHD
How to downgrade to 1.32.405.6 WWE
HTC - Quietly S-OFF. Again.
About:
The problems started when HTC released their 1.72.405.3 OTA update. That update could not be rooted, and many people got stuck in stock roms. Now a downgrade method has arrived! After this process, you can use any root (+ S-OFF) method you want. Basically your device will be just like any other Desire HD with older build version. Downgrading will completely reset your device to factory defaults, so remember to back up all important data (such as contacts, game saves and sms messages).
System requirements:
HTC Sync (or ADB drivers)
Desire HD with build number 1.72 or higher
[Warning] Telus DHDs may lose sound because the 1.32.405.6 is not fully compatible with the sound chip. Just start using a custom ROM, and it will work fine.
How to downgrade:
Section 1
Disable any antivirus software
If you have a branded / regional (like Indian or Vodaphone) device, you have to make a Goldcard. Use "mmc2" instead of "mmc1"!!
Download the attached file and extract it
Get stock 1.32 PD98IMG.zip ROM, mirror
Put the PD98IMG.zip into your SD card. Do not put it into a folder, and do not extract it.
Click to expand...
Click to collapse
Section 2a [For Froyo ROMs, 1.7x and 1.8x]
Connect Desire HD to a computer. Charge only, USB Debugging enabled!
Open up a cmd and go to Downgrade folder, execute commands:
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
Click to expand...
Click to collapse
Section 2b [For Gingerbread ROMs, 2.x]
Connect Desire HD to a computer. Charge only, USB Debugging enabled!
Open up a cmd and go to Downgrade folder, execute commands:
Code:
adb push misc_version /data/local/tmp
adb push fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
./data/local/tmp/fre3vo -debug -start FBB00000 -end FFFFFFFF
Click to expand...
Click to collapse
Section 3
If you got "#" in the result, you have temporary root! Proceed with commands:
Code:
cd /data/local/tmp
./misc_version -s 1.31.405.6
Close the CMD. Reboot while holding volume down, it will go to the bootloader
Follow the instructions (start the update)
Done. You can now click my thanks button! Proceed with old S-OFF methods, and remove the PD98IMG.zip from your SD. I recommend Radio S-OFF for new users.
Click to expand...
Click to collapse
Big thanks: Scotty2, Guhl and the fre3vo team
Downloadcount for Downgrade package v1 is 15808, and for v2 it is 32012.

FAQ:
Q: Will I lose all my settings and applications?
- Yes, so make a backup with MyBackup Pro.
Q: I have done Radio S-OFF and SuperCID, do I need this?
- No, with those you do not need this kind of trickery.
Q: I have flashed a custom ROM with e.g. 1.84 build number, do I need this?
- No, with ClockworkMod you can jump between builds freely.
Q: It says '#' but I still cannot use root applications!
- That is normal, this method only gives root in command line. Just go ahead and downgrade.
Q: Is my phone Froyo or Gingerbread?
- Check it in Settings -> About -> Software information -> Android version. 2.2 is Froyo and 2.3 is Gingerbread.
Q: How do I navigate to downgrade folder?
- You can read this short and easy explanation.
Click to expand...
Click to collapse
Troubleshooting:
- "Main version is older"? You did not type everything correctly. Please try it again and see if any errors come up.
- "Error opening backup file"? You did not use "Charge only" -connection, or your SD card is faulty.
- "CID mismatch/CID incorrect"? Your device is branded. Just make a Goldcard, put the PD98IMG.zip to the card again and go to the bootloader.
- "Model ID incorrect"? Some Telus DHDs get this, just make a Goldcard.
- "Failed to set prot mask (Inappropriate ioctl for device)"? Use Gingerbread method to downgrade.
- Zip will not load in bootloader? Format your SD card to FAT32, no quick format! You can also try another SD.
- Problems while making Goldcard? See this post.
- PD98IMG.zip md5sum is: C3D244A9F056E48EE3851A14FF52204C
Click to expand...
Click to collapse
If you like my work, please consider: (or just hit the thanks button )

Am I missing something or is it your link that just ain't there ?? lol

mcnob said:
Am I missing something or is it your link that just ain't there ?? lol
Click to expand...
Click to collapse
He's most likely updating it as we type - hate clutter so lets sit back and wait
http://forum.xda-developers.com/showpost.php?p=10428859&postcount=162

mcnob said:
Am I missing something or is it your link that just ain't there ?? lol
Click to expand...
Click to collapse
Look:
http://forum.xda-developers.com/showpost.php?p=10428115&postcount=54
but you should use DHD RUU (not desire Z) and lower version numer (since unbranded rootable version for DHD is 1.32.405.6)

Great work to everyone involved, now finally those lame "root doesn't work" posts will vanish

Excellent
So has any one tried it?

Got temp root trying to flash old ruu...lets see

I have temproot working. Currently downloading the RUU file on my REALLY slow internet...
I think there is a couple of small errors?
cd /data/local/tmp
./misc-version -s 1.31.405.3
should be
cd /data/local/tmp/
./misc_version -s 1.31.405.3
also, the psneuter is a .txt file, just remove the .txt extension to use the file.

robE9 said:
Got temp root trying to flash old ruu...lets see
Click to expand...
Click to collapse
Second confirmation for temp root but I've ran out of time to flash RUU

"So, rebooted in bootloader, loaded pd98img.zip....checked it but after says Main Version is older ! Update Fail ! Press power to reboot.
Any ideeas to try ?

Once i am home again I shall donate a crate of beer to the team!!

BlackTigerX said:
Great work to everyone involved, now finally those lame "root doesn't work" posts will vanish
Click to expand...
Click to collapse
You still will not have permanent root of 1.72/1.75! but this does allow you to downgrade and attain root on older Firmware

robE9 said:
"So, rebooted in bootloader, loaded pd98img.zip....checked it but after says Main Version is older ! Update Fail ! Press power to reboot.
Any ideeas to try ?
Click to expand...
Click to collapse
Did you get #, and did you run the misc_version executable? Did you write the version number correctly there?
ghostofcain said:
You still will not have root of 1.72/1.75! but this does allow you to downgrade and attain root on older Firmware
Click to expand...
Click to collapse
That is right. The psneuter gives temporary root, but as scotty2 said, it kind of shoots the current rom in the head while doing that..

i tried again with _ instead of - at version and now its updating hope will be ok

.. PD98IMG.zip to apply the file gives me an error
View attachment 483907
Any ideas?. Thanks!

Is it possible to flash the PD98IMG without using an SD card?
My DHD bricked mine http://forum.xda-developers.com/showthread.php?t=895593

apside said:
.. PD98IMG.zip to apply the file gives me an error
Any ideas?. Thanks!
Click to expand...
Click to collapse
What error? I cannot find error in that screenshot.
xdario said:
Is it possible to flash the PD98IMG without using an SD card?
My DHD bricked mine http://forum.xda-developers.com/showthread.php?t=895593
Click to expand...
Click to collapse
The RUU itself might work, but I would not bet on it. Just get a new SD.

apside said:
.. PD98IMG.zip to apply the file gives me an error
View attachment 483907
Any ideas?. Thanks!
Click to expand...
Click to collapse
dont write "reboot bootloader" just reboot by power buton and press down the volume button until you are in bootloader
Btw the downgrade was succesfull, i just rooted with visionary thx guys a lot :X

at me work fine

I'm waiting for Hboot 0.98.0002 S-OFF

My Desier S hboot is 0.98.0002,so I can't s-off my decive
please help me...thx...
PS:my RUU is 1.47......so http://forum.xda-developers.com/showthread.php?t=1173083 can't used...

Evilier said:
My Desier S hboot is 0.98.0002,so I can't s-off my decive
please help me...thx...
PS:my RUU is 1.47......so http://forum.xda-developers.com/showthread.php?t=1173083 can't used...
Click to expand...
Click to collapse
u need to use search button... its a yellow thing up

Evilier said:
My Desier S hboot is 0.98.0002,so I can't s-off my decive
please help me...thx...
PS:my RUU is 1.47......so http://forum.xda-developers.com/showthread.php?t=1173083 can't used...
Click to expand...
Click to collapse
Hi, you might wanna try to flash this ROM to get back to old Hboot
http://www.4shared.com/file/bAebAgjC/RUU_Saga_HTC_Europe_1284011_Ra.html
It may or may not work on your s-on device but worth to try.

ofc he can downgrade with s-on
i did the same, he is just too lazy to use search function

Blezz said:
ofc he can downgrade with s-on
i did the same, he is just too lazy to use search function
Click to expand...
Click to collapse
actually he cant with his radio the temp root using gingerbreak dosent work, so there is no way to downgrade, i have tried every method and have had no luck, but i am sure alpharevx will sort it out eventually

Blezz said:
ofc he can downgrade with s-on
i did the same, he is just too lazy to use search function
Click to expand...
Click to collapse
People like this annoy me. As the OP already stated, he can't downgrade with s-on. Just because YOU did, doesn't mean he can. His stock RUU is too new (1.47) and there is no exploit to get temp root yet for this RUU, so downgrading is not possible.
Agreed, he should use the search function, there are about 3 threads of people trying to s-off their 1.47 device. But in his defence, all 3 of those threads are filled with morons like yourself telling people they can do it. Newsflash, you can't.... yet

I'm waiting to :-(
Hope it will no take very long time ahah

Evilier said:
My Desier S hboot is 0.98.0002,so I can't s-off my decive
please help me...thx...
PS:my RUU is 1.47......so http://forum.xda-developers.com/showthread.php?t=1173083 can't used...
Click to expand...
Click to collapse
Hi Evilier.
I just have few questions regarding to your phone, since its one of the "new" software, do you have the Wi-Fi Death Grip? More info can be found here.
And can you tell me which of the v1.47 do you have? Which country I mean.
Well this is going to be a stretch, since you're on the "new" phones software version, can you update/RUU to the latest (RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.0 85AU_3805.06.02.03_M_release_199476_signed)? Then double check if you still have the so could Wi-Fi Death Grip. Thanks a lot.

+ 1 for a method to unlock/root the "new " firmware. Please devs do your magic
Sent from my HTC Desire S using XDA App

davidreece said:
actually he cant with his radio the temp root using gingerbreak dosent work, so there is no way to downgrade, i have tried every method and have had no luck, but i am sure alpharevx will sort it out eventually
Click to expand...
Click to collapse
Davidreece, I'm on the same wagon here... Tried every thinkable method but simply no joy
Did anyone of you test the ROM suggested by Yungyeh?

jakmor said:
Davidreece, I'm on the same wagon here... Tried every thinkable method but simply no joy
Did anyone of you test the ROM suggested by Yungyeh?
Click to expand...
Click to collapse
i have actually managed it i used fre3vo from this thread
http://forum.xda-developers.com/showthread.php?t=1150006
but i combined the instructions with post 4 from the downgrade thread ( part where you have to chmod the version file then change the version.
first download http://forum.xda-developers.com/attachment.php?attachmentid=591335&d=1304969547
and also this
http://forum.xda-developers.com/attachment.php?attachmentid=661246&d=1311240968
extract them to the same folder then open a command prompt in that folder and follow these instructions
Instructions:
1. adb push fre3vo /data/local/tmp
2. adb push misc_version /data/local/tmp
3. adb shell chmod 777 /data/local/tmp/fre3vo
4. adb shell chmod 777 /data/local/tmp/misc_version
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt.
run 'adb shell' and you should have a '#' prompt instead of $
6. cd /data/local/tmp
./misc_version -s 1.27.405.6
From here you can then install the update/downgrade from the ruu exe for your phone from http://forum.xda-developers.com/showthread.php?t=1002506
then you can just follow the alpharevx instructions as normal because you will be able to run gingerbreak etc, this works on the latest updates as i couldnt use gingerbreak to downgrade due to the vodafone uk update and i am now on a custom rom and s offed
hope this helps everyone.

davidreece said:
i have actually managed it i used fre3vo from this thread
http://forum.xda-developers.com/showthread.php?t=1150006
but i combined the instructions with post 4 from the downgrade thread ( part where you have to chmod the version file then change the version.
first download http://forum.xda-developers.com/attachment.php?attachmentid=591335&d=1304969547
and also this
http://forum.xda-developers.com/attachment.php?attachmentid=661246&d=1311240968
extract them to the same folder then open a command prompt in that folder and follow these instructions
Instructions:
1. adb push fre3vo /data/local/tmp
2. adb push misc_version /data/local/tmp
3. adb shell chmod 777 /data/local/tmp/fre3vo
4. adb shell chmod 777 /data/local/tmp/misc_version
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt.
run 'adb shell' and you should have a '#' prompt instead of $
6. cd /data/local/tmp
./misc_version -s 1.27.405.6
From here you can then install the update/downgrade from the ruu exe for your phone from http://forum.xda-developers.com/showthread.php?t=1002506
then you can just follow the alpharevx instructions as normal because you will be able to run gingerbreak etc, this works on the latest updates as i couldnt use gingerbreak to downgrade due to the vodafone uk update and i am now on a custom rom and s offed
hope this helps everyone.
Click to expand...
Click to collapse
This part got me all excited in the pants a little. I tried it, but the fre3vo script is hanging at "Frame Buffer handle: 4" for about 5 minutes now.
I will try factory reset on my 1.47 RUU and try once more.
@davidreece: can you confirm what RUU version you had when this worked for you?

davidreece said:
i have actually managed it i used fre3vo from this thread
http://forum.xda-developers.com/showthread.php?t=1150006
but i combined the instructions with post 4 from the downgrade thread ( part where you have to chmod the version file then change the version.
first download http://forum.xda-developers.com/attachment.php?attachmentid=591335&d=1304969547
and also this
http://forum.xda-developers.com/attachment.php?attachmentid=661246&d=1311240968
extract them to the same folder then open a command prompt in that folder and follow these instructions
Instructions:
1. adb push fre3vo /data/local/tmp
2. adb push misc_version /data/local/tmp
3. adb shell chmod 777 /data/local/tmp/fre3vo
4. adb shell chmod 777 /data/local/tmp/misc_version
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt.
run 'adb shell' and you should have a '#' prompt instead of $
6. cd /data/local/tmp
./misc_version -s 1.27.405.6
From here you can then install the update/downgrade from the ruu exe for your phone from http://forum.xda-developers.com/showthread.php?t=1002506
then you can just follow the alpharevx instructions as normal because you will be able to run gingerbreak etc, this works on the latest updates as i couldnt use gingerbreak to downgrade due to the vodafone uk update and i am now on a custom rom and s offed
hope this helps everyone.
Click to expand...
Click to collapse
Thanks for the tip. But I'm a little confused at step 5. I'm the ultimate Android noob so please excuse my stupidity, but what exactly did the step mean by "Run the binary via 'adb shell /data/local/tmp/fre3vo"?
How exactly does one "run the binary? I typed in the 'adb shell /data/local/tmp/fre3vo' command for this step and I get
fre3vo by #teamwin
Please wait...
At this point I can't type anything and actually waited...but after about 15 minutes, nothing is happening. Could you point me in the right direction?

vankox said:
Thanks for the tip. But I'm a little confused at step 5. I'm the ultimate Android noob so please excuse my stupidity, but what exactly did the step mean by "Run the binary via 'adb shell /data/local/tmp/fre3vo"?
How exactly does one "run the binary? I typed in the 'adb shell /data/local/tmp/fre3vo' command for this step and I get
fre3vo by #teamwin
Please wait...
At this point I can't type anything and actually waited...but after about 15 minutes, nothing is happening. Could you point me in the right direction?
Click to expand...
Click to collapse
You appear to be doing exactly the correct thing...just be patient...(although I admit it does say a few minutes).
See this refined guide....http://forum.xda-developers.com/showpost.php?p=16104882&postcount=16
I'd be tempted to reboot the phone and start at the beginning again, (although the first two steps may well error as the files will be already there - ignore that and proceed).

first of all many thanks for all the guides, secondly i've followed all the steps and everything works fine but when i run the .exe to actually downgrade it always says that i'm under 30% of phone charge (battery is fully loaded). I made a gold card and everything also... strange..

ratss123 said:
first of all many thanks for all the guides, secondly i've followed all the steps and everything works fine but when i run the .exe to actually downgrade it always says that i'm under 30% of phone charge (battery is fully loaded). I made a gold card and everything also... strange..
Click to expand...
Click to collapse
Just grasping at straws here....Try to fully charge the battery and then power down device and remove the battery, allow both the battery and the device to cool down.
Try again.
Now, again I'm not sure but a full factory reset from HBOOT may remove the existing battery stats....so you could try that?

ben_pyett said:
Just grasping at straws here....Try to fully charge the battery and then power down device and remove the battery, allow both the battery and the device to cool down.
Try again.
Now, again I'm not sure but a full factory reset from HBOOT may remove the existing battery stats....so you could try that?
Click to expand...
Click to collapse
uhm didn't work also with factory reset.... keeps saying it's less then 30%..
lol so near to the s-off and then it doesn't work for something like that!!

Worked like a charm now s- off again running pre rooted 1.47.401 European Rom many thanks
Sent from my HTC Desire S using XDA App

ratss123 said:
uhm didn't work also with factory reset.... keeps saying it's less then 30%..
lol so near to the s-off and then it doesn't work for something like that!!
Click to expand...
Click to collapse
do you know anyone with the same device so that you could try to swap batteries for the update in case your has failed?

ben_pyett said:
do you know anyone with the same device so that you could try to swap batteries for the update in case your has failed?
Click to expand...
Click to collapse
no sadly i don't, tried to run it also on another pc but it's the same.. there is also another thing, few days ago i tried to run the .exe hoping that it would downgrade, later i found out that i've got hboot 92 so i waited for a new method.. When i tried I didn't get any error message, just thath obviusy it couldn't downgrade... today i tried again and I keep gettint low battery....

[Q] Help with S-Off and Rooting my HTC Merge

I understand there are other threads about this however I do feel my situation is either unique or I've missed something in the other threads.
I've got an HTC Merge through US Cellular. I upgraded to Gingerbread 2.3.4 as soon as it was released through USC's website. Now I'd like to root and all that other stuff.
1.: I didn't S-off before the update. Does anyone know how to properly S-off 2.3.4 Gingerbread on a USC HTC Merge?
2.: I've never rooted a phone before, but I'm pretty sure I've read about it plenty and I'm ready to give it a shot. What's the best way to do this on my current phone?
3.: What are some good modded ROMs available for this device, if any exist at all? I've been interesting in Cyanogen Mod but as far as I've seen it's not supported on the Merge yet.
If anyone can assist me I'd appreciate it greatly. Thanks in advance. =)

if you have adb set up and working,and have some knowledge of it,you can use drellisdees directions in this post,along with the new zergRush temp root tool from alpharev/unrevoked. donate to them both if it works for you.
download the zergRush tool from this post:http://forum.xda-developers.com/showthread.php?t=1296916 and place the file thats inside the .zip into the same folder as your other exploits(tools or platform-tools in ost cases)
below is his post,modified slightly,with the zergRush directions(bold) in place of the originaly froyo directions.
i also removed the parts about downloading your carriers RUU,and backing up your system for vzw since you said you were USC.
assuming you want to remain on rooted GB,just use the same RUU that you used to upgrade at the end where it says to run your carriers RUU.
drellisdee said:
Well, ask and you shall receive!!!
I got s-off on vzw merge. However, altell or USC ones it will require supercid or a goldcard to flash ruu from another carrier.
Tested and working CWM recovery I made for merge and latest radio hboot zips after s-off.
You must verify all Md5sums after downloading to computer (don't even think about downloading on phone) before flashing or risk a brick!!!!! Windows users can get one here & linux users can just type md5sum (name of file) into terminal.
Md5's
8cd1ca796e755b6b72f35e5686dc973a PD42IMG_cw_recovery_gnm.zip
97e35ecc802081b67e27d6cc8323cf81 PD42IMG_radio_1.08.00.320.zip
cc2e7c077fddd017d7b0db614661c535 PD42IMG_1.49.605.1_no_system.zip
4fe37c64b21d1d4542a801779fad5c57 misc-downgrade.img
6d37a0f3526295ebb779f4465a328c96 rom.zip (leaked 1.23.605.1)
http://www.mediafire.com/file/6b2jatt0445h41g/PD42IMG_cw_recovery_gnm.zip
http://www.mediafire.com/file/gbayon7dkmaq98i/PD42IMG_radio_1.08.00.320.zip
I am exploring a goldcard method that will allow flashing of the vzw ruu 1.23.605.1 that can be s-off'ed to allow other carriers merge's to be able to downgrade to s-off.
How to on s-off will be coming soon .... stay posted
Ok how to guide for s-off.
Files needed:
MISCIMG Downgrade http://www.mediafire.com/file/f7c3boee7ixa3i9/misc-downgrade.img
VZW leak 1.23.605.1 ruu.zip http://forum.xda-developers.com/showpost.php?p=8237592&postcount=2
Exploits http://www.mediafire.com/file/e9w92clv6l71el3/exp.zip
HEADS UP: This guide will reflash your phone and cause loss of all non-backed up data
Goldcard is required for ALL NON-VZW phones
Read how to make one here : http://www.mikesouthby.co.uk/2010/0...yo-official-ota-for-network-branded-handsets/
I used the app goldcard helper from market and if you use it skip right to the step of "Go to this page and enter this new number into the SD Card Serial (CID) field" and enter the output of the sdcard cid for mmc2 into the goldcard generator site.
After goldcard is made via directions in link above or if on vzw branded device you can skip the goldcard part. Next rename the vzw leak ruu.zip to PD42IMG.zip and place it on root of sdcard.
Next from dir you downloaded stuff to unzip the exp.zip and copy the exp folder to your android sdk platform-tools dir (if using windows) linux users should have adb in path so this shouldn't be needed just open terminal from download dir. Make sure the phone is in usb mode charge-only from this point on with usb-debugging turned on (settings/applications/development).
Code:
[B]adb push zergRush /data/local/
adb shell[/B] [I]this will change your promt to a $[/I]
[B]chmod 755 /data/local/zergRush
/data/local/zergRush[/B]
Next we backup our existing misc partition.
Code:
adb shell
dd if=/dev/block/mmcblk0p17 of=/sdcard/misc-stock.img bs=4096
/data/local/busybox md5sum /sdcard/misc-stock.img
/data/local/busybox md5sum /dev/block/mmcblk0p17
Make sure the md5sum of the misc-stock.img matches the one from /dev/block/mmcblk0p17
Next we use temp root to flash a misc.img that I hex edited to allow downgrading FW. misc-downgrade.img needs to be in platform-tools dir for windows users.
Code:
adb push misc-downgrade.img /sdcard/
adb shell
dd if=/sdcard/misc-downgrade.img of=/dev/block/mmcblk0p17
sync
Next power off your phone and boot it holding vol_dn + power.
Let the PD42IMG.zip complete ( will do hboot + radio then self reboot and restart to finish the rest)
Once rebooted into the 1.23.605.1 firmware
Code:
adb push exp /data/local
adb shell
chmod 0755 /data/local/psneuter
chmod 0755 /data/local/wpthis
chmod 0755 /data/local/gfree
/data/local/psneuter (to get temp root again)
adb shell
/data/local/wpthis (to disable emmc write protect)
/data/local/gfree -f (this will supercid, simunlock, and s-off phone)
rm /sdcard/PD42IMG.zip (remove/delete the leaked FW so hboot wont load it again)
Reboot into bootloader and verify you have s-off
If so reboot into android and use your carrier's RUU to replace your FW. You will not lose s-off. If on vzw unzip the PD42IMG_1.49.605.1_no_system.zip and add your system.img from your memory card we dumped earlier to the zip. Rezip and rename to PD42IMG.zip and place on root of sdcard and reboot into hboot to flash it just like we did earlier. This will restore the shipped 1.49.605.1 hboot, radio, boot.img, stock recovery.img, and system.img.
After you have upgraded backup you can use the clockwork recovery.img I made and rename it to PD42IMG.zip (make sure to delete the old PD42IMG.zip on your sdcard) and place it on root of sdcard and flash via hboot just like the other PD42IMG.zip's. Then you will have s-off and a custom recovery. Remember to remove/rename/move the PD42IMG.zips when done as they will flash if you enter hboot. Recovery can be entered via bootloader by picking recovery or via "adb reboot recovery".
Flashing this zip via clockwork recovery will install root (su & superuser.apk), busybox & symlink applets, flash & dump image. signed_merge_su_eng_toolkit.zip
After you have root on your release firmware:
The following commands will restore your stock misc.img
from a root # shell: (will need to type su after adb shell and accept superuser pop-up)
Code:
adb shell
dd if=/sdcard/misc-stock.img of=/dev/block/mmcblk0p17
sync
Special thanks to Scotty2 & Tmzt who wrote and developed the wpthis & gfree exploits for the G2 without these s-off for lexikon wouldn't have been possible for me.
My donation link is below if anyone wants to toss me a donation. Took me about a week to port RA recovery to merge only to fail as it had issues then to setup the board files for lexikon for cm7 to do a clockwork recovery and not to mention dumping partitons and working on the s-off stuff and goldcard.
Click to expand...
Click to collapse

I got as far as the /data/local/zergRush and got this error:
[-] Cannot copy boomsh. : Permission denied.
adb push zergRush /data/local/
adb shell this will change your promt to a $
chmod 755 /data/local/zergRush
/data/local/zergRush
Any ideas?
Thanks

kclive said:
I got as far as the /data/local/zergRush and got this error:
[-] Cannot copy boomsh. : Permission denied.
adb push zergRush /data/local/
adb shell this will change your promt to a $
chmod 755 /data/local/zergRush
/data/local/zergRush
Any ideas?
Thanks
Click to expand...
Click to collapse
that error comes from running zergrush twice. http://androidforums.com/merge-all-...simunlock-supercid-htc-merge.html#post3522248

pls how can i run this commands with miniadb, i dont hav access to the whole android sdk tool...and besides, the zergrush binary link above aint workin..any other alternative dload link pls??

akins47 said:
pls how can i run this commands with miniadb, i dont hav access to the whole android sdk tool...and besides, the zergrush binary link above aint workin..any other alternative dload link pls??
Click to expand...
Click to collapse
zergrush is broken with newer builds. fre3vo worked for some. i would recomend you htcdev unlock in order to gain root access for downgrade.
follow directions here to htcdev unlock:
http://androidforums.com/merge-all-things-root/635459-unlock-htcdev.html
then follow directions here:
http://androidforums.com/merge-all-things-root/434029-root-s-off-simunlock-supercid-htc-merge.html
using the "htcdev" step 5 in post#2

New downgrade for J Butterfly 1.36.970.1 > 1.15.970.1

There is a new downgrade option released for firmware 1.36.970.1 to 1.15.970.1.
However my Japanese is not perfect and my understanding of hacking is very weak.
If there is someone more in the know could understand what the steps to take are that would be great.
Good luck all. I hope someone can make a guide as well to help other out.
I'll try my best as well.
Here is the link.
http://htcsoku.info/htcsokudev-news/au-deluxe-136to115-downgrade/

link to RUU 1.15.970.1 is dead

I have successfully downgraded my J Butterfly based on those instructions. I have simplified it because the original instructions seems to be overly complicated. It involved tricking a system app with root privileges to run an custom command, only to use run_root_shell later anyway.
I also did not use the run_root_shell supplied by the guide, instead I compiled a newer version direct from the source: https://github.com/android-rooting-tools/android_run_root_shell
You'll need
1. revone.dna-0.2.1
http://forum.xda-developers.com/showthread.php?t=2314582
2. A newer build of run_root_shell (attached)
3. 1.15 ROM: PL99IMG_DLX_WLJ_JB_45_KDDI_JP_1.15.970.1_R_Radio_1.00.10.1127_3_NV_2.28_01C_release_signed.zip
(renamed to rom.zip in this tutorial)
https://mega.co.nz/#!jQtQ0BLS!279lf8k4sbKPTmWHTsPg6hbaGDatpq3xGGv4aE8N1h4
4. firmware.zip extracted from OTA_DLX_WLJ_JB_45_KDDI_JP_1.36.970.1-1.29.970.1_release_330380g3nfgypcfojku8a9.zip:
http://kie.nu/1urK
5. adb and fastboot
6. An HEX editor such as XVI32
THIS WILL WIPE YOUR USER DATA, BACKUP ALL YOUR STUFF FIRST
Steps:
1. Run the following commands in command prompt to push files required by run_root_shell to device:
adb push run_root_shell /data/local/tmp/
adb push device.db /data/local/tmp/
2. Run in command prompt:
adb shell
to access the shell on your device. Run the following commands to run run_root_shell, disregard messages about HTL21 not supported. You will be returned to the command line but with a hash (#) instead of a dollar sign, that means you have temprooted.
cd /data/local/tmp/
chmod 755 *
./run_root_shell
3. Run these commands on device shell:
chmod 666 /dev/msm_acdb
dd if=/dev/block/mmcblk0p21 of=/sdcard/p21
4. Run in another command prompt:
adb pull /sdcard/p21
to pull the file p21 from device, then open it with an HEX editor. Refer to the images on the original Japanese tutorial, change the version number near "ClearAutoImage" to 1.00.000.0 and save the file as p21mod.
5. Push the modified file back to the device by running in command prompt:
adb push p21mod /sdcard/p21mod
6. Back to the device shell, run these commands to write the modifications to the device and reboot into bootloader.
dd if=/sdcard/p21mod of=/dev/block/mmcblk0p21
reboot bootloader
7. Run in command prompt:
fastboot oem rebootRUU
to boot to RUU.
8. Run in command prompt:
fastboot flash zip firmware.zip
and it willl fail with this error: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
9. Run in command prompt:
fastboot flash zip rom.zip
to flash 1.15 ROM. It should take around 6 minutes. This wipes your user data.
10. In command prompt, push run_root_shell to device again. Also push revone.dna-0.2.1 to device.
adb push run_root_shell /data/local/tmp/
adb push device.db /data/local/tmp/
adb push revone.dna-0.2.1 /data/local/tmp/revone.dna
11. Refer to step 2 to temproot again.
12. Run revone.dna on device shell:
./revone.dna -P
and you should see "revone successful - please reboot to continue".
13. Reboot and repeat step 12 again, this time you should see "revone successful - no need to reboot".
14. Run on device shell:
./revone.dna -s 0 -u
and you should see "revone successful".
15. ???
16. PROFIT!
You have now successfully S-OFFed and may proceed to unlocking and SuperCIDing your device as usual.

Corrupted
Phil_123 said:
3. 1.15 ROM: PL99IMG_DLX_WLJ_JB_45_KDDI_JP_1.15.970.1_R_Radio_1.00.10.1127_3_NV_2.28_01C_release_signed.zip
(renamed to rom.zip in this tutorial)
.
Click to expand...
Click to collapse
I have downloaded this file twice and found it corrupted. Can't open it so i can't uncompress and reach firmware.zip either.
:crying:
Could you reupload it?

corrupted
darky4e said:
I have downloaded this file twice and found it corrupted. Can't open it so i can't uncompress and reach firmware.zip either.
:crying:
Could you reupload it?
Click to expand...
Click to collapse
I have "fixed" it by Zip2Fix and made a zip file what can be extracted. But the two zip file size isn't match so i guess its isn't the same and there isn't any firmware.zip in the nem zip file so i guess the program extracted everything.
I have read that some people succesfully used corrupted ruu, and it's made corrupted by reason. I will read more about it and try to find a correct firmware.zip for the method. If you could help me in any means it would be great.

darky4e said:
I have "fixed" it by Zip2Fix and made a zip file what can be extracted. But the two zip file size isn't match so i guess its isn't the same and there isn't any firmware.zip in the nem zip file so i guess the program extracted everything.
I have read that some people succesfully used corrupted ruu, and it's made corrupted by reason. I will read more about it and try to find a correct firmware.zip for the method. If you could help me in any means it would be great.
Click to expand...
Click to collapse
My bad, my instructions were wrong. I wrote them only after successfully doing it myself, I must have mixed some things up while writing.
I looked at the original Japanese guide again, the firmware.zip is in OTA_DLX_WLJ_JB_45_KDDI_JP_1.36.970.1-1.29.970.1_release_330380g3nfgypcfojku8a9.zip and can be downloaded here:
http://kie.nu/1urK

Phil_123 said:
My bad, my instructions were wrong. I wrote them only after successfully doing it myself, I must have mixed some things up while writing.
I looked at the original Japanese guide again, the firmware.zip is in OTA_DLX_WLJ_JB_45_KDDI_JP_1.36.970.1-1.29.970.1_release_330380g3nfgypcfojku8a9.zip and can be downloaded here:
http://kie.nu/1urK
Click to expand...
Click to collapse
Thank you very much! I have succesfully downgraded the phone! Thx for the instructions again!!

run_root_shell and revone.dna-0.2.1 work with HTC Butterfly kddi HTL21 with HBOOT 1.41 ? I'am stuck on run_root_shell and it say's "Error No such file or directory" when I use the command in adb "$ ./run_root_shell"
what can I do ?

dfani511 said:
run_root_shell and revone.dna-0.2.1 work with HTC Butterfly kddi HTL21 with HBOOT 1.41 ? I'am stuck on run_root_shell and it say's "Error No such file or directory" when I use the command in adb "$ ./run_root_shell"
what can I do ?
Click to expand...
Click to collapse
This method can only be used for the software version of the 1.36.970.1, I think your software version 1.39.970.1 is not SOFF

i have 1.39.970.3 ?????????????
OTA ??????????

Nice share, im succesfully unlock soff with this way
Sent from my MITO_A10 using XDA Free mobile app

"htl21 1399703 firmware" I want up because it cannot find the file.

RUU File for RADIO-26.17.14.11_M

Hi,
I have the HTC Inspire 4g with:
Software #: 3.20.502.52 710RD
Android Version 2.3.5
HTC Sense 3.0
Baseband version: 12.69a.60.29u_26.17.14.11_M
I have unlocked the bootloader using htcdev and have successfully rooted the the device but i'm still S-ON. I have tried installing some custom ROMs however after flashing the device did not boot. I understand that I have to flash the boot.img file located in the .zip file of the custome ROM. That I know how to do... My concern is that I want to try out some ROMs but as a precaution I would like to have the stock RUU file for the type device I have should I need to restore it.
I did create a backup of my ROM and have used it previously to restore the phone after installing the custom roms that haven't boot. I just want to know if I flash the boot.img file will a restore bring it back to where it was before the flash or do i need the RUU file to restore stock?
If the later please advice where I can find that particular file as I've searched but can't seem to find the one to use.
Thanks a million.
360fifa

360fifa said:
Hi,
I have the HTC Inspire 4g with:
Software #: 3.20.502.52 710RD
Android Version 2.3.5
HTC Sense 3.0
Baseband version: 12.69a.60.29u_26.17.14.11_M
I have unlocked the bootloader using htcdev and have successfully rooted the the device but i'm still S-ON. I have tried installing some custom ROMs however after flashing the device did not boot. I understand that I have to flash the boot.img file located in the .zip file of the custome ROM. That I know how to do... My concern is that I want to try out some ROMs but as a precaution I would like to have the stock RUU file for the type device I have should I need to restore it.
I did create a backup of my ROM and have used it previously to restore the phone after installing the custom roms that haven't boot. I just want to know if I flash the boot.img file will a restore bring it back to where it was before the flash or do i need the RUU file to restore stock?
If the later please advice where I can find that particular file as I've searched but can't seem to find the one to use.
Thanks a million.
360fifa
Click to expand...
Click to collapse
RUU 3.20.502.52

Thank you kindly for taking the time to respond and also help.

Hi Gizmoe,
is there a rooted and s-off RUU file I could use as well?
Thanks again..

360fifa said:
Hi Gizmoe,
is there a rooted and s-off RUU file I could use as well?
Thanks again..
Click to expand...
Click to collapse
RUU 's can not be modified. You will not lose s off however by running an ruu. After you run ruu just pd98img a recovery and flash away.

Gizmoe said:
RUU 's can not be modified. You will not lose s off however by running an ruu. After you run ruu just pd98img a recovery and flash away.
Click to expand...
Click to collapse
So are you saying that I would need to unlock the bootloader again then following the same steps I have now? I had the impression based off could threads I've read that there's a way to root the device while gaining S-OFF that will allow me to avoid having to manually flash the boot.IMG everytime i install a custom rom. If there's a thread I can read or a guide to follow please provide a link so that I can proceed. Oh, does all the pd98img file the same?
Thanks again.
360fifa

360fifa said:
So are you saying that I would need to unlock the bootloader again then following the same steps I have now? I had the impression based off could threads I've read that there's a way to root the device while gaining S-OFF that will allow me to avoid having to manually flash the boot.IMG everytime i install a custom rom. If there's a thread I can read or a guide to follow please provide a link so that I can proceed. Oh, does all the pd98img file the same?
Thanks again.
360fifa
Click to expand...
Click to collapse
Yeah that's right. Your not s off. Well here is the only method left for the inspire. It may be a bit intimidating but really isn't that hard. Here is link.
http://tau.shadowchild.nl/attn1/?cat=6

Gizmoe said:
Yeah that's right. Your not s off. Well here is the only method left for the inspire. It may be a bit intimidating but really isn't that hard. Here is link.
Click to expand...
Click to collapse
Your're right very intimidating, however I'm willing to try my only concern is what is dd highlighted below "High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img"?
Also i navigated to the folder on my device however it doesn't show any boot.img file. Just a init.rc file. Could you explain just this part of it please?
Thanks again,
360fifa

360fifa said:
Your're right very intimidating, however I'm willing to try my only concern is what is dd highlighted below "High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img"?
Also i navigated to the folder on my device however it doesn't show any boot.img file. Just a init.rc file. Could you explain just this part of it please?
Thanks again,
360fifa
Click to expand...
Click to collapse
DD is copy and convert. It will copy boot files and convert it into boot.img. Use adb shell to do it as shell works within phone directories. Then pull it from pc using adb pull. He is giving you the exact adb commands to do both.
Code:
adb shell
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img

Gizmoe said:
DD is copy and convert. It will copy boot files and convert it into boot.img. Use adb shell to do it as shell works within phone directories. Then pull it from pc using adb pull. He is giving you the exact adb commands to do both.
Code:
adb shell
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img
Click to expand...
Click to collapse
Lol... I figured those were the commands to use, was just wondering what dd stand for.. ( copy and convert ). So let me see if i understand whats happening in the code.
So firstly I need to have the the HTC drivers installed and have the Android SDK on the root of c drive. Basically the same folder used when I unlocked to bootloader. In that folder I have the adb files, should I also add the files listed in the zip file he provided? If so let me explain the code, if no please shed some light.
So adb shell starts the emulator with the device
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot will copy and convert the mmcblk0p22 file if it is found in the /dev/block folder on the device and place it to the /data/local/tmp/ folder and call it boot.img
adb pull /data/local/tmp/boot.img I'm thinking that the computer is going to pull the boot.IMG file from the /data/local/tmp folder however where is it putting it? In the same folder that I started the command prompt from? That is the Android folder on my c drive?

360fifa said:
Lol... I figured those were the commands to use, was just wondering what dd stand for.. ( copy and convert ). So let me see if i understand whats happening in the code.
So firstly I need to have the the HTC drivers installed and have the Android SDK on the root of c drive. Basically the same folder used when I unlocked to bootloader. In that folder I have the adb files, should I also add the files listed in the zip file he provided? If so let me explain the code, if no please shed some light.
So adb shell starts the emulator with the device
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot will copy and convert the mmcblk0p22 file if it is found in the /dev/block folder on the device and place it to the /data/local/tmp/ folder and call it boot.img
adb pull /data/local/tmp/boot.img I'm thinking that the computer is going to pull the boot.IMG file from the /data/local/tmp folder however where is it putting it? In the same folder that I started the command prompt from? That is the Android folder on my c drive?
Click to expand...
Click to collapse
You will want to work out of the platform-tools directory.
Yes adb pull will always pull to your working directory unless another path is specified. Adb shell will need root. So if you type adb shell and don't see a # sign type su to get it. When done in adb shell you will need exit so you can pull to computer. If you had to take two steps to get a # prompt then you will type exit twice.

Gizmoe said:
You will want to work out of the platform-tools directory.
Yes adb pull will always pull to your working directory unless another path is specified. Adb shell will need root. So if you type adb shell and don't see a # sign type su to get it. When done in adb shell you will need exit so you can pull to computer. If you had to take two steps to get a # prompt then you will type exit twice.
Click to expand...
Click to collapse
Kool, thats the directory i'm referring to... I'm sure i'm already rooted. But your saying that when i send the command "adb shell" if I don't see the # sign then i should type su. Are you then saying that if I had to type su twice then I need to hit exit twice to pull to pc?
Oh before I forget should i run ruu before attempting this or remain as is? Also, do I need cmw recovery installed or can i remain on twrp 2.6.0.0?
Thanks again bro..
360fifa

360fifa said:
Kool, thats the directory i'm referring to... I'm sure i'm already rooted. But your saying that when i send the command "adb shell" if I don't see the # sign then i should type su. Are you then saying that if I had to type su twice then I need to hit exit twice to pull to pc?
Oh before I forget should i run ruu or remain as is?
Thanks again bro..
360fifa
Click to expand...
Click to collapse
Yes you would need to type su to see #. Adb shell root access works independently of phone root. It needs root access over adb which without an UN-secure boot img will need the su command. Exit for each level. Once for su and once for shell itself. You want to exit until you are back at Windows directory. Adb shell is at the phones root directory. The dd command is moving files within the phone, while Adb pull would be used to copy from phone to pc. I would not run that ruu if you are going to try and s off. I would run 2.47.502.7. Which I posted a link in the att stock Rom thread.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
http://forum.xda-developers.com/showthread.php?p=50027824

Gizmoe said:
Yes you would need to type su to see #. Adb shell root access works independently of phone root. It needs root access over adb which without an UN-secure boot img will need the su command. Exit for each level. Once for su and once for shell itself. You want to exit until you are back at Windows directory. Adb shell is at the phones root directory. The dd command is moving files within the phone, while Adb pull would be used to copy from phone to pc. I would not run that ruu if you are going to try and s off. I would run 2.47.502.7. Which I posted a link in the att stock Rom thread.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
http://forum.xda-developers.com/showthread.php?p=50027824
Click to expand...
Click to collapse
Do i need to run a ruu or can I proceed as is? If so u recommend running the 2.47.502.7 ruu before going thru the adb commands, y?
Thanks again..

360fifa said:
Do i need to run a ruu or can I proceed as is? If so u recommend running the 2.47.502.7 ruu before going thru the adb commands, y?
Thanks again..
Click to expand...
Click to collapse
Yes go ahead and proceed as is. You should not have any issues. If not successful then try ruu. You may not be able to run the older ruu if your bootloader is newer. Which in that case just run the newer one. I beleive I used this process on a phone with the newer software but the older works for sure.

Gizmoe said:
Yes go ahead and proceed as is. You should not have any issues. If not successful then try ruu. You may not be able to run the older ruu if your bootloader is newer. Which in that case just run the newer one. I beleive I used this process on a phone with the newer software but the older works for sure.
Click to expand...
Click to collapse
Gizmoe you have been very patient and very helpful i thank you a million times. If i encounter any other issues I'll definitely let you know.
Thanks again..
360fifa

360fifa said:
Gizmoe you have been very patient and very helpful i thank you a million times. If i encounter any other issues I'll definitely let you know.
Thanks again..
360fifa
Click to expand...
Click to collapse
I encountered an issue while trying to pull the boot.img file from /data/local/tmp/. The command used was adb pull /data/local/tmp/boot.img I then got a msg saying the adb is not a command, if I remove the adb and send the command with just pull it says pull is not a command.
If I exit su "#" it brings me to $ and if I send the command again it says that I don't have permission. Can you advise what I might be doing wrong? Oh, I got the mmcblk0p22 file to copy and convert into the boot.img file. I was able to see it using ES File explorer on my phone.
Do I need to go in fastboot usb, does unknown sources need to be checked?
Thanks again.

360fifa said:
I encountered an issue while trying to pull the boot.img file from /data/local/tmp/. The command used was adb pull /data/local/tmp/boot.img I then got a msg saying the adb is not a command, if I remove the adb and send the command with just pull it says pull is not a command.
If I exit su "#" it brings me to $ and if I send the command again it says that I don't have permission. Can you advise what I might be doing wrong? Oh, I got the mmcblk0p22 file to copy and convert into the boot.img file. I was able to see it using ES File explorer on my phone.
Do I need to go in fastboot usb, does unknown sources need to be checked?
Thanks again.
Click to expand...
Click to collapse
You need to exit one more time so you can see c prompt with your platform tools folder. Your still in shell therefore still in phone and not actually pulling to your pc. Only the pc uses Adb commands so you have to be at your platform tools folder. If you restart your phone temp empties too so if you can't see boot img anymore that's why.

Gizmoe said:
You need to exit one more time so you can see c prompt with your platform tools folder. Your still in shell therefore still in phone and not actually pulling to your pc. Only the pc uses Adb commands so you have to be at your platform tools folder. If you restart your phone temp empties too so if you can't see boot img anymore that's why.
Click to expand...
Click to collapse
Okay.. I am going to try that now, I swore I did that as well but lets see.

360fifa said:
Okay.. I am going to try that now, I swore I did that as well but lets see.
Click to expand...
Click to collapse
Here's what it said "failed to copy '/data/local/tmp/boot.img' to ' ./boot.img': Permission denied

Database Info

welcome