Related
I just converted my AT&T to Europe model PN0710000 installed RUU and installed OTA unlocked. Changed my MID via ENG Hboot :good: conversion is def NOT for the faint of heart and could BRICK easily with one mess up so now my model reads PN0710000 instead of dev edition/ AT&T model ID so it works and is possible
Sweet, thought that might work.
Interesting, I've got an ASIA model (that's what is supplied in Australia) but again it's a different MID so we can't flash Euro WWE and ASIA releases seem to be very very slow, even for unbranded.
One thing though... did it change any of the network bands as far as you can tell? I 100% need one of the bands that EURO models do not have (need 3G850, euro drops that for 800 LTE). AFAIK it's the same radio hardware but I don't know how the phone works out what bands to make available, and therefore don't know if this is going to stuff me up.
M.
daddioj said:
I just converted my AT&T to Europe model PN0710000 installed RUU and installed OTA unlocked. Changed my MID via ENG Hboot :good: conversion is def NOT for the faint of heart and could BRICK easily with one mess up so now my model reads PN0710000 instead of dev edition/ AT&T model ID so it works and is possible
Click to expand...
Click to collapse
Awesome, thanks for figuring this out. Are you gonna post instructions? I wonder if someone could come up with a script to ease the chance of brickage.. I wouldnt be disapointed if you didnt post them.. Could be a mess. Most people really wont need to do this anyway.
mattman83 said:
Interesting, I've got an ASIA model (that's what is supplied in Australia) but again it's a different MID so we can't flash Euro WWE and ASIA releases seem to be very very slow, even for unbranded.
One thing though... did it change any of the network bands as far as you can tell? I 100% need one of the bands that EURO models do not have (need 3G850, euro drops that for 800 LTE). AFAIK it's the same radio hardware but I don't know how the phone works out what bands to make available, and therefore don't know if this is going to stuff me up.
M.
Click to expand...
Click to collapse
nugzo said:
Awesome, thanks for figuring this out. Are you gonna post instructions? I wonder if someone could come up with a script to ease the chance of brickage..
Click to expand...
Click to collapse
I don't know about bands.. as far as instruction's. i'll see if I could get to something if someone does not beat me too it. the thing is once you overwrite hboot with the DNA boot. the phone does not boot back into hboot without holding power and down volume. so at first I thought my phone was bricked. once you change MID.example.. PN0710000 and CID you want. weather it be HTC__001 or 11111111 you can go ahead and flash the WWE. but first you have to put the phone into RUU mode with fastboot oem rebootRUU.......... . once it starts it will overwrite hboot with a htc one. but it will shut off when it overwrites the hboot. you have to hold down power and to get it back up and the RUU will continue. and say hello to your coverted MID. I am sure it will be easier once we get our own ENG hboot.
daddioj said:
I don't know about bands.. as far as instruction's. i'll see if I could get to something if someone does not beat me too it. the thing is once you overwrite hboot with the DNA boot. the phone does not boot back into hboot without holding power and down volume. so at first I thought my phone was bricked. once you change MID.example.. PN0710000 and CID you want. weather it be HTC__001 or 11111111 you can go ahead and flash the WWE. but first you have to put the phone into RUU mode with fastboot oem rebootRUU.......... . once it starts it will overwrite hboot with a htc one. but it will shut off when it overwrites the hboot. you have to hold down power and to get it back up and the RUU will continue. and say hello to your coverted MID. I am sure it will be easier once we get our own ENG hboot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2320271
http://forum.xda-developers.com/show....php?t=2155214
nugzo said:
Awesome, thanks for figuring this out. Are you gonna post instructions? I wonder if someone could come up with a script to ease the chance of brickage.. I wouldnt be disapointed if you didnt post them.. Could be a mess. Most people really wont need to do this anyway.
Click to expand...
Click to collapse
you right I don't want to be bombed with PM's and posts why people hate me lol
daddioj said:
you right I don't want to be bombed with PM's and posts why people hate me lol
Click to expand...
Click to collapse
Yeah I get that's it's a risky thing.. maybe big red flashing warning signs, not that most people on here pay attention Flashing the eng hboot is fine (there are posts covering that), just wondering how you changed the MID?
M.
mattman83 said:
Yeah I get that's it's a risky thing.. maybe big red flashing warning signs, not that most people on here pay attention Flashing the eng hboot is fine (there are posts covering that), just wondering how you changed the MID?
M.
Click to expand...
Click to collapse
fastboot oem writemid PNxxxxxxx etc. eng hboot is fine to flash if we have one that boots with our device. as far as I know we don't? I am not sure
daddioj said:
fastboot oem writemid PNxxxxxxx etc. eng hboot is fine to flash if we have one that boots with our device. as far as I know we don't? I am not sure
Click to expand...
Click to collapse
I haven't heard of a booting ENG HBOOT. Just gotta flash ENG, change MID and flash back to stock HBOOT. As you say the phone won't boot normally with the ENG HBOOT as it's technically for the DNA and the NAND is partitioned differently.
There are instructions for flashing the ENG HBOOT from the phone, but I VERY HEAVILY recommend using fastboot from a PC as you're going to need it to flash back to a stock HBOOT anyway before your phone can boot normally. I'd hate to have an ENG HBOOT flashed only then find out my phone isn't playing along with fastboot
M.
mattman83 said:
I haven't heard of a booting ENG HBOOT. Just gotta flash ENG, change MID and flash back to stock HBOOT. As you say the phone won't boot normally with the ENG HBOOT as it's technically for the DNA and the NAND is partitioned differently.
There are instructions for flashing the ENG HBOOT from the phone, but I VERY HEAVILY using fastboot from a PC as you're going to need it to flash back to a stock HBOOT anyway before your phone can boot normally. I'd hate to have an ENG HBOOT flashed only then find out my phone isn't playing along with fastboot
M.
Click to expand...
Click to collapse
that's exactly what I did. but flashing is not straight forward bc since its a DNA hboot. it will refuse to flash other than the way I described it
daddioj said:
that's exactly what I did. but flashing is not straight forward bc since its a DNA hboot. it will refuse to flash other than the way I described it
Click to expand...
Click to collapse
Ok...so won't even flash as a .img via fastboot? I'm aware the .zip in the DNA thread won't work If dd'ing I presume you have to be booting into system for it to work.
M.
mattman83 said:
Ok...so won't even flash as a .img via fastboot? I'm aware the .zip in the DNA thread won't work If dd'ing I presume you have to be booting into system for it to work.
M.
Click to expand...
Click to collapse
yeah in the system it will work. but after getting it back I have not figured it out without flashing the ruu. I am writing something up now. unless someone knows something I don't. the more input the better I tried just the image file via fastboot and it didn't let me bc its looking for a DNA hboot. but I also had moonshine hboot at the time so I dunno if that had something to do with it
daddioj said:
yeah in the system it will work. but after getting it back I have not figured it out without flashing the ruu. I am writing something up now. unless someone knows something I don't. the more input the better
Click to expand...
Click to collapse
PLEASE TAKE THE TIME TO READ AND LEARN. BUT ITS AT YOUR OWN RISK. WHAT I WROTE AND WHAT OTHERS WROTE HERE ARE A GREAT HELP. TY WHO ADDED MORE OPTIONS TO MY CRAZY METHODS I LEARNED FROM READING OTHER THREADS. AND TRIAL AND ERROR
[/COLOR][/SIZE]
Step 1 - Have a stable PC! and Required Drivers Installed.! (phone must be in usb debugging mode for the time being)
Step 2- Download http://developer.android.com/sdk/index.html#download ( if you Dont have it Already)
Step 3- Download Hboot From DNA forums. once downloaded rename from Hboot.nbo to hboot.img
http://forum.xda-developers.com/showthread.php?t=2155214
Step 4 - place file on your sd card.
Step 5- boot into android. once booted. (via SDK) the one you downloaded run this command adb shell. then type su. sometimes su will work sometimes not. then type cd sd card. once your there run this command
dd if=/sdcard/HBOOT.img of=/dev/block/mmcblk0p12
(reboot into fastboot. you should now have ENG-hboot)
once in fastboot you will use "fastboot oem writemid" and choose what mid you want for what phone model and region check out mikes guide to show you which MID goes with what region
http://forum.xda-developers.com/showthread.php?t=2182823
so if you want WWE europe it would be PN0710000 etc. and a CID of HTC__001
this part is optional
you can totally wipe the phone via fastboot using. these commands.
fastboot erase cache
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot erase radio
you can skip this part if you want too.
once you changed your CID and MID go ahead and put your phone into RUU mode by typing fastboot oem rebootRUU
at this point your phone might shut off dont panic hold power and volume down. you will now be in RUU mode. now run the RUU. its going to send then flash hboot. it will reboot and might shut off. dont panic! hold power and down volume until in turns back on the RUU will continue. let the phone flash the rest of the way. and you will now have your converted AT&T phone
OTA's will also work and will not require a locked bootloader
THERE MIGHT BE AN EASIER WAY TO GET BACK TO STOCK HBOOT. I DIDNT PLAY AROUND ENOUGH. SO INPUT WOULD BE GOOD. ALSO YOU CAN JUST WAIT UNTIL THERE IS A OFFICIAL ENG-HBOOT FOR US.
FOR A MORE SIMPLE METHOD USE cschmitt BELOW. THEN USE THE REST OF THIS GUIDE. BUT YOU CAN ONLY USE THE FASTBOOT ERASE COMMANDS WITH A ENG-HBOOT
daddioj said:
yeah in the system it will work. but after getting it back I have not figured it out without flashing the ruu. I am writing something up now. unless someone knows something I don't. the more input the better
Click to expand...
Click to collapse
Here's how to flash the eng hboot and restore the original following MID change. Trick is the fastboot flash hboot won't allow writing the eng hboot (which is why you use dd), but it will write the original hboot back (versions, signatures, or something.)
FYI, to anyone reading this, if you don't understand what's going on here don't try this. I'm not responsible for anything you do to your phone as the result of trying this. Requires S-OFF.
Code:
# push eng hboot to phone
adb root
adb push enghboot.img /sdcard/enghboot.img
# backup original hboot to pc
adb shell dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12.bin
adb pull /sdcard/mmcblk0p12.bin mmcblk0p12.bin
# stop and verify mmcblk0p12.bin in on your pc!!!!!
# write eng hboot and reboot into it
adb shell dd if=/sdcard/enghboot.img of=/dev/block/mmcblk0p12
adb reboot bootloader
# after bootloader loads, writemid etc.
fastboot oem writemid ????????
# restore orignal hboot
fastboot flash hboot mmcblk0p12.bin
fastboot reboot-bootloader
# might have to hold down power for 20 seconds, reboot might take a bit
Edit: just saw your instructions above
cschmitt said:
Here's how to flash the eng hboot and restore the original following MID change. Trick is the fastboot flash hboot won't allow writing the eng hboot (which is why you use dd), but it will write the original hboot back (versions, signatures, or something.)
FYI, to anyone reading this, if you don't understand what's going on here don't try this. I'm not responsible for anything you do to your phone as the result of trying this. Requires S-OFF.
Code:
# push eng hboot to phone
adb root
adb push enghboot.img /sdcard/enghboot.img
# backup original hboot to pc
adb shell dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12.bin
adb pull /sdcard/mmcblk0p12.bin mmcblk0p12.bin
# stop and verify mmcblk0p12.bin in on your pc!!!!!
# write eng hboot and reboot into it
adb shell dd if=/sdcard/enghboot.img of=/dev/block/mmcblk0p12
adb reboot bootloader
# after bootloader loads, writemid etc.
fastboot oem writemid ????????
# restore orignal hboot
fastboot flash hboot mmcblk0p12.bin
fastboot reboot-bootloader
# might have to hold down power for 20 seconds, reboot might take a bit
Edit: just saw your instructions above
Click to expand...
Click to collapse
thanks this will help too!! :good: this might even be a good way for people who just want to change MID without touching anything else. so both guides are great ty!
Very good info here. Suggestion to OP: Daddioj edit your thread title to something more useful so more people can learn.
Sent from my HTC One using xda app-developers app
You can flash hboot via hboot (lol) just put the hboot.img in a zip that has the correct android txt in it.. for example the modified hboot zip in dev that removes the red warning ... Replace the .img in there with the eng one and rebootruu and flash the zip... Do it twice don't reboot if it fails.
I messed with the eng hboot from the DNA and that is how I went back and forth between hboots ... The ruu is needed to reset the right emmc sdcard location. Which ruu you use is not specific asking as you have the correct cid
Sent from my HTC One using xda premium
---------- Post added at 09:54 PM ---------- Previous post was at 09:48 PM ----------
If you manage to extract the correct sdcard size from the ruu (.img and .hdr) of your model then whe. Flashing back to the stock hboot make sure those are in the zip too. I have the 32gb version and I can't extract those from any ruu.. if you have the 64gb then your lucky
Sent from my HTC One using xda premium
Tachi91 said:
You can flash hboot via hboot (lol) just put the hboot.img in a zip that has the correct android txt in it.. for example the modified hboot zip in dev that removes the red warning ... Replace the .img in there with the eng one and rebootruu and flash the zip... Do it twice don't reboot if it fails.
I messed with the eng hboot from the DNA and that is how I went back and forth between hboots ... The ruu is needed to reset the right emmc sdcard location. Which ruu you use is not specific asking as you have the correct cid
Sent from my HTC One using xda premium
---------- Post added at 09:54 PM ---------- Previous post was at 09:48 PM ----------
If you manage to extract the correct sdcard size from the ruu (.img and .hdr) of your model then whe. Flashing back to the stock hboot make sure those are in the zip too. I have the 32gb version and I can't extract those from any ruu.. if you have the 64gb then your lucky
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
that's another option. thanks for the input :good:
Just out of curiosity, what is the point of changing the MID, when you already have the CID changed to SuperCID, and will allow you to flash any RUU? Are you saying that OTAs dont work on only CID changed phones.
I make this guide as there is no guide to change your phone to developer edition hTC One
-First of all your device must be 70% or more
-Have hTC drivers installed
-uninstall any kies or hTC sync or any thing related to them
-and ofcourse S-OFF
-Required Downloades
1-MINI SDK
Dropbox Mirror
2-ENG HBOOT
-For international hTC ONE
-For Google Play edition
-for any other hTC One edit android_info.text in the zip and change the mid and cid to your current mid and cid
3-Developer edition RUU
4- 3.22.1540.1.zip firmware
Instructions
1-copy the eng hboot.zip and the firmware.zip to the mini sdk folder
2-boot your device to bootloader
3-open cmd.exe in the mini sdk folder
4-type the command fastboot oem rebootRUU
5-type the command fastboot flash zip ENGHBOOTINternational/googleplayedition/etc zip
6-press the power button and the volume down button to boot to bootloader [untill you get grey screen]
7-type the command fastboot oem writecid BS_US001
8-type the command fastboot oem writemid PN0712000
9-type the command fastboot flash zip 3.22.1540.1.zipwhich is the firmware
10-it will ask to retry entering the command just do it
11-now reboot to bootloader power+volume down
12-then run the developer edition RUU and install it as a normal ruu
13-CONGRATULATIONS YOU MADE IT
Based in this?
http://htc-one.wonderhowto.com/how-...one-into-htc-one-with-sense-no-bloat-0148220/
Sent from my HTC O'ne-xus
mitchst2 said:
Based in this?
http://htc-one.wonderhowto.com/how-...one-into-htc-one-with-sense-no-bloat-0148220/
Sent from my HTC O'ne-xus
Click to expand...
Click to collapse
no it is not
[edit] I read the guide in that link and it doesn't mention anything about ENG hboot and changing the modelid of the phone
my guide makes you transform your htc one to a factory developer edition with its modelid and cid as if you bought a developer edition hTC One
also that guide in the link makes you download the developer edition ruu even if your device isn't I mean you won't go back with your stock sense rom [if you have international or carrier htc one] by using that guide
It occurred to me that there have been a number of 'I went s-on and relocked my bootloader, etc.' posts that have ended badly-- no RUU to flash, unable to return to stock or a working rom.
Now I'm not saying these folks are idiots, more likely just unfortunate mistakes. I myself am prone to the occasional derp.
That got me thinking about how to protect an s-off device from an accidental 'fastboot oem writesecureflag 3' that would leave me crying.
Basically, 4 things:
1. Find an RUU and tuck it away. For me, with an AT&T One, its 1.29.1540.16 from htc1guru. Why this RUU? Well it has a very old hboot 1.44.0000 (pre June, 2013) that is easy to s-off with revone, and can be unlocked via HTC Dev. Also, they are very easy to come by on sites like HTC Dev, htc1guru, etc.
2. Change CID to match what the RUU expects:
Code:
fastboot oem writecid BS_US001
The CID doesn't really matter for anything else, unless you plan on taking an OTA directly.
3. Make sure MID matches what the RUU expects as well: PN0712000 (which matches my AT&T device already.) If not then change it to match with the eng hboot (I won't go into that here, but if you've changed it once already then you're familiar with the process.)
4. Lastly, and most important: flash the hboot and change the firmware main version so that it matches what the 'rescue RUU' is expecting. For me, that's hboot 1.44.000 and 1.29.1540.16 so I created the attached 'firmware_reset_1.29.1540.16.zip' that can be flashed via:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware_reset_1.29.1540.16.zip
and it does nothing more than flash hboot 1.44.0000 and the android-info.txt resets the mainver to 1.29.1540.16 in the process.
This last step is important because with s-on you cannot RUU a downgrade hboot or mainver, so having hboot 1.44.0000 and mainver 1.29.1540.16 will allow the 'rescue RUU' to do it's thing.
So now we're all set. If things go south at some point and I need to get back to a known good, I can flash the RUU exe (even if s-on and locked), then unlock via HTC Dev, flash a custom recovery, root, and go.
cschmitt said:
It occurred to me that there have been a number of 'I went s-on and relocked my bootloader, etc.' posts that have ended badly-- no RUU to flash, unable to return to stock or a working rom.
Now I'm not saying these folks are idiots, more likely just unfortunate mistakes. I myself am prone to the occasional derp.
That got me thinking about how to protect an s-off device from an accidental 'fastboot oem writesecureflag 3' that would leave me crying.
Basically, 4 things:
1. Find an RUU and tuck it away. For me, with an AT&T One, its 1.29.1540.16 from htc1guru. Why this RUU? Well it has a very old hboot 1.44.0000 (pre June, 2013) that is easy to s-off with revone, and can be unlocked via HTC Dev. Also, they are very easy to come by on sites like HTC Dev, htc1guru, etc.
2. Change CID to match what the RUU expects:
Code:
fastboot oem writecid BS_US001
The CID doesn't really matter for anything else, unless you plan on taking an OTA directly.
3. Make sure MID matches what the RUU expects as well: PN0712000 (which matches my AT&T device already.) If not then change it to match with the eng hboot (I won't go into that here, but if you've changed it once already then you're familiar with the process.)
4. Lastly, and most important: flash the hboot and change the firmware main version so that it matches what the 'rescue RUU' is expecting. For me, that's hboot 1.44.000 and 1.29.1540.16 so I created the attached 'firmware_reset_1.29.1540.16.zip' that can be flashed via:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware_reset_1.29.1540.16.zip
and it does nothing more than flash hboot 1.44.0000 and the android-info.txt resets the mainver to 1.29.1540.16 in the process.
This last step is important because with s-on you cannot RUU a downgrade hboot or mainver, so having hboot 1.44.0000 and mainver 1.29.1540.16 will allow the 'rescue RUU' to do it's thing.
So now we're all set. If things go south at some point and I need to get back to a known good, I can flash the RUU exe (even if s-on and locked), then unlock via HTC Dev, flash a custom recovery, root, and go.
Click to expand...
Click to collapse
This is nice, but then people say "I want to go back to stock for warranty" and mess up the order of steps, and mess up their phones as a result..
Secondly, that is a very old bootloader, and it won't work with us people who have windows 8.1. Then you'll have to go around explaining to everyone how to recover from a partial flash of their RUU.
Also, changing MID isn't dangerous any longer. There's a method if doing it without flashing the eng bootloader.
Thirdly, if you're gonna modify the mainver inside android-info, it's gonna get unsigned, even an hboot outside of an RUU will be unsigned, so it isn't gonna work with s-on..
Also, the CID does matter for other stuff except OTAs/RUUs, it provides localised languages in system and keyboard, as well as the lyrics content changes (although here it's beneficial to have a US CID)
Just think these points over..
I'd say the best way to idiot proof it would be never to go s-on, so although they can mess stuff bad with s-off, at least it's recoverable. For Canadian users, while going back to stock, flash the oldest ruu you find, and then first set your bootloader status to "locked", flash the RUU, and only then go back s-on, take OTAs After you go s-on, I've heard that the command doesn't work well with phones having bootloader 1.55 and onwards.
(Edit) misunderstood your point about flashing the bootloader/changing the mainver,
but even if you do it while s-off, that'd still be, well, not ideal..
Sent from my iPod touch using Tapatalk
I'm certain it's not a solution that's perfect for everyone, really a starting point to be tailored to your specific device, region, and available ruu.
The whole going back to stock is something I'd rarely do, but wanted to have a plan if needed.
Absolutely agree that staying s-off is the best bet.
Do appreciate your comments.
Hello everyone, This is my first post in Desire 816 forum.
It seem like many people restored lollipop backup with WiFi issue. This is happen because you didn't update firmware that come with official OTA. I made firmware mod with removed red text warning hboot and decide to share it here.
S-OFF with SuperCID only
How to:
- Reboot phone to fastboot mode by press vol down + power then select fastboot in hboot menu
- Copy firmware zip to platform-tools folder of Android SDK or your own copy place of fastboot
- Rename it to firmware.zip
- Open terminal side the folder and type
Code:
fastboot oem rebootRUU
- You will see white HTC logo then type
Code:
fastboot flash zip firmware.zip
- Now type the same command again
Code:
fastboot flash zip firmware.zip
- Finished! You can reboot by
Code:
fastboot reboot
For S-ON user you can flash official firmware zip if you are using one of CID listed.
Download:
Mod no red warning text
https://www.dropbox.com/s/osavx0ud6cvgou0/a5_firmware_2.34.401.1_no_red_text.zip?dl=0
Official firmware for Europe
CID: HTC__001, HTC__A07, HTC__J15
https://www.dropbox.com/s/ld221ljbfvxsl8v/a5_firmware_2.34.401.1.zip?dl=0
You can find firmware for A5_DUG in this thread thank to our good user seekfind. :good:
thanksss
but is there any way with s-on ????
belal1981 said:
thanksss
but is there any way with s-on ????
Click to expand...
Click to collapse
I have edit the post with official firmware for S-ON user.
How could i check what is my cid ?
Sent from my CW-Vi8 using XDA Premium HD app
Search cid in playstore
12rithy said:
Hello everyone, This is my first post in Desire 816 forum.
It seem like many people restored lollipop backup with WiFi issue. This is happen because you didn't update firmware that come with official OTA. I made firmware mod with removed red text warning hboot and decide to share it here.
S-OFF with SuperCID only
How to:
- Reboot phone to fastboot mode by press vol down + power then select fastboot in hboot menu
- Copy firmware zip to platform-tools folder of Android SDK or your own copy place of fastboot
- Rename it to firmware.zip
- Open terminal side the folder and type
Code:
fastboot oem rebootRUU
- You will see white HTC logo then type
Code:
fastboot flash zip firmware.zip
- Now type the same command again
Code:
fastboot flash zip firmware.zip
- Finished! You can reboot by
Code:
fastboot reboot
For S-ON user you can flash official firmware zip if you are using one of CID listed.
Download:
Mod no red warning text
https://www.dropbox.com/s/osavx0ud6cvgou0/a5_firmware_2.34.401.1_no_red_text.zip?dl=0
Official firmware for Europe
CID: HTC__001, HTC__A07, HTC__J15
https://www.dropbox.com/s/ld221ljbfvxsl8v/a5_firmware_2.34.401.1.zip?dl=0
Click to expand...
Click to collapse
Can i use it on S-ON A5_DWG+Unlocked Bootloader+Twrp..?
Please do replay as i want to restore to stock....!!
Please, make one zip for a5_dug HTC Cid_59
psolunke said:
Can i use it on S-ON A5_DWG+Unlocked Bootloader+Twrp..?
Please do replay as i want to restore to stock....!!
Click to expand...
Click to collapse
You must relock bootloader with correct CID.
KimUyLong said:
Please, make one zip for a5_dug HTC Cid_59
Click to expand...
Click to collapse
Sorry I don't own any Cid HTC_59 device
a huge thanks to you for the explanation I'll be looking around for OTA image for A5_DUG to fix my firmware then
so, I extracted A5_DUG firmware.zip from its OTA. when I try to flash the firmware, this is what I get.
when should I flash it anyway? before or after restoring the TWRP lolipop backup?
also, am I correct to assume that by flashing this, I will lose custom recovery and have to flash TWRP again ?(as firmweare.zip includes the stock recovery.img)
*EDIT* Nevermind. I found out that if you're S-On , the bootloader should be locked in order to flash a zip in RUU, so you'll have to type in this command before flashing:
Fastboot oem lock
Click to expand...
Click to collapse
and ofcourse, you'll need to unlock later, and it doesn't accept your old Unlocktoken, so you'll have to get another one from HTCdev
and then flash custom recovery afterwards.
seekfind said:
so, I extracted A5_DUG firmware.zip from its OTA. when I try to flash the firmware, this is what I get.
when should I flash it anyway? before or after restoring the TWRP lolipop backup?
also, am I correct to assume that by flashing this, I will lose custom recovery and have to flash TWRP again ?(as firmweare.zip includes the stock recovery.img)
*EDIT* Nevermind. I found out that if you're S-On , the bootloader should be locked in order to flash a zip in RUU, so you'll have to type in this command before flashing:
and ofcourse, you'll need to unlock later, and it doesn't accept your old Unlocktoken, so you'll have to get another one from HTCdev
and then flash custom recovery afterwards.
Click to expand...
Click to collapse
Could you share your firmware in case other with same CID need?
12rithy said:
Could you share your firmware in case other with same CID need?
Click to expand...
Click to collapse
sure, I'll make a new thread for A5_Dug and link to your thread for A5_DWG users. you can do the same
seekfind said:
sure, I'll make a new thread for A5_Dug and link to your thread for A5_DWG users. you can do the same
Click to expand...
Click to collapse
linked
my htc's cid is htc_038
12rithy said:
You must relock bootloader with correct CID.
Sorry I don't own any Cid HTC_59 device
Click to expand...
Click to collapse
can u please tell me how to chnge cid ?? and you are saying relock bootloader with correct cid but how , i only know how to unlock !! please help !!
ripper1681 said:
can u please tell me how to chnge cid ?? and you are saying relock bootloader with correct cid but how , i only know how to unlock !! please help !!
Click to expand...
Click to collapse
Are you S-OFF? if so, you can change the cid this way.
If you're S-on, there's not much you can do.( I read somewhere that you can edit CID in the firmware files so that your device accepts it but I can't remember where or how it was.)
ripper1681 said:
can u please tell me how to chnge cid ?? and you are saying relock bootloader with correct cid but how , i only know how to unlock !! please help !!
Click to expand...
Click to collapse
relock bootloader process is the same as unlock. In fastboot mode type this command
Code:
fastboot oem lock
I am on cm 12.1
Kitkat firmware
HTC desire 816 a5 DWG Indian dual sim
CID HTC__038
S-ON
Will this work for me?
Hi download links are not working. please provide a mirror
Just an FYI type thing that may save people a bit of digging around sometime.
I tried to get the update that just came out, but as i had TWRP as recovery, no good. Anyhow, in my trying i completely bollixed the phone. Would start, but always booted to TWRP and had various conniptions. Could not even get a TWRP backup to load. Strange not encountered before by me stuff............
Anyhow, recovered by the following method to stock and am back in business.
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
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_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Not my own work, adapted from this thread by t-bon3
https://forum.xda-developers.com/showthread.php?t=2542219
which I found thanks to eens post18 at this thread
https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084/page2
After this, Motorola system update installed. On Australian XT1676 is build number NPP25.137-15-7
Patch level 1-May-2017
Still get the I cant be trusted page on power up as have unlocked bootloader.
Many thanks to all at XDA, its a resource that can certainly get you into trouble, but then out of it again.
where do you get the stock firmware?
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
We're you able to revert to a locked bootloader after this, I am looking forward to do so
We're you able to revert to a locked bootloader after this, I am looking forward to do so
Click to expand...
Click to collapse
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
astmacca said:
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
Click to expand...
Click to collapse
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
ap4ss3rby said:
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
Click to expand...
Click to collapse
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
TheFixItMan said:
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
Click to expand...
Click to collapse
Thanks, but this is why I made a Google pixel themed logo.bin and used a matching boot animation to go with it some time earlier
downgrade
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
distclean said:
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
Click to expand...
Click to collapse
No you cannot downgrade (same firmware version or newer required)
Yes - unlocked bootloader not required
As long as your phone still goes into the bootloader
You should flash all sparsechunks in number order
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
You maybe able to - there are different variants of the same phone
As long as the firmware is the same or newer (as in the bootloader and API version) it may flash
It will either flash or error out
There's only one way to find out - if your phone is dead anyway it's not going to make alot of difference
No - generally you can never downgrade firmware - doing so would be dangerous and you may loose the bootloader for good
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
distclean said:
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
Click to expand...
Click to collapse
You can write in adb
Code:
adb shell
cat /proc
cat /proc/partitions
Hello,
Does anyone know where can I download the latest firmware for Moto G5 XT1676 baseband Version: m8937_ 8000.122.02.40 R
Thanks
astmacca said:
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
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_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Click to expand...
Click to collapse
You're partially right. These commands won't work for our files. You have to flash the firmware according to the instructions contained within the "flashfile.xml" file within the archive. For example we have no "motoboot" partition
I've flashed every stock package available now (4 I think) and haven't been offered an update once. I've ran a couple of custom ROMs but they're just not right in one way or another. Might be time to move on.
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
I upgraded to this and since then can't downgrade the phone to the stock roms available online. From memory trying to flash gpt.bin gave a "Security version downgrade" error. So I wouldn't assume you'll be able to downgrade and until there is a copy of this particular firmware, you won't be able to flash back or relock the bootloader
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Is this ROM is good to my XT1676 Baseband: M8937_11.16.02.51R ?
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Hi, i own the same model of moto g5, i do this in fastboot window
fastboot erase userdata
now the phone only boot in twrp and show a message "failed to mount /data". i think that delete my userdata partition, how could i fix it?
once i can avoid this loop in twrp, i follow these steps to flash stock rom
thanks in advance
juan