Database Users

loaded wrong rom, stuck on boot screen

Apologies for this stupid question resulting from a stupid mistake. Hoping somebody will be able to walk me through getting out of this.
I successfully rooted my sprint hero, then loaded modaco 3.0 (yes now I know that was bad). On reboot, the phone hangs on the black htc screen, and will respond to nothing.
The only thing I've been able to do is remove the battery, then turn it on in recovery mode. There, I did a wipe data/restore factory setting. Then I rebooted - and got the same boot screen, same problem.
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
When I try to restore, I get these:
(bart) error: run bart via adb
(nandroid) can't open file
Please help! I am out of ideas. Thanks very much in advance.

you'll probably have to take it back to the very beginning......
Get the Sprint RUU stock rom (a couple of posts below this one) and run that
then re-root your hero
Flash one of the roms ON THIS BOARD ONLY!!! Any other Hero rom is meant for the GSM version so it will give you the same headache again.

thanks
Thanks for the quick response! I'll try that.

Hmm, not looking good here. When I tried to install the stock hero RUU I got this error:
no signature
verification failed
which I presume is related to the htc sync requirement for that rom in the unrooting procedure that I did earlier.
Any idea for working around that?

So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.

david.danaan said:
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
Click to expand...
Click to collapse
Don't use 1.1, grab a later one.
Which recovery? 1.5.x won't let you go back to the main menu without disabling USB-MS again... I don't remember what 1.2.3 did. If worse comes to worst, reboot the phone after copying the file.

gu1dry said:
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
Click to expand...
Click to collapse
Yes, that's the one.
Using recovery 1.5.1. I can try a later rom, see if that works. I think I downloaded 1.3.

So first off yes, you aren't booting past the HTC screen because you flashed the wrong rom. However you aren't bricked. It's almost impossible to do once you're rooted and have RA's recovery installed unless you flash radios and stuff which you shouldn't.
Explanations for your other problems:
1. RUU doesn't work on the phones that are coming from the factory with 1.56. http://geekfor.me/news/sprint-ruu-fails/
There is a possible work-around but it's pretty detailed and I haven't gotten it to work. But you don't need to RUU if you can get in to RA.
2) (nandroid) can't open file is likely caused by RA 1.5.1. It had a bug that corrupted the backups. 1.5.2 is out. But for now don't worry about that cause your backup already sounds corrupted, nothing you can do.
3) can't open /sdcard/update.zip (bad). To me that sounds like your update was just corrupted.
How to fix it:
1. Boot in to recovery. With phone powered off hold your home button and then power.
2. Download fresh rom from http://geekfor.me/new-release/fresh-rom-1-0/ (what can I say... I'm partial. )
3. Within RA enable USB toggle and copy fresh rom to the root of your sdcard. Don't worry about renaming it to update.zip
4. Disable usb toggle. Go to flash zip from SD and choose fresh. That should be it. If you get the error saying the zip is bad then compare your downloaded copy with the md5 hash check on the download page (google it if you aren't sure how). If it matches then it's possible you have a bad sdcard. If it doesn't match then your downloads are crappy.

working!
Got it working by flashing the modaco v1.3a - must have been a bad update.zip before like you said. Thank you so much for the help and clear explanations, I was really worried I had bricked it.

David, now that it is working, I would recommend updating your recovery to 1.5.2.

I just want to thank everyone that posted to this reply I honestly thought that I bricked my phone and thank to you guys I was able to revive it. Thank you again.

G1 RADIO FLASH HANGS UP “Formatting CACHE…” (2.22.23.02) brick ?

I was rooting a G1 and was flashing the latest radio 2.22.23.02. with RA dream 1.7.0. It went through its paces:
flash-> reboot (home+back)->does it’s own thing -> boots back into recovery screen & then hangs on “formatting cache…” (at bottom of recovery screen)
It hangs up on G1 screen but will go into recovery. I’ve gone back and wiped everything, flashed (radio) from 2 different fresh sd cards, etc, etc…nada
Anything I can do? Un-root it? Re-flash recovery rom?
Thanks P-

if the phone will not boot normally but will go in to recovery, why not wipe it and flash a ROM?

pk2 said:
I was rooting a G1 and was flashing the latest radio 2.22.23.02. with RA dream 1.7.0. It went through its paces:
flash-> reboot (home+back)->does it’s own thing -> boots back into recovery screen & then hangs on “formatting cache…” (at bottom of recovery screen)
It hangs up on G1 screen but will go into recovery. I’ve gone back and wiped everything, flashed (radio) from 2 different fresh sd cards, etc, etc…nada
Anything I can do? Un-root it? Re-flash recovery rom?
Thanks P-
Click to expand...
Click to collapse
The good news is that the radio flashed successfully and you're NOT bricked.
The process goes like this:
From recovery, you SET UP your cache partition to store the radio image and set the misc partition to initiate the flashing process. It then reboots into update-radio mode, flashes the radio, and configures the misc partition to format the cache. It then does that, and theoretically, you're done.
Something screwed up in your format cache. NOT THE END OF THE WORLD!
What you've got to do is STOP flashing the radio! Its already flashed, it will either WORK or NOT WORK. There IS no IN BETWEEN.
Now recovery obviously isn't working for you, so what we need to do is this: Use FASTBOOT. WHAT SPL do you have installed? Is it a 0.95.3000 or a 1.33.2xxx? If it is, then you reboot into fastboot, perform a "fastboot -w system", and then a "fastboot update signed-dream_devphone_userdebug-img-14721.zip" (which you can download from developer.htc.com/adp.html). This will put your phone into a WORKING STOCK ADP1 state (which has root).
The instructions are all on the htc site at that link.
AND FINALLY:
DO NOT EVER UNROOT IT!!!!
You have root now, there is ABSOLUTELY NO reason to EVER "unroot" it. DO NOT EVER (no matter WHAT any RETARD ever says) write an NBH file to the thing.
If you do NOT have a fastboot SPL, then install one first.... I recommend 1.33.2003 which you can find here: http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76

AdrianK said:
if the phone will not boot normally but will go in to recovery, why not wipe it and flash a ROM?
Click to expand...
Click to collapse
Thanks for the reply,
That was my thought, sort of a "Hail Marry pass". but I was afraid to take myself any further to oblivion. The second post seems a little safer.
Thanks again, PK
IBCODER, many, many thanks,
lbcoder said:
Something screwed up in your format cache. NOT THE END OF THE WORLD!
Click to expand...
Click to collapse
Don't leave me!! This was my favorite little g1...a keeper, I've done 6 without a hitch. I need some coffee, shake some fuzz out of my head (morning here), and do some home-work. Will be back soon....
Regards, PK

Thanks very much for the reply,
lbcoder said:
The process goes like this:
From recovery, you SET UP your cache partition to store the radio image and set the misc partition to initiate the flashing process. It then reboots into update-radio mode, flashes the radio, and configures the misc partition to format the cache. It then does that,
Click to expand...
Click to collapse
O.K., that fills in some blanks. And this right here is where I’m stuck eh? Oddly, I can still navigate the RA-dream recovery screen with frozen cache thing.
lbcoder said:
and theoretically, you're done. Something screwed up in your format cache. NOT THE END OF THE WORLD!
Click to expand...
Click to collapse
Thats a relief. I thought I had followed the directions to a “T” (theunlockr.com), this is not my first.
lbcoder said:
What you've got to do is STOP flashing the radio! Its already flashed, it will either WORK or NOT WORK. There IS no IN BETWEEN.
Now recovery obviously isn't working for you, so what we need to do is this: Use FASTBOOT. WHAT SPL do you have installed? Is it a 0.95.3000 or a 1.33.2xxx?
Click to expand...
Click to collapse
As far as the SPL, on the FASTBOOT screen I have an “hroot 1.33.2995”(?). I flashed a generic G1-SPL over the bad radio install (WTF) and may have flashed Danger SPL. I don’t know how to tell if either took.
lbcoder said:
If it is, then you reboot into fastboot, perform a "fastboot -w system", and then a "fastboot update signed-dream_devphone_userdebug-img-14721.zip" (which you can download from developer.htc.com/adp.html). This will put your phone into a WORKING STOCK ADP1 state (which has root).
Click to expand...
Click to collapse
Can this cause any turmoil with Danger-SPL (if I flashed it)? Could either SPL have taken with the radio half installed or in a dubious state and are they a game changer if they did? The FASTBOOT screen idicates the "radio 2.22.23.02" i was trying to install, as if it took(?)
lbcoder said:
The instructions are all on the htc site at that link
AND FINALLY:
DO NOT EVER UNROOT IT!!!!
You have root now, there is ABSOLUTELY NO reason to EVER "unroot" it. DO NOT EVER (no matter WHAT any RETARD ever says) write an NBH file to the thing.
If you do NOT have a fastboot SPL, then install one first.... I recommend 1.33.2003 which you can find here: http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76
Click to expand...
Click to collapse
Thanks for the link, I’ve used adb and a little linux in the past but am new to FASTBOOT. The basics look a little familiar.
If any of my concerns regarding my SPL status, please do. And please elaborate if you can.
Thanks again for the direction.
PK

You're actually looking very good in most regards.
Yes, the radio flash took successfully -- of this there is no doubt. If it didn't, your phone wouldn't even turn on, it would be completely dead.
As for the SPL, you said "hroot 1.33.2995" -- I believe that you mean "hboot 1.33.2005", right? That being the case, you are actually in a VERY strong place! You have a *proper* engineering SPL installed (not the one I would pick, but a good one nevertheless... and yes, it is the infamous deathspl.)
The problem is that the thing is failing to format your cache partition and it is probably not getting to the point of clearing your misc partition.
NO PROBLEM.
In fact, you say that you are able to navigate the recovery despite the format cache failing. This is a VERY good thing! It makes thing a bit easier.
I actually just thought of something....
You say that it just keeps automatically going into recovery when you turn it on.... the SPL is designed to do that in TWO circumstances; 1) When the boot-recovery command is set in the misc partition, (2) When the BOOT partition is empty or corrupt. I assume that (1) doesn't apply since it appears that recovery IS WORKING.... which leaves (2)....
Have you tried to simply flash a ROM to the thing? I mean it. Sounds simple? Yes. Try to JUST FLASH A ROM! Put CM5.0.8's update.zip onto your sdcard and FLASH IT! See what happens. Can't hurt. If it doesn't change anything, then we just need to go back and force clean the misc partition.

