Hey Everybody..
Here a little guide to how to make you T-Mobile HTC One a Developer Edition and receive OTA updates directly from HTC with no carries delays.
after downloading and unzip the revone.zip file do the following:
MAKE SURE YOUR ADB AND FASTBOOT ARE WORKING PROPERLY. AND UNINSTALL HTC SYNC MANAGER BEFORE DOING ANY OF THESE STEPS!!
ONLY DO THIS IF YOU ARE COMFORTABLE IN WHAT YOU DOING.
adb push revone /data/local/tmp
adb shell
cd /data/local/tmp
chmod 755 revone
./revone -P
exit
reboot your phone
adb shell
cd /data/local/tmp
./revone -s 0 -u
exit
adb reboot bootloader
your bootloader should now be S-OFF
to change CID do this:
fastboot oem writecid 11111111
fastboot reboot-bootloader
your bootloader screen should now show the new CID
you can now flash the Original RUU for the HTC One Developer Edition from http://www.htcdev.com/devcenter/downloads
i take no credit for this guide this is just a re-write from the real devs page. i wanted to make it easy for those looking in this section
Is this reversible? Also, do you get everything you get on the Tmo version except wifi calling and Tmo apps? Thanks.
I think links to the revone s-off thread would be more appropriate than just rewriting their instructions and posting their file here, don't you? Those devs deserve proper credit, and the real support for problems is going to be there....
Legaleye3000 said:
Is this reversible? Also, do you get everything you get on the Tmo version except wifi calling and Tmo apps? Thanks.
Click to expand...
Click to collapse
yes and yes
When HTC updates though wouldn't they also be updating the radio? If that's the case won't that affect our 1700 band or will we still keep it? All I care about is stock since I'm already over the whole flashing and rooting stuff. Wish HTC did a dev edition with tmobile bands.
Sent from my HTC One
Gja88 said:
When HTC updates though wouldn't they also be updating the radio? If that's the case won't that affect our 1700 band or will we still keep it? All I care about is stock since I'm already over the whole flashing and rooting stuff. Wish HTC did a dev edition with tmobile bands.
Sent from my HTC One
Click to expand...
Click to collapse
I'm running the Dev edition radio and still have 1700 band.
Gja88 said:
When HTC updates though wouldn't they also be updating the radio? If that's the case won't that affect our 1700 band or will we still keep it? All I care about is stock since I'm already over the whole flashing and rooting stuff. Wish HTC did a dev edition with tmobile bands.
Click to expand...
Click to collapse
That's extact what this guide does.. HTC one dev edition and with pentaband
Sent from my HTC One using xda app-developers app
just want to confirm, it should be this?
One
Brightstar US
USA
RUU
3.4.10
v4.1 984.7 MB
1.29.1540.16 Developer Edition
Gja88 said:
When HTC updates though wouldn't they also be updating the radio? If that's the case won't that affect our 1700 band or will we still keep it? All I care about is stock since I'm already over the whole flashing and rooting stuff. Wish HTC did a dev edition with tmobile bands.
Sent from my HTC One
Click to expand...
Click to collapse
Exactly.
Sent from my HTC One using Tapatalk 2
id10terrordfw said:
I'm running the Dev edition radio and still have 1700 band.
Click to expand...
Click to collapse
Again...
jay661972 said:
just want to confirm, it should be this?
One
Brightstar US
USA
RUU
3.4.10
v4.1 984.7 MB
1.29.1540.16 Developer Edition
Click to expand...
Click to collapse
yup.. i used that one .. everything works flawless.. no t-mobile bloatware
adb says: device not found. I installed everything. From android sdk to fastboot. Hasoon2000's all in one kit works, so it is not my USB connection. I really need to recover with a developer edition RUU. My HTC One is useless right now.
Oh well something strange happend. When I command: fastboot reboot-bootloader my HTC One reboot in to bootloader. It is not working on adb, but on fastboot commands.
YaviSGS said:
adb says: device not found. I installed everything. From android sdk to fastboot. Hasoon2000's all in one kit works, so it is not my USB connection. I really need to recover with a developer edition RUU. My HTC One is useless right now.
Oh well something strange happend. When I command: fastboot reboot-bootloader my HTC One reboot in to bootloader. It is not working on adb, but on fastboot commands.
Click to expand...
Click to collapse
boot your phone into the OS, then try the adb devices see if show up
YaviSGS said:
adb says: device not found. I installed everything. From android sdk to fastboot. Hasoon2000's all in one kit works, so it is not my USB connection. I really need to recover with a developer edition RUU. My HTC One is useless right now.
Oh well something strange happend. When I command: fastboot reboot-bootloader my HTC One reboot in to bootloader. It is not working on adb, but on fastboot commands.
Click to expand...
Click to collapse
i do have issue last night in doing the steps, decided to do it using android terminal and its flawless
---------- Post added at 02:36 PM ---------- Previous post was at 02:01 PM ----------
xitaxuta said:
yup.. i used that one .. everything works flawless.. no t-mobile bloatware
Click to expand...
Click to collapse
i run the RUU this morning but hang in Sending for more than 20 minutes thats why i remove unplug the usb
xitaxuta said:
boot your phone into the OS, then try the adb devices see if show up
Click to expand...
Click to collapse
I do not have OS. Everything on my phone is wiped. I only have a USB kabel, HTC One which is still unlocked. My only hope is S-OFF and then flash developer edition cause there is no T-Mobile RUU available
Edit: I think it works. I see a white screen with HTC logo and text at the bottom: "This is build is for development purposes only etc". So I commanded: adb reboot bootloader and it works. Bit still, when I command: adb devices, there is no device.
Is your phone with super-cid?
Sent from my HTC One using xda app-developers app
xitaxuta said:
Is your phone with super-cid?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I don't know what that means.
This is all I can say about my phone:
***TEMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013, 17:22:59:-1
This is what I got when I command:
C:\Android\adb push revone /data/local/tmp
failed to copy 'revone' to '/data/local/tmp' : No such file or directory
YaviSGS said:
I don't know what that means.
This is all I can say about my phone:
***TEMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013, 17:22:59:-1
Click to expand...
Click to collapse
Your phone is showing
S-ON
You need to s-off using the revone file.. and after that you need change it to super-cid.
Sent from my HTC One using xda app-developers app
xitaxuta said:
Your phone is showing
S-ON
You need to s-off using the revone file.. and after that you need change it to super-cid.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes I try to do that now. I putted the revone file in the map where my adb files are. There I opened cmd and typed this:
C:\Android\adb push revone /data/local/tmp
failed to copy 'revone' to '/data/local/tmp' : No such file or directory
I think its refers to my internal storage? Cause there are no files in my storage right now... Or is it something else?
I'm heading to work right now so won't be able to assist you until I get back home.. what rom are you using? Try to cd\android
adb push revone /data/local/tmp
Sent from my HTC One using xda app-developers app
Related
Hello
I got HTC J Butterfly from Japan and have been trying to get it working in Finland since.
We tried first to change the phone to Taiwan version (x920d), but the result was no good 2G.
The next step was to try to change to phone into Droid DNA,
Starting point:
DELUXE_J PVT SHIP S-OFF
CID-KDDI_801
HBOOT-1.41.0000
RADIO-1.01.10.0201
OpenDSP-v6.120.274.0114
Original HTC J Butterfly ROM
What was done:
1. installed jdk1.7.0_25 and android sdk tools, platform tools and google usb driver (installer_r22.0.5)
2. installed ViperDNA 1.3.5 ROM (via CWM recovery from external sd card)
3. installed engineering HBOOT (see below)
fastboot oem rebootRUU
fastboot flash zip xxxxxx.zip
4. installed twrp recovery: twrp-htc-dlxj.img
5. modify (CID: 11111111 and IMEI and MEID according to my phone) in mmcblk0p5 block file and copy to /dev/block with dd:
dd if=/sdcard/mmcblk0p5 of=/dev/block/mmcblk0p5 (copied to /sdcard/ with adb push in recovery mode)
NOTE1: HERE ADB STILL OK
6. fastboot oem writemid PL8320000
NOTE2: HERE ADB CANNOT BE USED ANYMORE
NOTE3: phone was encrypted and asking for password (cleared by formatting internal SD)
7. flash firmware
fastboot oem rebootRUU
fastboot flash zip dna2.06firmware.zip
7.1 installed twrp recovery: twrp-htc-dlx.img
8. installed engineering HBOOT (see below)
fastboot oem rebootRUU
fastboot flash zip xxxxxx.zip
Current situation:
MONARUDO PVT ENG S-OFF
CID-11111111
HBOOT-1.39.2000 (PL8320000)
RADIO-1.01.04.0308
OpenDSP-v6.120.274.0114
No ROM currently
Fastboot USB (OK)
ADB (NOK)
USB connection (NOK)
- cannot connect to device from Windows 7 or Windows XP, because the phone/device is flashing as portable device called:
WPD FileSystem Volume Driver
What I would like to do is to flash ROM.
but since I cannot transfer any files to the system it seems to be impossible.
I can flash in fastboot, because that is working just fine.
Any ideas how to proceed are more than welcome !?
Thank you
Can you run the RUU ? Or if can not because windows does not see it, run the RUU to extract the files to temp folder, then flash the zips manually via fastboot?
You prolly have seen this thread;
http://forum.xda-developers.com/showthread.php?t=2155334
thehoovie said:
Can you run the RUU ? Or if can not because windows does not see it, run the RUU to extract the files to temp folder, then flash the zips manually via fastboot?
You prolly have seen this thread;
http://forum.xda-developers.com/showthread.php?t=2155334
Click to expand...
Click to collapse
Thanks for the reply.
What do you mean by running the RUU ? fastboot oem rebootRUU ? (that is working for me)
I was also thinking that I cannot flash anything for DELUXE_J since I changed the moid. Not sure if this is true ?
Thanks
Hello again
Currently I'm assuming there is no way to install ROM without working USB/ADB, because no replies.
If you know such method and needed files please let me know.
Thank you
Hello
Raised the topic since I have not received any replies.
Most probably someone knows how to get the phone working again (install ROM).
Please help. Thanks
jko76 said:
Hello
Raised the topic since I have not received any replies.
Most probably someone knows how to get the phone working again (install ROM).
Please help. Thanks
Click to expand...
Click to collapse
Since you're S-OFF you could probably just change the model id back to the J Butterfly the same way you changed it to the DNA
Sent from my HTC6435LVW using xda app-developers app
times_infinity said:
Since you're S-OFF you could probably just change the model id back to the J Butterfly the same way you changed it to the DNA
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
For changing the model id I would need to copy a block file to the device. Currently i cannot do that.
Any other ideas ?
jko76 said:
For changing the model id I would need to copy a block file to the device. Currently i cannot do that.
Any other ideas ?
Click to expand...
Click to collapse
In the OP you said you changed the model id with fastboot oem writemid.
Since you're soff, you should just be able to do that again, back to the J Butterfly mid
Sent from my HTC6435LVW using xda app-developers app
Yeah why did you flash DNA files on a j butterfly anyways man you probably messed the phone up .
Sent from my HTC6435LVW using Tapatalk 2
times_infinity said:
In the OP you said you changed the model id with fastboot oem writemid.
Since you're soff, you should just be able to do that again, back to the J Butterfly mid
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
In the OP step 5 I copied Droid DNA block file into my phone and then changed the mid. I was thinking that without putting back my original
block HTC J blockfile I cannot change the mid back. Of course I could try the command but I'm worried that the incorrect block file mid combination will brick the phone totally.
Is there any RUU available for Droid DNA that could be flashed through fastboot ?
Thanks
coachcrey said:
Yeah why did you flash DNA files on a j butterfly anyways man you probably messed the phone up .
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
The idea was to try to make the phone working in Finland (the phone was locked to AU network in Japan). It did not work with x920d SW (2G NOK) and therefore decided to give the DNA SW a go.
Yes, the phone might be messed up, but still I would like to think there is a way to recover since the fastboot and recovery are working.
Thanks
jko76 said:
The idea was to try to make the phone working in Finland (the phone was locked to AU network in Japan). It did not work with x920d SW (2G NOK) and therefore decided to give the DNA SW a go.
Yes, the phone might be messed up, but still I would like to think there is a way to recover since the fastboot and recovery are working.
Thanks
Click to expand...
Click to collapse
I guess the better question is who gave you the idea to try and flash dna files on a butterfly to my understanding they are similar phones not the same.
Sent from my HTC6435LVW using Tapatalk 2
coachcrey said:
I guess the better question is who gave you the idea to try and flash dna files on a butterfly to my understanding they are similar phones not the same.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
The idea was mine.
We tried x920d SW as well and that was working apart from the unstable 2G connection.
thehoovie said:
Can you run the RUU ? Or if can not because windows does not see it, run the RUU to extract the files to temp folder, then flash the zips manually via fastboot?
You prolly have seen this thread;
http://forum.xda-developers.com/showthread.php?t=2155334
Click to expand...
Click to collapse
I can run the RUU*.exe until it checks the USB connectivity. In the temp files I can find the data1.cab file which most probably has the image files that I would need. The remaining problem is that I cannot extract the data1.cab file.
Does anyone know how to extract the cab file ?
Thank you
jko76 said:
I can run the RUU*.exe until it checks the USB connectivity. In the temp files I can find the data1.cab file which most probably has the image files that I would need. The remaining problem is that I cannot extract the data1.cab file.
Does anyone know how to extract the cab file ?
Thank you
Click to expand...
Click to collapse
Actually I found the ROM.zip as well from temp directory. I cannot unzip the file.
How to use this ROM.zip file ?
jko76 said:
Actually I found the ROM.zip as well from temp directory. I cannot unzip the file.
How to use this ROM.zip file ?
Click to expand...
Click to collapse
Use ruuveal to decrypt the zip
Sent from my HTC6435LVW using xda app-developers app
times_infinity said:
Use ruuveal to decrypt the zip
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Done and now I can open/extract the rom.zip. There are many .img files inside.
Now I need some help how to proceed ?
Please remember that the phone is S-OFF and engineering HBOOT is currently installed.
Do I need to change HBOOT ? What about S-ON ?
What is the best way of flashing the images ?
Thank you very much for your help.
jko76 said:
Done and now I can open/extract the rom.zip. There are many .img files inside.
Now I need some help how to proceed ?
Please remember that the phone is S-OFF and engineering HBOOT is currently installed.
Do I need to change HBOOT ? What about S-ON ?
What is the best way of flashing the images ?
Thank you very much for your help.
Click to expand...
Click to collapse
You can try just flashing the whole zip. Do fastboot oem rebootRUU and then fastboot flash zip ruu.zip
Sent from my HTC6435LVW using XDA Premium 4 mobile app
times_infinity said:
You can try just flashing the whole zip. Do fastboot oem rebootRUU and then fastboot flash zip ruu.zip
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
AFTER fastboot flash zip rom.zip:
MONARUDO PVT SHIP S-OFF
CID-11111111
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
fastboot flash recovery twrp-htc-dlx.img
TWRP recovery installed
fastboot flash zip PL832.zip
MONARUDO PVT ENG S-OFF
HBOOT-1.39.2000 (PL8320000)
Unfortunately the USB/ADB is still unstable. Also it seems that the ROM does not boot up. The droid boot image can be seen. Then it goes away and I can see in the upper part of the screen USB debugging connected flashing...
Fastboot interface is ok, bootloader and recovery as well.
Let's see what could be the next step/try. Currently it seems that Droid SW cannot be used with HTC J Butterfly HW !?
All I can offer is they obviously have differences or the kernels would be the same. Try using the proper kernel for it and see if it proceeds any further in booting the ROM. Making it think its a DNA doesn't change the hardware itself, at a minimum the kernel needs to be the correct one foe the device hardware, not name, and maybe the ROM just to eliminate drivers and libs being incompatible as well.
Or is the kernel the same?
Tapatalked from my HTC DNA - Carbon
my HTC one is on 4.3 ota with 1.55 hboot as far as i have read on one thread someone had succesfully soff with rumrunner
It wasnt clear if he was using atat htc One.
I have tried this 20 times and i get stuck with this
it reboots fine once into hboot reboots once into fastboot then locks up at adb reboot
i have all the proper drivers i have adb drivers installed .I have unchecked fastboot in power settings
I also have downloaded the proper rumrunner for my firmware which is os-3.17.502.3
Am i missing something here guys ..is this even possible with the att One on 1.55 hboot with 4.3 android or am i on the wrong track waisting time, this is rediculous
ANY other options to downgrade to get soff from where i stand. I need soff
THIS IS WHAT I GET
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (32/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
Waiting for ADB (20/120)
lojak29 said:
my HTC one is on 4.3 ota with 1.55 hboot as far as i have read on one thread someone had succesfully soff with rumrunner
It wasnt clear if he was using atat htc One.
I have tried this 20 times and i get stuck with this
it reboots fine once into hboot reboots once into fastboot then locks up at adb reboot
i have all the proper drivers i have adb drivers installed .I have unchecked fastboot in power settings
I also have downloaded the proper rumrunner for my firmware which is os-3.17.502.3
Am i missing something here guys ..is this even possible with the att One on 1.55 hboot with 4.3 android or am i on the wrong track waisting time, this is rediculous
ANY other options to downgrade to get soff from where i stand. I need soff
THIS IS WHAT I GET
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (32/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
Waiting for ADB (20/120)
Click to expand...
Click to collapse
All I can tell you is that it worked for me. AT&T Unlocked HBOOT 1.55, firmware 3.17.502.3, ROOTED... just like yours. After I ran rumrunner a prompt appeared on the phone screen that I confirmed with OK and that was it. The phone rebooted several times and ended up with LOCKED HBOOT and S-OFF. I had to unlock again with a new Unlock code from htcdev.
lojak29 said:
my HTC one is on 4.3 ota with 1.55 hboot as far as i have read on one thread someone had succesfully soff with rumrunner
It wasnt clear if he was using atat htc One.
I have tried this 20 times and i get stuck with this
it reboots fine once into hboot reboots once into fastboot then locks up at adb reboot
i have all the proper drivers i have adb drivers installed .I have unchecked fastboot in power settings
I also have downloaded the proper rumrunner for my firmware which is os-3.17.502.3
Am i missing something here guys ..is this even possible with the att One on 1.55 hboot with 4.3 android or am i on the wrong track waisting time, this is rediculous
ANY other options to downgrade to get soff from where i stand. I need soff
THIS IS WHAT I GET
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (32/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
Waiting for ADB (20/120)
Click to expand...
Click to collapse
Did you do this on windows 8
Did u have to extract the rumrunner zip into a specific folder such as fastboot folder and run it from there?, did u need adb drivers it says if you htcdev unlock the adb doesn't need to be downloaded.
I mean of all else fails where's the exact files /links you used , there's to many variables here can you help any further ?
Why won't my phone keep rebooting past the 2nd fastboot reboot instead just keeps counting.
Sent from my HTC One using xda app-developers app
lojak29 said:
Did you do this on windows 8
Did u have to extract the rumrunner zip into a specific folder such as fastboot folder and run it from there?, did u need adb drivers it says if you htcdev unlock the adb doesn't need to be downloaded.
I mean of all else fails where's the exact files /links you used , there's to many variables here can you help any further ?
Why won't my phone keep rebooting past the 2nd fastboot reboot instead just keeps counting.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes I did this on Win 8. I unzipped the file in a folder on the desktop and ran soju.exe file. I had the ADB drives installed for my previous HTC One X. Didn't download anything extra except for the rumrunner.zip. Make sure you are full stock and rooted. Also you have to uninstall HTC Sync if you have it installed.
lightflier said:
Yes I did this on Win 8. I unzipped the file in a folder on the desktop and ran soju.exe file. I had the ADB drives installed for my previous HTC One X. Didn't download anything extra except for the rumrunner.zip. Make sure you are full stock and rooted. Also you have to uninstall HTC Sync if you have it installed.
Click to expand...
Click to collapse
I'm starting to think I'm experiencing a usb3.0 issue on my gateway which is apparently a huge issue topic under the how to get around soff block thread ..
Windows Usb3.0 on windows 8 doesn't work well with fastboot.
But it seems complicated to change/force Intel usb3.0 drivers which allow fastboot adb to work flawlessly in place of the windows 3.0 usb .
That's the whole issue here I believe.
Sent from my HTC One using xda app-developers app
lojak29 said:
I'm starting to think I'm experiencing a usb3.0 issue on my gateway which is apparently a huge issue topic under the how to get around soff block thread ..
Windows Usb3.0 on windows 8 doesn't work well with fastboot.
But it seems complicated to change/force Intel usb3.0 drivers which allow fastboot adb to work flawlessly in place of the windows 3.0 usb .
That's the whole issue here I believe.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
This is exactly what I was going to say Good luck with USB 2
Make sure your adb is up to date and that you have turned off all anti-virus software...
I had issues too but finally got it to work on my ATT One
Sent from my HTC One using Tapatalk
Does anybody have a mirror of rumrunner for 3.17.502.3? Their website is currently down. Thanks guys.
Edit: Site is back up.
lojak29 said:
my HTC one is on 4.3 ota with 1.55 hboot as far as i have read on one thread someone had succesfully soff with rumrunner
It wasnt clear if he was using atat htc One.
I have tried this 20 times and i get stuck with this
it reboots fine once into hboot reboots once into fastboot then locks up at adb reboot
i have all the proper drivers i have adb drivers installed .I have unchecked fastboot in power settings
I also have downloaded the proper rumrunner for my firmware which is os-3.17.502.3
Am i missing something here guys ..is this even possible with the att One on 1.55 hboot with 4.3 android or am i on the wrong track waisting time, this is rediculous
ANY other options to downgrade to get soff from where i stand. I need soff
THIS IS WHAT I GET
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (32/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
Waiting for ADB (20/120)
Click to expand...
Click to collapse
Did you solve this problem mate? I have the same issue with my one..
mctodd said:
Did you solve this problem mate? I have the same issue with my one..
Click to expand...
Click to collapse
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
make sure you installed latest driver
This is working now I just did mine yesterday. The previous version would lock my phone up while running the tests.
Sent from my HTC One using XDA Premium 4 mobile app
Linux makes life so easy.........
Worked flawless on my One last night. Same firmware as OP:thumbup:
Sent from my HTC One using Tapatalk
I got
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (6/120)
FATAL: **** It
........................................................................................................................................................................................................................................................
so am i screwed?
Hboot 1.55 LOCKED S-Off w/ Rumrunner
So, I unlocked my boot loader with HTCDEV. I than used Rumrunner to gain s-off and root. It worked but now it says Tampered "locked" but is S-off. I'd like to unlock my bootloader and if possible without HTCDEV again. I just got the phone set back up. I backed up my apps but I couldn't get TWRP to load through a flashing app or Goomanager. I'm guessing this is because I'm locked. Can anyone help?? Not sure what to do here. Sounds like you guys figured this out but I didn't see the howto..
is it ok to ask what the purpose of s- off is?
I had to be on stock ROM to be able to S-OFF when I tried the other day. I also had to put all the rumrunner files in the same folder as my sdk/adb stuff. Make sure, if your phone prompts you to accept the connection from the PC, to accept.
Is your phone even showing up when you try 'adb devices' ?
Yes, that all worked fine. I ended up installing Clock work through their app.. never could get twrp to work
Sent from my HTCONE using xda app-developers app
pontypool said:
is it ok to ask what the purpose of s- off is?
Click to expand...
Click to collapse
The purpose of S-OFF is so you can change the CID (carrier ID) and a few other things. It is the master access to the phone pretty much. Once you change the CID you can flash stock ROMs (custom roms can be flashed without S-OFF), which allow you to convert your AT&T HTC one to the google play edition or any other edition like the European editions.
I got it to work on my One. I had to try twice. I think it failed the first time because of an SU permission popup or something which I pressed allow but then rumrunner ended without finishing. The second time it worked though.
How did you uninstall the HTC Sync app? I've tried a couple of different ways, but it comes back after I restart the phone.
Mod edit: Firewater has been shut down server-side and is no longer supported. Try Sunshine.
It claims to S-off any HTC device that is rooted/unlocked.
*Works with Hboot 2.47
Home
welcome to firewater
what firewater can do for you:
S-OFF Your HTC device
Unlock your bootloader
Prerequisites
Working adb on your PC. Yes, that means OS X, linux, Windows, etc. are all supported.
HTC drivers installed and working
HTC sync removed (not closed – REMOVED)
All other phone software removed or disabled (Samsung Kies, PDANet, etc.)
A working internet connection ON YOUR DEVICE - wifi, 3g, 4g, etc. are all supported. There is no way around this requirement, don’t ask.
USB debugging enabled on your device
Your device must be HTCDEV unlocked/rooted or have a working temproot. A temproot that works with many modern (not all) HTC devices is provided below.
Do not attempt to run firewater from a terminal emulator on your device. You MUST use adb along with a PC.
A supported device. firewater *should* work with most modern QUALCOMM BASED HTC devices, including (but not limited to) the htc one, droid dna, one s, one max, and many others.
Instructions (normal, rooted device method)
Once you confirm you meet the above pre-requisites, it’s time to get started.
Ensure device is booted to android with usb debugging enabled.
USB 2.0 ports are preferred.
You should not be connected using any hubs which may cause connectivity issues
Ensure that lock screen security is disabled on your device.
no passcode lock
no pattern lock
no face lock
Download firewater HERE - _http://firewater-soff.com/firewaterdownload-3
Push, Prepare, and Execute firewater:
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
Agree to the terms and conditions you are prompted with
Allow the exploit to do its work.
Profit
Instructions (temp-root method)
This method may allow firewater to work on a fully stock/htcdev locked device. This method is being provided as a convenience. Do NOT seek support if this temproot does not work for you.
Ensure device is booted to android with usb debugging enabled.
USB 2.0 ports are preferred.
You should not be connected using any hubs which may cause connectivity issues
Ensure that lock screen security is disabled on your device.
no passcode lock
no pattern lock
no face lock
Download firewater HERE - _http://firewater-soff.com/firewaterdownload-3
Download temproot HERE - _http://firewater-soff.com/temprootdownload
Push, Prepare, and Execute temproot and firewater:
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp
adb push temproot /data/local/tmp
adb shell
chmod 755 /data/local/tmp/temproot
chmod 755 /data/local/tmp/firewater
/data/local/tmp/temproot
/data/local/tmp/firewater
Agree to the terms and conditions you are prompted with
Allow the exploit to do its work.
Profit
_http://firewater-soff.com/instructions/
ps: i am not a member of firewater team
Support
Support for firewater s-off is available at #firewater on the freenode and andirc networks. Please make sure you meet all of the requirements before contacting support.
Click to expand...
Click to collapse
For those in HBOOT 2.49, please revert to stock 1.19.xxx ROM and try this - more instructions http://forum.xda-developers.com/showthread.php?t=2765383
LOLZ
worked a treat, many thanks, cheers again
DANIELWHITT said:
worked a treat, many thanks, cheers again
Click to expand...
Click to collapse
Good to know mate, so your hboot is version 2.47 which you were not able to unlock before. is that correct?
pradeepvizz said:
Good to know mate, so your hboot is version 2.47 which you were not able to unlock before. is that correct?
Click to expand...
Click to collapse
I was s off in the old hboot but put it back to stock for a repair, once on the new h boot rumrunner wouldn't work, however this did and an awful lot faster as well.
DANIELWHITT said:
I was s off in the old hboot but put it back to stock for a repair, once on the new h boot rumrunner wouldn't work, however this did and an awful lot faster as well.
Click to expand...
Click to collapse
Now you are lucky! when you say new hboot, whats the version please? i suppose its 2.47 and also is your phone the international unlocked model T6UL ?
pradeepvizz said:
Now you are lucky! when you say new hboot, whats the version please? i suppose its 2.47 and also is your phone the international unlocked model T6UL ?
Click to expand...
Click to collapse
Hboot is 2.47 and int one max t6up
DANIELWHITT said:
Hboot is 2.47 and int one max t6up
Click to expand...
Click to collapse
Thanks!
help
I can't seem to get the temp root to work , I have a verizon HTC one 4.3 , last 2 commands are not working for me ,anyone mind helping me out via PM
It worked!!!
Thanks a lot! It worked like a charm...
Tried rumrunner but without success. Firewater did it in under 30 seconds! Amazing!
I have a German Telekom based One Max with 2.46 hboot (T6UL).
Thanks for your work!
OMG! Thank you so much. i have max one UK hboot 2.47 and this worked in less that 2 mins. now s-off'd
thank you
Tampered message also gone too!
will relock now and see if fingerprint scanner enables.
:laugh:
Edit: re-locked bootloader and now fingerprint scanner works too! also if i unlock, i dont ever get the tampered message again!
thank you so much.
has anyone tested on the HTC One? i dont see a thread there for that but OP says that it should work
Worked like a charm on HTC One (m7ul/International) - ****ing speedy and easy - once I dusted off my adb hahaha.
sns0582 said:
I can't seem to get the temp root to work , I have a verizon HTC one 4.3 , last 2 commands are not working for me ,anyone mind helping me out via PM
Click to expand...
Click to collapse
Use rumrunner on VZW One Max, worked like a charm for me. Fully bone stock when I ran it, worked first try.
Sent from my HTC One Max
thank you
verizon htc one 4.3 hboot 1.55 want temproot
I tried the commands to temp root ,not working on my HTC one , any ideas if it's just I have files in wrong area , I have them in my adb folder ,
sns0582 said:
I tried the commands to temp root ,not working on my HTC one , any ideas if it's just I have files in wrong area , I have them in my adb folder ,
Click to expand...
Click to collapse
is your device must be HTCDEV unlocked?
pradeepvizz said:
is your device must be HTCDEV unlocked?
Click to expand...
Click to collapse
Yes... Your device must be HTCDEV unlocked and rooted.
Worked like a charm on my International One Max, thank you!
im trying to temp root to s off and unlock
pradeepvizz said:
is your device must be HTCDEV unlocked?
Click to expand...
Click to collapse
. If I read correctly it states I need to temp root to s-off , is there a way to HTC dev unlock 4.3 hboot 1.55 on Verizon,
Hello all, I've just recently recovered my DNA back to stock from a botched ROM install on the 3.06 software. Prior to running the RUU, I used Rumrunner to unlock my bootloader to put CWM on as my recovery. Then I had to re-lock it to run the RUU. Now I'm stuck at re-unlocking it. The HTCdev site is giving me a MID not allowed error and I'm thinking it has something to do with the fact that I used Rumrunner? Call me stupid, the DNA is still relatively new to me. Thank you!!
You shouldn't need to relock it to RUU. The RUU will overwrite your recovery with stock but the bootloader should remain unlocked (and s-off if you did that as well). At this point you should be able to just run rumrunner again to unlock the bootloader and then you can flash a custom recovery and go from there.
Sent from my HTC6435LVW using xda app-developers app
iissmart said:
You shouldn't need to relock it to RUU. The RUU will overwrite your recovery with stock but the bootloader should remain unlocked (and s-off if you did that as well). At this point you should be able to just run rumrunner again to unlock the bootloader and then you can flash a custom recovery and go from there.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Tried doing Rumrunner again, Getting this error, "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)" I've uninstalled the drivers via device manager, let windows 7 reinstall them and installed/uninstalled HTCsync with no luck.
Edit: Nevermind, tried a different cable. Hate it when that happens.
Edit 2: Rumrunner must have failed, device still relocked.
Hubblemuffin said:
Tried doing Rumrunner again, Getting this error, "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)" I've uninstalled the drivers via device manager, let windows 7 reinstall them and installed/uninstalled HTCsync with no luck.
Click to expand...
Click to collapse
Does 'adb devices' show your serial number? Did you enable debugging in the developer options?
iissmart said:
Does 'adb devices' show your serial number? Did you enable debugging in the developer options?
Click to expand...
Click to collapse
I don't even see ADB devices in device manager. Just Android USB Devices.
Hubblemuffin said:
I don't even see ADB devices in device manager. Just Android USB Devices.
Click to expand...
Click to collapse
ADB Devices is a command issued from the command prompt. It should return the S/N of the device connected. If there is no response the drivers are not installed on the PC. If you are using Win 8 or 8.1 you will have issues
RLGL said:
ADB Devices is a command issued from the command prompt. It should return the S/N of the device connected. If there is no response the drivers are not installed on the PC. If you are using Win 8 or 8.1 you will have issues
Click to expand...
Click to collapse
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Hubblemuffin said:
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Click to expand...
Click to collapse
Hı, have you find out a solution to this one ?
I am struggling with a similar situation:
http://forum.xda-developers.com/showthread.php?p=51140962
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Hubblemuffin said:
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I have heard if you flash a new hboot the relocked text will go away, but I haven't had this issue myself so I can't personally confirm it. I do recommend updating your hboot and radio, though, for other reasons like better radio signal.
iissmart said:
I have heard if you flash a new hboot the relocked text will go away, but I haven't had this issue myself so I can't personally confirm it. I do recommend updating your hboot and radio, though, for other reasons like better radio signal.
Click to expand...
Click to collapse
Updating the hboot and radio seems a little daunting. Definitely something I want to look in to once I can figure out how to get a ROM on this without calling a mulligan and starting from scratch again.
Hubblemuffin said:
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Click to expand...
Click to collapse
Adb is universal to all android devices, I highly recommend getting used to it if you plan on rooting future devices, the only thing native to HTC is the S-OFF portion of eMMC
Hubblemuffin said:
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Are you S-OFF? If so issue this command in fastboot:
fastboot oem writecid 22222222
Go to htcdev.com and then it will allow you to unlock the bootloader also make sure you have 8 2's in the command.
I have a HTC one 32GB and it's currently s-on with tampered showing and unlocked showing . My hboot is 1.56.0000. Need to return to stock since att sending me overnight a replacement...i have stupid purple camera really bad.
Sent from my KFSOWI using Tapatalk
This should be the right one, double check your version. http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
EDIT: have you ever flashed an ruu before?
Sent from my HTC One using XDA Premium 4 mobile app
Yes I have currently trying to lock boot loader but says device is offline
Sent from my HTC One using Tapatalk
bigfdaddy2 said:
Yes I have currently trying to lock boot loader but says device is offline
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Start the phone in fastboot mode and type the following command:
Code:
fastboot devices
What's the output?
hafizimtiaz said:
Start the phone in fastboot mode and type the following command:
Code:
fastboot devices
What's the output?
Click to expand...
Click to collapse
i got adb to work i had 2 change roms... how do i go about relocking myphone so i can run the ruu
Got my phone relocked know gonna run the ruu
Sent from my KFSOWI using Tapatalk
If you take the phone back to an ATT store for an exchange or to have them fix it, you don't have to return it to stock. they don't check and they don't care. The only time you need to return it to stock is if you are having to send it back to HTC. If at all possible deal with ATT as they will most of the time just hand you a new one while HTC will give you a refurb. You won't get your original back from HTC.
hafizimtiaz said:
Start the phone in fastboot mode and type the following command:
Code:
fastboot devices
What's the output?
Click to expand...
Click to collapse
new phone same prblm error device offline while using adb..but run venom adb works but no su when typed in and asked
C:\AndroidSDK>fastboot devices
HT36MW903711 fastboot
C:\AndroidSDK>
bigfdaddy2 said:
new phone same prblm error device offline while using adb..but run venom adb works but no su when typed in and asked
C:\AndroidSDK>fastboot devices
HT36MW903711 fastboot
C:\AndroidSDK>
Click to expand...
Click to collapse
As it is showing your device ID in fastboot mode, your phone is properly connected in fastboot mode. Does the screen say FASTBOOT USB? If yes, you can run RUU.exe file.
Yes it does and can run the ruu.... My issue know is how come adb says device offline with stock rooted Rom but with venom Rom it's connected but doesn't grant root when asked to through adb
Sent from my HTC One using Tapatalk
Stock kernel blocks this...
bigfdaddy2 said:
Yes it does and can run the ruu.... My issue know is how come adb says device offline with stock rooted Rom but with venom Rom it's connected but doesn't grant root when asked to through adb
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Which kernal do I need then I tried with bullet I believe the name was
Sent from my KFSOWI using Tapatalk
Wonders_Never_Cease said:
Stock kernel blocks this...
Click to expand...
Click to collapse
Doesn't he need USB debugging and accept the computers adb key? That could be why he gets that.
Sent from my HTC One using XDA Premium 4 mobile app
He could but these prop settings mess things up
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.adb.secure=1
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.metropcs.ui=0
GalaxyUser50 said:
Doesn't he need USB debugging and accept the computers adb key? That could be why he gets that.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I've gotten to accept root through adb and am trying to use Firewater to s-off my new one and it just fails every time .... Can't seem to find a how to or step by step on it like the older hboots have ...I got 1.56 of course lol ...
Sent from my HTC One using Tapatalk
Wonders_Never_Cease said:
Stock kernel blocks this...
Click to expand...
Click to collapse
how do i achieve s-off on hboot 1.56 ive tried rumrunner,firewater,arhd,venom rom
i think i used firewater for s-off,I unlocked via htc dev and then ran the firewater on numerous htc ones, you do need an unsecured boot image for your device though...root actually isnt needed,is a plus but i didnt root my devices and it worked with just a unsecured boot image I made
bigfdaddy2 said:
how do i achieve s-off on hboot 1.56 ive tried rumrunner,firewater,arhd,venom rom
Click to expand...
Click to collapse
Wonders_Never_Cease said:
i think i used firewater for s-off,I unlocked via htc dev and then ran the firewater on numerous htc ones, you do need an unsecured boot image for your device though...root actually isnt needed,is a plus but i didnt root my devices and it worked with just a unsecured boot image I made
Click to expand...
Click to collapse
this my current setup: win7 ,htc one m732gb,hboot 1.56.00,rom currently using arhd 31.6.... i am unlocked,rooted,fastboot disabled,no lock...what else am i missing to achieve this ?
adb/fastboot configured correctly? htc sync removed and latest drivers installed?
bigfdaddy2 said:
this my current setup: win7 ,htc one m732gb,hboot 1.56.00,rom currently using arhd 31.6.... i am unlocked,rooted,fastboot disabled,no lock...what else am i missing to achieve this ?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
adb/fastboot configured correctly? htc sync removed and latest drivers installed?
Click to expand...
Click to collapse
sync is gone adb works ,fastboot works,latest drivers....
C:\Users\ace\Desktop\htc 1 toolkit>adb reboot
C:\Users\ace\Desktop\htc 1 toolkit>adb wait-for-device push firewater /data/loca
l/tmp
protocol failure
C:\Users\ace\Desktop\htc 1 toolkit>adb push firewater /data/local/tmp
2532 KB/s (4519496 bytes in 1.743s)
C:\Users\ace\Desktop\htc 1 toolkit>adb shell
[email protected]:/ # su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.5.15 ===========================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
[email protected]:/ #
C:\Users\ace\Desktop\htc 1 toolkit>