Database Users

Help! Droid 2 stuck in boot loop.(solved.)

Ok, so I was playing around with the new Root Tools app and made a few, what I thought were safe, tweeks to the system and rebooted the phone. It gets past the M screen, runs the boot animation and then starts the boot animation again. No way out except to pull the battery.
How can I get it out of this endless bootloop? If I have to factory reset and start again from scratch, so be it. I would just like to know how.
I've tried holding down different button combinations on boot but haven't come up with the right sequence I guess.
I've also tried pulling the battery as the animation starts, then putting it back in and rebooting which is supposed to call up the recovery mode, but it doesn't. I'm not sure what to try next? I wish these things had a reset button
It's a Droid 2 Rooted with the stock rom running Froyo 2.2. I have the Bootstrap recovery loaded and did a backup with the clockwork recovery. I also have, and use, Titanium Backup Pro for Root.

After bootlooping pull the battery and put it back in. Then plug the droid 2 in with the cable either wall or USB will work. Then turn it on and it should get you recovery. The phone has to be completely off when you plug it in though.
Sent from my DROID2 using XDA App
EDIT: I tested it and USB won't work (at least for me) better off just using the wall plug.

Thanks, but that not working either. When I plug in the cable after the battery pull it starts up automatically and goes to the battery charge screen. I then shut it off and start it back up with no battery but plugged in and it goes right back into the boot loop after the M screen.

The batter charge screen is what you want. Just press the power button after you get the charge screen and you'll be booted into clockwork.
But in order to factory reset from a bootloop you have to flash an .sbf theres a few different tutorials. One in Windows, Another in linux/mac, and another in linux but for windows machines through an Ubuntu livecd(that I made).

Oh, OK I thought it was going to go right into recovery mode. Good to know.
I finally figured out how to get into the stock recovery and bootloader, so I tried to run the stock restore but after it wiped the data, it couldn't find the recovery file! So then I read in another post about using RSDlight 4.9 to do an sdf restore so I used that method. Of course while it was flashing I did come across your Ubuntu method and that does look like it would be a simpler process. I'm going make one of those CD's to have for next time.
Anyway, I was able to get it back to stock. It looks like most of my stuff is still on the SD card, so that's a bonus! I'll have to re-root before I can restore everything via Titanium, but that's going to be tomorrow's project. As for now just happy to to have my phone back. Especially before the wife (who has been telling me for weeks to stop F'in with it) found out .
I really appreciate that you took the time to help, thanks again!

No problem.

Could you change your Thread title to include [SOLVED]. Thanks

Can you please explain to me how you fixed this problem? I am currently having this problem now.

Please do not open/post in multiple threads for the same issue. This is a waste of time as we can see you have an open thread. Please reply to my response in your original thread for further assistance. (http://forum.xda-developers.com/showthread.php?t=824254)

newk8600 said:
Could you change your Thread title to include [SOLVED]. Thanks
Click to expand...
Click to collapse
Ok, your wish is my command! ;-)
Sent from my DROID2 using XDA App

Can I close this?

Yes. This issue has been resolved.

theecho said:
Yes. This issue has been resolved.
Click to expand...
Click to collapse
Ok, thanks

My HD doesn't go further than the HTC bootscreen: Is it bricked?

Its teh first time this happened. I booed into recovery mode, applied an update.zip (MODACO). That went fine but when rebooting I dont come further then the HTC startup screen.
What can I do now? Is my phone bricked? What would be the next steps if it is bricked or what else can I try to make it work again?
i found some posts about what can be done but it was not quite clear to me what are the next steps involved (Do I need fastboot?).
Thanks for any help. I guess I should have been more careful but never ran into any issues in the past.

If you can get to fastboot (holding down vol dwn button on boot), go into recovery, clearing data before flashing whatever update.zip. If it doesn't work, follow this guide: http://forum.xda-developers.com/showthread.php?t=841890 . It should bring you back to a stock, unrooted rom where you can start afresh.
Sent from my Desire HD

luckily i was still able to boot into recovery....and after a factory reset i was able to boot ....althoug the launcher didnt work...anyway, I could then copy another rom on the sd card and that one worked again.
i guess now its time to start using those nandroid backups!

I think you must do crazy terror for your phone until you cannot go to fastboot/recovery.. I have always couple of backups if something went wrong...
Sent from my Desire HD using XDA App

[Q] Can't boot... have been meticulous... Help please?

This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic

syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App

Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??

Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App

OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App

syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!

syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.

last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.

You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???

Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.

lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.

Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.

lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!

And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?

syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App

OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!

Help please!!!

hey guys. im trying to be a good guy and help out a friend who is currently working on his phone. ok now lemme get in every detail as much as possible as you guys can fully understand what we're doing and what we've been done.
his phone is rooted. with s-off. now we tried flashing cm7 last night. did everything right. full wipe and all of that. so.. cm7 did finish the installation. it went thru the white mytouch4g screen, then onto the cm7 blue circle splash screen. after that it asked him all of his info to login to google. it was working for a good 2 hours. later that night, he told me he took out the battery to restart his phone. when he restarted.. white screen finished loading. but on the blue cm7 circle, it stayed there forever.
now im not sure what he did wrong since he told me he just wanted to restart his phone. we cant even go back since it gets stuck on the blue cm7 splash screen. i really really really need your help guys. maybe you guys can private message me or hit me up directly on my email. i would greatly appreciate all the help. i tried searching and searching and all i got was to go thru rom manager, but how are we gonna do that if we cant even get the phone to boot up correctly. thanks in advanced guys.

Sent you a pm
Sent from my HTC Glacier using XDA App

Well 1st that question belongs in Q&A : )
Power dwn the phone & hold the power button & volume dwn button at the same time until it goes into the fastboot screen then scroll dwn to recovery & select it by pressin the power button,u should now be in clockwrk recovery,try to rewipe everythin & flash again.. Now if u try that & all u get is cnt mount data/cache errors,then ur Emmc chip went bad... At that point google search emmc chip for mytouch 4g & read... : )
Sent from my HTC Glacier using xda premium