Hello Ibcoder,
Thanks a lot for the follow up. I hope this prob. Is still enough of a challenge to keep you interested. Before I take the plunge I just want to clarify a few points: (I’ll guess it doesn’t matter but…):
lbcoder said:
"hroot 1.33.2995" -- I believe that you mean "hboot 1.33.2005", right?
Click to expand...
Click to collapse
Yes, at least this is indicated in the bootloader screen…corrupt or not (the lingering "formatting cache..." when I was flashing the radio).
lbcoder said:
You say that it just keeps automatically going into recovery when you turn it on....
Click to expand...
Click to collapse
Actually it boots into the “G1” screen but just hangs there. However, with the usual button combinations, I can boot into recovery and the bootloader screens, navigate around and execute stuff. Does that still sound like a corrupt partition? does it matter?
lbcoder said:
Have you tried to simply flash a ROM to the thing?
Click to expand...
Click to collapse
Not yet, but if this post doesn’t change anything I’m ready.
Regards and many thanks, PK
BTW:
lbcoder said:
Deathspl…not the one I would pick, but
Click to expand...
Click to collapse
Worth another topic I guess, but what would you use that’s compatible with CM 5.08, CM 6.0 and maybe the embryonic froyos?

pk2 said:
Not yet, but if this post doesn’t change anything I’m ready.
Click to expand...
Click to collapse
Quit stalling and do it already! Nothing important is corrupt -- if it was, it wouldn't do ANYTHING.
You installed an SPL that changed the partition mapping so that the END of the system partition is further ahead, BOTH ends of the cache partition are in different places, and the start of the userdata partition is back further. OF COURSE IT WON'T BOOT!
Worth another topic I guess, but what would you use that’s compatible with CM 5.08, CM 6.0 and maybe the embryonic froyos?
Click to expand...
Click to collapse
ALL SPLs are compatible with ALL ROMs, NO EXCEPTIONS!
This is DESPITE what is claimed by the majority of those who are technically inept.

It worked. CM 5.08
Thank you
Sorry for taking your time. I’ve done lots of roots and rom flashes with out a hitch. I’ve heard though, (after the fact) that if you screw up your radio or SPL flash you have a brick. Got me thinkn', with my symptoms, I might be on my way to one (a brick).
Thanks again much, much for all your trouble,
PK

and as a follow up, i tried flashing the same radio on an HTC T mobile G1 it kinda got stuck on the formatting cache screen too, but I can still access the recovery menu, in fact it got stuck on the recovery menu saying at the bottm "formatting cache" so I decided that I just reboot using the menu screen of the recovery and then it went through the usual booting process and I checked it so there it was the radio was updated, still have not reflashed the rom or anything won't it affect the rom flashing in anyway?

