Good Day community, I have a question to see if you can help me or someone who has already done.
I have my M8 (CID CWS_001 was originally AT & T) and I have SuperCID, I'm s-off, I have unlocked the bootloader, I installed the firmware 2.22.401.5 and TWRM 2.7.1 rom with 7.1 HD Maximus, good now my question is: I want to make the official Developer Edition version of HTC (CID BS_US002 and firmware 2.22.1540.3) the idea is to stick with OTA updates and all could help me with what I want? thank you very much to all.
the idea is that it looks as if you had bought the developer edition version and not the at & t
greetings,
the easiest way would be to run the dev edition RUU, thats what i did, just be sure to change the cid to match.
chizler said:
the easiest way would be to run the dev edition RUU, thats what i did, just be sure to change the cid to match.
Click to expand...
Click to collapse
and where I downloaded the developer edition of RUU friend?
Enviado desde mi HTC One_M8 mediante Tapatalk
the htc dev website, http://www.htcdev.com/devcenter/downloads/P00. just select what you need.
chizler said:
the htc dev website, http://www.htcdev.com/devcenter/downloads/P00. just select what you need.
Click to expand...
Click to collapse
The only file for the Developer Edition that I could find is the MR1 file, but no RUU. I have an AT&T branded M8, fully converted to GPe. Is there a way to run the MR1 to convert my current setup to the Developer Edition?
https://www.dropbox.com/s/txz5sv2r3...31A.4145.02L_release_372510_signed_2.exe?dl=0
That should be the link to it in my dropbox. just give it a min to upload.
Thanks for posting the RUU! I changed my phone's CID to BS_US002 and ran the RUU, only to get the dreaded 159 error. I find myself missing Sense, but I really don't want to revert to AT&T's bloatware-infested version and deal with their constant update delays.
I wonder If the error has something to do with the HBOOT version on the 4.4.4 GPe firmware?
Pretty sure you have to convert back to sense before you run the RUU.
Believe you are [email protected]
jsaldarriaga said:
Good Day community, I have a question to see if you can help me or someone who has already done.
I have my M8 (CID CWS_001 was originally AT & T) and I have SuperCID, I'm s-off, I have unlocked the bootloader, I installed the firmware 2.22.401.5 and TWRM 2.7.1 rom with 7.1 HD Maximus, good now my question is: I want to make the official Developer Edition version of HTC (CID BS_US002 and firmware 2.22.1540.3) the idea is to stick with OTA updates and all could help me with what I want? thank you very much to all.
the idea is that it looks as if you had bought the developer edition version and not the at & t
greetings,
Click to expand...
Click to collapse
I converted my AT&T One M8 to US unlocked version (CID: BS_US001) using the directions in the thread below:
http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
This assumes you have S-OFF, and unlocked bootloader and i started with an AT&T stock rom with no root. I am not sure if that is a requirement. For this i did the AT&T RUU by installing an older stock recovery. (AT&T 4.4.3 RUU)
1. Change CID to BS_US001 - open command prompt on your computer and navigate to your fastboot folder; alternatively open the fastboot folder and hold down shift and rightclick, and select open command prompt here. turn USB debugging ON on your phone and connect it to your computer in fastboot mode (turn your phone off and while holding the VOL down button press the power button, the phone goes to bootloader mode, select the fastboot [first option] and press power button, connect the phone to computer and it should say fastboot-usb), verify connection by typing fastboot devices in cmd prompt, it should give your device code. after confirming you are connected via fastboot, type "fastboot oem writecid BS_US001" Reboot bootloader and confirm CID change by typing "fastboot getvar all" and your CID should read "BS_US001".
2. Restore developer nand - for this you will need a custom recovery like TWRP or CWM. If you already have TWRP, then please proceed. To install custom recovery, download TWRP from here. save the twrp recovery image file to your fastboot folder. put your phone in fastboot mode and connect to computer and open cmd prompt from your fastboot folder and type "fastboot flash recovery recoveryname.img", recoveryname should be exactly what the same as TWRP recovery filename. Verify TWRP installation by typing "fastboot reboot-bootloader" and selecting recovery. TWRP recovery should load. Download BS-US001 stock nand from here. At this point boot your phone normally and connect to computer. The navigate to the TWRP folder and backup folder, and paste the BS_US001 nand zip file here. Reboot to TWRP recovery and select restore and select the BS_US001 file you just copied.
3. Install Unlocked version (BS_US001) firmware which includes stock recovery - Download the unlocked version firmware from here. For installing firmware i used this thread. There are two methods however, i used the following method and is my favorite. For this it is recommended that the HT sync manager be uninstalled leaving just the HTC drivers. Place the firmware zip in the fastboot folder. Put your phone in fastboot mode and connect to computer. Open cmd prompt in your fastboot folder. Type "fastboot oem rebootRUU", phone will turnoff and a dark screen with only HTC will appear (this is the RUU mode), now type "fastboot flash zip firmware.zip" replace firmware with the actual filename of the firmware zip. You will see a green progress bar while the firmware is being flashed. I read somewhere that the flash will fail the first time so reflash the firmware a second time by typing "fastboot flash zip firmware.zip". It did fail for me the first time and installed the firmware a second time and it worked. type "fastboot reboot-bootloader" from here select option to reboot your phone normally. Once booted and connected to the internet, you will receive an OTA update notification for 4.4.3. After installing that, another OTA for GPS improvements will appear.
This worked for me. If you are stuck at some point, please read through the original threads. Especially the firware installation thread has a nice FAQ. Goodluck. Please remember, you can not install an OTA while you have a custom recovery. Please wait until you install the firmware zip for accepting the OTA. If the firmware does not install fro some reason, you can pull the stock recovery from the firmware zip and install this recovery using fastboot. Then you can accept the OTAs.
Let me know how it goes.
Converting back to Sense from GPe prior to running the RUU is what I was afraid of. Oh well, I guess I'll have to set aside a couple of hours this weekend. Thanks for the clarification, guys!
here is a link to show you how to do it, once you have all the files it doesnt take 10 mins. i have done it at least 3 times without a problem.
http://forum.xda-developers.com/showthread.php?t=2733523
chizler said:
here is a link to show you how to do it, once you have all the files it doesnt take 10 mins. i have done it at least 3 times without a problem.
http://forum.xda-developers.com/showthread.php?t=2733523
Click to expand...
Click to collapse
It worked like a charm. I'm now running a full DevEd. Thanks for all your help!
Glad it worked for you.
This was my first full day running the phone since I converted to DevEd and the first thing I've noticed is that the battery life is through the roof. With moderately heavy usage, I currently have about 40% of battery life left. The phone would have been dead by 6 pm when I was running GPe.
Some Help Please!
Hello guys, I converted a BS_US001 to gpe, but I want to go back to stock sense. Yesterday I followed this youtube video http://youtu.be/BLbJaSMfFks to restore the newest stock nandroid backup available 2.22....4, I was able to copy the files and restore everything but for some reason after restoring the boot up of the OS was extremely slow it was taking 5 mins or so to fully boot, I think that my mistake was not doing a "Full custom wipe" in TWRP or a compatibility problem I do not know. I ended up re-installing the GPE RUU.
Today I want to start fresh, could you guys please help me with a few simple steps?
I think this is the order I have to follow:
1. Change CID to 11111111
2. Flash 1.54.401.5
3. Boot into stock recovery to Factory reset
4. Install custom recovery TWRP
5. perform a full custom wipe formating system partition
6. reboot into fastboot and change CID to BS_US001
7. Reboot Fastboot and run RUU (or do I have to have a backup restored first?)
I am missing something? Thank you.
Note: I was able to find this RUU_M8_UL_K44_SENSE60_SECURITY_BrightstarUS_WWE_1.54.1540.10_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_372510_signed_2.exe
*UPDATE: I've messing around with this RUU to avoid the error 59 previously described and I found a great tutorial to extract the RUU zip from the .exe, unfortunately the zip appears to be invalid and cannot be opened (someone mentioned that Zip Repair Pro does the trick but that sounds kinda messy) I tried to flash the 0P6BIMG.zip and the error I get is this:
sending 'zip' (633306 KB)...
OKAY [ 38.593s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 40.025s
Could you guys please share the BrightstarUS RUU again just to confirm if the RUU that I downloaded is corrupted or not?
Thank you again!
lsv-1 said:
Hello guys, I converted a BS_US001 to gpe, but I want to go back to stock sense. Yesterday I followed this youtube video http://youtu.be/BLbJaSMfFks to restore the newest stock nandroid backup available 2.22....4, I was able to copy the files and restore everything but for some reason after restoring the boot up of the OS was extremely slow it was taking 5 mins or so to fully boot, I think that my mistake was not doing a "Full custom wipe" in TWRP or a compatibility problem I do not know. I ended up re-installing the GPE RUU.
Today I want to start fresh, could you guys please help me with a few simple steps?
I think this is the order I have to follow:
1. Change CID to 11111111
2. Flash 1.54.401.5
3. Boot into stock recovery to Factory reset
4. Install custom recovery TWRP
5. perform a full custom wipe formating system partition
6. reboot into fastboot and change CID to BS_US001
7. Reboot Fastboot and run RUU (or do I have to have a backup restored first?)
I am missing something? Thank you.
Note: I was able to find this RUU_M8_UL_K44_SENSE60_SECURITY_BrightstarUS_WWE_1.54.1540.10_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_372510_signed_2.exe
*UPDATE: I've messing around with this RUU to avoid the error 59 previously described and I found a great tutorial to extract the RUU zip from the .exe, unfortunately the zip appears to be invalid and cannot be opened (someone mentioned that Zip Repair Pro does the trick but that sounds kinda messy) I tried to flash the 0P6BIMG.zip and the error I get is this:
sending 'zip' (633306 KB)...
OKAY [ 38.593s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 40.025s
Could you guys please share the BrightstarUS RUU again just to confirm if the RUU that I downloaded is corrupted or not?
Thank you again!
Click to expand...
Click to collapse
I'm having the same problem. I want to convert to Developer edition using a RUU, but none of the Windows 7 machines I can find will run the exe file properly. It's so incredibly frustrating for me! All I need is a working ZIP that doesn't give me the 32 header error
lsv-1 said:
Hello guys, I converted a BS_US001 to gpe, but I want to go back to stock sense. Yesterday I followed this youtube video http://youtu.be/BLbJaSMfFks to restore the newest stock nandroid backup available 2.22....4, I was able to copy the files and restore everything but for some reason after restoring the boot up of the OS was extremely slow it was taking 5 mins or so to fully boot, I think that my mistake was not doing a "Full custom wipe" in TWRP or a compatibility problem I do not know. I ended up re-installing the GPE RUU.
Today I want to start fresh, could you guys please help me with a few simple steps?
I think this is the order I have to follow:
1. Change CID to 11111111
2. Flash 1.54.401.5
3. Boot into stock recovery to Factory reset
4. Install custom recovery TWRP
5. perform a full custom wipe formating system partition
6. reboot into fastboot and change CID to BS_US001
7. Reboot Fastboot and run RUU (or do I have to have a backup restored first?)
I am missing something? Thank you.
Note: I was able to find this RUU_M8_UL_K44_SENSE60_SECURITY_BrightstarUS_WWE_1.54.1540.10_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_372510_signed_2.exe
*UPDATE: I've messing around with this RUU to avoid the error 59 previously described and I found a great tutorial to extract the RUU zip from the .exe, unfortunately the zip appears to be invalid and cannot be opened (someone mentioned that Zip Repair Pro does the trick but that sounds kinda messy) I tried to flash the 0P6BIMG.zip and the error I get is this:
sending 'zip' (633306 KB)...
OKAY [ 38.593s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 40.025s
Could you guys please share the BrightstarUS RUU again just to confirm if the RUU that I downloaded is corrupted or not?
Thank you again!
Click to expand...
Click to collapse
If you are GPe converted then to need to follow the instructions here to go back to Sense.
http://forum.xda-developers.com/showthread.php?t=2733523
Sent from my HTC One_M8 using Tapatalk
Related
Hello, I am unable to get into recovery or in my rom. I can getting into the bootloader, but cannot get into recovery. I am on 1.50 HBOOT and phone is unlocked. I would like to get back to stock so I can do an OTA update. Any help would be great, please let me know if you need more information.
XcsaS said:
Hello, I am unable to get into recovery or in my rom. I can getting into the bootloader, but cannot get into recovery. I am on 1.50 HBOOT and phone is unlocked. I would like to get back to stock so I can do an OTA update. Any help would be great, please let me know if you need more information.
Click to expand...
Click to collapse
What happend to your recovery? Also you need to fastboot oem lock while in hboot using adb
If you wanna go stock you will need the RUU exe you can find this in footballs post in the dev section...
reaper24 said:
What happend to your recovery? Also you need to fastboot oem lock while in hboot using adb
If you wanna go stock you will need the RUU exe you can find this in footballs post in the dev section...
Click to expand...
Click to collapse
not sure what happened with recovery, just wouldn't boot. will I be able to use the RUU exe while in fastboot?
XcsaS said:
Hello, I am unable to get into recovery or in my rom. I can getting into the bootloader, but cannot get into recovery. I am on 1.50 HBOOT and phone is unlocked. I would like to get back to stock so I can do an OTA update. Any help would be great, please let me know if you need more information.
Click to expand...
Click to collapse
if you have a copy of your boot.img and/or your recovery.img file flash that through your fastboot usb screen and reboot you should be ok pending your /system and /data partitioms are ok... if not follow the rest....
ok im goignt to guess youre new to flashing and the android development... but first thing is first... download the stock recovery zip on the other listed thread and rename it PG86IMG.zip... then reboot into your hboot/bootloader.... this will install a stock rom and recovery AFTER that you must reboot then shut down and reboot into your hboot again and from there go to fastboot and plug in the usb cable so your prompt says fastboot usb and then relock your boot loaderafter that finishes reboot again to the ROM and then run your updates... after you get the updates you want you can unlock again and then reinstall superuser and proceed as you want....
wloftus said:
if you have a copy of your boot.img and/or your recovery.img file flash that through your fastboot usb screen and reboot you should be ok pending your /system and /data partitioms are ok... if not follow the rest....
ok im goignt to guess youre new to flashing and the android development... but first thing is first... download the stock recovery zip on the other listed thread and rename it PG86IMG.zip... then reboot into your hboot/bootloader.... this will install a stock rom and recovery AFTER that you must reboot then shut down and reboot into your hboot again and from there go to fastboot and plug in the usb cable so your prompt says fastboot usb and then relock your boot loaderafter that finishes reboot again to the ROM and then run your updates... after you get the updates you want you can unlock again and then reinstall superuser and proceed as you want....
Click to expand...
Click to collapse
Ok following your instructions I downloaded the RUU (two of them infact) changed the name to PG86IMG.zip, when booting into the bootloader, it starts checking the PG86IMG.zip file, there is a blue status bar on the top right, when it fills completely in, it just starting checking the SD card for files again, and then goes back to the normal bootloader screen with options to select fastboot, factory reset, etc... Is there something I missed? I believe there should be some more options.
EDIT: the football post http://forum.xda-developers.com/showthread.php?t=1334473 only goes to .exe files, I had downloaded a .zip file from a different source with the same name, Should I have changed the .exe to PG86IMG.zip?
After using the command flashboot oem lock
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 66977136 (0x3FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.937s
Now showing
*** RELOCKED ***
*** Security Warning ***
XcsaS said:
Ok following your instructions I downloaded the RUU (two of them infact) changed the name to PG86IMG.zip, when booting into the bootloader, it starts checking the PG86IMG.zip file, there is a blue status bar on the top right, when it fills completely in, it just starting checking the SD card for files again, and then goes back to the normal bootloader screen with options to select fastboot, factory reset, etc... Is there something I missed? I believe there should be some more options.
EDIT: the football post http://forum.xda-developers.com/showthread.php?t=1334473 only goes to .exe files, I had downloaded a .zip file from a different source with the same name, Should I have changed the .exe to PG86IMG.zip?
Click to expand...
Click to collapse
no...do not install the exe file at all.... the zip file if it is a trusted source should work...after it loads the files it finishes booting into the hboot screen...from there you can boot into the rom to verify that there is no superuser program and then power down and boot into your hboot again and relock your bootloader then reboot to the rom and update....when you boot back into the rom after installing the zip file it should look like the way it was when you first got it...if not you may have the wrong zip file
Ok I found out there was a zip on that page, I will download that and see where I get. Thank you so much for the help so far.
Ok issue is solved. I guess I needed to be relocked before I could update with PG86IMG.zip. So I guess in the future make sure you are not rooted when trying to update
I was on 4.0.3 and I flashed the zip through AromRa recovery.
Now, when booting up, its stuck at the 4G screen.
The update was the OTA update released to update radios to Global. THIS
It didn't gave any error at all, it said "Reboot to complete installation or update". But when I clicked the reboot option, I saw a line saying something like "Can't write....." then the screen went off and it rebooted. This line was not there, or atleast not visible before I clicked the reboot option.
I am new to rezound and android, so please let me know what I can do. I wasn't able to get a nandroid backup before doing this, had no ext. SD card.
All I did before flashing the zip was flashing the custom recovery. Nothing else. No SU or anything else.
Can I RUU 4.0.3 to fix this problem?
Yes you need to ruu to get it back. I'm assuming your s on. You need to be s off in order to flash radios by themselves.
Sent from my ADR6425LVW using xda app-developers app
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
lamborg said:
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
Click to expand...
Click to collapse
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
feralicious said:
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
Click to expand...
Click to collapse
I relocked but then tried flashing the zip twice.
Here's what comes in cmd:
sending....
OKAY
writing
<bootloader>adopting sig ....
<bootloader>checking sig
failed <remote: not allowed>
finished
After rebooting, it gets stuck on the white HTC screen.
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
mike7728 said:
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
Click to expand...
Click to collapse
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You have to fastboot oem rebootRUU first
then fastboot flash zip PH98IMG.zip
you may have to flash the zip twice.
Code:
androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
(I can't link yet)
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You don't flash this in fastboot since it's a zip file.
EDIT: Looks like you can flash in fastboot as mentioned in the above post. Cool, I like that. I would flash it twice as I've read several times that you need to to make sure it gets all the system files.
If htat doesn't work for whatever reason, just put it on the sd card of your phone, detach your phone from your pc and reboot. hboot should find it (it looks for the PH98IMG.zip file) and flash it. Flash it twice to be sure it gets all the system files.
When it's done and you're rebooted use a file explorer and delete the PH98IMG file so it doesn't flash again on the next reboot.
I have experience with HTC EVO phones, but the Rezound is new to me. it's root and s-off are different, and I've gotten myself stuck.
Before I make things worse, I want to ask for some help. I tried flashing the newest CM ROM, while s-on, and now can't get past the HTC boot screen. I can get into the bootloader, and into recovery, but I'm not sure what to flash to get the phone bootable again. I can't mount the USB from TWRP (well I can, but can't see the SD card in either windows on Linux), so I have to take the card, but it into another phone to copy files to it, then put it back into this phone.
So, here is where I am now, how should I proceed?
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
eMMC-boot
TWRP recovery works fine, but I'm not sure what to install from here to fix me up. I have 3 RUU files, (1.02.605.6, 2.01.605.11 and 3.14.605.12 ICS) but can't get the USB connection to work so I need to flash from recovery. I could try connecting to a windows 7 machine (I'm running windows 8 and Ubuntu 13.10)
My goal is to get back to something stock, so I can s-off, so I can install a recent ICS build and use a Verizon phone with the Telcel GSM network in Mexico.
All help is much appreciated!!
JustinChase said:
I have experience with HTC EVO phones, but the Rezound is new to me. it's root and s-off are different, and I've gotten myself stuck.
Before I make things worse, I want to ask for some help. I tried flashing the newest CM ROM, while s-on, and now can't get past the HTC boot screen. I can get into the bootloader, and into recovery, but I'm not sure what to flash to get the phone bootable again. I can't mount the USB from TWRP (well I can, but can't see the SD card in either windows on Linux), so I have to take the card, but it into another phone to copy files to it, then put it back into this phone.
So, here is where I am now, how should I proceed?
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
eMMC-boot
TWRP recovery works fine, but I'm not sure what to install from here to fix me up. I have 3 RUU files, (1.02.605.6, 2.01.605.11 and 3.14.605.12 ICS) but can't get the USB connection to work so I need to flash from recovery. I could try connecting to a windows 7 machine (I'm running windows 8 and Ubuntu 13.10)
My goal is to get back to something stock, so I can s-off, so I can install a recent ICS build and use a Verizon phone with the Telcel GSM network in Mexico.
All help is much appreciated!!
Click to expand...
Click to collapse
the reason you are stuck is because you have to fastboot flash the boot.img exctracted from that rom via fastboot usb in the bootloader...you must also have an unlocked bootloader to do this....if you need further instructions ill be glad to help.....as for the RUU's you need to be s-off and have a relocked bootloader for them to work or you can brick the device
REV3NT3CH said:
the reason you are stuck is because you have to fastboot flash the boot.img exctracted from that rom via fastboot usb in the bootloader...you must also have an unlocked bootloader to do this....if you need further instructions ill be glad to help.....as for the RUU's you need to be s-off and have a relocked bootloader for them to work or you can brick the device
Click to expand...
Click to collapse
Thanks. Considering my goal for now is to get back to a stock ROM so I can get s-off, would it be better to rename an RUU to PH98IMG.zip, then relock my bootloader, then flash the PH98IMG from the bootloader, to get me to a stock/updated/known ROM all in one shot, or do I have to figure out how to flash the boot.img file from the CM ROM, then flash the RUU after that's done. Either way, I need to relock the bootloader to flash or install an RUU, correct?
My Windows 8 computer just seems to have given up on reading/identifying the phone while the phone is in recovery, and I've spent too many hours trying to fix that stupid problem, that I'm almost ready to dump windows 8, and install 7 on this new laptop. I have another w7 laptop in the house that I could use, but if there's a simple HTC drivers for windows 8 fix that actually works, I'd probably rather keep windows 8 and do it all with this machine.
thanks again.
JustinChase said:
Thanks. Considering my goal for now is to get back to a stock ROM so I can get s-off, would it be better to rename an RUU to PH98IMG.zip, then relock my bootloader, then flash the PH98IMG from the bootloader, to get me to a stock/updated/known ROM all in one shot, or do I have to figure out how to flash the boot.img file from the CM ROM, then flash the RUU after that's done. Either way, I need to relock the bootloader to flash or install an RUU, correct?
My Windows 8 computer just seems to have given up on reading/identifying the phone while the phone is in recovery, and I've spent too many hours trying to fix that stupid problem, that I'm almost ready to dump windows 8, and install 7 on this new laptop. I have another w7 laptop in the house that I could use, but if there's a simple HTC drivers for windows 8 fix that actually works, I'd probably rather keep windows 8 and do it all with this machine.
thanks again.
Click to expand...
Click to collapse
ruu is an exe file... ota is a .zip.....your best option to do s-off is install amon ra recovery and install a stock based rom found in Rezound Android Developement....if you follow my s-off guide here in the Rezound [email protected] youll find links to everything you will need.....windows 8 requires special drivers for anything to work....i suggest downgrading to windows 7 if you can as 8 has way too many compatibility issues with anything that requires legacy stuff
REV3NT3CH said:
ruu is an exe file... ota is a .zip.....your best option to do s-off is install amon ra recovery and install a stock based rom found in Rezound Android Developement....if you follow my s-off guide here in the Rezound [email protected] youll find links to everything you will need.....windows 8 requires special drivers for anything to work....i suggest downgrading to windows 7 if you can as 8 has way too many compatibility issues with anything that requires legacy stuff
Click to expand...
Click to collapse
Yeah, I saw someone suggest to rename the RUU.exe file to PH98IMG.zip file to flash it with the bootloader. it this would work, it seems the easiest thing to do from here, but you suggest that it might brick the phone, so I'm not ready to try that yet.
Yes, I was trying to follow your "how to" guide, and you say to flash a stock ROM, and point to one as an example (Global OTA RED-1.0) ROM, but that ROM points to another thread on how to flash ROM with s-on, and it's not particularly clear what one should do, so I'm not sure how to proceed from here, exactly. Here are the steps that are unclear to me...
-adb reboot bootloader
-fastboot erase cache
-fastboot oem lock
-fastboot oem rebootRUU (is this the exact text to type, or do they mean -fastboot oem Global_OTA_RED-v1.0.zip or do they mean -fastboot oem RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe or something else entirely?)
-fastboot flash zip firmware.zip (where am I getting "firmware.zip or is this another example of me needing to replace firmware.zip with something else, and if so, what?)
(it will fail for with pre-update flush again immediately error). So do it again -->
-fastboot flash zip firmware.zip
(it will finish)
when its done:
-fastboot reboot-bootloader
-fastboot flash unlocktoken Unlock_code.bin
-pull the battery and replace.
Once this is done, I think I could then proceed to the s-off process.
[Stupid windows 8 drivers - I will have to install Windows 7 on another partition now ]
JustinChase said:
Yeah, I saw someone suggest to rename the RUU.exe file to PH98IMG.zip file to flash it with the bootloader. it this would work, it seems the easiest thing to do from here, but you suggest that it might brick the phone, so I'm not ready to try that yet.
Yes, I was trying to follow your "how to" guide, and you say to flash a stock ROM, and point to one as an example (Global OTA RED-1.0) ROM, but that ROM points to another thread on how to flash ROM with s-on, and it's not particularly clear what one should do, so I'm not sure how to proceed from here, exactly. Here are the steps that are unclear to me...
-adb reboot bootloader
-fastboot erase cache
-fastboot oem lock
-fastboot oem rebootRUU (is this the exact text to type, or do they mean -fastboot oem Global_OTA_RED-v1.0.zip or do they mean -fastboot oem RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe or something else entirely?)
-fastboot flash zip firmware.zip (where am I getting "firmware.zip or is this another example of me needing to replace firmware.zip with something else, and if so, what?)
(it will fail for with pre-update flush again immediately error). So do it again -->
-fastboot flash zip firmware.zip
(it will finish)
when its done:
-fastboot reboot-bootloader
-fastboot flash unlocktoken Unlock_code.bin
-pull the battery and replace.
Once this is done, I think I could then proceed to the s-off process.
[Stupid windows 8 drivers - I will have to install Windows 7 on another partition now ]
Click to expand...
Click to collapse
no an ruu.exe you run in windows and is a program....a ph98img is an ota update file or something custom made like a recovery and when flashing a rom you have to extract that particular rom with lets say 7 zip...pull the boot.img file out of it and place it in the fastboot folder on your pc.. boot into bootloader on the phone and select the fastboot option then plug it into pc....once the phone says fastboot usb in command prompt direct it using cd C:\yourfastbootdirectory then once you are in fastboot folder in command prompt typt fastboot flash boot boot.img....you only do this after flashing a rom in custom recovery
Edit: btw this is your only option to have a usable rom while s-on including getting to a stock rom again....running the ruu.exe while s-on will brick you....a ph98img.zip with a version of android older than what you are on will brick also or give you a main version is older error
REV3NT3CH said:
no an ruu.exe you run in windows and is a program....a ph98img is an ota update file or something custom made like a recovery and when flashing a rom you have to extract that particular rom with lets say 7 zip...pull the boot.img file out of it and place it in the fastboot folder on your pc.. boot into bootloader on the phone and select the fastboot option then plug it into pc....once the phone says fastboot usb in command prompt direct it using cd C:\yourfastbootdirectory then once you are in fastboot folder in command prompt typt fastboot flash boot boot.img...you only do this after flashing a rom in custom recovery
Edit: btw this is your only option to have a usable rom while s-on including getting to a stock rom again....running the ruu.exe while s-on will brick you....a ph98img.zip with a version of android older than what you are on will brick also or give you a main version is older error
Click to expand...
Click to collapse
Thanks again. I thought it was weird to rename an RUU to the img file, which is why I asked before proceeding. So, since I flashed the CM ROM, I need to pull the boot.img from that same ROM, put it in the android SDK folder on my machine (which is now running Windows 7), then run the fasboot flash boot boot.img and then I should have a functioning phone again.
Then, do the s-off procedure, then I can flash the newest RUU to get everything updated/current, then I can run any ICS ROM from that point.
Sound about right?
Oh, I had to wipe the machine to install windows 7, so I no longer have Ubuntu installed for dual boot. The unlimited site says it only works with Ubuntu 32-bit, and doesn't work with Live USB. I don't want to install 32 bit Ubuntu (rather install 64 bit). What is the best method for s-off, considering these limitations?
thanks again for all your help!!
JustinChase said:
Thanks again. I thought it was weird to rename an RUU to the img file, which is why I asked before proceeding. So, since I flashed the CM ROM, I need to pull the boot.img from that same ROM, put it in the android SDK folder on my machine (which is now running Windows 7), then run the fasboot flash boot boot.img and then I should have a functioning phone again.
Then, do the s-off procedure, then I can flash the newest RUU to get everything updated/current, then I can run any ICS ROM from that point.
Sound about right?
Oh, I had to wipe the machine to install windows 7, so I no longer have Ubuntu installed for dual boot. The unlimited site says it only works with Ubuntu 32-bit, and doesn't work with Live USB. I don't want to install 32 bit Ubuntu (rather install 64 bit). What is the best method for s-off, considering these limitations?
thanks again for all your help!!
Click to expand...
Click to collapse
ive done it on ubuntu 12.04 64 bit....those on higher versions have had to instal the 32bit libs on 64bit which in the comments in my s-off guide a guy posted on how to do just that
REV3NT3CH said:
ive done it on ubuntu 12.04 64 bit....those on higher versions have had to instal the 32bit libs on 64bit which in the comments in my s-off guide a guy posted on how to do just that
Click to expand...
Click to collapse
Worked great!!! I'm now s-off.
Now I just need to figure out how to get updated to the most recent radios and firmware, then pick a new ROM.
Thanks for all your help!
JustinChase said:
Worked great!!! I'm now s-off.
Now I just need to figure out how to get updated to the most recent radios and firmware, then pick a new ROM.
Thanks for all your help!
Click to expand...
Click to collapse
in my downgrade/upgrade guide the ph98img ota's are the updates to most recent hboot and radios...
Hello,
My phone is at:
Android ver 4.4.2
Sense 6.0
Software ver ARHD 71.1 (ROM ver# 5.11.401.10)
HTC SDK API 6.20
Kernel 3.4.10-ElementalX-14.8
Baseband ver 4T.24.3218.09_10.26.1718.01L
S-ON (Unlocked via HTCDev)
HBOOT - 1.56
AT&T
How do I update my firmware to v5.12.502.2 with S-ON ? Is there a zip file that I can flash ?
Thank you in advance...
I updated ota after restoring my stock backup and stock recovery.
Sent from my HTC One
Clselfridge said:
I updated ota after restoring my stock backup and stock recovery.
Sent from my HTC One
Click to expand...
Click to collapse
Thanks !
I will give that a shot if nothing else works.
Yesterday, I extracted firmware.zip file from the AT&T OTA update released on June 5th (thanks to @xangel9626). I confirmed that MID and CID are matching in the android-info.txt. But when I flash it vai twrp, it keeps on failing. It seems custom recovery is not able to open it. I tried adb method and it also failed with error code -99.
st167 said:
Thanks !
I will give that a shot if nothing else works.
Yesterday, I extracted firmware.zip file from the AT&T OTA update released on June 5th (thanks to @xangel9626). I confirmed that MID and CID are matching in the android-info.txt. But when I flash it vai twrp, it keeps on failing. It seems custom recovery is not able to open it. I tried adb method and it also failed with error code -99.
Click to expand...
Click to collapse
Yes I believe you need stock recovery... Not sure though as I restored my stock everything and just let my phone ota itself.
Sent from my HTC One
st167 said:
Thanks !
I will give that a shot if nothing else works.
Yesterday, I extracted firmware.zip file from the AT&T OTA update released on June 5th (thanks to @xangel9626). I confirmed that MID and CID are matching in the android-info.txt. But when I flash it vai twrp, it keeps on failing. It seems custom recovery is not able to open it. I tried adb method and it also failed with error code -99.
Click to expand...
Click to collapse
go read again the instructions to flash firmware
http://forum.xda-developers.com/showthread.php?t=2365506
http://forum.xda-developers.com/showthread.php?t=2419699
Stock recovery,stock rom,accept ota no way around it
st167 said:
Thanks !
I will give that a shot if nothing else works.
Yesterday, I extracted firmware.zip file from the AT&T OTA update released on June 5th (thanks to @xangel9626). I confirmed that MID and CID are matching in the android-info.txt. But when I flash it vai twrp, it keeps on failing. It seems custom recovery is not able to open it. I tried adb method and it also failed with error code -99.
Click to expand...
Click to collapse
Okay so after lots of reboots and lost original stock backup, I was able to update firmware...
Here is what I did:
1. Create backup in twrp
2. Install stock recovery image
(recovery_1.26.502.15_signed.img)
3. fastboot oem lock
After installing stock recovery and relock:
4. place firmware zip file in fastboot directory
(5.12.502.2.firmware.zip [http://forum.xda-developers.com/showthread.php?t=2775650&])
5. enable usb debug, disable fastboot, connect phone to pc
6. open cmd to fastboot directory
7. adb reboot bootloader
8. fastboot devices (checks connection – should display your device)
9. fastboot erase cache
10. fastboot oem rebootRUU
11. fastboot flash zip zipfilename.zip (most likely will fail at pre-update…)
12. fastboot flash zip zipfilename.zip (same command again)
13. fastboot reboot-bootloader (should see new firmware version listed)
14. fastboot reboot
Then, unlock again:
a. fastboot erase cache
b. fastboot flash unlocktoken unlock_code.bin
Restore backup:
I. flash twrp 2.7.1.0
II. put backup folder back to sdcard
III. flash backup
Thank you everyone !
Edit: I have also uploaded a Guru_Reset of this if anyone is interested (Thanks to @crushalot)
Download it Here
for instructions look here >> http://forum.xda-developers.com/showthread.php?t=2358738
WARNING!!! include optional flashable radio.
..here is the Stock Nandroid before the phone was rooted
http://www.androidfilehost.com/?fid=23501681358543596
MD5: b01ad6da065b19c7aff36f77724a5b74
Extract zip, copy 'HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted' folder to /sdcard/TWRP/BACKUPS//HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted
For complete stock Say no to installing Root when exiting TWRP and Flash the Stock Recovery
It's also recommended to Factory Reset in TWRP after Restoring the Firmware
http://www.androidfilehost.com/?fid=23501681358543599
MD5: 1a8b1482d4525488c89335df07dc24f2
reboot into fastboot USB
fastboot flash recovery 5.12.502.2.recovery.img
fastboot erase cache
fastboot reboot
Be Very Careful with the firmware posted below, I actually put my HTC One into QHSUSB_DLOAD Flashing this. I was able to fix it (Thanks to dexter93) but be very careful and do not flash a 3.xx.502.x firmware with the one posted below !!
http://forum.xda-developers.com/showthread.php?t=2770684
This will fix devices which were bricked due to firmware incompatibility. This can be caused with the way HTC handles the firmware updates in it's m7's OTAs. If you've been flashing from a 3.x firmware to a 5.x firmware via OTA, or manually, you most likely have a device stuck in QHSUSB_DLOAD. This tool is for you
Click to expand...
Click to collapse
For Completeness here's the 5.12.502.2.firmware.zip
http://www.androidfilehost.com/?fid=23501681358543602
MD5: 4d671edd6bcf1876c44c3798aaaebb0c
Flash with fastboot oem rebootRUU
fastboot oem rebootRUU
fastboot flash zip 5.12.502.2.firmware.zip
fastboot flash zip 5.12.502.2.firmware.zip
Greetings,
Please stay on topic.
Thanks,
BD619
Hey, quick question:
do I need S-Off for this to work?
kml.krk said:
Hey, quick question:
do I need S-Off for this to work?
Click to expand...
Click to collapse
no, I don't think so
A little help. I have S-Off, Unlocked bootloader, and am rooted. The only mods to my stock rom are rooting and a tweak to enable wifi hotspot. Will your instructions still work to update my phone to latest firmware? Do I have to unroot first and relock my bootloader?
clsA said:
As the title says ..this is the Stock Nandroid before the phone was rooted
Edit: I have also uploaded a Guru_Reset (Thanks to @crushalot) of this if anyone is interested just shoot me a PM
http://www.androidfilehost.com/?fid=23501681358543596
MD5: b01ad6da065b19c7aff36f77724a5b74
Extract zip, copy 'HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted' folder to /sdcard/TWRP/BACKUPS/<serialnum>/HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted
For complete stock Say no to installing Root when exiting TWRP and Flash the Stock Recovery
http://www.androidfilehost.com/?fid=23501681358543599
MD5: 1a8b1482d4525488c89335df07dc24f2
reboot into fastboot USB
fastboot flash recovery 5.12.502.2.recovery.img
fastboot erase cache
fastboot reboot
Be Very Careful with the firmware posted below, I actually put my HTC One into QHSUSB_DLOAD Flashing this. I was able to fix it (Thanks to dexter93) but be very careful and do not flash a 3.xx.502.x firmware with the one posted below !!
http://forum.xda-developers.com/showthread.php?t=2770684
For Completeness here's the 5.12.502.2.firmware.zip
http://www.androidfilehost.com/?fid=23501681358543602
MD5: 4d671edd6bcf1876c44c3798aaaebb0c
Flash with fastboot oem rebootRUU
fastboot oem rebootRUU
fastboot flash zip 5.12.502.2.firmware.zip
fastboot flash zip 5.12.502.2.firmware.zip << Yes Two times (First time updates hboot)
fastboot reboot
Click to expand...
Click to collapse
Worked nicely, thanks.
Edit: Also, it's very very very recommended to Factory Reset in TWRP after Restoring the Firmware. If not done right after Restore, the device may malfunction in some areas, and may (very little) lead to Bricking. I have done this before, when flashing the USA Firmware Version of HTC One's Sense 6. Had to return to Stock due to some recent news in my Data, not connecting to the AT&T Towers, and other stuff. That being said, I've done the old fastboot oem lock and relocked my bootloader, and never again will I ever flash a ROM or anything on my device. Thanks again.
Code:
C:\Program Files (x86)\Android\sdk\platform-tools>fastboot flash recovery 5.12.5
02.2.recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (12426 KB)...
OKAY [ 1.482s]
writing 'recovery'...
OKAY [ 0.891s]
finished. total time: 2.373s
C:\Program Files (x86)\Android\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.048s]
finished. total time: 0.048s
C:\Program Files (x86)\Android\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.034s
SMaximus7 said:
A little help. I have S-Off, Unlocked bootloader, and am rooted. The only mods to my stock rom are rooting and a tweak to enable wifi hotspot. Will your instructions still work to update my phone to latest firmware? Do I have to unroot first and relock my bootloader?
Click to expand...
Click to collapse
I don't know what firmware your on now
it's critical you don't try and skip a version
you have to go 3.xx -->> 4.xx ->> 5.xx
3.xx ->> 5.xx can send you into the QHSUSB_DLOAD Brick
Be careful
clsA said:
I don't know what firmware your on now
it's critical you don't try and skip a version
you have to go 3.xx -->> 4.xx ->> 5.xx
3.xx ->> 5.xx can send you into the QHSUSB_DLOAD Brick
Be careful
Click to expand...
Click to collapse
Sorry I should have mentioned I'm on 4.18.502.7. So I guess the question would be, is it ok to flash this over what I have, or should I install the 4.18.502.7 RUU first to take me to complete stock and then flash this?
Also, can someone point me in the direction of a 4.18.502.7 stock recovery?
Thanks for the help.
SMaximus7 said:
Sorry I should have mentioned I'm on 4.18.502.7. So I guess the question would be, is it ok to flash this over what I have, or should I install the 4.18.502.7 RUU first to take me to complete stock and then flash this?
Also, can someone point me in the direction of a 4.18.502.7 stock recovery?
Thanks for the help.
Click to expand...
Click to collapse
Here you go
https://www.dropbox.com/s/u1ldcszwq5fc0f0/4.18.502.7 stock_recovery.img
clsA said:
Here you go
https://www.dropbox.com/s/u1ldcszwq5fc0f0/4.18.502.7 stock_recovery.img
Click to expand...
Click to collapse
im in the same boat... do i flash this from TWRP or from stock boot loader?
ubnjacked said:
im in the same boat... do i flash this from TWRP or from stock boot loader?
Click to expand...
Click to collapse
what are you trying to gain by flashing just recovery ?
fastboot flash recovery stock_recovery.img
4.18.502.7 stock_recovery - Delete the part in Red
clsA said:
what are you trying to gain by flashing just recovery ?
fastboot flash recovery stock_recovery.img
4.18.502.7 stock_recovery - Delete the part in Red
Click to expand...
Click to collapse
im trying to get the stock recovery on... i currently was using rom manager and want to change to stock sorry really kinda noob when it come to this phone, my old htc inspire was super easy =)
I think this is just what I need -- I can restore just system from the this TWRP backup in my TWRP recovery and then essentially have an 5.5 --> 6.0 upgrade same as OTA would do if I weren't S-ON/unlocked and could actually apply OTA updates??
I want to avoid having to reconfigure or reinstall anything. I know I take my own risk and if trouble, will have to factory reset.
Dont know if that will work....good luck
Almost does. Booted up just fine and all my apps and settings/config was there other than the wallpaper and Blinkfeed settings. Feeling great right up until the spontaneous reboot, lol. OK, now I'll just do a full restore of this backup and then do a Titanium Backup restore for my apps and settings. Hopefully, that works no prob...
Your gonna have issues again,never restore system data/settings....apps ok
StephenMSmith said:
Almost does. Booted up just fine and all my apps and settings/config was there other than the wallpaper and Blinkfeed settings. Feeling great right up until the spontaneous reboot, lol. OK, now I'll just do a full restore of this backup and then do a Titanium Backup restore for my apps and settings. Hopefully, that works no prob...
Click to expand...
Click to collapse
Really? I've done it in the past (flashed an RUU for 4.x and then restored system settings and user apps) w/o issue. Will report on this attempt shortly.
This worked fine. I retired user apps and system data (not system apps of course ). All my setting intact except for the sense stuff. No problems at all.
Last post in here as to not hijack thread, it is always best to reinstall and set up apps from scratch on new rom, the way you and many others do this restore,your settings from an older system/rom may overwrite the newer improvements enhancements in the newer rom, your walking two steps forward and 6 backwards...just my thoughts on it
@clsA sent you a pm