Database Info

[MOD] KENDON ROCKS boot.img with adb remount and rooted adb shell support

All credit goes the Kendon from villainrom he rocks my socks
If you want to be able to use adb with root permissions you need one of these boot.imgs. you use this at your own risk, no matter what! i assume you have adb working, if not, there are guides (also here on the site, might look for one later).
this boot.img is from RUU_Ace_HTC_WWE_1.32.405.6, it might break wifi for other roms. let me know if you have problems, i will try to find the correct boot.img for you then.
Code:
abd490503190fff2c0c7d17ec42a14c1 dhd/boot.img
- get fastboot.exe, put it on your pc in the same directory as adb.exe
- download the proper boot.img for your device, put it in c:\.
- connect your phone via usb, make sure usb debugging is enabled, open a command prompt and type:
Code:
adb reboot bootloader
fastboot boot c:\boot.img
if all goes well and the device boots up you know it works. now do:
Code:
adb reboot bootloader
fastboot flash boot c:\boot.img
this will make it permanent.
you probably need the s-off bootloader for this, as usually the s-on doesn't allow fastbooting or flashing img files.
To get boot.img go here
http://www.villainrom.co.uk/forum/s...with-adb-remount-and-rooted-adb-shell-support
find the same here for the T-Mobile G2/Desire Z: http://www.villainrom.co.uk/forum/showthread.php?3366

Permaroot the gift that keeps giving, this works fine on my DHD just clockwork recovery then CM here we come

testing something now tee hee shh

mikecoffee said:
All credit goes the Kendon from villainrom he rocks my socks
If you want to be able to use adb with root permissions you need one of these boot.imgs.
Click to expand...
Click to collapse
once you get s-off and the write protection has been removed do you really get declined root with adb?
i mean i had root with adb with temp root :S
did you try adb remount and see if that gave you write access to the partition?
slighlty confused as to what this is.
agree with you tho about Kendon, he sure does rock! had a hero and am happy i donated to VR cos they gave that device some life lmfao

Thanks a lot mikecoffee! Working fine here, no ... undesirable results

Don't really need this since I can find myself around the linux command line well enough to mount /system as read-write but thanks all the same. I'm sure some people will find it well handy.

dr.m0x said:
Don't really need this since I can find myself around the linux command line well enough to mount /system as read-write but thanks all the same. I'm sure some people will find it well handy.
Click to expand...
Click to collapse
I also, like to think, i can find myself around with CLI but was having problems with getting system mounted r/w, to be fair it was probably something i had neglected to do late at night, and personally found this boot image helped

has anyone got a mirror for this boot.img? the site seems to be down for me

billington.mark said:
has anyone got a mirror for this boot.img? the site seems to be down for me
Click to expand...
Click to collapse
Hi
the site is up, sorry if its been down not sure why!

dr.m0x said:
Don't really need this since I can find myself around the linux command line well enough to mount /system as read-write but thanks all the same. I'm sure some people will find it well handy.
Click to expand...
Click to collapse
So this is not needed to write to /system? I've done visionary r12 permroot + engineering hboot s-off but still can't write to /system.
mount -o remount,rw /dev/block/mmcblk0p25 /system works (mount shows /system as rw) but I still can't move files to it via terminal emulator nor adb.

Hboot information and downgrading