From My experience you should be able to flash your rom (can't be responsible if it bricks).
PK

Flash the Rom. Wont brick it. Same happened to me on 2 different phones. It's ok
Sent from my HTC Magic SparksMod using XDA App

Hello,
I had the same problem. i was aslso stucked in the "formating cache". a normal boot was not pissible.
i rebootet a few times and then the message did not apear anymore.after that i flashed a new rom without problems.
so i have no idea what happened but i am happy that its working.

PTG said:
Hello,
I had the same problem. i was aslso stucked in the "formating cache". a normal boot was not pissible.
i rebootet a few times and then the message did not apear anymore.after that i flashed a new rom without problems.
so i have no idea what happened but i am happy that its working.
Click to expand...
Click to collapse
That's what happened to me to yesterday night after flashing the DangerSPL. Although I was able to access to the recovery image, so all I did was to flash over the room. Hope that will work for u too..

[Q] Installed rom now phone is broke

Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.

You need to put it on the phones internal sd card plus sometimes you need to put text message setting yourself like message centres number .
Sent from my GT-I9000 using XDA App

Is this a troll?
mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages.
Click to expand...
Click to collapse
That's because you have to install a DL09 kernel and modem as well.
I thought maybe I'd try another rom. So I downloaded one called hamsters rom.
Click to expand...
Click to collapse
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.

THANK YOU, THANK YOU, THANK YOU!!
My phone is back and working on the stock rom. I am definitely clueless when it comes to this but I am not giving up. I am going to get the dl09_supah_clean_04 rom working. I'll be more careful this time though.
Thanks again!
s44 said:
Is this a troll?
That's because you have to install a DL09 kernel and modem as well.
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.
Click to expand...
Click to collapse

not trying to be a d!ck but, you really need to stop before you do brick your phone. read, read, and read some more. its clear you dont understand what your doing and are going to end up screwing up even worse. read EVERYTHING dealing with ONLY the VZN fascinate. if it says anything other that VZN fascinate DO NOT READ IT. your in to big of a hurry and will brick your phone. hell, i have been hacking phones for years and am still not comfortable with android yet. i have rooted but not installed a rom because i dont want to mess it up. hell, i havent even done the new update from VZN. im waiting for more reports to come in. just take your time and read, then worry about flashing to another rom.

If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.

mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.
Click to expand...
Click to collapse
You also need to odin the DL09 modem. or SMS and other things WILL be broken.

1.4hitachi said:
If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.
Click to expand...
Click to collapse
When people take Odin for granted, they end up with bricks.

Odin can be your friend...as long as you use PDA and not Phone...which is counter intuitive

adrynalyne said:
When people take Odin for granted, they end up with bricks.
Click to expand...
Click to collapse
Shouldn't you say, 'when people use Odin incorrectly"? I mean, as long as he follows the instructions and un-does and kernel changes beforehand the device will be returned back to stock. Also with the official DL09.md5 package it has inside all necessary operating parts. It sounds to me like all he did was attempt a rom flash twice. Odin with the "offical" DL09.md5 will return his Fascinate to stock.

Thanks everybody! I got back to stock and let phone receive the ota update of DL09. Figured that would take care of the kernel and modem and I could install dl09_supah_clean_04. Worked like a champ. I think I learned a lot in this process as well... time will tell.

[Q] current rooting/2.3 instructions

As the thread title states, I'm looking for info on the steps to root my stock MT4g, and install the new ROM that's floating around. I'm pretty technically capable, but the info I've found looks slightly dated. When I was active in the iPhone jailbreak scene, using old directions could brick a phone pretty easy, or prevent future jailbreaking. I haven't kept up with this scene enough to be able to know what's dated and what isn't.
This is my current plan, please correct it if I'm missing anything or have it wrong.
(based on wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide)
I've got ADB going
I need a backup solution for app data right? What's my best option here?
Once backed up, I plan to install busybox, Superuser package & Temporary Root package via ADB
Use gfree to make that root permanent
Install ClockworkMod recovery
Reboot into recovery, and install faux123's ROM
Does that sound correct, and did I skip anything? Any input at all is welcome, I'd like to stand tall on the backs of giants.

There are two popular methods floating around
You can either use the Root.sh method [ Found Here ]
Or the ./gfree method [ Found here ]
Either method will work perfectly. I've used both and can say with confidence they work.
The Cyanogen method can be goofy at times. I've see alot of people say they cannot get it working for them. I'd rock one of the two above. You shouldn't have a problem either way.

Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?

lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
For backing up apps and data, use titanium backup. for backing up your whole phone, use the backup feature in clockworkmod recovery after you've flashed it via rom manager after permarooting.

lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
The best way to back up your Data and Applications is like mentioned above is Titanium Backup. The free version will work well but i recommend the paid one.
as far as a snap shot of the entire ROM incase you want to go back to it. reboot into recovery > backup/restore > backup. And it will do the rest.

Well I made it halfway there, but didn't nail the whole thing. I've got permanent root access (yay) now, and was able to make backups via Titanium. I then rebooted the phone into "recovery" using the ROM Manager from Clockwork. First boot had a red exclamation mark, I unplugged the handset from the USB and tried a second time. After that, I was greeted with the Orange and black interface, and selected "restore to factory". I then started searching for the cache clearing, which changed verbage between 3.x and 4.x releases of Clockwork. After exploring the menus a little, the phone reboots itself from this screen. My blood-pressure goes up, and I worry my toy just became a b-word. Not all was lost though, and the phone happily booted into the stock t-mobile welcome wizard.
I still have superUser installed, and still have root (S=OFF I guess?). I install ROM Manager again, and do the "Flash ClockworkMod Recovery" (which now shows both current and latest recovery as ClockworkMod 3.0.2.4). When I choose Reboot into Recovery however, it reboots back to the MyTouch 4G logo screen (non-animated one), and hangs. After some reading I tried to force recovery boot via ADB, which produced the same result as the soft reset from ROM Manager. After that I tried doing it the manual way with holding the volume button, which launched me into what I believe is a stock recovery console (white with colored options, uses vol +/- and power to navigate). Choosing "recovery" from that screen *also* produces the white logo screen hang.
So my question now is, in it's current state; how can I get to the Clockwork recovery again? From there I bet installing the image will be easy street, but I believe I'm stuck for now.
Side-note: the phone functions fine on regular boots and pure vanilla mode; I just don't want to stop here when I'm pretty close to my 2.3 goal

Well good news and bad news. I was able to get Clockwork going by reverting it to 3.0.0.5 and just using that version. Was able to install ROMs, tested a few. Phone started freezing after/during installing packages. Started the clear cache/install ROM process, ran into this:
Code:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
http://forum.xda-developers.com/showthread.php?p=14389074
Totally stuck at boot screen, but able to get into Clockwork. All ROM zips off the sdcard produce this or an invalid zip error.

Other guy smight tell you what a status 7 might be, but with the flurry of flashing youre doing, you may have gotten some corruption on your sd
try formatting your sd card in the pc, or use another one so you dont have to back everything up on this one. put one rom zip on the root and see if that helps
also, i would make super sure you wiped/factory resetted every possible data/cache in CWM before flashing the zip
lastly, i would md5 test the download to make sure it matches the web page. Plus, after it's transferred to the cleanly-formetted sd, check it again either thru adb, or do the trans on the pc using an sdcard reader and check it once it's on the sdcard, then pop it into back your phone.
good luck

Thanks a ton for the uber fast reply. When I format on the PC, what format do I use, or is there a specific tool to properly format it for the phone?
When I'm wiping /data it's taking forever and I get the following message back:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log/last_log
E:Can't open /cache/recovery/log/last_log
Don't have an adapter at the office today for the sdcard, but I guess I can just grab a new one at lunch? All it would need is a fresh format then the .zip of the ROM in question at the root?

Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.

Jack_R1 said:
Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.
Click to expand...
Click to collapse
So I use the same PD15IMG.zip i did to start, flash it using Clockwork, then start the root > rom process over? I think that it currently tells me it can't find that zip anymore on the white screen pre console, is that expected? I just xfer it to the sdcard prior to fixing?

Yes, that's the right procedure. Move it to the card and start from scratch. Beware not to use the newer Panache/MT4G Gingerbread RUU, otherwise you'll be left with no way to root, or at least harder way.

Ok, so I didn't have a PD15IMG.zip to begin with, I see this thread:
http://forum.xda-developers.com/showthread.php?t=1059347
and that's proper that I'm flashing the radio itself for this process? Which of those images do I want to grab? I always like to double check when I read warnings that are pretty specific about bricking the device

No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.

acsi007 said:
No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.
Click to expand...
Click to collapse
Jesus, glad I asked before getting in there.
So I was going to offer you a beer sometime, I think I owe you a few rounds at this point...
Edit: this one right http://forum.xda-developers.com/showthread.php?t=924923 ?

Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...

acsi007 said:
Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...
Click to expand...
Click to collapse
I rooted gfree originally, and think I may be in the bad place
Fail-PU errors running the update from pd15img. Do I have any options at this point? I bought the phone from Wirefly.com, and since I can't get a recovery image going, I may be fuct here on a return eh?

looks like i'm moving to: http://forum.xda-developers.com/showthread.php?p=14487111#post14487111

Good luck Lars. Let us know that they did and if you had to pay.

Can't boot to system or flash rom. E:footer is wrong E: signature failed

Hello,
I'm looking for help. I wish I could ask on the development page, but I don't have access to do so because of my low post count.
I've had a problem with my HTC Bolt screen. I made a video of the problem and put it on youtube:
https://www.youtube.com/watch?v=1eR5NFDcnvU
I thought it may be a problem with the firmware/stock rom that is loaded with bloatware, so I decided to tinker with rooting, etc...
First thing I did was gain root using this method:
https://forum.xda-developers.com/bolt/how-to/root-supersu-v2-78-sr5-s-off-sunshine-t3513048
Then I downloaded and ran Sunshing to get S-off.
I then tried to install a new Rom, but it wouldn't install, giving the " E:footer is wrong .. E: signature failed" on the android recover.
The phone on my screen continued to glitch, so I tried to go back to stock using the RUU as described here:
https://forum.xda-developers.com/bo...t-htc-bolt-1-17-651-11-updated-t3502778/page4
but the process hung when trying to install a new rom using the RUU . I assume this happens because of the same "E:footer is wrong .. E: signature failed" problem when I try to flash a ROM.
Please help. I can't boot up into the system and am new to this. Also, if you can point my problem to the developers, that would be great.
recovery screen shows this:
*** Software status: Official ***
*** Unlocked ***
*** S-Off ***
This looks good to me to give me access to flashing, but the error keeps getting in the way.
Thanks,
Marc

what recovery are you using?
when you reboot to download mode and use fastboot, type fastboot devices. Does the serial number and fastboot show up?
what method are you using to RUU?

I tried all of the recoveries I could find, but I guess most were close to stock . I still can't figure out why I couldn't install rom from SD card.
UPDATE: I was able to reflash with RUU exe from my computer. Problem ended up being available disk space on C: drive. The RUU .exe needed about 7 gb free to run all the way through. First try I only had 2gb, which wasn't enough and caused. Exe to hang.
I just updated to latest software, 22 and screen problem still happening. Someone else commented that they have had the same problem on two different Bolts. Guess there are some manufacturing or software issues with the bolt, so be ready for screen issues. Hopefully it is software or firmware rather than hardware.
After running RUU, I assume I'm stock, but how do I lock and get s-on again?

marcram said:
I tried all of the recoveries I could find, but I guess most were close to stock . I still can't figure out why I couldn't install rom from SD card.
UPDATE: I was able to reflash with RUU exe from my computer. Problem ended up being available disk space on C: drive. The RUU .exe needed about 7 gb free to run all the way through. First try I only had 2gb, which wasn't enough and caused. Exe to hang.
I just updated to latest software, 22 and screen problem still happening. Someone else commented that they have had the same problem on two different Bolts. Guess there are some manufacturing or software issues with the bolt, so be ready for screen issues. Hopefully it is software or firmware rather than hardware.
After running RUU, I assume I'm stock, but how do I lock and get s-on again?
Click to expand...
Click to collapse
Is the screen always black, or intermitting?
in download mode
fastboot oem lock( it will say relocked and not Locked though)

OK, thanks. Maybe some chmod can solve it. Sprint is charging since it is more than 20 days old. Going to HTC instead since under their warranty.
The problem is intermittent, but is getting worse with each hour. Others are having the same issue.

I've been seeing the same issue with the display not waking since the .22 update...it's very intermittent on mine though, maybe 10% of the time...I haven't been able to narrow it down.
did u flash twrp recovery before flashing a ROM?

Thought I replied to this, but guess not. I didn't flash twrp. I thought that was only available through app, where one touch operations could be performed. I previously couldn't boot into system.

marcram said:
Thought I replied to this, but guess not. I didn't flash twrp. I thought that was only available through app, where one touch operations could be performed. I previously couldn't boot into system.
Click to expand...
Click to collapse
no, twrp is best installed by flashing it in download mode, u cannot flash a ROM via stock recovery, only custom recovery(twrp)...https://forum.xda-developers.com/devdb/project/?id=18340#downloads

Thanks, twrp did the trick. But with 3 different roms, I'm still having screen blackout issues. Going to need help getting back to locked and s on after RUU. Guess I'll start a new thread for that.