I hate asking for help as I can almost always find the answer through searching but I ihink I killed my One -_-
I moved from Sprint to Tmobile. I got a new HTC One from Tmobile (silver). I wanted to keep my old HTC One (black.) The plan was to unlock both SIM card slots and send my sister the new one (Tmobile didnt have any black and I prefer the black over silver.) Got an unlock code off ebay for the Tmobile silver, Sprint would not give me an unlock code for the black.
Looked at a bunch of different forum posts and followed the guide here http://forum.xda-developers.com/showthread.php?t=2586704
Since I have 1.29.651.7 with S-ON, I did more searching to make sure the methods would work and saw posts from others with similar situations refered back to this post. So I started with Solution 3a, got all the files, made sure phone was fully charged, etc.
Tried rumrunner and it went through the motions but did not work, got error
"ERROR: looks like device is not rooted AND lacks an unsecure kernel. SU or FU!!"
My HTC One black is rooted. Tried again, same thing.
Scrounged I dont know how many posts, somewhere along the lines I read to use a version of RUU that works with S-ON. Ran it, all was going well, progress bar was almost at the end and it stopped and it showed an ERROR RECOVERY [0].
Followed the onscreen instructions, When I unplug it from my computer as instructed, I get a "bootloader" screen that just has "RUU" in orange. Continued and it fails again, this time when I unplug it I get RUU "hboot Version is older!" Stuck at the black HTC screen with 4 triangles in each corner. Can not get to recovery, bootloader, anything.
black original running Beanstalk 4.4
Tampered
Unlocked
S-ON
Hboot 1.44
1.29.651.7
black now
Tampered
Relocked
S-On
hboot 1.55
OS 1.29.651.7 (3.04.651.2)
fastboot getver all
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 1.00.20.0315
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.29.651.7
INFOversion-misc: PVT SHIP S-ON
INFOserialno: FAxxxxxxxx
INFOimei: 99xxxxxxxxxxx
INFOmeid: 99xxxxxxxxxxxx
INFOproduct: m7_wls
INFOplatform: HBOOT-8064
INFOmodelid: PN0720000
INFOcidnum: SPCS_001
INFObattery-status: good
INFObattery-voltage: 4281mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: dirty-371c4f408e
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.073s
Any help appreciated
People like you really get on my nerves. How do you start with solution 3a? Did you even read what is it for? If you are on 1.29 you just need root and than run the SIMUnlocker app. You DIDN'T need the ruu. You really seem to want to kull your phone.
Anyway you have hboot 1.55 that's why the 1.29 ruu doesn't work. Lock your bootloader. You need this ruu http://forum.xda-developers.com/showthread.php?t=2576995
Unlock bootloaderFlash the BadBoys 4.3 rom and run the simunlock helper
Sent from my HTC One using Tapatalk
---------- Post added at 01:13 PM ---------- Previous post was at 12:55 PM ----------
Try adb reboot-bootloader it should take you to bootloader. Maybe you don't even need to run the ruu to get it working
Sent from my HTC One using Tapatalk
Actually that was a mistype, I used 3b not a, because as mentioned I do not have s-off and I started with hboot 1.44. I did try SIMUnlocker first, but as the description said it does not work with every Rom and it did not work on mine.
Appreciate the help and will try what you've mentioned.
Sent from my HTC One using xda app-developers app
Rea_Rea said:
Actually that was a mistype, I used 3b not a, because as mentioned I do not have s-off and I started with hboot 1.44. I did try SIMUnlocker first, but as the description said it does not work with every Rom and it did not work on mine.
Appreciate the help and will try what you've mentioned.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
To make some things clear you have hboot 1.44 or 1.55? The simunlockhelper works with every rom, you didn't have root access or weren't on a sense rom. First try if you can boot on the os, let's start from there
Sent from my HTC One using Tapatalk
elvisypi said:
To make some things clear you have hboot 1.44 or 1.55? The simunlockhelper works with every rom, you didn't have root access or weren't on a sense rom. First try if you can boot on the os, let's start from there
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I did already relock the bootloader, as that was part of the initial instructions. I started with 1.44, now it has 1.55. Correct, I was not on a sense rom. I tried flash InsertCoin back on since I came to that from Beanstalk. I cannot boot into the OS, no. I can use fastboot commands but I do not get the bootloader options, only RUU.
Rea_Rea said:
I did already relock the bootloader, as that was part of the initial instructions. I started with 1.44, now it has 1.55. Correct, I was not on a sense rom. I tried flash InsertCoin back on since I came to that from Beanstalk. I cannot boot into the OS, no. I can use fastboot commands but I do not get the bootloader options, only RUU.
Click to expand...
Click to collapse
You did pretty much everything wrong. Do what I said in the previous post: lock bootloade, than the ruu in that link. After that unlock bootloader, flash the 4.3 BadBoyz ROM from here http://forum.xda-developers.com/devdb/project/dl/?id=2301&task=get
Now you can finally unlock with the SIMUnlock helper
Sent from my HTC One using Tapatalk
Related
Hi guys! I have a question...
I was thinking about using a RUU to clean install a stock rom on my one...so, I was at htc-dev site and looked at downloads...
I find: the developer edition RUU, android 4.3 (the last one)...ok, this is the classic RUU, I have to execute it when I'm on "fastboot oem rebootRUU", I'm s-off, it wipes everything and I have the stock firmware and rom...and it's ok...have I got to relock the bootloader?
then....I see, just below, a zip file, as big as the RUU one, but is a zip...what is this? is the zip that the RUU flashes, but for a different use, with the raw method, on the terminal?
and, another one...I looked at the google play edition section...and I founded two zips for each version: one "stock ui" and one "framework support files"....ok, what is this?! isn't there a RUU? what if I want to flash a clean google play edition, with full wipe and stock clean firmware? what can I do with these files?
thank you for listening, and sorry for my bad english
throcker said:
Hi guys! I have a question...
I was thinking about using a RUU to clean install a stock rom on my one...so, I was at htc-dev site and looked at downloads...
I find: the developer edition RUU, android 4.3 (the last one)...ok, this is the classic RUU, I have to execute it when I'm on "fastboot oem rebootRUU", I'm s-off, it wipes everything and I have the stock firmware and rom...and it's ok...have I got to relock the bootloader?
then....I see, just below, a zip file, as big as the RUU one, but is a zip...what is this? is the zip that the RUU flashes, but for a different use, with the raw method, on the terminal?
and, another one...I looked at the google play edition section...and I founded two zips for each version: one "stock ui" and one "framework support files"....ok, what is this?! isn't there a RUU? what if I want to flash a clean google play edition, with full wipe and stock clean firmware? what can I do with these files?
thank you for listening, and sorry for my bad english
Click to expand...
Click to collapse
You must have s-off and super cid "11111111" to flash ruu that are not specific to your phone. You do not have to lock your bootloader. Again, you MUST have s-off and super cid! As long as you have those, you can pretty much convert your phone to whichever you want. I always recommend downgrading your hboot to 1.44 before doing this. You need encrypted ruu's to use the "fastboot oem rebootRUU" mode. Remember to flash stock recovery if you want OTA updates. I have never used the .exe files. I converted my att htc one to google edition, then back, then developer, then back. Its really no different than just running roms, but at least you get a new splash screen and bootloader with each.
http://forum.xda-developers.com/showthread.php?t=2358781 This is the google edition conversion link I used my first time converting my phone. if you look at post 2, it shows how to go back to stock "or pretty much any ruu"
an0ther said:
You must have s-off and super cid "11111111" to flash ruu that are not specific to your phone. You do not have to lock your bootloader. Again, you MUST have s-off and super cid! As long as you have those, you can pretty much convert your phone to whichever you want. I always recommend downgrading your hboot to 1.44 before doing this. You need encrypted ruu's to use the "fastboot oem rebootRUU" mode. Remember to flash stock recovery if you want OTA updates. I have never used the .exe files. I converted my att htc one to google edition, then back, then developer, then back. Its really no different than just running roms, but at least you get a new splash screen and bootloader with each.
http://forum.xda-developers.com/showthread.php?t=2358781 This is the google edition conversion link I used my first time converting my phone. if you look at post 2, it shows how to go back to stock "or pretty much any ruu"
Click to expand...
Click to collapse
ok, thanks for your answer, first....
I already tried the conversion, and it worked fine...but that's not what I'm looking for
I was asking how does the official source files work...
delete me
throcker said:
ok, thanks for your answer, first....
I already tried the conversion, and it worked fine...but that's not what I'm looking for
I was asking how does the official source files work...
Click to expand...
Click to collapse
What do you mean 'work'? They are used to put the phone back to a factory state, a hard reset if you will. It means you can always revert back to stock should you want/need to send it in for repair
As for GPe files, they are not for flashing and are source files to make your own software
EddyOS said:
What do you mean 'work'? They are used to put the phone back to a factory state, a hard reset if you will. It means you can always revert back to stock should you want/need to send it in for repair
As for GPe files, they are not for flashing and are source files to make your own software
Click to expand...
Click to collapse
OK that's the answer! GPE files are the source? same for the zip file next the ruu?
No, the RUU and the 1GB ZIP are the same thing but flashed in different ways...
The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation
Basic Steps but...
Not worked for me, i downloaded right htcdev rom for my desire c
Waiting for device... is appeared and no way out.
Any Ideas??
EddyOS said:
No, the RUU and the 1GB ZIP are the same thing but flashed in different ways...
The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation
Click to expand...
Click to collapse
an0ther said:
You must have s-off and super cid "11111111" to flash ruu that are not specific to your phone. You do not have to lock your bootloader. Again, you MUST have s-off and super cid! As long as you have those, you can pretty much convert your phone to whichever you want. I always recommend downgrading your hboot to 1.44 before doing this. You need encrypted ruu's to use the "fastboot oem rebootRUU" mode. Remember to flash stock recovery if you want OTA updates. I have never used the .exe files. I converted my att htc one to google edition, then back, then developer, then back. Its really no different than just running roms, but at least you get a new splash screen and bootloader with each.
http://forum.xda-developers.com/showthread.php?t=2358781 This is the google edition conversion link I used my first time converting my phone. if you look at post 2, it shows how to go back to stock "or pretty much any ruu"
Click to expand...
Click to collapse
Hey, sorry for bothering you, i am trying to revert my Htc desire 510 to stock, i do not have a backup. I found files on the htcdev.com and thought they were Roms (easy catch). Unfortunately they are not. I dont even know what to do with these files inorder to get my rom in place. pleace help me.
Zubagy said:
Hey, sorry for bothering you, i am trying to revert my Htc desire 510 to stock, i do not have a backup. I found files on the htcdev.com and thought they were Roms (easy catch). Unfortunately they are not. I dont even know what to do with these files inorder to get my rom in place. pleace help me.
Click to expand...
Click to collapse
There are no more RUU on htcdev.com, these files are kernel source code and not useful to restore your phone. Can you post the output of "fastboot getvar all" (hide your IMEI and serialno), I'll check if I can find something for you.
alray said:
There are no more RUU on htcdev.com, these files are kernel source code and not useful to restore your phone. Can you post the output of "fastboot getvar all" (hide your IMEI and serialno), I'll check if I can find something for you.
Click to expand...
Click to collapse
Thank you for your response. This is what i get
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 01.02.012_U10251_39.08.40922
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: xxxx
INFOimei: xxxx
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: a11_ul
INFOplatform: hTCBmsm8916
INFOmodelid: 0PCV20000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 295e1798
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOmfg-name: 1001
all: Done!
Zubagy said:
Thank you for your response. This is what i get
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 01.02.012_U10251_39.08.40922
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: xxxx
INFOimei: xxxx
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: a11_ul
INFOplatform: hTCBmsm8916
INFOmodelid: 0PCV20000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 295e1798
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOmfg-name: 1001
all: Done!
Click to expand...
Click to collapse
There are 3 RUU for Vodafone UK's Desire 510:
1.51.161.10
1.51.161.11
1.51.161.12
Unfortunately these files are only available from a paid site (ir-file)
Not sure which one you'll need since your version-main is blank
Here are the files name just in case you can find elsewhere than ir-file:
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.10_Radio_01.02.012_U10251_39.08.40922_release_416938_signed.zip
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.11_Radio_01.02.012_U10251_39.08.40922_release_427262_signed.zip
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.12_Radio_01.02.012_U10251_39.08.40922_release_450233_combined_signed.zip
alray said:
There are 3 RUU for Vodafone UK's Desire 510:
1.51.161.10
1.51.161.11
1.51.161.12
Unfortunately these files are only available from a paid site (ir-file)
Not sure which one you'll need since your version-main is blank
Here are the files name just in case you can find elsewhere than ir-file:
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.10_Radio_01.02.012_U10251_39.08.40922_release_416938_signed.zip
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.11_Radio_01.02.012_U10251_39.08.40922_release_427262_signed.zip
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.12_Radio_01.02.012_U10251_39.08.40922_release_450233_combined_signed.zip
Click to expand...
Click to collapse
Thankyou for your help, ill get started on looking for them. does this work, found it but still have my doubts... not yet downloaded it.
https://www.dropbox.com/s/cp3hif7sg...51_39.08.40922_release_398419_signed.rar?dl=0
Zubagy said:
Thankyou for your help, ill get started on looking for them. does this work, found it but still have my doubts... not yet downloaded it.
https://www.dropbox.com/s/cp3hif7sg...51_39.08.40922_release_398419_signed.rar?dl=0
Click to expand...
Click to collapse
no, your phone is S-ON and branded to vodafone UK so you can only use RUU for vodafone UK (x.xx.161.x).
1.51.401.1 is for HTC Europe WWE not vodafone.
alray said:
no, your phone is S-ON and branded to vodafone UK so you can only use RUU for vodafone UK (x.xx.161.x).
1.51.401.1 is for HTC Europe WWE not vodafone.
Click to expand...
Click to collapse
A developer sent me this link, looks like it is The ONE. But it looks a lower version than the ones that u mentioned above.
https://mega.nz/#!d4ZknKYT!ZhCHoiBSNJl3pBO_G-uv518ssNrGDY6UPH4EpqZ7qog
Zubagy said:
A developer sent me this link, looks like it is The ONE. But it looks a lower version than the ones that u mentioned above.
https://mega.nz/#!d4ZknKYT!ZhCHoiBSNJl3pBO_G-uv518ssNrGDY6UPH4EpqZ7qog
Click to expand...
Click to collapse
I would try this one
alray said:
I would try this one
Click to expand...
Click to collapse
Oh, ok, then let me get started with it. By the way, do u happen to know where i can also pick any custom ROMs for the 64bit, i checked out the cm12, but its gat bugs
Zubagy said:
Oh, ok, then let me get started with it. By the way, do u happen to know where i can also pick any custom ROMs for the 64bit, i checked out the cm12, but its gat bugs
Click to expand...
Click to collapse
not sure for x64 but everything should be here: http://forum.xda-developers.com/desire-510
So basically my predicament is in the title.
Everything has been wiped from the phone
I cannot adb only fastboot.
I really need help, as the phone is from Germany and I live in Canada (and can't seem to ever get through to HTC Ger)
INFOversion: 0.5
INFOversion-bootloader: 1.54.0000
INFOversion-baseband: 4A.17.3250.14
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.24.161.1
INFOversion-misc: PVT SHIP S-ON
INFOserialno: -----
INFOimei:-----
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: VODAP102
INFObattery-status: good
INFObattery-voltage: 4295mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-d16dc66985
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Because of S-On, I am not able to flash anything to the phone. I really don't want to have to buy a new phone. Can anyone help?
This all started because I wanted to unroot to fix an microphone issue!
alrmsrn said:
So basically my predicament is in the title.
Everything has been wiped from the phone
I cannot adb only fastboot.
I really need help, as the phone is from Germany and I live in Canada (and can't seem to ever get through to HTC Ger)
Because of S-On, I am not able to flash anything to the phone. I really don't want to have to buy a new phone. Can anyone help?
This all started because I wanted to unroot to fix an microphone issue!
Click to expand...
Click to collapse
S-off Ur phone useing rumrunner.us
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 12:52 AM ---------- Previous post was at 12:49 AM ----------
alrmsrn said:
So basically my predicament is in the title.
Everything has been wiped from the phone
I cannot adb only fastboot.
I really need help, as the phone is from Germany and I live in Canada (and can't seem to ever get throug
Because of S-On, I am not able to flash anything to the phone. I really don't want to have to buy a new phone. Can anyone help?
This all started because I wanted to unroot to fix an microphone issue!
Click to expand...
Click to collapse
Unlock Ur bootloder first useing htsdev
Sent from my HTC One using XDA Premium 4 mobile app
alrmsrn said:
So basically my predicament is in the title.
Everything has been wiped from the phone
I cannot adb only fastboot.
I really need help, as the phone is from Germany and I live in Canada (and can't seem to ever get through to HTC Ger)
Because of S-On, I am not able to flash anything to the phone. I really don't want to have to buy a new phone. Can anyone help?
This all started because I wanted to unroot to fix an microphone issue!
Click to expand...
Click to collapse
Mate, you've an unlocked bootloader?
If yes, flash a recovery from fastboot, do an erase cache, boot in it and sideload a rom
And, an advice, remove your IMEI and S/N from your post.
@apood_vip, please, remove from the quote the imei and S/N
apood_vip said:
S-off Ur phone useing rumrunner.us
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 12:52 AM ---------- Previous post was at 12:49 AM ----------
Unlock Ur bootloder first useing htsdev
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Bootloader cannot be unlocked because it is in S-On
You don't need s off for bootloader unlock
Sent from my HTC One X using xda app-developers app
alrmsrn said:
Bootloader cannot be unlocked because it is in S-On
Click to expand...
Click to collapse
Mate, isn't right this
With S-ON you can unlock the bootlader and flash recovery, rom and much more
Follow these 2 video tutorials (xda official) to unlock bootloader and install custom recovery.
http://forum.xda-developers.com/htc-one#root
as said, s-off not required
alray said:
Follow these 2 video tutorials (xda official) to unlock bootloader and install custom recovery.
http://forum.xda-developers.com/htc-one#root
as said, s-off not required
Click to expand...
Click to collapse
error: cannot load 'Unlock_code.bin'
This is the error I am constantly getting.
alrmsrn said:
error: cannot load 'Unlock_code.bin'
This is the error I am constantly getting.
Click to expand...
Click to collapse
Is the unlock code in the same folder as fastboot?
alrmsrn said:
This all started because I wanted to unroot to fix an microphone issue!
Click to expand...
Click to collapse
also, dont use the same Unlock_code.bin file that you used the first time when you unlocked your bootloader to root the phone. Every time the bootloader is relocked, it generate a different token, you need a new unlock code that match with the new identifier token.
Working
Hey guys,
Thank you for all the information.
I realized what happened. For some reason the ADK Bundle I was using was missing a code. So I had to re download, and I finally got it un-bricked.
I was ****ting myself for quite a while. But I reinstalled HTC Stock ROM, and she is working like a beauty. Only thing is the microphone issue. But I do not receive or make many calls. So not really bothering me!
Thanks for all the replies!
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.
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: XXXXXX
imei: XXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4333mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2485651 here is a list of firmware
You can downgrade your hboot and then run the RUU. Make sure it's a stock hboot and NOT a modified one (it'll say either or). You can open the firmeware zips (not extract) and open and edit the android.info text file and add in your CID and model id as required if necessary
You can then flash the RUU as normal after. No need to step down hboots
consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified.
Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this 4.18.502.7 decrypted ROM. and the instructions are from clsA:
Copy your downloaded file to your fastboot / adb folder
Rename the file Rom.zip
open a command prompt in the same folder (shift + right click - command prompt here )
adb reboot-bootloader
fastboot commands:
fastboot oem rebootRUU
wait for the Silver HTC logo
fastboot flash zip Rom.zip
the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip Rom.zip
most times the green status bar does not reach the 100% mark. So when the output in the command window is complete, you can reboot:
fastboot reboot
Click to expand...
Click to collapse
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.
Decrypted ROM Failed
majmoz said:
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this and the instructions are from clsA:
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.
Click to expand...
Click to collapse
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?
consequense said:
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?
Click to expand...
Click to collapse
you can try it again but flash this firmware first and it should work.
http://d-h.st/a1w
You could also use the full RUU after flashing the above firmware. http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe