So I thought it would be better to bring the chatter here rather than further cluttering the S-OFF threads.
Note in my Pre-S-OFF guide in my signature I have a lot of useful info for people wanting to S-OFF.
In case you're on your mobile thinking what guide in signature..... It's Here!
sent by homing Dragon.....
The War Horse said:
So I thought it would be better to bring the chatter here rather than further cluttering the S-OFF threads. Any S-OFF related troubleshooting questions etc should still be posted in the appropriate exploit thread.
Here is a place for us trying to find a way around the new HBoot to discuss ideas and post test results etc.
Note in my Pre-S-OFF guide in my signature I have listed a load of things that are already tried and don't work. As well as the helpful advice to people wanting S-OFF of course.
In case you're on your mobile thinking what guide in signature..... http://forum.xda-developers.com/showthread.php?t=2431515
sent by homing Dragon.....
Click to expand...
Click to collapse
Good idea, and you are the right person to start the thread. Kudos to u.
zaphodbeeb said:
Good idea, and you are the right person to start the thread.
Click to expand...
Click to collapse
Cheers. I am probably the most guilty of filling the S-OFF dev threads with my ideas and trials and thought last night that the poor people that just want to S-OFF using especially revone have to trawl through far too many pages of useless and unnecessary information to find the answers they're looking for. I think it might be a good idea for the mods to have a really good clear out of the threads. Specifically revone to reduce the amount of junk..... Mostly my junk lol.
sent by homing Dragon.....
Ok so as I stated in the revone thread before moving the chat here. I don't know of any way I can upgrade, whilst s-on to the newest hboot. Does anyone know any possible way? CID HTC__001 so think I'm stuck currently.... Sort of puts a spanner in the works for the test lol.
sent by homing Dragon.....
Great initiative man, kudos!
>> Sent from the abyss <<
The War Horse said:
No no you misunderstand I think. We can use a signed firmware with 1.54 hboot inside, rename to PN07IMG.zip and it should work. The hboot needs to start writing then we stop it half way causing it to be corrupt. Then we can use the tool swapping the hboot and misc images inside to ours and downgrade hboot.
sent by homing Dragon.....
---------- Post added at 09:21 AM ---------- Previous post was at 09:09 AM ----------
Oh yeh. May be an issue with me taking the 1.55 plunge. With PM0710000 HTC__001 S-ON device I don't think I can even update it yet.... Unless anyone knows a way?
sent by homing Dragon.....
---------- Post added at 10:14 AM ---------- Previous post was at 09:21 AM ----------
Ok so I decided to start a thread specifically for us trying to find a way round the hboot stuff. Lets leave this thread for troubleshooting and issues relating to revone....
Discussion thread is Located Here!
sent by homing Dragon.....
Click to expand...
Click to collapse
i don't see a way how you want to get to the status writing hboot, every time it fails on hboot checking, it does not even start writing..hm?
If we corrupt hboot we can write over it.... It's corrupting it that's gonna be the hard bit though
Sent from my HTC One using XDA Premium 4 mobile app
The War Horse said:
If we corrupt hboot we can write over it.... It's corrupting it that's gonna be the hard bit though
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
offer it a bribe or some hard drugs
in seriousness though great idea setting this thread up! I will be watching this closely!
Lol. Well most likely we will achieve nothing but worth trying stuff eh.... Long as no-one spontaneously combusts haha.
Sent from my HTC One using XDA Premium 4 mobile app
Maybe we oughtta find a way to upgrade to the 1.55 hboot instead, if what this guy says is true.. What's your input, @The War Horse? http://forum.xda-developers.com/showthread.php?p=46144216#post46144216
Theshawty said:
Maybe we oughtta find a way to upgrade to the 1.55 hboot instead, if what this guy says is true.. What's your input, @The War Horse? http://forum.xda-developers.com/showthread.php?p=46144216#post46144216
Click to expand...
Click to collapse
I don't know how we can upgrade.... But we need to somehow....
Perhaps revolutionary know something about 1.55 that everyone else doesn't...
Sent from my HTC One using XDA Premium 4 mobile app
The War Horse said:
I don't know how we can upgrade.... But we need to somehow....
Perhaps revolutionary know something about 1.55 that everyone else doesn't...
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe we could apply the official OTA's? By reverting to odexed stock with stock recovery, locking the bootloader (for good measure) and then install the OTA when it arrives?
Theshawty said:
Maybe we could apply the official OTA's? By reverting to odexed stock with stock recovery, locking the bootloader (for good measure) and then install the OTA when it arrives?
Click to expand...
Click to collapse
Oh well yeh..... That will work but it means waiting haha....
Sent from my HTC One using XDA Premium 4 mobile app
The War Horse said:
Oh well yeh..... That will work but it means waiting haha....
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Patience, young apprentice!
Theshawty said:
Patience, young apprentice!
Click to expand...
Click to collapse
Haha. I've never had this lol..... I have ADHD so waiting for anything means too much waiting lol....
I'm sat fully stock, unrooted, still unlocked though 2.24.401.8..... It's been a few hours and I'm sick of the wait already haha.
Sent from my HTC One using XDA Premium 4 mobile app
Hi The War Horse & Theshawty,
I have been following your adventures regarding S-Off closely. I have tried everything to get S-Off on 1.54 hboot myself (War Horse our minds work the same way – tried everything you did myself haha). I have also been trying to downgrade the hboot. In regards to your plan to brick the hboot please be careful. I successfully bricked my hboot by entering RUU mode and flashing a firmware.zip with 1.54 hboot (cid and mid matched my phone). I timed it perfectly by holding the power button 1.5 seconds before I ran the “fastboot flash zip firmware.zip” command. The phone reset at exactly the point hboot was writing. The trick was to flash a firmware.zip that includes 1.54 hboot (must be for your phone cid and mid). Anyway, the downside of this is that because the phone was reset while the hboot was writing the phone obviously won’t boot and is stuck in QHSUSB_DLOAD MODE. Anyway if you know how to use QPST maybe you can flash 1.44 hboot that way. I don’t have QPST so my phone is now bricked. No matter, I tried everything else so it was worth a shot.
---------- Post added at 01:24 AM ---------- Previous post was at 01:15 AM ----------
Guys I think you can upgrade using the new DE RUU. You will have to use Windows for this. It will not work with fastboot. There is a way to bypass the cid and mid checks for an RUU. Also since the new RUU has a newer hboot the hboot check won’t fail. To do this you need:
-ARUWizard.exe (get this and the accompanying version of adb and fastboot plus all required config files/dlls etc. from your Windows temp directory when you run the ruu.exe – copy them all to the same directory)
-ROM.ZIP from the 4.3 DE RUU
In the ARUWizard.exe directory update android-info.txt to include your cidnum and modelid num. Then run ARUWizard.exe. The reason this will work is when ARUWizard.exe runs the cid and model id check are performed using android-info.txt and not by reading the phone. These steps should pass now.
If you upgrade this way OTA’s won’t work because your cid and mid won’t match the OTA.
alasdair.grant said:
Anyway if you know how to use QPST maybe you can flash 1.44 hboot that way. I don’t have QPST so my phone is now bricked. No matter, I tried everything else so it was worth a shot.
Click to expand...
Click to collapse
Wow, you made it this far, well done I'll do some research later when I've got time but i did a quick search and found qpst downloads and this: https://www.google.com.au/url?sa=...fNv-IBW_jT3_l4dJWrOMcg&bvm=bv.53537100,d.aGc if that doesn't help just ignore me for the moment, I'll be back later with information
Sent from my HTC One using XDA Premium 4 mobile app
alasdair.grant said:
Hi The War Horse & Theshawty,
I have been following your adventures regarding S-Off closely. I have tried everything to get S-Off on 1.54 hboot myself (War Horse our minds work the same way – tried everything you did myself haha). I have also been trying to downgrade the hboot. In regards to your plan to brick the hboot please be careful. I successfully bricked my hboot by entering RUU mode and flashing a firmware.zip with 1.54 hboot (cid and mid matched my phone). I timed it perfectly by holding the power button 1.5 seconds before I ran the “fastboot flash zip firmware.zip” command. The phone reset at exactly the point hboot was writing. The trick was to flash a firmware.zip that includes 1.54 hboot (must be for your phone cid and mid). Anyway, the downside of this is that because the phone was reset while the hboot was writing the phone obviously won’t boot and is stuck in QHSUSB_DLOAD MODE. Anyway if you know how to use QPST maybe you can flash 1.44 hboot that way. I don’t have QPST so my phone is now bricked. No matter, I tried everything else so it was worth a shot.
---------- Post added at 01:24 AM ---------- Previous post was at 01:15 AM ----------
Guys I think you can upgrade using the new DE RUU. You will have to use Windows for this. It will not work with fastboot. There is a way to bypass the cid and mid checks for an RUU. Also since the new RUU has a newer hboot the hboot check won’t fail. To do this you need:
-ARUWizard.exe (get this and the accompanying version of adb and fastboot plus all required config files/dlls etc. from your Windows temp directory when you run the ruu.exe – copy them all to the same directory)
-ROM.ZIP from the 4.3 DE RUU
In the ARUWizard.exe directory update android-info.txt to include your cidnum and modelid num. Then run ARUWizard.exe. The reason this will work is when ARUWizard.exe runs the cid and model id check are performed using android-info.txt and not by reading the phone. These steps should pass now.
If you upgrade this way OTA’s won’t work because your cid and mid won’t match the OTA.
Click to expand...
Click to collapse
like this?? http://imgur.com/Ig43fic
AnumEndzeit said:
like this?? http://imgur.com/Ig43fic
Click to expand...
Click to collapse
I found QPST but don't have any of the hex, xml, drivers, images etc needed to flash the phone but I know I am in QHSUSB_DLOAD MODE because the phone is lifeless (no charging LED or anything). When I plug it into a MAC or PC I can see it listed as a USB device in device manager with the name QHSUSB_DLOAD MODE.
alasdair.grant said:
I found QPST but don't have any of the hex, xml, drivers, images etc needed to flash the phone but I know I am in QHSUSB_DLOAD MODE because the phone is lifeless (no charging LED or anything). When I plug it into a MAC or PC I can see it listed as a USB device in device manager with the name QHSUSB_DLOAD MODE.
Click to expand...
Click to collapse
im sure you'll be able to find something after googling around.
Related
See tweet here: https://twitter.com/#!/htcdev/status/169946512019816448 and official booloader unlock page here: http://htcdev.com/bootloader
The Eris can now have its bootloader officially unlocked. Mine already is, so I haven't tried this myself.
Wow... Talk about too little too late. ROFL
Sent from my Sabotaged Droid Incredible 2.
Interesting process to say the least. According to this:
http://htcdev.com/bootloader/preview_unlock_process
you register an "account" with them (email and password), send them your device ID, and they "give you instructions" and a passcode of some sort which is unique to your handset.
(A PC with working drivers and fastboot is required).
Also, from the link which doogald provided, note the asterisk after Droid Eris indicating that a "a bootloader upgrade is required".
Also note this interesting tidbit from the HTCdev FAQ (See the very last item):
[SIZE=+1]Why is my security still on (S-On) after I have unlocked my bootloader?[/SIZE]
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. You can easily see that you have successfully unlocked the bootloader by looking at the top of the screen when entering the bootloader screen. Security is left on to protect things like the radio, and SIM lock.
Click to expand...
Click to collapse
Well, I am going to register, and we'll see what we get...
It delivers an RUU with ROM version 2.41.605 - that's useful, as I believe that's one nobody has had before.
[edit] Scratch that - the RUU is 6.1 MB, so it must be just the bootloader and not the actual software
Also, the instructions for installing say that you must install HTC Sync first, and give an HTC web site that is supposed to have it - but they do not list the Eris in the models on the site.
doogald said:
It delivers an RUU with ROM version 2.41.605 - that's useful, as I believe that's one nobody has had before.
[edit] Scratch that - the RUU is 6.1 MB, so it must be just the bootloader and not the actual software
Also, the instructions for installing say that you must install HTC Sync first, and give an HTC web site that is supposed to have it - but they do not list the Eris in the models on the site.
Click to expand...
Click to collapse
Perchance did you start the RUU and pull the "rom.zip" file out (of the temp folder)? We can probably find the bootloader version number easily from there.
What is the use? I don't see it....
That's what I was thinking. The super one click method for the Eris is the best rooting and s off method I have seen for any phone.
Sent from my Sabotaged Droid Incredible 2.
bftb0 said:
Perchance did you start the RUU and pull the "rom.zip" file out (of the temp folder)? We can probably find the bootloader version number easily from there.
Click to expand...
Click to collapse
No, let's take a look, though. Back in a bit.
Bootloader file name is hboot_7501a_1.51.0000_111229.nb0
So, I'm thinking that makes the bootloader version 1.51.0000?
I guess the next thing is to extract that and fastboot flash it, huh?
doogald said:
Bootloader file name is hboot_7501a_1.51.0000_111229.nb0
So, I'm thinking that makes the bootloader version 1.51.0000?
I guess the next thing is to extract that and fastboot flash it, huh?
Click to expand...
Click to collapse
From the FAQ on the HTC site, it would appear that it is going to be a S-ON bootloader, so reversing that flash back to 1.49.20000 may be impossible.
I've got a spare eris with a wonky digitizer that I don't care what happens to it at this time.
But - as others mentioned - it does seem a bit academic at this point.
Can you post the rom.zip file? I'm betting it's small enough to be a post attachment.
bftb0
bftb0 said:
But - as others mentioned - it does seem a bit academic at this point.
Click to expand...
Click to collapse
Right. I'm not quite sure why they bothered - the current bootloader is rootable, doesn't block kernel flashes - what's the point of a new BL with S-ON? I was curious, though, to see what they were going to deliver. I'm going to keep stock on the phone to see if they ever deliver an OTA update, though.
Can you post the rom.zip file? I'm betting it's small enough to be a post attachment.
Click to expand...
Click to collapse
It's attached.
What ota update is that? The one for the bootloader update?
Sent from my Sabotaged Droid Incredible 2.
disconnecktie said:
What ota update is that? The one for the bootloader update?
Click to expand...
Click to collapse
Right. When you run the RUU it goes through all of the steps and then fails at the end, with an error message that says that the current ROM is not supported (my phone had the latest March 2011 OTA installed), but that an update would be available soon that will be supported. It says that there will be a message on the phone, so I assume it's a new OTA.
Hey discon, I used that same app on my Wife's Eris and i didn't get s-off. I miss something? LMAO
Sent from my ADR6300 using xda premium
I could of swore that app gives s off..... Im probably wrong. I haven't turned that thing on since I got my dinc2. Sorry for any confusion. I know I've flashed different radios with that phone though.
Sent from my Sabotaged Droid Incredible 2.
Man, turn me on to them...all I can find is two of them and would like more to test out on my Wife's Eris.....
I think radios from the hero work but you might wanna research first
Sent from my Sabotaged Droid Incredible 2.
Thanks
Sent from my ADR6300 using xda premium
Ok I did some looking and the Eris did get s off and mine is s off. There is a specific h boot that has to be flashed but you have to have a specific version starting to do it. Plus flashing a bootloader is very risky and is the easiest way to brick your phone.
Sent from my Sabotaged Droid Incredible 2.
YouTube S-Off
How to S-Off HTC One without a PC.
As you can see from the video I am running ViperRom with stock kernel, from what I understand some kernels will cause S-Off to fail. Must be rooted to use this method. Also this will break Hot reboot, but doing an RUU will fix this but also wipe all your data.
Download Revone here http://revolutionary.io/revone OP is here http://forum.xda-developers.com/showthread.php?t=2314582
Once its downloaded move to data/local/tmp
Then open terminal
Type the following
su (enter)
cd /data/local/tmp (enter)
chmod 755 revone.bin (enter) (some users may have to remove the .bin if thats you remove it from all of the lines)
./revone.bin -P (enter) (Capital P is needed)
Reboot
open terminal
cd /data/local/tmp (enter)
su (enter)
./revone.bin -s 0 -u
Reboot.
To remove "tampered"
open terminal
cd /data/local/tmp
su
./revone.bin -t
As a life long Samsung user this who'll SOff confuses me I'm rooted I can flash ROMs and kernals so why do I want SOFF is it so I can make my device look like its not tampered and flash a radio if I ever choose?
Sent from my HTC One using xda app-developers app
snowwhite007 said:
As a life long Samsung user this who'll SOff confuses me I'm rooted I can flash ROMs and kernals so why do I want SOFF is it so I can make my device look like its not tampered and flash a radio if I ever choose?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Main advantage is you can have super cid which means you can flash any ruu and get 1st updates, for example my hox is 3 branded and I got jb update 2 months later then unbranded devices if I had s-off I could have updated asap it got released, another thing is SIM unlocking.
Aside from that there's not many other advantages, of course you can run custom bootloader, write to any partition, this more of a advanced user stuff then regular flasher stuff.
Sent from my HTC One using xda premium
I always use custom ROMs that usually update quickly I might soff just to remove tampered in case I need to send to HTC or EE for repair thanks
Sent from my HTC One using xda app-developers app
---------- Post added at 08:04 PM ---------- Previous post was at 07:36 PM ----------
When will the official told drop rather than the preview?
Sent from my HTC One using xda app-developers app
snowwhite007 said:
As a life long Samsung user this who'll SOff confuses me I'm rooted I can flash ROMs and kernals so why do I want SOFF is it so I can make my device look like its not tampered and flash a radio if I ever choose?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
You can also flash radios with s-off.
Shan89 said:
Main advantage is you can have super cid which means you can flash any ruu and get 1st updates, for example my hox is 3 branded and I got jb update 2 months later then unbranded devices if I had s-off I could have updated asap it got released, another thing is SIM unlocking.
Click to expand...
Click to collapse
Holy **** what did you just say
Sent from my HTC One using xda app-developers app
Hmm, adding the .bin to chmod 755 revone or to /revone doesn't seem to work for me. I have to remove that to make it work and thats how I got S-Off. Weird. Maybe its because I have a developer edition or I'm on dricktroid 7. Anyway, a really good guide. Thanks.
demongrim said:
Hmm, adding the .bin to chmod 755 revone or to /revone doesn't seem to work for me. I have to remove that to make it work and thats how I got S-Off. Weird. Maybe its because I have a developer edition or I'm on dricktroid 7. Anyway, a really good guide. Thanks.
Click to expand...
Click to collapse
Thanks for the input. I did two phones and one I have to use .bin and the other I didnt so I will add that to the guide.
snowwhite007 said:
I always use custom ROMs that usually update quickly I might soff just to remove tampered in case I need to send to HTC or EE for repair thanks
Sent from my HTC One using xda app-developers app
---------- Post added at 08:04 PM ---------- Previous post was at 07:36 PM ----------
When will the official told drop rather than the preview?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
You missed my point mate , yes you can flash small firmware updates but for example when the android 4.3 or android 5 arives it'll most likely have Hboot ( bootloader ) update , and if you're locked onto some network with their cid = you wont recieve update for sure at least 1month if not more vs the others who will have it the same day it got released.
That would be one of the main adventages. Tho if you're patient guy/girl and can wait for career ( if you're even on the career ) then this is no issue for you
Another good thing would be adding cid for stock android edition from the HTC google edition = have pure stock + receive updates from google itself.
Of course this maters only if you like AOSP at all
Either way S-OFF is great thing to have. At least for me.
Aside from all this you can also unlock your bootloader without even using HTC Dev , you can S-OFF without root / unlocked bootloader via HTC.dev and unlock / relock / lock bootloader along with removing all the traces of your phone ever being flashed = warrenty wasn't voided This was huge issue on HTC One X , many warrenties were denied just cuz of bootloader was unlocked even tho that software had nothing to do with for example *wifi bug* that we had. This way HTC cannot decline your warrenty even if you did [email protected] up something which is the joy of this
Think of it as .. hmm well you can pretty much do whatever you want to your device and in case you mess things up you can always go back for warrenty , tho if you brick your phone there still shouldn't be a way for them to tell were you messing with the software since the phone is dead
When I type the second command it says invalid option -p
Revone successful
Edit:- nm. It was just the capital P causing the problem. M s off now
Sent from my Nexus 10 using XDA Premium HD app
Sry, my English is not the best, and I didn't understand everything what stands in the first post.
If I do this now, what happens really?
Do I have to flash my Rom from the beginning? Or is everything the same, just with S-OFF?
Is anything gone, like my sd card?
Sent from my HTC One using xda app-developers app
Konfuzion said:
Thanks for the input. I did two phones and one I have to use .bin and the other I didnt so I will add that to the guide.
Click to expand...
Click to collapse
So it depends on the phone?
demongrim said:
So it depends on the phone?
Click to expand...
Click to collapse
I think it depends on what browser you use to download the revone file with. I could be wrong on this.
EnesGTR said:
Sry, my English is not the best, and I didn't understand everything what stands in the first post.
If I do this now, what happens really?
Do I have to flash my Rom from the beginning? Or is everything the same, just with S-OFF?
Is anything gone, like my sd card?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Your English is fine. Nothing gets wiped you will just have s-off after. However this breaks hot reboot and I guess to get it back you have to run the RUU which will wipe your phone. I dont use hot reboot myself so I just left things as is.
Hot reboot...
Is this the quick start option?
Sent from my HTC One using xda app-developers app
So first command worked, rebooted. Opened terminal got this. What should I do now?
Sent from my HTC One using xda premium
tacotino said:
So first command worked, rebooted. Opened terminal got this. What should I do now?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I would just start over. if you are on custom kernel that could be the problem.
Cheers OP, worked a charm
Sent from my HTC One using xda app-developers app
what are all advantages of s-off please ??
can i flash any hboot with s-off ?
thanks
Got error code 1, running trickdroid, can i just clarify what rom i would need to be on to get this to work please?
---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------
tacotino said:
So first command worked, rebooted. Opened terminal got this. What should I do now?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Same here.
DOES NOT WORK WITH INTERNATIONAL DEVICES THAT ARE ON HBOOT 1.54! DONT EVEN BOTHER TRYING. I WILL NOT SUPPORT YOU IF YOU'RE NOT SMART ENOUGH TO FOLLOW THIS GUIDE OR ARE USING AN INTERNATIONAL VERSION OF THE DEVICE
Hello, here is a very simple guide to be able to use revone or moonshine to s-off on the US variants of the HTC One
Make sure you have dev unlocked and you flashed a custom recovery (CWM or TWRP both work fine)
make sure you have also grabbed an appropriate RUU from androidfiles.org
AT&T - http://ruu.androidfiles.org/getdown....13_10.33.1150.01_release_318450_signed_2.exe
T-Mobile - Need RUU link - Working on getting it
Sprint - http://www.androidfilehost.com/?fid=22979706399752930 <-- Extract zip and run RUU.exe
After that, you need to make sure adb works (if you can't figure out how to do any of this, I will not help you. If you can't find out basic things about Android, then you shouldn't have s-off)
So, as we all know, HTC has made it so with newer bootloaders, you cannot downgrade to older firmwares. Well, this is true except when the software version changes but the hboot version doesn't. So all we need to do is this:
Boot into recovery
echo 1.00.000.0 | dd of=/dev/block/mmcblk0p19 bs=1 skip=160
adb reboot bootloader
start the RUU EXE, wait for progress bar to finish for extraction then it opens a new window with a checkbox, next, and cancel
after that, open windows explorer and goto %temp%
back out 1 directory then search for rom.zip
move that to desktop
then close the RUU
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip PATH\TO\DESKTOP\rom.zip
it'll flash hboot then tell you to flush
just re-run the flash zip command (just press up and enter then it should flash again)
Will this return the phone stock
Will this return the phone to stock and therefore allow moonshine to run correctly? Currently I am running cm10 and therefore cannot get moonshine or revone to work.
Indirect said:
echo 1.00.00.0 | dd of=/dev/block/mmcblk0p19 bs=1 skip=160
Click to expand...
Click to collapse
That's some scary **** right there. But awesome find if it works.
Is 0p19 the hboot partition or does it just contain the hboot version? Or is it some other version number we are changing with this?
Why wouldn't this work with the international version? Can't you just flash the WWE RUU instead?
Sent from my iPad using Tapatalk HD
ionstorm3 said:
Will this return the phone to stock and therefore allow moonshine to run correctly? Currently I am running cm10 and therefore cannot get moonshine or revone to work.
Click to expand...
Click to collapse
Yes.
io53 said:
That's some scary **** right there. But awesome find if it works.
Is 0p19 the hboot partition or does it just contain the hboot version? Or is it some other version number we are changing with this?
Why wouldn't this work with the international version? Can't you just flash the WWE RUU instead?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
It is changing the main version and allows a downgrade but doesn't touch hboot pre-update version.
Sent from my hidden jewel
I don't think there is an ruu for tmobile lower than .11, would we be able to change CID in a similar way?
Sent from my HTC One using Tapatalk 4 Beta
io53 said:
Is 0p19 the hboot partition or does it just contain the hboot version? Or is it some other version number we are changing with this?
Why wouldn't this work with the international version? Can't you just flash the WWE RUU instead?
Click to expand...
Click to collapse
hboot is p12. p19 is a "misc" partition where mainver is stored (I think).
As the OP states, this doesn't work if your hboot is 1.54, for reasons that don't need to be repeated again here.
Can you just use the At&t RUU if you're on T-Mobile, then updat radio after soff? Or is that crazy?
Sent from my HTC One using xda app-developers app
You need supercid to run another variants ruu
Sent from my HTC One using Tapatalk 4
iElvis said:
hboot is p12. p19 is a "misc" partition where mainver is stored (I think).
As the OP states, this doesn't work if your hboot is 1.54, for reasons that don't need to be repeated again here.
Click to expand...
Click to collapse
OP says that it does not work on INTERNATIONAL devices on 1.54.
Sent from my HTC One using Tapatalk 4
io53 said:
OP says that it does not work on INTERNATIONAL devices on 1.54.
Click to expand...
Click to collapse
OP can clarify, but what I believe he means is the international carriers that have rolled out 4.2.2. If you took that OTA, you're stuck. No US carriers have rolled out 4.2.2, so no stock US devices have hboot 1.54, but there have been OTAs that blocked s-off.
But this method does not work on US devices that are rooted and upgraded to 1.54 either, because you cannot downgrade hboot without s-off.
iElvis said:
OP can clarify, but what I believe he means is the international carriers that have rolled out 4.2.2. If you took that OTA, you're stuck. No US carriers have rolled out 4.2.2, so no stock US devices have hboot 1.54, but there have been OTAs that blocked s-off.
But this method does not work on US devices that are rooted and upgraded to 1.54 either, because you cannot downgrade hboot without s-off.
Click to expand...
Click to collapse
How this works is that due to the fact that radio / sbl doesn't protect the misc partition which contains version number for the rom / firmware but doesn't contain the hboot number. If it did, this would allow a full downgrade from anything.
Indirect said:
How this works is that due to the fact that radio / sbl doesn't protect the misc partition which contains version number for the rom / firmware but doesn't contain the hboot number. If it did, this would allow a full downgrade from anything.
Click to expand...
Click to collapse
Nice find. But of course it will be patched shortly, I assume.
iElvis said:
Nice find. But of course it will be patched shortly, I assume.
Click to expand...
Click to collapse
Nope. Won't be patched. System needs to be able to write to it when it has a new rom
Indirect said:
Nope. Won't be patched. System needs to be able to write to it when it has a new rom
Click to expand...
Click to collapse
Aha, I didn't think of that. Of course, it's not a big vulnerability either, so HTC may not care anyway.
iElvis said:
Aha, I didn't think of that. Of course, it's not a big vulnerability either, so HTC may not care anyway.
Click to expand...
Click to collapse
Nope. Just makes s-off easier when they don't bump up hboot version number.
ROM.ZIP access
Is there any other way to get the ROM.zip for the AT&T variant? I cannot get it using the process listed.
Sorry for the noob question.
I have a Wind-Mobility HTC One (that shares the same MID as T-Mobile but has a different CID), will this RUU method work? It does have a 1.44 hboot version and not a 1.54 hboot.
Does this not include verizon?
Sent from my HTC6500LVW using XDA Premium HD app
RUU file faulty
Indirect said:
DOES NOT WORK WITH INTERNATIONAL DEVICES THAT ARE ON HBOOT 1.54! DONT EVEN BOTHER TRYING. I WILL NOT SUPPORT YOU IF YOU'RE NOT SMART ENOUGH TO FOLLOW THIS GUIDE OR ARE USING AN INTERNATIONAL VERSION OF THE DEVICE
Hello, here is a very simple guide to be able to use revone or moonshine to s-off on the US variants of the HTC One
Make sure you have dev unlocked and you flashed a custom recovery (CWM or TWRP both work fine)
make sure you have also grabbed an appropriate RUU from androidfiles.org
file=M7/RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe[/url]
start the RUU EXE, wait for progress bar to finish for extraction then it opens a new window with a checkbox, next, and cancel
after that, open windows explorer and goto %temp%
back out 1 directory then search for rom.zip
move that to desktop
Click to expand...
Click to collapse
wrarvoz said:
Does this not include verizon?
Sent from my HTC6500LVW using XDA Premium HD app
Click to expand...
Click to collapse
No, it does not. Verizon does not currently have an RUU to downgrade with nor a version number that works with any current exploit.
So I posted a thread here asking for help (the phone was functional at this point) and one user suggested a root method to try out in the comments there http://forum.xda-developers.com/showthread.php?t=2379833
After running this root method my wifi is now dead. It's killing me! Someone please help me out here.
My phone model is a Japanese Softbank 201 M with the 4.1.2 update. It's not rooted but is unlocked. The phone is the developer edition if that helps any.
System version
9.3.102.201M.SBM.en.JP
Model No
201M
Android version
4.1.2
Baseband
SM_T_BP_1539.000.35.03P
Kernel Version
3.0.42-g721d60d
Build Number
9.8.2Q-34_SMJ-102
HBogard said:
So I posted a thread here asking for help (the phone was functional at this point) and one user suggested a root method to try out in the comments there http://forum.xda-developers.com/showthread.php?t=2379833
After running this root method my wifi is now dead. It's killing me! Someone please help me out here.
My phone model is a Japanese Softbank 201 M with the 4.1.2 update. It's not rooted but is unlocked. The phone is the developer edition if that helps any.
System version
9.3.102.201M.SBM.en.JP
Model No
201M
Android version
4.1.2
Baseband
SM_T_BP_1539.000.35.03P
Kernel Version
3.0.42-g721d60d
Build Number
9.8.2Q-34_SMJ-102
Click to expand...
Click to collapse
Ouch. Your WiFi is broken because he told you to flash a US VZW (XT-907) firmware.
Okay. First, you should try to find a 201M restore file. That will get your WiFi back. Next, since you've got a Dev edition, you can bootloader unlock and install a custom recovery, then flash a root zip
EDIT: Found it
http://sbf.droid-developers.org/scorpion_mini_xt902/list.php
Use one of those to restore your WiFi
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Ouch. Your WiFi is broken because he told you to flash a US VZW (XT-907) firmware.
Okay. First, you should try to find a 201M restore file. That will get your WiFi back. Next, since you've got a Dev edition, you can bootloader unlock and install a custom recovery, then flash a root zip
EDIT: Found it
http://sbf.droid-developers.org/scorpion_mini_xt902/list.php
Use one of those to restore your WiFi
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
While the link I gave him was unidentified as to warnings to non vzw users (now fixed) , the flashing of vzw sw comes in step 8 clearly he would have had to have pulled it from a xml himself if he even got that far. And if he did it would have been from reading the rzr op. As the bare motochopper has no vzw sw inside.
aviwdoowks said:
While the link I gave him was unidentified as to warnings to non vzw users (now fixed) , the flashing of vzw sw comes in step 8 clearly he would have had to have pulled it from a xml himself if he even got that far. And if he did it would have been from reading the rzr op. As the bare motochopper has no vzw sw inside.
Click to expand...
Click to collapse
Oh my bad. Thought you sent him to your other post... Still I suspect he got to step 8 and pulled the vz firmware.
OP: Download one of those restore files for the 201M and flash it. That should repair any damage done...
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Oh my bad. Thought you sent him to your other post... Still I suspect he got to step 8 and pulled the vz firmware.
OP: Download one of those restore files for the 201M and flash it. That should repair any damage done...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I didn't get the system img at all. I just wanted to flash the superuser files to /data which I thought would set me up to flash the whole thing with Rom manager.
Anyway, thank you for the help. I am downloading the firmware you linked to now. This guide tells me to edit the XML file and remove the getvar text from it, should this apply here as well? (Edit: Cant post outside links, but I think you get my point)
I'm going to use RSD 6.1.4 to restore the firmware. Any further instructions would be appreciated as I have never done this before.
HBogard said:
I didn't get the system img at all. I just wanted to flash the superuser files to /data which I thought would set me up to flash the whole thing with Rom manager.
Anyway, thank you for the help. I am downloading the firmware you linked to now. This guide tells me to edit the XML file and remove the getvar text from it, should this apply here as well? (Edit: Cant post outside links, but I think you get my point)
I'm going to use RSD 6.1.4 to restore the firmware. Any further instructions would be appreciated as I have never done this before.
Click to expand...
Click to collapse
Don't think you'll need to since it's designed for your device. You can try without the edit and do it if it doesn't work. I'll try to find a guide for RSDLite (been a while since I used it myself - fastboot is usually what I use now...
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Don't think you'll need to since it's designed for your device. You can try without the edit and do it if it doesn't work. I'll try to find a guide for RSDLite (been a while since I used it myself - fastboot is usually what I use now...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Dear sir,
I'd like you to buy a ticket to Karachi right now because I'd run all the way to the airport to KISS YOU until the police dragged me away.
The process worked. My wifi just turned back on. Thank you very much for the weekend stress relief!
I think I'm gonna give up on the idea of rooting this thing until there's a more reliable method available. Also, if anyone has the same issue then take note: I did remove the getvar commands when using RSD.
HBogard said:
.....
Click to expand...
Click to collapse
I am glad SC took care of you & I am sorry I lead you in that direction.
Please fill in some details for others?
How do you have a path to the newer sw? Is it your carriers ota? If you can obtain the same in the xml form there is an easy root using a modded ver w/ unlocked phone. The ota.zip could also be useful if you take it while you have root. It resides in /cache.
Thank you
aviwdoowks said:
I am glad SC took care of you & I am sorry I lead you in that direction.
Please fill in some details for others?
How do you have a path to the newer sw? Is it your carriers ota? If you can obtain the same in the xml form there is an easy root using a modded ver w/ unlocked phone. The ota.zip could also be useful if you take it while you have root. It resides in /cache.
Thank you
Click to expand...
Click to collapse
It wasn't your fault for trying to help, so it's ok. I'm glad a solution existed.
I'm more than willing to answer the questions, but I am a layman here so please explain some things for me: What do you mean by SW? I just installed the update by going into about phone -> system update on Wifi. The carriers here don't even support 3G, much less 4G (So now you know why Wifi was important for me).
The phone came unlocked day one when I bought it from a friend's friend. I don't know if he did it that way or if it comes unlocked because it is the developer edition.
I installed CW Recovery using Fastboot. I installed the incorrect superuser file using Motofail which wrote the superuser file but failed at all other steps. I was then unable to either access or remove this superuser apk file.
Since I am back on 4.0.4. now, what's the easy way to get root access and superuser permissions that you mention? I wish other XT902 owners would post here too, generating interest would really help in getting development support for this phone.
HBogard said:
Dear sir,
I'd like you to buy a ticket to Karachi right now because I'd run all the way to the airport to KISS YOU until the police dragged me away.
The process worked. My wifi just turned back on. Thank you very much for the weekend stress relief!
I think I'm gonna give up on the idea of rooting this thing until there's a more reliable method available. Also, if anyone has the same issue then take note: I did remove the getvar commands when using RSD.
Click to expand...
Click to collapse
Lol no problem, glad to know it worked. Getting root is actually really simple since you're unlocked. All you need to do is flash a custom recovery and flash a root .zip from there... No exploits required
I can try to write up a guide to that if you want
Sent from my XT907 using Tapatalk 4
sloosecannon said:
Lol no problem, glad to know it worked. Getting root is actually really simple since you're unlocked. All you need to do is flash a custom recovery and flash a root .zip from there... No exploits required
I can try to write up a guide to that if you want
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
I tried that, and while it did install superuser, it seemed to have no effect. I couldn't get permissions for any app and using ROM manager's functions would just freeze up that particular application. Any ideas?
HBogard said:
It.
Click to expand...
Click to collapse
Once you root on 404 you can grab your update.zip & copy it to your sd . Any rooting exploit would evolve from that Or the newest xml ver of the 404 you just flashed from rsd. You may be able to request it from your carrier.
---------- Post added at 01:21 PM ---------- Previous post was at 12:40 PM ----------
You can paste the mods from my vzw restore (no vzw software will be used) into the 404 xml & obtain root from a preinstalled cwmr! Then maintain root with voodoo for your ota.
I will help you just read the op. Link is in my signature.
HBogard said:
I tried that, and while it did install superuser, it seemed to have no effect. I couldn't get permissions for any app and using ROM manager's functions would just freeze up that particular application. Any ideas?
Click to expand...
Click to collapse
Hmm... Which zip did you use?
Sent from my XT907 using Tapatalk 4
sloosecannon said:
Hmm... Which zip did you use?
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
http://www.aosp.us/wp-content/files/Root.zip <- This one.
HBogard said:
http://www.aosp.us/wp-content/files/Root.zip <- This one.
Click to expand...
Click to collapse
I am making a xml to gain root. Which of the two xmls did you flash? & why.
the smj-165 must be newer.
aviwdoowks said:
I am making a xml to gain root. Which of the two xmls did you flash? & why.
the smj-165 must be newer.
Click to expand...
Click to collapse
7.7.1Q-164_SMJ-143_SCORPION_MINI_SBM_SIGNED_CFC
I used this one. Why? I saw them posted somewhere else as while while doing a little research on using RSD and saw that the mirrors on that other link mentioned JP in the file name - I have the Japanese softbank model so I figured this was the one specific to my phone. Turned out to be right.
HBogard said:
http://www.aosp.us/wp-content/files/Root.zip <- This one.
Click to expand...
Click to collapse
Try this. Which recovery are you using? ClockworkMod or TWRP?
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Try this. Which recovery are you using? ClockworkMod or TWRP?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I did use this one. It didn't work for me. Clockwork mod always gave an error for writing superuser.apk or something.
HBogard said:
I did use this one. It didn't work for me. Clockwork mod always gave an error for writing superuser.apk or something.
Click to expand...
Click to collapse
I'm an idiot and forgot the link...
http://forum.xda-developers.com/showthread.php?t=1538053
Sent from my Nexus 7 using Tapatalk 4
HBogard said:
7.7.1Q-164_SMJ-143_SCORPION_MINI_SBM_SIGNED_CFC
I used this one. Why? I saw them posted somewhere else as while while doing a little research on using RSD and saw that the mirrors on that other link mentioned JP in the file name - I have the Japanese softbank model so I figured this was the one specific to my phone. Turned out to be right.
Click to expand...
Click to collapse
Can you upload the xml only ~ 1kb
I have run threads like this in the past for several other devices.
Here I will be covering all sorts of guides and how to's for the HTC One M9! These guides will all be in Video form. Expect S-Off, Root, Recovery, and Rom videos. Check back often for updates to this thread!
How To Root:
How To S-OFF
Unboxing and First Impressions:
Also be sure to subscribe to my youtube channel to be the first to see these videos when they come out! http://youtube.com/droidmodd3rx
Exactly what I was looking for. Will you be making a video on how to unlock the boot loader as well for the unlocked version???
Mine is already unlocked so no, but I'll link to one
Sent from my Nexus 6 using XDA Free mobile app
Waiting eagerly for S-Off. thanks in advance
sephstyler said:
Waiting eagerly for S-Off. thanks in advance
Click to expand...
Click to collapse
S-OFF Guide added
change mid?
to get developer edition mid ...
Why would you wanna change mid?
Thanks!
acidspider said:
Why would you wanna change mid?
Click to expand...
Click to collapse
i have cid and developer room, so to get updates like a developer edition
overon37 said:
i have cid and developer room, so to get updates like a developer edition
Click to expand...
Click to collapse
@scotty1223 will post it here when it's ready .. patience
thx a lot
i will keep an eye on this post
I'm kinda annoyed, I have the M9 from t mobile and i can't even flash twrp without it being s-off, and this s-off requires me to be rooted.
nibblemynutz said:
I'm kinda annoyed, I have the M9 from t mobile and i can't even flash twrp without it being s-off, and this s-off requires me to be rooted.
Click to expand...
Click to collapse
trust me, you can.. you do anything wrong
Any chance of a video on how to return to stock in order to take a firmware upgrade? Thanks - Adam
Adam182 said:
Any chance of a video on how to return to stock in order to take a firmware upgrade? Thanks - Adam
Click to expand...
Click to collapse
a video of a guy running 2 fastboot commands ? is that really necessary ?
clsA said:
a video of a guy running 2 fastboot commands ? is that really necessary ?
Click to expand...
Click to collapse
theres a little more to it that just that - Adam
I will try to get it posted soon
Sent from my SM-G925V using XDA Free mobile app
Adam182 said:
theres a little more to it that just that - Adam
Click to expand...
Click to collapse
Humm yeah
How do I restore stock system so that I can accept an OTA?
Copy the system.emmc.win from your TWRP backup folder to the folder containing fastboot on your PC (or any folder, if fastboot is in your PATH). Make sure your Android SDK platform-tools are up to date!!
Reboot the device into Download mode (adb reboot download) and connect to PC.
Fastboot flash the backup file* (fastboot flash system system.emmc.win).
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
Reboot to system, install OTA.
Click to expand...
Click to collapse
The S-OFF is permament right? If i'm making any updates to the ROM it won't change it to S-ON?
Yes, S-OFF is permament!