Before I start this thread, I should say that all credit goes to otaking71 for finding this crack.
The two original threads are here
http://forum.xda-developers.com/showthread.php?t=1255043
http://forum.xda-developers.com/showthread.php?t=1255360
All of the work was done in the #htc_evo_shift channel on freenode irc.
Table of contents:
1. Hboot information about the exploit.
2. Downgrading
2.1 Notes
3. Full root(Updated 2.2 root)
4. Links
5. Credits/donation links
I will aim to make it so this mod can be ported to other devices to help downgrade bootloaders and software. Please read the entire thread before flashing anything and trying this.
Hboot
Hboot uses a hidden partition to check everything it flashes against, this partition is "misc", or hboot -1, or on the shift mmcblk0p17(hboot itself is at mmcblk0p18).
Some raw dumps of this partition using strings to filter ascii strings brings out this type of dump.
Locked bootloader for the evo shift's dump
"SPCS_001
DeviceWarmBoot
CE Serial InUse
Debug Cable Ena
CE USB InUse
ClearAutoImage
2.76.651.4
FNOC
FNOC"
Unlocked bootloader for the verizon thunderbolt
"VZW__001
DeviceWarmBoot
CE Serial InUse
Debug Cable Ena
CE USB InUse
ClearAutoImage
1.02.605.6
FNOC
FNOC"
Eng spl unlocked evo shift
"FN0C
FN0C
FN0C"
Now the place to focus at is the version numbers, 2.76.651.4. Hboot will check all items you try to flash via hboot or ruu utility against this number and if it is lower than what you are trying to flash, it will allow you to proceed in flashing through hboot, or ruu. If the number is higher, it will reject the flash. If the number doesn't exist(like in the eng spl) it will assume it is able to flash it(ONLY TESTED ON ENG SPL, not locked bootloaders). So by dumping the TB's misc partition into our own, we made it so the locked hboot would accept flashes. Either by RUU or hboot.
We believe the package you flash still needs to be signed though so that only leaves you with official ruu's and extracted ruu zips.
Joeykrim's history(Located on the second page of this thread)
joeykrim said:
for those curious, a lil bit of history:
same method as used on the evo part 2 thread by toastcfh at xda.
only diff is shift is emmc and evo was mtd. shift emmc partitions are a bit more in number and named differnetly when compared to the evo mtd partitions. on the evo this partition was labeled as "misc" in /proc/partitions. the misc partition being flashed holds the software version number which hboot checks against to verify whether or not it will allow an RUU to be loaded.
also, i want to recall a web site somewhere which allows users to create a custom misc file with a provided version number.
thought this partition was protected by the internal memory write protection but appears it wasn't. not much of a surprise as the first release of the shift didn't have write protection for the hboot partition turned on.
great this works! sadly, they'll prob patch it next OTA around as they did for the evo.
good job on testing (sorry about the lost shift), publishing and releasing! glad to see the shift has unlocked internal memory write protection again!!!
you're path to the internal partition location is incorrect. as the OP states, use:/dev/block/mmcblk0p17
full command: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
great article with the history and usage of dd, its a classic unix/linux command. very good to become familiar with: http://en.wikipedia.org/wiki/Dd_(Unix)
Click to expand...
Click to collapse
How to downgrade your device
For the shift, will be different on other devices with a bit of modding.
1. Temproot(With Fre3vo for the shift) http://forum.xda-developers.com/showthread.php?t=1185243
2. Move the file misc.img to the root of your sdcard, and PG06IMG.zip too if you plan on flashing through hboot.
3. Modify the misc partition to bypass the version check, type the following in an adb shell or a terminal emulator on your phone.
Code:
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Note for other devs: misc.img is the image from the TB, could be other images as long as it has a lower version number.
4. This is up to you, you can either use the ruu utility to revert or the PG06IMG.zip in hboot. I'll include links to both. Since both utilities check the misc partition, both are able to flash =)
5. Reboot and then full root like normal on your downgraded device.
Notes
1. When flashing hboot/using this exploit it always flashes twice/stops early and recontinues. Don't worry about it, this is normal(Sometimes it looks like more than 2 but just chill out).
2. Some SDcards are not recognized by hboot, so you will either have to switch cards for this operation or use the ruu utility method.
3. Remove the PG06IMG from your sdcard after flash, or hboot will pick it up next time.
Full root for downgraded 2.2
Flash ENG bootloader
1. Download these files and extract them to the root of your sdcard: www.thebcblends.com/shift/Shift-root.zip
2. Obtain temproot from z4Root, visionary, OR CM's temproot wiki
3. Flash hboot with Engineer SPL:
Code:
dd if=/sdcard/Shift/hboot_eng.nb0 of=/dev/block/mmcblk0p18
4. Boot into bootloader and check for S-OFF
Flashing a recovery
1. Grab latest shift recovery from: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
2. Make sure you're temprooted(may have to temp root again)
3. Install recovery from rom manager
Alternative install can be done if you grab another recovery's recovery.img and do one of the following below.
a. Okay this is for those with fastboot - flash the recovery with fastboot: fastboot flash recovery recovery.img
b. This is for those where fastboot doesn't work or they don't have it - 1. Place recovery.img on the root of your sdcard, then type the command below.
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
Full root/Rom flashing
Well I know you don't have anything you want to save from the 2.2 ruu since it's just a stock flash, so I am going to leave it off here as flash whatever rom you want over the new system via recovery and you should end up with a fully rooted android.
Just remember to wipe data/factory reset after flash.
Links - MD5Sums aren't terribly important here as the files will not flash if they are not correct due to the signatures.
Fre3vo temp root for GB - http://forum.xda-developers.com/showthread.php?t=1185243
misc.img for the misc partition - http://dl.dropbox.com/u/41040697/misc.img MD5Sum: c88dd947eb3b36eec90503a3525ae0de
Misc.img mirror(You guys took down my second dropbox.....trying a different site now): http://www.box.net/shared/0l8ex73zne0tfr10ob69
Second mics.img mirror: http://dl.dropbox.com/u/15373824/misc.img
Another mirror for misc.img: http://dev-host.org/a9dbnuzgb9qv/misc.zip (Thanks Fdxrider)
Official ruu file for downgrading to 2.2 - http://www.multiupload.com/15N2D30H6C MD5SUM: a4b880954d2ac29d5bdf0dade9dede3c
PG06IMG for hboot downgrading to 2.2 - http://dl.dropbox.com/u/41040697/PG06IMG.zip MD5SUM: d20be478fd860b80f5e800c958f79077
Mirror for PG06IMG(First link went down temporarily due to generating too much traffic on my account, good job guys xD) - http://dl.dropbox.com/u/15373824/PG06IMG.zip
Mirror for PG06IMG: http://dev-host.org/xmlaaco0s2ph/PG06IMG.zip
2.2 root [Bcnice guide]- http://forum.xda-developers.com/showthread.php?t=932153
Cm's rooting method(For those without z4root or visionary) - http://wiki.cyanogenmod.com/wiki/HTC_Evo_Shift_4G:_Full_Update_Guide
Credits
Otaking71 - Discoverer of this exploit for the shift and working throughout the night to establish it as a working downgrade.
Bcnice20 & other 2.2 root devs - I borrowed your root methods for this guide, and linked to them. Just had to update it for recovery basically.
Stuke00 - Fre3vo temp root for 2.3.3
Joeykrim - Donating that history for the curious minds.
Donation links:
Otaking71 - Main driver of this discovery/creator and came up with this theory
http://forum.xda-developers.com/donatetome.php?u=1762836

