My phone just boots right to fastboot. Is there anyway to fix this?
There are two possible solutions, the first one requires an Engineering SPL, and the other possibly a goldcard.
1. If you have an Engineering SPL then you can just use the command "fastboot flash recovery recovery.img" and then flash a ROM from that recovery.
2. If you don't have an Engineering SPL you can copy a SAPPIMG.zip file to your SDCard which will automatically flash the phones' radio,spl,recovery,splash,boot,data,system...and what not, restoring it to an un-rooted state.
fastboot info
hockeyadc said:
My phone just boots right to fastboot. Is there anyway to fix this?
Click to expand...
Click to collapse
What do you c on your screen?
Post it all here... then we can help you :0)
The good news is as long you have fastboot, your phone IS NOT BRICKED :0)
Stuck in Fastboot after attempting to flash new CM from ROM Manager
I have always manually installed through Amon RA, but I downloaded ROM Manager from the market and tried to install the new stable CM 6.0. I was stuck with the T-Mobile G1 screen for 20 minutes before attempting to reboot into recovery (removing the battery and holding down Home+Power). It went back to the G1 screen.
I can get to Fastboot (Power+Camera), but that's it. I'm not sure where to go from there. I don't know how to get back to recovery or interact with my phone through USB connection to my computer. Can someone help? All I see in Fastboot is what is below. Pressing numbers on my keypad on my phone does nothing.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA1000)
CPLD-4
RADIO-2.22.23.02
APR 20 2009, 15:30:43
HBOOT
Parsing...[DREAIMG.nbh]
[1] BOOTLOADER
[2] RECOVERY
[3] BOOT
[4] SPLASH1
[5] SYSTEM
[6] USERDATA
[7] RADIO_V2
Do you want to start update?
<ACTION> Yes
<POWER> No
graymoment said:
I have always manually installed through Amon RA, but I downloaded ROM Manager from the market and tried to install the new stable CM 6.0. I was stuck with the T-Mobile G1 screen for 20 minutes before attempting to reboot into recovery (removing the battery and holding down Home+Power). It went back to the G1 screen.
I can get to Fastboot (Power+Camera), but that's it. I'm not sure where to go from there. I don't know how to get back to recovery or interact with my phone through USB connection to my computer. Can someone help? All I see in Fastboot is what is below. Pressing numbers on my keypad on my phone does nothing.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA1000)
CPLD-4
RADIO-2.22.23.02
APR 20 2009, 15:30:43
HBOOT
Parsing...[DREAIMG.nbh]
[1] BOOTLOADER
[2] RECOVERY
[3] BOOT
[4] SPLASH1
[5] SYSTEM
[6] USERDATA
[7] RADIO_V2
Do you want to start update?
Yes
No
Click to expand...
Click to collapse
You would be better off asking in the G1 forums since this one is for the myTouch/HTC Magic one.
Sent from my HTC Magic using XDA App
Related
Hi all,
Hopefully someone knows the answer to this one. I am completely screwed here and need some help.
I rooted my MyTouch 3G 3.5mm (32a) with no problems and tried several ROMS. So, I was going to try a ROM with a required radio and tried following this http://forum.xda-developers.com/showthread.php?t=605239 to do so.
It seemed ok, but then all heck broke loose.
Now I am stuck with the following:
HBOOT-1.33.2010
CPLD-13
RADIO-3.22.20.17
And nothing else.
I tried to unroot it and everything I could think of. That was probably a mistake (#2) because that replaced the recovery. So, now I can FASTBOOT and that's it.
If I try to replace the SPL or recovery or anything, I get a "Signature Verify Fail" from ADB and if I try using the SD card, it loads the img, checks it, and then does nothing.
Any ideas?
Your SPL is perfected so you cannot fastboot. Do you have a recovery that you can boot into?
As far as your fast boot problem goes look at this :
http://forum.xda-developers.com/showthread.php?t=548218
Click to expand...
Click to collapse
Does that translate into "I am screwed"?
can you enter any kind of boot, try volume + power, home + power, if you can, then use droid explorer to reflash the system
Do you a recovery you can boot into?
No recovery. :-(
I can get into the system via down vol+Power and Back+Power, but that's it.
I'll see if Droid Explorer can see anything.
From what I see, Droid Explorer requires the system be booted.
TheForgotten said:
Your SPL is perfected so you cannot fastboot. Do you have a recovery that you can boot into?
As far as your fast boot problem goes look at this :
Click to expand...
Click to collapse
Will I tried that to see if it would work. It actually gives me the option to start the flash.
The first section to flash is SYSTEM. It starts unzipping and stops right there and hangs.
Oh, I am not sure if this changes things, but the entire top data when at FASTBOOT is:
SAPPHIRE UNKNOWN 32A ENG S-ON H
HBOOT-1.33.2010 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
Jun 2 2009, 17:27:03
Any ideas or advice?
Have you tried entering recovery through AndroidSDK?
If you mean
"fastboot boot recovery.img", yeah. Is there a good recovery img I should use?
It doesn't seem to do anything when I try it. No error. It appears to work, but the phone does nothing.
Armon_Ra's recovery Heres a link: http://forum.xda-developers.com/showthread.php?t=530492. You have a 3.22 version radio so dont use the Hero recovery like he tells you even though you have a 32a (hero version is meant for 6.35 RaDIO)
Hi guys/gals, I know I did a stupid thing which I downloaded a wrong SAPPIMG.zip for breaking the perfect SPL, my Magic is a 32A device and the original SPL version should be a "H" instead of "G".
Now after flashing the sappimg.zip, my phone's SPL + Radio info as below:
SAPPHIRE UNKNOWN 32A SHIP s-ON G
HBOOT-1.33.0006 (SAPP10000)
CPLD-12
RADIO-2.22.19.26I
May 27 2009, 19:06:41
So... I tired to use fastboot method to boot to recovery, it shows remote not allow. And then, I tired to use the gold card method to flash the Europe RUU by using the rom1.zip renaming as sappimg.zip, I've also tried the Roger one
Everything is going fine but I got the Partition Update Fail, message like below:
[1] BOOTLOADER - OK
[2] RADIO V2 - OK
[3] SPLASH1 - OK
[4] RECOVERY - OK
[5] BOOT - OK
[6] SYSTEM - Fail-PU
[7] USERDATA - OK
Partition update fail!
Update Fail!
More over, my Magic is from Hong Kong and I've tired the Hong Kong RUU, but I got a "Main Version is older" using the gold card method, and I got a "Bootloader Version Error" by running the RUU on windows.
And then, I've tired the ROM v2.53.707.2 from the thread "[How-To] Fix perfected SPL (fastboot remote: not allow)" by Amon_RA (Sorry for I am too new to post a URL here)
Is there anyone experienced the same and got a solution? I've tried the whole day but I just can't any suitable sappimg.zip or whatever. Could someone point me to the right direction?
Thanks so much for your time reading this post.
I've rooted my Magic, got Cyanogenmod running nicely, etc. I was then trying to flash a new splash screen, and noticed that my security in fastboot shows as begin on (S-ON). Sure enough it wouldn't let me flash the splash screen, it said the signature was not valid.
So, I tried flashing every single engineering SPL possible, and it never changes to off.
Here is my info from the fastboot/hboot screen.
SAPPHIRE PVT 32A ENG S-ON H
HBOOT 1.33.2010 (SAPP5000)
CPLD-12
RADIO-3.22.20.17
June 2 2009, 17:27:03
Thanks!
Find zipped hboot, put it in your sd card and flash it trough recovery...
pera987 said:
Find zipped hboot, put it in your sd card and flash it trough recovery...
Click to expand...
Click to collapse
That's what I've done. I've flashed every single engineering hboot file I can find and each one still shows S-ON during fastboot/hboot, and I"m unable to flash through fastboot.
Follow these steps (you should find it in this Mytouch Room)
1. Create your goldcard.
2. Comeback to 1.5 version by flashing rom 1.5 from goldcard.
3. Install Recovery Flasher (RF).
4. Run RF, chose Flash Cyanogen 1.4 img
5. Copy new E-SPL to root of Sdcard, Boot to Recovery mode, flash this file SPL
6. You can flash new recovery img (like 1.7.0G) by fastboot mode through your PC.
Check your new SPL now and S-ON becomes S-OFF.
I've successed on Magic 32B with perfect SPL 1.33.0006 and S-ON.
vinamilk said:
Follow these steps (you should find it in this Mytouch Room)
1. Create your goldcard.
2. Comeback to 1.5 version by flashing rom 1.5 from goldcard.
3. Install Recovery Flasher (RF).
4. Run RF, chose Flash Cyanogen 1.4 img
5. Copy new E-SPL to root of Sdcard, Boot to Recovery mode, flash this file SPL
6. You can flash new recovery img (like 1.7.0G) by fastboot mode through your PC.
Check your new SPL now and S-ON becomes S-OFF.
I've successed on Magic 32B with perfect SPL 1.33.0006 and S-ON.
Click to expand...
Click to collapse
Thanks. I'll give this a shot when I get home this afternoon.
PaulieORF said:
That's what I've done. I've flashed every single engineering hboot file I can find and each one still shows S-ON during fastboot/hboot, and I"m unable to flash through fastboot.
Click to expand...
Click to collapse
If this currently a 1.33.20** spl with s=off and a custom recovery can you please do the following
Run 'adb shell dump_image misc /tmp/misc_dat.img'
Then
'adb pull /tmp/misc_dat.img misc_dat.img'
Then send me the resulting image somehow (pm me a rapid share link or ask for my email.. there ought not be any identifiably info in misc but just in case)
This may or may not clear up why there is an issue.. and let a better process to fix it be created.. untill then try unrooting (or installing a stock spl) and re-rooting as was mentioned, just onto forget radio versions may change in the process requiring caution not to skip ahead of yourself and brick.
UPDATE:
So I got the file, misc was nearly all blank without the usual data (boot mode, CID and some other data) this is easily fixed by re-flashing misc from recovery.. I think this can even be made into an update.zip.. (since all magic/dream misc partitions are essentially the same besides the CID, and the CID is still being passed to the recoveries command line when stuck in this state.
I have a mytouch 3g with the 3.5 mm jack
i tried to root it via theunlockr.com. I went as far as downloading the sappimg.zip file, however when i clicked on the link it sent me to yahoo search saying it couldnt find the file. so i did a search there n got 1 after i let the sappimg that i found install on my phone n it rebooted with the vodafone logo n froze from there. i tried geting other sappimg files but they all got stcuk at unzippiging system.
this is the screen it get:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
MAY 8 2009,21:02:32
HBOOT
Parsing...[SD ZIP]
[1] SYSTEM -Unzipping
[2] USERDATA
[3] BOOT
[4] BOOTLOADER
[5] RADIO_V2
[6] RECOVERY
[7] sPLASH1
Update is in progress...
Do not power off the device!
can some1 help me to correct it plz
Yeah, don't go flashing files to your phone when you have no idea what they are. Have a look around, there are plenty of people with the same issue.
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.