The hope of this thread is to centralize downgrade questions and also make the resources more accessible.
It is important to know your status.
-are you stock ota
-are you htc dev unlock hc
-are you s off hc
If you can not figure this out, god help you. To figure this out get into hboot the top will say
-s on
-unlocked
-s off
Don't know how to get into hboot? Wow! Novice. Hold power and volume down until flyer boots into white screen with androids on skateboards. Ta da!
Now that we know our status how do you downgrade? I take no credit for any of these methods.
Ota stock hboot
http://forum.xda-developers.com/showthread.php?t=1428104
Htc dev unlock
http://forum.xda-developers.com/showthread.php?t=1307759
S off hc
Third post of this thread
http://forum.xda-developers.com/showthread.php?t=1358758
If you have a question ask here or downgrade thread, do not start your own thread. Read the other questions asked first, the hope is that after a little while most scenarios will be covered. If a question is repeated multiple times it will be ignored.
Why bother doing this? I have an odd compulsion to help. I remember when I got my first android device and I rooted it and deleted gtalk. My market stopped working. I went into newbie panic and others helped me even though my issue was pathetic. I remember what that felt like and how cool it was that someone helped me. So, I hope this helps
Need help
Hello,
After a few weeks trying I still have problems downgrading to GB.
My Flyer is Relocked and S-on.
HTC__001
Softwareno. 3.55.1114.31
S-on
HBoot 1.11.0011
Radio-3822.10.08.07_M
I have the following RUU: RUU_Flyer_HTC_WWE_Wifi_2.27.1114.31_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204727_signed
I have used Globatrons guide.
The problem appears when I type the command:
adb shell /data/local/tacoroot.bin --root
I get the following message:
cannot create /data/local.prop: permission denied
And after this i cannot go on.
Can someone tell me what to do, I think I have tried everything now.
thx Driesman
*EDIT: globatron has already mentioned this, but just to confirm, it does not work if you have already unlocked your bootloader through htcdev.com. it does not work if you have obtained CWM recovery through htc unlock. it does not work if you have root through htc unlock. it will only work if you have unmodified stock HC. at least this was my experience.
Have you unlocked before?
I have unlocked and relocked the flyer.
Globatron has to guides; one with unlocked and one with locked flyer.
Is there another way to go back to GB?
I think you should unlock your hboot again. Flash a recovery and super user. Then follow the thread I linked in the op for htc dev unlock
Okay I will try.
Can you tell me step by step how to do: "I think you should unlock your hboot again. Flash a recovery and super user"
Maybe I am doing something wrong.
Follow this site to unlock bootloader
http://htcdev.com/bootloader/
Then get into fastboot mode, I assume you have adb and fastboot commands on your PC. Place this in same folder as command
https://www.box.com/shared/9bb9ba944ea6f301afe8
Open commands on PC then enter command
Fastboot flash recovery "name of file you downloaded"
Place this on your external SD
https://www.box.com/shared/b51a527355d7fba5dca3
Get into recovery and select install zip from Sd. Select this file
Flyer
Everything seems to work ok until I type the following command:
adb shell
$ su
# chmod 777 /data/local/misc_version
# /data/local/misc_version -s 2.27.1114.31
Then I get the error below:
D:\Adb>adb shell
$ su
# chmod 777 /data/local/misc_version
# /data/local/misc_version -s 2.27.1114.31$ $ su
$: permission denied
$ # chmod 777 /data/local/misc_version
$
See also uploaded screenshot
Am I doing something wrong?
What to do now?
You flashed super user in recovery
Flyer
Is that a question?
Yes.
Yes I did.
Can I copy, paste the command below or do I have to run each line seperately?
adb shell
$ su
# chmod 777 /data/local/misc_version
# /data/local/misc_version -s 2.27.1114.31
Each line seperate
Make sure when you enter in su to have your flyers screen on and to allow sufficient access when prompted
Flyer
Yes, I think it is working now??
See attachment
Now I will try to finish it....
The next step is to Reboot to fastboot.
Do I have to enter the command (adb reboot bootloader) into the dos screen or do I choose the option on the Flyer (REBOOT BOOTLOADER)?
However you want
Flyer
YES........It worked!
After all these hours trying.
How can I thank you?
There is a button for that. Glad to hear it worked. Enjoy
Where is the THANKS button?
Have searched for it before but cannot find it.
Depends if you are using app. Or Web page. no worries
Flyer
Related
This procedure applies to both flyers and view
Required downloads
First download the Gingerbread RUU for your device from this thread.
If you don't have adb and fastboot on your PC
Get fastboot and adb tool for windows here
Get Fastboot and adb for linux here
I don't have a simple bundde for Mac, would welcome a link if anyone has one.
Download my universal misc_version and unzip to obtain the misc_version file.
Download tacoroot
Place both the misc_version and tacoroot.bin files in the same directory as adb
Procedure
Check the version number for your gingerbread RUU
In my example I am using this RUU: RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.08 9BU_3809.05.04.10_M_release_194964_signed.exe
The version is the part highlighted in red.
Boot your flyer up to android if it's not already on, with usb debugging enabled and connect it to the PC.
Run the following adb commands
Code:
adb push tacoroot.bin /data/local/
adb push misc_version /data/local/
adb shell chmod 755 /data/local/tacoroot.bin
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/tacoroot.bin --setup
At this point your device will reboot to recovery
Simultaneously press Volume Up, Volume Down and Power
Reboot your device
Run the following command
Code:
adb shell /data/local/tacoroot.bin --root
Your device will reboot, do not worry if it does not boot fully, it doesn't matter for this procedure, and it is a side effect of this root exploit.
Run the following command:
Code:
adb shell /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]
Note that the number in RED is the version number retrieved in step 1.
Reboot to fastboot:
Code:
adb reboot bootloader
Relock the bootloader:
Code:
fastboot oem lock
Go back to fastboot mode ( lock causes the device to reboot )
Run your RUU ( if on linux or mac, see other similar threads from me on how to RUU on those OSes )
Special Thanks
jcase for the tacoroot.
s*** too late!!!!
Yesterday I unlocked my Tab via HTC Unlock, hopefully I'll never need the warranty ...
But thanks for your detailed and very helpful instructions in this forum, don't know where I would be without you.
globatron said:
7. Run the following command:
Code:
adb # /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]
Click to expand...
Click to collapse
I think there is a mistake, it should be:
Code:
adb shell /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]
But: it doesn't work. The device hangs in the boot process after flashing the RUU.
Tutmanichtun said:
I think there is a mistake, it should be:
Code:
adb shell /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]
But: it doesn't work. The device hangs in the boot process after flashing the RUU.
Click to expand...
Click to collapse
The typo correction is correct but that it doesn't work is not. I've done this multiple times with both my own and other peoples devices and it works just fine. Make sure you used a gingerbread RUU and the it flashed completely. AND that you not doing this on an S-OFF device.
globatron said:
AND that you not doing this on an S-OFF device.
Click to expand...
Click to collapse
Thats the fault. My Flyer is S-OFF. Is there a possibility to get back to GB anyway?
Edit: Found a Solution. It cost me the whole day, but now it works.
The bad note: I don't know the Link with the solution. But it was in this Forum.
I got to it by Flashing a 3.2.1 ROM, and after that a 2.3.4 ROM via Goldcard-Method. (Via the SD-Card.)
During the process the Bootloader creates a message, that the installed hboot version isn't downgradeable or something like that. I hacked that into Google and it throws out a Thread in this Forum with the Solution.
Might be a little off topic, but the title:
[Pocedure]No HTC unlock HC-GB downgrade for official HC OTA
"[Pocedure]" is missing a letter r
echaru said:
Might be a little off topic, but the title:
[Pocedure]No HTC unlock HC-GB downgrade for official HC OTA
"[Pocedure]" is missing a letter r
Click to expand...
Click to collapse
Cool. someone who actually reads
Thanks echaru, fixed.
Im on the HC leak - can I use this method flash the RUU for US WIFI HC Release or do I need to go back to GB first?
Back to gingerbread I believe is your only option
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
Back to gingerbread I believe is your only option
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
That's Correct.
Tutmanichtun said:
Thats the fault. My Flyer is S-OFF. Is there a possibility to get back to GB anyway?
Edit: Found a Solution. It cost me the whole day, but now it works.
The bad note: I don't know the Link with the solution. But it was in this Forum.
I got to it by Flashing a 3.2.1 ROM, and after that a 2.3.4 ROM via Goldcard-Method. (Via the SD-Card.)
During the process the Bootloader creates a message, that the installed hboot version isn't downgradeable or something like that. I hacked that into Google and it throws out a Thread in this Forum with the Solution.
Click to expand...
Click to collapse
What you say does not make sense to me. This thread specifically says this is for official HC upgrade which implies you have to be S-ON and locked.
If you are S-OFF you need to follow Globatron's other thread http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
cnewsgrp said:
What you say does not make sense to me. This thread specifically says this is for official HC upgrade which implies you have to be S-ON and locked.
If you are S-OFF you need to follow Globatron's other thread http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
Click to expand...
Click to collapse
Thats what I said: I've made a mistake.
hi
I try this method ... but something is wrong
adb push msc_version /data/local
error : cannot stat msc_version : No such file or directory
your file is misc_version
rename misc_version to msc_version? or ?!
plz help
nader1450 said:
hi
I try this method ... but something is wrong
adb push msc_version /data/local
error : cannot stat msc_version : No such file or directory
your file is misc_version
rename misc_version to msc_version? or ?!
plz help
Click to expand...
Click to collapse
Typo in the procedure, fixed now.
Hi
I followed the instruction and at this point:
adb shell /data/local/misc_version -s 2.00.405.3
I have a message: error opening input file.
I assume it is for the RUU.. where do I need to copy the RUU file to my SD or to the same folder where ADB is?
That is not the ruu. It is the misc file and all files should not be on your ad unless you are trying to flash the zip through hboot. They should be in your adv folder
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
That is not the ruu. It is the misc file and all files should not be on your ad unless you are trying to flash the zip through hboot. They should be in your adv folder
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Thx for your answer. I have the misc file in the ADB folder the sameone I downloaded from the instruction.. any other idea?
Right the whole message is after I enter the command:
Finding misc partition
misc partition found: /dev/block/mmcblk0p28!
backing up misc partition to /data/local/miscBackup-1325954343.bin and determing
version length...
Error opening input file.
You failed to get root with tacoroot.
Start again from the last command in step 3.
globatron said:
You failed to get root with tacoroot.
Start again from the last command in step 3.
Click to expand...
Click to collapse
I think this would be the problem then after i run this:
C:\Android>adb shell /data/local/tacoroot.bin --root
Rebooting into root.
cannot create /data/local.prop: permission denied
globatron said:
Type in the procedure, fixed now.
Click to expand...
Click to collapse
thanks
i try again ... but:
adb shell /data/local/misc_version -s 2.27.707.1
have error (i don't remember error but something like that): misc only 11 number but this is 10
any way, restart and come htc boot and didn't go to android.
i flash HC ... and go to android ... but adb cannot connect device
error is: devices not found
i try:
adb kill-server
but still problem
plz help me
This procedure applies to both flyers and view
Required downloads
First download the Gingerbread RUU for your device from this thread.
If you don't have adb and fastboot on your PC
Get fastboot and adb tool for windows here
Get Fastboot and adb for linux here
I don't have a simple bundde for Mac, would welcome a link if anyone has one.
Download my universal misc_version and unzip to obtain the misc_version file.
Download tacoroot
Place both the misc_version and tacoroot.bin files in the same directory as adb
Procedure
Check the version number for your gingerbread RUU
In my example I am using this RUU: RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.08 9BU_3809.05.04.10_M_release_194964_signed.exe
The version is the part highlighted in red.
Boot your flyer up to android if it's not already on, with usb debugging enabled and connect it to the PC.
Run the following adb commands
Code:
adb push tacoroot.bin /data/local
adb push misc_version /data/local
adb shell chmod 755 /data/local/tacoroot.bin
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/tacoroot.bin --setup
At this point your device will reboot to recovery
Simultaneously press Volume Up, Volume Down and Power
Reboot your device
Run the following command
Code:
adb shell /data/local/tacoroot.bin --root
Your device will reboot, do not worry if it does not boot fully, it doesn't matter for this procedure, and it is a side effect of this root exploit.
Run the following command:
Code:
adb shell /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]
Note that the number in RED is the version number retrieved in step 1.
Reboot to fastboot:
Code:
adb reboot bootloader
Run your RUU ( if on linux or mac, see other similar threads from me on how to RUU on those OSes )
Special Thanks
jcase for providing the tacoroot.
Nice release globatron! I was actually looking at Tacoroot for this last night but didn't really want to go into it too much and decided against using it. Glad to see I wasn't the only one with the idea for it though.
heh, Gave jcase the updated misc_version so he has it on the github radme for tacoroot already but didn't want to release the procedure until I has actually tested misc_version to run on at least a few HTC emmc devices and with multiple version string lengths.
Even if you didn't release this today, I probably would have started on it tonight, I'm a bored teenager with too much time. Still, keep up the good work. If you want me to make a script for you or anything, let me know and I'll get to work on it. (also, you know you can actually have adb from the recovery so you dont need to hit the buttons on it, just have it wait then adb reboot (or even adb shell reboot))
Of course I know that but that's not the what the buttons is about here.
What are the points of the button?
Sent by breaking the sound barrier
To ensure with absolute certainty that a log will be created.
Ah, you want the button presses to be logged to ensure it's done the job. Alright, fair enough.
Glad to TacoRoot in use!
Thanks for the spice jcase, just realized I had a typo in the procedure....jcase *provided*, not tested (well that too), tacoroot.
globatron said:
Thanks for the spice jcase, just realized I had a typo in the procedure....jcase *provided*, not tested (well that too), tacoroot.
Click to expand...
Click to collapse
is the typo msc_version being misc_version
thanks Kevin, fixed that.
yep, didnt notice it until someone tried to do my procedure today lol... copy and paste my friend lol. Plus I just need to know one thing. This brings you down to GB but still keeps you locked right? You still technically have to use HTC unlock to bring it back to 1.13.000 correct?
Part1: correct, you've never unlocked if you do this.
Part2: No, you don't have to unlock at all during this procedure.
so to go from the 1.14 hboot to 1.13 u dont need to htc unlock?
kevinrocksman said:
so to go from the 1.14 hboot to 1.13 u dont need to htc unlock?
Click to expand...
Click to collapse
That's correct.
globatron said:
This procedure applies to both flyers and view
Required downloads
First download the Gingerbread RUU for your device from this thread.
the download link takes me to the flyer RUU, i understand the view & flyer are the same except the 3g/4g network on the View. i just want to make sure i download the correct RUU for my View. what verision do i need? this one "RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.0531_NV_2.28_SPCS_release_198141_signed.exe"
agian thank you for the support
Click to expand...
Click to collapse
That one is fine. Express is the board name or the view so an RUU with express (not expresskt) in the name is what you need.
Hello, thanks for the downgrade help. Upgraded to honeycomb and hated it so I followed your instructions and everything went exactly as described until the middle of the RUU upgrade itself where it stopped and gave me an
ERROR[140]: BOOTLOADER VERSION ERROR
The ROM Update utility cannot update your android phone
Please get the correct ROM update utility and try again.
It won't successfully reboot now. When I go back to bootloader mode the recover screen shows
*** LOCKED ***
express pvt ship s-on rl
hboot-1.14.0005
microp-0656
radio-1.05.01.1006_3
emmc-boot
oct 25 2011, 16:35:13
used RUU_Express_Sprint_WWE_1.22.651.1
Its completely stock, was notified of the new update by htc and installed it over wifi. Thanks in advance for any help
What appears to have happened here is that somewhere along the way something didn't work fully and you failed to set the version to the same as or lower than the RUU you used.
I would need to see the output of :
Code:
fastboot getvar version-main
to be absolutely certain of this. If that is the case then becasue you are completely stock the best course of action would be for you to return it for repair. Tell the technical support people that this happened when you tried to take the OTA update to HoneyComb. The alternative will require you to use the HTC unlock.
One month after i bought it, my ShooterU has got a MB replacement (RMA)
And now it's impossible for me to unlock bootloader with the htcdev method.
Is there another way to make it possible (Evo3d with stock ICS) ?
Thank you for helping me, i'm furious with it.
Post in q&a not development !
crossmanbx said:
One month after i bought it, my ShooterU has got a MB replacement (RMA)
And now it's impossible for me to unlock bootloader with the htcdev method.
Is there another way to make it possible (Evo3d with stock ICS) ?
Thank you for helping me, i'm furious with it.
Click to expand...
Click to collapse
HTCDev unlock method doesn't work on phones with replaced motherboards. You're out of luck, sorry.
it's called bad blocks. nothing you can do about it ...
Can't you use juopunutbear and do the wire trick?
00mpollard said:
Can't you use juopunutbear and do the wire trick?
Click to expand...
Click to collapse
I think it's a good idea to try the juopunutbear, but i need to have temp root at least.
And all temp root i find are made for Gingerbread.
Does anyone know a temp root method for ICS ?
Thank you
Questions and non-development related should be posted in the appropriate sections. This thread is not dev related, so I'm moving it.
So there isn't another method to unlock my bootloader ? Htcdev is the only way to do this ? What does it mean ?
My evo 3d is unrootable ? The bootloader still be blocked forever ?
Please help me not to sell it ! Thank you
crossmanbx said:
So there isn't another method to unlock my bootloader ? Htcdev is the only way to do this ? What does it mean ?
My evo 3d is unrootable ? The bootloader still be blocked forever ?
Please help me not to sell it ! Thank you
Click to expand...
Click to collapse
Unless Unlimited.io releases a version of controlbear that works on just temp root, nothing can be done.
Such a method already exists for the HTC Sensation.
kgs1992 said:
Unless Unlimited.io releases a version of controlbear that works on just temp root, nothing can be done.
Such a method already exists for the HTC Sensation.
Click to expand...
Click to collapse
I don't believe there's a temp root technique that works on the Evo 3D anyway, but if you know of one some users here have been looking for it for other reasons, especially one that works with ICS.
The Evo 3D is definitely not the same phone as the Sensation and has different capabilities and limitations.
ramjet73
ramjet73 said:
I don't believe there's a temp root technique that works on the Evo 3D anyway, but if you know of one some users here have been looking for it for other reasons, especially one that works with ICS.
The Evo 3D is definitely not the same phone as the Sensation and has different capabilities and limitations.
ramjet73
Click to expand...
Click to collapse
I agree. Only speculating.
Doesn't TPSparkyRoot work?
Try this:
To root:
Code:
adb shell "rm /data/local/tmp.orig"
adb shell "mv /data/local/tmp /data/local/tmp.orig"
adb shell "rmdir /data/local/tmp"
adb shell "ln -s /data /data/local/tmp"
adb shell "rm /data/local.prop"
adb shell "chmod 777 /data/local/"
adb shell "echo ro.kernel.qemu=1 > /data/local/local.prop"
adb reboot
adb shell "chmod 777 /data/local/local.prop"
adb shell "mv /data/local/local.prop /data/local.prop"
adb reboot
It's okay if the "adb shell rm" or "adb shell rmdir" commands fail.
To unroot:
Code:
adb shell "rm /data/local.prop"
adb shell "rm /data/local/tmp"
adb shell "mv /data/local/tmp.bak /data/local/tmp"
kgs1992 said:
I agree. Only speculating.
Doesn't TPSparkyRoot work?
Click to expand...
Click to collapse
Never heard of that for the Evo 3D. If you can post a link I'll give it a try if it's compatible with the CDMA Evo 3D. Mostly people are looking for it so they can backup a stock unrooted ROM with Titanium Backup before they root and S-OFF.
ramjet73
ramjet73 said:
Never heard of that for the Evo 3D. If you can post a link I'll give it a try if it's compatible with the CDMA Evo 3D. Mostly people are looking for it so they can backup a stock unrooted ROM with Titanium Backup before they root and S-OFF.
ramjet73
Click to expand...
Click to collapse
Instructions are above. But it needs to be tried on LOCKED S-ON E3D.
Temp root is unstable, the only thing you can see on the phone is the statusbar.
You can't use the phone till temproot is removed, only use adb commands.
You can probably adb pull /data & restore it later.
kgs1992 said:
Instructions are above. But it needs to be tried on LOCKED S-ON E3D.
Temp root is unstable, the only thing you can see on the phone is the statusbar.
You can't use the phone till temproot is removed, only use adb commands.
You can probably adb pull /data & restore it later.
Click to expand...
Click to collapse
I'm out of thanks right now, but appreciate your posting that.
Being S-OFF already via JuopunutBear I'm not as anxious to try it since it requires going back to S-ON, but maybe someone who is currently S-ON on an Evo 3D would be willing to test. I'm assuming that it shouldn't matter if the phone is a GSM or CDMA model based on the commands above.
ramjet73
ramjet73 said:
I'm out of thanks right now, but appreciate your posting that.
Being S-OFF already via JuopunutBear I'm not as anxious to try it since it requires going back to S-ON, but maybe someone who is currently S-ON on an Evo 3D would be willing to test. I'm assuming that it shouldn't matter if the phone is a GSM or CDMA model based on the commands above.
ramjet73
Click to expand...
Click to collapse
Yes, that's right, it doesn't matter.
That is basically the TPSparkyRoot exploit, but I've modified it slightly.
Hope it does work.
If it doesn't, whoever tries it, please post the error message.
kgs1992 said:
I agree. Only speculating.
Doesn't TPSparkyRoot work?
Try this:
To root:
Code:
adb shell "rm /data/local/tmp.orig"
adb shell "mv /data/local/tmp /data/local/tmp.orig"
adb shell "rmdir /data/local/tmp"
adb shell "ln -s /data /data/local/tmp"
adb shell "rm /data/local.prop"
adb shell "chmod 777 /data/local/"
adb shell "echo ro.kernel.qemu=1 > /data/local/local.prop"
adb reboot
adb shell "chmod 777 /data/local/local.prop"
adb shell "mv /data/local/local.prop /data/local.prop"
adb reboot
It's okay if the "adb shell rm" or "adb shell rmdir" commands fail.
To unroot:
Code:
adb shell "rm /data/local.prop"
adb shell "rm /data/local/tmp"
adb shell "mv /data/local/tmp.bak /data/local/tmp"
Click to expand...
Click to collapse
i am willing to test this.i have gsm evo 3d with hboot 1.5(OTA ICS),LOCKED S-ON.but i have some questions:
1)when i execute those commands should i be in fastboot usb or just connect the phone in charging mode and with usb debugging checked?
2)if i sucesfully temp root what can i do in order to perm root my phone?
THANKS!!!
johnmarshton said:
i am willing to test this.i have gsm evo 3d with hboot 1.5(OTA ICS),LOCKED S-ON.but i have some questions:
1)when i execute those commands should i be in fastboot usb or just connect the phone in charging mode and with usb debugging checked?
2)if i sucesfully temp root what can i do in order to perm root my phone?
THANKS!!!
Click to expand...
Click to collapse
1) adb access required. Hence, charging mode with USB Debugging enabled.
2) You cannot permanently root without an unlocked bootloader or S-OFF.
kgs1992 said:
1) adb access required. Hence, charging mode with USB Debugging enabled.
2) You cannot permanently root without an unlocked bootloader or S-OFF.
Click to expand...
Click to collapse
then,if i succesfully obtain temp root,what can i do?can i unlock my bootloader,downgrade hboot?what can i do?thanks!
johnmarshton said:
then,if i succesfully obtain temp root,what can i do?can i unlock my bootloader,downgrade hboot?what can i do?thanks!
Click to expand...
Click to collapse
Very little. You can probably make backup of your data.
You can get root access via adb shell. But what you can do is limited.
The most this will establish is whether or not the E3D can be temprooted or not.
kgs1992 said:
Very little. You can probably make backup of your data.
You can get root access via adb shell. But what you can do is limited.
The most this will establish is whether or not the E3D can be temprooted or not.
Click to expand...
Click to collapse
Could he push an "su" binary to the system partition while he has temp root?
ramjet73
Short story is, I got a DNA off of Craigslist for cheap that was stuck in fastboot mode and would not RUU. Its S-ON/Relocked/Tampered. After trying many things, I flashed a 2.06 update zip, and now it boots into a custom ROM that already has working root access. Looks like someone tried to put it back to a stock state but relocked it preamturely.
Now that I am back into a bootable state, neither Revone or Moonshine will work to get S-OFF so I can clean up the mess. Moonshine fails at 'launching temproot -> waiting 10 seconds -> Error; run distiller again' , and Revone auto-reboots after running ./revone.dna -P, and I've tried all the tricks in that thread here. I've factory reset/powered down and tried ad nauseum, with no luck.
My next line of thinking is, since it already has a working root, is it possible to have Moonshine bypass the temproot process? Or is it somehow possible to reflash a stock 2.06 system image? (I know there is no RUU yet.)
Since I did successfully flash the 2.06 update, which would restore the kernel and all that, Any suggestions on what to try next?
[EDIT] SOLVED!! I had to manually supercid and then unlock the bootloader via htcdev (most folks in a similar situation as I was would likely need temproot first.). After, I was able to S-OFF via facepalm.
Big thanks to Zanzibar in freenode #moonshiners for the tip!!
hurrrtin said:
Short story is, I got a DNA off of Craigslist for cheap that was stuck in fastboot mode and would not RUU. Its S-ON/Relocked/Tampered. After trying many things, I flashed a 2.06 update zip, and now it boots into a custom ROM that already has working root access. Looks like someone tried to put it back to a stock state but relocked it preamturely.
Now that I am back into a bootable state, neither Revone or Moonshine will work to get S-OFF so I can clean up the mess. Moonshine fails at 'launching temproot -> waiting 10 seconds -> Error; run distiller again' , and Revone auto-reboots after running ./revone.dna -P, and I've tried all the tricks in that thread here. I've factory reset/powered down and tried ad nauseum, with no luck.
My next line of thinking is, since it already has a working root, is it possible to have Moonshine bypass the temproot process? Or is it somehow possible to reflash a stock 2.06 system image? (I know there is no RUU yet.)
Since I did successfully flash the 2.06 update, which would restore the kernel and all that, Any suggestions on what to try next?
[EDIT] SOLVED!! I had to manually supercid and then unlock the bootloader via htcdev (most folks in a similar situation as I was would likely need temproot first.). After, I was able to S-OFF via facepalm.
Big thanks to Zanzibar in freenode #moonshiners for the tip!!
Click to expand...
Click to collapse
I've got a DNA in the same situation, mind telling me how you manually supercid on the 2.06 firmware?
PhantomApollyon said:
I've got a DNA in the same situation, mind telling me how you manually supercid on the 2.06 firmware?
Click to expand...
Click to collapse
fastboot oem writecid xxxxxxxxx if you have issues with revone, try typing "su" before ./revone -p in shell so it runs as root (if you have root obviously)
Also omitting the "-p" switch might help.
fr4nk1yn said:
Also omitting the "-p" switch might help.
Click to expand...
Click to collapse
Even though this is marked solved in the op, im going to leave this tidbit here as it most likely would have applied here.
adb install dnashellroot.apk
[16:40] <@beaups> then
[16:40] <@beaups> adb shell
[16:40] <@beaups> am start -n c.fyf/.MainActivity
[16:41] <@beaups> wait 10 seconds, then
[16:41] <@beaups> /dev/sh
[16:41] <@beaups> let me know if $ turns into #
[16:41] <maxiixam> k
[16:42] <maxiixam> hah, helps if im not in fastboot =P
[16:43] <@beaups> indeed
[16:43] <maxiixam> don't worry this aint my first rodeo
[16:43] <@beaups> says the guy who went s-on...
[16:44] <Nick> lmfao
[16:44] <maxiixam> every dog has his day.
[16:44] <maxiixam> also next, we got #
[16:45] <@beaups> cool
[16:45] <@beaups> echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
[16:45] <@beaups> ^copy/paste that
[16:45] <@beaups> do NOT screw it up
[16:45] <maxiixam> done
[16:46] <@beaups> ok
[16:46] <@beaups> exit
[16:46] <@beaups> exit
[16:46] <@beaups> adb reboot bootloader
[16:46] <@beaups> fastboot getvar cid
[16:46] == Bowsakirby [[email protected]/web/freenode/ip.69.92.52.209] has quit [Ping timeout: 250 seconds]
[16:46] <maxiixam> all 2222222's just procede to htcdev?
[16:47] <@beaups> yep
[16:47] <@beaups> then use facepalm for s-off
Run this from an elevated cmd prompt where you have un zipped moonshine.
*I am not responsible for what may happen to your phone*
rumrunner s-off is now available for select htc one's, including those that have been previously unexploitable.
brought to you by beaups and fuses
www.rumrunner.us
note:
you MUST be htc dev unlocked or rooted
you MUST have working drivers (windows)
you MUST meet all of the prerequisites
support is available at #rumrunners on freenode and andirc
do NOT clutter support channels with unsupported configurations
updated version for 2.24.401.8 posted. If you are on this firmware and have been having issues, please remove ALL old versions and download again from rumrunner.us. Sorry for the issues.
Rumrunner custom hboot. Enjoy.
No portion of it may be redistributed, repacked, rehosted, or oneclicked!
S-OFF device is required!!
Features:
Full set of fastboot flash commands
Full set of fastboot erase commands
Full set of fastboot oem commands (eng-hboot command set)
Removes red banner
Removes tampered text
Download here
How to flash:
1) Put your phone in fastboot mode
2) Type the following commands into terminal
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rumrunner_2.24_401.8_hboot.zip
fastboot reboot-bootloader
If you like our work, please donate at rumrunner.us
thread opened.
Just sent a request for Sprint support
Hmmm, so I carefully ensured that I met the requirements and had the right package for my model 224113, I restored a stock TMO twrp backup, and ran rumrunner.
All seemed well until suddenly I encountered the following error during test 3
FATAL: **** IT
Now it's been printing periods in the cmd window for about 15 minutes.
The device is in bootloader.
What is safe for me to do?
S-OFFed yesterday. Thank you for this!
S-OFFed successfully, thank you very much
any way to remove "tampered" flag?
Will you be releasing Custom Hboot for different variants?
zorbakun said:
Will you be releasing Custom Hboot for different variants?
Click to expand...
Click to collapse
+1..
Will this support Hboot 1.55?
I'm unfortunately stuck on that HBoot...
hypocritelecteur said:
Hmmm, so I carefully ensured that I met the requirements and had the right package for my model 224113, I restored a stock TMO twrp backup, and ran rumrunner.
All seemed well until suddenly I encountered the following error during test 3
FATAL: **** IT
Now it's been printing periods in the cmd window for about 15 minutes.
The device is in bootloader.
What is safe for me to do?
Click to expand...
Click to collapse
Disable antivirus/firewall/Windows Defender etc etc. Retry.
Tabtoub said:
S-OFFed successfully, thank you very much
any way to remove "tampered" flag?
Click to expand...
Click to collapse
You can use revone to remote TAMPERED : http://forum.xda-developers.com/showthread.php?t=2314582
You should do BOLD steps:
Instructions
Use any operating system you like, you only need adb.
1. Download revone and push it to your device: adb push revone /data/local/tmp/
2. Open an adb shell and: => command : adb shell
* cd /data/local/tmp
* chmod 755 revone
3. (optional) If your device is unlocked and rooted please switch to root using su.
4. Prepare to gain S-OFF by running the command: ./revone -P
4a. If revone reports success reboot the device and proceed to step 5)
4b. If revone reboots the device (we'll pretend this isn't an undiagnosed random crash) please wait 2 minutes then try again from step 2.
4c. If revone reports that you need to reboot and try again please reboot and try again from step 2.
5. Now that revone has successfully prepared your device for S-OFF please open another adb shell (as per step 2) and change to
the /data/local/tmp directory.
6. Instruct revone to grant you S-OFF and unlock status by running the command: ./revone -s 0 -u
6a. Other optional command arguments:-
* -u - Unlock the device
* -l - Lock the device (as if it was never unlocked)
* -r - Relock the device (mark the device as relocked)
* -t - Reset the device's tamper flag.
7. Presuming revone reported success please reboot the device again, this time to the bootloader (adb reboot bootloader)
8. You should now observe your device is S-OFF (and the lock status changed if you invoked that option).
9. (optional) Re-run revone to remove TAMPERED from your HBOOT screen: ./revone -t
Click to expand...
Click to collapse
Does it works on Viper 2.7.0 sense based Custom ROM with build 2.24.401.1? Becase I lost my nandroid backup for last OTA 4.2.2 update
My HTC One Is International version
Asia WWE Version
Unlocked via HTCDev.com
Sent from my HTC One using xda premium
@acank46.mh I S-OFF'd with ViperOne 2.6.0, so 2.7.0 should be fine.
---------- Post added at 12:33 PM ---------- Previous post was at 12:33 PM ----------
@balla786 It will work on 1.55.
acank46.mh said:
Does it works on Viper 2.7.0 sense based Custom ROM with build 2.24.401.1? Becase I lost my nandroid backup for last OTA 4.2.2 update
My HTC One Is International version
Asia WWE Version
Unlocked via HTCDev.com
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thank's Sir
Sent from my HTC One using xda premium
To remove 'Tampered' banner after S-OFF'ing, put this is in terminal emulator
Code:
su
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
Just copy and paste it into terminal to ensure no errors
Credits @scotty1223
Maybe @beaups can put this in the OP to prevent repeat questions?
Got S-Off this AM. Good start to a Monday! Thank you!
Sent from my HTC One using Tapatalk
Got my HTC one s-offed last friday. I was tring to make it work on windows 8.1 but it was impossible to get the fastboot drivers to work. finaly I tried on a different computer with windows 8 and all worked perfectly.
thank you for the hard work.
polys_a said:
Got my HTC one s-offed last friday. I was tring to make it work on windows 8.1 but it was impossible to get the fastboot drivers to work. finaly I tried on a different computer with windows 8 and all worked perfectly.
thank you for the hard work.
Click to expand...
Click to collapse
Ah, so it doesn't work on windows 8.1. Thanks for the tip, I've been trying for two days on 8.1 with no luck so I will try on Windows 8. Thanks.:good: