GO HERE AFTER CAREFULLY FOLLOWING THIS PROCEDURE TO INSTALL ROMS, S-OFF, ETC.
delacerda said:
Confirmed! Stock AT&T OneX on 3.18 JB 4.1.1. SuperCID 11111111 , HTC Dev bootloader unlocked, TWRP recovery installed, perm rooted.
Click to expand...
Click to collapse
nhshah7 said:
Got SuperCID and about to unlock after I backup some data.
Thank you so much!
Here is what I did and what worked for me:
Copy oneXchopper, ownage, and busybox files to folder with ADB (this is if you have the android sdk)
Code:
adb push oneXchopper /data/local/tmp/xpwn
adb push busybox /data/local/tmp/busybox
adb push ownage /data/local/tmp/phase1.sh
adb shell chmod 755 /data/local/tmp/xpwn /data/local/tmp/busybox
adb shell
(within ADB shell)
ln -s /data/local/tmp/busybox /data/local/tmp/sed
/data/local/tmp/xpwn
You will see this:
[+] This may take a few minutes.
[+] Success!
2+0 records in
2+0 records out
1024 bytes transferred in 0.001 secs (1024000 bytes/sec)
2+0 records in
2+0 records out
1024 bytes transferred in 0.001 secs (1024000 bytes/sec)
2+0 records in
2+0 records out
1024 bytes transferred in 0.008 secs (128000 bytes/sec)
exit (will exit from shell)
adb reboot bootloader
This will reboot you to the bootloader. If you have the android SDK, you can confirm superCID via the command "fastboot getvar cid".
Next step, hit up HTCdev.com for an unlock code!
Thanks man
Click to expand...
Click to collapse
Root on the ATT 3.18 firmware for HTC One XL and SuperCID. Linux only for now due to laziness.
Here ya go, just extract and run pwn.sh. This automated method is untested, however I have done it manually to my own phone last night.
Just to clarify, this is a temp root which sets your CID to SuperCID allowing a bootloader unlock via HTCDev. It does NOT install Superuser or anything of that sort.
I'm not responsible for bricks, warranty voiding, etc. and please let me know if this works or if I need to tweak some things. It SHOULD handle everything automatically.
Thanks to Dan Rosenberg for Motochopper, which I modified very slightly for use in this script.
Thanks also to the people who paid the bounty. You guys are awesome and probably just bought me something nice. Not sure what yet
One more thanks to Daft Punk for providing some decent music to listen to while I worked on this. I was up all night to get lucky xD
A backup of mmcblk0p4 is made in /sdcard/backup.cid. You can run /data/local/tmp/xpwn manually and restore this backup should things go wrong.
dd if=/sdcard/backup.cid of=/dev/block/mmcblk0p4
This script is sponsored, created, and fueled by absolute hatred of AT&T. Enjoy your HTC Dev unlock!
UPDATE: There is now a Windows auto-pwn script available, thanks to Megadoug13.
You can get it from HERE
I am unable to test or really work with this because I have no Windows box, so contact Megadoug13 if it doesn't work.
The instructions I received with this package are as follows:
Megadoug13 (via email) said:
Just double click "ONLY ONE X" have usb debugging on. and when the phone gets into bootloader it wont tell you that your cid is 11111111. just get your token id and then submit at htcdev. this is only the cid change script. oh make sure to unzip it lol. dont click on anything BUT "ONLY ONE X"
Click to expand...
Click to collapse
myusernam3 said:
Root on the ATT 3.18 firmware for HTC One XL and SuperCID. Linux only for now due to laziness.
Here ya go, just extract and run pwn.sh. This automated method is untested, however I have done it manually to my own phone last night.
I'm not responsible for bricks, warranty voiding, etc. and please let me know if this works or if I need to tweak some things. It SHOULD handle everything automatically.
Thanks to Dan Rosenberg for Motochopper, which I modified very slightly for use in this script.
A backup of mmcblk0p4 is made in /sdcard/backup.cid. You can run /data/local/tmp/pwn manually and restore this backup should things go wrong.
dd if=/sdcard/backup.cid of=/dev/block/mmcblk0p4
This script is sponsored, created, and fueled by absolute hatred of AT&T. Enjoy your HTC Dev unlock!
Click to expand...
Click to collapse
Well well that's sooner than I thought. Good job man. Now to see if other users report success with this.
Sent from Xparent Red using my Venomized Evita
ImagioX1 said:
Well well that's sooner than I thought. Good job man. Now to see if other users report success with this.
Sent from Xparent Red using my Venomized Evita
Click to expand...
Click to collapse
Thank you. As I said, though, I have no clue if the automated method works due to not having a test dummy.
If you need to do it manually, the two scripts "pwn.sh" and "ownage" have everything you need to do in them. Just read them.
myusernam3 said:
Thank you. As I said, though, I have no clue if the automated method works due to not having a test dummy.
If you need to do it manually, the two scripts "pwn.sh" and "ownage" have everything you need to do in them. Just read them.
Click to expand...
Click to collapse
I'll see if I can talk the wife into letting me try it on hers. Awesome job man. Thanks
Sent from my One X using Tapatalk 2
myusernam3 said:
Thank you. As I said, though, I have no clue if the automated method works due to not having a test dummy.
If you need to do it manually, the two scripts "pwn.sh" and "ownage" have everything you need to do in them. Just read them.
Click to expand...
Click to collapse
I'm on hboot 1.09 soff already so no need for me to test. If yall don't mind me making a suggestion I would suggest you pm venomtester and ask him to try your script. He has a riff box and can jtag the phones in case of a brick.
Sent from Xparent Red using my Venomized Evita
ImagioX1 said:
I'm on hboot 1.09 soff already so no need for me to test. If yall don't mind me making a suggestion I would suggest you pm venomtester and ask him to try your script. He has a riff box and can jtag the phones in case of a brick.
Sent from Xparent Red using my Venomized Evita
Click to expand...
Click to collapse
Shot him a PM, we'll see what happens.
Subscribed and will test this once my phone is charged.
Sent from my Transformer Prime TF201 using Tapatalk HD
EDIT: Windows Manual method added from this post
nhshah7 said:
Okay, since people are having issues with the manual methods for Windows, I'm going to recommend installing using the Android SDK. @myusernam3, please remove the code from the OP and the other thread and replace it with a link to this post.
DISCLAIMER: Please read this post 4 times over before you attempt this procedure. It may render your phone unusable (read: a brick) if you don't follow it correctly. I and anyone else associated with this exploit is not responsible for any issues that may arise from this process, such as if you brick your phone. Proceed at your own risk, and with extreme caution. This procedure is not for those who don't want to take the time to read and understand how this works.
Download the android SDK and install it. Once that's done, open the android SDK manager and download platform-tools.
Navigate to C:\Program Files (x86)\Android\android-sdk\platform-tools to make sure adb.exe and fastboot.exe are there.
Download the files in the OP and then copy oneXchopper, ownage, and busybox to the platform-tools folder.
Once the files are moved over, you need to open a command prompt window. In windows explorer open to that folder (platform-tools), hold down the shift button and right click anywhere in the folder (not on a file). Then click Open command prompt window here. You should then see a command prompt window open to the platform tools window.
Plug in your phone and make sure USB debugging is enabled (Settings, developer options - enable this if it asks you, make sure USB debugging is checked). Now back in the command prompt, type "adb devices". It should show you HTCxxxxxxxxxx. That confirms that your phone and adb can see each other. If not, make sure you have the correct drivers installed. You can google around for help with this if you have trouble.
With that, we're ready to start typing in commands!
Type the following commands in one line at a time, minus the stuff in parenthesis. When you get to the first adb shell line, hit enter, then type the following line by line:
chmod 755 /data/local/tmp/xpwn /data/local/tmp/busybox
ln -s /data/local/tmp/busybox /data/local/tmp/sed line
/data/local/tmp/xpwn
You'll see a bunch of lines of code (see below)
Once this is all done, type in "exit", then "adb reboot bootloader" (at the bottom of the code quote)
Code:
adb push oneXchopper /data/local/tmp/xpwn
adb push busybox /data/local/tmp/busybox
adb push ownage /data/local/tmp/phase1.sh
adb shell
(within ADB shell)
chmod 755 /data/local/tmp/xpwn /data/local/tmp/busybox
ln -s /data/local/tmp/busybox /data/local/tmp/sed
/data/local/tmp/xpwn
You will see this:
[+] This may take a few minutes.
[+] Success!
2+0 records in
2+0 records out
1024 bytes transferred in 0.001 secs (1024000 bytes/sec)
2+0 records in
2+0 records out
1024 bytes transferred in 0.001 secs (1024000 bytes/sec)
2+0 records in
2+0 records out
1024 bytes transferred in 0.008 secs (128000 bytes/sec)
exit (will exit from shell)
adb reboot bootloader
You should now be in the bootloader. type in "fastboot getvar cid" and it should show you that your CID is "11111111". If so, it worked! From here, you can follow the instructions here to unlock your bootloader (go to htcdev.com and follow instructions for unlocking a device. in the dropdown device list, select the bottom "other" option).
From there you have to flash TWRP (download link: http://techerrata.com/browse/twrp2/evita - NOTE download 2.3.3.1 because some roms don't flash via TWRP 2.5.0.0). Instructions on how to flash are here (http://techerrata.com/browse/twrp2/evita). you should install via the "Download - Recovery Image Method" - run the fastboot command from the platform-tools folder command prompt above. Your phone should be in bootloader ("adb reboot bootloader" will get you there if you are in android). Copy the downloaded recovery image file to the platform-tools folder, then input the command at the website above (fastboot flash recovery...). Once it flashes successfully, use the up/down volume buttons to select bootloader (on the phone itself), then select recovery via pressing the power button to select. In recovery, make sure you have your rom loaded on your phone first. then go to wipe, and click factory data reset and wipe system. then hit the home button, hit install then install the rom you want. (this is assuming you want to install a rom, not just root.
After unlocking, it will wipe your SD card and you will lose all your sd card data and will have to load a rom to the SD card after unlocking it. it will boot up into the stock rom after you unlock so you can do that here after unlocking and/or flashing TWRP. Alternatively, you can flash SuperSU in recovery to obtain root in the stock rom, then obtain S-Off (see sticky in Developer sub-threads). If you want to use CM or any rom in the Original Android sub-thread, you will have to downgrade your touch-panel firmware. There are stickies in the Original Android Development sub-thread for this.
Good luck!
Click to expand...
Click to collapse
nhshah7 said:
Subscribed and will test this once my phone is charged.
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
Best of luck. I'd be happy to take any feedback and if it doesn't work I will resolve it.
If you have TeamViewer or similar we could also walk through doing the whole process manually (5 minutes or so)
I am down to try it here in a few. I'll get my linux machine going tonight and post back.
Sent from my HTC One X using xda app-developers app
Just took a look at the download, do you have a windows script I can use? Or could you provide me with the commands? Thanks!
Sent from my Transformer Prime TF201 using Tapatalk HD
nhshah7 said:
Just took a look at the download, do you have a windows script I can use? Or could you provide me with the commands? Thanks!
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
Read the shell script pwn.sh, it has all the commands in it. You can open it in Wordpad (Notepad eats the line endings).
adb push oneXchopper /data/local/tmp/xpwn
adb push busybox /data/local/tmp/busybox
adb push ownage /data/local/tmp/phase1.sh # Yes, it needs to be named this, That's what oneXchopper executes instead of copying su.apk.
adb shell chmod 755 /data/local/tmp/xpwn /data/local/tmp/busybox
adb shell ln -s /data/local/tmp/busybox /data/local/tmp/sed
adb shell "/data/local/tmp/xpwn"
adb reboot bootloader # Your CID should now be 11111111
EDIT: Oh f***, I left out a quotation mark in the script that's run on the phone.
Edit that before you push it! The line starting with "./sed" should be
./sed 's/CWS__001/11111111/' /data/local/tmp/cid > /data/local/tmp/newcid
Good work!
iElvis said:
Good work!
Click to expand...
Click to collapse
Not good work. The .tar.gz that was up a second ago might break stuff. The new one should be fine though.
myusernam3 said:
Not good work. The .tar.gz that was up a second ago might break stuff. The new one should be fine though.
Click to expand...
Click to collapse
I meant finding a way to edit CID.
iElvis said:
I meant finding a way to edit CID.
Click to expand...
Click to collapse
Well, thanks for the compliment. May as well post this cheap, lame way I did it in the thread for people who'd prefer to do it manually.
This is to be run on your HOXL after pushing Busybox and oneXchopper, and obtaining root.
dd if=/dev/block/mmcblk0p4 of=/data/local/tmp/cid
dd if=/dev/block/mmcblk0p4 of=/sdcard/backup.cid
./sed 's/CWS__001/11111111/' /data/local/tmp/cid > /data/local/tmp/newcid
dd if=/data/local/tmp/newcid of=/dev/block/mmcblk0p4
Do I have the balls? Been drinking but hopefully I don't turn the phone into slingshot ammo. Lemme find my laptop.....
-Sugardaddy
Arrow44 said:
Do I have the balls? Been drinking but hopefully I don't turn the phone into slingshot ammo. Lemme find my pc.....
-Sugardaddy
Click to expand...
Click to collapse
I'm not entirely sure what happens if you manage to corrupt mmcblk0p4, but a backup is made during the CID changing process.
If the phone still boots after that, there's still hope.
myusernam3 said:
I'm not entirely sure what happens if you manage to corrupt mmcblk0p4, but a backup is made during the CID changing process.
If the phone still boots after that, there's still hope.
Click to expand...
Click to collapse
If this screws up I am SOL because I just got a refurbished one from AT&T
Arrow44 said:
If this screws up I am SOL because I just got a refurbished one from AT&T
Click to expand...
Click to collapse
If you'd prefer (and if you can trust me with TeamViewer or a similar program) I can try and do it manually, just to make sure nothing goes wrong.
myusernam3 said:
If you'd prefer (and if you can trust me with TeamViewer or a similar program) I can try and do it manually, just to make sure nothing goes wrong.
Click to expand...
Click to collapse
Well Im in Backtrack right now and if what you say is correct all i should do is run the script?
Related
Make sure your battery has a decent amount of charge in it, you don't want to run out of juice in the middle of this.
You will need to have the android sdk installed, as you will need to use the adb tool.
Windows users will need to install HTC Sync in order to get the usb driver for the phone installed.
Part 1: In which we find that the Evo spreads easier than a Thai whore during tourist season
Code:
adb shell "rm /data/local/rights/mid.txt"
adb shell "ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt"
adb reboot
Part 2: In which we find that engineers have no personality, but they make one hell of a bootloader
Put the files from Toast's Part 2, for nand unlock onto the sdcard (PC36IMG.zip, mtd-eng.img, recovery.img, flash_image)
then (after making sure the sdcard is remounted to the phone if you used disk mode to xfer the files):
Code:
adb shell "cat /sdcard/flash_image > /data/local/rights/flash_image"
adb shell "chmod 755 /data/local/rights/flash_image"
adb shell "/data/local/rights/flash_image misc /sdcard/mtd-eng.img"
adb reboot bootloader
When asked if you want to update, say yes. Relax for a while, the update takes some time.
When the phone eventually boots back up:
Part 3: In which I find the whore, and make her install a custom recovery
Code:
adb shell "cat /sdcard/flash_image > /data/flash_image"
adb shell "chmod 755 /data/flash_image"
adb shell "/data/flash_image recovery /sdcard/recovery.img"
After this you should be fully rooted with nand unlock.
I highly recommend going through Whitslack's Starting Over method to bring your software and radios up to date.
You're done.
Pity this only came to light a few days before people are going to be upgrading to a new OTA.
No, this will not work for anyone who updated to 2.2.
epic!!! 789
niice!
Nice Find!
At least now people can be rooted prior to the new OTA!
damn it!
___
Sweet! Wish I had that method starting out. Lol.
Sent from my PC36100 using XDA App
does this method really work??
BAttitude7689 said:
does this method really work??
Click to expand...
Click to collapse
Yes it does.
ok, so i have no idea how that works... care to go into it alittle bit more?
khshapiro said:
ok, so i have no idea how that works... care to go into it alittle bit more?
Click to expand...
Click to collapse
The init scripts chmod 777 mid.txt on boot (this means that anyone can do anything to the file basically). By removing the file and linking it to mtd1, the chmod now makes mtd1 accessible by everyone after a reboot, which means that you can go directly to toast's part2 which starts with flashing mtd-eng.img.
Incidentally it appears the droid eris guys have been using this flaw to their advantage for a while as well ;D.
So no, really? What is "root?"
You do fine work, sir
posting in a legendary thread
Couldn't you then just use wits "start over" method for part two to make the process even shorter?
netarchy said:
Part 1:
Code:
adb shell rm /data/local/rights/mid.txt
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
adb reboot
Click to expand...
Click to collapse
What would be more interesting is for someone on the new OTA non-root to see if this exists in the Froyo release. I'll look around for a posting of the OTA update non-rooted and try it on my smashed phone. At least I won't care if that thing looses root.
Could we get a "The easiest 1.47.651.1 root method with nand unlock" for dummies? I have no clue what to do with this code.
You need to use an ADB shell for this using the Android SDK....
I tried to use the Evo-Recovery shell and received permission denied errors.
I am not a DEV by any means, and do not claim any credit for any of this. However, for people who need help, this may offer some assistance -- this is definitely the easiest root method out there.
1. Download and Install Android SDK - Learn Here
http://forum.xda-developers.com/showthread.php?t=694250
2. Open up a Command Prompt by holding windows button & pressing R or by pressing Run and typing CMD.
3. Navigate your way in DOS to the Android SDK folder, then to the Tools Folder
4. Then enter in the code in part 1. After each line press enter...the line will repeat below it.
5. Follow Toasts Part 2 -- Link: http://forum.xda-developers.com/showthread.php?t=701835 -- Video found here: http://www.youtube.com/watch?v=tUXTB0eydwE.
5A. Because you didn't do Toast's Part 1 of Root first (you used an exploit provided by the OP), you will NOT have a NAND Backup. Put the Custom ROM you want to load on your SD card, and after unlocking NAND protection and doing the wipes, load it from the custom recovery in lieu of restoring your NAND backup.
6. You're now rooted w/ NAND Unlocked!
7. I would then suggest going here, and running this so you have a fully rooted, stock ROM with all your radio/wimax up to date: http://forum.xda-developers.com/showthread.php?t=715915.
Anyone know if this method will work on an unrevoked3'd Evo? I am trying to acquire full root and I was going to use SimpleRoot today but if this will work...
Thank you for this! Question about number part 7. YOu suggest running the fully rooted stock 1.47.651.1 afterwards. Would it be a bad idea to Just run the fully rooted stock froyo 3.23.651.3 or even any other custom rom for that matter? i.e OMJ's EVO 2.2 Custom rom? Thanks
regulator207 said:
Couldn't you then just use wits "start over" method for part two to make the process even shorter?
Click to expand...
Click to collapse
No because you need the engineering hboot to flash it since it's not signed by HTC.
Should work on 1.32 or 1.47. Nice.
Someone should test if this still works in the new 2.2 update. Good chance it does.
damit!
justinisyoung said:
damn it!
___
Click to expand...
Click to collapse
Hey! That's what I was gonna say!
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....
sorry about all the updates i am trying to remember as i go along with the help of the comments below, we will get this working as i know it does
i have actually managed it i used fre3vo from this thread
http://forum.xda-developers.com/showthread.php?t=1178912
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 pressing enter at the end of each step
(big thanks to Jorgen2009 for cleaning up the 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. reboot the phone with the cable attached to the computer
6. adb shell (this gives a $-prompt)
7. /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF (when everything is OK you'll go back to your own prompt, not the phones)
8. adb shell (you'll have a #-prompt now, cause the the is temp-rooted)
9. /data/local/tmp/misc_version -s 1.27.405.6
10. install the earliest RUU version you can find. I used RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release_177977_signed
11. after rebooting your phone has the old HBOOT (0.98.0000)
12. enable USB Debugging (Settings - Applications - Development) and reboot the phone again
13. Run the AlphaRevX binary and don't install the CWM recovery, we'll use 4EXTRecovery lateron
congratulations, your phone is now S-OFF!
download the latest EXT4Recovery from here
adb reboot bootloader
fastboot flash recovery [PATH TO recovery.img]
fastboot reboot-bootloader
go to the recovery and install any ROM you like
hope this helps everyone.
as usuall not my fault, brick yadda yadda
credit to sethario, the fre3vo dev team and Jorgen2009
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.
as usuall not my fault, brick yadda yadda
Click to expand...
Click to collapse
Brilliant and well done. .
could you please add exactly which 1.47 version that you achieved this on and from which country.
also get this useful thread added to the INDEX sticky thread that we have be either PM' ing threads OP or adding post in that Thread.
Sent from my HTC Desire S using XDA Premium App
ben_pyett said:
Brilliant and well done. .
could you please add exactly which 1.47 version that you achieved this on and from which country.
also get this useful thread added to the INDEX sticky thread that we have be either PM' ing threads OP or adding post in that Thread.
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
not sure exactly what 1.47 as its gone now but as i said in my post im on a vodafone uk if that helps
also just to make it clear, none of this is my own work guys a lot brighter than me figured all the hard stuff out, i just fitted the different bits together
davidreece said:
not sure exactly what 1.47 as its gone now but as i said in my post im on a vodafone uk if that helps
also just to make it clear, none of this is my own work guys a lot brighter than me figured all the hard stuff out, i just fitted the different bits together
Click to expand...
Click to collapse
All the same, Putting the bits together, writing the guide and having the balls to try all of these steps on your own device is worthy of thanks and just a little praise
Sent from my HTC Desire S using XDA Premium App
thanks ben just glad to put something back instead of leeching all the devs hard work all the time
Thanx davidreece, great find!
Unfortunately it's not working for me I get stuck at point 5 running the fre3vo binary. I waited 20 minutes for it to complete, but it's still saying "please wait" with a blinking cursor. For the record, I'm using this rom: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed. That could be the problem perhaps.
I also noticed that the the fre3vo link from your article is a bit older then the fre3vo version on the fre3vo thread. Of course i tried that one too, but it gives the same result for me
Any ideas?
Cheers
not a clue jorgen sorry i should maybe add the words "some"
just a thought when you ran the fre3vo command where you in adb shell or at the command prompt >, i seem to remember it happened to me the first time i tried it but i cant remember how i got it wrong, ithink you have to enter the adb shell command first then enter /data/local/tmp/fre3vo next or it may be enter them both together as one line i cant really remember, i was so surprised it worked if anyone else gets this to work could you please clarify the fre3vo steps and i will update the main post thanks, hope this helps, also i only used the link version not any newer one
davidreece said:
not a clue jorgen sorry i should maybe add the words "some"
just a thought when you ran the fre3vo command where you in adb shell or at the command prompt >, i seem to remember it happened to me the first time i tried it but i cant remember how i got it wrong, ithink you have to enter the adb shell command first then enter /data/local/tmp/fre3vo next or it may be enter them both together as one line i cant really remember, i was so surprised it worked if anyone else gets this to work could you please clarify the fre3vo steps and i will update the main post thanks, hope this helps, also i only used the link version not any newer one
Click to expand...
Click to collapse
I tried both methods, both with the same result. It's great to see however it worked for you. It means there is at least a possibility to get S-OFF on updated devices
jorgen2009 said:
I tried both methods, both with the same result. It's great to see however it worked for you. It means there is at least a possibility to get S-OFF on updated devices
Click to expand...
Click to collapse
really sorry i falsly got your hopes up, maybe ask in the fre3vo forum maybe im just getting it wrong, it was 4am here when i succeeded so its all a bit hazy
jorgen2009 said:
Thanx davidreece, great find!
Unfortunately it's not working for me I get stuck at point 5 running the fre3vo binary. I waited 20 minutes for it to complete, but it's still saying "please wait" with a blinking cursor. For the record, I'm using this rom: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed. That could be the problem perhaps.
I also noticed that the the fre3vo link from your article is a bit older then the fre3vo version on the fre3vo thread. Of course i tried that one too, but it gives the same result for me
Any ideas?
Cheers
Click to expand...
Click to collapse
Eureka i have updated the instructions jurgen also redownload my fre3vo link just in case it was different, i knew i had to do something else, please let me know if it works now
I remember seeing in the original fre3evo thread there was a series or range of hex addresses to try if the first default one didn't achieve root
Sent from my HTC Desire S using XDA Premium App
I am stuck on instructions step 5. it says unable to chmod -debug: No such file or directory. My Bootloader version is 0.98.0002. In my understanding instructions step 5 is confusing as first i wrote it with step 4 and then i realize that first write adb shell chmod 777 etc etc. Am i doing right?
maroof.saeed said:
I am stuck on instructions step 5. it says unable to chmod -debug: No such file or directory. My Bootloader version is 0.98.0002. In my understanding instructions step 5 is confusing as first i wrote it with step 4 and then i realize that first write adb shell chmod 777 etc etc. Am i doing right?
Click to expand...
Click to collapse
sorry maroof not sure whats wrong maybe ask in the original thread linked at the 1st post
maroof.saeed said:
I am stuck on instructions step 5. it says unable to chmod -debug: No such file or directory. My Bootloader version is 0.98.0002. In my understanding instructions step 5 is confusing as first i wrote it with step 4 and then i realize that first write adb shell chmod 777 etc etc. Am i doing right?
Click to expand...
Click to collapse
Hello, you're right there appears to is a slight mistake above, from my understanding of this the commands they should be entered as I've shown below from your PC within a command shell window with a <RETURN> at the end of every line.
Code:
C:\Program Files\Microsoft Support Tools> [B]adb shell [/B]
$ [B]chmod 777 /data/local/tmp/fre3vo[/B]
$ [B]chmod 777 /data/local/tmp/misc_version[/B]
$ [B]/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF[/B]
davidreece said:
sorry maroof not sure whats wrong maybe ask in the original thread linked at the 1st post
Click to expand...
Click to collapse
Thanks for the reply but the thing is that am i doing the right way as i wrote in my last thread that first i mix 4th step and fifth but then i realize and did the same as in 4th step? If its right then offcourse i 'll ask someone in the original thread.
davidreece said:
Eureka i have updated the instructions jurgen also redownload my fre3vo link just in case it was different, i knew i had to do something else, please let me know if it works now
Click to expand...
Click to collapse
That did the trick!! I'm running Saga LBC Mod as we speak!! The steps I followed after downloading the bits from the first post for this were the following:
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
reboot the phone with the cable attached to the computer
adb shell (this gives a $-prompt)
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF (when everything is OK you'll go back to your own prompt, not the phones)
adb shell (you'll have a #-prompt now, cause the the is temp-rooted)
/data/local/tmp/misc_version -s 1.27.405.6
install the earliest RUU version you can find. I used RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
after rebooting your phone has the old HBOOT (0.98.0000)
enable USB Debugging (Settings - Applications - Development) and reboot the phone again
Run the AlphaRevX binary and don't install the CWM recovery, we'll use 4EXTRecovery lateron
congratulations, your phone is now S-OFF!
download the latest EXT4Recovery from here
adb reboot bootloader
fastboot flash recovery [PATH TO recovery.img]
fastboot reboot-bootloader
go to the recovery and install any ROM you like
Big thanx again to David!
glad it worked, i knew it was in there somewhere is it ok if i add your instructions to the first post to save confusion
@david
Of course it is, let the S-OFF-ing begin (again)
jorgen2009 said:
That did the trick!! I'm running Saga LBC Mod as we speak!! The steps I followed after downloading the bits from the first post for this were the following:
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
reboot the phone with the cable attached to the computer
adb shell (this gives a $-prompt)
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF (when everything is OK you'll go back to your own prompt, not the phones)
adb shell (you'll have a #-prompt now, cause the the is temp-rooted)
/data/local/tmp/misc_version -s 1.27.405.6
install the earliest RUU version you can find. I used RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
after rebooting your phone has the old HBOOT (0.98.0000)
enable USB Debugging (Settings - Applications - Development) and reboot the phone again
Run the AlphaRevX binary and don't install the CWM recovery, we'll use 4EXTRecovery lateron
congratulations, your phone is now S-OFF!
download the latest EXT4Recovery from here
adb reboot bootloader
fastboot flash recovery [PATH TO recovery.img]
fastboot reboot-bootloader
go to the recovery and install any ROM you like
Big thanx again to David!
Click to expand...
Click to collapse
all worked well but while installing RUU_Saga_HTC_Europe_1.28.401.1. Its gives an error saying CUSTOMER ID Error. Now what
maroof.saeed said:
all worked well but while installing RUU_Saga_HTC_Europe_1.28.401.1. Its gives an error saying CUSTOMER ID Error. Now what
Click to expand...
Click to collapse
are you using the exe version of the ruu, if you are maybe try making your sdcard into a gold card
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
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