Should we vote this to the front or try to keep it on the downlow?
^ Shift Faced

I'm at work now, but am I to understand that there is now a full root for shifts on gb?
Sent from my PC36100 using XDA App

totalnub911 said:
I'm at work now, but am I to understand that there is now a full root for shifts on gb?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Something of that sort, you can obtain full root through this exploit. Though it's through downgrading the firmware you use old 2.2 rooting methods.

totalnub911 said:
I'm at work now, but am I to understand that there is now a full root for shifts on gb?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
that is correct if you downgrade then root with shiftRR. thats what i'm getting from all this
EDIT: got beat to it

YoungCorruption said:
that is correct if you downgrade then root with shiftRR. thats what i'm getting from all this
EDIT: got beat to it
Click to expand...
Click to collapse
sounds like its time to change your siggy there youngcorruption!

Im sorry for the noobish but what does this mean and how do i do this
2. Modify the misc partition: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
misc.img is the image from the TB, could be other images as long as it has a lower version number.

halrulez said:
Im sorry for the noobish but what does this mean and how do i do this
2. Modify the misc partition: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
misc.img is the image from the TB, could be other images as long as it has a lower version number.
Click to expand...
Click to collapse
In more specific directions it means to move the downloaded file misc.img to /sdcard , then to type the command "dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17 misc.img" without quotes. The rest just means it'll be different on other devices.

Nice write up, thanks to otaking and scary you all saved the shifters from a horrible ota update
Sent from my Supreme Shift using Tapatalk

