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.
Related
Hi,
I have a tmobile mytouch 3g 1.2 (3.5mm jack phone). I tried to root my phone and it failed during the SYSTEM---UnZipping process. (it stuck there forever). I then looked at options of unrooting it. When I apply SAPPIMG.zip it says Main Version Older! Update Fail!
Then I reboot the phone in recovery mode (tried to reset to factory settings and then reboot). The phone gives me the below error upon startup. The only thing i can see is an notification bar.
the process android.process.acore has stopped unexpectedly. "FORCE CLOSE"
Please can someone help me how to get my phone working? Appreciate all your help!
If you go to tmobile.com then go to there forum under android development you will see a topic called how to unroot the mytouch. In that topic they have a link for the original sappimg .. download to your zip cars in the root of the card (no folders) then just boot into hboot and apply the sappimg. I have done it many times so I know it works. Then when you go to root your just us the universal androot method. Feel few to pm me i
ent from my HTC Magic using XDA App
Type this in fastboot:
Code:
fastboot getvar version-main
Then we can try to see if we can update it.
If not, you can always try to flash RUU.
The system starts, that's a good thing -> you have adb access!
Just don't go around and flash all kind of sapphire.nbh/zip...
Wait intil you have the right info :0)
I have had this problem and solved it. I would either get this acore stopped working error or just a loop in the boot screen. I think what caused this is there is not enough internal room for the ROM and gapps. Make sure you wipe everything. Do you have a nandroid backup? Can you get into recovery? Which recovery do you have installed? Do this, make a goldcard. Use fastboot to reroot the phone because you may have halfway unrooted it and made root useless. Boot into recovery and wipe. Install from sd any MyTouch ROM without Gapps. This should get you into the OS and now you can use other methods of getting your phone back. When I got here I used nandroid backup to get my phone back to a date it was when it worked and have had no problems since.
mumilover said:
Type this in fastboot:
Code:
fastboot getvar version-main
Then we can try to see if we can update it.
If not, you can always try to flash RUU.
The system starts, that's a good thing -> you have adb access!
Just don't go around and flash all kind of sapphire.nbh/zip...
Wait intil you have the right info :0)
Click to expand...
Click to collapse
I tried the command - fastboot getvar version-main
it just says < waiting for device > and then nothing happens...
also when i run the adb devices command, it does not display my devices. (But i have the number noted down when i tried to root the phone which failed...) can this number be used in any manner for anything
housry23 said:
I have had this problem and solved it. I would either get this acore stopped working error or just a loop in the boot screen. I think what caused this is there is not enough internal room for the ROM and gapps. Make sure you wipe everything. Do you have a nandroid backup? Can you get into recovery? Which recovery do you have installed? Do this, make a goldcard. Use fastboot to reroot the phone because you may have halfway unrooted it and made root useless. Boot into recovery and wipe. Install from sd any MyTouch ROM without Gapps. This should get you into the OS and now you can use other methods of getting your phone back. When I got here I used nandroid backup to get my phone back to a date it was when it worked and have had no problems since.
Click to expand...
Click to collapse
i did not take any nandroid backup ...i got into revovery boot...but whn i did the wipe clean option and reboot i get this error.
to make a gold card i would need to have the USB debugging enabled right? I am not able to go past the error screen (Home does not work, settings does not work )
and when i run the adb devices command, it does not display my devices. (But i have the number noted down when i tried to root the phone which failed...)
is there any other way to enable the USB Debugging as I am not able to open settings or even see anything on my phone...?
Would there be any option that's something like doing a System Restore to an earlier date on Windows OS on the computer?
please let me know the next steps...appreciate all of your help...
It's driver related.
Fix the drivers and try again to run the commands.
mumilover said:
It's driver related.
Fix the drivers and try again to run the commands.
Click to expand...
Click to collapse
You mean re-install the USB drivers for mytouch 3g? i tried that but still nothing happens...
Well you have to...
In fastboot mode this command shall give you the device nr .
Code:
fastboot devices
If not, the drivers are still bad!
You could also try to do a HARD RESET from hboot ( volume - together with power)...
mumilover said:
Well you have to...
In fastboot mode this command shall give you the device nr .
Code:
fastboot devices
If not, the drivers are still bad!
You could also try to do a HARD RESET from hboot ( volume - together with power)...
Click to expand...
Click to collapse
Thanks for the steps. I got the version details.
by executing the fastboot getvar version-main in fastboot mode.
version-main: 2.53.707.2
finished. total time: 0.001s
What will be the next steps...how to I update?
ganesh.raj.ms said:
Thanks for the steps. I got the version details.
by executing the fastboot getvar version-main in fastboot mode.
version-main: 2.53.707.2
finished. total time: 0.001s
What will be the next steps...how to I update?
Click to expand...
Click to collapse
Hey, i tried the below. can you please let me know if this is correct? and what do i do next?
userdebug-img-14721_1.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.0013
Baseband Version.....: 2.22.23.02
Serial Number........: HT03TPB01582
--------------------------------------------
checking product... FAILED
Device product is 'sapphire'.
Update requires 'trout'.
finished. total time: 0.042s
how do i try to rectify the checking product...FAILED???
OK....
Let's get the facts right.
You tried to root with wrong guide.
The sapphire.zip/nbh image you used if for the 32A.
How do i know that ?
Well the main version nr tells me that you have flashed this:
2.53.707.2 SEA WWE test-signed (from this page: http://forum.xda-developers.com/showthread.php?t=659403)
That's why you have troubles!
The solution....
I need all your fastboot info.. ALL.
Then i can figure out what to do. Or else i will work in the dark...
mumilover said:
OK....
Let's get the facts right.
You tried to root with wrong guide.
The sapphire.zip/nbh image you used if for the 32A.
How do i know that ?
Well the main version nr tells me that you have flashed this:
2.53.707.2 SEA WWE test-signed (from this page: http://forum.xda-developers.com/showthread.php?t=659403)
That's why you have troubles!
The solution....
I need all your fastboot info.. ALL.
Then i can figure out what to do. Or else i will work in the dark...
Click to expand...
Click to collapse
Is it the below that you want?
[FONT="]SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009,22:33:27[/FONT]
Yes...
You have the right radio/spl combo. That's good.
The problem is that your main version is set to high.
If you try to flash any RUU for the 1.2 magic, you will get main-version older error...
Even if you use a goldcard.
Do you still have access to adb?
Even for a little... then we can flash a custom recovery and get the system back.
Even if your system don't start up... as long you can boot more then 20 sec and you don't get reboots.
If not, then we have to flash a 32A sappimg.zip using a goldcard.
From there we flash custom recovery. Then eng spl. Then flash system,boot, userdata. Then flash the 1.2 spl... Then we are done :0)
So it's a long one... but first test if we have adb access.
Code:
adb devices
mumilover said:
Yes...
You have the right radio/spl combo. That's good.
The problem is that your main version is set to high.
If you try to flash any RUU for the 1.2 magic, you will get main-version older error...
Even if you use a goldcard.
Do you still have access to adb?
Even for a little... then we can flash a custom recovery and get the system back.
Even if your system don't start up... as long you can boot more then 20 sec and you don't get reboots.
If not, then we have to flash a 32A sappimg.zip using a goldcard.
From there we flash custom recovery. Then eng spl. Then flash system,boot, userdata. Then flash the 1.2 spl... Then we are done :0)
So it's a long one... but first test if we have adb access.
Code:
adb devices
Click to expand...
Click to collapse
adb devices does not give me anything...its not working
Does the computer recognise the device?
Maybe it's driver related...
PS: check your pm
My device is a HTC MAGIC 32A, the phone cid is HTC__038
Hey I had flashed Rogers RUU 2.1 update over a rom with old radio and old spl
The update failed and I had to take out the battery
Now my phone only opens in the ruu white screen where its written SAPPHIRE 32A SHIP S-ON
HBOOT- 1.76.0010 s-on H
CPLD-12
RADIO-3.22.20.17
Jan 14 2010,00:14:58
And there is a chip with a cross at the bottom
I have fastboot acces but have tried almost all the known commands but to no avail
TRIED FASTBOOT FLASH RECOVERY XXXX... but gives signature fail
fastboot flash zip rom.zip gives main version older in case of official roms and signature error even in extracted roms
fastboot boot recovery xxxx... nothing happens just after the cmd shows booting
tried fastboot erase recovery/system /booot all of them give remote not allow
I have tried to run other official ruu(all of these found here forum.xda-developers.com/showthread.php?t=659403 ) with goldcard butr all of them give error 140 bootloader version error and show main version older on phone screen
I have tried to run the official rogers 2.1 ruu again but it gives error 132- signature error
When running ruu the current device image shows version 3.54.631.7
Tried everything in this thread http://forum.xda-developers.com/showthread.php?t=793704&page=5
and this one
http://forum.xda-developers.com/showthread.php?t=824633
PLEASE HELP ME!!
Either a signed rom(hex edited) with image version greater than 3.54 or a way to get adb working or turn s-on to s-off through fastboot would do the trick
Or simply if somebody could tell me how to revive a phone with S-ON with rom version 3.54 using FASTBOOT Thanks
If you are getting an error main version older with goldcard, then it is not a goldcard. If you can get another goldcard, or still have the numbers to get another goldcard image and remake your goldcard it will work. I have been in the same position and remade the goldcard and it worked. I don't know why or if it happens all the time or with just certain brands, the goldcard no longer works after using it. I don't have a Kiingston only a Samsung microSD and have had to remake it twice. I would get the remote:not allow when trying to flash or boot recovery from fastboot, but when I remade my goldcard it worked.
housry23 said:
If you are getting an error main version older with goldcard, then it is not a goldcard. If you can get another goldcard, or still have the numbers to get another goldcard image and remake your goldcard it will work. I have been in the same position and remade the goldcard and it worked. I don't know why or if it happens all the time or with just certain brands, the goldcard no longer works after using it. I don't have a Kiingston only a Samsung microSD and have had to remake it twice. I would get the remote:not allow when trying to flash or boot recovery from fastboot, but when I remade my goldcard it worked.
Click to expand...
Click to collapse
Hey I dont have a spare phone to check the above, but with the current goldcard I have I am able to pass the CID check with any rom(otherwise get cust id error) but am not able to get past the Main version check so will making a goldcard again help
hEY MY CURRENT ROM VERSION IS 3.54 AND THE OTHER RUU'S AVAILABLE HAVE MAX UPTO 3.05 AND I AM UNABLE TO DOWNGRADE EVEN WITH A PROPER GOLD CARD. PLEASE HELP!!
i have same problem, did you fixed?
primux said:
i have same problem, did you fixed?
Click to expand...
Click to collapse
Almost, got access to adb with su priveleges but by mistake flashed wrong flash_image file and ruined it, now my phone is lying with HTC care who are thieves and say the "Phone is EXITING while we are trying to update your software" then they call me and say that that they will have to change my motherboard despite my hardware being completely fine(I think they have taken out all my original parts and initially say my warranty has expired, then do something that makes my phone not even boot and then say i have warranty, just hope they give back my phone soon ) ..
My advice would be to try the below else perform JTAG as HTC care are greedy, unprofessional, illiterate cheats.
Type fastboot oem boot or fastboot boot oem while in fastboot and your phone will boot and keep restarting every 2 min
Good Luck
i see, can you tell me how you got adb access? i just have RUU MODE and when i tried to upload a new flash stuck in SYSTEM - unzipping, my phone it's same version as yours. i'll appreciate any help
The whole story is a little bit long.
I still can access to fastboot. On the RUU screen, I can read the following information:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0008(SAPP10000)
CPLD-12
RADIO-3.22.20.17
Nov 3 2009, 15:56:29
Here is how it happened. I flashed the radio to 3.22 and run a wrong RUU file (RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe). The problem comes: after unsuccessfully flash the RUU file (as the radio in the RUU is 6.35), the security is turned ON (S-ON). Those RUU files with radio 3.22.XX have different version of SPL from 1.76.XXX. I cannot find a RUU file with SPL 1.76.008 and radio 3.22.XX. Therefore, I cannot use any RUU file to change the situation (I got a goldcard).
The security is turned on and I cannot change the radio, SPL or recovery in fastboot (cannot pass the infoSignature checking).
Now I still can access to fastboot (such as fastboot devices).
I don't know why I cannot use fastboot to boot a recovery (fastboot boot recovery-RA-sapphire-v1.7.0H.img). I was able to send the recovery img to the device. But the booting of recovery takes for ever.
I can only enter fastboot mode now using any combination of buttons.
Please give your comment and help to solve this.
Thank you very much!
htchd2sg said:
The whole story is a little bit long.
I still can access to fastboot. On the RUU screen, I can read the following information:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0008(SAPP10000)
CPLD-12
RADIO-3.22.20.17
Nov 3 2009, 15:56:29
Here is how it happened. I flashed the radio to 3.22 and run a wrong RUU file (RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe). The problem comes: after unsuccessfully flash the RUU file (as the radio in the RUU is 6.35), the security is turned ON (S-ON). Those RUU files with radio 3.22.XX have different version of SPL from 1.76.XXX. I cannot find a RUU file with SPL 1.76.008 and radio 3.22.XX. Therefore, I cannot use any RUU file to change the situation (I got a goldcard).
The security is turned on and I cannot change the radio, SPL or recovery in fastboot (cannot pass the infoSignature checking).
Now I still can access to fastboot (such as fastboot devices).
I don't know why I cannot use fastboot to boot a recovery (fastboot boot recovery-RA-sapphire-v1.7.0H.img). I was able to send the recovery img to the device. But the booting of recovery takes for ever.
I can only enter fastboot mode now using any combination of buttons.
Please give your comment and help to solve this.
Thank you very much!
Click to expand...
Click to collapse
Many of this was answered, search the forum.
Here is the thing you have wrong spl radio combination,you have perfected spl. You can do a fastboot boot xxxxxx.img and enter recovery. Then you must flash eng spl 1.33.2010.And you will be unbricked
Thank you for the reply.
I tried fastboot recovery-RA-sapphire-v1.7.0H.img. But after the sending of the image is over, it will stay in booting for ever. I don't understand why I cannot boot the recovery.
htchd2sg said:
Thank you for the reply.
I tried fastboot recovery-RA-sapphire-v1.7.0H.img. But after the sending of the image is over, it will stay in booting for ever. I don't understand why I cannot boot the recovery.
Click to expand...
Click to collapse
You cant boot that recovery try the one hero recovery Ra-magic1.6.2H smthing recovery
I downloaded the 1.6.2 recovery from http://forum.xda-developers.com/showpost.php?p=4549551&postcount=1
But I still cannot boot the recovery(I can send the recovery)
htchd2sg said:
I downloaded the 1.6.2 recovery from http://forum.xda-developers.com/showpost.php?p=4549551&postcount=1
But I still cannot boot the recovery(I can send the recovery)
Click to expand...
Click to collapse
Hmm did you try the sappimg.nbh to restore your magic???
Updated: I tried to use sappimg.nbh in fastboot mode. However, it responses that the main version is older. This is because I have run the RUU (RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_No Driver.exe), whose main version is 3.05 while the sappimg.nbh is older than this number.
Now I can access fastboot and the hboot, but not the recovery. Of course, I cannot boot the android OS either. Is there a method to root just in the fastboot mode? I have the security turned on (S-ON)?
Anyone got suggestion? Thanks!
Can anyone help on this? really get frustrated
htchd2sg said:
Updated: I tried to use sappimg.nbh in fastboot mode. However, it responses that the main version is older. This is because I have run the RUU (RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_No Driver.exe), whose main version is 3.05 while the sappimg.nbh is older than this number.
Now I can access fastboot and the hboot, but not the recovery. Of course, I cannot boot the android OS either. Is there a method to root just in the fastboot mode? I have the security turned on (S-ON)?
Anyone got suggestion? Thanks!
Click to expand...
Click to collapse
You need to create a goldcard www.theunlockr.com at How to's and then use sappimg.nbh
I got gold card already. . Thank you!
Do you solve this? I got the exactly problem with you =(
I actually had this same issue months ago and nothing worked. Unfortunately I ended up getting another phone.
Sent from my SGH-T959 using XDA App
r3v4N said:
I actually had this same issue months ago and nothing worked. Unfortunately I ended up getting another phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
What a bad news =( I had sent this phone to repair, but all of their experts cannot fix as well.
That's lame.... did you try the unroot process?
Sent from my SGH-T959 using XDA App
You could try unbricking by flashing the Rogers or Brazilian Android 2.1 RUU. The main version is newer and a goldcard should make it work.
Please make sure your battery is full and that you have a PROPER GOLDCARD!!! Otherwise this will most likely fail.
I've uploaded the sappimg to http://www.multiupload.com/WO0S35S53S
Rename it to sappimg.zip, copy it to the root of your SD card and boot into fastboot (vol-down and power). That SHOULD fix your phone. Then again, it could also brick it even worse, but what do you have left to lose?
After loaded sappimg, it checking sappimg, then went back to HBOOT. Nothing happened. I've tried to recreate my gold card, no luck with it =(
How To Flash A Different HBoot On The Go. I miss the good ol days when we could just flash an hboot on the go via the bootloader itself. Looks like this is the closest were getting for now.
Requirements:
S-Off
Terminal Emulator (Get it free from Google Play)
Commom ADB/Fastboot experience to understand this...
On the device, open Terminal Emulator
Step 1:
Run:
su
Step 2:
Run:
cd sdcard
Step 3:
Run:
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/mmcblk0p12
Notes:
Replace "LOCATIONOFHBOOT" with the actual location it is stored on. For example, the 3 Hboots I have are stored on /sdcard/System/HBoot/
Replace "HBOOT.img" with the actual name of the hboot file. Example: enghboot.nbo or stock_hboot.img
Final example for my device would be: dd if=/sdcard/System/Hboot/hboot.img of=/dev/block/mmcblk0p12
KEEP IN MIND, ONCE YOU FLASH AND BOOT INTO THE ENG HBOOT, YOU WILL NOT BE ABLE TO BOOT BACK UP UNTIL FLASHING ANOTHER HBOOT VIA FASTBOOT.
Sent Via My HTC One, On The Now Network By Sprint!
cant you just do fastboot flash hboot location or something?
Why cant you use a eng hboot to boot android?
Do you have a eng hboot for m7?
tjsooley said:
cant you just do fastboot flash hboot location or something?
Why cant you use a eng hboot to boot android?
Do you have a eng hboot for m7?
Click to expand...
Click to collapse
You can run
fastboot oem rebootruu
fastboot oem flash hboot hboot.img but that requires a computer, where as this method is as titled, On The Go.
The eng hboot compatible with our device can't load emmc.
I'll link you to it in a sec...
Sent Via My HTC One, On The Now Network By Sprint!
Whats the likelyhood that a eng hboot will be released that will work 100% with are device and load emmc
tjsooley said:
Whats the likelyhood that a eng hboot will be released that will work 100% with are device and load emmc
Click to expand...
Click to collapse
I couldn't have an answer for you.
Here is the ENG-Hboot
http://forum.xda-developers.com/showthread.php?t=2155214
Sent Via My HTC One, On The Now Network By Sprint!
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.