Post Reply

Convert AT&T HTC One M8 to Developer Edition?

OP NextNexus

21st May 2014, 05:35 PM   |  #1  
OP Senior Member
Thanks Meter: 118
 
464 posts
Join Date:Joined: Jan 2007
Does anyone know if it's possible to convert the HTC One M8 to a developer edition version? I've tried searching online and see that it was a possibility on last year's M7 but can't find anything specifically about the M8. Thanks.
The Following User Says Thank You to NextNexus For This Useful Post: [ View ]
21st May 2014, 07:33 PM   |  #2  
garyd9's Avatar
Recognized Developer
Flag Pittsburgh, PA
Thanks Meter: 2,210
 
2,105 posts
Join Date:Joined: Sep 2006
Quote:
Originally Posted by NextNexus

Does anyone know if it's possible to convert the HTC One M8 to a developer edition version? I've tried searching online and see that it was a possibility on last year's M7 but can't find anything specifically about the M8. Thanks.

Yes, it's possible.
The Following 2 Users Say Thank You to garyd9 For This Useful Post: [ View ]
21st May 2014, 07:35 PM   |  #3  
OP Senior Member
Thanks Meter: 118
 
464 posts
Join Date:Joined: Jan 2007
Quote:
Originally Posted by garyd9

Yes, it's possible.

Thanks. Can you provide more detail on how to accomplish this or refer me to a thread that has that info?
21st May 2014, 07:43 PM   |  #4  
garyd9's Avatar
Recognized Developer
Flag Pittsburgh, PA
Thanks Meter: 2,210
 
2,105 posts
Join Date:Joined: Sep 2006
Quote:
Originally Posted by garyd9

Yes, it's possible.

I guess you want some details, huh?

You'll need to get a Developer Edition stock recovery and a Developer Edition nandroid backup. (I'm lazy, so will just use "DevEd" instead of Developer edition.)

To get BOTH of these things, hop on over to a thread in the non-carrier specific M8 section: http://forum.xda-developers.com/show....php?t=2701376

Find and download the nandroid (TWRP) for CID BS_US002. Specifically, you should get the 1.12.1540.17 version. (There's a good reason for getting the older version...) You should also get a current TWRP image. (.img, not a zip file.) If you don't know how to get this image, then I'd advise NOT converting your device.

Then you can follow these steps:

Boot your phone normally.

Unpack the TWRP nandroid and place the folder into the proper directory on your phone's sdcard (/sdcard/TWRP/Backups/SERIAL_NUMBER/ or /sdcard2/TWRP/Backups/SERIAL_NUMBER) Replace "SERIAL_NUMBER" with your device's serial number. You should end up with a folder structure similar to: "./TWRP/Backups/HTXXXXXXXX/BackupName/" with the actual backup files in that directory.

... at this point, you might want to go ahead and boot into TWRP recovery to make sure that the backup you put in there is visible. It's fairly common for people to put the nandroid in the wrong place. I even did that myself once....


reboot into fastboot mode.

change CID to BS_US002 (BS_US001 is the "unlocked" version, BS_US002 is the DevEd version): fastboot oem writecid BS_US002

If you're starting with an AT&T branded device, there's no need to change the model ID (MID) as it's identical to the DevEd device.

reboot back into fastboot (to make sure the CID change worked): fastboot reboot-bootloader

use fastboot to put the proper DevEd STOCK recovery in place: fastboot flash stock_recovery.img

Probably not needed, but while in fastboot go ahead and run this: fastboot erase cache

Use fastboot to boot into (but not flash) the appropriate custom recovery. Example: fastboot boot openrecovery-twrp-2.7.0.2-m8.img

Use the custom recovery to wipe the data/cache/dalvik cache partitions.

Use the custom recovery to do a full restore from the backup copied to the phone above.

Reboot to the normal system. You can now accept OTA's and they should work. (They did for me.)


.... The reason for installing the older firmware version was to "test" the system by allowing the OTA to happen. If the OTA fails, then you screwed up the above steps.

Quote:

Thanks. Can you provide more detail on how to accomplish this or refer me to a thread that has that info?

I was typing.
The Following 26 Users Say Thank You to garyd9 For This Useful Post: [ View ]
24th May 2014, 08:12 AM   |  #5  
Wonders_Never_Cease's Avatar
Recognized Contributor
Thanks Meter: 880
 
1,780 posts
Join Date:Joined: Jul 2013
Donate to Me
Either will work, does not matter if its BS_XXXX1 or BS_XXXX2 as long as its the Brightstar cid, has no bearing on software whatsoever or the functionality of the software or phone...the ota comes with both so either will work regardless.....lol

Quote:
Originally Posted by garyd9

I guess you want some details, huh?

You'll need to get a Developer Edition stock recovery and a Developer Edition nandroid backup. (I'm lazy, so will just use "DevEd" instead of Developer edition.)