Scaryghoul said:
In more specific directions it means to move the downloaded file misc.img to /sdcard , then to type the command "dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17 misc.img" without quotes. The rest just means it'll be different on other devices.
Click to expand...
Click to collapse
ok can do this in terminal from my phone or do i have to do this in adb from my computer?
and if so what are the full steps to get to the point so i can enter this. I am trying to understand adb hell i am just starting in linux so i am hella noob

halrulez said:
ok can do this in terminal from my phone or do i have to do this in adb from my computer?
and if so what are the full steps to get to the point so i can enter this. I am trying to understand adb hell i am just starting in linux so i am hella noob
Click to expand...
Click to collapse
Either one, you can either mount your phone on usb and move the misc.img to your sdcard then type the command in terminal on your phone.
OR
You can adb push the file to your sdcard then adb shell the command.
I'll make the instructions more detailed in a bit.

What do you mean by: Modify the misc partition: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p1?
I moved the misc.img to sdcard but I have no mmcblk0pl in dev/block. Do I have to create that folder? And dd and of....lost me there.

I just did it and it worked perfectly. Back on 2.2, ready to root. Thanks again to otaking and scary for all your hard work.

ok so i was able to do this from the terminal from my android
bow though when i am trying to run the ruu from my computer is starts to go but keeps says that it is waiting for the booloader. the phone wont boot in to the boot loader

halrulez said:
ok so i was able to do this from the terminal from my android
bow though when i am trying to run the ruu from my computer is starts to go but keeps says that it is waiting for the booloader. the phone wont boot in to the boot loader
Click to expand...
Click to collapse
you might need to install htc sync to run ruu's. http://www.htc.com/managed-assets/support/software/htc-sync/setup_3.0.5557.exe

im just going to put this out there as well because i have had problems with the drivers that came with sync and i was forced to use the modified usb drivers found in the unrevoked evo tool, i dunno its weird but my vista pc didnt like anything but them drivers, and another guy i helped ruu from a major mess up, he couldnt get anything with sync to reconize his shift untill he used the same modified evo drivers . i hope no one has an issue but if it come about this is how to fix a driver issue

Best day ever!!!!!!!!!!!!!!!!!!!!!!!!!

strapped365 said:
im just going to put this out there as well because i have had problems with the drivers that came with sync and i was forced to use the modified usb drivers found in the unrevoked evo tool, i dunno its weird but my vista pc didnt like anything but them drivers, and another guy i helped ruu from a major mess up, he couldnt get anything with sync to reconize his shift untill he used the same modified evo drivers . i hope no one has an issue but if it come about this is how to fix a driver issue
Click to expand...
Click to collapse
provide link to said drivers?

riggsandroid said:
provide link to said drivers?
Click to expand...
Click to collapse
kinda cant provide an actual link directly to the drivers because i had to set up unrevoked just like i was rooting an evo, so i just hinted they were in the tool
http://unrevoked.com/recovery/
thats where you can get the tool from to setup your drivers if you have issues with sync not playing well or your pc just dont want to read the drivers right

for those curious, a lil bit of history:
same method as used on the evo part 2 thread by toastcfh at xda.
only diff is shift is emmc and evo was mtd. shift emmc partitions are a bit more in number and named differnetly when compared to the evo mtd partitions. on the evo this partition was labeled as "misc" in /proc/partitions. the misc partition being flashed holds the software version number which hboot checks against to verify whether or not it will allow an RUU to be loaded.
also, i want to recall a web site somewhere which allows users to create a custom misc file with a provided version number.
thought this partition was protected by the internal memory write protection but appears it wasn't. not much of a surprise as the first release of the shift didn't have write protection for the hboot partition turned on.
great this works! sadly, they'll prob patch it next OTA around as they did for the evo.
good job on testing (sorry about the lost shift), publishing and releasing! glad to see the shift has unlocked internal memory write protection again!!!
blakeatl said:
What do you mean by: Modify the misc partition: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p1?
I moved the misc.img to sdcard but I have no mmcblk0pl in dev/block. Do I have to create that folder? And dd and of....lost me there.
Click to expand...
Click to collapse
you're path to the internal partition location is incorrect. as the OP states, use:/dev/block/mmcblk0p17
full command: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
great article with the history and usage of dd, its a classic unix/linux command. very good to become familiar with: http://en.wikipedia.org/wiki/Dd_(Unix)

