Hi everyone,
I unlocked my HTC One, S-OFF, Root and installed TWRP.
Now I'm searching for the correct RUU.
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4A.21.3263.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.63.163.1
INFOversion-misc: PVT SHIP S-OFF
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__203
INFObattery-status: good
INFObattery-voltage: 4281mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-fd1bd949
INFOhbootpreupdate: 11
INFOgencheckpt: 0
I tried this one but it didn't worked
ruu_m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-exe
Thanks for your help !
PParixx said:
Hi everyone,
I unlocked my HTC One, S-OFF, Root and installed TWRP.
Now I'm searching for the correct RUU.
INFOversion-bootloader: 1.55.0000
INFOversion-main: 3.63.163.1
INFOversion-misc: PVT SHIP S-OFF
INFOproduct: m7_ul
INFOmodelid: PN0710000
INFOcidnum: HTC__203
I tried this one but it didn't worked
ruu_m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-exe
Thanks for your help !
Click to expand...
Click to collapse
1- Something is a bit confusing, you have a .163. firmware (3.63.163.1), but with a .401. CID (HTC__203).
2- the reason the ruu didnt work, is because of hboot 1.55, you need to downgrade hboot to 1.44 first, then the ruu should work; no need to relock since you are s-off; check my guide in my signature on how to downgrade hboot first (it's in the first post)
KEEP S-OFF
Ok I did it !
But now I want to lock the boot loader and go to S-ON but my phone isn't recognize in fast boot...
PParixx said:
Ok I did it !
But now I want to lock the boot loader and go to S-ON but my phone isn't recognize in fast boot...
Click to expand...
Click to collapse
Are you SURE you want to go S-On? I really do not recommend it.
If you do then please follow my guide to the letter.... if you have a questions, then please ask!!
As for fastboot not recognizing phone, best to use a Win7 (or XP or even Ubuntu Live USB) machine; lots of problems with Win8 and especially 8.1
Ok so should I let the bootloader unlocked AND the S-OFF ?
Will it be a problem for the next updates ?
PParixx said:
Ok so should I let the bootloader unlocked AND the S-OFF ?
Will it be a problem for the next updates ?
Click to expand...
Click to collapse
you can set it locked, but it's really not necessary, all the OTAs will work fine even with unlocked bootloader. If you want to set it locked, that's OK too.
However, consider S-Off your "get out of jail" card, if something should ever go wrong, the only thing can save you is S-Off. That's why the S-Off is important, locked or unlocked is minor.
Ok so I will stay this way.
And my phone isn't recognize anymore (I don't know why cause it worked before) in fastboot with my W8.1 so it's fine.
Thanks for your help !
PParixx said:
Ok so I will stay this way.
And my phone isn't recognize anymore (I don't know why cause it worked before) in fastboot with my W8.1 so it's fine.
Thanks for your help !
Click to expand...
Click to collapse
Win8.1 has issues
but once you take the OTA updates to 3.62 it should work again, i remember reading that 8.1 seems not to work older hboots.
feel free to press the thanks button if l i helped , and if all is good, please edit the main thread title to include [SOLVED]
nkk71 said:
Win8.1 has issues
but once you take the OTA updates to 3.62 it should work again, i remember reading that 8.1 seems not to work older hboots.
feel free to press the thanks button if l i helped , and if all is good, please edit the main thread title to include [SOLVED]
Click to expand...
Click to collapse
Yes even a RUU that changes the hboot below 1.55 will fail on windows 8.1, the pc will loose connectivity the instant the hboot is downgraded. It then requires another pc to fix it. Or a boot cd as you mentioned.
I run windows 8.1 but i keep a windows 7 box close by just for this reason ( it also comes in handy for other things like Odin - ACMEInstaller - Jungleflasher - Etc )
clsA said:
Yes even a RUU that changes the hboot below 1.55 will fail on windows 8.1, the pc will loose connectivity the instant the hboot is downgraded. It then requires another pc to fix it. Or a boot cd as you mentioned
Click to expand...
Click to collapse
oh good to know, thanks. didn't think of that one, a RUU getting stuck in the middle would not be nice.
Luckily I dont need it at the moment, but I think I'll look into creating an Ubuntu USB over the weekend, seems to be working better with fastboot, rumrunner, etc.
Related
I hate to make this my first post, but I've wasted so much of my time reading the forums and trying the solutions, but I think I've hit the point where I simply must be missing something, so I'm hoping someone will see my info and slap me into what I'm sure is an obvious or glaring oversight.
Anyhow...when running Revone mod as per Vomer's guide (as well as multiple AIO approaches), I'm getting "Revone failed (error code = 2)".
I've tried everything I can see in the threads...-T, root:root, etc.
Here's my phone info:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.18.3250.23
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.29.1500.21
INFOversion-misc: PVT SHIP S-ON
INFOserialno: XXXXXXXXXXXX
INFOimei: XXXXXXXXXXXXXXX
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0713000
INFOcidnum: GLOBA001
INFObattery-status: good
INFObattery-voltage: 4244mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
Any advice or guidance would be greatly appreciated and may result in me getting more than 4 hours of sleep as I've likely wasted 18 hours of my nights trying to figure this out without posting what I'm sure is a noob issue.
Thanks!
teddyoctober said:
I hate to make this my first post, but I've wasted so much of my time reading the forums and trying the solutions, but I think I've hit the point where I simply must be missing something, so I'm hoping someone will see my info and slap me into what I'm sure is an obvious or glaring oversight.
Anyhow...when running Revone mod as per Vomer's guide (as well as multiple AIO approaches), I'm getting "Revone failed (error code = 2)".
I've tried everything I can see in the threads...-T, root:root, etc.
Here's my phone info:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.18.3250.23
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.29.1500.21
INFOversion-misc: PVT SHIP S-ON
INFOserialno: XXXXXXXXXXXX
INFOimei: XXXXXXXXXXXXXXX
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0713000
INFOcidnum: GLOBA001
INFObattery-status: good
INFObattery-voltage: 4244mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
Any advice or guidance would be greatly appreciated and may result in me getting more than 4 hours of sleep as I've likely wasted 18 hours of my nights trying to figure this out without posting what I'm sure is a noob issue.
Thanks!
Click to expand...
Click to collapse
You may have to use an older ATT RUU to downgrade the firmware. I believe AT&T patched the s-off in the .15. You can download the oldest version of the RUU here: http://androidruu.com/getdownload.p....13_10.33.1150.01_release_318450_signed_2.exe
Revone won't work at the first attemp, you have to re-try a lot of time.
For example, see this pastebin...
After some times he s-offed with success
chenchen399 said:
You may have to use an older ATT RUU to downgrade the firmware. I believe AT&T patched the s-off in the .15. You can download the oldest version of the RUU here: http://androidruu.com/getdownload.p....13_10.33.1150.01_release_318450_signed_2.exe
Click to expand...
Click to collapse
You know you can't downgrade without s-off?
Guich said:
Revone won't work at the first attemp, you have to re-try a lot of time.
For example, see this pastebin...
After some times he s-offed with success
You know you can't downgrade without s-off?
Click to expand...
Click to collapse
I believe you can downgrade with this one as long as you're on hboot 1.44
I had the -2 error (or maybe -1 error I don't remember)
I used an RUU to downgrade and it worked afterwards idk why!
chenchen399 said:
I believe you can downgrade with this one as long as you're on hboot 1.44
I had the -2 error (or maybe -1 error I don't remember)
I used an RUU to downgrade and it worked afterwards idk why!
Click to expand...
Click to collapse
Thanks for the replies.
I'll try both of your suggestions when I get home from the office tonight and report back.
I've tried revone over 200 times...was getting error -6, now getting error 2.
I'll see if I can downgrade the RUU as you've noted here, but it was my understanding that S-Off was only contingent on hboot 1.44.
I'll be back tonight...any other recommendations are welcome!
teddyoctober said:
Thanks for the replies.
I'll try both of your suggestions when I get home from the office tonight and report back.
I've tried revone over 200 times...was getting error -6, now getting error 2.
I'll see if I can downgrade the RUU as you've noted here, but it was my understanding that S-Off was only contingent on hboot 1.44.
I'll be back tonight...any other recommendations are welcome!
Click to expand...
Click to collapse
Use this (http://forum.xda-developers.com/showpost.php?p=45487258&postcount=55) to downgrade, then run the ATT RUU. Basically you will flash a backup based on 1.26.502.10, then relock your bootloader, then you'll be able to run the 1.26.502.12 RUU, and then be prepared to s-off. This worked for me. Only certain mainver's (along witht 1.44 HBoot) can be s-off'd
homeslice976 said:
Use this (http://forum.xda-developers.com/showpost.php?p=45487258&postcount=55) to downgrade, then run the ATT RUU. Basically you will flash a backup based on 1.26.502.10, then relock your bootloader, then you'll be able to run the 1.26.502.12 RUU, and then be prepared to s-off. This worked for me. Only certain mainver's (along witht 1.44 HBoot) can be s-off'd
Click to expand...
Click to collapse
I've got all of the necessary files, but when I downloaded the files to downgrade (prior to running ATT RUU), the 32 GB ATT Stock files, there are now 6 files in the folder (.win and .md5)...I'm worried about cocking this up...how do I load these files/which do I load?
I understand that once I've loaded those, I can run the ATT RUU and then I know how to run revone from there.
Anyone around to tell me I'm a noob, but offer some insight?
Thanks.
teddyoctober said:
I've got all of the necessary files, but when I downloaded the files to downgrade (prior to running ATT RUU), the 32 GB ATT Stock files, there are now 6 files in the folder (.win and .md5)...I'm worried about cocking this up...how do I load these files/which do I load?
I understand that once I've loaded those, I can run the ATT RUU and then I know how to run revone from there.
Anyone around to tell me I'm a noob, but offer some insight?
Thanks.
Click to expand...
Click to collapse
click on the .exe and folow wizzard
teddyoctober said:
I've got all of the necessary files, but when I downloaded the files to downgrade (prior to running ATT RUU), the 32 GB ATT Stock files, there are now 6 files in the folder (.win and .md5)...I'm worried about cocking this up...how do I load these files/which do I load?
I understand that once I've loaded those, I can run the ATT RUU and then I know how to run revone from there.
Anyone around to tell me I'm a noob, but offer some insight?
Thanks.
Click to expand...
Click to collapse
The whole folder needs to go in your Recovery's backup folder (if you're using TWRP, it would be /sdcard/TWRP/Backups/YourPhone'sSN/). Then you boot to recovery and restore that backup. Once it's booted, relock your bootloader and you'll be able to run the RUU.
criszz said:
click on the .exe and folow wizzard
Click to expand...
Click to collapse
Hi criszz,
Thanks for the reply.
I understand with the RUU that there is an executable file, but the part (in the linked instructions) before downgrading the RUU, there's an instruction to download and install the 32Gb ATT Stock files (nandroid, I believe). Those are the ones I don't know what to do with...there are 3 .win files and 3 .md5 files.
Any suggestion on that?
teddyoctober said:
Hi criszz,
Thanks for the reply.
I understand with the RUU that there is an executable file, but the part (in the linked instructions) before downgrading the RUU, there's an instruction to download and install the 32Gb ATT Stock files (nandroid, I believe). Those are the ones I don't know what to do with...there are 3 .win files and 3 .md5 files.
Any suggestion on that?
Click to expand...
Click to collapse
You need to put them all in a folder in the location I posted above - that is a backup, which is why there are multiple files. All the files need to be in the same folder in your Recovery's backup folder
homeslice976 said:
The whole folder needs to go in your Recovery's backup folder (if you're using TWRP, it would be /sdcard/TWRP/Backups/YourPhone'sSN/). Then you boot to recovery and restore that backup. Once it's booted, relock your bootloader and you'll be able to run the RUU.
Click to expand...
Click to collapse
Ah...thanks!
I'm back at the office now, but I'll try this tonight.
My girlfriend was laughing at me last night because I've had this phone for 2 weeks and haven't used it. She sees me spending what little free time I have each night, messing around with it and doesn't understand why. :silly:
I'll report back after I screw this up.
Thanks again.
teddyoctober said:
Ah...thanks!
I'm back at the office now, but I'll try this tonight.
My girlfriend was laughing at me last night because I've had this phone for 2 weeks and haven't used it. She sees me spending what little free time I have each night, messing around with it and doesn't understand why. :silly:
I'll report back after I screw this up.
Thanks again.
Click to expand...
Click to collapse
We've all been there
teddyoctober said:
Hi criszz,
Thanks for the reply.
I understand with the RUU that there is an executable file, but the part (in the linked instructions) before downgrading the RUU, there's an instruction to download and install the 32Gb ATT Stock files (nandroid, I believe). Those are the ones I don't know what to do with...there are 3 .win files and 3 .md5 files.
Any suggestion on that?
Click to expand...
Click to collapse
those are TWRP nandroid back-up
which you will have to restore your one's twrp/cwm recovery backup folder
then go back to twrp/cwm recovery to run restore
before running the ruu.exe
Hey guys!
I am fairly new to the forums, I hope I am in the right corner!
I have various problems with my HTC One and I want to return it for repairs. The thing is, I am running cyanogenmod at the moment, which breaks the warranty.
I tried to return to Stock once, but the task ended with an error message (sorry, I don't remember the error code), probably because I chose the wrong RUU. I then stopped tinkering around because I only have a basic knowledge how all of this works and I got scared a bit.
Can anybody help me find the correct RUU?
Or does anybody have an idea how I'd get my device back to stock so I can return it? (I thought of doing the Guru Reset from "htc1guru" (sorry, I can't post links yet). Would this be a good idea?)
My Bootloader (I live and bought the device in Switzerland) says the following:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013, 00:54:00.0
Thanks in advance!
PS: I'd be happy to transfer 20$ to the persons paypal account, who helps me restoring Stock ROM and removing the necessary traces so I can return my device..
http://forum.xda-developers.com/showthread.php?t=2358738
microsyntax said:
Hey guys!
I am fairly new to the forums, I hope I am in the right corner!
I have various problems with my HTC One and I want to return it for repairs. The thing is, I am running cyanogenmod at the moment, which breaks the warranty.
I tried to return to Stock once, but the task ended with an error message (sorry, I don't remember the error code), probably because I chose the wrong RUU. I then stopped tinkering around because I only have a basic knowledge how all of this works and I got scared a bit.
Can anybody help me find the correct RUU?
Or does anybody have an idea how I'd get my device back to stock so I can return it? (I thought of doing the Guru Reset from "htc1guru" (sorry, I can't post links yet). Would this be a good idea?)
My Bootloader (I live and bought the device in Switzerland) says the following:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013, 00:54:00.0
Thanks in advance!
PS: I'd be happy to transfer 20$ to the persons paypal account, who helps me restoring Stock ROM and removing the necessary traces so I can return my device..
Click to expand...
Click to collapse
I'll outline the steps you need to get back to 100% stock, so the repair center doesn't know you unlocked it:
1- get s-off using rumrunner
------ your on 2.2.4.401.1 so download Guru Reset 2.24.401.1 and flash that (http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/)
------ use rumrunner to achieve s-off (read and follow the instructions to the letter)
2- remove tampered, use either revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- change back to LOCKED (not RELOCKED) using revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- download and run the European RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
----- make sure you're CID and MID are compatible with it, if you post a "fastboot getvar all" (remove IMEI and s/n), I'll confirm if this is the correct one
----- this RUU will only work if you have S-Off because it will need to downgrade, and the only way to do this is with S-Off.
Payment is not necessary, a hit of the thanks button will do just fine.
Let me know if you need more info
nkk71 said:
I'll outline the steps you need to get back to 100% stock, so the repair center doesn't know you unlocked it:
1- get s-off using rumrunner
------ your on 2.2.4.401.1 so download Guru Reset 2.24.401.1 and flash that (http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/)
------ use rumrunner to achieve s-off (read and follow the instructions to the letter)
2- remove tampered, use either revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- change back to LOCKED (not RELOCKED) using revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- download and run the European RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
----- make sure you're CID and MID are compatible with it, if you post a "fastboot getvar all" (remove IMEI and s/n), I'll confirm if this is the correct one
----- this RUU will only work if you have S-Off because it will need to downgrade, and the only way to do this is with S-Off.
Payment is not necessary, a hit of the thanks button will do just fine.
Let me know if you need more info
Click to expand...
Click to collapse
Many thanks for your great and comprehensive answer!
The "getvar all" command delivered the following:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3852mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
What does that tell you? Do you need more information?
EDIT: Can I do your steps from my mac? I upgraded my Windows Machine to 8.1, which results in fastboot not working...
microsyntax said:
Many thanks for your great and comprehensive answer!
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 2.24.401.1
Click to expand...
Click to collapse
You need Guru Reset 2.24.401.1 and rumrunner to achieve S-Off.
microsyntax said:
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
Click to expand...
Click to collapse
The RUU (exe) I posted before works for you once you're s-off
---------- Post added at 05:30 PM ---------- Previous post was at 05:27 PM ----------
microsyntax said:
EDIT: Can I do your steps from my mac? I upgraded my Windows Machine to 8.1, which results in fastboot not working...
Click to expand...
Click to collapse
The RUU is a Windows executable, so you will need Windows for the last step. I think the latest drivers work with Windows 8.1, they're called "HTCDriver_4.8.0.002.exe" search for them.
nkk71 said:
You need Guru Reset 2.24.401.1 and rumrunner to achieve S-Off.
The RUU (exe) I posted before works for you once you're s-off
---------- Post added at 05:30 PM ---------- Previous post was at 05:27 PM ----------
The RUU is a Windows executable, so you will need Windows for the last step. I think the latest drivers work with Windows 8.1, they're called "HTCDriver_4.8.0.002.exe" search for them.
Click to expand...
Click to collapse
Thanks again for your quick reply!
This is going to be the first thing I do tomorrow.
Considering my edit, in case you haven't seen it: Can I do the steps you posted from my mac?
microsyntax said:
Thanks again for your quick reply!
This is going to be the first thing I do tomorrow.
Considering my edit, in case you haven't seen it: Can I do the steps you posted from my mac?
Click to expand...
Click to collapse
Like I said, for the last step:
The RUU is a Windows executable, so you will need Windows for the last step. I think the latest drivers work with Windows 8.1, they're called "HTCDriver_4.8.0.002.exe" search for them.
All the other steps, can be done on mac. And I'm sure if it doesn't work on Windows 8.1, you can find a friend with a Windows 7 or maybe 8 just to run the RUU.
nkk71 said:
Like I said, for the last step:
The RUU is a Windows executable, so you will need Windows for the last step. I think the latest drivers work with Windows 8.1, they're called "HTCDriver_4.8.0.002.exe" search for them.
All the other steps, can be done on mac. And I'm sure if it doesn't work on Windows 8.1, you can find a friend with a Windows 7 or maybe 8 just to run the RUU.
Click to expand...
Click to collapse
Yes, sorry, I didn't see that the first time I read it.
In case the drivers shouldn't work, I have this software called "CrossOver" on my mac, which is supposed to be able to run .exe files. Could that work?
EDIT: One last question: the rumrunner instructions state: "Fast boot disabled on your device (settings -> battery -> UNcheck “fast boot”)". I couldn't find out how to do this in cyanogenmod. Do you know how to do this?
microsyntax said:
Yes, sorry, I didn't see that the first time I read it.
In case the drivers shouldn't work, I have this software called "CrossOver" on my mac, which is supposed to be able to run .exe files. Could that work?
Click to expand...
Click to collapse
Don't know.
Some used Fusion (or whatever it's called), and for some it worked others it didnt.
Either way, go through the first parts and then we'll see about the RUU.
EDIT: oh, and i think rumrunner is either Windows or Linux !!
nkk71 said:
Don't know.
Some used Fusion (or whatever it's called), and for some it worked others it didnt.
Either way, go through the first parts and then we'll see about the RUU.
EDIT: oh, and i think rumrunner is either Windows or Linux !!
Click to expand...
Click to collapse
UPDATE: It worked like a charm! Thanks a lot! You're an awesome guy and I'd really make it up for you!
microsyntax said:
UPDATE: It worked like a charm! Thanks a lot! You're an awesome guy and I'd really make it up for you!
Click to expand...
Click to collapse
Having a similar issue. Unfortunately when i install a custom rom it cannot access the internal memory of the phone and i have no way of pushing the reset zip to the phone. Any recommendations?
hiroprotagonist said:
Having a similar issue. Unfortunately when i install a custom rom it cannot access the internal memory of the phone and i have no way of pushing the reset zip to the phone. Any recommendations?
Click to expand...
Click to collapse
Post your own thread with screenshots
hiroprotagonist said:
Having a similar issue. Unfortunately when i install a custom rom it cannot access the internal memory of the phone and i have no way of pushing the reset zip to the phone. Any recommendations?
Click to expand...
Click to collapse
Solution was to simply install TWRP recovery, copy the Guru Reset Zip to USB flash disk, use the USB OTG adapter to connect flash disk. Then i mounted the USB OTG partition in the mounts section and viola, file was available to flash. I have a fully functional phone now
So, before you tell me to go read other forums, I have. I have read ALOT. So, before I begin, I will start off by telling you my phone's information.
Android Version: 4.2.2
Sense: 5.0
Software: 2.24.401.1
HBOOT: 1.55
I am rooted, and I am unlocked.
I have attempted to use RumRunner with no success. I have gotton to about where it gets past rebooting to bootloader then back to home then it says "needs more fermenting" or something then it does like
[*************************]
and after that it does
[TTTT*******************]
then closes.
I have also used firewater, it sometimes chugs 6 bottles, and recently it has been chugging one, then just exiting.
I have been trying to s-off my phone sense i herd about 4.4 release. I have had my phone for a little over 3 months still with no success...If any help can be assisted, it would be greatly appreciated.
If anyone could help, it would be great. Lol
9595jakob said:
So, before you tell me to go read other forums, I have. I have read ALOT. So, before I begin, I will start off by telling you my phone's information.
Android Version: 4.2.2
Sense: 5.0
Software: 2.24.401.1
HBOOT: 1.55
I am rooted, and I am unlocked.
I have attempted to use RumRunner with no success. I have gotton to about where it gets past rebooting to bootloader then back to home then it says "needs more fermenting" or something then it does like
[*************************]
and after that it does
[TTTT*******************]
then closes.
I have also used firewater, it sometimes chugs 6 bottles, and recently it has been chugging one, then just exiting.
I have been trying to s-off my phone sense i herd about 4.4 release. I have had my phone for a little over 3 months still with no success...If any help can be assisted, it would be greatly appreciated.
Click to expand...
Click to collapse
flash an unsecured kernel and retry rumrunner
or
flash arhd 31.6 sense rom and retry rumrunner. (arhd because its rooted and already have an unsecured kernel)
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
Will give it a try after work. If no success, I'll post a reply.
OHHHH, Android Revolution, I have already attempted to use that Rom. I have tried that, carbon, and a stock.
9595jakob said:
OHHHH, Android Revolution, I have already attempted to use that Rom. I have tried that, carbon, and a stock.
Click to expand...
Click to collapse
which version of arhd did you tried? Use the version that match your firmware version and it should be fine.
3.0 I believe. The latest possible version of Android Revolution for non s-off HTC one. It was android 4.3
I have also tried it on Carbon, and a stock Rom.
alray said:
which version of arhd did you tried? Use the version that match your firmware version and it should be fine.
Click to expand...
Click to collapse
So just let me know. Thanks.
Any help would be niccccce....lol
9595jakob said:
Any help would be niccccce....lol
Click to expand...
Click to collapse
how about a "fastboot getvar all" excluding IMEI and s/n
nkk71 said:
how about a "fastboot getvar all" excluding IMEI and s/n
Click to expand...
Click to collapse
Wait...you want me to do what? Lol
9595jakob said:
Wait...you want me to do what? Lol
Click to expand...
Click to collapse
just want you to post a fastboot getvar all (excluding IMEI)
if you're not sure what that means, then you should do a little bit of research about fastboot and adb commands, etc.
I mean no disrespect whatsoever, but if you want to go S-Off, then you should know what these commands mean, and can / cannot do, before you end up with a paperweight (a nice one, but a paperweight nonetheless)
nkk71 said:
just want you to post a fastboot getvar all (excluding IMEI)
if you're not sure what that means, then you should do a little bit of research about fastboot and adb commands, etc.
I mean no disrespect whatsoever, but if you want to go S-Off, then you should know what these commands mean, and can / cannot do, before you end up with a paperweight (a nice one, but a paperweight nonetheless)
Click to expand...
Click to collapse
oh, lol wow. i was on my phone and i did a quick glance. ok. lemme boot into fastboot real quick and ill post it.
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4A.21.3263.03
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.24.531.3
INFOversion-misc: PVT SHIP S-ON
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0713000
INFOcidnum: T-MOB010
INFObattery-status: good
INFObattery-voltage: 3751mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-412e361e
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
9595jakob said:
oh, lol wow. i was on my phone and i did a quick glance. ok. lemme boot into fastboot real quick and ill post it.
INFOversion-bootloader: 1.55.0000
INFOversion-main: 3.24.531.3
INFOversion-misc: PVT SHIP S-ON
INFOmodelid: PN0713000
INFOcidnum: T-MOB010
all: Done!
Click to expand...
Click to collapse
i think http://firewater-soff.com/ should work for you, on a rooted ROM with unsecured kernel
nkk71 said:
i think http://firewater-soff.com/ should work for you, on a rooted ROM with unsecured kernel
Click to expand...
Click to collapse
I have tried Firewater
Annnnnnnny help would be nice
I'm a complete newbie to this XDA so would appreciate any help possible.
My HTC One is Bricked and wont go beyond the HTC logo screen.
I've look at all the different forums and threads and I cant find one particular thread to guide me through the process.
The simplest way I can tell to get my phone back to stock without rooting and doing s-off is to use a ruu file, but I cant find one any where for my phone.
Can anyone help or point me in the right direction:
MEID PN0711000
HTC_621 (TW)
3.63.709.3
HT3AJW906862
356376050293921
abreu6 said:
I'm a complete newbie to this XDA so would appreciate any help possible.
My HTC One is Bricked and wont go beyond the HTC logo screen.
I've look at all the different forums and threads and I cant find one particular thread to guide me through the process.
The simplest way I can tell to get my phone back to stock without rooting and doing s-off is to use a ruu file, but I cant find one any where for my phone.
Can anyone help or point me in the right direction:
MEID PN0711000
HTC_621 (TW)
3.63.709.3
HT3AJW906862
356376050293921
Click to expand...
Click to collapse
There is an RUU for your One. The only issue is that ur S-ON and the RUU is for a lower firmware version than the one you have. To flash the RUU, you will have to downgrade your firmware, which needs S-OFF
Post the output of your getvar all. It'll help a lot
And do u have custom recovery?? What exactly did you do which bricked the phone ??
raghav kapur said:
There is an RUU for your One. The only issue is that ur S-ON and the RUU is for a lower firmware version than the one you have. To flash the RUU, you will have to downgrade your firmware, which needs S-OFF
Post the output of your getvar all. It'll help a lot
And do u have custom recovery?? What exactly did you do which bricked the phone ??
Click to expand...
Click to collapse
Hello, Thanks for helping out. I have a taiwan build of the phone, for some reason I got the message prompt to upgrade to kitkat and sense 5.5 ( the release isnt officially out in my region) I'm thinking I got it because of the firmware build of my phone, once i tried to upgrade thats where the stall happened.
To get S-Off i need to root my phone from my understanding is this correct ? I dont have a custom recovery will post the get var here.
Thanks again.
Since you bricked your phone, I'm going to safely assume you were at least on an unlocked bootloader. If that's the case, you can download the TWRP recovery image onto your PC and boot into it off your phone with the fastboot command "fastboot boot (recovery name).img". Once there, you can go to TWRP's advanced settings and turn on ADB sideload to install a ROM. After that's done, go back into fastboot and flash the boot.img from the ROM separately before booting the ROM for the first time (since you're S-ON). That should get your phone back on.
My friend did the same thing the other day and that was how I got theirs working again.
Sent from my HTC One using xda app-developers app
decayer177 said:
"fastboot boot (recovery name).img".
Click to expand...
Click to collapse
That only works on hboot 1.44, "fastboot boot ...." was patched/broken after 1.44.
decayer177 said:
After that's done, go back into fastboot and flash the boot.img from the ROM separately before booting the ROM for the first time (since you're S-ON).
Click to expand...
Click to collapse
That's not needed on the M7, it'll get flashed automatically during the install even with S-On.
decayer177 said:
Since you bricked your phone, I'm going to safely assume you were at least on an unlocked bootloader. If that's the case, you can download the TWRP recovery image onto your PC and boot into it off your phone with the fastboot command "fastboot boot (recovery name).img". Once there, you can go to TWRP's advanced settings and turn on ADB sideload to install a ROM. After that's done, go back into fastboot and flash the boot.img from the ROM separately before booting the ROM for the first time (since you're S-ON). That should get your phone back on.
My friend did the same thing the other day and that was how I got theirs working again.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help, no its locked and not tampared. I'm guessing i do all of the above but unlook my bootloader first.
abreu6 said:
Thanks for the help, no its locked and not tampared. I'm guessing i do all of the above but unlook my bootloader first.
Click to expand...
Click to collapse
Which RUU file do you recommend I can downgrade to. The version I have is 3.63.709.3 is there a site with ruu files. I have the latest ota file from the htc website, is the ruu file in there ?
Will try the procedure today and re post here.
abreu6 said:
I'm a complete newbie to this XDA so would appreciate any help possible.
My HTC One is Bricked and wont go beyond the HTC logo screen.
I've look at all the different forums and threads and I cant find one particular thread to guide me through the process.
The simplest way I can tell to get my phone back to stock without rooting and doing s-off is to use a ruu file, but I cant find one any where for my phone.
Can anyone help or point me in the right direction:
MEID PN0711000
HTC_621 (TW)
3.63.709.3
HT3AJW906862
356376050293921
Click to expand...
Click to collapse
Here's a copy of my getvar, -
Version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.213263.04
version-cpld: None
version-micorp: None
version-main: 3.63.709.04
version-misc: PVT SHIP S-On
serialno:HT3AJW906862
ProductL m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC_621
battery-status: low
battery-voltage: 3475mV
partition-layout: Generic
security: on
build-mode:SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-a448e85a
hboottpreupdate: 11
gencheckpt: 0
i tried to get my phone fixed but because its cross region nothing htc can do, and cost is as much as value of the phone. Will try all the tips here and repost. Thanks for everyone's help. Really appreciate it, this is a great forum
If anyone else has any other suggestions let me know.
nkk71 said:
That only works on hboot 1.44, "fastboot boot ...." was patched/broken after 1.44.
That's not needed on the M7, it'll get flashed automatically during the install even with S-On.
Click to expand...
Click to collapse
Yup the fastboot thingy doesnt work, anyother way i can use twrp if this is required. Unlocked my boot loader, are there any short cuts in this. Cant I just unlock, s-off and download any of the latest ruu files to bring my phone back to life ?
abreu6 said:
Yup the fastboot thingy doesnt work, anyother way i can use twrp if this is required. Unlocked my boot loader, are there any short cuts in this. Cant I just unlock, s-off and download any of the latest ruu files to bring my phone back to life ?
Click to expand...
Click to collapse
not right now, too sleepy, but i highly recommend you (and everybody else that quoted you) edit your posts and remove IMEI ... that information should NOT be shared publicly!
nkk71 said:
not right now, too sleepy, but i highly recommend you (and everybody else that quoted you) edit your posts and remove IMEI ... that information should NOT be shared publicly!
Click to expand...
Click to collapse
will do, didnt realize i did that, thanks !
nkk71 said:
not right now, too sleepy, but i highly recommend you (and everybody else that quoted you) edit your posts and remove IMEI ... that information should NOT be shared publicly!
Click to expand...
Click to collapse
All removed, when i do the fastboot devices, the scrambled reply comes up which means im connected, but getvar all brings back nothing. I worried I may have done something wrong. Thanks
HTC one bricked
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: 4A.23.3263.28
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: FA34MW909277
INFOimei: 354439059885634
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: BS_US001
INFObattery-status: good
INFObattery-voltage: 3882mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-4dab9d12
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
please help me out. I am using custom rom now .... no network .... no baseband. i am also confused that ruu is for me... i tried one but failed
Hey guys and girls. A little backstory:
New to android
Use Cyanogenmod Installer
Get Purple Camera. Need to go back to stock.
Stumble upon guide by nkk71 http://forum.xda-developers.com/showthread.php?t=2541082
Botch last step
So I found an ruu with my CID and MID, but it was the GPE ruu not the ATT RUU! The ATT RUU zips don't list CID and MID so I assumed I should not use them and all that matters is matching those.
I had locked and went back to s-On when following the guide.... big mistake.
I've since unlocked and tried to root so that I could go back to S-Off.
Flashed several different correct recoveries and none will work. I am erasing the cache, but nothing works. I've tried the most recent versions of CWM and TWRP and can't get anywhere.
What should I try next?
bradreputation said:
Hey guys and girls. A little backstory:
New to android
Use Cyanogenmod Installer
Get Purple Camera. Need to go back to stock.
Stumble upon guide by nkk71 http://forum.xda-developers.com/showthread.php?t=2541082
Botch last step
So I found an ruu with my CID and MID, but it was the GPE ruu not the ATT RUU! The ATT RUU zips don't list CID and MID so I assumed I should not use them and all that matters is matching those.
I had locked and went back to s-On when following the guide.... big mistake.
I've since unlocked and tried to root so that I could go back to S-Off.
Flashed several different correct recoveries and none will work. I am erasing the cache, but nothing works. I've tried the most recent versions of CWM and TWRP and can't get anywhere.
What should I try next?
Click to expand...
Click to collapse
Sorry to hear that, I thought my guide was pretty clear
please post
1- a fastboot getvar all (excluding IMEI and s/n)
2- a screenshot of your bootloader
3- more details of what you have flashed (with links to the threads)
nkk71 said:
Sorry to hear that, I thought my guide was pretty clear
please post
1- a fastboot getvar all (excluding IMEI and s/n)
2- a screenshot of your bootloader
3- more details of what you have flashed (with links to the threads)
Click to expand...
Click to collapse
Your guide is very good and I thank you for it. I just messed up. I think it would be good to clarify that a person should reboot after flashing RUU before going back to S-On. I had the impression that was my only chance to go back S-On.
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4291mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
http://imgur.com/yXDR6lr Shot of my Bootloader
This is what I flashed for RUU http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
I've flashed the latest TWRP and CWM. The problem really started when I installed CWM and Su from this guidehttp://forum.xda-developers.com/showthread.php?t=2292729.
bradreputation said:
Your guide is very good and I thank you for it. I just messed up. I think it would be good to clarify that a person should reboot after flashing RUU before going back to S-On. I had the impression that was my only chance to go back S-On.
Click to expand...
Click to collapse
Technically, you can, but shouldn't reboot the OS because of the OTA notification, which may make it tempting to take, but I'll try and rephrase the guide.
bradreputation said:
version-bootloader: 1.54.0000
version-main:
version-misc: PVT SHIP S-ON
product: m7_ul
modelid: PN0712000
cidnum: CWS__001
http://imgur.com/yXDR6lr Shot of my Bootloader
This is what I flashed for RUU http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
I've flashed the latest TWRP and CWM. The problem really started when I installed CWM and Su from this guidehttp://forum.xda-developers.com/showthread.php?t=2292729.
Click to expand...
Click to collapse
bootloader is unlocked, good... do NOT try and lock it!!
reflash TWRP and a custom ROM (you can try ARHD 31.6 or similar), and get S-OFF using rumrunner and/or firewater
i'm off for tonight, sorry about the mess
The stock att RUU's would almost certainly have the stock CWS_001 Cid. You just need one that is the same or postdated to your current hboot version since you are s-on now. Unfortunately, now that you are s-on, you will also need to relock the bootloader to flash an RUU. I would do that and then use firewater/rumrunner/latest s-off method to get s-off and unlock boot loader. Then you want to fix the "relocked" flag to "locked", and s-on again, and get it repaired.
I would try to get S-OFF where you are now.
I'll keep this here just in case
Otherwise, you can use the 3.xx RUU.EXE: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
this will upgrade to hboot 1.55, and rumrunner and/or firewater should work on it.
(remember you need to relock bootloader for that to work with S-On, that's why i'm recommending to try where you are now, so you don't lock bootloader)
there is also a 4.xx RUU but do not use it, because it will upgrade your hboot to 1.56, making it even more difficult to S-OFF.
and once you're S-OFF, you should use this ruu.zip for my guide (which is for PN0712000 + CWS__001):
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/
AFH Mirror: http://www.androidfilehost.com/?fid=23501681358544977
nkk71 said:
I would try to get S-OFF where you are now.
I'll keep this here just in case
Otherwise, you can use the 3.xx RUU.EXE:
this will upgrade to hboot 1.55, and rumrunner and/or firewater should work on it.
(remember you need to relock bootloader for that to work with S-On, that's why i'm recommending to try where you are now, so you don't lock bootloader)
there is also a 4.xx RUU but do not use it, because it will upgrade your hboot to 1.56, making it even more difficult to S-OFF.
and once you're S-OFF, you should use this ruu.zip for my guide (which is for PN0712000 + CWS__001):
]
Click to expand...
Click to collapse
I was able to get TWRP (newest version) and ARHD (31.6) running. I then got S-OFF using Firewater. I'll use the RUU and follow the guide again.
I saw another one of your posts that suggested S-OFF may not effect warranty claims. Any further thought on that?
Thanks again for all your contributions.
bradreputation said:
I was able to get TWRP (newest version) and ARHD (31.6) running. I then got S-OFF using Firewater. I'll use the RUU and follow the guide again.
I saw another one of your posts that suggested S-OFF may not effect warranty claims. Any further thought on that?
Thanks again for all your contributions.
Click to expand...
Click to collapse
It's really very country/carrier/people specific, in theory, S-Off shouldn't matter as some phones accidentally ship S-Off (ok, it's very very very rare), but S-Off shouldn't void warranty https://twitter.com/htc/status/377422743626842112
Then again, in practice some carriers/technicians may try to use any excuse to refuse warranty.