To get BOTH of these things, hop on over to a thread in the non-carrier specific M8 section: http://forum.xda-developers.com/show....php?t=2701376

Find and download the nandroid (TWRP) for CID BS_US002. Specifically, you should get the 1.12.1540.17 version. (There's a good reason for getting the older version...) You should also get a current TWRP image. (.img, not a zip file.) If you don't know how to get this image, then I'd advise NOT converting your device.

Then you can follow these steps:

Boot your phone normally.

Unpack the TWRP nandroid and place the folder into the proper directory on your phone's sdcard (/sdcard/TWRP/Backups/SERIAL_NUMBER/ or /sdcard2/TWRP/Backups/SERIAL_NUMBER) Replace "SERIAL_NUMBER" with your device's serial number. You should end up with a folder structure similar to: "./TWRP/Backups/HTXXXXXXXX/BackupName/" with the actual backup files in that directory.

... at this point, you might want to go ahead and boot into TWRP recovery to make sure that the backup you put in there is visible. It's fairly common for people to put the nandroid in the wrong place. I even did that myself once....


reboot into fastboot mode.

change CID to BS_US002 (BS_US001 is the "unlocked" version, BS_US002 is the DevEd version): fastboot oem writecid BS_US002

If you're starting with an AT&T branded device, there's no need to change the model ID (MID) as it's identical to the DevEd device.

reboot back into fastboot (to make sure the CID change worked): fastboot reboot-bootloader

use fastboot to put the proper DevEd STOCK recovery in place: fastboot flash stock_recovery.img

Probably not needed, but while in fastboot go ahead and run this: fastboot erase cache

Use fastboot to boot into (but not flash) the appropriate custom recovery. Example: fastboot boot openrecovery-twrp-2.7.0.2-m8.img

Use the custom recovery to wipe the data/cache/dalvik cache partitions.

Use the custom recovery to do a full restore from the backup copied to the phone above.

Reboot to the normal system. You can now accept OTA's and they should work. (They did for me.)


.... The reason for installing the older firmware version was to "test" the system by allowing the OTA to happen. If the OTA fails, then you screwed up the above steps.

I was typing.

The Following 2 Users Say Thank You to Wonders_Never_Cease For This Useful Post: [ View ]
24th May 2014, 06:34 PM   |  #6  
DG4FREE's Avatar
Senior Member
Tempe
Thanks Meter: 57
 
109 posts
Join Date:Joined: Jun 2010
More
Thumbs up
Quote:
Originally Posted by garyd9

I guess you want some details, huh?

You'll need to get a Developer Edition stock recovery and a Developer Edition nandroid backup. (I'm lazy, so will just use "DevEd" instead of Developer edition.)

To get BOTH of these things, hop on over to a thread in the non-carrier specific M8 section: http://forum.xda-developers.com/show....php?t=2701376