Rooting MyTouch 4G Slide HBOOT 1.44.0006

So I know this is a stupid question, but I just go my MT4GS and lets just say it's not the run in the mill got it from the store. An HTC rep swapped my G2 for this phone since my G2 was dying on me. With that said, the MT4GS is running HBOOT 1.44.0006 which I realize isn't the standard .0007 HBOOT.
The thing is, the phone is already S-OFF'd however I can't flash clockwork onto it, even through the Fastboot method. So any help?

Appogee said:
So I know this is a stupid question, but I just go my MT4GS and lets just say it's not the run in the mill got it from the store. An HTC rep swapped my G2 for this phone since my G2 was dying on me. With that said, the MT4GS is running HBOOT 1.44.0006 which I realize isn't the standard .0007 HBOOT.
The thing is, the phone is already S-OFF'd however I can't flash clockwork onto it, even through the Fastboot method. So any help?
Click to expand...
Click to collapse
http://revolutionary.io
Sent from my Senseless Doubleshot using xda premium

Revolutionary only allows for 1.44.0007 HBOOT, which isn't 1.44.0006. Any other ways?

Not that i know of.
Sent from my MyTouch_4G_Slide using xda premium

Hi. I had the same problem...
Usb debugging must be checked and adb working.
To flash the recovery
1) use fre3vo for temp root
adb push fre3vo /local/data/
adb shell fre3vo
(wait)
2) copy the recovery to the device
adb push recovery.img /local/data
3) obtain privileges and copy the recovery to the right partition
adb shell
su
dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21
It worked for me.

imateriali said:
Hi. I had the same problem...
Usb debugging must be checked and adb working.
To flash the recovery
1) use fre3vo for temp root
adb push fre3vo /local/data/
adb shell fre3vo
(wait)
2) copy the recovery to the device
adb push recovery.img /local/data
3) obtain privileges and copy the recovery to the right partition
adb shell
su
dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21
It worked for me.
Click to expand...
Click to collapse
I learned something new today
Sent from my MyTouch_4G_Slide using xda premium

imateriali said:
Hi. I had the same problem...
Usb debugging must be checked and adb working.
To flash the recovery
1) use fre3vo for temp root
adb push fre3vo /local/data/
adb shell fre3vo
(wait)
2) copy the recovery to the device
adb push recovery.img /local/data
3) obtain privileges and copy the recovery to the right partition
adb shell
su
dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21
It worked for me.
Click to expand...
Click to collapse
Well I get through the steps, it hasn't exactly been rooted yet. What do you mean obtain privs and copy the recovery to right partition?

Appogee said:
Well I get through the steps, it hasn't exactly been rooted yet. What do you mean obtain privs and copy the recovery to right partition?
Click to expand...
Click to collapse
OK.
First of all I downloaded the correct recovery image from the clockworkmod site. Then renamed it "recovery.img" and moved to the same folder of ADB.
In the step 3 when you type "su" from the adb shell you elevate privileges to root;
when you "dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21" you copy the recovery image from /data/local to "mmcblk0p21" that is the recovery boot partition.
After that, to obtain permanent root, you shold copy the "su" file from http://downloads.androidsu.com/superuser/su-2.3.6.3-efgh-signed.zip to the doubleshot sd card and install from recovery (this is better explained in the s-off /root thread you can find in the developer section http://forum.xda-developers.com/showthread.php?t=1286324).
This is not a fail proof procedure but it worked for me use at your own risk.
By the way, sorry about my english.

imateriali said:
OK.
First of all I downloaded the correct recovery image from the clockworkmod site. Then renamed it "recovery.img" and moved to the same folder of ADB.
In the step 3 when you type "su" from the adb shell you elevate privileges to root;
when you "dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21" you copy the recovery image from /data/local to "mmcblk0p21" that is the recovery boot partition.
After that, to obtain permanent root, you shold copy the "su" file from http://downloads.androidsu.com/superuser/su-2.3.6.3-efgh-signed.zip to the doubleshot sd card and install from recovery (this is better explained in the s-off /root thread you can find in the developer section http://forum.xda-developers.com/showthread.php?t=1286324).
This is not a fail proof procedure but it worked for me use at your own risk.
By the way, sorry about my english.
Click to expand...
Click to collapse
NEVERMIND! I Just finished rooting, THANK YOU SO MUCH!

[How-To] Update devices via the OTA .zip

Hello everyone,
rhcp was able to locate a method with which to do updates the standard way HTC does them. If you are, for instance, on 1.73 and have the 1.85 OTA .zip file (the one sent from HTC, not a CWM .zip file), you can use this method to place it in the right location and start an update.
Disclaimer:
I do not take responsibility if something goes wrong. PLEASE do this at your own risk.
Please do not use this to go to 1.85 as you may lose root. This is more FYI for future OTA updates or after 1.85 is rooted.
Requirements:
You must have ROOT before doing this. You'll be accessing a location that is not writable without root.
You must have the official OTA file. If someone can help with this portion I can post it here for all users to use if they wish.
Follow these steps to pull the OTA update:
When it shows "downloading" and the OTA completes, if you have root, please do the following:
Code:
adb shell
cd /cache
ls -l
Locate the file ending with .zip here. May look extremely long and should resemble something like OTA_Evita_U_Cingular.........zip
Quit out of adb shell
Code:
adb pull /cache/<file name of the OTA package.zip>
Post that package.zip file on a file share and send me the link and I will add it to the OP.
To update using the OTA file, follow these steps:
Code:
adb push <file name of the OTA package.zip> /mnt/sdcard/
adb shell
su
cp <file name of the OTA package.zip> /cache/update.zip
cd /cache/
mkdir recovery
cd recovery
echo “–update_package=/cache/update.zip” > command
adb reboot recovery
This will cause your device to update using the OTA method that HTC uses to push updates.
If this helped you...PLEASE donate to rhcp, which happens to have had to pay for a new One S due to bricking the first time figuring this out. His donate link is here.
Toss me a Thanks if you think this guide was helpful .

h8rift said:
Hello everyone,
rhcp was able to locate a method with which to do updates the standard way HTC does them. If you are, for instance, on 1.73 and have the 1.85 OTA .zip file (the one sent from HTC, not a CWM .zip file), you can use this method to place it in the right location and start an update.
Disclaimer:
I do not take responsibility if something goes wrong. PLEASE do this at your own risk.
Requirements:
You must have ROOT before doing this. You'll be accessing a location that is not writable without root.
You must have the official OTA file. If someone can help with this portion I can post it here for all users to use if they wish.
Follow these steps to pull the OTA update:
When it shows "downloading" and the OTA completes, if you have root, please do the following:
Code:
adb shell
cd /cache
ls -l
Locate the file ending with .zip here. May look extremely long and should resemble something like OTA_Evita_U_Cingular.........zip
Quit out of adb shell
Code:
adb pull /cache/<file name of the OTA package.zip>
Post that package.zip file on a file share and send me the link and I will add it to the OP.
To update using the OTA file, follow these steps:
Code:
adb push <file name of the OTA package.zip> /mnt/sdcard/
adb shell
su
cp <file name of the OTA package.zip> /cache/update.zip
cd /cache/
mkdir recovery
cd recovery
echo “–update_package=/cache/update.zip” > command
adb reboot recovery
This will cause your device to update using the OTA method that HTC uses to push updates.
If this helped you...PLEASE donate to rhcp, which happens to have had to pay for a new One S due to bricking the first time figuring this out. His donate link is here.
Toss me a Thanks if you think this guide was helpful .
Click to expand...
Click to collapse
nice but this update didnt fix anything anyway. wifi still sucks.

djfrost40 said:
nice but this update didnt fix anything anyway. wifi still sucks.
Click to expand...
Click to collapse
Lol. Be it as it may....this is still a handy method for us to use with future OTA updates.

h8rift said:
Lol. Be it as it may....this is still a handy method for us to use with future OTA updates.
Click to expand...
Click to collapse
I think ATT and HTC just need to issue a refund to all of the unfortunate folks that fell for this phone hook line and sinker...LOL, I tried the update, and wifi is still bad maybe even worse... I just boxed mine up and went back to my HTC Vivid.

