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
Related
***unlocked***
shooter xc ship s-on RL
hboot 1.50.0000
radio -0.97.10.000
emmc-boot
aug 7 2011
I have a hand me down Sprint evo 3d that I believe has the HTC dev unlock. I attempted to install the following OTA update.
- OTA_Shooter_S_Sprint_WWE_2.08.651.3-2.08.651.2_release_2201598na37g8l1af4e904
The phone restarted during the update and went to the exclamation screen with the blue android guy. I can get into hboot but when I try to get into recovery the phone boot loops again.
I have been reading for hours and have found several suggestions but do not know where to go from here. From what I can tell I need to re-flash a rom and/or flash a recovery image but but I am not sure exactly what versions of either is needed, where I would get it or if any prior steps are required due to the phones current configuration. I am also not sure how to complete this as from what I can tell, I may have trouble due to the 1.5 boot loader. As much as I would like to try a few things on my own, I don not want to cause more damage or more work for myself.
A few notes.
- I am using a MAC
- I have the android SDK installed but am not familiar with any commands.
- I do not know what version of android I had installed prior to the attempted updated other then I am sure it was a stock HTC load.
- I have not done anything other then try to load recovery since the boot loop
- I can not locate a back up on the SD card.
- I have access to a external SD card reader
- I have access to a external battery charger.
Any help would be much appreciated.
flash stock recovery, lock your bootloader then run the ota exe. But why on earth are you flashing the old gingerbread ruu when ICS is available?
mnomaanw said:
flash stock recovery, lock your bootloader then run the ota exe. But why on earth are you flashing the old gingerbread ruu when ICS is available?
Click to expand...
Click to collapse
I attempted to flash the recover using recovery image you posted in another thread.
mnomaanw said:
Not all recoveries work on hboot 1.50 . I got only two working
First boot in bootloader by pressing volume down+power button, then select fastboot and flash this recovery http://www.mediafire.com/?n72emuv5a1c00sd
after flashing recovery , flash a boot.img from the ROM you want to use from fastboot (sorry dont know mac commands)
And then just follow the steps from step no 6 from the link given below.
You should flash the same ROM(MIUI is used in post below) from which you have flashed the boot.img above.
http://forum.xda-developers.com/showpost.php?p=19967637&postcount=16
necessary file are attached in the post and you should put them on SD card
If the above recovery wont boot ....try the recovery from this post
http://forum.xda-developers.com/showpost.php?p=19944274&postcount=9
Click to expand...
Click to collapse
The phone rebooted back into the boot loop. I can still access hboot but am not able to access recovery. I may be using the wrong method or commands.
Input:
./fastboot-mac boot ./recovery.img
Output:
downloading 'boot.img'... OKAY
booting... OKAY
Here is what I get in the fast boot help menu...
usage: fastboot [ <option> ] <command>
commands:
update <filename>.................................reflash device from update.zip
flashall..................................................flash boot + recovery + system
flash <partition> [ <filename> ]...............write a file to a flash partition
erase <partition>...................................erase a flash partition
getvar <variable>..................................display a bootloader variable
boot <kernel> [ <ramdisk> ]...................download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ].....create bootimage and flash it
devices.................................................list all connected devices
reboot....................................................reboot device normally
reboot-bootloader....................................reboot device into bootloader
options:
-w...............................................erase userdata and cache
-s <serial number>.......................specify device serial number
-p <product>................................specify product name
-c <cmdline>...............................override kernel commandline
-i <vendor id>...............................specify a custom USB vendor id​
Do you know if I am attempting to flash the recover correctly? It appears as if it is looking for a boot.img from a rom.
To answer your question, the original goal was to update to ICS. I was not aware that the the phone was dev unlocked and never considered that the OTA would cause a problem. I thought it was odd that the available OTA it offered was GB but wrote it off as potentially requiring a series of sequential updates to arrive at the latest version.
After reading this thread I tried flashing again....
http://forum.xda-developers.com/showthread.php?t=1592922
Input:
/fastboot-mac flash recovery recovery.img
Output:
sending 'recovery' (5068 KB)... OKAY
writing 'recovery'... OKAY
The phone went back into a boot loop. I am essentially back to were I started.
I would assume the above procedure is correct. Other then trying other recovery images, I am not sure where to go from here.
I flashed the CWM image from this link as well with no luck.
http://forum.xda-developers.com/showpost.php?p=19944274&postcount=9
Still no luck here. Does anyone think the problem flashing the recovery has anything to do with s-on? I found this link related to the legend and think it may apply.
http://forum.xda-developers.com/showthread.php?t=1290841
I obviously have not tried it because the linked CWM appears to not apply to my phone and I found nothing on CWM's site that would apply.
I am not specifically looking to go stock. I just would like to get the phone working again. Do I need to get recovery working to flash this? Should I just be looking for rom and using hboot with PG86IMG.zip on the SD card? Any input on this would be very much appreciate.
you should not boot the stock recovery , it will never work.
you should flash it to your device. then take the ota .
if it does not work, lock your bootloader after flashing stock recovery , then take OTA.
I'm having the same problem, boot loop after trying to flash the new OTA zip from the development section now no matter what ROM I flash nothing works. Do I have to try and relock the boot loader then run the stock RUU?
Sent from my cm_tenderloin using xda premium
mnomaanw said:
you should not boot the stock recovery , it will never work.
you should flash it to your device. then take the ota .
if it does not work, lock your bootloader after flashing stock recovery , then take OTA.
Click to expand...
Click to collapse
Thank you, I was not aware of that. However, I should be able to flash custom recoveries while unlocked s-on correct? I have tried flashing quite a few custom recoveries and am still unable to boot into recovery using hboot or ./fastboot-mac boot (recovery).img.
I plan on working on it more tonight and if I can get it working I'll be sure to post the resolution for other experiencing the same issue. Thanks again for your help.
I just relocked my bootloader and went back to stock Ill mess with it later but at least it works now.
That is great, thanks for the update. I'll give it a shot after work and report back. I got hung up on not being able to get a stock or custom recovery loaded. I was worried about not using recovery to "clean up" before moving on.
Out of curiosity, what method did you flash your rom?
I used the touch recovery then it went to bootloop so I re locked the bootloader and ran the stock RUU, then updated to the OTA 4.0.
Sent from my PG86100 using xda premium
malicenfz said:
I'm having the same problem, boot loop after trying to flash the new OTA zip from the development section now no matter what ROM I flash nothing works. Do I have to try and relock the boot loader then run the stock RUU?
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Did you actually flash the OTA successfully and no roms would boot afterward?
You can't take the ota if you are unlocked. Flash twrp 2.2.0 (directions are on their site), then flash a custom rooted ROM. Since you are s-on, you will have to flash the kernel properly (using fastboot or flash image GUI). I recommend you get s-off.
I would give you links, but I'm on my phone. Google is your friend.
Save the Drama for your Mama with Tapatalk 2
Wow Thanks Guy. I used this method to stop boot-loops with 4.0 Rom and it worked like a charm.
hey guys. after flashing a rom and fastbooting the boot.img, it seems that every time i take the battery out, the system gets stuck with the initial loading. The screen doesn't show the "beats audio"part and the sound is gone. then I get a dark screen and its stuck. Only when I fasboot the boot.img again it goes back to normal. Any idea if thats normal?
Use command
fastboot flash boot boot.img
not
fastboot boot boot.img
ckpv5 said:
Use command
fastboot flash boot boot.img
not
fastboot boot boot.img
Click to expand...
Click to collapse
hm. I'm getting an error message. I tried both with the Boot.img installer that came with the Fulmix Rom and the default Boot.img
C:\HTC>fastboot flash boot boot.img
sending 'boot' (4508 KB)...
OKAY [ 0.847s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 0.852s
gbarnoy said:
hm. I'm getting an error message. I tried both with the Boot.img installer that came with the Fulmix Rom and the default Boot.img
C:\HTC>fastboot flash boot boot.img
sending 'boot' (4508 KB)...
OKAY [ 0.847s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 0.852s
Click to expand...
Click to collapse
On which Hboot are you?
GtrCraft said:
On which Hboot are you?
Click to expand...
Click to collapse
1.20
I've done something wrong, haven't I? :crying:
gbarnoy said:
1.20
I've done something wrong, haven't I? :crying:
Click to expand...
Click to collapse
You have an old ICS hboot so it's best for you to flash an ICS rom and ICS boot.img
ckpv5 said:
You have an old ICS hboot so it's best for you to flash an ICS rom and ICS boot.img
Click to expand...
Click to collapse
I see. is there a possibility for me to upgrade it? if its possible, do you have a recommended Hboot or a thread I can read about it? I have been running to other problems as well when I was trying to get the rom up and running to be honest... I guess it could be related.
gbarnoy said:
I see. is there a possibility for me to upgrade it? if its possible, do you have a recommended Hboot or a thread I can read about it? I have been running to other problems as well when I was trying to get the rom up and running to be honest... I guess it could be related.
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=2212067 you find all info.
Read carrefully.
xpirt
xpirt said:
Here: http://forum.xda-developers.com/showthread.php?t=2212067 you find all info.
Read carrefully.
xpirt
Click to expand...
Click to collapse
ckpv5 said:
You have an old ICS hboot so it's best for you to flash an ICS rom and ICS boot.img
Click to expand...
Click to collapse
hey guys, just to give you an update - I checked out both of your suggestions. for the upgrade of the HBOOT I could not locate a version for my own CID. I did however go with the suggestion to work with ICS recovery and ICS rom to load up. This is what I did:
1) while in the JB rom, I flashed ICS TWRP recovery
2) then, according to ShadowX suggestions, I first loaded up the boot installer from the computer while in Fastboot mode
3) wiped Data and Cache
4) flashed the Rom. apparently it has Busybox within the installer
Now, so far so good. I took off the battery and it still loaded up fine. Thanks so much for your responses!
gbarnoy said:
hey guys, just to give you an update - I checked out both of your suggestions. for the upgrade of the HBOOT I could not locate a version for my own CID. I did however go with the suggestion to work with ICS recovery and ICS rom to load up. This is what I did:
1) while in the JB rom, I flashed ICS TWRP recovery
2) then, according to ShadowX suggestions, I first loaded up the boot installer from the computer while in Fastboot mode
3) wiped Data and Cache
4) flashed the Rom. apparently it has Busybox within the installer
Now, so far so good. I took off the battery and it still loaded up fine. Thanks so much for your responses!
Click to expand...
Click to collapse
What is your cid?
GtrCraft said:
What is your cid?
Click to expand...
Click to collapse
ORANG309 - should be Spain.
gbarnoy said:
ORANG309 - should be Spain.
Click to expand...
Click to collapse
If you have a backup from your stock rom, you can use that along with stock recovery and boot.img to upgrade to Hboot 1.25 so that you can use JB roms
GtrCraft said:
If you have a backup from your stock rom, you can use that along with stock recovery and boot.img to upgrade to Hboot 1.25 so that you can use JB roms
Click to expand...
Click to collapse
yeah, I managed to understand that only after rooting the phone without doing any backup... It seems no-one else on the internet has this CID or has a downloadable version.
As I was using CM 4.4.2, everything was going fine, I had 3 bars of LTE, and then I tried to make a call and it said mobile networks not available, I checked my signal in the status bar and it still said LTE and data still worked fine. I went to my phone settings and checked it and it said my mobile network was unknown, and my phone number was 000-000-0000. I wiped, and flashed CM10.2(4.3) and it did the exact same thing, only this time it said my phone number, but still, I couldn't make any calls or text, I've tried flashing two sense 5 roms and none of them display my phone number or let me call or text, but upon changing the subscription type from global to LTE/CDMA, it gives me LTE data, but that's it...Can anyone please help me?
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
santod040 said:
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So basically follow this guide? http://forum.xda-developers.com/showthread.php?t=2293919
rejectedjs said:
So basically follow this guide? http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
No, I was never implying to relock or return to s-on.
Flash my rooted stock odexed Rom and a stock recovery and do a factory reset.
Follow my guide above....
Sent from my HTC6500LVW using Tapatalk
santod040 said:
No, I was never implying to relock or return to s-on.
Flash my rooted stock odexed Rom and a stock recovery and do a factory reset.
Follow my guide above....
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Alright...I know I'm being annoying, but I want to thank you for helping anyway. Where do I find a stock recovery and how do I flash it?
rejectedjs said:
Alright...I know I'm being annoying, but I want to thank you for helping anyway. Where do I find a stock recovery and how do I flash it?
Click to expand...
Click to collapse
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
santod040 said:
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
Click to expand...
Click to collapse
It worked! Thanks so much dude, this problem has been bugging me since I was in school earlier today, and you helped me out within minutes, I wish I could press the thanks button multiple times.
rejectedjs said:
It worked! Thanks so much dude, this problem has been bugging me since I was in school earlier today, and you helped me out within minutes, I wish I could press the thanks button multiple times.
Click to expand...
Click to collapse
No problem bud.
Glad that worked out for you.
Same process always fixes 3g/4g issues after flashing many roms for me, on all of my devices.
:good:
This exact thing happened to me a few weeks ago. Busted my ass trying to fix it, after a few days of no service i finally got it.
---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------
The way you fixed it seems a lot easier than what I did. I returned to s-on, 1.15 hboot and the oldest firmware. Now my phone's bootloader will always say tampered too, since i had to HTC dev unlock it to get root.
santod040 said:
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
Click to expand...
Click to collapse
:good: Can't thank you enough.
I have a second DNA that I have not been able to use.
Since Moonshine S-off I have not had any data connection. It has been very frustrating.
Followed your steps and now it's back up and running.
Awesome my friend, just awesome. Thank you.
quick question
santod040 said:
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Regarding the instructions you listed above, are these run from the phone or adb/fastboot? Going to perform this after work tonight and just wanted to be sure. Thank you!
LuckyPuppy said:
Regarding the instructions you listed above, are these run from the phone or adb/fastboot? Going to perform this after work tonight and just wanted to be sure. Thank you!
Click to expand...
Click to collapse
Flash stock based Rom --- Done from Recovery
Flash stock recovery --- Done from Fastboot
Perform a factory reset --- Done from Bootloader
:good:
how to
sdamark said:
Flash stock based Rom --- Done from Recovery
Flash stock recovery --- Done from Fastboot
Perform a factory reset --- Done from Bootloader
:good:
Click to expand...
Click to collapse
Awesome! Thank you so much!
Where is there a stock rom
thayl0 said:
Where is there a stock rom
Click to expand...
Click to collapse
> HTC Droid DNA > Droid DNA Android Development > [ROM] OTA-DNA-Sence 5-3.06.605.4 Stock Deodexed Debloated Rooted
This one will work fine. It's the one I used. Stock based ROM.
sdamark said:
> HTC Droid DNA > Droid DNA Android Development > [ROM] OTA-DNA-Sence 5-3.06.605.4 Stock Deodexed Debloated Rooted
This one will work fine. It's the one I used. Stock based ROM.
Click to expand...
Click to collapse
I figured that out after i commented.
when u go to flash your custom rom back to you need to do a dirty clean or can it be a clean flash by wiping cache system sdcard everything.
thayl0 said:
I figured that out after i commented.
when u go to flash your custom rom back to you need to do a dirty clean or can it be a clean flash by wiping cache system sdcard everything.
Click to expand...
Click to collapse
You'll have to install a custom recovery first. I use TWRP. Install your custom ROM onto the sd card. Boot into recovery, make a nandroid, wipe in recovery> Data, Cache, and Dalvic, then install your ROM and reboot.
sdamark said:
You'll have to install a custom recovery first. I use TWRP. Install your custom ROM onto the sd card. Boot into recovery, make a nandroid, wipe in recovery> Data, Cache, and Dalvic, then install your ROM and reboot.
Click to expand...
Click to collapse
why would i do a dirty install?
Have same issue, lost signal..
Flashed stock 3.06, but can't flash stock recovery.. every time i try to flash, it Fails
(sending 'recovery' (8188 KB).
OKAY [ 0.938s]
writing 'recovery'...
FAILED (remote: not allowed)
Same when i try to install other version of TWRP (have 2.5.0.0 installed) or CWM.
phone is not unlocked by htcdev, but i have s-off. (Can't unlock at htcdev through, getting error 160 every time)
Any help would be greatly appreciated
uNdea said:
Have same issue, lost signal..
Flashed stock 3.06, but can't flash stock recovery.. every time i try to flash, it Fails
(sending 'recovery' (8188 KB).
OKAY [ 0.938s]
writing 'recovery'...
FAILED (remote: not allowed)
Same when i try to install other version of TWRP (have 2.5.0.0 installed) or CWM.
phone is not unlocked by htcdev, but i have s-off. (Can't unlock at htcdev through, getting error 160 every time)
Any help would be greatly appreciated
Click to expand...
Click to collapse
You do know flashing 3.06 ruu makes it stock recovery. Not sure of you flashed a Rom or a ruu
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Edit: The official ATT 4.4.2 sbf has been released, and this rom was built from that.
This CWM/TWRP flashable zip is from the sbf of 165.44.1.ghost_att.ATT.en.US (ATT xt1058). The modem and kernel are within the zip and must be flashed manually. The instructions below are mostly for rooted, locked ATT phones using safestrap.
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
Unlocked phones: You can flash the zip and manually flash boot.img, NON-HLOS.bin and fsg.mbn.
ATT locked phones:
If you can still get root, then you can use safestrap to install this zip of ATT 4.4.2 /system and get root again. Also within the zip is the official ATT 4.4.2 boot.img, NON-HLOS.bin and fsg.mbn (for fastboot). This zip does not alter your bootloader.
Prerequisite:
Rooted Moto x
Have fastboot (motorola version for this phone) and PC drivers installed and working
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA..
Safestrap instructions:
root (thanks jcase)
install safestrap (thanks Hashcode and Team Win)
Make a nandroid and copy it off the phone!?
download zip to sdcard (motox-442-165.44.1.ghost_att-ss.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
extract boot.img, NON-HLOS.bin and fsg.mbn from the .zip to the fastboot directory of your PC
enter safestrap recovery (twrp) and activate the stock-slot
twrp: wipe/factory reset (WARNING. THIS WILL WIPE YOUR USERDATA. This step may be optional for some users.)
twrp: flash rom (motox-442-165.44.1.ghost_att-ss.zip) to the stock-slot (be patient)
twrp: immediately flash supersu .zip
twrp: reboot to bootloader (home -> reboot -> bootloader)
on pc: execute fastboot commands (below).
Fastboot commands: Note: If you use MotoWPNoMo, then you should skip "flash recovery"
Code:
fastboot flash boot boot.img
fastboot flash recovery boot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
Downloads:
motox-442-165.44.1.ghost_att-ss.zip: http://www.androidfilehost.com/?fid=23329332407589378
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
If you hang up during flashing the rom, I had success by flashing supersu first. Then it worked like a charm. Very helpful for me!
Sent from my XT1058 using Tapatalk
I was coming from 4.2.2 and flashing this without updating the modem to at least 4.4 will cause problems:
1. Security setting cannot be opened
2. User apps cannot be uninstalled
Updating my modem to 4.4 resolves both problem.
The sbf was released, and I made a new CWM/TWPR flashable zip using the sbf. The new zip contains the official 4.4.2 modem in addition to the kernel.
I tested the new zip on my phone, and the link is in the op.
Coming from 4.4 rooted I installed safestrap and followed these instructions. I had errors reported back with the following commands:
fastboot flash recovery boot.img
fastboot flash modem NON-HLOS.bin
but the phone is now on 4.4.2
rmead01 said:
Coming from 4.4 rooted I installed safestrap and followed these instructions. I had errors reported back with the following commands:
fastboot flash recovery boot.img
fastboot flash modem NON-HLOS.bin
but the phone is now on 4.4.2
Click to expand...
Click to collapse
What error did you get?
What kernel version are you running? Still running the 4.4 version?
I think the files are right. I just successfully compared those files in the zip against other copies, and they are the same copies working on my phone.
Ctrl-Freak said:
What error did you get?
What kernel version are you running? Still running the 4.4 version?
I think the files are right. I just successfully compared those files in the zip against other copies, and they are the same copies working on my phone.
Click to expand...
Click to collapse
kernel version reads "3.4.42-g27de6975 build from 2/24/14
the flash boot boot.img command went through no problem. It was just the recovery command that failed.
flash recovery boot.img - variable not supported preflash validation failed (remote failure)
trying the modem a second time it went through and I again flashed the fsg.mbn and erased the modemst1/2 and did a cache erase
rmead01 said:
kernel version reads "3.4.42-g27de6975 build from 2/24/14
the flash boot boot.img command went through no problem. It was just the recovery command that failed.
flash recovery boot.img - variable not supported preflash validation failed (remote failure)
trying the modem a second time it went through and I again flashed the fsg.mbn and erased the modemst1/2 and did a cache erase
Click to expand...
Click to collapse
Strange. I double checked it:
Code:
fastboot flash recovery boot.img
sending 'recovery' (10240 KB)...
OKAY [ 0.810s]
writing 'recovery'...
OKAY [ 1.713s]
finished. total time: 2.523s
You don't have the 4.4.2 bootoader do you? (Doesn't make sense that you would be doing this if you already had 4.4.2 + root.)
The kernel version is right.
Ctrl-Freak said:
Strange. I double checked it:
Code:
fastboot flash recovery boot.img
sending 'recovery' (10240 KB)...
OKAY [ 0.810s]
writing 'recovery'...
OKAY [ 1.713s]
finished. total time: 2.523s
You don't have the 4.4.2 bootoader do you? (Doesn't make sense that you would be doing this if you already had 4.4.2 + root.)
The kernel version is right.
Click to expand...
Click to collapse
Not sure. Bootloader version 30.B2
I had 4.4 rooted and downloaded the files in your post. Was I suppose to remove the the 3 files from the zip or just copy them out? I extracted them but left the 3 files also in the zip file. I copied the zip file to my sdcard. installed safestrap. made a nandroid. flash the zip, flashed the SU, followed the fastboot commands and that's what I got.
---------- Post added at 10:41 AM ---------- Previous post was at 10:26 AM ----------
Here's my input though. I'm on 4.4.2. I'm rooted. I have the 4.4.2 kernel version. My phone actually feels much snappier. Not sure if that's from the cache clear or not but it's extremely noticable how much smoother it is. I have safestrap installed and can reboot to it. All in all i'd call this a success
I think I get it. You are on the 4.4 bootloader which stops the recovery trick. But.. you've used MotoWPNoMo so the recovery is not necessary.
Sound right?
Glad it is working.
I'm new to using safestrap but having looked around I understand some of the basics of what I need to know.
however I may have misunderstood the safestrap instructions: is it necessary to install the rom in the stock slot? or can we install to another slot in order to preserve the stock slot for 'safety'
Ctrl-Freak said:
I think I get it. You are on the 4.4 bootloader which stops the recovery trick. But.. you've used MotoWPNoMo so the recovery is not necessary.
Sound right?
Glad it is working.
Click to expand...
Click to collapse
Exactly it! :good:
frenchie007 said:
I'm new to using safestrap but having looked around I understand some of the basics of what I need to know.
however I may have misunderstood the safestrap instructions: is it necessary to install the rom in the stock slot? or can we install to another slot in order to preserve the stock slot for 'safety'
Click to expand...
Click to collapse
Kitkat 4.4 does not work in a rom slot. I am guessing 4.4.2 is the same.
If you are running the 4.4 bootloader and MotoWPNoMo, you do not need to flash recovery. If you do try to flash recovery, just ignore the error.
I made a note in the op. Thanks rmead01.
Is this the AT&T equivalent of this: http://rootzwiki.com/topic/116025-romsafestrap-unlockedxt1060-stock-rooted-vzw-164552-kitkat-442/?
natezire71 said:
Is this the AT&T equivalent of this: http://rootzwiki.com/topic/116025-romsafestrap-unlockedxt1060-stock-rooted-vzw-164552-kitkat-442/?
Click to expand...
Click to collapse
Yes
I was running Android 4.4 already when doing this process. I skipped the step of wiping user data and followed the steps exactly. (I flashed SuperSU FIRST, then the ROM, then SuperSU again before rebooting to the bootloader. Maybe was unnecessary but wanted to be sure it got in there). I had no issues at all and when the bootloader commands were done I pressed the power to select reboot in the bootloader. Phone rebooted, optimized 327 apps, and I'm done. 4.4.2 running great with root and no loss of any data.
Major thumbs up for posting this!! Thank you and god bless XDA-developers!! This forum is invaluable!!!!
Oh I am on a locked bootloader by the way. AT&T locked but safestrap worked great.
Apollo_316 said:
... (I flashed SuperSU FIRST, then the ROM, then SuperSU again before rebooting to the bootloader. Maybe was unnecessary but wanted to be sure it got in there)...
Click to expand...
Click to collapse
I do not think flashing supersu first is helpful. When you flash the ROM, it erases /system, and all of the su binaries would be erased.
Ctrl-Freak said:
I do not think flashing supersu first is helpful. When you flash the ROM, it erases /system, and all of the su binaries would be erased.
Click to expand...
Click to collapse
I figured it was pointless but a previous poster in this thread said they did that too and my bottom line was ensuring I don't lose root above all else. Thanks for pointing that out though. I remember it was formatting /system for a while and I wondered about superSU being in there but wasn't sure what was going to happen.
I'm on rooted 4.4, AT&T locked bootloader, write protection off.
If I install this via safestrap, after this is installed and I'm on 4.4.2 rooted with write protection off, can I then remove safestrap while maintaining my rooted, write protect off, 4.4.2 update?
Sent from my XT1058 using XDA Premium 4 mobile app
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