Find and download the nandroid (TWRP) for CID BS_US002. Specifically, you should get the 1.12.1540.17 version. (There's a good reason for getting the older version...) You should also get a current TWRP image. (.img, not a zip file.) If you don't know how to get this image, then I'd advise NOT converting your device.

Then you can follow these steps:

Boot your phone normally.

Unpack the TWRP nandroid and place the folder into the proper directory on your phone's sdcard (/sdcard/TWRP/Backups/SERIAL_NUMBER/ or /sdcard2/TWRP/Backups/SERIAL_NUMBER) Replace "SERIAL_NUMBER" with your device's serial number. You should end up with a folder structure similar to: "./TWRP/Backups/HTXXXXXXXX/BackupName/" with the actual backup files in that directory.

... at this point, you might want to go ahead and boot into TWRP recovery to make sure that the backup you put in there is visible. It's fairly common for people to put the nandroid in the wrong place. I even did that myself once....


reboot into fastboot mode.

change CID to BS_US002 (BS_US001 is the "unlocked" version, BS_US002 is the DevEd version): fastboot oem writecid BS_US002

If you're starting with an AT&T branded device, there's no need to change the model ID (MID) as it's identical to the DevEd device.

reboot back into fastboot (to make sure the CID change worked): fastboot reboot-bootloader

use fastboot to put the proper DevEd STOCK recovery in place: fastboot flash stock_recovery.img

Probably not needed, but while in fastboot go ahead and run this: fastboot erase cache

Use fastboot to boot into (but not flash) the appropriate custom recovery. Example: fastboot boot openrecovery-twrp-2.7.0.2-m8.img

Use the custom recovery to wipe the data/cache/dalvik cache partitions.

Use the custom recovery to do a full restore from the backup copied to the phone above.

Reboot to the normal system. You can now accept OTA's and they should work. (They did for me.)

Worked for me as well. Downloading the OTA as I type this. Thank you for the detailed instructions. Attempted to do this before when coming from the GPE ROM and had several issues. This time was much more streamlined thanks to your input.
25th May 2014, 03:16 AM   |  #7  
Alaris's Avatar
Senior Member
Thanks Meter: 26
 
449 posts
Join Date:Joined: May 2012
Quote:
Originally Posted by DG4FREE

Worked for me as well. Downloading the OTA as I type this. Thank you for the detailed instructions. Attempted to do this before when coming from the GPE ROM and had several issues. This time was much more streamlined thanks to your input.


Do I need to do anything different if I have twrp installed with stock Rom?
25th May 2014, 03:34 AM   |  #8  
DG4FREE's Avatar
Senior Member
Tempe
Thanks Meter: 57
 
109 posts
Join Date:Joined: Jun 2010
More
Quote:
Originally Posted by Alaris

Do I need to do anything different if I have twrp installed with stock Rom?

Stock rooted ROM or stock non rooted or stock Android (GPE or other ROM)?

Essentially follow the directions above, especially making sure you boot into TWRP recovery prior to flashing to the developer recovery since you already have it installed and go through the option to restore the developer edition nandroid backup. If it gives you the option to restore now, you should be fine to continue with the steps above. In short:

Reboot to bootloader.

Change your CID to BS_US002

Flash the developer recovery from the link above.

**Boot** into TWRP recovery (with the developer recovery still being the "installed recovery" using:

Code:
fastboot boot /location of recovery/recovery.img
TWRP should now open as if it was installed and allow you to restore from the developer edition nandroid even though you technically still have the developer edition recovery installed.

Once it restores you can reboot the phone and you should be good to go. Upon connecting to WiFi I was prompted to update to the latest OTA and everything has been working all day.

Sent from my HTC One_M8 using Tapatalk
The Following User Says Thank You to DG4FREE For This Useful Post: [ View ]
25th May 2014, 03:36 AM   |  #9  
Alaris's Avatar
Senior Member
Thanks Meter: 26
 
449 posts
Join Date:Joined: May 2012
Thanks debating on stay with att stock or this for faster updates.

Sent from my HTC One_M8 using Tapatalk
25th May 2014, 03:49 AM   |  #10  
DG4FREE's Avatar
Senior Member
Tempe
Thanks Meter: 57
 
109 posts
Join Date:Joined: Jun 2010
More
Quote:
Originally Posted by Alaris

Thanks debating on stay with att stock or this for faster updates.

Sent from my HTC One_M8 using Tapatalk

Its been great for me so far. I was on GPE and the little hardware issues (M8 is just better with Sense) made me come back. I've rocked the Maximus HD 4.0 ROM over in the open M8 forum and it has full AT&T support but thought I'd try this out. Sometimes I think the custom Roms put to much extras packed in although Maximus is decently light.

Sent from my Nexus 7 using Tapatalk

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools
Display Modes