djfrost40 said:
I think ATT and HTC just need to issue a refund to all of the unfortunate folks that fell for this phone hook line and sinker...LOL, I tried the update, and wifi is still bad maybe even worse... I just boxed mine up and went back to my HTC Vivid.
Click to expand...
Click to collapse
Sorry to hear that djfrost40. I have literally had zero issues with this phone. No issues mentioned here (besides HTC's software-tweaked multi-tasking) have been evident on my phone. Hope your Vivid treats you well.

h8rift said:
Sorry to hear that djfrost40. I have literally had zero issues with this phone. No issues mentioned here (besides HTC's software-tweaked multi-tasking) have been evident on my phone. Hope your Vivid treats you well.
Click to expand...
Click to collapse
Wow was starting to think I was the only one because like you I have had zero problems with my phone never had to replace it and the multi tasking doesn't really effect me all that much
Sent from My Nocturnalized Beast

The only issue I have is getting my OC to work 100%. Aside from that, I love the phone to death!

This method does not seem to work for me. I have no trouble following the steps but the phone just boots into recovery and nothing else. Also I think there are a couple of "exits" missing from the list of commands right after the creation of the command file, maybe they are implied.
Has anyone else verified this works for them? I am on a rooted, TWRP and still at 1.73. I also tried this method with CWM recovery installed but no luck.

anika200 said:
This method does not seem to work for me. I have no trouble following the steps but the phone just boots into recovery and nothing else. Also I think there are a couple of "exits" missing from the list of commands right after the creation of the command file, maybe they are implied.
Has anyone else verified this works for them? I am on a rooted, TWRP and still at 1.73. I also tried this method with CWM recovery installed but no luck.
Click to expand...
Click to collapse
If you have twrp, why have you flashed a custom Rom?
Sent from my HTC One X using Tapatalk 2

kleeman7 said:
If you have twrp, why have you flashed a custom Rom?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah, kinda does'nt make sense. Actually I am liking the original HTC sense and also I am not sure which rom to try out.

Update.zip for root??
Is it possible to make an update.zip that we could flash via stock recovery to push su bianary? Just a thought.

kizzle4 said:
Is it possible to make an update.zip that we could flash via stock recovery to push su bianary? Just a thought.
Click to expand...
Click to collapse
Nope, unless you work for HTC and know how to get the key to sign the update zip
Sent from my HTC One XL using Tapatalk 2

What about update zip from say an international version?

kizzle4 said:
What about update zip from say an international version?
Click to expand...
Click to collapse
It will fail once it reads the build prop and realizes that this isn't an international one x, and if it does flash you would have a nice paperweight
Besides what does this accomplish? You can't modify ANY zip file from HTC without breaking the signature. Which makes this method useless
Sent from my HTC One XL using Tapatalk 2

In order for a thread to exist in the development section, it must contain a link to downloadable content. Because this is more of a guide, I'm moving this to general.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.

What steps in the OP modify if there's not enough space on the cache partition to hold the update.zip? Is it safe to run the following steps in that case:
Code:
adb push <file name of the OTA package.zip> /mnt/sdcard/
adb shell
su
cd /mnt/sdcard/
mv <file name of the OTA package.zip> update.zip
cd /cache/recovery
echo "-update_package=/mnt/sdcard/update.zip" > command

AlxMAX said:
What steps in the OP modify if there's not enough space on the cache partition to hold the update.zip? Is it safe to run the following steps in that case:
Code:
adb push <file name of the OTA package.zip> /mnt/sdcard/
adb shell
su
cd /mnt/sdcard/
mv <file name of the OTA package.zip> update.zip
cd /cache/recovery
echo “–update_package=/mnt/sdcard/update.zip” > command
Click to expand...
Click to collapse
Wondering this too... or even using a larger partition like /data that has 1GB free. :-/

Can someone dd the radio partition for me and link to it?
Wanna make the zips =)
FYI: use this adb command and then pull the img of your sd card -
Code:
C:\adb>adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img

taylor.fowler said:
Can someone dd the radio partition for me and link to it?
Wanna make the zips =)
FYI: use this adb command and then pull the img of your sd card -
Code:
C:\adb>adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img
Click to expand...
Click to collapse
"removed from dropbox" stock radio from new at&t ota, download taylor.fowler cwm flashable

Cm10.x and sense zips coming soon!
Sent from my One X using xda app-developers app

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