Related
My phone name is HTC magic:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0004 (SAP1000)
CPLD-10
RADIO-2.22.19.261
Aug 4 2009, 23:43:40
When start can see HIAPK logo on screen
I was up wrong rom but when start can see recovery boot và fastboot.
Now up every rom to the
Installing update...
E: Can't find update scrip
Installation aborted.
How I do fix this problem?
Sorry i am a newbe and speak english not good.
Thank you so much
Who have original rom please give me please.
Thank alot.
Who can help me??????
fastboot getvar cidnum
This command shows cid from phone. With cid you can choose rom that is for your phone (look at rom collection in developer forum)
Sent from my A7-040 using Tapatalk
Thanks for help. As you say I up another rom the notice CID wrong. This rom i get from RUU rom. Please guide for me.
Thank so much
winball said:
Thanks for help. As you say I up another rom the notice CID wrong. This rom i get from RUU rom. Please guide for me.
Click to expand...
Click to collapse
1. What do you want? Official or custom rom?
2. Is SPL-info in first post correct? Did you change it?
3. Load phone into fastboot, connect to PC, then run from PC:
Code:
fastboot getvar main-version
This command shows you current rom version. Please write it.
Then run
Code:
fastboot getvar cidnum
or
Code:
fastboot getvar cid
to get current CID
write them too
p.s. Create Goldcard (just in case)
5[Strogino] said:
1. What do you want? Official or custom rom?
2. Is SPL-info in first post correct? Did you change it?
3. Load phone into fastboot, connect to PC, then run from PC:
Code:
fastboot getvar main-version
This command shows you current rom version. Please write it.
Then run
Code:
fastboot getvar cidnum
or
Code:
fastboot getvar cid
to get current CID
write them too
p.s. Create Goldcard (just in case)
Click to expand...
Click to collapse
Thank so much, I understood, thanks again.
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 found a easier way and safer way than hex edits. if people are still obsessed with there second CID's in the MISC partition. matching there main CID's instead of HEX editing you MUST have Eng-Hboot installed.
fastboot oem readbcid -command will tell you which cid you have there.
fastboot oem erasebcid - command will duh erase it. you can leave it blank If you wish
fastboot oem writebcid - Too anything you want HTC__001..... BS_US001......ETC
daddioj said:
I found a easier way and safer way than hex edits. if people are still obsessed with there second CID's in the MISC partition. matching there main CID's instead of HEX editing you MUST have Eng-Hboot installed.
fastboot oem readbcid -command will tell you which cid you have there.
fastboot oem erasebcid - command will duh erase it. you can leave it blank If you wish
fastboot oem writebcid - Too anything you want HTC__001..... BS_US001......ETC
Click to expand...
Click to collapse
Any dis advantages to eng-Hboot? Is the eng-hboot for the one? or for butterfly,dna?
Really nice find.
Or just flash a firmware.zip or ruu.. anything with an android-info.txt.
Magic.. they match the main cid after.
nugzo said:
Any dis advantages to eng-Hboot? Is the eng-hboot for the one? or for butterfly,dna?
Really nice find.
Click to expand...
Click to collapse
its made for the DNA at this moment
we cant boot with it installed. but the advantage is to use eng hboot commands you cant use with reg hboot. such as the commands I listed. along with many others such as wiping system to radio to recovery. etc usually I use eng hboot when I am ready to flash a RUU. but you can flash back to normal hboot. there are threads about it around
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.
Wanna convert to Dev Edition or EU Unlocked/Unbranded/GPE? There's a million question's and problem's constantly being posted about these conversion's. I have made this whole process as easy and painless as possible.As I have already done 90% of the work for you.Anyone should very easily be able to achieve full conversion and receive future ota's as well as return full stock.These are 100% clean stock's NO ROOT.Will boot directly to setup screen.These are done using TWRP backup to ensure complete and easy conversion.
How to convert-------
1...Select version,download and unzip,place folder in TWRP folder on sd.
2... Reboot to fastboot Change MID to required MID, instruction's can be found here-------->> thanks to @Shadowboy23 --->>> http://forum.xda-developers.com/showthread.php?t=2322820
A quick lesson on engineering HBoot if used to change MID. As stated on OP,your screen will go black DON'T PANIC!! Hold power button until you hear Windows chime and you will see HTC logo in oem ruu,then fastboot cmd can continue.
*****************************************************************************************************************************
2.5.... For a much easier CID/MID change without Eng Hboot thanks to @Wonders_Never_Cease. Download needed HBOOT from here--->> http://rumrunner.us/hboots/ It only needs to match needed provider,new hboot updates with firmware install. Install choosen Hboot,change MID/CID as needed. See commands at bottom.
******************************************************************************************************************************
3... Reboot to fastboot and flash respective firmware found here---------->> thanks to @godfirst for the collection --->>> http://forum.xda-developers.com/showthread.php?t=2419699
4...Flash backup,reboot and profit!!!!
**********************************************************************************************************************************************************************
Developer Edition Coversion/Target CID BS_US001 ota's will take with 11111111 / Target MID PN0712000 (Mandatory for ota)
Downloads-- 4.19.1540.9
Rom----- http://www.androidfilehost.com/?fid=23329332407580891
Stock Recovery for OTA--- http://www.androidfilehost.com/?fid=23329332407580889
*********************************************************************************************************************************************************************
EU Unlocked Unbranded Conversion/Target CID HTC_001 will take ota's on 11111111 / Target MID PN0710000 (Mandatory for ota)
Downloads-- 4.19.401.9
Rom---- http://www.androidfilehost.com/?fid=23329332407580890
Stock Recovery for OTA---- http://www.androidfilehost.com/?fid=23329332407580888
**********************************************************************************************************************************************************************
GPE Conversion/Target CID GOOGL001 will take ota on 11111111 / Target MID PN0712000 (Mandatory for ota) thanks to @graffixnyc for the RUU
Download---3.62.1700.1
Rom--->>
Stock Recovery for ota--->>
*********************************************************************************************************************************************************************
If I have made conversion easier for you,or you appreciate the effort. Please rate 5 star and maybe give a thanks.
**********************************************************************************************************************************
Fastboot commands for Hboot,CID,MID change Im expecting you to already know how to access adb and fastboot on your PC so commands are listed as i use them.
cd/android <--------- access to my adb fastboot
fastboot oem rebootRUU
fastboot flash zip Hboot.zip
fastboot oem writecid <---- not really needed stay with CID 11111111
fastboot oem writemid <--- Needed to OTA
fastboot erase cache
fastboot reboot.
Thanks for the thorough writeup, but this all is not needed....Simpler way is much safer and easier..could add these to your writeup....
Download/flash the appropriate hboot for your device, I used 2.24.408.8
http://rumrunner.us/hboots/
run commands as needed for changing cid/mid
fastboot oem writecid
fastboot oem writemid
I did this one 2 chinese versions without issue. I dont wish to see folks bricking their devices as the original way is a bit over whelming for some...this makes it even more painless and safer...
NO need for messing with engineer hboot
[email protected] said:
Wanna convert to Dev Edition or EU Unlocked/Unbranded? There's a million question's and problem's constantly being posted about these conversion's. I have made this whole process as easy and painless as possible.As I have already done 90% of the work for you.Anyone should very easily be able to achieve full conversion and receive future ota's as well as return full stock.These are 100% clean stock's.Will boot directly to setup screen.These are done using TWRP backup to ensure complete and easy conversion.
How to convert-------
1...Select version,download and unzip,place folder in TWRP folder on sd.
2... Reboot to fastboot Change MID to required MID, instruction's can be found here-------->> thanks to @Shadowboy23 --->>> http://forum.xda-developers.com/showthread.php?t=2322820
A quick lesson on engineering HBoot if used to change MID. As stated on OP,your screen will go black DON'T PANIC!! Hold power button until you hear Windows chime and you will see HTC logo in oem ruu,then fastboot cmd can continue.
3... Reboot to fastboot and flash respective firmware found here---------->> thanks to @godfirst for the collection --->>> http://forum.xda-developers.com/showthread.php?t=2419699
4...Flash backup,reboot and profit!!!!
**********************************************************************************************************************************************************************
Developer Edition Coversion/Target CID BS_US001 ota's will take with 11111111/Target MID PN0712000 (Mandatory for ota)
Downloads-- 4.19.1540.9
Rom----- http://www.androidfilehost.com/?fid=23329332407578288
Stock Recovery for OTA--- http://www.androidfilehost.com/?fid=23329332407578304
*********************************************************************************************************************************************************************
EU Unlocked Unbranded Conversion?Target CID HTC_001 will take ota's on 11111111/Target MID PN0710000 (Manatory for ota)
Downloads-- 4.19.401.9
Rom---- http://www.androidfilehost.com/?fid=23329332407578293
Stock Recovery for OTA---- http://www.androidfilehost.com/?fid=23329332407578306
*********************************************************************************************************************************************************************
If I have made conversion easier for you,or you appreciate the effort. Please rate 5 star and maybe give a thanks.
Click to expand...
Click to collapse
Thanks for the info. I will update OP shortly with newer info.
Updated Op with GPE info