Related
This is my first time messing with the hero, I created a gold card and tried to install the hercimg.zip through hboot. But I am not sure everything installed sucessfully.
I got hboot1.47 and my radio got updated to 2.42.00.03.10
but when I go to flash an recovery image by using
fastboot flash recovery recovery.img
it fails.
I also can't run adb remount
So I am guessing I didn't get root access when installing the RUU.
So is there anyway to force hercimg.zip to get extract and run again?
Everytime I load up hboot now I get the following menu
[vol up] fastboot
[back] simlock
[home recovery
the hercimg will unzip and it will check but it just returns to the menu.
a message flashes right before it goes back to the menu but I am unable to read what it says.
is there anything I can do? I tried searching but I haven't been able to find anything that might work.
As side note my phone still works and it is still on 1.5.
d-shade said:
This is my first time messing with the hero, I created a gold card and tried to install the hercimg.zip through hboot. But I am not sure everything installed sucessfully.
I got hboot1.47 and my radio got updated to 2.42.00.03.10
but when I go to flash an recovery image by using
fastboot flash recovery recovery.img
it fails.
I also can't run adb remount
So I am guessing I didn't get root access when installing the RUU.
So is there anyway to force hercimg.zip to get extract and run again?
Everytime I load up hboot now I get the following menu
[vol up] fastboot
[back] simlock
[home recovery
the hercimg will unzip and it will check but it just returns to the menu.
a message flashes right before it goes back to the menu but I am unable to read what it says.
is there anything I can do? I tried searching but I haven't been able to find anything that might work.
As side note my phone still works and it is still on 1.5.
Click to expand...
Click to collapse
What are you trying to do?
I am trying to root my phone using the leaked sprint ruu the one that came out back in march/april
I have an Alaska DigiTel phone so I couldn't root it using the normal methods
so I was trying to follow the Rooting ALL Non-Sprint CDMA Heros Stuck On 1.5 From Sprint's 2.1 RUU tutorial.
But now I seem to be stuck, my radio and hboot seems to have gotten updated but it looks like everything else didn't as I am still running 1.5 and don't have root access.
I got it to work, after my battery fell out when the white/green htc logo was on my screen and when I went back into hboot it installed fine.
I didn't do anything else other then retrying the things I have been doing.
Format sdcard, recreate gold card. loading hboot
it just worked magically after the batter came out when the phone was booting up.
Hello all,
I've been trying to find a solution to this problem for the last 3 days, and get nowhere. About a year ago, I rooted my Mt3g LE using the unlockr's goldcard method.
Everything worked fine until 5 days ago, when some programs stopped working. So I try to get into my recovery, and it's no longer there.
Now, I boot back into the ROM, and go to ROM manager to fix permissions. I reboot again, and try to get to my recovery. Still no, so then I got into my ROM, and clicked "Fix recovery".
Big mistake.
Now, my phone is stuck at the ROM loading splash screen. I found my goldcard, tried to flash the same SPL that it was rooted with [the top one on this page](http://forum.xda-developers.com/showthread.php?t=548218)
and it tells me "Model ID Incorrect".
Then, I tried both of the other SPL's on that page, and it tells me the same thing. I checked my goldcard on my friend's phone, and it seemed to work okay.
summary= Can't boot into ROM, can't get into recovery, can't flash SAPPIMG's.
I can get into HBOOT and FASTBOOT / FASTBOOT USB on my phone.
The lastest thing I've tried is to [unroot](http://forum.xda-developers.com/showthread.php?t=665814) but it tells me "Main Version is older! Update fail!"
Try the stock recovery (power off the phone, press and hold HOME+POWER, until you see the phone with exclamation sign, then let go and press HOME+POWER again, until you see the stock recovery, might take a few presses to get to it), with this rom "6db5d4965a64.OTA_Sapphire_TMOUS_3.56.531.1-2.10.531.4_P2_release", just do a search here. Rename the file to update.zip and put it on the root of your sd. When you're in stock recovery do a wipe and then flash the update.zip. See if that works for you.
I'm in the same situation though and nothing I've tried has worked.
I did discover that I can get into ADB when it's trying to boot.
Is there anything I can do via ADB?
I've attached a logcat for any ideas.
thanks dark0,
the screen just stays at the HTC MAGIC splash, though. I left home and power pressed for 6 minutes.
If you still have root access and your fastboot is working, try flashing the amon ra's recovery through fastboot (http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/ , skip to step 4 if you've already set up the adb on your pc), and see if that works, if you still have root, you won't be getting the "not allow" message when flashing.
From there you'll be able to flash the new rom to get out of the bootloop.
Go into fastboot mode and post here ALL info.
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
HBOOT
then I try to run a SAPPIMG.nbh or sappimg.zip and both of them say Model ID incorrect! Update Fail!
dark0: all fastboot commands say "remote:not allow"
Hi all, I am going to be as thorough as I can. I am rather new, and I'm stuck trying to downgrade my MT4G to froyo (PD15IMG). I have read the tutorials, and learned enough about adb to attempt this task, but I think by doing the HTC Bootloader unlocking update last week, it may be the reason I'm stuck. I follow the instructions on the tutorial, to gain temp root, until I get to the part where I should get a "#" in the command Window when I type "adb shell" but I keep getting "$" instead, although everything seems to be going ok until I get to that point.
*Also, I put the PD15IMG.zip on the root of my sd card, and start my phone in bootloader mode, and it finds the PD15IMG.zip, and a blue progress bar appears in the top right corner of my phone for about 90 seconds, it then displays "parsing PD15IMG.zip" then stops at the hboot screen and does nothing. I just select power down, then power on my phone and nothing will have been done to my phone. I guess what I need to know is, by doing the HTC bootloader unlock update (which I did before I read that it was a bad idea), can I still downgrade and root with normal methods, or will I have to do something different?
Sent from my HTC Glacier using Tapatalk
You can start differently. Since you've unlocked the bootloader, try to flash recovery directly, by downloading recovery image directly from Clockworkmod site, rebooting to FASTBOOT (adb reboot bootloader) and using the command "fastboot flash recovery your_just_downloaded_recovery.img".
If recovery flash doesn't work for you - download the 2.2.1 PD15IMG, unzip it, and flash the following 2 files from it:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata
Then reboot. You should end up on 2.2.1, which is perm-rootable using the guide (Visionary for temp-root, gfree for S-OFF, and then perm-root if you want).
Then flash the recovery and the engineering bootloader.
Here is what I did, I am giving a link to pastebin as instructed, it seems to go perfectly until I try to flash the StockRom. In the meantime I will attempt what was just posted above^^^^^^^ http://pastebin.com/fYrC6tAZ
One last thing before i have to throw away my phone. I couldnt leave well enough alone. I did this "fastboot flash boot boot.img" as you stated in the post above. It was successful. I then entered this one "fastboot flash system system.img", and it failed (said the img was too big or something) so I did the "fastboot-windows reboot" command and it is now stuck on the white HTC MyTouch 4g splashscreen. Is my phone toast? My PC no longer recognizes that my phone is connected to the USB port, however I can hold the volume dwn & power button and it comes on in the hboot mode.Is there any hope?
Also, when I boot it up by vol/dwn & pwr, the Hboot screen comes up and finds the PD15IMG that is on my sd card, goes through a 1 minute or so process (a blue status bar loads in top right corner), then it just stays on the hboot. It did that before it stuck on the splash screen, but never actually wrote anything i dont beleive.
OK its letting me use FASTBOOT and here is exactly what I got when i tried to flash the 2nd file in your post above. It came from the PD15IMG.zip as you instructed:
C:\adb>fastboot flash system system.img
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.016s
Can someone please let me know if there is hope for my phone? I can communicate with it through Fastboot (on my PC) and it will boot up in hboot mode. But it WON'T go past the Tmobile/MyTouch splash screen. If I get it fixed, I promise to never touch it again until I study! I truly feel there is hope, but I think don't know enough to figure it out. I loaded the PD15IMG on my SD, and it attempts to flash it, (a blue status bar appears in top right corner and fills up in about 90 seconds), but afterwards, it still sticks on splashscreen. Is there anything I can do to fix it? Anything I can flash it with in Fastboot? Please anyone?
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Jack_R1 said:
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Click to expand...
Click to collapse
Thank for your response. I have tried doing the PD15IMG.zip by booting my phone in bootloader mode. It finds the PD15IMG.zip and then a blue progress bar appears in the top right corner of the phone, finishes in about 90 seconds, the a message appears that says "wrong zip file". I would be happy just to get my phone back on with the gingerbread 2.3.4 on it, and simply leave it alone until I know what Im doing. Is there a way to just flash the original s/w back on it? If so if you could tell me how I will not mess with it again until I study alot more. But flashing the PD15IMG doesnt appear to be working for me.
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Jack_R1 said:
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Click to expand...
Click to collapse
Ok you were right, the one I had the wrong MD5SUM, but i d/l the correct one, it had the correct MD5SUM, but it still gave me the "wrong zip file error". I feel like there is hope, but I cant figure this out!! Thank you for trying, is there anything else I can do? I also tried going into recovery and doing factory reset/ data wipe etc...but it continues to get stuck on the splash screen....
How did you copy the correct one to the phone's SD card, and where did you put it? You either didn't copy it to your SD card, or named it wrong, or put it in wrong location, not overwriting the older file.
In any case, if flashing PD15IMG fails for you:
Download CWM recovery from here:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-glacier.img
Boot to bootloader.
Enter FASTBOOT.
Execute:
fastboot flash recovery recovery-clockwork-5.0.2.0-glacier.img
Boot to recovery. You should have Clockworkmod.
Download a stock rooted 2.2.1 ROM from Development section.
Flash it in Clockworkmod recovery.
Extract boot.img from this ROM.
Flash it in fastboot, using "fastboot flash boot boot.img".
Boot into the ROM.
Proceed with gfree.
OK!! I got it fixed and it all makes sense to me now! I flashed the 2.2.1 boot.img to my phone, when it still had the 2.3.4 on it. It was as simple as that. I hadnt flashed the downgrade on it when I flashed the boot.img and I guess it was a mismatch. I read your last post to extract the "boot.img" from the rom and then it clicked! Yesterday I wrote the 2.2.1 boot img. to a phone that had 2.3.4...so I found a stock 2.3.4 rom, extracted the boot.img from it a BAM! its rolling again....thank you so much....
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Jack_R1 said:
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Click to expand...
Click to collapse
Well I will soon attempt it again, however I think I need to read a little more so I can understand the concept of what I am doing. I learned a ton by making that mistake. But as soo as I got it fixed, I couldnt resist, I used revovery and flashed [ROM]:: ProjectMIUI 2.2.17 [R6]- UPDATED 2/21/12 - [Stable + Smooth from the DEV section and I have never been happier with my phones performance! I will soon try the cyanmod, but I want to chill with this rom for a week or so. Again, I appreciate your help, I learned alot.
As long as you don't mind flashing kernels separately using fastboot for each ROM you flash, you can go indefinitely and flash ROMs as much as you like with your current setup, not needing anything else. The only good reason for you to go for S-OFF would be to flash Engineering HBOOT, to be able to flash kernels from recovery directly, avoiding extra fastboot step.
Also, thanks for finally confirming that you can flash recovery using fastboot on HTC-Dev-unlocked device. There was one device that didn't allow it (I think Incredible S, but not sure), so it's good to know that on MT4G it works as it should.
I rooted through cyanogenmod method, then unrooted (went back to stock 2.2.1) with the stock P15100.zip. I had another hardware issue with my phone (microphone failing) and thought it could be software. The mic was still broken and I wanted to root again so went through cyanogen method again flashing CWM. I was able to reboot once into recovery to flash synth's ICS. When I try to fully reboot, then reboot into recovery again, I got bootloop for a minute, then eventually booted into the rom. I tried flashing 4ext and same issue. I tried flashing CWM again from app and still have the issue. I'm just guessing recovery is corrupted and it needs to be formatted and re-flashed? Anyone know how to format recovery via adb and then push cwm or 4ext?
Any help much is appreciated.
You can flash a recovery through terminal emulator. As I recall, the commands are:
su
flash_image recovery recoveryname.img
Sounds like you might be having bigger issues, though. I hope your recovery partition isn't going kaput.
Jack_R1 might have an idea.
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Nicgraner said:
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Click to expand...
Click to collapse
I have used adb a bit (for root with cyanogen method). I'm guessing that the delete command will reformat the recovery partition? I'll give this a go when I get home and get back to ya. Thanks for the reply! Is there a way to download the 4ext recovery img file?
Edit:
I downloaded the CWM touch img and connected to the phone in fastboot. Was able to follow your instructions, but the command is erase not delete. When I put in the delete command it came up with the instructions and was able to figure it out. Flashed recovery and I can now boot into recovery every time from fastboot, terminal, adb, and from power prompt in rom! BOOYAH! Thanks a ton!
Jack_R1 said:
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Click to expand...
Click to collapse
Hey Jack,
I have HTC Glacier. Was a typo for the PD15IMG name. I think I have a decent understanding of the phone, and most likely have a corrupted recovery partition. Seems that instead of just flashing a recovery over a recovery, I may need to reformat the partition and then flash? I'll try flashing the file you suggest and report back. If it is not the recovery that is corrupted, what else could be the issue? Possibly an issue with the bootloader not allowing the phone to boot into recovery? Thanks for the reply.
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Jack_R1 said:
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Click to expand...
Click to collapse
Sorry if I wasn't more descriptive. I really appreciate your help and everything you have done for this community. Seems the recovery was corrupted by the 4ext app. I was able to extract the recovery.img from the 4ext download and was able to flash it via fastboot. Everything boots properly now. HBoot is 0.85.2007 FYI. Thanks again!
Hello,
I just came from a custom ROM and flashed stock 6.0 and stock recovery, in order to send my phone into squaretrade. However, There seems to be no recovery on my phone now. When I power up, I get the boot logo and then eventually goes to my lockscreen. I try to unlock with my passcode and it just continues to loop back to the lockscreen. I shut down and try to go to recovery and there is only a screen that says "no command". I cannot seem to get adb to see my device while attached. Am I completely screwed?
Well, I used the return to stock tool and am able to set usb debugging on. However, I still don't have recovery and when I am in fastboot and check for adb devices, there are none found.
buggerritt said:
Well, I used the return to stock tool and am able to set usb debugging on. However, I still don't have recovery and when I am in fastboot and check for adb devices, there are none found.
Click to expand...
Click to collapse
When you get to the Android on his back saying "No command" press and hold Power and tap Vol Up, that should bring up the stock recovery menu.
When in fastboot, there is no adb, only fastboot... you need to use `fastboot devices`
When flashing the stock images, flash stock recovery, then start it and do a factory default, then reboot and flash the entire stock image.
Where are you getting the stock image and instructions? You should never be prompted for a passcode after flashing the stock images, the device should be a blank slate.
I forgot the stuff you reminded me of. Thank you. I'm back on track now.