Related
Hello Everyone,
I know this probably isn't the best place to post this question. I'm limited to not posting in the dev section.
I'm going to post my question and hope someone can help anyway.
I have an HTC One (M7) that seemed to have reception problems. I always thought I just needed to flash a new radio. So I went ahead and S-OFF'd my phone as well as Super CID. I then flashed a new radio & my reception problem seemed to go away. (or so i thought).
I then went ahead and turned my AT&T One into a Google Edition.
I have noticed that my reception problems never really went away. (When I am at home I have full bars. The conversation starts out fine, but about 10 seconds in, the person at the other end can no longer hear me.)
I now suspect this is a problem with the antenna & I have to get my phone back to stock so that I can hopefully switch out for a new one.
I'm just wondering which step I should do first. S-On again (I used REVONE to S-OFF) , CID back to AT&T, or switch back from the GE rom?
Any help would be appreciated.
Thank you,
Dan
demayod said:
Hello Everyone,
I know this probably isn't the best place to post this question. I'm limited to not posting in the dev section.
I'm going to post my question and hope someone can help anyway.
I have an HTC One (M7) that seemed to have reception problems. I always thought I just needed to flash a new radio. So I went ahead and S-OFF'd my phone as well as Super CID. I then flashed a new radio & my reception problem seemed to go away. (or so i thought).
I then went ahead and turned my AT&T One into a Google Edition.
I have noticed that my reception problems never really went away. (When I am at home I have full bars. The conversation starts out fine, but about 10 seconds in, the person at the other end can no longer hear me.)
I now suspect this is a problem with the antenna & I have to get my phone back to stock so that I can hopefully switch out for a new one.
I'm just wondering which step I should do first. S-On again (I used REVONE to S-OFF) , CID back to AT&T, or switch back from the GE rom?
Any help would be appreciated.
Thank you,
Dan
Click to expand...
Click to collapse
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Thanks so much for the response! I appreciate the help. Very informative. I'll read through & hopefully I report back with good news tomorrow morning. :cyclops:
Yay! All done!
Thanks so much for the guide! and the help!
-Dan
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I guess I spoke too soon. After completion, I realized that TWRP was still installed, so I flashed the stock recovery. At this point everything seemed fine, but I noticed that the supersu icon was still there. I also noticed that wifi will no longer turn on. Clearly I've done something wrong.
The first time I had used a nandroid backup to restore to stock, then lock, s-on, remove tampered. That is when I realized TWRP was still installed and SuperSu was still there.
This is when I downloaded an RUU that matched my phone, but it errors saying something like "wrong boot version" (I'm not near my home pc to look)
I tried the process again & somehow SuperSu lost binaries. So I unlocked my bootloader again through HTCDev.com This gave me working SuperSu again. And this is where I am stuck.
I wonder if the GE rom changed something so that this process wont work?
demayod said:
I guess I spoke too soon. After completion, I realized that TWRP was still installed, so I flashed the stock recovery. At this point everything seemed fine, but I noticed that the supersu icon was still there. I also noticed that wifi will no longer turn on. Clearly I've done something wrong.
The first time I had used a nandroid backup to restore to stock, then lock, s-on, remove tampered. That is when I realized TWRP was still installed and SuperSu was still there.
This is when I downloaded an RUU that matched my phone, but it errors saying something like "wrong boot version" (I'm not near my home pc to look)
I tried the process again & somehow SuperSu lost binaries. So I unlocked my bootloader again through HTCDev.com This gave me working SuperSu again. And this is where I am stuck.
I wonder if the GE rom changed something so that this process wont work?
Click to expand...
Click to collapse
when you run the RUU did you use the exe or Rom.zip /?
I use the rom.zip and flash in fastboot...
clsA said:
when you run the RUU did you use the exe or Rom.zip /?
I use the rom.zip and flash in fastboot...
Click to expand...
Click to collapse
I used the ruu. I didn't realize you can access a Rom.zip. how can I try that? Thanks!
demayod said:
I used the ruu. I didn't realize you can access a Rom.zip. how can I try that? Thanks!
Click to expand...
Click to collapse
This is the instructions posted by Scotty85
I'm just re-posting it for you
http://androidforums.com/t-one-all-things-root/723061-t-ruu-1-26-502-12-a.html#post5864243
Click to expand...
Click to collapse
here is how you extract rom.zip:
Quote:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
here are some directions to flash "rom.zip"
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse
clsA said:
This is the instructions posted by Scotty85
I'm just re-posting it for you
Click to expand...
Click to collapse
Thank you for the help, but still no good. I end up with FAILED (remote: 43 main version check fail) after I try to flash the zip.
demayod said:
Thank you for the help, but still no good. I end up with FAILED (remote: 43 main version check fail) after I try to flash the zip.
Click to expand...
Click to collapse
change your CID back to 11111111 and try again
Did you change you MID ?
What is the name of the RUU your using ?
My mid is PN0712000. I think that was always my mid. Don't recall changing it.
My cid is currently CW__001
I've tried: RUU_M7_UL_JB_50_Cingular_1.26.502.12.exe
also tried: RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2.exe
I'm currently S-On (could that be an issue?)
I'm unlocked.
clsA said:
change your CID back to 11111111 and try again
Did you change you MID ?
What is the name of the RUU your using ?
Click to expand...
Click to collapse
It worked once I set CID to 11111111 !!
So now I just have to change CID back, reverse S-Off again and change the unlocked and tampered flags?
Yep that should do it
Sent from my HTC One using Tapatalk 4
It did! I'm completely back to stock. I decided to update to the latest RUU that AT&T has released. Just to avoid AT&T wanting me to update to see if it fixes the problem. I know for a fact that it wouldn't fix the problem anyway.
Oddly, my phone told me I was up to date while on the .12 RUU even though I knew the .15 RUU exists. I downloaded the RUU for .15 and it ran fine once I went back to stock after running the .12 rom.zip.
In summary, you saved me from a huge headache! Thanks so much for all the help & kindness.
demayod said:
It worked once I set CID to 11111111 !!
So now I just have to change CID back, reverse S-Off again and change the unlocked and tampered flags?
Click to expand...
Click to collapse
How did you change our CID if you were S-On?
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Hi guys this might be the wrong platform for this question ...but can anyone pls help me with the stock cidnum for sprint htc one M8..thanks
larrydadz said:
Hi guys this might be the wrong platform for this question ...but can anyone pls help me with the stock cidnum for sprint htc one M8..thanks
Click to expand...
Click to collapse
Comments: Sprint
modelid:
cid: SPCS_001
Here's the Rom.zip I pulled from the AT&T 4.18.502.7 RUU
Encrypted version is Removed until i find another source (file was damaged, sorry for any inconvenience )
This will work if your s-off and your modelid: PN0712000 and CID: CWS__001
or you can EDIT the Android-info.txt to match your MID and CID
Decrypted version is here >> http://www.androidfilehost.com/?fid=23329332407580500
Huge thanks to @nkk71 for decrypting the files
And another Big thanks to @AndroidFileHost for the source RUU
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip
Instructions for flashing
If your s-on be sure the bootloader is locked
fastboot oem lock
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
I find these files much easier to use than the RUU.exe and these can be flashed with a MAC or Linux ....Have Fun !!
:good: :good:
clsA said:
Here's the Rom.zip I pulled from the AT&T 4.18.502.7 RUU
This will work if your s-on and your modelid: PN0712000 and CID: CWS__001
Encrypted version is here >> http://www.androidfilehost.com/?fid=23329332407580207
This will work if you s-off and your modelid: PN0712000 and CID: CWS__001
or you can EDIT the Android-info.txt to match your MID and CID
Decrypted version is here >> http://www.androidfilehost.com/?fid=23329332407580500
Huge thanks to @nkk71 for decrypting the files
And another Big thanks to @AndroidFileHost for the source RUU
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip
Instructions for flashing
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
I find these files much easier to use than the RUU.exe and these can be flashed with a MAC or Linux ....Have Fun !!
Click to expand...
Click to collapse
thanks again, much appreciated! I will give it a few more minutes but I work at 6am!
a little help please
I just put my One back to stock. S-on, relocked, tamper gone, etc When I try to update using the above method i get
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (1519630 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.002s
any ideas? thank you!
gsxrfl1k6 said:
I just put my One back to stock. S-on, relocked, tamper gone, etc When I try to update using the above method i get
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (1519630 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.002s
any ideas? thank you!
Click to expand...
Click to collapse
I just tested it and had the same problem ...I'll update when I get the new file uploaded
clsA said:
I just tested it and had the same problem ...I'll update when I get the new file uploaded
Click to expand...
Click to collapse
I'm also having the same issue. Have you been able to figure out what is wrong?
TaDoey said:
I'm also having the same issue. Have you been able to figure out what is wrong?
Click to expand...
Click to collapse
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
HEllo, friend now i feel very dissapointed thus i was not able to update my phone is a htc one M7 7120 from AT$T running this useless firmware 1.26.502.12, im in Colombia myabe thats why the AT&T system update is not working and i tried to run that RUU 3.X.502... but it still giving me the ERROR 158, any idea how can i update this phone? Thank man hope u can answer me.
Sli2cooL said:
HEllo, friend now i feel very dissapointed thus i was not able to update my phone is a htc one M7 7120 from AT$T running this useless firmware 1.26.502.12, im in Colombia myabe thats why the AT&T system update is not working and i tried to run that RUU 3.X.502... but it still giving me the ERROR 158, any idea how can i update this phone? Thank man hope u can answer me.
Click to expand...
Click to collapse
Is your bootloader locked/relocked?
Are you S-OFF or S-ON?
What is the CID?
Is this the RUU 3.17.502.3 that you are trying to run?
You will not get any AT&T updates if you are not on the AT&T network!
If you are not S-OFF, I would recommend obtaining S-OFF then rebrand your phone to the International (.401) variant. Then you could get the OTA updates and not worry about the AT&T network.
majmoz said:
Is your bootloader locked/relocked?
Are you S-OFF or S-ON?
What is the CID?
Is this the RUU 3.17.502.3 that you are trying to run?
You will not get any AT&T updates if you are not on the AT&T network!
If you are not S-OFF, I would recommend obtaining S-OFF then rebrand your phone to the International (.401) variant. Then you could get the OTA updates and not worry about the AT&T network.
Click to expand...
Click to collapse
Hello mate, thanks for the reply, now that you mention it sounds pretty interesting to rebrand to phone to int. variant, but... How do i ado that? Right now im running 4.18.502.7 Stock for AT&T, i would not liek to bother you so much but is there any way to do that i wouls appreciate the help.
Yes im S-OFF and yes im unlocked, TWRP tho, CWS__001, hboot 1.44.000000 and rooted.
Once again thanks for the help.
Sli2cooL said:
Hello mate, thanks for the reply, now that you mention it sounds pretty interesting to rebrand to phone to int. variant, but... How do i ado that? Right now im running 4.18.502.7 Stock for AT&T, i would not liek to bother you so much but is there any way to do that i wouls appreciate the help.
Yes im S-OFF and yes im unlocked.
Once againm thans for the help.
Click to expand...
Click to collapse
Here is a outline of what you will need to do.
Here are the steps to re-branding your phone to Int'l:
Unlock bootloader if not unlocked already!
Install Custom recovery
Download TWRP 2.6.3.3 from here: http://techerrata.com/browse/twrp2/m7
Achieve S-OFF, if not already!
With your hboot 1.5x use rumrunner or firewater to get S-Off: http://firewater-soff.com/ or http://rumrunner.us/
Try all options!
Change CID to the new code:
Code:
[B][I]adb reboot bootloader
fastboot oem writecid HTC__001[/I][/B] <- (CID is exactly 8 characters)
[B][I]fastboot reboot-bootloader[/I][/B]
Change MID to the new code: PN0710000 using: [TOOL] MID change without ENG HBOOT | Aroma GUI
Remove "Tampered" with the Guru Bootloader Reset Tool
Download and flash 4.19.401.9 firmware; place firmware in your fastboot/adb folder and rename to firmware.zip. Ensure you have moved all of your personal items off of your phone this firmware will wipe your phone. Open a command window in your fastboot/adb folder and type:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Execute http://www.htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe/ which now matches your CID & MID
There is no need to lock/relock bootloader with S-OFF, and do not even THINK about going back to S-ON!!!
Now you can receive the OTAs or flash them manually.
OTA_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.11-4.19.401.9_R_release_355954met8o678uio0omu3.zip
OTA_M7_UL_K44_SENSE60_MR_HTC_Europe_5.11.401.10-4.19.401.11_release_372404wj19h95c0x6oa19n.zip
OTA_M7_UL_K443_SENSE60_MR_HTC_Europe_6.09.401.5-5.11.401.10_release_386803.zip
OTA_M7_UL_K443_SENSE60_MR_HTC_Europe_6.09.401.10-6.09.401.5_release_397712mm1f6dd6rksg0p3s.zip
Click to expand...
Click to collapse
majmoz said:
Here is a outline of what you will need to do.
Click to expand...
Click to collapse
Thansk for the reply mate is it neccesary to change the MID of the phone?
Also the hboot is it good at 1.44?
Sli2cooL said:
Thansk for the reply mate is it neccesary to change the MID of the phone?
Also the hboot is it good at 1.44?
Click to expand...
Click to collapse
Only if it is different. I don't know your MID but if it is different from the Int'l MID then you will not be able to flash the firmware, RUU or OTAs.
Yes, it will change when you flash the firmware & RUU. I would keep a copy of it for future use.
majmoz said:
Only if it is different. I don't know your MID but if it is different from the Int'l MID then you will not be able to flash the firmware, RUU or OTAs.
Click to expand...
Click to collapse
I think it is 712000 from AT&T, quite different right?
Sli2cooL said:
I think it is 712000 from AT&T, quite different right?
Click to expand...
Click to collapse
Yes, just think you should only have to change it once!
majmoz said:
Yes, just think you should only have to change it once!
Click to expand...
Click to collapse
Ho danm , then i cannot get back to 7120? Anyways Int goes better i guess, no malfunction on LTE/4G?
Sli2cooL said:
Ho danm , then i cannot get back to 7120? Anyways Int goes better i guess, no malfunction on LTE/4G?
Click to expand...
Click to collapse
You can go back; just do the same steps for AT&T. If you have LTE/4G now you will still have LTE/4G after this process does not change the bands that are hard coded into the phone. The radio in the software merely enhances the bands that are in the phone but can not replace them.
majmoz said:
You can go back; just do the same steps for AT&T. If you have LTE/4G now you will still have LTE/4G after this process does not change the bands that are hard coded into the phone. The radio in the software merely enhances the bands that are in the phone but can not replace them.
Click to expand...
Click to collapse
Okey buddy thansk again for the help ill be trying it tomorrow and ill be updating the process. :good:
I missed this one, well it went well, now i can recieve the OTAs in auto mode, THX for the help @majmoz.
Sorry but when I type "fastboot flash zip Rom.zip" fastboot stops, Someone, can help me? :crying:
I'm S-ON
hboot 1.57
CID: CWS__001
Hey, just to let people know, be wary of flashing the firmware from the M7 Sense 6 update from T-Mobile, I pulled it from the OTA and it flashed successfully in RUU mode, but now im stuck in the dreaded QHSUSB_DLOAD mode, trying to figure a way to get a replacement, but just letting people know to be careful...
Whoareyou said:
Hey, just to let people know, be wary of flashing the firmware from the M7 Sense 6 update from T-Mobile, I pulled it from the OTA and it flashed successfully in RUU mode, but now im stuck in the dreaded QHSUSB_DLOAD mode, trying to figure a way to get a replacement, but just letting people know to be careful...
Click to expand...
Click to collapse
Please provide more details;
Do you have a T-Mobile device? --Did you change your CID?
What ROM?
What recovery?
Bootloader unlocked? S-Off?
What hboot did you have before flashing (stock? custom?)
How exactly did you pull the firmware?
These details would be very helpful.
Sent from my HTC One_M8 using Tapatalk
krook6023 said:
Please provide more details;
Do you have a T-Mobile device? --Did you change your CID?
What ROM?
What recovery?
Bootloader unlocked? S-Off?
What hboot did you have before flashing (stock? custom?)
How exactly did you pull the firmware?
These details would be very helpful.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111), had Firewater HBOOT previously.
ViperONE 6.2.1
TWRP
i used WinRAR and pulled the firmware.zip from the OTA file, then booted into rebootRUU mode and "fastboot flash zip firmware.zip" the it told me to flush again as per usual, i did it again, then when i went to reboot, i was in QHSUSB_DLOAD
Whoareyou said:
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111)...
Click to expand...
Click to collapse
Maybe an issue with SuperCID...
You should read this thread: http://forum.xda-developers.com/showthread.php?t=2753631
People had a similar problem and a few were able to get back into hboot by plugging the phone to computer and persistently pressing power and volume down and/or volume up in different combinations. If you can get back to the boot loader flash a know working firmware. It's worth a shot... Here are some relevant comments from that thread...
streather said:
Same problem here, bricked the phone.
I have managed to get it to turn back on and got to the silver HTC logo but I sent the wrong command over fastboot and it turned off again
Click to expand...
Click to collapse
BanBoo said:
How do you managed it?!
Click to expand...
Click to collapse
simaka said:
OK, I got back to the bootloader.
Guys, be persistent in pressing power+vol buttons while usb connected to PC, it took me about 10-15 minutes but now I am back to fastboot!
Any ideas what would be the best course of action now?
Click to expand...
Click to collapse
simaka said:
Not sure if it was power + vol down or + vol up... But I definitely waited each time about 20 secs before switching to the other possibility. And the phone was usb connected to my pc.
Click to expand...
Click to collapse
simaka said:
Yes, each time. I also tried pressing both + and - at the same time, but that was not the winning combination.
Click to expand...
Click to collapse
yoshi8 said:
how did you recognized that you are in fastboot again? did your screen turn on again?
Click to expand...
Click to collapse
simaka said:
Yes, it has booted and screen is lit and I am in fastboot. Now wondering what is the best next step... Which firmware should I upgrade with...
Click to expand...
Click to collapse
simaka said:
Here is what I did the last time:
1. winclock showing seconds in front of me.
2. hold power + vol down.
3. Count 3 seconds
4. release.
5. Go to 1 and add 1 second on step 3 . In about 20 minutes (when I surpassed 20 secs I started from 3 seconds on step 3 again) I woke it up.
good luck!
Click to expand...
Click to collapse
Sent from my HTC One_M8 using Tapatalk
All CID's must have eight characters. SuperCID would have to be 11111111 not 1111111
Sent from my HTC One using XDA Free mobile app
NxNW said:
All CID's must have eight characters. SuperCID would have to be 11111111 not 1111111
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
you know what i mean, it was all 1s also holding the buttons didnt work
Whoareyou said:
you know what i mean, it was all 1s also holding the buttons didnt work
Click to expand...
Click to collapse
Just checking- someone said it could be an issue with the CID, and that would definitely be "an issue" ; )
Whoareyou said:
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111), had Firewater HBOOT previously.
ViperONE 6.2.1
TWRP
i used WinRAR and pulled the firmware.zip from the OTA file, then booted into rebootRUU mode and "fastboot flash zip firmware.zip" the it told me to flush again as per usual, i did it again, then when i went to reboot, i was in QHSUSB_DLOAD
Click to expand...
Click to collapse
That right there is what bricked your phone. I honestly don't know why people care so much about the red message on boot to flash a modded Hboot. Most devs on the One international forum are starting to pull of their modded Hboots as people usually don't know flashing a modded one can brick phones on future updates or so.
I haven't manually flashed just firmware. I am s-off with supercid. To get most current I loaded the last tmous ruu then let it go through all updates until it was at the latest sense 6, then reloaded twrp and my latest nandroid.
Sent from my HTC One using XDA Free mobile app
Jorakal said:
I haven't manually flashed just firmware. I am s-off with supercid. To get most current I loaded the last tmous ruu then let it go through all updates until it was at the latest sense 6, then reloaded twrp and my latest nandroid.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
That is a good way however we should point if one has a moded hboot and applies the official RUU will brick the phone. Just pointing that out.
Sent from my HTC One using Tapatalk
Firmware Update
I have been looking to update to the latest firmware on my tmobile htc one, but i also have a custom hboot that i got from here " http://forum.xda-developers.com/showthread.php?t=2497712 " so im holding off on flashing the newest firmware, because it will probably brick my phone. But what i am wondering is does anyone know where i can just fine the 1.44 tmobile hboot that i was currently on?? so that i dont have to flash the stock RUU and start all back over from scratch ?? I could just flash back to the 1.44 stock hboot and then upgrade to the newest firmware without bricking my phone ??
Tewessarino said:
I have been looking to update to the latest firmware on my tmobile htc one, but i also have a custom hboot that i got from here " http://forum.xda-developers.com/showthread.php?t=2497712 " so im holding off on flashing the newest firmware, because it will probably brick my phone. But what i am wondering is does anyone know where i can just fine the 1.44 tmobile hboot that i was currently on?? so that i dont have to flash the stock RUU and start all back over from scratch ?? I could just flash back to the 1.44 stock hboot and then upgrade to the newest firmware without bricking my phone ??
Click to expand...
Click to collapse
Take a look @Behold_this thread TMOUS Firmware Packages - Release Builds for the correct firmware to return you to stock hboot.
factory reset
i tried almost everything i cant do ruu.exe cause i get and error 155 which is unknown error and yes i was relocked before running the ruu. i tried doing s-off with no luck im on t-mobile us network htc one m7
i have viper rom 6.2.0 running right now on it
bootloader menu i have
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-*** this is what im not sure why theres nothing when there used to be***
eMMC-boot 2048m
its tampered and unlocked at the moment plz help thanx i need to factory reset
matador1510 said:
i tried almost everything i cant do ruu.exe cause i get and error 155 which is unknown error and yes i was relocked before running the ruu. i tried doing s-off with no luck im on t-mobile us network htc one m7
i have viper rom 6.2.0 running right now on it
bootloader menu i have
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-*** this is what im not sure why theres nothing when there used to be***
eMMC-boot 2048m
its tampered and unlocked at the moment plz help thanx i need to factory reset
Click to expand...
Click to collapse
Which RUU.exe are you attempting to run? If it is this one: T-Mobile HTC One 4.3 3.24.531.3 RUU then your hboot is too high. I would suggest trying this one: T-Mobile USA | 4.4.2 | Sense 6 | 5.14.531.11. Also, since you are S-ON the bootloader needs to be locked/relocked for you to run a RUU. You can lock it in bootloader/FASTBOOT USB with this command: fastboot oem lock
If Viper is running on your One without an issue then you have an operating ROM and the missing OS is due to the custom recovery you used. If you are using TWRP, I would recommend TWRP 2.6.3.3 or TWRP 2.6.3.4 or TWRP 2.7.1.2! The last one has some changes built in that help eliminate the issue of a blank OS.
factory reset
majmoz said:
Which RUU.exe are you attempting to run? If it is this one: T-Mobile HTC One 4.3 3.24.531.3 RUU then your hboot is too high. I would suggest trying this one: T-Mobile USA | 4.4.2 | Sense 6 | 5.14.531.11. Also, since you are S-ON the bootloader needs to be locked/relocked for you to run a RUU. You can lock it in bootloader/FASTBOOT USB with this command: fastboot oem lock
If Viper is running on your One without an issue then you have an operating ROM and the missing OS is due to the custom recovery you used. If you are using TWRP, I would recommend TWRP 2.6.3.3 or TWRP 2.6.3.4 or TWRP 2.7.1.2! The last one has some changes built in that help eliminate the issue of a blank OS.
Click to expand...
Click to collapse
thanx i will try this will let you what happens
htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
lordtopher said:
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
Click to expand...
Click to collapse
Check out this post for the TWRP nandroid, firmware and stock recovery for your phone. You will need to unlock your bootloader to flash the recovery or TWRP. If you decide to flash the firmware your bootloader should remain locked. In fact, I would flash the firmware first, then install TWRP to install the nandroid.
majmoz said:
Check out this post for the TWRP nandroid, firmware and stock recovery for your phone. You will need to unlock your bootloader to flash the recovery or TWRP. If you decide to flash the firmware your bootloader should remain locked. In fact, I would flash the firmware first, then install TWRP to install the nandroid.
Click to expand...
Click to collapse
the problem is the phone... when i got the fastboot menu...i can scroll down and up but when i press on power button to enter the bootloader the phone freezer and i must turn it off. have you heard this issue??? must i buy another phone??:crying:
lordtopher said:
the problem is the phone... when i got the fastboot menu...i can scroll down and up but when i press on power button to enter the bootloader the phone freezer and i must turn it off. have you heard this issue??? must i buy another phone??:crying:
Click to expand...
Click to collapse
Can you connect the phone to a computer and is it recognized?
If yes, then I would recommend flashing the firmware. It contains hboot and you may have an issue with hboot.
Here is the procedure for flashing the firmware. If your phone is already in bootloader/FASTBOOT USB you can skip the first line.
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
I have a HTC desire 601 bought this Summer from Virgin Mobile USA, a CDMA based carrier using Sprint network. My son played with it yesterday and now it is bricked. A "HTC" log is shown up and frozen in the display, not able to shutdown the phone by pressing anything.
I asked my son what he did, but he didnt say anything as he is afraid of punishment
what I can do is try to remove the battery, then hold the volume down key and power key, then it brings up this screen:
***Tampered***
***Unlocked***
ZARA_C PVT SHIP S-ON RL
HBOOT-2.20.0000
RADIO-1.14.50.1003
OpenDSP-v16.2.0268.noBeats.0902
OS-1.10.652.9
eMMC-boot 1024MB
Oct 7 2013 18:39.56.0
HBOOT
<vol_up>to previewitem
<vol_down> to next item
<power> to select item
Fastboot
Recovery
Factory reset
CLEAR storage
SIMLOCK
Image CRC
Show barcode
after I press "recovery", it enter this page::
Team Win Recovery project v2.7.1.1(kk)
Install Wipe
Backup Restore
Mount Settings
Advanced Reboot
what I want to to go back to the stock Virgin Mobile ROM. what should I do? thanks.
I'm assuming you don't have a backup... Try a factory reset from twrp, if that didn't help seek out a zara_cl backup
attrunner said:
I have a HTC desire 601 bought this Summer from Virgin Mobile USA, a CDMA based carrier using Sprint network. My son played with it yesterday and now it is bricked. A "HTC" log is shown up and frozen in the display, not able to shutdown the phone by pressing anything.
I asked my son what he did, but he didnt say anything as he is afraid of punishment
what I can do is try to remove the battery, then hold the volume down key and power key, then it brings up this screen:
***Tampered***
***Unlocked***
ZARA_C PVT SHIP S-ON RL
HBOOT-2.20.0000
RADIO-1.14.50.1003
OpenDSP-v16.2.0268.noBeats.0902
OS-1.10.652.9
eMMC-boot 1024MB
Oct 7 2013 18:39.56.0
HBOOT
<vol_up>to previewitem
<vol_down> to next item
<power> to select item
Fastboot
Recovery
Factory reset
CLEAR storage
SIMLOCK
Image CRC
Show barcode
after I press "recovery", it enter this page::
Team Win Recovery project v2.7.1.1(kk)
Install Wipe
Backup Restore
Mount Settings
Advanced Reboot
what I want to to go back to the stock Virgin Mobile ROM. what should I do? thanks.
Click to expand...
Click to collapse
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive.
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
-Duir- said:
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive[/URL].
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
Click to expand...
Click to collapse
sir, can you show me where did you see it's Kitkat recovery on my device, and where did you see it's still Jelly bean? I am still leaning.
attrunner said:
sir, can you show me where did you see it's Kitkat recovery on my device, and where did you see it's still Jelly bean? I am still leaning.
Click to expand...
Click to collapse
Team Win Recovery project v2.7.1.1(kk)
^^where it says "kk" at the end means that is a kitkat recovery.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Hedied4me said:
Team Win Recovery project v2.7.1.1(kk)
^^where it says "kk" at the end means that is a kitkat recovery.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
where it shows it's jelly bean? thank you very much.
attrunner said:
where it shows it's jelly bean? thank you very much.
Click to expand...
Click to collapse
The OS version in your post is Jelly Bean.
-Duir- said:
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive.
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
Click to expand...
Click to collapse
sir, This is what I did:
1 I tried to use the RUU (file name RUU_ZARA_CL_JB422_SENSE50_Sprint_WWE_VM_1.10.652.9_Radio_1.14.50.1003_NV_SPCS_5.17_003_PRL55009_release_337148_signed_2.exe), but after the RUU erase data, and trying to send data, it has error message:
ERROR[155]: unknown error.
The ROM Update Utility can not update your Android phone.
Please get the correct ROM update utility and try again.
2 I tried different TWRP version as recovery, then use your RUU, all failed as step 1.
openrecovery-twrp-2.6.3.0-zaracl
openrecovery-twrp-2.7.0.0-zaracl
openrecovery-twrp-2.7.1.0-zaracl
3. I tried a stock ROM in Google dirve:
/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
I chose file JB_stock_system_dump.zip, tried to copy to external SD card and install from recovery, but failed.
So please help what should I try next. thank you very much
attrunner said:
sir, This is what I did:
1 I tried to use the RUU (file name RUU_ZARA_CL_JB422_SENSE50_Sprint_WWE_VM_1.10.652.9_Radio_1.14.50.1003_NV_SPCS_5.17_003_PRL55009_release_337148_signed_2.exe), but after the RUU erase data, and trying to send data, it has error message:
ERROR[155]: unknown error.
The ROM Update Utility can not update your Android phone.
Please get the correct ROM update utility and try again.
2 I tried different TWRP version as recovery, then use your RUU, all failed as step 1.
openrecovery-twrp-2.6.3.0-zaracl
openrecovery-twrp-2.7.0.0-zaracl
openrecovery-twrp-2.7.1.0-zaracl
3. I tried a stock ROM in Google dirve:
/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
I chose file JB_stock_system_dump.zip, tried to copy to external SD card and install from recovery, but failed.
So please help what should I try next. thank you very much
Click to expand...
Click to collapse
Lock the bootloader and then run it.
Also:
Custom recovery does not affect the RUU.
The system dump zip is literally that, a dump of the system partition. As such, it's not recovery flashable.
-Duir- said:
Lock the bootloader and then run it.
Also:
Custom recovery does not affect the RUU.
The system dump zip is literally that, a dump of the system partition. As such, it's not recovery flashable.
Click to expand...
Click to collapse
Don't lock the boot loader, that's not why the ruu is failing.
You need to change the mid first
mrplowdan said:
Don't lock the boot loader, that's not why the ruu is failing.
You need to change the mid first
Click to expand...
Click to collapse
That's exactly why it's failing. You need to be relocked to run the RUU.
-Duir- said:
That's exactly why it's failing. You need to be relocked to run the RUU.
Click to expand...
Click to collapse
Perhaps its different for the cl varient but for my ul, I'm 100% positive you don't need to be relocked. However, mid and cid must match the ruu.
*edit*
Also your hboot must be older or the same version as the ruu's hboot
mrplowdan said:
Perhaps its different for the cl varient but for my ul, I'm 100% positive you don't need to be relocked. However, mid and cid must match the ruu.
*edit*
Also your hboot must be older or the same version as the ruu's hboot
Click to expand...
Click to collapse
Well, they have the Virgin Mobile zara_cl variant which the RUU is made for, so the mid and cid shouldn't be an issue since they're S-ON and can't change it. Also, as stated their using 4.2.2. They still have the old firmware and partition layout which is why the version of twrp they installed won't work so hboot version is also not an issue. Also, it throws a different error if your device has a newer hboot than the RUU.
While it's not entirely outside the realm of possibility that something else could be causing the error, it's definitely not hboot version or mid/cid.
Were you S-OFF when you ran RUU on unlocked bootloader? I'm not sure of all the benefits of being S-OFF, but maybe one is being able to RUU with an unlocked bootloader. It makes perfect sense for an unlocked bootloader to throw an error since it can void your warranty and RUUs are generally ran by service techs.
But in all my experience the bootloader needs to be locked/relocked for the RUU to run.
-Duir- said:
... Were you S-OFF when you ran RUU on unlocked bootloader? I'm not sure of all the benefits of being S-OFF, but maybe one is being able to RUU with an unlocked bootloader. It makes perfect sense for an unlocked bootloader to throw an error since it can void your warranty and RUUs are generally ran by service techs.
But in all my experience the bootloader needs to be locked/relocked for the RUU to run.
Click to expand...
Click to collapse
I haven't tried running the ruu while s-on. I'm pretty sure the distinction is if your s-off you can flash ruu zips (which don't have the mid/cid requirements) after running fastboot oem rebootRUU as well as the standard exe RUUs, and if your s-on you can only run exe RUUs.
Hey, guys. I've finally made an account here after clumsily stepping into the world of custom ROMs. I recently got a Zara_CL on Virgin mobile and somehow wound up in the same position as the OP here. I never updated to KitKat due to the update failing with a custom recovery image. After unlocking the bootloader, I installed TWRP 2.7.1.1 and tried to flash InstertCoin yesterday without making a backup (couldn't mount certain partitions and now I know why ^_^). It took many hours to figure out what I did wrong and to make many plans of action to fix those mistakes.
I have re-locked my bootloader and the RUU has allowed me to get the stock Jellybean ROM back on my phone. I tried before while still unlocked and the RUU made no progress at all.
From what I've experienced, S-OFF and Unlocked are sort of interchangeable on a device in this stage of being cracked. One can flash recoveries with S-OFF and a locked loader, or with S-ON and an unlocked loader. I'm still learning after a few months and a successful root, s-off, and rom flash on an ancient EVO 3D. The high of that success drove me to buy this phone and try some magic on it, but my conjuration skills are quite unpolished.
To OP: Relock your bootloader with fastboot command "oem lock" and then run the RUU you found here. This should resurrect your handset flawlessly as it did in my situation. Don't punish your son, but teach him to be more careful. We both learned the hard way, but I guess I learned more quickly.
I had to always lock bootloader before running ruu. Would always get same error otherwise. This was for s-on. I can't remember my one experience running ruu while s-off.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Hedied4me said:
I had to always lock bootloader before running ruu. Would always get same error otherwise. This was for s-on. I can't remember my one experience running ruu while s-off.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
How to lock bootloader? I only know how to unlock.
Get into boot loader and type "oem lock" into adb/command prompt.
attrunner said:
How to lock bootloader? I only know how to unlock.
Click to expand...
Click to collapse
You're phone needs to be in fastboot mode.
You need adb on your computer and to run a command prompt from your adb folder. Plug your phone into the computer and from the command prompt type "fastboot oem lock" and press enter. You're bootloader will now be locked. If you get a message about too many flags or something and a security warning afterwards, don't worry, it worked.
Howdy folks...so my buddy picked up an M8 off of Craigslist that was apparently running some sort of vanilla android. It is unlocked and S off..he attempted to flash a Sense ROM and ended up in a boot loop. He's the kind of guy that shouldn't be doing such things...
This is where I come in to the rescue. After some reading this afternoon, I've come to the conclusion he must have a GPE converted phone. I personally have no experience with this device (G2 Verizon owner) but I'm pretty versed in fast boot and ADB.
The phone is currently in fast boot. This is all it has. If I attempt to boot it into recovery, it loops.
Can anyone help me get this thing running by pointing me in the right direction? Ideally, I'd like to have it fully AT&T stock.
My current plan was to push a recovery via fast boot and flash a GPE ROM off of SD. Will this work?
I just don't want to mess the phone up any further.
m8
Can you boot phone into bootloader? If so connect phone and type adb oem getvar all.
Should give you details of cid and rom required to get phone working again.
Googling ruu for cid will help so example is m8 ruu htc_001.
passion8059 said:
Can you boot phone into bootloader? If so connect phone and type adb oem getvar all.
Should give you details of cid and rom required to get phone working again.
Googling ruu for cid will help so example is m8 ruu htc_001.
Click to expand...
Click to collapse
Yes, bootloader is basically all I have. Thank you for the help!
I won't be able to get to work for a few hours, but I'll update with any progress.
OK...so turns out the phone indeed was converted to a GPE device, which caused his problem after attempting to flash a Sense ROM...I successfully flashed TWRP via fast boot and installed a GPE rom...now, just need to go about converting it back for him.
Thanks to member Passion for helping me out.
m8
mulhiny said:
OK...so turns out the phone indeed was converted to a GPE device, which caused his problem after attempting to flash a Sense ROM...I successfully flashed TWRP via fast boot and installed a GPE rom...now, just need to go about converting it back for him.
Thanks to member Passion for helping me out.
Click to expand...
Click to collapse
Change cid to super cid 11111111 (7 ones) by putting phone into fastboot , connect and typing fastboot oem writecid 1111111.
This allows phone to have most stock htc roms to be written to phone.
Find stock rom you require and flash which will revert to stock for you.
Hope this helps!
passion8059 said:
Change cid to super cid 11111111 (7 ones) by putting phone into fastboot , connect and typing fastboot oem writecid 1111111.
This allows phone to have most stock htc roms to be written to phone.
Find stock rom you require and flash which will revert to stock for you.
Click to expand...
Click to collapse
It appears the OP's phone had the full GPE conversion done to it, therefore changing the partitions, and that alone will prevent Sense ROMs for booting. Flashing a ROM in itself will not change the partitions back the Sense partition scheme.
Easiest way to revert is probably RUU. You're right in the OP needs to post getvar all data before all the steps can be laid our correctly. In short, OP needs the proper CID or SuperCID, and relock bootloader (if unlocked) or S-off to run RUU.
redpoint73 said:
It appears the OP's phone had the full GPE conversion done to it, therefore changing the partitions, and that alone will prevent Sense ROMs for booting. Flashing a ROM in itself will not change the partitions back the Sense partition scheme.
Easiest way to revert is probably RUU. You're right in the OP needs to post getvar all data before all the steps can be laid our correctly. In short, OP needs the proper CID or SuperCID, and relock bootloader (if unlocked) or S-off to run RUU.
Click to expand...
Click to collapse
Did gpe conversion with my m7 and had to flash with zip file of ruu in order to change.
I have tried looking myself to point him in the right direction for m8 zip's but have not had had any joy?
passion8059 said:
Did gpe conversion with my m7 and had to flash with zip file of ruu in order to change.
I have tried looking myself to point him in the right direction for m8 zip's but have not had had any joy?
Click to expand...
Click to collapse
Flashing a zip of the RUU isn't necessary. OP can either flash the official exe file: http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Or the bootable RUU here (no PC required): http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
redpoint73 said:
Flashing a zip of the RUU isn't necessary. OP can either flash the official exe file: http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Or the bootable RUU here (no PC required): http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
Click to expand...
Click to collapse
But doesn't bootloader need to be changed?
As you said partitions are different and ruu would not like it surely?
passion8059 said:
But doesn't bootloader need to be changed?
As you said partitions are different and ruu would not like it surely?
Click to expand...
Click to collapse
RUU will rewrite all partitions including hboot. I have the advice I did for a reason.
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
RUU will rewrite all partitions including hboot. I have the advice I did for a reason.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
So all I would have to do is run the bootable ruu to bring my gpe converted m8 back to stock sense? Just want to know for future ref
pclaunch said:
So all I would have to do is run the bootable ruu to bring my gpe converted m8 back to stock sense? Just want to know for future ref
Click to expand...
Click to collapse
Yes.
Keep in mind, if you are s-on, you need to have the proper CID or SuperCID. Plus, you can only run an RUU with equal or greater hboot number than the hboot presently installed on the phone.
S-off should bypass both these issuees (CID and hboot version check).