Hi guys,
I own a DNA and I use it overseas (not in the U.S.) via GSM only, obviously.
Whenever I enter the Software Updates menu to check for the OTA update, I get this message: "software update only work in CDMA mode".
Is there any way around it?
Cheers!
You have s off?
Sent from my HTC6435LVW using xda app-developers app
indeed..
My device is rooted+debloated+s-offed (no custom ROM installed).
Bigandrewgold said:
You have s off?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
would this work for him?
Code:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot oem boot
.torrented said:
would this work for him?
Code:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot oem boot
Click to expand...
Click to collapse
Maybe, here's what I would do.
First, flash the updated radios. There's a thread somewhere around on how to do this.
Next, you need to decide if you want the stock Rom and kernel from the update, or if you want custom ones. If you want custom ones then you are now done(assuming you want to keep the ones you already had), if you want the stock ones the go here and install the stock ones. You could also install one of the handful of roms that are based in the ota.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Maybe, here's what I would do.
First, flash the updated radios. There's a thread somewhere around on how to do this.
Next, you need to decide if you want the stock Rom and kernel from the update, or if you want custom ones. If you want custom ones then you are now done(assuming you want to keep the ones you already had), if you want the stock ones the go here and install the stock ones. You could also install one of the handful of roms that are based in the ota.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Hi,
First of all thanks for the quick response.
Second, I want to avoid flashing an entire ROM (and thus wiping my data and such).
Is there any way to just install the OTA without re-installing a complete ROM?
desheh said:
Hi,
First of all thanks for the quick response.
Second, I want to avoid flashing an entire ROM (and thus wiping my data and such).
Is there any way to just install the OTA without re-installing a complete ROM?
Click to expand...
Click to collapse
this is what you can try (I don't know if it will work)
I would just wait for a Dev to make a flashable (user firendly) zip
Download the OTAPkg.zip (Its floating around in the Development Section)
Code:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip OTAPkg.zip
fastboot oem boot
.torrented said:
this is what you can try (I don't know if it will work)
I would just wait for a Dev to make a flashable (user firendly) zip
Download the OTAPkg.zip (Its floating around in the Development Section)
Code:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip OTAPkg.zip
fastboot oem boot
Click to expand...
Click to collapse
Haven't tried it yet (don't like being a guinea pig )..
And news as to how to receive the OTA without flashing an entire ROM..?
Cheers..
Related
I realize that there are tons of threads about this but I haven't been able to find any that match my setup.
So I S-OFF'd while running the gb firmware, now I want to update to the ics ota firmware so I can run cm9. My question is that do I need to change my hboot after running the ruu, and if so how do I do that? I know these are probably simple questions but I just want to make sure I don't brick my only phone.
Sent from my ADR6425LVW using xda app-developers app
Without having to do the full ruu get these files listed from here http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/
[ICS][2.25][JB][5-7]PH98IMG.zip - This is radio/pateched hboot combo
&
PH98IMGSTOCKREC.zip This is stock recovery
Updated the radio/hboot with that combo. Then once completed flash the stock recovery and then do a factory reset. Once completed go back into hboot, reflash custom recovery. Then in your custom recovery wipe data/cache then choose your rom.
Snuzzo said:
Updated the radio/hboot with that combo.
Click to expand...
Click to collapse
I do that by renaming it to PH98IMG.zip correct? And I flash the stock recovery by renaming that PH98IMG.zip as well right?
magicnanners said:
I do that by renaming it to PH98IMG.zip correct? And I flash the stock recovery by renaming that PH98IMG.zip as well right?
Click to expand...
Click to collapse
Stock recovery, you can do that or extract it out and fastboot flash. The radio/hboot will need to be renamed.
Snuzzo said:
Stock recovery, you can do that or extract it out and fastboot flash. The radio/hboot will need to be renamed.
Click to expand...
Click to collapse
Awesome thanks I might wait until tomorrow to start all of this because if I don't finish tonight I won't have a phone in the morning lol. But thank you for your help I really appreciate it
magicnanners said:
I realize that there are tons of threads about this but I haven't been able to find any that match my setup.
So I S-OFF'd while running the gb firmware, now I want to update to the ics ota firmware so I can run cm9. My question is that do I need to change my hboot after running the ruu, and if so how do I do that? I know these are probably simple questions but I just want to make sure I don't brick my only phone.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Simple answer would be ....if you are soff. And fastboot is properly setup, then type fast boot OEM lock when you are in fast boot mode. It will lock and reboot. Pull battery. Boot back into bootloader (assuming you have a stock boot loader) and run the latest ics ruu exe. Then once it boots. Enable adb debbuging. Disable quickboot in power setting. Pull battery. Go back to fast boot. HTC dev unlock. You should already still have the unlock token on your pc. Unlock the bootloader. Then fastboot the recovery. Go to the recovery ( I like amon ra) and flash super user. Then reboot...or flash your Rom. All done.
stkiswr said:
Simple answer would be ....if you are soff. And fastboot is properly setup, then type fast boot OEM lock when you are in fast boot mode. It will lock and reboot. Pull battery. Boot back into bootloader (assuming you have a stock boot loader) and run the latest ics ruu exe. Then once it boots. Enable adb debbuging. Disable quickboot in power setting. Pull battery. Go back to fast boot. HTC dev unlock. You should already still have the unlock token on your pc. Unlock the bootloader. Then fastboot the recovery. Go to the recovery ( I like amon ra) and flash super user. Then reboot...or flash your Rom. All done.
Click to expand...
Click to collapse
You don't need to OEM Lock if you're S-Off.
darkghost568 said:
You don't need to OEM Lock if you're S-Off.
Click to expand...
Click to collapse
I'm sorry. I did that and forgot lol. Hell if your s off you can pretty much do what ever.
stkiswr said:
I'm sorry. I did that and forgot lol. Hell if your s off you can pretty much do what ever.
Click to expand...
Click to collapse
Ikr
So I decided to be the lab rat and took the update and tried unlocking bootloader and I confirmed this myself I am unlocking and about to flash kernel and root tools I will post in a few minutes wish results
t1gartist said:
So I decided to be the lab rat and took the update and tried unlocking bootloader and I confirmed this myself I am unlocking and about to flash kernel and root tools I will post in a few minutes wish results
Click to expand...
Click to collapse
It can all be done. did it earlier. all is still good.
I just did the same thing. I updated the firmware going back to stock via RUU and accepting the OTA Update, and re-flashing my original Unlock_code.bin. Now running ViperDNA 1.1.2 with the new firmware just fine.
You do know that since u flashed the venom Rom your back to old firmware?
Check your update the Verizon one will be there again. I did the same thing. Decided to stay stock until venom is updated.
Sent from my HTC6435LVW using xda premium
does anyone know if I flash the current system write kernel, will it undo any of the new update from the OTA?
Not entirely sure, the update flashes a new boot.img, try it and see. U can always revert. It won't hurt anything.
Sent from my HTC6435LVW using xda premium
cmay227 said:
You do know that since u flashed the venom Rom your back to old firmware?
Check your update the Verizon one will be there again. I did the same thing. Decided to stay stock until venom is updated.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Not entirely. I don't have the Rom portion of the new update, but the radio firmware and other portions of the update are still there (the underlying framework). But yeah, I'm not making full use of it until I use a 2.04-based ROM.
sadly i tried 10 times last night it would unlock until rebooted and i would be showed locked again to im not sure what the hell
cmay227 said:
Not entirely sure, the update flashes a new boot.img, try it and see. U can always revert. It won't hurt anything.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
tried flashing the system write kernel, and all hell breaks loose. Its gonna take some time for the dev to incorporate all the changes.
Flashed back to RUU for now.
t1gartist said:
sadly i tried 10 times last night it would unlock until rebooted and i would be showed locked again to im not sure what the hell
Click to expand...
Click to collapse
Are you certain it wasn't 9 times or 11 times?
Turn phone off all the way. Then boot into bootloader and run unlock.bin command.
Sent from my HTC6435LVW using xda premium
Backing up my internal memory guess I'll give it a go what the heck its Friday right?
binzokun said:
tried flashing the system write kernel, and all hell breaks loose. Its gonna take some time for the dev to incorporate all the changes.
Flashed back to RUU for now.
Click to expand...
Click to collapse
Custom kernels won't work on the update?
Here are the steps I took YMMV
Backup Internal Memory
Verify Fastboot and ADB Drivers are properly installed
Boot into Bootloader
RUN "fastboot OEM Lock"
Phone reboots
Run RUU as Administrator
Wait
Boot Device
Connect to WiFi
Run Software Update from Settings
Wait
Install Update
Checked for Updates Again (Nothing)
Copy Unlock_Code.bin to your fastboot directory
ADB Reboot Bootloader
Open command prompt from fastboot directly
Run "fastboot unlock token Unlock_code.bin"
Follow the prompts
Reboot bootloader verify unlocked
Place Recovery.img in fastboot directory
RUN "fastboot flash recovery recovery.img"
Reboot
Copy over Rooted ROM
Reboot into Recovery and flash
Profit
zone23 said:
Here are the steps I took YMMV
Backup Internal Memory
Verify Fastboot and ADB Drivers are properly installed
Boot into Bootloader
RUN "fastboot OEM Lock"
Phone reboots
Run RUU as Administrator
Wait
Boot Device
Connect to WiFi
Run Software Update from Settings
Wait
Install Update
Checked for Updates Again (Nothing)
Copy Unlock_Code.bin to your fastboot directory
ADB Reboot Bootloader
Open command prompt from fastboot directly
Run "fastboot unlock token Unlock_code.bin"
Follow the prompts
Reboot bootloader verify unlocked
Place Recovery.img in fastboot directory
RUN "fastboot flash recovery recovery.img"
Reboot
Copy over Rooted ROM
Reboot into Recovery and flash
Profit
Click to expand...
Click to collapse
Sorry for the noobish question, but will I have to go through such a complex procedure as this if I'm on stock rom, unlocked and rooted? Rooting alone the first time was quite time consuming for me :\
I know I could simply stick with what I have now. I'd really like to have the new firmware though, which supposedly fixes audio and wifi issues.
supertoast92 said:
Sorry for the noobish question, but will I have to go through such a complex procedure as this if I'm on stock rom, unlocked and rooted? Rooting alone the first time was quite time consuming for me :\
Click to expand...
Click to collapse
My suggestion then would be to wait and see if someone comes up with a way to flash the radios. That is the only reason I went through the process.
If I have a backup of stock rooted, do I still have to use RUU?
Will do, thanks!
Word of caution people, once you install the OTA update, your HBoot get updated, so the current RUU stops working. Once you apply the update, there's no going back. All custom kernels don't work, I spend all night trying all of them, the phone just stuck at the boot animation.
I would suggest holding out until all the kernels/custom roms/RUUs are updated, cause if anything goes wrong you have very little tools to work with, especially when we don't have S-Off.
That's good to know. Thank you!
Sent from my HTC DNA
This is my first post,so go easy.
I rooted,S-off,and SuperCID my HTC One and have been running CLEANRom 4.0 and love it, but now that 5.0 is here I would like to upgrade my firmware from 2.24.401.1 to the newest firmware before flashing 5.0. I also messed up and never made a nandroid of stock so going back to that is going to be difficult. Is there any way that I can update without returning phone to stock.
What would the process be to get this thing done?
I have also downloaded the 1.26.502.15 if that is any help.
bloodedemon said:
This is my first post,so go easy.
I rooted,S-off,and SuperCID my HTC One and have been running CLEANRom 4.0 and love it, but now that 5.0 is here I would like to upgrade my firmware from 2.24.401.1 to the newest firmware before flashing 5.0. I also messed up and never made a nandroid of stock so going back to that is going to be difficult. Is there any way that I can update without returning phone to stock.
What would the process be to get this thing done?
I have also downloaded the 1.26.502.15 if that is any help.
Click to expand...
Click to collapse
No need to revert to stock in order to install updated ROM. Firmware updates are optional but recommended.
Download a custom firmware file and flash in RUU mode.
Sent from my HTC One using xda app-developers app
ilal2ielli said:
No need to revert to stock in order to install updated ROM. Firmware updates are optional but recommended.
Download a custom firmware file and flash in RUU mode.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Ah, this is good! :laugh:
Thanks for the reply!
Now all I need to know is what RUU mode is and how do I get it going on my phone before I install this thing?
Go to the international section and there are guides on how to do it, I suggest looking there
Sent from my HTC One using Tapatalk 4
Thanks guys! Gonna start looking now. If you can remember any threads that will help please give me a link when you have time!
Sent from my HTC One using xda premium
bloodedemon said:
Thanks guys! Gonna start looking now. If you can remember any threads that will help please give me a link when you have time!
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
This should get you the newest ota radio and firmware for att.
http://forum.xda-developers.com/showpost.php?p=44260480&postcount=95
S.Reno9 said:
This should get you the newest ota radio and firmware for att.
http://forum.xda-developers.com/showpost.php?p=44260480&postcount=95
Click to expand...
Click to collapse
Thanks man. Now the thread says that you have to be s off before this. Will this return me to stock? Will i have to do S-off and superCID again and root as well?
bloodedemon said:
Thanks man. Now the thread says that you have to be s off before this. Will this return me to stock? Will i have to do S-off and superCID again and root as well?
Click to expand...
Click to collapse
No, this wont touch any of that...it is just firmware zip with radio, so wont touch your rom. And you cant lose s-off or supercid, unless you manual type in the commands to change them.... but I read somwhere its good to reflash whatever rom you are currently running, after updating firmware. But may not be necessary.....
S.Reno9 said:
No, this wont touch any of that...it is just firmware zip with radio, so wont touch your rom. And you cant lose s-off or supercid, unless you manual type in the commands to change them.... but I read somewhere its good to re-flash whatever rom you are currently running, after updating firmware. But may not be necessary.....
Click to expand...
Click to collapse
So the process is something like this:
1 Hook phone to computer
2 Put phone in fastboot
3 Run .exe file in the zip you download
enjoy?
Or am i missing a step in there? I keep seeing people re-lock the bootloader. Is that something that needs to happen?
I also downloaded one of these zips and it didn't have a exe file? was that one for side-loading?
bloodedemon said:
So the process is something like this:
1 Hook phone to computer
2 Put phone in fastboot
3 Run .exe file in the zip you download
enjoy?
Or am i missing a step in there? I keep seeing people re-lock the bootloader. Is that something that needs to happen?
I also downloaded one of these zips and it didn't have a exe file? was that one for side-loading?
Click to expand...
Click to collapse
Relock is necessary if not superCID.
Command is fastboot oem rebootRUU
Zip file is for flashing using fastboot. Go to RUU mode, then enter fastboot flash zip "zip name"
Sent from my HTC One using xda app-developers app
ilal2ielli said:
Relock is necessary if not superCID.
Command is fastboot oem rebootRUU
Zip file is for flashing using fastboot. Go to RUU mode, then enter fastboot flash zip "zip name"
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
For the firmware link I posted above, there is no need to be superCID, as long as you have the CID listed in that post.
Also not so sure about needing to relock....following the instructions here, I had no problems.
I have an AT&T HOX+ running stock. It's unlocked via HTC and rooted. I cannot download any OTAs. I learned the hard way that you cannot download OTAs if you have any stock apps disabled so I've re-enabled them. Now it goes through the motions and finds the update, but when I connect to Wifi all I see is a blank message as seen in the attached screenshot.
Nilpo said:
I have an AT&T HOX+ running stock. It's unlocked via HTC and rooted. I cannot download any OTAs. I learned the hard way that you cannot download OTAs if you have any stock apps disabled so I've re-enabled them. Now it goes through the motions and finds the update, but when I connect to Wifi all I see is a blank message as seen in the attached screenshot.
Click to expand...
Click to collapse
Maybe Unroot and try.......
You must first flash the stock recovery and then relock bootloader using the command "fastboot oem lock" in fastboot. The stock recovery.img can be flashed using the fastboot command "fastboot flash recovery recovery.img" where "recovery.img" is replaced with whatever your recovery name is and .img. Make sure you flash the recovery before relocking. Root should not mess up the update although you will lose root after the update. I updated while the device was still rooted!
Sent from my HTC One X+ using xda developers app
[email protected] said:
Maybe Unroot and try.......
Click to expand...
Click to collapse
Is there a way to unroot without losing data? I haven't found one yet.
ryandroid226 said:
You must first flash the stock recovery and then relock bootloader using the command "fastboot oem lock" in fastboot. The stock recovery.img can be flashed using the fastboot command "fastboot flash recovery recovery.img" where "recovery.img" is replaced with whatever your recovery name is and .img. Make sure you flash the recovery before relocking. Root should not mess up the update although you will lose root after the update. I updated while the device was still rooted!
Sent from my HTC One X+ using xda developers app
Click to expand...
Click to collapse
So there's no way to update and run a custom recovery? If I have to relock the bootloader, I can't unlock again without factory wiping.
Why can't HTC just get the bluetooth right from the start? How did they even release a phone when BT doesn't work?
Nilpo said:
Is there a way to unroot without losing data? I haven't found one yet.
Click to expand...
Click to collapse
It's not the unrooting that will cause you to lose any data or other content on your device. It is the re-unlocking of the bootloader or the running of a RUU. AFAIK, there is no way to keep your device contents while you update the radio and hboot. The only option is to backup contents of SD, backup apps using Google or TiBU, and backup sms and call log. I may be wrong but I'm pretty sure this is how it goes. With that being said, it is not mandatory that you upgrade the radio/hboot in order to install a ROM that is sense 5/JB 4.2.2. There are already ROM's out there for AT&T built on this base
Sent from my HTC One X+ using xda developers app
Nilpo said:
Is there a way to unroot without losing data? I haven't found one yet.
Click to expand...
Click to collapse
Yeah u can unroot using SuperSU App itself from the setting choose Full Unroot........
Unintsall all the root Apps too since it unnecessary to have then without root.......
Flash the Stock recovery and relock the bootloader and then check for updates.....:good:
ryandroid226 said:
It's not the unrooting that will cause you to lose any data or other content on your device. It is the re-unlocking of the bootloader or the running of a RUU. AFAIK, there is no way to keep your device contents while you update the radio and hboot. The only option is to backup contents of SD, backup apps using Google or TiBU, and backup sms and call log. I may be wrong but I'm pretty sure this is how it goes. With that being said, it is not mandatory that you upgrade the radio/hboot in order to install a ROM that is sense 5/JB 4.2.2. There are already ROM's out there for AT&T built on this base
Sent from my HTC One X+ using xda developers app
Click to expand...
Click to collapse
If I unroot and install the OTA, and then unlock the bootloader again, with it keep the updated firmware or drop back to factory?
If I'm going through all this trouble, maybe I should be looking at a custom ROM. Any suggestions for a Sense 5 one built on AT&T? I haven't seen one for this phone.
Nilpo said:
If I unroot and install the OTA, and then unlock the bootloader again, with it keep the updated firmware or drop back to factory?
If I'm going through all this trouble, maybe I should be looking at a custom ROM. Any suggestions for a Sense 5 one built on AT&T? I haven't seen one for this phone.
Click to expand...
Click to collapse
The unlocking will wipe ur Storage.....but u ll have the update of 4.2.2..
there are few Custom ROMS with Sense 5 u can go through this Forum
Nilpo said:
If I unroot and install the OTA, and then unlock the bootloader again, with it keep the updated firmware or drop back to factory?
If I'm going through all this trouble, maybe I should be looking at a custom ROM. Any suggestions for a Sense 5 one built on AT&T? I haven't seen one for this phone.
Click to expand...
Click to collapse
If you update via the OTA then your factory firmware WILL be updated. Maybe you can request that a dev make a ROM that is stock and rooted sense5/JB 4.2.2, you might grab the interest of someone.. That way you could have a "stock" image of the ROM and avoid the radio/hboot upgrade. Otherwise, you will just have to go through the update process, wiping your device. IMO, backing everything up is not too painstaking and it is a good practice to do this periodically anyways. Just my .02!
Sent from my HTC One X+ using xda app-developers app
Backing up isn't too difficult on JB. I've done it manually as well as with Helium and other apps throughout the rooting/experimenting process. It's been my experience that those app backups don't restore properly and I'm left starting over anyway. The issues could be app specific, but I honestly don't remember which apps didn't work now.
Of course, I suppose it's all a small price to pay to have a phone that actually works when I connect my BT headset.
Where does one find the stock recovery?
I hope this isn't silly, but I've been running custom recovery forever and I'm blanking as to where to locate/d-load the stock recovery.
thanks!
mrbillishere said:
Where does one find the stock recovery?
I hope this isn't silly, but I've been running custom recovery forever and I'm blanking as to where to locate/d-load the stock recovery.
thanks!
Click to expand...
Click to collapse
Not sill at all. I have an image that I believe is the stock recovery, but how can I be sure?
Nilpo said:
Not sill at all. I have an image that I believe is the stock recovery, but how can I be sure?
Click to expand...
Click to collapse
OK, well after dusting off the cobwebs and reading some threads for the Intl version I learned this... the stock firmware will also contain the radios and stock recovery. So now I'm looking for the correct firmware to match my phone's CID and Modelid. The command to dump these variables out is 'fastboot getvar all'
My AT&T OneX+ reported this:
(bootloader) modelid: PM6310000
(bootloader) cidnum: CWS__001
There's a txt file in the firmware.zip that will contain a list of the applicable CID numbers the firmware can apply to. Evidently since our phones are S-on an entry in the list must correspond to the device's reported CID.
So now I'm searching for an updated firmware.zip
You can find the stock rom here as found in this thread.
Software version 1.54.1540.9 w/Extreme Power Saving... Uploading ota now for folks who need or want it
https://drive.google.com/file/d/0Bx5-C2BrwNVxdjY2WVVsdXBIUzA/edit?usp=sharing
Wonders_Never_Cease said:
Software version 1.54.1540.9 w/Extreme Power Saving... Uploading ota now for folks who need or want it
https://drive.google.com/file/d/0Bx5-C2BrwNVxdjY2WVVsdXBIUzA/edit?usp=sharing
Click to expand...
Click to collapse
Thanks! I hope I can extract the firmware.zip out of this and RUU mode flash it on my Dev. I only want the updated firmware.
All you have to do after download is pull it outta the ota and flash it as you would any other firmware
Wonders_Never_Cease said:
All you have to do after download is pull it outta the ota and flash it as you would any other firmware
Click to expand...
Click to collapse
That's what I thought too, but now i'm hard bricked!!! :crying:
I used fastboot oem rebootRUU and then fastboot flash zip firmware.zip
I updated the firmware in my M7 a few times using this method without incident, but my M8 is now dead...
what was your cid? this was only for developer builds I redid my device twice with it...flashed a complete nand back up and then this ota through stock recovery... did you do the firmware upgrade to 1.54 euro? or any other firmware related flashes?
1 fastboot oem writecid BS_US001
2 fastboot oem readcid
3 fastboot reboot-bootloader
4 fastboot oem rebootRUU
5 fastboot flash zip nameofzip.zip
6 fastboot reboot-bootloader
guyd said:
That's what I thought too, but now i'm hard bricked!!! :crying:
I used fastboot oem rebootRUU and then fastboot flash zip firmware.zip
I updated the firmware in my M7 a few times using this method without incident, but my M8 is now dead...
Click to expand...
Click to collapse
Are you not super cid? When you say hard bricked what is your m8 doing now? Can you get to bootloader. You can't even flash unless you are soff or have true developer edition phone so I would assume you made your phone super cid too?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Wonders_Never_Cease said:
what was your cid? this was only for developer builds I redid my device twice with it...flashed a complete nand back up and then this ota through stock recovery... did you do the firmware upgrade to 1.54 euro? or any other firmware related flashes?
1 fastboot oem writecid BS_US001
2 fastboot oem readcid
3 fastboot reboot-bootloader
4 fastboot oem rebootRUU
5 fastboot flash zip nameofzip.zip
6 fastboot reboot-bootloader
Click to expand...
Click to collapse
CID was BS_US002 on a Developer Edition. No firmware upgrades, it was original!!!
I was S-OFF with custom ROM, custom Kernel, and custom Recovery. That's it.
I removed the boot.img and recovery.img out of the zip prior to flashing.
The flash process appeared to work, and nearly all pieces installed successfully.
But after I issued a fastboot reboot, it was dead! No screen, no led, no nothing.
Computer doesn't see it as a device, thus adb or fastboot no longer work.
My first hard brick ever, and I hope my last!
guyd said:
CID was BS_US002 on a Developer Edition. No firmware upgrades, it was original!!!
I was S-OFF with custom ROM, custom Kernel, and custom Recovery. That's it.
I removed the boot.img and recovery.img out of the zip prior to flashing.
The flash process appeared to work, and nearly all pieces installed successfully.
But after I issued a fastboot reboot, it was dead! No screen, no led, no nothing.
Computer doesn't see it as a device, thus adb or fastboot no longer work.
My first hard brick ever, and I hope my last!
Click to expand...
Click to collapse
Hate to hear that. I'm sure you have already tried this but just in case you haven't. Vol up and power for 10 sec then immediately vol down and power for 5 seconds. Even if you don't see bootloader try fastboot command. Try with and without phone plugged in.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Well sorry to hear this,probably reason it borked your device is it needs the stock recovery i think to finish flashing,didnt look at [email protected] but that would be my guess...I always flash stock recovery before flashing an ruu or firmware zip.
guyd said:
CID was BS_US002 on a Developer Edition. No firmware upgrades, it was original!!!
I was S-OFF with custom ROM, custom Kernel, and custom Recovery. That's it.
I removed the boot.img and recovery.img out of the zip prior to flashing.
The flash process appeared to work, and nearly all pieces installed successfully.
But after I issued a fastboot reboot, it was dead! No screen, no led, no nothing.
Computer doesn't see it as a device, thus adb or fastboot no longer work.
My first hard brick ever, and I hope my last!
Click to expand...
Click to collapse
an0ther said:
Hate to hear that. I'm sure you have already tried this but just in case you haven't. Vol up and power for 10 sec then immediately vol down and power for 5 seconds. Even if you don't see bootloader try fastboot command. Try with and without phone plugged in
Click to expand...
Click to collapse
Tried those like fifty times! My device is is bricked harder than a diamond...
Wish I knew what exactly happened so I don't do it again. As I said in my previous post, I've done this same thing on my M7 several times without a hitch. Only difference I saw this time was that the RUU flash routine didn't stop after flashing the hboot like it did on my M7 and make me run it one more time to get the rest of the firmware flashed. To be sure I got it all, I flashed it a second time anyway. That was the only difference I saw!
---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------
Wonders_Never_Cease said:
Well sorry to hear this,probably reason it borked your device is it needs the stock recovery i think to finish flashing,didnt look at [email protected] but that would be my guess...I always flash stock recovery before flashing an ruu or firmware zip.
Click to expand...
Click to collapse
I've ran the RUU flash command on my M7 with a custom recovery several times without incident. Didn't see why it would be any different on the M8, but something is. Wish I would have had an MD5 to verify my download, but it extracted fine so I think it was good.
Only one thing I found that was different from the M7 to the M8.
In the M7 it used hbootpreupdate:3
In the M8 it used hbootpreupdate:12
Wish I knew what this does different.
how did you remove the boot and recovery out of zip? Mine says corrupted when i try to unzip which usually means its encrypted. If you just manually zipped it back up that could be the problem. I don't know what happened and am interested to figure out. At least it is just dead and htc should swap it out no problem.
I'm curious. Sorry if this a silly question, I'm still new to all of this...
Wonders_Never_Cease, So I should flash back to the recoverydevm8.img you provided previously in the A_T_T_Test_1_12_1540_17_ISIS ROM you created first?
Thanks.
Safest way I would suggest is do a restore of a nand backup to completely stock developer build including recovery(1.12.1540.17) and then flash this via stock recovery if you havent gotten the notification after you revert to everything stock...You do not need to relock bootloader if s-off'd...as long as everything else is stock itll flash just fine...Hope this answered your questions about flashing this file.
skhullar said:
I'm curious. Sorry if this a silly question, I'm still new to all of this...
Wonders_Never_Cease, So I should flash back to the recoverydevm8.img you provided previously in the A_T_T_Test_1_12_1540_17_ISIS ROM you created first?
Thanks.
Click to expand...
Click to collapse
Thanks for the guidance.
Lets say a newbie, in his infinite wisdom excitedly rushed to apply a great ROM and failed to create a nand backup of his stock setup... Where would such a bonehead be able to get his hands on a complete nand backup of the stock developer build?
Wonders_Never_Cease said:
Safest way I would suggest is do a restore of a nand backup to completely stock developer build including recovery(1.12.1540.17) and then flash this via stock recovery if you havent gotten the notification after you revert to everything stock...You do not need to relock bootloader if s-off'd...as long as everything else is stock itll flash just fine...Hope this answered your questions about flashing this file.
Click to expand...
Click to collapse
skhullar said:
I'm curious. Sorry if this a silly question, I'm still new to all of this...
Wonders_Never_Cease, So I should flash back to the recoverydevm8.img you provided previously in the A_T_T_Test_1_12_1540_17_ISIS ROM you created first?
Thanks.
Click to expand...
Click to collapse
I would suggest you make your phone super cid before you do any flashing.
Hes already running my rom....Not needed,using brightstar cid works fine as att and developer builds are same mid
an0ther said:
I would suggest you make your phone super cid before you do any flashing.
Click to expand...
Click to collapse
Ill send you a link in the a.m.,lol
skhullar said:
Thanks for the guidance.
Lets say a newbie, in his infinite wisdom excitedly rushed to apply a great ROM and failed to create a nand backup of his stock setup... Where would such a bonehead be able to get his hands on a complete nand backup of the stock developer build?
Click to expand...
Click to collapse
Link and instructions sent...Enjoy
Thank You!
Wonders_Never_Cease said:
Link and instructions sent...Enjoy
Click to expand...
Click to collapse
So no definite way to convert to Dev Edition then I'm guessing, right?