Related
OTA update to cupcake make you lose root? Have a fastboot enabled SPL?
These instructions are for those who have a Bootloader with fastboot enabled. (Hard SPL, Engineering SPL, etc.)
Again these instructions are for those who have a bootloader with fastboot enabled.
THIS WILL WORK ON ALL FIRMWARE VERSIONS WITHOUT HAVING TO REFLASH!
As long as you have fastboot enabled in your SPL you can root any of the OTA update without having to reflash your firmware or downgrade.
1) Download JF Recovery V 1.43
2) Extract recovery.img from the data directory
3) Boot phone into bootloader (power off then power+camera buttons)
4) use fastboot to boot into recovery firmware (this will NOT flash just boot)
# fastboot boot recovery.img
5)wait for firmware to boot and hit Alt+x
6)press enter when it tells you
7)type on your phone
# mount system
8)wait for a new prompt #
9)type on your phone
# cd /system/bin
# cat sh > su
# chmod 4755 su
# reboot
10) Your phone is now rooted
semyazza said:
OTA update to cupcake make you lose root? Have a fastboot enabled SPL?
These instructions are for those who have a Bootloader with fastboot enabled. (Hard SPL, Engineering SPL, etc.)
Again these instructions are for those who have a bootloader with fastboot enabled.
THIS WILL WORK ON ALL FIRMWARE VERSIONS WITHOUT HAVING TO REFLASH!
As long as you have fastboot enabled in your SPL you can root any of the OTA update without having to reflash your firmware or downgrade.
1) Download JF Recovery V 1.43
2) Extract recovery.img from the data directory
3) Boot phone into bootloader (power off then power+camera buttons)
4) use fastboot to boot into recovery firmware (this will NOT flash just boot)
# fastboot boot recovery.img
5)wait for firmware to boot and hit Alt+x
6)press enter when it tells you
7)type on your phone
# mount system
8)wait for a new prompt #
9)type on your phone
# cd /system/bin
# cat sh > su
# chmod 4755 su
# reboot
10) Your phone is now rooted
Click to expand...
Click to collapse
How can this be done through adb ? if you can't load-flash hard-spl or the engineered one ? It states E:No signature
Please read the directions
You must have the Hard SPL,Engineering SPL or a Fastboot enabled SPL for this to work. Try the file I have linked to at the bottom of this post. It is a production signed SPL and has the proper non-test keys so should be able to flash as stock firmware. This SPL is also fastboot enabled.
http://www.filedropper.com/hboot-09500007d2fc780
If it still gives you a key error my method will not work for you (because the first direction I posted is you MUST have an fastboot enabled SPL).
http://www.filedropper.com/hboot-09500007d2fc780
semyazza said:
You must have the Hard SPL,Engineering SPL or a Fastboot enabled SPL for this to work. Try the file I have linked to at the bottom of this post. It is a production signed SPL and has the proper non-test keys so should be able to flash as stock firmware. This SPL is also fastboot enabled.
http://www.filedropper.com/hboot-09500007d2fc780
If it still gives you a key error my method will not work for you (because the first direction I posted is you MUST have an fastboot enabled SPL).
http://www.filedropper.com/hboot-09500007d2fc780
Click to expand...
Click to collapse
Thanks for the link. Still can't flash.
can anyone confirm this works?
Worked for me
This procedure worked for me. I took the JF 1.43 recovery image from http://code.google.com/p/android-roms/
Worked perfect running gfh_eu CRB43 all OTA updated
I don't understand the point of this... As long as your running the official ADP image or a JF ROM you shouldn't have lost root in the first place. Since the OTA update doesn't include a new SPL you can still downgrade to RC29 and use the root bug to update to 1.5.
Am I missing something?
I believe the official ADP images do not come by default with root enabled any more. I could be wrong though.
Datruesurfer said:
I don't understand the point of this... As long as your running the official ADP image or a JF ROM you shouldn't have lost root in the first place. Since the OTA update doesn't include a new SPL you can still downgrade to RC29 and use the root bug to update to 1.5.
Am I missing something?
Click to expand...
Click to collapse
Yes, I followed the instructions to update to Haykuro 6.0.
Flashed radio first,then spl, then firmware.
I now have no root and can only downgrade to rc29 through recovery and flash dream. I cannot flash anything ! Cannot flash the recovery.test keys. Am stuck on the ota cupcake( the only file I can flash).
Any suggestions. I downgraded and rooted several times. Still cannot flash anything.
Datruesurfer said:
I don't understand the point of this... As long as your running the official ADP image or a JF ROM you shouldn't have lost root in the first place. Since the OTA update doesn't include a new SPL you can still downgrade to RC29 and use the root bug to update to 1.5.
Am I missing something?
Click to expand...
Click to collapse
Why would you want to have to reflash your phone twice? Your chips CAN wear out from repeated unnecessary flashing. You will also have to install a modified build then (see below).
techvd said:
I believe the official ADP images do not come by default with root enabled any more. I could be wrong though.
Click to expand...
Click to collapse
Techvd is correct. The new google production ADP images do not allow you to SU to a root prompt. ADB still works but it is kind of pointless without root access. I prefer the least modified firmware possible as it is much more stable than the custom roms (although that is getting less and less true).
I had just updated to the newest hero rom and for some reason i lost root. I followed your step except for the recovery image part because i already had it on my phone, thanks for the instructions!!!
why it doesn't works for me? I have the SPV thing, and the haykuro SPL. when I press camera and power, after a very fast sliding of messages telling me that a don't have this this and this (but in my sd, on root, there are the dreaming.* and the recovery.img from JF 1.43 files), I got a screen telling
Dream PVT 32B ENG S-off
HBOOT-1.33.2005 (DREA1100)
CPLD-4
RADIO 2.22.19.26I
Apr 20 2009, 15.30:43
HBOOT
<BACK> FastBoot Mode
by pressing <Back>
I obtain the following screen:
FASTBOOT (evidenced in red)
<Camera step2> hboot mode
<Send> reset device
<Action> Restart to HBOOT
<Menu> Power down
So how to enter if fast boot mode? I'm really missed up! any help?
iso67 said:
I obtain the following screen:
FASTBOOT (evidenced in red)
<Camera step2> hboot mode
<Send> reset device
<Action> Restart to HBOOT
<Menu> Power down
So how to enter if fast boot mode? I'm really missed up! any help?
Click to expand...
Click to collapse
You are already in fastboot mode. You need to flash the recovery image to the phone now. Open a terminal window and use the command:
Code:
fastboot flash recovery [i]/path/to/JF_recovery.img[/i]
Then, press MENU on the phone, and it will reboot. Reboot the phone into recovery mode (HOME+POWER), Alt+X at the log screen, and then enter those commands.
Why fastboot? Use ADB
I don't understand why there's the need to change the recovery image or use fastboot at all. You can do this from ADB.
Code:
$ adb remount
$ adb shell
# cd /system/bin
# cat sh > su
# chmod 4755 su
# reboot
($ and # are terminal prompts, not to be entered on the command line)
rpcameron said:
You are already in fastboot mode. You need to flash the recovery image to the phone now. Open a terminal window and use the command:
Code:
fastboot flash recovery [i]/path/to/JF_recovery.img[/i]
Click to expand...
Click to collapse
but how to enter this command from this screen? I don't know how to open a terminal windows from here (I know how to open it from the telefon properly powered on)
Then, press MENU on the phone, and it will reboot. Reboot the phone into recovery mode (HOME+POWER), Alt+X at the log screen, and then enter those commands.[/QUOTE]
whenb to run those commands?
Has anoyne else tried running the recovery.img (JF 1.43) from the fastboot on the new Rogers Dream phones?
Mine just displays the Rogers text and logo, but never boots into the recovery mode.
I got it!
I didn't perfom the the recovery.img part, since I already have the JF 1.43, and since I didn't understand the process!
I didn't just the second part and it worked!
thanks
rpcameron said:
I don't understand why there's the need to change the recovery image or use fastboot at all. You can do this from ADB.
Code:
$ adb remount
$ adb shell
# cd /system/bin
# cat sh > su
# chmod 4755 su
# reboot
($ and # are terminal prompts, not to be entered on the command line)
Click to expand...
Click to collapse
And what do you do when you are running a Google/T-mobile production ROM instead of a user debug? I CAN guarantee you that will not work. Also, you are not changing the recovery image on the phone (as stated in the directions). You are simply booting from the modified recovery image on your computer.
outsider787 said:
Has anoyne else tried running the recovery.img (JF 1.43) from the fastboot on the new Rogers Dream phones?
Mine just displays the Rogers text and logo, but never boots into the recovery mode.
Click to expand...
Click to collapse
There seems to be an incompatibility with the Rogers Phone and the Recovery images that we currently have. If anyone has a NAND dump of the *stock* boot, recovery, and System images for the rogers Phone I'll give it a go and try to get a modified recovery working.
I have HTC Panache. I tried to install Ice Cream Sandwitch on my Phone
http://forum.xda-developers.com/showthread.php?t=1341847&page=17
The phone rebooted using ROM manager. it was extracting. I believe I pressed the power button. Anyways, the phone rebooted and now its just showing the MI logo and a sound that indicates that its a new rom but doesnot goes futher..
I tried to reboot using adb . But when I go into the Clockwork mod recovery, it just shows a hat with a yellow round arrow underneath it. My Clock work mod recovery version is 5.0.2.0
Just discovered
My version is as follows. Is it some thing to be worried ?
<6>[ 6.091674] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.
chem.manish said:
Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.
Click to expand...
Click to collapse
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devices
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.
saranhai said:
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devces
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.
Click to expand...
Click to collapse
Correction, first command should be-
fastboot devices
Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command
ahaseeb said:
Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command
Click to expand...
Click to collapse
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium
saranhai said:
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.
He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.
Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
Tez MyTouch said:
Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
Click to expand...
Click to collapse
eng bootloader you can use fastboot with, and you can change more stuff.
correct me if i'm wrong...
chem.manish said:
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.
Click to expand...
Click to collapse
You mean I should follow all the steps of rooting once again ?
Jack_R1 said:
He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.
Click to expand...
Click to collapse
So you mean, I should install bootloader using adb again ?
What was the command flash ... ?
When I type reboot recovery, it goes into the bootloader and a phone appears.. Thats all
When your phone is booting, run "adb shell" and watch. The "#" sign should appear.
If the shell stays and doesn't drop out when the phone is bootlooping (the sign is still there after 2-3 minutes) - you're good to go.
WARNING: YOU'LL BE FLASHING BOOTLOADER. WRONG MOVE - AND YOUR PHONE IS A BRICK.
Since you're already running a rooted OS, "adb shell" should present you with "#" sign.
The thread below has steps to flash engineering bootloader. Don't use those steps, but download the bootloader and check the md5sum (do me a favor and don't ask how to do it, simple googling will spill you 200000000 answers). Put the bootloader into your ADB directory.
http://forum.xda-developers.com/showthread.php?t=858996
Direct link to the file: http://www.megaupload.com/?d=NN5726Z8
md5sum: df4fd77f44993eb05a4732210d2eddc6
Now, to flash engineering bootloader while you're in the ADB root shell, use these steps:
Open Windows' Command prompt in the ADB directory (DO NOT enter ADB shell yet!).
Type (EXACTLY as below):
adb push hboot_dhd.nb0 /data/local/
adb shell
("#" should appear)
cd /data/local/
dd if=hboot_dhd.nb0 of=/dev/block/mmcblk0p18
You should see something like: 2048 bytes in 2048 bytes out 1048576 bytes copied blah blah blah
Now reboot into bootloader, see that you have 0.85.2007 version, enter FASTBOOT mode (select FASTBOOT with volume keys and press power button), and from there you can follow the suggestion above to fastboot flash the recovery, or anything you want.
And on the side note: you won't see any ICS in MIUI that you've attempted flashing. You should have read the thread - it clearly says "all the ICS changes are under the hood, visually it's just a regular MIUI".
I do not see # sign when i type adb shell..
Means I have to root again ?
What do you see? "$"?
In that case, try typing "su" and see if it brings you root.
If it doesn't - you can try to achieve temp root like when downgrading, using fr3vo.
For instructions - section "gain temp root" from the following thread:
http://forum.xda-developers.com/showthread.php?t=1178912
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.
this link returns me error
an error occured while running the exploit <-1> errno 25..
Probbaly because its already exploited may be ?
I am stuck and confused..
Dont know what to do :S
Jack_R1 said:
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.
Click to expand...
Click to collapse
This.
Please google up "mt4g return to stock" or "mt4g apply pd15img", I'm sure there are enough guides to find.
Though applying pd15img.zip is pretty simple, there is even a simpler way for you to return to stock - just find the panache ruu executable in dev section, connect your phone to pc and run that exe.
Is this the file you are referring to ?
http://dl.dropbox.com/u/25823285/RUU...466_signed.exe
I have heard about phones being bricked. So do I need to be extra careful ?
It worked. Great. Now I am on HTC Sense. 2.1 !
Sounds great
Now should i start from zero again ?
Originally posted in here
Click to expand...
Click to collapse
Okay, I tried the taco root exploit as suggested here.
Since I'm new to Android, the process was a little vague for me. Finally managed to get it done properly after reading through I really don't know how many pages here on this forum and google searches. Didn't wanna risk a brick, lol.
I've just written down the step by step procedure if someone like me needs the help.
1st off, my device is a Sensation running 2.3.4 OTA stock, unrooted/ untouched and Revolutionary fails to S-off this phone.
Edit: Just got a brand new Sensation Xe where I faced the same problem, no OTA etc (I unpacked the phone), but Revolutionary S-OFFstill fails. Tried the same methode below and it is S-OFF now. Screenshot of the new phone below:
DISCLAIMER
Using the following method might void your warranty.
I am not responsible if following this method results in bricking your phone.
Whatever you do is at your own risk
You'll need the tacoroot.bin file (I got mine from the htcsupertool v3 zip)
ADB set up.
HTC drivers. I used the HTC v 3.0.0.007 drivers.
Copy/move the tacoroot.bin file to a folder and open a command window from there or move it to the Android SDK/ tools folder (my set up) and navigate there from a command window depending on how you have ADB setup.
Run the following adb commands.
Code:
adb push tacoroot.bin /data/local
adb shell chmod 755 /data/local/tacoroot.bin
adb shell /data/local/tacoroot.bin --setup
The phone will reboot to recovery.
Press Volume Up, Volume Down and Power.
Reboot.
Press the Power button once if the screen remains blank (dark).
Wait for boot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin --root
The phone will reboot.
Run Revolutionary.
Once Revolutionary is successful, reboot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin –-undo
Done. Go ahead with custom recovery etc. I did not install any custom recovery with Revolutionary as I didn't want to risk anything. Someone better equipped folks might be able to say if that would disrupt the whole process.
I've installed ARHD 6.5.1 XE on this Sensation now, no issues. It's a friend's phone, my own XE is running the same without all this drama )
Note: Shamelessly copied bits and parts from all over the forum and the net. Thanks to everyone here and no offense if something has been taken from someone without acknowledgement.
Warnings and Disclaimers
TacoRoot may void your warranty. This is not an s-off/unlock, but a temporary root method – and an unstable one at that (note, however, that it’s technically a “quasi-perm” root in that your phone will stay rooted after you pull the battery). Your phone will be unstable until the undo parameter is used, and may not fully boot. ADB, however, will come up as root.
If your phone breaks as a result of this exploit, neither Android Police nor Justin Case can be held liable.
Edit: I corrected the command line to undo tacoroot, thanks to mathrania's post below.
Thanks for the guide... just a comment:
Instead of : adb shell /data/local/tacoroot.bin –undo
it should be: adb shell /data/local/tacoroot.bin ––undo
I just died trying the first command
thanks..
now i see.. it must be double dash..
i didnt know that. i will try to root again..
can i install clockwork after s-off?
will this work for hboot 1.27 S-on?
bestmodel03 said:
will this work for hboot 1.27 S-on?
Click to expand...
Click to collapse
No cus u cant run revolution on 1.27
1st off, my device is a Sensation running 2.3.4 OTA stock
Click to expand...
Click to collapse
fuel3100 said:
now i see.. it must be double dash..
i didnt know that. i will try to root again..
can i install clockwork after s-off?
Click to expand...
Click to collapse
Sure, you can. I'm using 4EXT Touch Recovery though.
Brilliant Baba! kewl method... Salute Forever_n00b
ty so much....
was suffering A LOT!!!!
Awesome
Works perfectly for HTC SEnsation XE with Hboot1.18...
Thanks mate... Tacoroot ROCKZ...!!
Installing ROM now..
Success
Successfully S-Off using Tacoroot on my Sensation HBoot 1.18.0000
Thank you very much Forevernoob!
Phollux said:
Successfully S-Off using Tacoroot on my Sensation HBoot 1.18.0000
Thank you very much Forevernoob!
Click to expand...
Click to collapse
Same for me, worked great.
after adb shell /data/local/tacoroot.bin --root command, my phone now boot loop on bootanimation i don't know what should i do...
echbel said:
after adb shell /data/local/tacoroot.bin --root command, my phone now boot loop on bootanimation i don't know what should i do...
Click to expand...
Click to collapse
Mee too, how is it going?
drcrazy91 said:
Mee too, how is it going?
Click to expand...
Click to collapse
while on boot loop, i've connected phone to pc and started revolutionary tool, it completed the command succesfully
echbel said:
while on boot loop, i've connected phone to pc and started revolutionary tool, it completed the command succesfully
Click to expand...
Click to collapse
I also ran revolutionary while on boot loop and it completed successfully. However after that im now stuck in boot loop and am unable to run the --undo command. I've tried running the --undo command while in boot loop but it dosnt seem to help.
Sometimes it will make it to the wallpaper for a few seconds then just reboot again..... Anyone know how i can fix this?
just some additional info: revolutionary definately worked. It shows S-OFF in fastboot on Hboot 1.17.1111
I dont think im not bricked but i just need some assistance getting things back on track!
jez151 said:
I also ran revolutionary while on boot loop and it completed successfully. However after that im now stuck in boot loop and am unable to run the --undo command. I've tried running the --undo command while in boot loop but it dosnt seem to help.
Sometimes it will make it to the wallpaper for a few seconds then just reboot again..... Anyone know how i can fix this?
just some additional info: revolutionary definately worked. It shows S-OFF in fastboot on Hboot 1.17.1111
I dont think im not bricked but i just need some assistance getting things back on track!
Click to expand...
Click to collapse
Let the phone reboot and in the mean time run the adb from pc and do the undo command
(you can verify the phone is connected or not using "adb devices")
Sent from my pyramid.. Through blazing fast sonic waves
ganeshp said:
Let the phone reboot and in the mean time run the adb from pc and do the undo command
(you can verify the phone is connected or not using "adb devices")
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Yeah I've done this now so i assume it has worked. It Unfortunately hasnt fixed the problem.
Any other ideas?
EDIT: ok i mangaed to get clockwork on the phone and I'm rocking insert coin no worries. Thanks for your reply.
In November, I helped my friend unlock and root his T-Mobile HTC One S using Hasoon's All-In-One-Toolkit.
He left the ROM as stock, and hasn't uninstalled any apps or bloats.
A couple weeks ago he got the OTA message to update. When he hits the notification to proceed with the update, the following happens:
phone resets
clockwork mod recovery v5.8.3.1
finding update package...
e: unknown volume for path [internals dcard: download/OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.10-1.84.531.2_release_2978576yp8mjiw19tsxxey.zip]
e: can't mount INTERNAL SDCARDownload/OTA(tons of numbers).zip
His current software version is 1.84.531.2.710ORD, and he's on Android 4.0.3.
What needs to be done to enable the OTA update? I'm not near him, but I can talk him through it with Skype. I'm just not used to the HTC environment and terminology.
All he needs is to relock bootloader and install stock recovery, here is a link to download it from my dropbox..
http://db.tt/YTK06p9b
how to install stock recovery
Can you please explain how to relock the bootloader and how to install the stock recovery.
shadowch31 said:
All he needs is to relock bootloader and install stock recovery, here is a link to download it from my dropbox..
Click to expand...
Click to collapse
espaniol said:
Can you please explain how to relock the bootloader and how to install the stock recovery.
Click to expand...
Click to collapse
shadowch31 said:
All he needs is to relock bootloader and install stock recovery, here is a link to download it from my dropbox..
Click to expand...
Click to collapse
Put the phone into bootloader.
Type in the following command in a command shell, opened in the adb directory: fastboot oem lock
espaniol said:
Can you please explain how to relock the bootloader and how to install the stock recovery.
shadowch31 said:
All he needs is to relock bootloader and install stock recovery, here is a link to download it from my dropbox..
Click to expand...
Click to collapse
Your friend will need to have the phone drivers installed and an adb/fastboot folder set up (similar to the "data" folder from Hasoon's All-In-One-Toolkit with fastboot, adb, etc.). Get the phone to the bootloader then go to fastboot mode and connect the USB (it should say "fastboot usb"). Now flash the stock recovery by running the following command in the terminal:
Code:
fastboot flash recovery stock_recovery.img
then lock the bootloader with this command:
Code:
fastboot oem lock
as Raptylos suggested
Click to expand...
Click to collapse
I have found that revone s-off originally for the HTC One/Droid DNA works on the One S. You MUST be rooted for this to work. Super CID is NOT required. I do NOT take any credit for this, I just want to bring it to your atention. All the credit goes to @ieftm who made this tool.
HTC One revone s-off link: http://forum.xda-developers.com/showthread.php?t=2314582
HTC Droid DNA revone s-off link: http://forum.xda-developers.com/showthread.php?t=2314706
NOTE
Please do not ask me if this works on any other firmware other than 3.16.401.8/9. Unfortunately I cannot tell you or test it with your firmware. Please try it at least and if it WORKED, comment below and I will add it to the list below.
CONFIRMED working on:
3.16.401.8/9 WWE
If you are not rooted or on stock rom you can root by downloading Kingo Android Root from here. You need a Windows PC or a Mac/Linux running Wine Windows Program Loader
Instructions
1. Download revone here.
2. Connect your phone with USB Debugging On and open a Command/Terminal window.
3. cd to the folder containing revone.
4. Type in the following:
Code:
adb push revone /data/local/tmp/
adb shell
cd /data/local/tmp/
chmod 755 revone
5. Prepare your phone by typing:
Code:
./revone -P
6. If you get a message saying "success" then proceed to step 7.
**If your phone reboots then wait 2 minutes and try again from step 3.
**If you are told to reboot then do so and try again from step 3.
**If you get an error and your phone does not reboot or if you are not told to reboot then you can try step 7 but not guaranteed to work.
7. To s-off using revone type in:
Code:
./revone -s 0 -u
8. If it reported success type in:
Code:
exit
adb reboot bootloader
9. You should now see s-off. If not try again.
10. Here are some OPTIONAL commands:
Code:
./revone -u (Unlocks the bootloader)
./revone -l (Locks the bootloader with locked message)(Important for warranty reasons)
./revone -r (Relocks the bootloader with relocked message)
./revone -t (Removes the tampered message)
Please hit the thanks button here and here if this helped.
Good to have a another option
Sent from my One S using Tapatalk
at least now we can unlock bootloader without htcdev or losing data, i've tested all of the commands myself and can confirm they all work
Does this work with 3.16.401.9?
it should, i tried it with 3.16.401.8 and please tell me if it does work
is superCID required for this?
dd98 said:
at least now we can unlock bootloader without htcdev or losing data, i've tested all of the commands myself and can confirm they all work
Click to expand...
Click to collapse
I may have missed something out but, how can you be root (to use revone s-off) without htcdev?
@twist3d0n3 its not
@Bricolo_fr i added program called kingo android root which supports the htc one s and doesnt require a bootloader unlock
i get 'unable to open revone: permission denied' when doing the chmod 755 revone command... what do?
after adb shell type su and try again
aye that gets past it, thanks.
when i run ./revone -P it says failed (code 1).
i carried on based on what the OP says, says successful but still won't s-off on reboot. tried 4 times now and still the same
twist3d0n3 said:
i get 'unable to open revone: permission denied' when doing the chmod 755 revone command... what do?
Click to expand...
Click to collapse
I assume you're doing it straight from the phone, so try the "su" command before you start all the other commands (which is done by simply typing in "su".)
I have aquestion of my own also... On the "./revone -P" command, I get a "revone failed (error code = 1)". What do I do about this? I'm trying to do it straight from the terminal emulator by he way.
Speeder975 said:
I assume you're doing it straight from the phone, so try the "su" command before you start all the other commands (which is done by simply typing in "su".)
I have aquestion of my own also... On the "./revone -P" command, I get a "revone failed (error code = 1)". What do I do about this? I'm trying to do it straight from the terminal emulator by he way.
Click to expand...
Click to collapse
You haven't read too much from those links in OP aren't you? If you have done that, you've noticed that the same error was discussed there as well. Shortly, you are either on the wrong ROM to try revone or you should reboot till it works. If after rebooting several times you got the same error, then you might need to flash first a ROM as close to stock as possible... Viper could be an option but I'm not sure cause I didn't try
Sent from nowhere over the air...
Rapier said:
You haven't read too much from those links in OP aren't you? If you have done that, you've noticed that the same error was discussed there as well. Shortly, you are either on the wrong ROM to try revone or you should reboot till it works. If after rebooting several times you got the same error, then you might need to flash first a ROM as close to stock as possible... Viper could be an option but I'm not sure cause I didn't try
Sent from nowhere over the air...
Click to expand...
Click to collapse
I DID read those links. Tried about 4 different ROMS, two of which were Sense-based. Oddly enough, Viper is a ROM I haven't tried yet... I'll do that
Speeder975 said:
I DID read those links. Tried about 4 different ROMS, two of which were Sense-based. Oddly enough, Viper is a ROM I haven't tried yet... I'll do that
Click to expand...
Click to collapse
OK, sorry I presumed wrongly...try Viper also. I remember in the first days of the S-Off "thing",, it was one of the ROMs of choice for starting this. I was never trying S-Off since I don't needed but I've read alot about it and the ways of achieving it.
This looks like the perfect solution to get S-OFF without losing all my data. But I can't even get root with Kingo. It tells me "Root Failed! The current status of your device is S-ON, please go to "Tools"=>"HTC UnlockBootloader" to unlock it to S-OFF and try again." I know this is the wrong thread for Kingo questions, but maybe someone on his way to S-OFF has solved the problem? Btw: Where is this "Tools" menu?
I'm stuck in an endless loop here
tried this a few times on my stock (rooted) backup and still no go... says failed at both bits that start ./revone
FraBle said:
Does this work with 3.16.401.9?
Click to expand...
Click to collapse
Read OP
hi i got this message after step 5
Gaining root access (thanks to Dan's motochopper)...Segmentation fault
139|[email protected]:/data/local/tmp $
whats the problem.