What's the point in searching for it it means you bricked
cmdmilitia13 said:
Well 1st that question belongs in Q&A : )
Power dwn the phone & hold the power button & volume dwn button at the same time until it goes into the fastboot screen then scroll dwn to recovery & select it by pressin the power button,u should now be in clockwrk recovery,try to rewipe everythin & flash again.. Now if u try that & all u get is cnt mount data/cache errors,then ur Emmc chip went bad... At that point google search emmc chip for mytouch 4g & read... : )
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App

tvotony said:
Sent you a pm
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
ok i will try and see what he says. ill pm you back tony. thanks a lot.

cmdmilitia13 said:
Well 1st that question belongs in Q&A : )
Power dwn the phone & hold the power button & volume dwn button at the same time until it goes into the fastboot screen then scroll dwn to recovery & select it by pressin the power button,u should now be in clockwrk recovery,try to rewipe everythin & flash again.. Now if u try that & all u get is cnt mount data/cache errors,then ur Emmc chip went bad... At that point google search emmc chip for mytouch 4g & read... : )
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
my bad i forgot to answer your question. ok we tried reflashing everything. nothing of that kind of error showed up. it just said complete. then when we tried booting up the phone.. it just got stuck on the blue circle thing.
tony, i sent you an email. anyone else willing to help?
i was thinking.. maybe the cm7 that we downloaded was corrupt? he said he has clockwork version 5.X.X.X
not sure if thats gonna make a difference but yeah. also since we cant go to the phone since it gets stuck on the blue circle, we tried flashing cm7. in the end, the last line says "installation aborted"
so right now, im completely clueless. i have searched everywhere and tried other methods to see what will work. my phone is rooted with royal ginger and everything is fine with it. i have already restarted maybe 10x the last couple of hours trying to help my friend.

Sounds like the sudden power lose from pulling the battery corrupted some system data. Boot into recovery and reflash the rom. Battery pulls can and have been known to corrupt system data making the rom unbootible.
I would start from stock and reflash the stock rom and start from a clean base

zelendel said:
Sounds like the sudden power lose from pulling the battery corrupted some system data. Boot into recovery and reflash the rom. Battery pulls can and have been known to corrupt system data making the rom unbootible.
I would start from stock and reflash the stock rom and start from a clean base
Click to expand...
Click to collapse
no. im sure this is not the case. we finished rooting the phone around 10pm last night. from then on, everything went well. i even showed him some other ideas on what app to download and all that. he took out the battery probably 3 hours later and thats when it just got stuck at the blue circle cm7 splash screen.

beryenbeh said:
no. im sure this is not the case. we finished rooting the phone around 10pm last night. from then on, everything went well. i even showed him some other ideas on what app to download and all that. he took out the battery probably 3 hours later and thats when it just got stuck at the blue circle cm7 splash screen.
Click to expand...
Click to collapse
Yes pulling the battery without allowing it to shut down properly will and has caused this, while not very common I have been in the same boot my self when I used to run a CM based rom.

zelendel said:
Yes pulling the battery without allowing it to shut down properly will and has caused this, while not very common I have been in the same boot my self when I used to run a CM based rom.
Click to expand...
Click to collapse
ok nevermind that. he said, he restarted his phone. he didnt take out the battery. he just decided to restart it and thats when the blue circle got stuck.

beryenbeh said:
ok nevermind that. he said, he restarted his phone. he didnt take out the battery. he just decided to restart it and thats when the blue circle got stuck.
Click to expand...
Click to collapse
Best bet would be to redownload the rom, boot into recovery and mount it so you can copy the new rom zip to the sd card. Do a full wipe and then reflash the rom. Other then that his only chance maybe going back to a stock rom and doing a clean rom flash just in case

