Related
SAPPHIRE UNKNOWN 32A SHIP S-ON G
HBOOT-1.33.0006 (SAPP50000)
CPLD-12
RADIO-2.22.23.02
I flashed the 2.22.23.02 through fastboot by mistake and now I can't get into recovery mode, or flash any other radios onto the phone. The fastboot menu is the only thing I can get to on the phone.
I tried reflashing the 2.22.23.02 again but it won't go through...
Anyone have any ideas on what I can do to unbrick it?
Edit: Tried sappimg.nbh via volume down and power button but i get a Model ID error. Now i can't fastboot anything over to my phone.
Edit: Flashed the sappimg.nbh, sappimg 2.16.707.3, sappimg 2.53.707.2, via gold card but I now get the error: Main Version is older!
I have answered similar questions before...
Use the search function.
But to get you started here is a quick solution.
1) flash eng spl that starts with 1.33.20XX where XX can be 05,09 or 10.
Restart into fastboot.
2) flash the right spl/radio/recovery combo.
This is confirmed to work....
Next time post ALL fastboot info... there are some info mission in your post!
all the fastboot info...
SAPPHIRE UNKNOWN 32A SHIP S-ON G
HBOOT-1.33.0006 (SAPP50000)
CPLD-12
RADIO-2.22.23.02
I have just tried flashing hboot-1.33.2010 via fastboot.
However, I get the error message:
sending 'hboot' (512 KB)... FAILED (remote: not allow)
do this:
----- If you boot into fastboot and have issues with "fastboot:remote not allow", then your SPL won't work. Upgrade to Engineering SPL before continuing.
----- If you do not have an Engineering SPL, download 1.33.2010 and flash through recovery before starting this procedure. Flash the SPL update.zip like any other update.zip file.
in http://forum.xda-developers.com/showthread.php?t=605239
Unfortunately... I can't boot into recovery either, nor can i push a recovery image to the phone. I get the same error: "fastboot:remote not allow".
ok... you are very limited...
Do this:
Find a suitable sappimg.nbh... Not sappimg.zip...
Use this which i just uploaded for you:
http://rapidshare.com/files/421772202/SAPPIMG.nbh
Using your goldcard flash the sappimg.nbh in fastboot.
The sappimg.nbh does not need any unzipping... it's a complete img of the nand and overwrites everything.
I can't seem to find the answer to this anywhere....
is there a way to create a goldcard at this point for me?
I can't get into debug mode on the phone (for obvious reasons) and therefore can't do adb....
Find ANY android device and make a goldcard...
Then use the goldcard on your device...
wouldn't suppose anyone have the goldcard.img from their email that they could send me...
1)Download the -G magic RA recovery
2) rename it to recoveryG.img
3) run 'fastboot boot recoveryG.img' (with the phone in fastboot mode)
4) allow recovery to boot then run the following adb commands
Code:
adb push recoveryG.img /tmp/recoveryG.img
adb flash_image recovery /tmp/recoveryG.img
5) Now power down the phone
6) boot into recovery by holding home+power
10) flash 1.33.2009 or 1.33.2010
Now you will have fastboot again
Most likely you will want to find and flash via fastboot radio 3.22.20.17 if you are not a Rogers/Fido customer or have signed the e911 wavier, otherwise you want 3.22.26.17..
After flashing the 3.x radio flash RA -h recovery via fastboot (and while in fastboot run 'fastboot erase system -w'); this will let you flash the ebi1 rom of choice
I just downloaded the recovery-RA-sapphire-v1.7.0G.img
renamed it so recoveryG.img.
When i try to run the command: fastboot boot recoveryG.img
I get the error message:
downloading 'boot.img'...FAILED (remote: not allow)
Then its best to just install the official e911 ruu from rogers and re-root
I have tried that, but it doesn't work...
What's your fastboot info?
Sent from my HTC Magic using XDA App
isn't the info on my first post the fastboot info?
bigbrotherbear said:
isn't the info on my first post the fastboot info?
Click to expand...
Click to collapse
Yes, I'm also not sure why people are ignoring that fact that you can't use fastboot either :-S
My bad, using my phone and completely missed the first page.
EDIT: I think mum was on the right track. Your going to need a goldcard. No one will be able to send you their .img because its SD card specific. You don't know anyone with a Android based phone?
Sent from my HTC Magic using XDA App
Looks like i'm getting progress....?
I have a gold card now thanks to my friend, however...
when I try to flash the SAPPIMG.nbh I get a Main Version is older!
I also tried the 2.53.707.2 SAPPIMG.zip and I still get this error.
I also just tried 2.16.707.3 SAPPIMG.zip and I still get this error.
YOU ARE STILL MAKING THE GOLDCARD THE WRONG WAY...
You should not get that error msg...
Try to remake the goldcard.
Did it on two different SD cards, the same way I did it before to get my phone off perfected SPL... not sure what I could've done to do it wrong this time around.....
a mmc CID can't change right?
followed this guide:
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
This is wht My Fender LE edition says in fastboot mode. I can not load into receovery or update using sappimg.zip. It always says Model id incorrect! I have a gold card but its not working at all now.
Everytime i start the phone up its gets stuck at the "HTC MAGIC" logo!!!
Anyhelp??
Matteo8810 said:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
This is wht My Fender LE edition says in fastboot mode. I can not load into receovery or update using sappimg.zip. It always says Model id incorrect! I have a gold card but its not working at all now.
Everytime i start the phone up its gets stuck at the "HTC MAGIC" logo!!!
Anyhelp??
Click to expand...
Click to collapse
Your radio doesn't look right. Did you flash a radio?
C0dy said:
Your radio doesn't look right. Did you flash a radio?
Click to expand...
Click to collapse
yes,, it was from a post in this section but i can no longer find it
Matteo8810 said:
yes,, it was from a post in this section but i can no longer find it
Click to expand...
Click to collapse
Well, the thing is, the only radio that is compatible with the Fender/1.2 is the stock raido. At this point, it's a brick. Put the phone is fastboot mode, download the Android SDK, go cmd (if you're running Windows, and assuming you installed it to the root of the C drive) and then type:
cd\
cd AndroidSDK\tools
fastboot devices
If you get a 'waiting for device', it's done for. Now, if you do get it to show up, download the original radio, SPL, and a custom recovery, put them in the AndroidSDK/tools folder, and flash them with the following commands:
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0
fastboot flash recovery recovery.img
fastboot reboot bootloader
If you need help, free free to PM me.
C0dy said:
Well, the thing is, the only radio that is compatible with the Fender/1.2 is the stock raido. At this point, it's a brick. Put the phone is fastboot mode, download the Android SDK, go cmd (if you're running Windows, and assuming you installed it to the root of the C drive) and then type:
cd\
cd AndroidSDK\tools
fastboot devices
If you get a 'waiting for device', it's done for. Now, if you do get it to show up, download the original radio, SPL, and a custom recovery, put them in the AndroidSDK/tools folder, and flash them with the following commands:
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0
fastboot flash recovery recovery.img
fastboot reboot bootloader
If you need help, free free to PM me.
Click to expand...
Click to collapse
Fastboot devices "HT011PB041145"
But everything else says (remote: notallow)
Fastboot commands aren't going to work unless you can get an engineering SPL loaded up with S-OFF (Security Off). Try making your goldcard again and re-rooting using the guide in my signature.
This is in the wrong forum. It should have been posted in General not Development.
DonJuan692006 said:
Fastboot commands aren't going to work unless you can get an engineering SPL loaded up with S-OFF (Security Off). Try making your goldcard again and re-rooting using the guide in my signature.
This is in the wrong forum. It should have been posted in General not Development.
Click to expand...
Click to collapse
goldcard created successfully... its the same one i had from when i first rooted my phone, but now its not working.. all i'm getting is wrong id model
My friend handed me their MyTouch 2.1 to fix and I don't know what to do with this one.
When I gave them the phone it had SPL 1.33.2010 and the old 3.22 radio. They were on Cyanogen 6.
He wanted to put Gingerbread on the phone so he upgraded the radio to 6.35.10.18 however recovery went missing. He could flash different recoveries from fastboot but it wouldn't boot in to recovery. It just hung at the green MyTouch screen.
He tried downgrading the radio thinking that would fix the issue with recovery not working. It didn't. As a last resort he flashed the Saphire.nbh. That restored his radio and hboot to a lower version however there still is no recovery installed on the phone and now there is no access to flash via fastboot.
Info shows:
SAPPHIRE UNKNOWN 32A SHIP S-ON G
HBOOT-1.33.006 (SAPP31000)
RADIO-2.22.28.25
May 27 2009, 19:06:41
Any help would be greatly appreciated!
Trav1sty said:
My friend handed me their MyTouch 2.1 to fix and I don't know what to do with this one.
When I gave them the phone it had SPL 1.33.2010 and the old 3.22 radio. They were on Cyanogen 6.
He wanted to put Gingerbread on the phone so he upgraded the radio to 6.35.10.18 however recovery went missing. He could flash different recoveries from fastboot but it wouldn't boot in to recovery. It just hung at the green MyTouch screen.
He tried downgrading the radio thinking that would fix the issue with recovery not working. It didn't. As a last resort he flashed the Saphire.nbh. That restored his radio and hboot to a lower version however there still is no recovery installed on the phone and now there is no access to flash via fastboot.
Info shows:
SAPPHIRE UNKNOWN 32A SHIP S-ON G
HBOOT-1.33.006 (SAPP31000)
RADIO-2.22.28.25
May 27 2009, 19:06:41
Any help would be greatly appreciated!
Click to expand...
Click to collapse
You can access android now? You need to root it again and install recovery after that eng spl and radio 3.22
WoblyGoblin said:
You can access android now? You need to root it again and install recovery after that eng spl and radio 3.22
Click to expand...
Click to collapse
I Can't access the operating system either. it just sits at the green MyTouch screen. The only thing I have access to is Fastboot and hboot.
Trav1sty said:
I Can't access the operating system either. it just sits at the green MyTouch screen. The only thing I have access to is Fastboot and hboot.
Click to expand...
Click to collapse
If you can access fastboot you should be ok.
Download a copy of clockworkmod 2.5.0.7 or amon-ra recovery
Make sure you have android sdk on your computer and a copy of fastboot installed in the tools directory on your computer. Copy the recovery into your tools folder on your computer and rename it recovery.img
Boot the phone into fastboot and connect it to the computer.
Open a terminal on your computer and run "fastboot devices" and make sure it sees the phone, you should get something back like HXXXXXXXX
Then just flash it over.
If I remember correctly the command is
fastboot flash recovery /android-sdk/tools/recovery.img
(that is assuming your android-sdk is in a directory called android-sdk and the recovery.img file is in tools)
fastboot reboot
That will get recover back on the phone. From there with either clockwork or amon_ra you should be able to reflash a rom
cyberstoic said:
If you can access fastboot you should be ok.
Download a copy of clockworkmod 2.5.0.7 or amon-ra recovery
Make sure you have android sdk on your computer and a copy of fastboot installed in the tools directory on your computer. Copy the recovery into your tools folder on your computer and rename it recovery.img
Boot the phone into fastboot and connect it to the computer.
Open a terminal on your computer and run "fastboot devices" and make sure it sees the phone, you should get something back like HXXXXXXXX
Then just flash it over.
If I remember correctly the command is
fastboot flash recovery /android-sdk/tools/recovery.img
(that is assuming your android-sdk is in a directory called android-sdk and the recovery.img file is in tools)
fastboot reboot
That will get recover back on the phone. From there with either clockwork or amon_ra you should be able to reflash a rom
Click to expand...
Click to collapse
Yeah that's not going to work.
@ the OP, since you have a perfected SPL you'll need to create a goldcard and flash an engineering SPL to the phone with it. Then you can do the steps from above. Secondly, since you have the 6.35 radio you'll have to flash Amon Ra's recovery for the Hero, version 1.6.2.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Thanks DonJuan692006. I went hunting for the goldcard I used to originally root his phone. I was able to get the original sappimg.nbh installed on the phone. Fortunately for me it was still on the card.
Info now shows:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
RADIO-2.22.23.02
Oct 21 2009, 22:33:27
Now that the phone is functional I can fix it for him. Thanks for the help everyone.
Looks like the I have no access to the SD Card now in the rom. It says Removed SD Card. I've tried 5 different cards 1GB-16GB and it doesn't see any of them.
Interestingly it says "recovery can't mount /dev/block/mmcblk0" when I try and flash an update.zip from recovery. This it turning out to be very frustrating.
I am sorry for making multiple threads, I am so lost, I was asking the wrong questions.
This is my phones information when I did 'power down + power on'
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT- 1.33.0013 (SAPH31000)
CPLD-13
RADIO2.22.28.25
OCT 21 2009,22:33:27
HBOOT
<BACK> FastBoot Mode
Can I just flash any Hard SPL I want without worry?
No. the only spl that works fully on that phone is 0013 or 0013d
Sent from my Gingerbread on Sapphire using XDA Premium App
gotgohan said:
Can I just flash any Hard SPL I want without worry?
Click to expand...
Click to collapse
Well... you can flash the 1.33.2010 eng spl to do some stuff. But if you want a fully functional device, you have to flash the 0013 or 0013d spl as tvall stated.
tvall said:
No. the only spl that works fully on that phone is 0013 or 0013d
Sent from my Gingerbread on Sapphire using XDA Premium App
Click to expand...
Click to collapse
So I just download 0013 or 0013d spl and just flash it in recovery correct?
Then I will have a better recovery, thus making it easier to install radios, and maybe even Rom's?
no.... you must need an eng spl... the 1.33.2010 or something.
The 0013 and 0013d radios are almost exactly the same. to flash roms download rom manager from the market. Them use that to get clockworkmod recovery. You flash roms from that
Sent from my Gingerbread on Sapphire using XDA Premium App
Here are my questions now:
Can I install Radio with Rom Manager?
Can I install SPL with Rom Manager?
If not, I read this: http://forum.xda-developers.com/showthread.php?t=605239. How do I do a full backup with nandroid or w/e it is.
As I think I know what it means, this is what I did:
I installed that app 'Rom Manager, then installed clockword' but when I did it the first time I clicked the 32B one on accident first, so I redid it with 32a one. It gave me the option of the 2. Now when I tried to make a backup with the app, it would restart, and just sit at the mytouhc screen =( I messed up? The phone still works, I just had to pull battery.
I even tried using RA 1.7 from the ROM manager and it still sits at green screen if I boot in recovery =/
Sigh, so I tried bypassing Rom manager by just using SDK/ADB to install the recovery I wanted...
I try getting into fastboot from my pc, and it says the phone isn't connected. I tried reinstalling the usb drivers MULTIPLE times. I have windows xp, when I go to fastboot it asks to install a separate driver than when the phone is booted up.
The driver is called: #USB\VID\0BB4&PID_0FFF.DeviceDescRelease%. It will install this but it doesn't do jack
If you need fastboot flash an eng spl temporarily. But you need a recovery to do that.. You might be able to do it in adb... Look at the stickies.
Sent from my Gingerbread on Sapphire using XDA Premium App
Can you give me a link to the two files I should use? I am sorry for being bothersome, but I just know I will eff up if I search the files on my own =/
You could try installing a recovery from terminal on your device. Get a terminal emulator from the market and then follow the directions in Amon_ra's recovery post. That way you wouldn't need to change spl or use rom manager. Hope that helps.
Tried this, got passed SU, but it says this:
flash_image: not found after typing flash_image recovery /sdcard/recovery-RA-sapphire.v1.7.0H
Copy recovery-RA-passion-v2.2.1.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-sapphire.v1.7.0H(press enter)
reboot recovery(press enter)
The file you copied to your sd and what you type into the term should be the same. If you have "passion" on your sd card and type in "sapphire" in the term that's the problem. The sapphire recovery is the one you want for your device.
Actually I renamed the file to recovery.img to make it easy to type in. is that a problem?
Sigh I wish I could just figure out why when I put the phone into fastboot mode, then hook the phone to the PC that the PC will not see the phone when I type adb devices... wtf?
When I went through SDK and installed google usb driver rev 4 it seemed to download, but its not showing up in my directory folder... I am so aggravated atm
Okay I got this far:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Michele>cd c:\
C:\>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.
C:\>fastboot
C:\>androidsdk\tools
'androidsdk\tools' is not recognized as an internal or external command,
operable program or batch file.
C:\>androidsdk\tools
'androidsdk\tools' is not recognized as an internal or external command,
operable program or batch file.
C:\>androidsdk\tools\
'androidsdk\tools\' is not recognized as an internal or external command,
operable program or batch file.
C:\>cd c:\androidsdk\tools
C:\androidSDK\tools>adb devices
List of devices attached
C:\androidSDK\tools>cd c:\
C:\>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (status read failed (Too many links))
finished. total time: 35.609s
C:\>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (remote: not allow)
finished. total time: 0.000s
C:\>
If I understand it correctly you need and engineering spl to use most fastboot functions that's why I suggested the term install of recovery. What you type into the term has to be what the file is called on your sd so if you changed the name, you type in what you changed the name to.
i.e. #flash_image recovery /sdcard/recovery.img but the recovery you should be installing is the sapphire one NOT the passion one.
Sir I have been doing what you are suggesting right now. It consistently says not found for the emulator, or if I do it via fastboot. Just says remote: not allow.
I put a sappimg.zip file into my sd card and when into fastboot mode. I am currently waiting for it to load which I got the ZIP from http://forum.xda-developers.com/showthread.php?t=547133: it seems after you do this the fastboot will work?
Though I have no idea what this sappimg.zip is doing atm, I have been getting antsy, so I probably just ****ed my phone... What evs we shall see when this thing finishes updating.
I am worried now. Its taking hella long to boot up my device... god I wish I wasn't so impatient, I probably just effed my phone by doing that sappimg
gotgohan said:
Sir I have been doing what you are suggesting right now. It consistently says not found for the emulator, or if I do it via fastboot. Just says remote: not allow.
I put a sappimg.zip file into my sd card and when into fastboot mode. I am currently waiting for it to load which I got the ZIP from http://forum.xda-developers.com/showthread.php?t=547133: it seems after you do this the fastboot will work?
Though I have no idea what this sappimg.zip is doing atm, I have been getting antsy, so I probably just ****ed my phone... What evs we shall see when this thing finishes updating.
I am worried now. lol
Click to expand...
Click to collapse
that guide says its for the original mytouch 3g. if i remember correctly you have the 1.2.. theres a huge risk of bricking your phone now
Well my phone isn't bricked, but the touch screen doesn't work =/
This is where I got the idea:http://forum.xda-developers.com/showthread.php?t=548218 so I searched sappimg.zip
Then I got that other link so I just downloaded that sappimg.zip, what sappimg.zip should I be using?
lol I ****ed myself over so bad...
Here is where my phone is atm.. it boots up no idea what the rom is, but it tells me the info:
1.5
Baseband Version
Radio 3.22.20.17
kernal
2.6.27-cb85e129
2.53.707.2 146733 CL#37318 test-keys
Not a clue how to fix what I just did to myself =/
Try and get back to stock. There is a sappimg.zip somewhere that I used once. I'll find a link.
Or try and use fastboot. If it works then you can flash the correct spl, radio, and custom recovery. Ill get you some links when I get on the computer next
Sent from my Gingerbread on Sapphire using XDA Premium App
gotgohan said:
Well my phone isn't bricked, but the touch screen doesn't work =/
This is where I got the idea:http://forum.xda-developers.com/showthread.php?t=548218 so I searched sappimg.zip
Then I got that other link so I just downloaded that sappimg.zip, what sappimg.zip should I be using?
lol I ****ed myself over so bad...
Here is where my phone is atm.. it boots up no idea what the rom is, but it tells me the info:
1.5
Baseband Version
Radio 3.22.20.17
kernal
2.6.27-cb85e129
2.53.707.2 146733 CL#37318 test-keys
Not a clue how to fix what I just did to myself =/
Click to expand...
Click to collapse
if you have fastboot working then follow this guide http://forum.xda-developers.com/showthread.php?t=831139
it will get you to a custom recovery and the spl and radio i recommend using.
if you still dont have fastboot then flash the spl from here
http://www.4shared.com/file/E2zhvzIr/SAPPIMG_Sapphire_T-Mobile_US_2.html
and re-root
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.