Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
wow, it seems like all the old school glacier users are having bad luck... Glad mine is still going strong though! Sorry to hear it though, you have been a great help to many of us and will be missed bro!
Sent from my HTC Glacier using xda premium
irrelephant said:
wow, it seems like all the old school glacier users are having bad luck... Glad mine is still going strong though! Sorry to hear it though, you have been a great help to many of us and will be missed bro!
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I'm on my 3rd one going strong :/ with bad screen and chip but I call every once in awhile to see if I can get a mt4gs. Good luck teejay! As for none booting just run pd15img and do a battery pull while it's updating until it won't turn on anymore
Sent from my HTC Glacier using xda premium
This is one of the reasons I had to jump ship on this phone. Was scared it might take a **** on any given time.
But I always love the MT4G, hopefully TJ can get something viable from TMO.
TeeJay3800 said:
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
Click to expand...
Click to collapse
that doesn't really look like failed eMMC yet... and you can't really tell until you flash PD15IMG.zip in bootloader. but yeah, if the phone can still boot, i think it's just that your recovery is messin' with ya
how about reflashing the recovery image and see if those errors are still there?
saranhai said:
that doesn't really look like failed eMMC yet... and you can't really tell until you flash PD15IMG.zip in bootloader. but yeah, if the phone can still boot, i think it's just that your recovery is messin' with ya
how about reflashing the recovery image and see if those errors are still there?
Click to expand...
Click to collapse
You think re-flashing the recovery will eliminate the errors? I could be wrong, but it seems to me that even if that works, the errors could still reappear at any time. My gut says there is an actual hardware problem, and that measures like recovery flashing would only be a temporary fix. Worth a shot though.
TeeJay3800 said:
You think re-flashing the recovery will eliminate the errors? I could be wrong, but it seems to me that even if that works, the errors could still reappear at any time. My gut says there is an actual hardware problem, and that measures like recovery flashing would only be a temporary fix. Worth a shot though.
Click to expand...
Click to collapse
yeah, worth a shot lol
but well, like i said before, unless you try the PD15IMG file and it gives you Fail-PUs, you don't know if it's dead eMMC. but if your phone still works, then i doubt the chip died...
Your eMMC most likely isn't dead or anywhere near. Cache errors in recovery can be a lot of things, usually partition corruption.
If you have engineering bootloader, try "fastboot erase cache" and "fastboot flash recovery". If that doesn't help - flash PASSIMG and re-root (after you backed up the ROM, of course).
I heard awhile back that there was a way to enter some commands through terminal emulator to the hboot partition that will brick the phone. dont know which partition it is though.
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
my2sense said:
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
Click to expand...
Click to collapse
Had the exact same thing happen to me yesterday.
Mine went belly-up recently too. No Failed-PU message but it would not flash or boot properly. Powered it on and got a 7 to 8 vibrates in a row on the splash screen before it powered itself off. Recovery (4EXT) failed to restore a nandroid (couldn't mount data) and shortly thereafter couldn't boot recovery. Flashing recovery (and original splash) through ADB fastboot claimed to be successful but didn't actually work. Flashing PD15IMG from bootloader also failed, shortly into it. T-Mobile sent a warranty replacement MT4G (it was just under 1 year). Bad screen and eMMC, but I'll live with it. Will find out if they notice the engineering bootloader and custom splash...
Jack_R1 said:
Your eMMC most likely isn't dead or anywhere near. Cache errors in recovery can be a lot of things, usually partition corruption.
If you have engineering bootloader, try "fastboot erase cache" and "fastboot flash recovery". If that doesn't help - flash PASSIMG and re-root (after you backed up the ROM, of course).
Click to expand...
Click to collapse
my2sense said:
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
Click to expand...
Click to collapse
Well, this is a little embarrassing, but it seems that a simple cache wipe fixed the problem. I was hesitant doing that initially thinking that would aggravate the problem and make the phone unusable. The question now is what caused it. Last week I flashed the newest radio. I knew that in some cases a cache wipe was necessary after flashing a radio to prevent freezing at the slash screen, but my phone booted normally after the radio flash and worked fine for days after. This is the first case I've heard of where I radio flash caused cache errors in recovery. In any case, it all seems fine now so thanks all for the kind words and input.
If you've flashed radio from recovery - the script that didn't properly unmount the /cache partition after flashing and before reboot might have been the reason for corruption, or some well-hidden bugs in the CWM itself.
Anyway, glad that your phone is working. It's better to panic and be relieved, than not to panic but get things screwed
Jack_R1 said:
If you've flashed radio from recovery - the script that didn't properly unmount the /cache partition after flashing and before reboot might have been the reason for corruption, or some well-hidden bugs in the CWM itself.
Anyway, glad that your phone is working. It's better to panic and be relieved, than not to panic but get things screwed
Click to expand...
Click to collapse
I only flash radios via fastboot commands from the computer, but I think you're right about something not unmounting or a CWM bug. There were something like half a dozen CWM bug-fix releases after the original version 5, so it wouldn't be too surprising. And yeah your last statement is exactly correct!
TeeJay3800 said:
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
Click to expand...
Click to collapse
Sorry to hear that, if you was to give an estimate, how many roms have you flashed before this happened, also tmobile still ships mt4g, i just ordered a replacement for my girlfriend last week thursday and she received a new phone next day.. she had the bad emmc(Embedded Multi-Media Card) chip, i ran the code with terminal emulator and she's not rooted, she's on stock rom..her problem was the buttonS was not responding..after she received the new phone, it still had the bad chip(she don't care as long as the darn phone works).. so you just might get a good or bad one either way i believe they still ship the mt4g.
jr_718 said:
Sorry to hear that, if you was to give an estimate, how many roms have you flashed before this happened, also tmobile still ships mt4g, i just ordered a replacement for my girlfriend last week thursday and she received a new phone next day.. she had the bad emmc(Embedded Multi-Media Card) chip, i ran the code with terminal emulator and she's not rooted, she's on stock rom..her problem was the buttonS was not responding..after she received the new phone, it still had the bad chip(she don't care as long as the darn phone works).. so you just might get a good or bad one either way i believe they still ship the mt4g.
Click to expand...
Click to collapse
Thanks, but did you read the rest of the thread? No replacement for me, at least not yet.
TeeJay3800 said:
Well, this is a little embarrassing, but it seems that a simple cache wipe fixed the problem.
Click to expand...
Click to collapse
Awesome. Glad it worked for you too. I never had to clear cache after radio flash before either except for the latest radio. Freaked me out too when I first saw it too
my2sense said:
Awesome. Glad it worked for you too. I never had to clear cache after radio flash before either except for the latest radio. Freaked me out too when I first saw it too
Click to expand...
Click to collapse
I hadn't had to either. There's definitely something different about this latest radio.
Related
Well I have had my Xoom now for about a month. I use it pretty heavily and as soon as I got it I rooted it and installed Tiamats v1.4.4 kernel with OC'd GPU. I was running pretty flawless OC'd to 1.5Ghz until last night. I was in the middle of reading some posts on here on tapatalk and out of the blue the screen went black and rebooted. It was stuck on the spash screen for 20 minutes. I tried a hard boot and got bootloops.
I then downloaded the stock images and reflashed it back to stock and even relocked the bootloader. Still bootloops. I ended up flashing the stock images like 3 times in all with the same results. Sometimes I can get into the OS and go through setup and sometimes not. Most of the time if I can get into android apps start force closing and it reboots, or the touchscreen becomes unresponsive. I noticed most of the time when rebooting I get bright white flashes of light on the splash screen. Here is a video of the boot sequence:
http://www.youtube.com/watch?v=1ctODeIPANU&feature=player_profilepage
Around 1 minute into the video you can see the white flashes of light. Anyone know if there is any chance of recovering this? BTW, its a verizon 3g xoom. I'm pretty sure its a brick. I just wanted to see if anyone else had seen this same thing happen.
EDIT: I also noticed that sometimes the front camera is flashing red also when rebooting. Weird.
Had you updated any apps like superuser or busybox installer? Were you able to do a nandroid recovery through CMR? What stock files did you flash (what version?) I'll bet you are not completely bricked...there seems to be a fix for almost every crash. It's just that without knowing anything about why it may have crashed or exactly what you did afterwards it hard to know how to help.
okantomi said:
Had you updated any apps like superuser or busybox installer? Were you able to do a nandroid recovery through CMR? What stock files did you flash (what version?) I'll bet you are not completely bricked...there seems to be a fix for almost every crash. It's just that without knowing anything about why it may have crashed or exactly what you did afterwards it hard to know how to help.
Click to expand...
Click to collapse
I didn't update anything at all. I tried my stock nandroid and it locked up too. I tried flashing both factory images for the VZW xoom from motorolas website and they both do the same thing. I've never seen it lock up so much and the screen become unresponsive like it is. Restoring it to factory should fix it and after 3 times of flashing the stock images it should be fine, but its not. The stock files I tried were MZ600_HRI39 and MZ600_HRI66. I'm not sure what else to even try. The flashing white screen and the camera flashing red are definitely not a good sign.
sabbotage said:
I didn't update anything at all. I tried my stock nandroid and it locked up too. I tried flashing both factory images for the VZW xoom from motorolas website and they both do the same thing. I've never seen it lock up so much and the screen become unresponsive like it is. Restoring it to factory should fix it and after 3 times of flashing the stock images it should be fine, but its not. The stock files I tried were MZ600_HRI39 and MZ600_HRI66. I'm not sure what else to even try. The flashing white screen and the camera flashing red are definitely not a good sign.
Click to expand...
Click to collapse
Wow, maybe you have a hardware failure. Did it act funky before at all? I saw that it just bootloops by itself...can you still get it into any kind of recovery? I think that if you can get into fastboot and use adb, you can do a wipe and maybe start over. Of course it you have a hardware fail that's another issue.
okantomi said:
Wow, maybe you have a hardware failure. Did it act funky before at all? I saw that it just bootloops by itself...can you still get it into any kind of recovery? I think that if you can get into fastboot and use adb, you can do a wipe and maybe start over. Of course it you have a hardware fail that's another issue.
Click to expand...
Click to collapse
Yeah i can get into fastboot and I tried erasing everything before reflashing the stock images with no luck.
Sent from my HTC Thunderbolt using Tapatalk
sabbotage said:
Yeah i can get into fastboot and I tried erasing everything before reflashing the stock images with no luck.
Sent from my HTC Thunderbolt using Tapatalk
Click to expand...
Click to collapse
If you can go to the IRC Xoom Channel you could chat with people who know much more than I do. I think with your weird light flashes and continuous boot cycle, that might be your best bet. The address is in brd's signature line.
I sincerely wish you good luck!
okantomi said:
If you can go to the IRC Xoom Channel you could chat with people who know much more than I do. I think with your weird light flashes and continuous boot cycle, that might be your best bet. The address is in brd's signature line.
I sincerely wish you good luck!
Click to expand...
Click to collapse
Thanks I jumped on there and i'll see what everyone says. I've tried it all and nothing is working.
OK heres the deal. I have done tons of searching and it looks like I SHOULD be able to get out of this, but I cant figure it out and I may have gone to far(by unrooting with 4.24 and bootloader 2.16).
So long story short, my launch day evo got lost about a month after I got it. Got a replacement from Sprint(or whoever their insurance is), my original Evo got found about a month or so after that. It has not been powered on since then(a year realistically) with no battery or SD card in it. I got bored and decided to power it up and update everything(because I cant do **** with my new Evo3d, yet since im on a Mac and have no access to a PC). Here are where things went bad.
Phone was rooted with the very original Toast method including S-off with the .76 Eng boot loader. I was running some form of CM6 on it when I lost it.
-Went to power it up and it boot looped at the white Evo4g screen.
-Went into bootloader and tried to get into recovery(had Amon RA 1.7 I think). No go.
-Flashed the new TWRP recovery and got into recovery just fine.
-Flashed the CM7.1.0-RC1
-reboot into a boot loop
-battery pull and a reboot and it loaded, but after about 30 seconds, reboot into a boot loop.
-Thought maybe TWRP didnt like the phone so I flashed Amon RA 2.3
-went into recovery just fine. Did complete wipes of everything using Calkulin Wipe all.zip
-re-flashed CM7.1.0 RC1
-boot loop
-flashed latest radios
-rebooted back into recovery
-reflashed cm7.1.0 rc1
-boot loop
During all of the reboots I would occasionally get the CM7 splash screen and then a reboot into boot loops. I THINK everything was flashing ok.
At this point I was frustrated and was thinking it was something I was doing that was jacked up so I decided to unroot and I flashed the newest RUU(which obviously removes root, S-off, .76 boot loader, etc...) so I did it. Figured I was just trying to get the phone running to sell anyway. Flashed was successful, chose to reboot and guess what. Boot loop. I pulled the battery out for about 10 minutes and it boots into the rom, runs for about 10-15 seconds in the rom and then reboots, back into the rom at least, but only about 10-15 seconds later, another reboot.
Every thread I read on these infinite boot loops were guys saying they couldnt even get into recovery or flash anything, which I had no problem doing(obviously cant really do that anymore with losing root and s-off). So I am stuck.
So current state of the phone is boot loader 2.16 S-on with 4.24.651.1 with all current radios, etc... flashed(as far as I can tell) from the RUU posted on Goo-inside.me.
Does anybody have any ideas for me to try? It seems like I am so close to getting it running because it will run for about 60 seconds but then reboot. I am guessing a hardware issue, but I honestly at this point have no clue.
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Rem3Dy said:
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Thats what I am leaning towards, but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
drdrewdown said:
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
Click to expand...
Click to collapse
I know. I probably should have posted up and waited, but I got impatient and thought that was a last ditch effort anyway since I tried everything else I knew to try.
rjacobs said:
but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
Click to expand...
Click to collapse
because in the boot loader and recovery menu I'm sure the phone is not accessing radios, audio components, gps, and all manner of other hardware components that get activated once the phone tries to boot up for real.
It sounds like according to this thread: http://forum.xda-developers.com/showthread.php?t=805612&page=4
That my NV is FUBAR, but since I ran RUU and lost S-off, I cant do the fix. Oh well, I am sure eventually somebody will crack the boot loader and then I can fix it. Otherwise I have to send it off to HTC and I am sure pay them to fix it.
Just to clarify. The thread you linked to is for people who wrote nv items to their device.
What I'm afraid you are experiencing is the bootloop commonly complained about by those running CM roms.
I have yet to find a solution to the CM bootloop and all signs point to hardware failure.
Sent from my Evo using XDA Premium App
Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.
TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven
TWRP2.0 is an evo killer as far as I know there is no fix for a TWRP brick I'm pretty sure it messes up something in the partitions possibly boot or system partition which is why it bootloops
We are legion, for we are many
Unfortunately your phone is toast. Had the same problem, and really there is no way to recover. You should have bit the bullet in used insurance instead of going through Sprint since the Evo is past EOL. You maybe waiting a long time to get a replacement where as going through Ausion (sp) you either would have gotten either a new Evo, a refurb'ed Evo, or a new Evo3D (most likely).
Sent from my ICS-less Transformer TF101 using Tapatalk
Art2Fly said:
Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.
Click to expand...
Click to collapse
scottspa74 said:
TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven
Click to expand...
Click to collapse
It's been a busy week for me, but I am still alive, and still using my previously-soft-bricked device .
I can link you to what I was able to do to get mine working (HERE), but if you can't get the device to boot up at all, you might be in dire straits. What is your HBOOT status? (version, NAND status)
hey Cap'n, you need some kind of superhero shield in your user icon
sent from AOKP heaven
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.
Okay, so first off, I'm literally about to light this fking thing on fire.
This damn phone has been the death of me. I have a Tbolt and Galaxy Tab, and NEITHER have been as much of a pain in my ass.
This seems impossible because since I got the phone, I've had nothing but problems.
1. Unlocked bootloader via fastboot. K, done.
2. Flash AmonRa Recovery (I did this before AND after using CWM recovery, having custom rom, etc, it never worked) Always sat in a loop at the google X with unlock symbol, or just reboots into normal (and yes, the MD5s are correct) 3. I've had the phone get into the rom both with SIM and without, and randomly reboot, from using anything from market, to file explorer, to hitting the lock screen.
Honestly, I'm tempted to just sell it again (since I bought it off ebay) and buy something different, though that's a pain to do, and I need it for a trip to europe in a week, so I would love to have a phone I'm not pissed off at. And yea, already got mad enough I threw it.
I've literally spent HOURS looking through Google results on all the issues. And have YET to make this lil pos stable enough for me to use like I do my tbolt. nice 100 battery pulls. Seriously. Heeelllpp on this, :-/
hkbladelawhk said:
Okay, so first off, I'm literally about to light this fking thing on fire.
This damn phone has been the death of me. I have a Tbolt and Galaxy Tab, and NEITHER have been as much of a pain in my ass.
This seems impossible because since I got the phone, I've had nothing but problems.
1. Unlocked bootloader via fastboot. K, done.
2. Flash AmonRa Recovery (I did this before AND after using CWM recovery, having custom rom, etc, it never worked) Always sat in a loop at the google X with unlock symbol, or just reboots into normal (and yes, the MD5s are correct) 3. I've had the phone get into the rom both with SIM and without, and randomly reboot, from using anything from market, to file explorer, to hitting the lock screen.
Honestly, I'm tempted to just sell it again (since I bought it off ebay) and buy something different, though that's a pain to do, and I need it for a trip to europe in a week, so I would love to have a phone I'm not pissed off at. And yea, already got mad enough I threw it.
I've literally spent HOURS looking through Google results on all the issues. And have YET to make this lil pos stable enough for me to use like I do my tbolt. nice 100 battery pulls. Seriously. Heeelllpp on this, :-/
Click to expand...
Click to collapse
try
fastboot erase cache
fastboot erase userdata
fastboot erase system
and then flash via fastboot the AmonRa recovery again.
BTW, which ROM are you trying to flash? ICS or Gingerbread? And do you have Blackrose installed?
taodan said:
try
fastboot erase cache
fastboot erase userdata
fastboot erase system
and then flash via fastboot the AmonRa recovery again.
BTW, which ROM are you trying to flash? ICS or Gingerbread? And do you have Blackrose installed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=872441 << Flashed this.
So far, I've knocked my network to 2g and it's been fine. though not really much of a fix. And I had cleared all of the above using CWM prior to the attempted flash. I'd rather not have to wipe everything again just to get AmonRa. I've wiped quite a few times. Though did get something about /sd-ext missing when erasing via CWM. Also, I tried erasing recovery, and got this: "erasing 'recovery'... FAILED (remote: not allowed)". Not sure if that matters. Just seems that flashing via Fastboot has failed everytime. I flashed CWM via fastboot and that failed too, I ended up getting it working via RomManager.
I had the same problem. After i dropped my phone on the floor everything worked fine
Sent from my GT-I9001 using Tapatalk
jojogangsta said:
I had the same problem. After i dropped my phone on the floor everything worked fine
Sent from my GT-I9001 using Tapatalk
Click to expand...
Click to collapse
Yea, though I still feel like I'm getting intermittent reboots. IT's not an everyday use phone, so I'll have to see how it fares when I'm overseas.
flash 4ext touch via 4ext recovery control app
Then install a different rom like miui or cm7 or hypersense nova
Sent from my Nexus One using XDA
joelshawdow said:
flash 4ext touch via 4ext recovery control app
Then install a different rom like miui or cm7 or hypersense nova
Sent from my Nexus One using XDA
Click to expand...
Click to collapse
Done and done. Still have a problem with boot looping. Google X with vibration, then goes black and does it again, and it loops like that indefinitely. Though this isn't new, been since I unlocked it....POS.
Deleted
Leave it in a freezer for a day no joke
Sent from My Samsung Galaxy S2 running Paranoidandroid Rom.What else if not?=P
First of all any ROM you find here for an update is going to have bugs. So have to prepared for reboots, and/or no boots.
On the other hand, you have to verify to see if you have any hardware issues. In order to do so, you have to flash to a stock ROM to see if the issue continues. If stock ROM is just fine, then its the custom ROM that is causing grief! So try another custom ROM, until the one that suits your needs.
my sugestion 2 u - use cm7.2. use 4ext touch recov, wipe all ur stuff, flash blackrose hboot with no repartitioning, flash cm7.2 rom, finally, stop b!tching!
ai6908 said:
First of all any ROM you find here for an update is going to have bugs. So have to prepared for reboots, and/or no boots.
On the other hand, you have to verify to see if you have any hardware issues. In order to do so, you have to flash to a stock ROM to see if the issue continues. If stock ROM is just fine, then its the custom ROM that is causing grief! So try another custom ROM, until the one that suits your needs.
Click to expand...
Click to collapse
Did it when it went back to stock. And Whoever said put it in the freezer, I did, and worked on it with AC on it, and it worked better . Though for some reason, never been able to flash recoveries via fastboot. Oh well. 4ext rocks.
hkbladelawhk said:
Did it when it went back to stock. And Whoever said put it in the freezer, I did, and worked on it with AC on it, and it worked better . Though for some reason, never been able to flash recoveries via fastboot. Oh well. 4ext rocks.
Click to expand...
Click to collapse
I never had any luck flashing recovery using fastboot either. Anyhow, it sounds like a motherboard issue to me. Sorry pal!
ai6908 said:
Anyhow, it sounds like a motherboard issue to me. Sorry pal!
Click to expand...
Click to collapse
This. The description fits overheating and overly sensitive to temperature CPU.
yon can flash another rom
yon can flash another rom
Still having bootup problems
Okay, sorry to bring this back up, but I am still having an issue with the phone booting. If I get the phone on, it's fine, doesn't randomly turn off or anything. However, if I try to reboot, power off and power back on for any reason....it becomes a pain to get back up and running. I usually have to do a couple battery pulls before it comes back up. Does the same thing. Hits the X, vibrates once like it's gonna turn on. Then a few seconds to a min later, goes black, then flashes the x and vibrates once again. It loops like this until I pull the battery and try again. Sometimes it takes a couple times to work. Its not the ROM either, because this is the issue I had when I first got the phone and did fastboot oem unlock. It would hang on stock. It's done it on all 3 ROMs I've tried. I don't wanna say fully it's a CPU issue, because I don't have issues once it's on.
Any new idears?
PS. I tried CM7, and I didn't like it. Not a fan of AOSP ironically enough.
The Nexus One will give off 7 Vibrations to indicate a hardware issue, we will just have to wait and see