[Solved] May have bricked my Z;( - G2 and Desire Z General

Edit: "Rom Development" is only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here. Moved thread to "General." Please refer to "[REF] STOP! Read before posting!" ~TheRomMistress
Guys i think i may have bricked my Z
I did the following
I flashed the wpthis-Z.ko file
then i flashed the wpthis.PreOTA file
then i flashed the hboot, which worked fine.
But now i get lots and lots of force closes when sense boots,
Can anyone help please?
JD

Go back to stock using the RUU

EddyOS said:
Go back to stock using the RUU
Click to expand...
Click to collapse
Will give it a go mate,
Was that the right way to s-off?
JD

JupiterDroid said:
Guys i think i may have bricked my Z
I did the following
I flashed the wpthis-Z.ko file
then i flashed the wpthis.PreOTA file
then i flashed the hboot, which worked fine.
But now i get lots and lots of force closes when sense boots,
Can anyone help please?
JD
Click to expand...
Click to collapse
ok first of all that is not a brick! Bricks are when you cannot even power on the device, if you're getting all the way into the ROM that is NOT A BRICK.
Second. Learn what you're doing before you do it. wpthis-Z.ko is for the DZ wpthis-pre-OTA.ko is for the G2, both does not mean better.
Third. Which hboot did you flash? if you flashed the g2 hboot that means that your partitions are gonna be different in which case you should flash the roms from the g2 forum not this one.

Sphaerophoria said:
ok first of all that is not a brick! Bricks are when you cannot even power on the device, if you're getting all the way into the ROM that is NOT A BRICK.
Second. Learn what you're doing before you do it. wpthis-Z.ko is for the DZ wpthis-pre-OTA.ko is for the G2, both does not mean better.
Third. Which hboot did you flash? if you flashed the g2 hboot that means that your partitions are gonna be different in which case you should flash the roms from the g2 forum not this one.
Click to expand...
Click to collapse
I flashed the z hboot,
Im just getting errors with sense, lots of force closes;(
JD

JupiterDroid said:
I flashed the z hboot,
Im just getting errors with sense, lots of force closes;(
JD
Click to expand...
Click to collapse
My suggestion would be to re-flash the rom.
http://forum.xda-developers.com/showthread.php?t=832503 has a guide, since you're s-offed you *should* (not positive about this) be able to skip basically everything, grab the rom from RUU and flash it via hboot and you should be fine.

dont worry mate we will find a way,
I'm searching G2 fora right now, will report

Sphaerophoria said:
My suggestion would be to re-flash the rom.
http://forum.xda-developers.com/showthread.php?t=832503 has a guide, since you're s-offed you *should* (not positive about this) be able to skip basically everything, grab the rom from RUU and flash it via hboot and you should be fine.
Click to expand...
Click to collapse
So what is it I have actually done? I don't have clockwork mod installed so can i flash the RUU as normal?
JD

gtrab said:
dont worry mate we will find a way,
I'm searching G2 fora right now, will report
Click to expand...
Click to collapse
Your a diamond mate
Im not sure how to play it from here:/
JD

JupiterDroid said:
Guys i think i may have bricked my Z
...
But now i get lots and lots of force closes when sense boots,
Click to expand...
Click to collapse
I just remembered THIS SAME SHIZZ ALREADY HAPPENED TO ME
You are NOT bricked, just getting a lotof annoying FORCE CLOSE messages, ain't ???
If so, then this is what I did:
1.- remove the battery 30 secs
2.- hold vol down + power
3.- in bootlader, select "FACTORY RESET" (use vol keys to up-down)
Then my phone rebooted and everything was back to normal

gtrab said:
I just remembered THIS SAME SHIZZ ALREADY HAPPENED TO ME
You are NOT bricked, just getting a lotof annoying FORCE CLOSE messages, ain't ???
If so, then this is what I did:
1.- remove the battery 30 secs
2.- hold vol down + power
3.- in bootlader, select "FACTORY RESET" (use vol keys to up-down)
Then my phone rebooted and everything was back to normal
Click to expand...
Click to collapse
cool mate, so the accidental flashing of the OTA after the z.ko is not going to hurt anything?
JD

JupiterDroid said:
cool mate, so the accidental flashing of the OTA after the z.ko is not going to hurt anything?
JD
Click to expand...
Click to collapse
just do it
what else could go worst ??
when your phone turns stable, connect to PC and push wpthis-Z.ko again

gtrab said:
just do it
what else could go worst ??
when your phone turns stable, connect to PC and push wpthis-Z.ko again
Click to expand...
Click to collapse
Very true, will do that mate
Really appriciate your help
JD

Hi Friend,
I just had similar problem as you.
I rooted phone, flashed hboot s-off and..?
..first my Z was restarting in loop every 2-3 minutes.
I uninstalled VISIONARY+ and apps that force closed every boot.
But still there were many problems with my phone.
I couldn't install many apps from market,
and random ones just disappeared every reboot.
It wasn't nice.
Then I used Clockwork recovery, did clear cache, full wipe,
and the phone is in perfect condition, s-off, with clock-recovery,
after wipe my apps has been restored - including SuperUser,
and its rooted already, after wipe
No need to use VISIONARY+ again!
Try it
br,
condi

Related

[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!

New EVO User, Old XDA User

So can I or can't I root my phone?
Any tutorials? Searched for an hour. :/
Coming from MIUI HD2 by the way.
If gingerbread is on your phone (2.3.3)
http://forum.xda-developers.com/showthread.php?t=1218386
http://forum.xda-developers.com/showthread.php?t=1228566
If froyo is on your phone (2.2)
http://forum.xda-developers.com/showthread.php?t=838448
I don't mean to be mean, but 5 posts below yours answers your question.
mattykinsx said:
If gingerbread is on your phone (2.3.3)
http://forum.xda-developers.com/showthread.php?t=1218386
http://forum.xda-developers.com/showthread.php?t=1228566
If froyo is on your phone (2.2)
http://forum.xda-developers.com/showthread.php?t=838448
Click to expand...
Click to collapse
Stuck on "waiting on device". Followed instructions to a tee. On 2.3.3.
kariuki said:
Stuck on "waiting on device". Followed instructions to a tee. On 2.3.3.
Click to expand...
Click to collapse
Usually means debugging isn't on on ur phone. Go to setting/applications/ its in there
Papa Smurf151 said:
Usually means debugging isn't on on ur phone. Go to setting/applications/ its in there
Click to expand...
Click to collapse
Thanks for the reply, but I had recently uninstalled Sync, I restarted my pc, and now it's working.
Had everything working, when I tried to boot a ROM, it was stuck on the htc EVO 4G screen. I went into recovery and wiped everything. Now I'm definitely lost.
Bump, hope it's not bricked...
If you can boot into the white HTC screen, IT IS NOT BRICKED! Put your recovery so you can transfer another rom via usb to your sdcard, then flash a different rom after wiping everything!
Art2Fly said:
If you can boot into the white HTC screen, IT IS NOT BRICKED! Put your recovery so you can transfer another rom via usb to your sdcard, then flash a different rom after wiping everything!
Click to expand...
Click to collapse
I had to transfer a ROM from another phone to this one. Working now. Hope this is isn't a problematic phone.
kariuki said:
I had to transfer a ROM from another phone to this one. Working now. Hope this is isn't a problematic phone.
Click to expand...
Click to collapse
It also helps to know what recovery you're using to flash. Depending on the rom amonra works better than clockwork. I use amonra but that's just my preference. Not getting past the white htc screen isn't that problematic, battery pull vol down+power. How long you sit on the htc screen depends on the rom, some roms take all day to boot on that first one and you need to just let it sit and not panic. Some roms just don't work on some phones. I love Evolved's work but I could not get his "Directors Cut" rom to get past the white htc screen but my guy has the same hardware as I do and his booted right up. To me there is no perfect rom, it's the rom that's perfect for you. We're all different people and like different things. Happy flashing.
p.s.- Just make sure you do the usual wipes before flashing alot of devs also have a format zip that you should use as well. It really doesn't matter which one. Used them all and don't really have a preference to either of them.
Try doing a search next time buddy..
someonenewhere said:
Try doing a search next time buddy..
Click to expand...
Click to collapse
Why should he? Every question he asked, with attitude even, was answered in his thread even though the answers to all his questions were available all on the front page of the forum.
Sent from my Nexus S 4G using Tapatalk

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

Please.

Guys please I know this is the wrong forum but no one is answering help. At all. Alright, I went to flash the ICS Sense alpha, and needed to restore a backup. I went into hboot, and restored the PD98IMG.zip. Afterwards it said "Press power to reboot" so i did. The phone turned off, and now nothing. After a LONG time the phone turned on to the White HTC Splash and vibrated CONSTANTLY, until the battery was pulled. I tried volume down + power but nothing. Except for the occasional white screen, nothing. Please, anyone/.
You're bricked
Sent from my Desire HD using telepathy...
I think your phone had a bootloop. Did you already installed custom recovery? Can you enter it through fastboot menu (vol down + power)?
I doubt he's bricked,why are you restoring that zip? You restore your back up....from clockwork?
Sent from my Desire HD using XDA Premium App
It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG
HTC_Phone said:
It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG
Click to expand...
Click to collapse
I am confused. So what exactly happens when doing this:
remove or rename the PD98IMG on the sd card
pull the battery from the DHD
re-enter it and hold volume down and power until the hboot starts
navigate by volume down/up to Recovery and press POWER
If you had to restore back to factory, why bother flashing ICS?
You should get away by installing one of the RUU using PC. here is a guide on how to install RUU and you'll have to search this section to find a RUU or google it.
Though firstly i would ask you if you can go into the recovery mode anyhow since you're saying that your phone can get the HTC logo. For that, hold down POWER + volume DOWN key to get you into hboot (IF YOU CAN) and choose recovery from there, once in recovery, go to option where you wipe your data + cache, wipe both of em and try restarting again...If you can't even get into recovery then do the RUU way of getting the rom working.
EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.
Lol least its on
Sent from my Desire HD using XDA Premium App
HTC_Phone said:
EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.
Click to expand...
Click to collapse
Gratz, suppose this thread's unnecessary now?
Anyway take care of what you do: always do a nandroid backup prior to flashing everything. Better spend 5min for backup than 5 days without a phone.
I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Also spamming the threads is a pretty good way of getting banned. Maybe zel or Andy will be nice about it
marsdta said:
I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Click to expand...
Click to collapse
That sounds somewhat correct. I DID get it replaced, but had a GB PD98 on the SD card. Anyway, it vibrated for quite some time, and eventually the vibration stopped. So I let the phone sit as I figured out some way to salvage the phone. And the the next HTC splash booted, and the phone proceeded into the stock ROM. Idk what happened, but I'm not complaining.
Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.
HTC_Phone said:
Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.
Click to expand...
Click to collapse
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.
motherninja said:
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.
Click to expand...
Click to collapse
The phone itself is already rooted, but I tried booting into CWM, and it did the same thing as it did before. So I have to run the RUU, and then S on the phone, and run the hack kit again. I already ran the RUU once, and nothing.
Probably best just to start over and do everything again,even if you've already done it,maybe the root didnt work?
Your phones a nightmare mate
Sent from my Desire HD using XDA Premium App
So you intentionally created a thread in the wrong section?
I guess the rules don't apply to you then.

Help PLEASE random disaster

I was running virtuous primodonna. i wasnt doing anything, but my phone randomly illuminated with a black screen. i pulled the batter and when i rebooted it stayed at splash screen, then the screen showed random screwed up lines and all this. then it rebooted by itself and went to recovery. I've wiped my data and cache and dalvik but nothing works. i've tried restoring backups but it says that its failing to recover the system. please someone help
If no one knows. can someone please provide me with a rom that will brick my phone so it WONT BOOT UP WHATSOEVER. that way i can go to the tmo store for replacement? so they cant go into recovery and figure out i've rooted it. PLEASE someone
tradejak66 said:
I was running virtuous primodonna. i wasnt doing anything, but my phone randomly illuminated with a black screen. i pulled the batter and when i rebooted it stayed at splash screen, then the screen showed random screwed up lines and all this. then it rebooted by itself and went to recovery. I've wiped my data and cache and dalvik but nothing works. i've tried restoring backups but it says that its failing to recover the system. please someone help
If no one knows. can someone please provide me with a rom that will brick my phone so it WONT BOOT UP WHATSOEVER. that way i can go to the tmo store for replacement? so they cant go into recovery and figure out i've rooted it. PLEASE someone
Click to expand...
Click to collapse
Let's not brick your phone intentionally just yet! Try getting hold of a PD15IMG.zip (2.2.1 or 2.3.4, either works unless you want to root again, then go for 2.2.1). Boot into bootloader with the PD15IMG on the root of your SD, then let it update. If it doesn't and says Fail-PU, then you are bricked and could send it back to T-Mobile. Or you could try flashing another ROM. Hope this helps!
invasion2 said:
Let's not brick your phone intentionally just yet! Try getting hold of a PD15IMG.zip (2.2.1 or 2.3.4, either works unless you want to root again, then go for 2.2.1). Boot into bootloader with the PD15IMG on the root of your SD, then let it update. If it doesn't and says Fail-PU, then you are bricked and could send it back to T-Mobile. Or you could try flashing another ROM. Hope this helps!
Click to expand...
Click to collapse
tried that too..... and i dont want to send it back to t-mobile since they can still look and see its rooted. so yes thats why i need to brick it lol. please.
tradejak66 said:
tried that too..... and i dont want to send it back to t-mobile since they can still look and see its rooted. so yes thats why i need to brick it lol. please.
Click to expand...
Click to collapse
OK since that did not work, place the PD15IMG on your SD, and when it is updating, pull the battery. That will brick it for sure (I think..). Press thanks if I helped.
invasion2 said:
OK since that did not work, place the PD15IMG on your SD, and when it is updating, pull the battery. That will brick it for sure (I think..). Press thanks if I helped.
Click to expand...
Click to collapse
k hold up let me try
tradejak66 said:
I was running virtuous primodonna. i wasnt doing anything, but my phone randomly illuminated with a black screen. i pulled the batter and when i rebooted it stayed at splash screen, then the screen showed random screwed up lines and all this. then it rebooted by itself and went to recovery. I've wiped my data and cache and dalvik but nothing works. i've tried restoring backups but it says that its failing to recover the system. please someone help
If no one knows. can someone please provide me with a rom that will brick my phone so it WONT BOOT UP WHATSOEVER. that way i can go to the tmo store for replacement? so they cant go into recovery and figure out i've rooted it. PLEASE someone
Click to expand...
Click to collapse
do this: wipe data/factory reset
wipe cache
wipe dalvik
flash the original ROM (the one you have a backup of, but not the actual back up)
THEN restore the backup, it shouldnt get stuck at system anymore
i had a similar problem and this helped. hopefully it works for you
invasion2 said:
OK since that did not work, place the PD15IMG on your SD, and when it is updating, pull the battery. That will brick it for sure (I think..). Press thanks if I helped.
Click to expand...
Click to collapse
I've tried twice and it still boots :0
tradejak66 said:
I've tried twice and it still boots :0
Click to expand...
Click to collapse
Whoops. I think it's flashing a new radio then. Flash the radio just like you did with the PD15IMG and take the battery out during the process. If it still boots, I'll look into how to brick it lol!
invasion2 said:
Whoops. I think it's flashing a new radio then. Flash the radio just like you did with the PD15IMG and take the battery out during the process. If it still boots, I'll look into how to brick it lol!
Click to expand...
Click to collapse
lol. start looking now just in case.
invasion2 said:
Whoops. I think it's flashing a new radio then. Flash the radio just like you did with the PD15IMG and take the battery out during the process. If it still boots, I'll look into how to brick it lol!
Click to expand...
Click to collapse
I can't even access the recovery anymore. i have the PD15image thing pop up everytime so i cant get to the sd card whatsoever. i took out my sdcard then tried to access the recovery but it doesnt work
Actually, I think we've done a pretty successful job, because, they can't access the recovery, the PD15img keeps saying Fail-PU. the only thing left is S-Off, which i hope they dont notice >.>
tradejak66 said:
Actually, I think we've done a pretty successful job, because, they can't access the recovery, the PD15img keeps saying Fail-PU. the only thing left is S-Off, which i hope they dont notice >.>
Click to expand...
Click to collapse
I think you're fine honestly. Good luck matey!
Get a 12v power supply, cut the end off and strip the wires. Take the battery out and touch the wires to the phones battery contacts a couple times. Replace battery try to power on. If it doesn't turn on your done, if it does try again. Tell them it was on the charger and shut off when you unplugged it and wouldn't turn on.
Sent from my HTC Glacier using Tapatalk
tradejak66 said:
I can't even access the recovery anymore. i have the PD15image thing pop up everytime so i cant get to the sd card whatsoever. i took out my sdcard then tried to access the recovery but it doesnt work
Click to expand...
Click to collapse
I had a similar problem when the splash screen got stuck last night flashing a new radio. I took the sdcard and plugged it in the netbook, accessed the root rolder and renamed the PD15IMG.zip so the HBOOT wouldn't read the file. It stopped the HBOOT from reading the file so I could access Recovery then reflashed my recovery file. I forgot to do the data wipe/dalvik before I flashed the radio lol.
This is an AWESOME how to brick your phone on purpose guide good job guys
Sent from my ROOTIE TOOTIE FRESH 'N FRUITY GLACIER
OH GOD tmobile is out of MT4g's and i had to order one from HTC. they specificly stated they will make sure its not rooted and all that >.> I asked the woman what rooting was if that helped but obviously i dont think it will. Im pissed my pants when i heard that sentence. HTC is obviously more prone to finding root then T-mobile who will just throw the phone away 0_0
tradejak66 said:
OH GOD tmobile is out of MT4g's and i had to order one from HTC. they specificly stated they will make sure its not rooted and all that >.> I asked the woman what rooting was if that helped but obviously i dont think it will. Im pissed my pants when i heard that sentence. HTC is obviously more prone to finding root then T-mobile who will just throw the phone away 0_0
Click to expand...
Click to collapse
and then youre gonna be waiting another 2 months to recieve the replaced/repaired/refurbished phone..
you could have just made it work instead of completely bricking it
its an HTC android.. very, VERY hard to perma-brick
grimey01 said:
and then youre gonna be waiting another 2 months to recieve the replaced/repaired/refurbished phone..
you could have just made it work instead of completely bricking it
its an HTC android.. very, VERY hard to perma-brick
Click to expand...
Click to collapse
Where there's a will (and a hammer) there's a way.
grimey01 said:
and then youre gonna be waiting another 2 months to recieve the replaced/repaired/refurbished phone..
you could have just made it work instead of completely bricking it
its an HTC android.. very, VERY hard to perma-brick
Click to expand...
Click to collapse
Yea its hard to permabrick unless you don't want to brick it from what I hear...
Sent from my HTC Glacier
grimey01 said:
and then youre gonna be waiting another 2 months to recieve the replaced/repaired/refurbished phone..
you could have just made it work instead of completely bricking it
its an HTC android.. very, VERY hard to perma-brick
Click to expand...
Click to collapse
your assuming that it was software that broke >.> it was most likely hardware since it broke in this manner and no flashing, resets, anything helped. and its 2 weeks btw lol.

Categories

Resources