Took this from the Motorola website directly, decided to mirror it on my G-Drive. Flash these in fastboot using the motorola fastboot binary if you ever run into any problems and need to flash back to stock! Just follow the instructions below if you are new to the process.
https://drive.google.com/file/d/0B3-cp2-eXDUMY29DbklvNHJoZHM/edit?usp=sharing
Directly from Motorola's website:
FLASH AND RELOCK YOUR DEVICE
After downloading the image for your device:
Unzip the image.
Put your device in fastboot mode.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock
Click to expand...
Click to collapse
Do you think this can work on an unlocked BL Latinamerica Moto x? (XT1058)
Sent from muy Moto X
Has anyone figured out how to get native tethering working on this build?
gueszman said:
Do you think this can work on an unlocked BL Latinamerica Moto x? (XT1058)
Sent from muy Moto X
Click to expand...
Click to collapse
I wouldn't attempt it, this is made for the verizon CDMA moto, where you have a gsm variant. It mostly likely will boot? But you will have major issues afterwards , worst case, you'll soft brick your moto and will have to rsd lite back if possible. Wait as all carriers will get kk sooner than later. Have some Patience
Sent on my Moto X
Yeah, I agree with Flash, just wait until they eventually release stock images for your device on KitKat
Where do you download the motorola fastboot?
publicanimal said:
Has anyone figured out how to get native tethering working on this build?
Click to expand...
Click to collapse
Yes, on Dev Edition only: http://forum.xda-developers.com/showthread.php?t=2536166
schmoe0013 said:
Where do you download the motorola fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=33228220
Does Settings > Security continually crash and close on y'all after flashing these fastboot image files? Everything else seems to be working fine.
Would this work on a bl unlocked sprint x?
Sent from my XT1056 using Tapatalk
AFAIK, only for VZW Developer Edition
defsquad said:
Does Settings > Security continually crash and close on y'all after flashing these fastboot image files? Everything else seems to be working fine.
Click to expand...
Click to collapse
So, I've read it could be because of the modem that this is happening? Just seems strange.. I'm not sure why this is failing, especially following the Moto provided instructions. This is indeed an unlocked VZW developer edition. Anyone else run into this issue? Unfortunately, it won't install the OTA so I had to go this route (e.g. flashing the provided images)
alex94kumar said:
Took this from the Motorola website directly
Click to expand...
Click to collapse
Can you post a link?
Bradart said:
Would this work on a bl unlocked sprint x?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
I'd be curious about this too. I've seen posts of people running T-Mobile Roms on Verizon and all kinds of crazy shenanigans, so I wonder if this is possible.
Sent from my XT1056 using Tapatalk
MichaelMcEntire said:
I'd be curious about this too. I've seen posts of people running T-Mobile Roms on Verizon and all kinds of crazy shenanigans, so I wonder if this is possible.
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
I'm thinking about attempting it but I am reluctant.
Sent from my XT1056 using Tapatalk
Bradart said:
I'm thinking about attempting it but I am reluctant.
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
I hear ya. I would think it would be safe as long as you back up first, all my experience says so. However I've never owned a Moto device before. Can't see what could be different, but who knows?
Sent from my XT1056 using Tapatalk
Bradart said:
I'm thinking about attempting it but I am reluctant.
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Don't do it. Flashing roms from other carriers isn't the same as flashing these VZW image files to your device. It doesn't matter if you have an unlocked bootloader on sprint since these are made specifically for the Verizon Dev Edition.
Any of y'all have issues with Security Settings force closing? (on a VZW Developer Edition)
Help! I'm at a loss as to how to fix this . I've tried going through these steps (several times now) in the OP as well as the similar ones on Moto's site for the recovery images.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Click to expand...
Click to collapse
Where are the Darwin/, Linux/ and Windows/ directories located? I assume for windows its C:/Windows/ but on OSX (my os right now) there is no /Darwin/. Thanks for the assistance gentlemen. I'm getting back into this and have been away since the DInc days.
Anyone have the GSM version of this?
ak110707 said:
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Where are the Darwin/, Linux/ and Windows/ directories located? I assume for windows its C:/Windows/ but on OSX (my os right now) there is no /Darwin/. Thanks for the assistance gentlemen. I'm getting back into this and have been away since the DInc days.
Click to expand...
Click to collapse
Bump. Anyone know?
Related
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..
Hello
I got HTC J Butterfly from Japan and have been trying to get it working in Finland since.
We tried first to change the phone to Taiwan version (x920d), but the result was no good 2G.
The next step was to try to change to phone into Droid DNA,
Starting point:
DELUXE_J PVT SHIP S-OFF
CID-KDDI_801
HBOOT-1.41.0000
RADIO-1.01.10.0201
OpenDSP-v6.120.274.0114
Original HTC J Butterfly ROM
What was done:
1. installed jdk1.7.0_25 and android sdk tools, platform tools and google usb driver (installer_r22.0.5)
2. installed ViperDNA 1.3.5 ROM (via CWM recovery from external sd card)
3. installed engineering HBOOT (see below)
fastboot oem rebootRUU
fastboot flash zip xxxxxx.zip
4. installed twrp recovery: twrp-htc-dlxj.img
5. modify (CID: 11111111 and IMEI and MEID according to my phone) in mmcblk0p5 block file and copy to /dev/block with dd:
dd if=/sdcard/mmcblk0p5 of=/dev/block/mmcblk0p5 (copied to /sdcard/ with adb push in recovery mode)
NOTE1: HERE ADB STILL OK
6. fastboot oem writemid PL8320000
NOTE2: HERE ADB CANNOT BE USED ANYMORE
NOTE3: phone was encrypted and asking for password (cleared by formatting internal SD)
7. flash firmware
fastboot oem rebootRUU
fastboot flash zip dna2.06firmware.zip
7.1 installed twrp recovery: twrp-htc-dlx.img
8. installed engineering HBOOT (see below)
fastboot oem rebootRUU
fastboot flash zip xxxxxx.zip
Current situation:
MONARUDO PVT ENG S-OFF
CID-11111111
HBOOT-1.39.2000 (PL8320000)
RADIO-1.01.04.0308
OpenDSP-v6.120.274.0114
No ROM currently
Fastboot USB (OK)
ADB (NOK)
USB connection (NOK)
- cannot connect to device from Windows 7 or Windows XP, because the phone/device is flashing as portable device called:
WPD FileSystem Volume Driver
What I would like to do is to flash ROM.
but since I cannot transfer any files to the system it seems to be impossible.
I can flash in fastboot, because that is working just fine.
Any ideas how to proceed are more than welcome !?
Thank you
Can you run the RUU ? Or if can not because windows does not see it, run the RUU to extract the files to temp folder, then flash the zips manually via fastboot?
You prolly have seen this thread;
http://forum.xda-developers.com/showthread.php?t=2155334
thehoovie said:
Can you run the RUU ? Or if can not because windows does not see it, run the RUU to extract the files to temp folder, then flash the zips manually via fastboot?
You prolly have seen this thread;
http://forum.xda-developers.com/showthread.php?t=2155334
Click to expand...
Click to collapse
Thanks for the reply.
What do you mean by running the RUU ? fastboot oem rebootRUU ? (that is working for me)
I was also thinking that I cannot flash anything for DELUXE_J since I changed the moid. Not sure if this is true ?
Thanks
Hello again
Currently I'm assuming there is no way to install ROM without working USB/ADB, because no replies.
If you know such method and needed files please let me know.
Thank you
Hello
Raised the topic since I have not received any replies.
Most probably someone knows how to get the phone working again (install ROM).
Please help. Thanks
jko76 said:
Hello
Raised the topic since I have not received any replies.
Most probably someone knows how to get the phone working again (install ROM).
Please help. Thanks
Click to expand...
Click to collapse
Since you're S-OFF you could probably just change the model id back to the J Butterfly the same way you changed it to the DNA
Sent from my HTC6435LVW using xda app-developers app
times_infinity said:
Since you're S-OFF you could probably just change the model id back to the J Butterfly the same way you changed it to the DNA
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
For changing the model id I would need to copy a block file to the device. Currently i cannot do that.
Any other ideas ?
jko76 said:
For changing the model id I would need to copy a block file to the device. Currently i cannot do that.
Any other ideas ?
Click to expand...
Click to collapse
In the OP you said you changed the model id with fastboot oem writemid.
Since you're soff, you should just be able to do that again, back to the J Butterfly mid
Sent from my HTC6435LVW using xda app-developers app
Yeah why did you flash DNA files on a j butterfly anyways man you probably messed the phone up .
Sent from my HTC6435LVW using Tapatalk 2
times_infinity said:
In the OP you said you changed the model id with fastboot oem writemid.
Since you're soff, you should just be able to do that again, back to the J Butterfly mid
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
In the OP step 5 I copied Droid DNA block file into my phone and then changed the mid. I was thinking that without putting back my original
block HTC J blockfile I cannot change the mid back. Of course I could try the command but I'm worried that the incorrect block file mid combination will brick the phone totally.
Is there any RUU available for Droid DNA that could be flashed through fastboot ?
Thanks
coachcrey said:
Yeah why did you flash DNA files on a j butterfly anyways man you probably messed the phone up .
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
The idea was to try to make the phone working in Finland (the phone was locked to AU network in Japan). It did not work with x920d SW (2G NOK) and therefore decided to give the DNA SW a go.
Yes, the phone might be messed up, but still I would like to think there is a way to recover since the fastboot and recovery are working.
Thanks
jko76 said:
The idea was to try to make the phone working in Finland (the phone was locked to AU network in Japan). It did not work with x920d SW (2G NOK) and therefore decided to give the DNA SW a go.
Yes, the phone might be messed up, but still I would like to think there is a way to recover since the fastboot and recovery are working.
Thanks
Click to expand...
Click to collapse
I guess the better question is who gave you the idea to try and flash dna files on a butterfly to my understanding they are similar phones not the same.
Sent from my HTC6435LVW using Tapatalk 2
coachcrey said:
I guess the better question is who gave you the idea to try and flash dna files on a butterfly to my understanding they are similar phones not the same.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
The idea was mine.
We tried x920d SW as well and that was working apart from the unstable 2G connection.
thehoovie said:
Can you run the RUU ? Or if can not because windows does not see it, run the RUU to extract the files to temp folder, then flash the zips manually via fastboot?
You prolly have seen this thread;
http://forum.xda-developers.com/showthread.php?t=2155334
Click to expand...
Click to collapse
I can run the RUU*.exe until it checks the USB connectivity. In the temp files I can find the data1.cab file which most probably has the image files that I would need. The remaining problem is that I cannot extract the data1.cab file.
Does anyone know how to extract the cab file ?
Thank you
jko76 said:
I can run the RUU*.exe until it checks the USB connectivity. In the temp files I can find the data1.cab file which most probably has the image files that I would need. The remaining problem is that I cannot extract the data1.cab file.
Does anyone know how to extract the cab file ?
Thank you
Click to expand...
Click to collapse
Actually I found the ROM.zip as well from temp directory. I cannot unzip the file.
How to use this ROM.zip file ?
jko76 said:
Actually I found the ROM.zip as well from temp directory. I cannot unzip the file.
How to use this ROM.zip file ?
Click to expand...
Click to collapse
Use ruuveal to decrypt the zip
Sent from my HTC6435LVW using xda app-developers app
times_infinity said:
Use ruuveal to decrypt the zip
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Done and now I can open/extract the rom.zip. There are many .img files inside.
Now I need some help how to proceed ?
Please remember that the phone is S-OFF and engineering HBOOT is currently installed.
Do I need to change HBOOT ? What about S-ON ?
What is the best way of flashing the images ?
Thank you very much for your help.
jko76 said:
Done and now I can open/extract the rom.zip. There are many .img files inside.
Now I need some help how to proceed ?
Please remember that the phone is S-OFF and engineering HBOOT is currently installed.
Do I need to change HBOOT ? What about S-ON ?
What is the best way of flashing the images ?
Thank you very much for your help.
Click to expand...
Click to collapse
You can try just flashing the whole zip. Do fastboot oem rebootRUU and then fastboot flash zip ruu.zip
Sent from my HTC6435LVW using XDA Premium 4 mobile app
times_infinity said:
You can try just flashing the whole zip. Do fastboot oem rebootRUU and then fastboot flash zip ruu.zip
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
AFTER fastboot flash zip rom.zip:
MONARUDO PVT SHIP S-OFF
CID-11111111
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
fastboot flash recovery twrp-htc-dlx.img
TWRP recovery installed
fastboot flash zip PL832.zip
MONARUDO PVT ENG S-OFF
HBOOT-1.39.2000 (PL8320000)
Unfortunately the USB/ADB is still unstable. Also it seems that the ROM does not boot up. The droid boot image can be seen. Then it goes away and I can see in the upper part of the screen USB debugging connected flashing...
Fastboot interface is ok, bootloader and recovery as well.
Let's see what could be the next step/try. Currently it seems that Droid SW cannot be used with HTC J Butterfly HW !?
All I can offer is they obviously have differences or the kernels would be the same. Try using the proper kernel for it and see if it proceeds any further in booting the ROM. Making it think its a DNA doesn't change the hardware itself, at a minimum the kernel needs to be the correct one foe the device hardware, not name, and maybe the ROM just to eliminate drivers and libs being incompatible as well.
Or is the kernel the same?
Tapatalked from my HTC DNA - Carbon
As the titles signifies I want to know what these commands do?
Thanks in advance!
deej_roamer said:
As the titles signifies I want to know what these commands do?
Thanks in advance!
Click to expand...
Click to collapse
Founds this:
fastboot oem fb_mode_clear: While in fastboot loop, this command exits the loop and allows your device to reboot normally.
I think it's for prepping certain phones (seems like some Motorolas) for flashing firmware and to boot it out of that mode if it's stuck or you don't need it anymore.
I've done tons of fastboot stuff on a lot of HTC, Nexus devices, and a couple of Motos and others and have never even seen either for anything.
es0tericcha0s said:
Founds this:
fastboot oem fb_mode_clear: While in fastboot loop, this command exits the loop and allows your device to reboot normally.
I think it's for prepping certain phones (seems like some Motorolas) for flashing firmware and to boot it out of that mode if it's stuck or you don't need it anymore.
I've done tons of fastboot stuff on a lot of HTC, Nexus devices, and a couple of Motos and others and have never even seen either for anything.
Click to expand...
Click to collapse
It does not make a difference weather i use the fb make for flashing firmware as It has always worked without It. No doubt It works with the command as well.
What difference will It make if i dont use these? I cant seem to find any
Sent from my XT1033 using Tapatalk
deej_roamer said:
It does not make a difference weather i use the fb make for flashing firmware as It has always worked without It. No doubt It works with the command as well.
What difference will It make if i dont use these? I cant seem to find any
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
I dunno. I've never had use of those commands, or even seen them, and I've rooted and / or restored tons of phones that had fastboot. Are you seeing those commands in a certain guide for your phone or something?
All stock firmware has these commands!
es0tericcha0s said:
I dunno. I've never had use of those commands, or even seen them, and I've rooted and / or restored tons of phones that had fastboot. Are you seeing those commands in a certain guide for your phone or something?
Click to expand...
Click to collapse
I downloaded three different firmwares for my XT1033 AsiaRetail, GBRetail, GPe all the factory xml files had this line in
Code:
<step operation="oem" var="fb_mode_set" />
<step operation="oem" var="fb_mode_clear" />
their XML files.
and i believe they can manually be activated by fastboot using
Code:
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
I just dont understand these commands and their purpose!
Thanks for your interest and help!
ANYONE?
ANYONE?
I still can't find any explanation other than it's something to do with the stock firmwares and it's only a Moto thing. Most of the stuff about the lines are that it works to remove them when flashing fails on a lot of phones / updates. Can't be that important.
I know this is an old thread but here is what I have found elsewhere. "fastboot oem fb_mode_set" forces fastboot mode on reboot. "fastboot oem fb_mode_clear" clears the force to fastboot mode on reboot so that the device will boot normally. Motorola stock firmware uses these commands during the flashing process so that the device will always boot to fastboot until the flashing process is complete.
Dear Mr. Deej. I got the problem that almost the same here.. My Moto G default boot is to recovery. The way i could enter the rom is with Bootloader option "Normal powerup". Is there any way to change it back to normal with that command line? I'm currently on CM 12.1 Unofficial and running TWRP 2.8.6.0. Thanks in advance..
cheppiroma said:
Dear Mr. Deej. I got the problem that almost the same here.. My Moto G default boot is to recovery. The way i could enter the rom is with Bootloader option "Normal powerup". Is there any way to change it back to normal with that command line? I'm currently on CM 12.1 Unofficial and running TWRP 2.8.6.0. Thanks in advance..
Click to expand...
Click to collapse
I too have this problem. I have to go through bootloader manually selecting the 'Normal Powerup' option. The phone no longer boots into the ROM by itself.
willowen100 said:
I too have this problem. I have to go through bootloader manually selecting the 'Normal Powerup' option. The phone no longer boots into the ROM by itself.
Click to expand...
Click to collapse
If the problem is your boot on TWRP this post should fixed it. I try that and it fixed my boot problem. And always DWYOR
this commands for
deej_roamer said:
ANYONE?
Click to expand...
Click to collapse
Motorola NO Network After Frp (Solution Inside)
fastboot oem config bootmode
fastboot oem fb_mode_clear
willowen100 said:
I too have this problem. I have to go through bootloader manually selecting the 'Normal Powerup' option. The phone no longer boots into the ROM by itself.
Click to expand...
Click to collapse
Hi! I have the same problem. Did you find a solution? The above command "fastboot oem fb_mode_clear" does not work.
seryogin_108 said:
Hi! I have the same problem. Did you find a solution? The above command "fastboot oem fb_mode_clear" does not work.
Click to expand...
Click to collapse
I ended up using a command found here https://r.tapatalk.com/shareLink?ur...re_type=t
Device always boots into recovery. It wipes the misc partition. if you're using TWRP you can use the terminal and type the command straight into that.
Sent from my LG-H930 using Tapatalk
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?
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.
NextNexus said:
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.
Click to expand...
Click to collapse
Yes, it's possible.
garyd9 said:
Yes, it's possible.
Click to expand...
Click to collapse
Thanks. Can you provide more detail on how to accomplish this or refer me to a thread that has that info?
garyd9 said:
Yes, it's possible.
Click to expand...
Click to collapse
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/showthread.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.
Thanks. Can you provide more detail on how to accomplish this or refer me to a thread that has that info?
Click to expand...
Click to collapse
I was typing.
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
garyd9 said:
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/showthread.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.
Click to expand...
Click to collapse
garyd9 said:
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/showthread.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.)
Click to expand...
Click to collapse
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.
DG4FREE said:
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.
Click to expand...
Click to collapse
Do I need to do anything different if I have twrp installed with stock Rom?
Alaris said:
Do I need to do anything different if I have twrp installed with stock Rom?
Click to expand...
Click to collapse
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
Thanks debating on stay with att stock or this for faster updates.
Sent from my HTC One_M8 using Tapatalk
Alaris said:
Thanks debating on stay with att stock or this for faster updates.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
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
Dumb question ?
What would be the main benefits to changing to lets say from the at&t m8 to a dev edition, other than faster updates ?
DG4FREE said:
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
Click to expand...
Click to collapse
Thanks everyone had a couple of speed bumps but I got through it. Just out of curiousity would there be any difference between the Dev Ruu and doing this?
Alaris said:
Thanks everyone had a couple of speed bumps but I got through it. Just out of curiousity would there be any difference between the Dev Ruu and doing this?
Click to expand...
Click to collapse
Wasn't aware of a Dev RUU being posted (at least an official one) but from what I understand it'd be the same thing.
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 08:36 PM ---------- Previous post was at 08:34 PM ----------
Roefastford said:
Dumb question ?
What would be the main benefits to changing to lets say from the at&t m8 to a dev edition, other than faster updates ?
Click to expand...
Click to collapse
No AT&T branding/bloat. I know there's Roms out there that are debloated but you'd still be required to manually flash updates and or use the built in OTA of that ROM if it has such a feature. This in a way gives you the best of both.
Sent from my HTC One_M8 using Tapatalk
Anyone notice the red writing during setup that said something along the lines of this being a test device and HTC will collect info like location etc.? Is this something that I should be worried about?
Roefastford said:
What would be the main benefits to changing to lets say from the at&t m8 to a dev edition, other than faster updates ?
Click to expand...
Click to collapse
Assuming you're comparing "stock" to "stock": No carrierIQ, faster updates, no AT&T bloatware. (However, you lose Isis and the visual voice mail integration.)
Alaris said:
Anyone notice the red writing during setup that said something along the lines of this being a test device and HTC will collect info like location etc.? Is this something that I should be worried about?
Click to expand...
Click to collapse
I never noticed that. My understanding is that the warning comes up if you're using a recovery or kernel that doesn't match the rest of the firmware. If you follow the instructions I posted, you should end up with a completely stock recovery + kernel, so won't see that red warning.
Oh, and if you DO see the warning, it's completely harmless.
Take care
Gary
garyd9 said:
Assuming you're comparing "stock" to "stock": No carrierIQ, faster updates, no AT&T bloatware. (However, you lose Isis and the visual voice mail integration.)
I never noticed that. My understanding is that the warning comes up if you're using a recovery or kernel that doesn't match the rest of the firmware. If you follow the instructions I posted, you should end up with a completely stock recovery + kernel, so won't see that red warning.
Oh, and if you DO see the warning, it's completely harmless.
Take care
Gary
Click to expand...
Click to collapse
Do you have s-off?
Alaris said:
Do you have s-off?
Click to expand...
Click to collapse
Yes.
Sent from my HTC One_M8
garyd9 said:
Yes.
Sent from my HTC One_M8
Click to expand...
Click to collapse
Do my a favor go to settings>about and there should be one that says tell HTC click it and scroll to the bottom. Do you see any red writing that says HTC will collect data? Because i did exactly what you did and I have that writing that says the will collect data and i cant opt out of it. It doesn't sound like me and you have anything that we did differently unless you didn't notice yours during the initial setup.
Alaris said:
Do my a favor go to settings>about and there should be one that says tell HTC click it and scroll to the bottom.
Click to expand...
Click to collapse
I don't have anything like "tell HTC". I did go through everything in settings->about, but nothing like what you described.
Sent from my HTC One_M8
I don't get why I that then
Sent from my HTC One_M8 using Tapatalk