help
beryenbeh said:
ok nevermind that. he said, he restarted his phone. he didnt take out the battery. he just decided to restart it and thats when the blue circle got stuck.
Click to expand...
Click to collapse
follow directions slowly and to the letter need not hurry when flashing or acheiving s=off..

underyourskyn said:
follow directions slowly and to the letter need not hurry when flashing or acheiving s=off..
Click to expand...
Click to collapse
i followed everything correctly and accurately. i even had him double check what i was doing to make sure. we rooted perfectly and flashed cm7 without a problem. i am not sure what happened when he restarted his phone.
can any of you guys speak to me directly? maybe via aim or any kind of instant messenger? i really wanna help him fix this problem but im not sure what else to do.

how did you root the phone to begin with?

neidlinger said:
how did you root the phone to begin with?
Click to expand...
Click to collapse
this way..
http://forum.xda-developers.com/showthread.php?t=858996

tvotony said:
What's the point in searching for it it means you bricked
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Cause me & a couple other people were able to recover frm those errors with the pd15 zip file... Some people were lucky..
Sent from my HTC Glacier using xda premium

beryenbeh said:
this way..
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
So honestly you may have a bad emmc, its a problem that has plagued the MT4G for quite some time now.
If you happen to read the bad emmc chip thread you will notice that some people that rooted with the gfree method, this one -->http://forum.xda-developers.com/showthread.php?t=858996 bricked devices.
Please stand by and I will attempt to find the thread with the info on the bad emmc. I hope that your friend doesn't have a bad emmc.
Edit: http://forum.xda-developers.com/showthread.php?t=1081243&highlight=Bad+emmc+chip
I believe that is the one. I can't be 100% sure but if you do run into problems search in the main sections. i.e. where it says general, Q&A, acc, dev, etc. and just search bad emmc. Some stuff about the screens will come up, you can ignore those. I really hope this helped in your efforts to fix your friends phone.
Worse comes to worse, try and get tmo to replace it, dont mention root and if they said you voided your warranty, throw it against the wall and claim it for the 130 dollars. BNIBs are going for close to 300 and ULN are going for 200-250 from where I am from.

Please look at the Glacier Wiki, Troubleshooting section. Link in my signature.

thanks a lot. hopefully his emmc isnt the problem. i checked his hboot and it says 0.86.0000 not sure if that rings a bell to any of you guys. ill keep reading more information and a possible solution. i read one that says to update the PDIMG file or whatever.. and then re-flash RG3.0. will try this one, hope itll work. once again, thanks for all the help guys. really appreciate it.
Rillusion08 said:
So honestly you may have a bad emmc, its a problem that has plagued the MT4G for quite some time now.
If you happen to read the bad emmc chip thread you will notice that some people that rooted with the gfree method, this one -->http://forum.xda-developers.com/showthread.php?t=858996 bricked devices.
Please stand by and I will attempt to find the thread with the info on the bad emmc. I hope that your friend doesn't have a bad emmc.
Edit: http://forum.xda-developers.com/showthread.php?t=1081243&highlight=Bad+emmc+chip
I believe that is the one. I can't be 100% sure but if you do run into problems search in the main sections. i.e. where it says general, Q&A, acc, dev, etc. and just search bad emmc. Some stuff about the screens will come up, you can ignore those. I really hope this helped in your efforts to fix your friends phone.
Worse comes to worse, try and get tmo to replace it, dont mention root and if they said you voided your warranty, throw it against the wall and claim it for the 130 dollars. BNIBs are going for close to 300 and ULN are going for 200-250 from where I am from.
Click to expand...
Click to collapse

So, have I bricked my phone?

Used ROM Manager and downloaded Leedriod 3.0, ran Terminal Emulator and did everything by the book. Went into ClockWork Recovery mode and everything looked okay. Then went to HTC boot animation screen and that's where it has been ever since. Every five minutes or so I get the delightful sound of HTC and a permanently on HTC, Quietly Brilliant Boot screen. It's been going like that for about 25 minutes now.
Any help would be appreciated.

No its not bricked, its in bootloop.
This is what i do when it happens to me:
Pull out the battery. If the phone is off, turn it back on with volume down + power on button. Wait till you get the bootloader screen. Now select recovery. In ClockWork Recovery you can set your backup back. (if you had made one before).
I hope its helps you. Goodluck.

Or just copy another rom file to the sd card and flash again.

Unfortunately I made the classic error of not backing up first, was trying to do this while in work (not good) so I presume at this point I'm screwed

joooe said:
Or just copy another rom file to the sd card and flash again.
Click to expand...
Click to collapse
Thanks, will try that tonight.

It doesn't hurt to try to flash the rom you already have once again.

Just what joooe said. Use super wipe to clear data. just for sure.
Good luck.
Sent from my Desire HD using XDA Premium App

Just a quick thanks to you guys, did Super Wipe and installed Android Revolution 6.20 last night and all went well. It was worth the screw up to have the small learning curve in the end

I did this one of the first times i flashed roms
i did have abackup first but its a scary experience lol