Just upgraded my T-Mobile M9 to Marshmallow and have been playing around with it. I've flashed TWRP and ElementalX 4.00, but I can't root it. Every time I do, it fails to boot. With systemless, it bootloops, and with the standard method, it gets stuck on one of the boot screens. Please help!
ROOT
Hey friend had the same problem as you couldnt get root on TMO MM update, but finally got it this morning by flashing SuperSU v2.62 in recovery and it stuck, so search in SuperSU thread for link to it, hope this helps
I took the OTA then loaded TWRP 3.0 and loaded the SuperSU Beta (2.67 I believe) and had problems with boot loop. I went back into twrp and loaded the current stable ver 2.65 and it worked fine.
kelvin216 said:
Hey friend had the same problem as you couldnt get root on TMO MM update, but finally got it this morning by flashing SuperSU v2.62 in recovery and it stuck, so search in SuperSU thread for link to it, hope this helps
Click to expand...
Click to collapse
ThePhoneGeek said:
I took the OTA then loaded TWRP 3.0 and loaded the SuperSU Beta (2.67 I believe) and had problems with boot loop. I went back into twrp and loaded the current stable ver 2.65 and it worked fine.
Click to expand...
Click to collapse
Thanks, both of you guys. Finally got it rooted.
Can anyone details the steps for this
I have S-Off rooted stock 5.1 currently. I would like to do a clean install of MM and the re-root.
I assume I need to
1. Wipe phone with Twrp
2. Flash stock recovery (do I need to wipe again with stock?)
3. Take the OTA
4. Flash Twrp again
5. Flash SuperSU 2.6.5
Is that it?
DssTrainer said:
Can anyone details the steps for this
I have S-Off rooted stock 5.1 currently. I would like to do a clean install of MM and the re-root.
I assume I need to
1. Wipe phone with Twrp
2. Flash stock recovery (do I need to wipe again with stock?)
3. Take the OTA
4. Flash Twrp again
5. Flash SuperSU 2.6.5
Is that it?
Click to expand...
Click to collapse
OR just flash the MarshMallow RUU that's available and have have those steps taken care of. Then Install TWRP and SuperSU.
But as far as kernels go ElementalX didn't work for me.
@rgao007 how did the kernel work for you? I couldn't get Signal when I flashed it.
Tachi91 said:
OR just flash the MarshMallow RUU that's available and have have those steps taken care of. Then Install TWRP and SuperSU.
But as far as kernels go ElementalX didn't work for me.
@rgao007 how did the kernel work for you? I couldn't get Signal when I flashed it.
Click to expand...
Click to collapse
ElementalX worked fine for me. Are you sure you flashed 4.00?
Tachi91 said:
OR just flash the MarshMallow RUU that's available and have have those steps taken care of. Then Install TWRP and SuperSU.
But as far as kernels go ElementalX didn't work for me.
@rgao007 how did the kernel work for you? I couldn't get Signal when I flashed it.
Click to expand...
Click to collapse
Ok just tried flashing the RUU to my phone. It failed: Error 155 Unknown Error
Now my phone stuck at the download screen.
I followed RUU to try to recover and it tried again, but same error.
I'll better explain my current settings
HTC One M9 Tmobile 5.1
S-Off with Sunshine
TWRP installed and rooted
I want to goto Marshmallow. I know I can't take OTA so I downloaded the RUU here:
http://www.htc.com/us/support/htc-one-m9-t-mobile/news/
Then tried to run it and update my phone.
So what did I do wrong and how can I get my phone back?
Thanks
-EDIT- from what i've read online I need to relock my bootloader. But not sure how to get out of this download mode screen. Holding the powerbutton for 30 secs does nothing.
DssTrainer said:
Ok just tried flashing the RUU to my phone. It failed: Error 155 Unknown Error
Now my phone stuck at the download screen.
I followed RUU to try to recover and it tried again, but same error.
I'll better explain my current settings
HTC One M9 Tmobile 5.1
S-Off with Sunshine
TWRP installed and rooted
I want to goto Marshmallow. I know I can't take OTA so I downloaded the RUU here:
http://www.htc.com/us/support/htc-one-m9-t-mobile/news/
Then tried to run it and update my phone.
So what did I do wrong and how can I get my phone back?
Thanks
Click to expand...
Click to collapse
Wrong RUU there buddy, that's lollipop.
Heres the Marshmallow RUU
http://dl3.htc.com/application/RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.7.exe
Before flashing the RUU make sure you have the correct T-Mobile CID and MID.
Tachi91 said:
Wrong RUU there buddy, that's lollipop.
Heres the Marshmallow RUU
http://dl3.htc.com/application/RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.7.exe
Before flashing the RUU make sure you have the correct T-Mobile CID and MID.
Click to expand...
Click to collapse
Actually their page has been updated it seems. Same file name as the one you linked
http://screencast.com/t/FXrLl5tYoXB7
It's updated now and the file is the same as the one you linked.
Either way even if I was flashing lollipop again it still shouldn't fail.
Error 155 points to unlocked bootloader issues. Is that an issue? Do I need to re-lock to flash MM?
Do I need to flash stock recovery back first?
I set the mid and cid to tmobile when I first unlocked it.
---------- Post added at 10:16 PM ---------- Previous post was at 09:48 PM ----------
Ok I locked the bootloader, checked my MID and CID.. all looks correct
Code:
c:\sdk\platform-tools>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) RELock successfully...
OKAY [ 0.090s]
finished. total time: 0.091s
c:\sdk\platform-tools>fastboot devices
FA53XYJ12302 fastboot
c:\sdk\platform-tools>fastboot getvar mid
mid: 0PJA120
finished. total time: 0.003s
c:\sdk\platform-tools>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.053s]
finished. total time: 0.054s
c:\sdk\platform-tools>
---------- Post added at 10:24 PM ---------- Previous post was at 10:16 PM ----------
Ok bootloader locked.... Just tried again.. Error 155 again
Maybe I need to flash stock recovery and try the OTA
---------- Post added at 10:32 PM ---------- Previous post was at 10:24 PM ----------
Ok now I see if you are s-off you shouldn't need to relock bootloader.
Then wtf.
DssTrainer said:
Actually their page has been updated it seems. Same file name as the one you linked
http://screencast.com/t/FXrLl5tYoXB7
It's updated now and the file is the same as the one you linked.
Either way even if I was flashing lollipop again it still shouldn't fail.
Error 155 points to unlocked bootloader issues. Is that an issue? Do I need to re-lock to flash MM?
Do I need to flash stock recovery back first?
I set the mid and cid to tmobile when I first unlocked it.
---------- Post added at 10:16 PM ---------- Previous post was at 09:48 PM ----------
Ok I locked the bootloader, checked my MID and CID.. all looks correct
Code:
c:\sdk\platform-tools>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) RELock successfully...
OKAY [ 0.090s]
finished. total time: 0.091s
c:\sdk\platform-tools>fastboot devices
FA53XYJ12302 fastboot
c:\sdk\platform-tools>fastboot getvar mid
mid: 0PJA120
finished. total time: 0.003s
c:\sdk\platform-tools>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.053s]
finished. total time: 0.054s
c:\sdk\platform-tools>
---------- Post added at 10:24 PM ---------- Previous post was at 10:16 PM ----------
Ok bootloader locked.... Just tried again.. Error 155 again
Maybe I need to flash stock recovery and try the OTA
---------- Post added at 10:32 PM ---------- Previous post was at 10:24 PM ----------
Ok now I see if you are s-off you shouldn't need to relock bootloader.
Then wtf.
Click to expand...
Click to collapse
Either theres typo, but this is what I get for MID
Code:
C:\Users\lvale\Desktop>fastboot getvar mid
mid: 0PJA12000
finished. total time: -0.000s
Idk if RUU is that stingy for a couple extra zeros missing. Make sure you write the MID with all the zeros like mine.
Also try flashing the rom.zip itself. When the RUU opens up use TaskManager to find the file and in that same directory is a rom.zip and the HTC fastboot witch will allow you to use flash the rom.zip and youll see the verbose output instead of the RUU just saying it failed for whatever reason.
Save the fastboot.exe(In RUU temp folder) since its modified to allow you to flash huge zip files.
Tachi91 said:
Either theres typo, but this is what I get for MID
Code:
C:\Users\lvale\Desktop>fastboot getvar mid
mid: 0PJA12000
finished. total time: -0.000s
Idk if RUU is that stingy for a couple extra zeros missing. Make sure you write the MID with all the zeros like mine.
Also try flashing the rom.zip itself. When the RUU opens up use TaskManager to find the file and in that same directory is a rom.zip and the HTC fastboot witch will allow you to use flash the rom.zip and youll see the verbose output instead of the RUU just saying it failed for whatever reason.
Save the fastboot.exe(In RUU temp folder) since its modified to allow you to flash huge zip files.
Click to expand...
Click to collapse
Ok I'll try later today and let you know.
Thanks for the help
Ok I updated my mid and actually redownloaded the RUU file just in case.. This time all went perfect!
Thanks for your help! Funny that I was able to flash it initially without the missing zeros.. if that was the actual inhibitor... It was an unlocked AT&T model that I brought to Tmobile and after setting the MID and CID with less zeros, I was able to flash the tmus version of lollipop without issue.
In any case, Thanks all for the help Time for me to enjoy some marshmallow love
okay i can't get the MM RUU to install on my M9
I have a rooted stock rom
TWRP
S-ON and Bootloader unlocked
When i first ran the RUU I got error 131 Customer ID
So i checked my MID and CID, they seem okay.
I locked the bootloader and tried using the RUU again via download mode, same error
so I needed my phone back for work next the day so i unlocked my bootloader again and restored a recovery I created early. any ideas on what i should do?
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar mid
mid: 0PJA12000
finished. total time: -0.000s
please help me. i have a htc one m9. t mobile, 0PJA120, it keeps restartin. how can i get its original zip file to flash. it is not recognising any pc through usb.
Related
I think I may have soft bricked my HTC Raider.
I was attempting to flash CM9 on my HTC. I followed the pre-flash procedures (Wiping Data, etc). Then, once it was complete, I rebooted the phone. The phone could not get past the CM9 Blue Tunnel animation. I left it there for about an hour, but nothing happened. I can still access my recovery and bootloader. I have tried flashing another ROM, as well as restoring a Nandroid backup I made, but they all lead to the white HTC screen. My Raider has S-ON.
User MzzSarahx3 had an extremely similar case, except that person had an AT&T Vivid, as seen here:
http://forum.xda-developers.com/showthread.php?t=1416836&page=51
MzzSarahx3 managed to fix the problem by running an RUU, so that is why I believe I can fix my situation by doing the same. I am aware of the RUU Collection that Football uploaded, but clicking on a link on FileFactory will give me an error saying that all download slots are in use.
So could somebody please link me, or upload, an ICS RUU for the HTC Raider on Rogers? Help would be much appreciated.
Just means site is busy keep checking
Sent from my HTC PH39100 using xda premium
ronnie498 said:
Just means site is busy keep checking
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
I have been clicking on that link since this morning. And it still gives me the same message. I will continue to check, though.
Does anyone have an alternate solution?
The stock Bell ICS RUU should work fine on your Rogers Raider. ( I have a Bell Raider but installed it on my buddy's Rogers Raider).
I'm uploading the stock Bell ICS RUU to Depositfiles right now but its gonna take an hour. I'll update my post with the link when it's done.
You can probably find the stock Bell ICS RUU on various threads in the forum. I believe that's where I got it from originally.
Note that if you have unlocked your bootloader (via htcdev), the stock RUU will refuse to install !
LaZiODROID said:
The stock Bell ICS RUU should work fine on your Rogers Raider. ( I have a Bell Raider but installed it on my buddy's Rogers Raider).
I'm uploading the stock Bell ICS RUU to Depositfiles right now but its gonna take an hour. I'll update my post with the link when it's done.
You can probably find the stock Bell ICS RUU on various threads in the forum. I believe that's where I got it from originally.
Note that if you have unlocked your bootloader (via htcdev), the stock RUU will refuse to install !
Click to expand...
Click to collapse
Thank you very much for uploading it!
I am definitely looking forward to using my phone again!
BTW I have looked around for the Bell ICS RUU on these forums, but did not find anything. The closest thing I found was this:
http://forum.xda-developers.com/showthread.php?t=1672800&highlight=bell+ics+ruu
But they said it was not a RUU so.....
I have uploaded the Bell ICS RUU to DepositFiles. You're welcome!
Filename: RUU_HOLIDAY_ICS_35_S_BM_3.38.666.2_Radio_3.04.4740.11_34.29.701040.22_release_255916_signed.exe
http://depositfiles.com/files/ofalwm57q
LaZiODROID said:
I have uploaded the Bell ICS RUU to DepositFiles. You're welcome!
Filename: RUU_HOLIDAY_ICS_35_S_BM_3.38.666.2_Radio_3.04.4740.11_34.29.701040.22_release_255916_signed.exe
Click to expand...
Click to collapse
Umm, well I downloaded the RUU file you kindly uploaded, but I have encountered a problem.
ERROR [131]: CUSTOMER ID ERROR
I have tried many times. Got this error every time. I guess it is because I have a Rogers phone and attempting to update using a Bell RUU.
Any suggestions?
LeoCFZ said:
Umm, well I downloaded the RUU file you kindly uploaded, but I have encountered a problem.
ERROR [131]: CUSTOMER ID ERROR
I have tried many times. Got this error every time. I guess it is because I have a Rogers phone and attempting to update using a Bell RUU.
Any suggestions?
Click to expand...
Click to collapse
Damn... I don't remember having to do that for my buddy's Rogers Raider. Sorry.. it was some time ago.
He's here so I just checked his phone... we must have put in the SuperCID back then (which may accept any RUU?)
C:\Users\Master>fastboot getvar cid
cid: 11111111
finished. total time: 0.000s
and I ran mine (actual Bell Raider).:
C:\Users\Master>fastboot getvar cid
cid: BM___001
finished. total time: 0.000s
Feeling adventurous? I'm not sure if you need to be S-OFF to do this (or have unlocked bootloader, or even both) but...
You can change the CID via fastboot.
Fastboot commands that you can do: (thank you jmone from showpost.php?p=25187040&postcount=199)
(to check your current CID - write it down?)
fastboot getvar cid
(to write a new CID to the phone)
fastboot oem writecid 11111111 (where the 11111111 contains the CID you want - you can try the 11111111 (is that known as SuperCID?) or you can try mine, which is BM___001 as specified above)
(then reboot into bootloader mode)
fastboot reboot-bootloader
(then if it reboots back into fastboot mode, you can run this to verify your desired CID made it)
fastboot getvar cid
Then maybe the RUU will allow itself to install?
LaZiODROID said:
Damn... I don't remember having to do that for my buddy's Rogers Raider. Sorry.. it was some time ago.
He's here so I just checked his phone... we must have put in the SuperCID back then (which may accept any RUU?)
C:\Users\Master>fastboot getvar cid
cid: 11111111
finished. total time: 0.000s
and I ran mine (actual Bell Raider).:
C:\Users\Master>fastboot getvar cid
cid: BM___001
finished. total time: 0.000s
Feeling adventurous? I'm not sure if you need to be S-OFF to do this (or have unlocked bootloader, or even both) but...
You can change the CID via fastboot.
Fastboot commands that you can do: (thank you jmone from showpost.php?p=25187040&postcount=199)
(to check your current CID - write it down?)
fastboot getvar cid
(to write a new CID to the phone)
fastboot oem writecid 11111111 (where the 11111111 contains the CID you want - you can try the 11111111 (is that known as SuperCID?) or you can try mine, which is BM___001 as specified above)
(then reboot into bootloader mode)
fastboot reboot-bootloader
(then if it reboots back into fastboot mode, you can run this to verify your desired CID made it)
fastboot getvar cid
Then maybe the RUU will allow itself to install?
Click to expand...
Click to collapse
I typed in the commands and I got this:
c:\Users\Leo Zheng\Desktop\Vivid Toolkit\Data>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO holiday_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.076s]
finished. total time: 1.076s
c:\Users\Leo Zheng\Desktop\Vivid Toolkit\Data>fastboot getvar cid
cid: ROGER001
finished. total time: 0.002s
So, that means the SuperCID did not manage to write. I searched around and found hints about something called Radio S-OFF or Gold Card, but it was for a different HTC phone...
Is there a guide to follow so i could get this?
BTW SuperCID would allow the user to use any RUU.
LeoCFZ said:
I typed in the commands and I got this:
c:\Users\Leo Zheng\Desktop\Vivid Toolkit\Data>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO holiday_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.076s]
finished. total time: 1.076s
c:\Users\Leo Zheng\Desktop\Vivid Toolkit\Data>fastboot getvar cid
cid: ROGER001
finished. total time: 0.002s
So, that means the SuperCID did not manage to write. I searched around and found hints about something called Radio S-OFF or Gold Card, but it was for a different HTC phone...
Is there a guide to follow so i could get this?
BTW SuperCID would allow the user to use any RUU.
Click to expand...
Click to collapse
Ahhh.. so you need to be S-OFF it seems. The S-OFF procedure isn't super easy, but it's nice to have (because with S-OFF, the custom roms you install will be able to automatically flash their kernel. With S-ON, to run a custom rom, you need to flash the kernel separately... not a huge deal, but having S-OFF is convenient if you like to try different custom roms). To S-OFF, you have to be willing to void your phone's warranty.
Theres gotta be the Roger RUU out there somewhere (that is ICS). I have the Rogers Gingerbread RUU... but I think it will only work if you havent upgraded your phone to ICS yet...
LaZiODROID said:
Ahhh.. so you need to be S-OFF it seems. The S-OFF procedure isn't super easy, but it's nice to have (because with S-OFF, the custom roms you install will be able to automatically flash their kernel. With S-ON, to run a custom rom, you need to flash the kernel separately... not a huge deal, but having S-OFF is convenient if you like to try different custom roms). To S-OFF, you have to be willing to void your phone's warranty.
Theres gotta be the Roger RUU out there somewhere (that is ICS). I have the Rogers Gingerbread RUU... but I think it will only work if you havent upgraded your phone to ICS yet...
Click to expand...
Click to collapse
I also have the Gingerbread RUU and yes, it does not work. You were right about the ICS RUU out there somewhere.
I dug deeper into the comments of Football's thread on the Shipped RUU Collection to see if anyone had trouble downloading from FileFactory and somebody requested the Rogers ICS RUU mirror there. I downloaded it any now my cell is back to being operational!
http://forum.xda-developers.com/showthread.php?t=1338919&highlight=football&page=14
Thanks to LaZiODROID, ronnie498,and Gene Poole for all their help!
Well, I also like to make sure I don't make the same mistake again. Anyone know why my phone ended up the way it is?
LeoCFZ said:
I also have the Gingerbread RUU and yes, it does not work. You were right about the ICS RUU out there somewhere.
I dug deeper into the comments of Football's thread on the Shipped RUU Collection to see if anyone had trouble downloading from FileFactory and somebody requested the Rogers ICS RUU mirror there. I downloaded it any now my cell is back to being operational!
http://forum.xda-developers.com/showthread.php?t=1338919&highlight=football&page=14
Thanks to LaZiODROID, ronnie498,and Gene Poole for all their help!
Well, I also like to make sure I don't make the same mistake again. Anyone know why my phone ended up the way it is?
Click to expand...
Click to collapse
Amazing! Glad it worked out. Thanks for that link. I'll be archiving a copy of that Rogers RUU.
As for why your phone wouldnt boot with CM9... Is CM9 still in development? Maybe you should try a different ROM.
I'm using Pegasus right now and enjoying it. (As per kozmik I did have to do an extra step to get my LTE going, but it was pretty easy).
Remember to do a backup and your 4 wipes (data, cache, dalvik,and /system) before you install the rom, of course!
OK, thanks for the tips and the ROM suggestion.
I'll try Pegasus next.
LeoCFZ said:
OK, thanks for the tips and the ROM suggestion.
I'll try Pegasus next.
Click to expand...
Click to collapse
Thanks for this post. I had the same problem and was looking on the site to find an answer....
I uploaded all the RUU's here including the rogers one
http://forum.xda-developers.com/showthread.php?t=2013122
from my HTC PH39100 using xda premium
Here's today's brain teaser of a question: if you have Super CID on, do you need to have the bootloader re-locked in order to run any RUU?
Spazmogen said:
Here's today's brain teaser of a question: if you have Super CID on, do you need to have the bootloader re-locked in order to run any RUU?
Click to expand...
Click to collapse
Yes, I am pretty sure you do. I re-locked mine whenever I had to use a RUU.
I'm currently trying to upgrade to the latest firmware and I'm having trouble with the process. I have the Bootloader unlocked and S-off. Any ideas on why the firmware zip is not flashing? Any help is appreciated, Thanks!
C:\adb>fastboot reboot
rebooting...
finished. total time: 5.554s
C:\adb>adb reboot bootloader
C:\adb>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adb>fastboot flash zip C:\adb\firmware.zip
error: cannot load 'C:\adb\firmware.zip'
progressive_edm said:
I'm currently trying to upgrade to the latest firmware and I'm having trouble with the process. I have the Bootloader unlocked and S-off. Any ideas on why the firmware zip is not flashing? Any help is appreciated, Thanks!
C:\adb>fastboot reboot
rebooting...
finished. total time: 5.554s
C:\adb>adb reboot bootloader
C:\adb>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adb>fastboot flash zip C:\adb\firmware.zip
error: cannot load 'C:\adb\firmware.zip'
Click to expand...
Click to collapse
be abit clearer with what youre asking. are you trying to get the latest stock 4.2.2 that has recently came out? or are you actually trying to update the firmware?
Luke-b said:
be abit clearer with what youre asking. are you trying to get the latest stock 4.2.2 that has recently came out? or are you actually trying to update the firmware?
Click to expand...
Click to collapse
I'm trying to update the actual firmware (2.24.401.12)
progressive_edm said:
I'm trying to update the actual firmware (2.24.401.12)
Click to expand...
Click to collapse
in what format do you have this update you say you have a .ZIP what zip is this?
you say you are s-off so to get this update i would return your Rom and recovery both to stock and then check your Cid and if its available for you CID recieve the OTA update to change your CID and MID so you can receive it.
The OTA update will update everything. so your firmware, update it to 2.24.401.12 and also to the latest radio
Luke-b said:
in what format do you have this update you say you have a .ZIP what zip is this?
you say you are s-off so to get this update i would return your Rom and recovery both to stock and then check your Cid and if its available for you CID recieve the OTA update to change your CID and MID so you can receive it.
The OTA update will update everything. so your firmware, update it to 2.24.401.12 and also to the latest radio
Click to expand...
Click to collapse
I'ts the (2.24.401.12) firmware zip. Got it from Vomer's post if that helps http://forum.xda-developers.com/showthread.php?t=2183023&page=2496 . And i thought with having S-off you could just update without worrying about the Cid and Mid? I will take your suggestion into consideration, thanks.
Yes you can update the firmware without changing the cid and mid. But that only refers to the hboot. For full upgrade to 4.2.2 if it's not already available for your cid then you would need to change the cid and mid to receive it. And remember to have a stock recovery. There are guides available if you look through the thread about the update people have posted how to do this. It's Easiest and safest way to do this.
fastboot commands to run RUU files will get you into trouble
Sent from my HTC One using xda app-developers app
hi guys ive been off the htc one thread for a few months and so much has happend just need some help
ive unlocked the bootloader
done S OFF
done this http://forum.xda-developers.com/showthread.php?t=2316726
my phone is a 3uk branded rom with cidnum: H3G__001 (which i changed to fastboot oem writecid 11111111)
so now ive done them basically my phone is as good as sim free (apart from the sim lock)
so if i needed to return phone i just follow steps and reinstall any stock rom (as a 3 branded one i dont think they is any)
and 3 would never know any different
thanks
A great start would be to check the other 15,000 threads covering this subject.
Is there a question in there somewhere?
brockyneo said:
hi guys ive been off the htc one thread for a few months and so much has happend just need some help
ive unlocked the bootloader
done S OFF
done this http://forum.xda-developers.com/showthread.php?t=2316726
my phone is a 3uk branded rom with cidnum: H3G__001 (which i changed to fastboot oem writecid 11111111)
so now ive done them basically my phone is as good as sim free (apart from the sim lock)
so if i needed to return phone i just follow steps and reinstall any stock rom (as a 3 branded one i dont think they is any)
and 3 would never know any different
thanks
Click to expand...
Click to collapse
I think he is asking about what he will need to do if he needs to return to stock for a phone return/exchange.
brockyneo,
Since you are s-off you can reset everything needed before returning the phone if needed.
However since there is no RUU for your device, it will be a little harder than just re-installing a stock rom. Since you flashed a modified hboot you will need to reset all your sytem stuff back like hboot, splash screen, recovery, etc before you can relock the phone so it looks the same as it did out of the box.
I won't go into all the steps needed, but just know if you need to go back to stock there are many threads here that detail how to do so.
Just keep your bootloader unlocked and keep s-off until you need to return/exchange the device.
If you haven't flashed a custom recovery yet, do:
fastboot boot customrecovery.img
And do a backup. This will backup stock ROM and recovery. There is no 3 RUU and probably never will be, I don't know what their deal is..
Then to go back to stock, restore your backup, flash your recovery.img from your backup, change your CID back to original, flash a STOCK hboot, and last use Revone to lock the bootloader and then do s-on.
EDIT : just noticed on another thread you said you were running TrickDroid - disregard my post..
Sent from my HTC One using xda premium
ok guys i think ive screwed up big time i did a full wipe in cwm (sc card too) then was going to adb sideload the rom but now my pc doesnt reconise my phone i remember having to relock my bootloader to fix this so i went back to the original file in this thread http://forum.xda-developers.com/showthread.php?t=2316726
and relocked bootloader then when i tried to unlock it i get this error
sending 'unlocktoken' (0 KB)...
OKAY [ 0.159s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.173s
any help please
brockyneo said:
ok guys i think ive screwed up big time i did a full wipe in cwm (sc card too) then was going to adb sideload the rom but now my pc doesnt reconise my phone i remember having to relock my bootloader to fix this so i went back to the original file in this thread http://forum.xda-developers.com/showthread.php?t=2316726
and relocked bootloader then when i tried to unlock it i get this error
sending 'unlocktoken' (0 KB)...
OKAY [ 0.159s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.173s
any help please
Click to expand...
Click to collapse
Can you unlock using rev one?
redbull123 said:
Can you unlock using rev one?
Click to expand...
Click to collapse
problem i have is i have no rom installed and doesnt seem to be reconzing my phone only thing that works is fastboot
brockyneo said:
problem i have is i have no rom installed and doesnt seem to be reconzing my phone only thing that works is fastboot
Click to expand...
Click to collapse
can you post a photo of your hboot?
redbull123 said:
can you post a photo of your hboot?
Click to expand...
Click to collapse
sorry i have no way of taking a pic it was 1.44.0000
brockyneo said:
sorry i have no way of taking a pic it was 1.44.0000
Click to expand...
Click to collapse
What have you been using to unlock/lock your bootloader? HTC-Dev? This is just a guess - probably wrong, but you may need to ask for a newer unlock token and try again?
You have to go back and request a new token at htcdev.
FYI -once your bootloader is unlocked and you have s-off, KEEP IT THAT WAY. There is not really a reason to keep flipping, only if you need to return/exchange the phone.
Bootloader should not have an effect on ADB sideload. I'm unlocked and I use that all the time. If you have an issue with sideloading or something else, just post about it and someone will help, but you shouldn't need to flip your bootloader.
My htc one is a M7_UL with S-ON
HBOOT-1.56
OS-4.20.708.10
So i have stupidly wiped my device but i can still access the TWRP program
when i flash this RUU (OTA_M7_UL_JB43_SENSE55_MR_hTC_Asia_HK_3.63.708.3-2.24.708.4_release_339322l8015akovncw94nh.zip)
i was given this message:
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 64.528s
And obviously i cant get my os to work and im stuck in the 'HTC' startup screen when i reboot
Could any helpful people please show me what im doing wrong thanks
tiger6265 said:
My htc one is a M7_UL with S-ON
HBOOT-1.56
OS-4.20.708.10
So i have stupidly wiped my device but i can still access the TWRP program
when i flash this RUU (OTA_M7_UL_JB43_SENSE55_MR_hTC_Asia_HK_3.63.708.3-2.24.708.4_release_339322l8015akovncw94nh.zip)
i was given this message:
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 64.528s
And obviously i cant get my os to work and im stuck in the 'HTC' startup screen when i reboot
Could any helpful people please show me what im doing wrong thanks
Click to expand...
Click to collapse
Post output of fastboot getvar all,( minus imei & serial no )
That also an OTA, cant be flashed on its own
.
bored_stupid said:
Post output of fastboot getvar all,( minus imei & serial no )
That also an OTA, cant be flashed on its own
Click to expand...
Click to collapse
thanks for the reply
INFOversion: 0.5
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: ***********
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.20.708.10
INFOversion-misc: PVT SHIP S-ON
INFOserialno:**************
INFOimei: **************
INFOmeid: **************
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0714000
INFOcidnum: HTC__622
INFObattery-status: good
INFObattery-voltage: 4306mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-f6d46eca
INFOhbootpreupdate: 11
INFOgencheckpt: 0
also i would appreciate it if you could explain how i can flash an OTA
Do you have a working rom on the phone, If not the OTA is useless as its just that,( an update to the rom ) and not the full rom.
You need to download the RUU for your phone.
If you do have a working rom then you need to flash the stock recovery for your rom version and relock your bootloader,( your S-On ) to install the update.
bored_stupid said:
Do you have a working rom on the phone, If not the OTA is useless as its just that,( an update to the rom ) and not the full rom.
You need to download the RUU for your phone.
If you do have a working rom then you need to flash the stock recovery for your rom version and relock your bootloader,( your S-On ) to install the update.
Click to expand...
Click to collapse
unfortunately i dont have a working rom on my phone and i cant find an RUU with *.**.708.**
tiger6265 said:
unfortunately i dont have a working rom on my phone and i cant find an RUU with *.**.708.**
Click to expand...
Click to collapse
There is one site that may contain the *.**.708.**. Read here
http://forum.xda-developers.com/showthread.php?t=2725869&highlight=4+20+708+10&page=2
Other than that, I can only suggest a custom stock rom
bored_stupid said:
There is one site that may contain the *.**.708.**. Read here
http://forum.xda-developers.com/showthread.php?t=2725869&highlight=4+20+708+10&page=2
Other than that, I can only suggest a custom stock rom
Click to expand...
Click to collapse
in order for this to work do i need to have s-off?
and can i flash this?
tiger6265 said:
in order for this to work do i need to have s-off?
and can i flash this?
Click to expand...
Click to collapse
I cant answer that But if you can achieve S-Off then you could change your MID & CID in order to flash a alternative RUU
bored_stupid said:
I cant answer that But if you can achieve S-Off then you could change your MID & CID in order to flash a alternative RUU
Click to expand...
Click to collapse
thank you for all your help
bored_stupid said:
I cant answer that But if you can achieve S-Off then you could change your MID & CID in order to flash a alternative RUU
Click to expand...
Click to collapse
one last thing, can you reccommend me a good custom RUU?
tiger6265 said:
one last thing, can you reccommend me a good custom RUU?
Click to expand...
Click to collapse
Sent from my HTC One using Xparent Skyblue Tapatalk 2
ARHD 71.1 is as stock as you will get only better, plus its bang up to date
bored_stupid said:
I cant answer that But if you can achieve S-Off then you could change your MID & CID in order to flash a alternative RUU
Click to expand...
Click to collapse
when i try to install the ruu : RUU_M7_UL_JB_50_S_hTC_Asia_HK_2.24.708.4.zip
i get this message come up :
load_file: could not allocate 1399586263 bytes
im sure this is the correct RUU for my wiped phone but it wont install
tiger6265 said:
when i try to install the ruu : RUU_M7_UL_JB_50_S_hTC_Asia_HK_2.24.708.4.zip
i get this message come up :
load_file: could not allocate 1399586263 bytes
im sure this is the correct RUU for my wiped phone but it wont install
Click to expand...
Click to collapse
can you post a screenshot of your cmd prompt, would like to see what command you are doing excatly. also post a link to the ruu file.
---------- Post added at 03:13 PM ---------- Previous post was at 03:09 PM ----------
tiger6265 said:
when i try to install the ruu : RUU_M7_UL_JB_50_S_hTC_Asia_HK_2.24.708.4.zip
(...)
im sure this is the correct RUU for my wiped phone but it wont install
Click to expand...
Click to collapse
Btw, your phone firmware is currently 4.20.708.10 (from your fastboot getvar all) so you can't use a 2.24.708.4 ruu because its a downgrade and you must have s-off do downgrade.
alray said:
can you post a screenshot of your cmd prompt, would like to see what command you are doing excatly. also post a link to the ruu file.
---------- Post added at 03:13 PM ---------- Previous post was at 03:09 PM ----------
Btw, your phone firmware is currently 4.20.708.10 (from your fastboot getvar all) so you can't use a 2.24.708.4 ruu because its a downgrade and you must have s-off do downgrade.
Click to expand...
Click to collapse
how can i get s-off when i have no operation system
tiger6265 said:
how can i get s-off when i have no operation system
Click to expand...
Click to collapse
you can flash a custom rom and try to s-off the phone. then if you have s-off you will be able to flash almost everything.
still waiting for the screenshot
alray said:
you can flash a custom rom and try to s-off the phone. then if you have s-off you will be able to flash almost everything.
still waiting for the screenshot
Click to expand...
Click to collapse
right i ran it again and its different now and its stuck :/
as its a hong kong one its chinese http://pan.baidu.com/share/link?shareid=1432675332&uk=587915873
alray said:
you can flash a custom rom and try to s-off the phone. then if you have s-off you will be able to flash almost everything.
still waiting for the screenshot
Click to expand...
Click to collapse
do i have to relock my bootloader before flashing the custom stock that bored_stupid recomended (http://android-revolution-hd.blogspot.co.uk/p/android-revolution-hd-mirror-site-var.html)
this is when i used the custom stock:
http://gyazo.com/0036d2f32816f341199575c7baf43b3b
tiger6265 said:
right i ran it again and its different now and its stuck :/
as its a hong kong one its chinese http://pan.baidu.com/share/link?shareid=1432675332&uk=587915873
Click to expand...
Click to collapse
like i said above (post 13), you can't use this ruu because its a downgrade. S-OFF is required to downgrade so any RUU below your version (4.20.708.10) will not work. So trying to flash them = wasting your time.
---------- Post added at 05:55 PM ---------- Previous post was at 05:55 PM ----------
tiger6265 said:
do i have to relock my bootloader before flashing the custom stock that bored_stupid recomended (http://android-revolution-hd.blogspot.co.uk/p/android-revolution-hd-mirror-site-var.html)
Click to expand...
Click to collapse
this is a rom and you have to install it from custom recovery, no need to relock bootloader.
adb push or sideload it to your sdcard, then install it from twrp
alray said:
like i said above (post 13), you can't use this ruu because its a downgrade. S-OFF is required to downgrade so any RUU below your version (4.20.708.10) will not work. So trying to flash them = wasting your time.
---------- Post added at 05:55 PM ---------- Previous post was at 05:55 PM ----------
this is a rom and you have to install it from custom recovery, no need to relock bootloader
Click to expand...
Click to collapse
okay thanks, i dont know how to get the rom on my phone in the first place :s im not sure if i should go through the process of using ADB side loader
anyway im going to sleep now
tiger6265 said:
okay thanks, i dont know how to get the rom on my phone in the first place :s im not sure if i should go through the process of using ADB side loader
anyway im going to sleep now
Click to expand...
Click to collapse
ok
just post here when you'll be ready, I can assist you to ''adb push'' the rom to your phone, its quite easy to do.
Hello everyone,
I'm trying to return my HTC ONE Hboot 1.57 to Stock using an RUU, but its not working. It shows error 155 after a while.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4331mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Version-Main and BaseBand are empty for some reason...
I need your help please.
ahmadghizzawi said:
Hello everyone,
I'm trying to return my HTC ONE Hboot 1.57 to Stock using an RUU, but its not working. It shows error 155 after a while.
I need your help please.
Click to expand...
Click to collapse
Error 155 means your using the wrong RUU, post your fastboot getvar all please, remove your IMEI and serial number before posting.
Seanie280672 said:
Error 155 means your using the wrong RUU, post your fastboot getvar all please, remove your IMEI and serial number before posting.
Click to expand...
Click to collapse
Post Updated
Well, the Version is not showing for some reason.
ahmadghizzawi said:
Post Updated
Well, the Version is not showing for some reason.
Click to expand...
Click to collapse
ok, you have an M7U, you must pretty much have the latest version main otherwise known as firmware as your on HBOOT 1.57, it will also be the 401 firmware based on your cid, so my next question is, are you returning to stock for warranty purposes or you just want it working as im not so sure there is an RUU available for your device, however its my understanding, you can flash M7UL rom's, just the LTE parts will be skipped.
Seanie280672 said:
ok, you have an M7U, you must pretty much have the latest version main otherwise known as firmware as your on HBOOT 1.57, it will also be the 401 firmware based on your cid, so my next question is, are you returning to stock for warranty purposes or you just want it working as im not so sure there is an RUU available for your device, however its my understanding, you can flash M7UL rom's, just the LTE parts will be skipped.
Click to expand...
Click to collapse
Nah not for warranty. I just want it working, because right now it's bricked and I dont know what to do. I appreciate your help.
ahmadghizzawi said:
Nah not for warranty. I just want it working, because right now it's bricked and I dont know what to do. I appreciate your help.
Click to expand...
Click to collapse
just follow this, save me typing it all again: http://forum.xda-developers.com/showpost.php?p=58542916&postcount=6
Any problems, just report back. :good:
Seanie280672 said:
just follow this, save me typing it all again: http://forum.xda-developers.com/showpost.php?p=58542916&postcount=6
Any problems, just report back. :good:
Click to expand...
Click to collapse
Thanks man, I'll give a try. Will this method enable me to download OTA updates from HTC later on?
ahmadghizzawi said:
Thanks man, I'll give a try. Will this method enable me to download OTA updates from HTC later on?
Click to expand...
Click to collapse
probably not as its initially built for the M7_UL, you'll be stuck with custom rom's now unless you can find an RUU and get s-off to enable back flashing, you have to be full stock, nothing custom or modified to get HTC updates, to be honest, most Dev's on here release the rom's before HTC do, take Lollipop as an example, ive been using custom rom's since day 1 of getting my device, most of them blow the stock rom out of the water.
---------- Post added at 09:12 AM ---------- Previous post was at 09:07 AM ----------
ahmadghizzawi said:
Thanks man, I'll give a try. Will this method enable me to download OTA updates from HTC later on?
I tried flashing the custom rom here's what I got:
sending 'recovery' (9184 KB)...
OKAY [ 1.172s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.907s
Click to expand...
Click to collapse
is your bootloader unlocked ?
Seanie280672 said:
probably not as its initially built for the M7_UL, you'll be stuck with custom rom's now unless you can find an RUU and get s-off to enable back flashing, you have to be full stock, nothing custom or modified to get HTC updates, to be honest, most Dev's on here release the rom's before HTC do, take Lollipop as an example, ive been using custom rom's since day 1 of getting my device, most of them blow the stock rom out of the water.
---------- Post added at 09:12 AM ---------- Previous post was at 09:07 AM ----------
is your bootloader unlocked ?
Click to expand...
Click to collapse
It wasn't xD
Forgot to unlock it. I'm downloading the stock rom right now. I'll let you know if anything happens.
Seanie280672 said:
probably not as its initially built for the M7_UL, you'll be stuck with custom rom's now unless you can find an RUU and get s-off to enable back flashing, you have to be full stock, nothing custom or modified to get HTC updates, to be honest, most Dev's on here release the rom's before HTC do, take Lollipop as an example, ive been using custom rom's since day 1 of getting my device, most of them blow the stock rom out of the water.
---------- Post added at 09:12 AM ---------- Previous post was at 09:07 AM ----------
is your bootloader unlocked ?
Click to expand...
Click to collapse
I've installed the rom., picked full wipe, and waited 20 minutes for it to boot for the first time. However, it is restarting each time I try to unlock the screen for some reason. Please help.
ahmadghizzawi said:
I've installed the rom., picked full wipe, and waited 20 minutes for it to boot for the first time. However, it is restarting each time I try to unlock the screen for some reason. Please help.
Click to expand...
Click to collapse
strange that it didn't work, as you'll see here, M7_UL roms are fully compatible with the M7 U http://forum.xda-developers.com/showthread.php?t=2223236
Maybe the Rom just doesn't like your device, it happens, i'll see if I can find another for you.
Give this one a try https://www.androidfilehost.com/?fid=95916177934516346
Seanie280672 said:
strange that it didn't work, as you'll see here, M7_UL roms are fully compatible with the M7 U http://forum.xda-developers.com/showthread.php?t=2223236
Maybe the Rom just doesn't like your device, it happens, i'll see if I can find another for you.
Give this one a try https://www.androidfilehost.com/?fid=95916177934516346
Click to expand...
Click to collapse
Okay man, I'll give it a try. Thanks.
Seanie280672 said:
strange that it didn't work, as you'll see here, M7_UL roms are fully compatible with the M7 U http://forum.xda-developers.com/showthread.php?t=2223236
Maybe the Rom just doesn't like your device, it happens, i'll see if I can find another for you.
Give this one a try https://www.androidfilehost.com/?fid=95916177934516346
Click to expand...
Click to collapse
Same thing happened with this rom. What the hell is wrong
Baseband is showing N/A does it have anything to do with it?
ahmadghizzawi said:
Same thing happened with this rom. What the hell is wrong
Baseband is showing N/A does it have anything to do with it?
Click to expand...
Click to collapse
Don't know how I missed that one , yes I very much expect that's whats wrong, however, how did that happen ?
should be able to fix it by flashing the firmware for your device, however that leads to another problem, no baseband, no version main = which firmware.
All I can suggest at this point is try all of the 6.09.401.x firmware from the link below, start with the earliest one (6.09.401.5) if it fails try the next one up, when one of those install, stop there, the 6 series firmware's came with HBOOT 1,57, if they are older than your current firmware they will fail, if its the same as your current firmware it will install, don't forget each firmware must be flashed twice, first time will say please flush again immediately (flush is HTC Typo, they meant flash), also your bootloader must be locked or re-locked to flash firmware whilst s-on.
on another note, you will need to open each firmware that you download and edit the anroid info txt file, change the model id number in that file to the same number as your phone, then save and flash.
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Before proceeding with this just let me get it confirmed by some of the guys on here, yep im calling you @clsA @Danny201281 @nkk71 :good::good::good:
Seanie280672 said:
Don't know how I missed that one , yes I very much expect that's whats wrong, however, how did that happen ?
should be able to fix it by flashing the firmware for your device, however that leads to another problem, no baseband, no version main = which firmware.
All I can suggest at this point is try all of the 6.09.401.x firmware from the link below, start with the earliest one (6.09.401.5) if it fails try the next one up, when one of those install, stop there, the 6 series firmware's came with HBOOT 1,57, if they are older than your current firmware they will fail, if its the same as your current firmware it will install, don't forget each firmware must be flashed twice, first time will say please flush again immediately (flush is HTC Typo, they meant flash), also your bootloader must be locked or re-locked to flash firmware whilst s-on.
on another note, you will need to open each firmware that you download and edit the anroid info txt file, change the model id number in that file to the same number as your phone, then save and flash.
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Before proceeding with this just let me get it confirmed by some of the guys on here, yep im calling you @clsA @Danny201281 @nkk71 :good::good::good:
Click to expand...
Click to collapse
He is s-on so won't be able to flash a modified firmware so changing the model I'd in android info.txt is not an option.
As he's on hboot 1.57 he must be on a 5.xx or a 6.xx firmware so flashing strait to the latest won't be an issue. I posted a link to the firmware 6.09.401.111 for another user just a day or 2 ago. That is what he needs just a sec I'll be back with a link
---------- Post added at 09:23 PM ---------- Previous post was at 09:20 PM ----------
@ahmadghizzawi @Seanie280672
Everything you need is here http://forum.xda-developers.com/htc-one/development/backup-100-stock-6-09-401-111-twrp-t2992871 :good:
Danny201281 said:
He is s-on so won't be able to flash a modified firmware so changing the model I'd in android info.txt is not an option.
As he's on hboot 1.57 he must be on a 5.xx or a 6.xx firmware so flashing strait to the latest won't be an issue. I posted a link to the firmware 6.09.401.111 for another user just a day or 2 ago. That is what he needs just a sec I'll be back with a link
---------- Post added at 09:23 PM ---------- Previous post was at 09:20 PM ----------
@ahmadghizzawi @Seanie280672
Everything you need I'd here http://forum.xda-developers.com/htc-one/development/backup-100-stock-6-09-401-111-twrp-t2992871 :good:
Click to expand...
Click to collapse
Your a star :good:
Seanie280672 said:
Your a star :good:
Click to expand...
Click to collapse
:good: no problem, your welcome
@Seanie280672 @Danny201281 Thank you so much guys. I really appreciate your help. I'll give it a try and tell you what happens. Thank you again
Danny201281 said:
He is s-on so won't be able to flash a modified firmware so changing the model I'd in android info.txt is not an option.
As he's on hboot 1.57 he must be on a 5.xx or a 6.xx firmware so flashing strait to the latest won't be an issue. I posted a link to the firmware 6.09.401.111 for another user just a day or 2 ago. That is what he needs just a sec I'll be back with a link
---------- Post added at 09:23 PM ---------- Previous post was at 09:20 PM ----------
@ahmadghizzawi @Seanie280672
Everything you need is here http://forum.xda-developers.com/htc-one/development/backup-100-stock-6-09-401-111-twrp-t2992871 :good:
Click to expand...
Click to collapse
@Seanie280672 @Danny201281 When trying to flash the radio, this is what I am getting
sending 'radio' (76800 KB)...
OKAY [ 4.823s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.003s
ahmadghizzawi said:
@Seanie280672 @Danny201281 When trying to flash the radio, this is what I am getting
sending 'radio' (76800 KB)...
OKAY [ 4.823s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.003s
Click to expand...
Click to collapse
Try flashing the firmware, it will contain the radio, that's your best bet, again make sure the bootloader is locked or relocked then issue these commands:
fastboot oem rebootRUU (screen will go black with silver HTC logo)
fastboot flash zip "name of firmware".zip
fastboot flash zip "name of firmware".zip - yup twice
at this point make sure it says successful at the end, if so:
fastboot reboot-bootloader