Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,805,313 Members 49,346 Now Online
XDA Developers Android and Mobile Development Forum

Developer Edition Updated

Tip us?
 
Wonders_Never_Cease
Old
(Last edited by Wonders_Never_Cease; 5th May 2014 at 05:56 PM.)
#1  
Senior Member - OP
Thanks Meter 496
Posts: 1,074
Join Date: Jul 2013

 
DONATE TO ME
Default Developer Edition Updated

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...it?usp=sharing
The Following 6 Users Say Thank You to Wonders_Never_Cease For This Useful Post: [ Click to Expand ]
 
guyd
Old
#2  
guyd's Avatar
Senior Member
Thanks Meter 270
Posts: 675
Join Date: Feb 2011
Location: Indianapolis
Quote:
Originally Posted by Wonders_Never_Cease View Post
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...it?usp=sharing
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.
 
Code:

  Phone: HTC One M8 (at&t)       Tablet: Nexus 7 (2013)
  ROM: ViperOne M8 1.8.0         ROM: AOKP 4.4.3 (06/14)
  Kernel: Elemental-X 0.18       Kernel: Elemental-X 2.13
  Recovery: TWRP 2.7.1.0         Recovery: TWRP 2.7.1.1
  Radio: 1.19.213311491.A22G     Bootloader: 4.0.2
 
Wonders_Never_Cease
Old
#3  
Senior Member - OP
Thanks Meter 496
Posts: 1,074
Join Date: Jul 2013

 
DONATE TO ME
All you have to do after download is pull it outta the ota and flash it as you would any other firmware
 
guyd
Old
#4  
guyd's Avatar
Senior Member
Thanks Meter 270
Posts: 675
Join Date: Feb 2011
Location: Indianapolis
Quote:
Originally Posted by Wonders_Never_Cease View Post
All you have to do after download is pull it outta the ota and flash it as you would any other firmware
That's what I thought too, but now i'm hard bricked!!!

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...
 
Code:

  Phone: HTC One M8 (at&t)       Tablet: Nexus 7 (2013)
  ROM: ViperOne M8 1.8.0         ROM: AOKP 4.4.3 (06/14)
  Kernel: Elemental-X 0.18       Kernel: Elemental-X 2.13
  Recovery: TWRP 2.7.1.0         Recovery: TWRP 2.7.1.1
  Radio: 1.19.213311491.A22G     Bootloader: 4.0.2
 
Wonders_Never_Cease
Old
#5  
Senior Member - OP
Thanks Meter 496
Posts: 1,074
Join Date: Jul 2013

 
DONATE TO ME
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
 
an0ther
Old
#6  
an0ther's Avatar
Senior Member
Thanks Meter 191
Posts: 584
Join Date: Sep 2013
Quote:
Originally Posted by guyd View Post
That's what I thought too, but now i'm hard bricked!!!

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...
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
 
guyd
Old
#7  
guyd's Avatar
Senior Member
Thanks Meter 270
Posts: 675
Join Date: Feb 2011
Location: Indianapolis
Quote:
Originally Posted by Wonders_Never_Cease View Post
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
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!
 
Code:

  Phone: HTC One M8 (at&t)       Tablet: Nexus 7 (2013)
  ROM: ViperOne M8 1.8.0         ROM: AOKP 4.4.3 (06/14)
  Kernel: Elemental-X 0.18       Kernel: Elemental-X 2.13
  Recovery: TWRP 2.7.1.0         Recovery: TWRP 2.7.1.1
  Radio: 1.19.213311491.A22G     Bootloader: 4.0.2
 
an0ther
Old
(Last edited by an0ther; 4th May 2014 at 05:04 AM.)
#8  
an0ther's Avatar
Senior Member
Thanks Meter 191
Posts: 584
Join Date: Sep 2013
Quote:
Originally Posted by guyd View Post
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!
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
 
Wonders_Never_Cease
Old
#9  
Senior Member - OP
Thanks Meter 496
Posts: 1,074
Join Date: Jul 2013

 
DONATE TO ME
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 it@scriptong but that would be my guess...I always flash stock recovery before flashing an ruu or firmware zip.

Quote:
Originally Posted by guyd View Post
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
Old
(Last edited by guyd; 4th May 2014 at 02:20 PM.)
#10  
guyd's Avatar
Senior Member
Thanks Meter 270
Posts: 675
Join Date: Feb 2011
Location: Indianapolis
Quote:
Originally Posted by an0ther View Post
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
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 ----------

Quote:
Originally Posted by Wonders_Never_Cease View Post
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 it@scriptong but that would be my guess...I always flash stock recovery before flashing an ruu or firmware zip.
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.
 
Code:

  Phone: HTC One M8 (at&t)       Tablet: Nexus 7 (2013)
  ROM: ViperOne M8 1.8.0         ROM: AOKP 4.4.3 (06/14)
  Kernel: Elemental-X 0.18       Kernel: Elemental-X 2.13
  Recovery: TWRP 2.7.1.0         Recovery: TWRP 2.7.1.1
  Radio: 1.19.213311491.A22G     Bootloader: 4.0.2

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes