Database Users

fastboot flash cwm failed: remote not allowed

I fubared my royalgingerless glacier this afternoon, it stuck on the mytouch boot screen for over 30 minutes after attempting to flash the new sense 3.0 3d rom. (I know I'm sure I did something dumb)
Before that flash I did a wipe all and flash, it flashed, I rebooted and then it hung on the mytough screen for over 10 minutes. I pulled the batt, and had no boot, went to cwm and tried to restore my cwm backup and it said something like e: cache not found etc..
Well I tried to wipe the cache, same deal, tried a bunch of other stuff, no avail, put the pd15img.zip on my sd card, it ran
Parsing ...[SD.Zip]
Recovery -Fail-PU
Boot -Fail PU
Radio_V2 -Updating
it hangs here, so I pulled batt,
At this time I have lost recovery, still have fastboot and hboot so I am not a brick as far as I know.
fastboot devices returns SH12JRM00507 so somethings happening...
I have showing
GLACIER PVT SHIP S-OFF
HBOOT-0.86.000
RADIO-26.0.3.02.26_M
eMMC-boot
Sept 27 2010,11:12:59
Ive been at this for a while, slipped my tmo chip back ino my hyperdroid hd2 and am awaiting some good thoughts on what to do next.

Please search the numerous threads about "Fail-PU", including recent "Rooting dangers" thread in Development section. To say it shortly - your phone is dead.

Cool thanks
I got it completely kia now I'll call htc fore repairs.

another one bites the dust...... this is getting serious
happened to me a couple of days ago and suddenly its spreading like wildfire. I got rid of the mytouch because of it but i really hope it gets resolved soon
side thought: i dunno about anyone else, but isnt the Sense 3.0 rom being mentioned a lot when this happens? Coincidence? Hope so

Same Here
Almost exact same scenario happened to me, except I wasn't trying to flash anything. I was running CM7...whatever the latest nightly was about a week ago. I started getting random reboots, then it just finally stuck on the MyTouch boot screen. I am able to get into HBOOT, FASTBOOT, and CWM Recovery no problem. Attempting to flash ANYTHING just locks up and/or fails.
Time to move to Verizon anyway....boo!

"Almost exact same scenario happened to me, except I wasn't trying to flash anything."
It's crazy that you're able to access the phone thru hboot yet for naught. I've read all the threads like a detective, and it still puzzles, that with the access you still have to CWM and fastboot, that you're not able to repair the situation.
What could these guys have done differently to avoid this?
tankmorph has access to cwm and fastboot - isn't that supposed to allow him to apply some herioc measures to get out of this? At least, that's why I flashed my 085 hboot, to be available in situations like this...
Stinks.

If you just get partition mount failure - ENG HBOOT will help you out of it.
If you have Fail-PU - you need to replace the eMMC on the board (which I'm not sure is possible). Access to bootloader won't help.

[Q] Help - MT4G intermittently works then loops

I bought my wife a MT4G
Always completely stock running Froyo
No water or drop damage
2 days ago, it would just die.
on reboot, several processes would force close and never be usable.
- once this happens a bettery pull is required.
- If i dont pull the battery on a failed boot, the phone wont charge.
I entered HBoot and did a factory reset, the phone must have lost its ROM and just deleted everything as it didnt boot at all after that.
I did research and found that i could put PD15IMG.zip on the root of the SD card, boot into HBoot, and it would flash.
Success!! i booted it up, and loaded my wifes accounts and even rebooted successfully several times. Gave it back to my wife and considered it done.
Until 1 hour later when the phone wouldnt respond again.
Same issue. force closes all over the place.
Repeated HBoot with success, but more sleep of death issues.
any recommendations? I have not tried to do anything in ADB, and would perfer to avoid it, but if necessary i can read up and use it if it will help.
I dont believe it is a bad eMMC, but then again, i am not sure.
I switched to Family Mobile so I cant just go into a T-Mobile store and get a replacement.
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.03.26_M
eMMC-boot
Sep 27 2010, 11:12:59
Thanks in advance.

I suggest you do an upgrade to stock Ginger Bread. Follow the link in my signature.
Select the unrooted version & follow the instructions....
Sent from my HTC Glacier using Tapatalk

Thanks for the GB image. Unfortunately the same thing happened after i flashed it.
Have there been reports of the system memory failing/having faulty connections?
It seems to work every once in a while, but when it doesnt, it keeps looping the "My" boot screen. almost like it cant find the system image anymore.
if it is faulty and within a year, can i call HTC? or does it have to go through t mobile? and will tmobile honor the warranty if i am not a customer?

hkstallion said:
Thanks for the GB image. Unfortunately the same thing happened after i flashed it.
Have there been reports of the system memory failing/having faulty connections?
It seems to work every once in a while, but when it doesnt, it keeps looping the "My" boot screen. almost like it cant find the system image anymore.
if it is faulty and within a year, can i call HTC? or does it have to go through t mobile? and will tmobile honor the warranty if i am not a customer?
Click to expand...
Click to collapse
try with HTC.

This sounds familiar, I remember someone posted the same problem a while back... I think your phone is about to die. well that's what happened to his. He had the bad chip. Do a warranty exchange
Sent from my HTC Glacier using XDA App

Final Update
i called HTC, and they issued an RMA.
thanks for all the help.

[Q] Mytouch 4g 2.3.4 not responding

I attempted to root my 2.3.4 phone using visionary. I didn't check the eMMC code before starting. I'm an idiot, I know. Now it freezes on startup and hard reset, without ever turning on. I can get into hboot. Here's what happened:
1) Attempt temp root using visionary
2) Visionary quits before finishing and doesn't restart. Terminal emulator says permission denied when I type su, thus temp root has failed.
3) Phone totally laggy so I restart.
4) Bootflops on round "my" ball screen
5) Attempt hard key reset, freezes on mytouch 4g screen
6) Went to Tmobile store (found I'm no longer in warranty -game on-
7) Attempt to flash 2.3.4 RUU from saranhai's anti-bricked guide
8) Loads the ROM, checks it, goes back to hboot as if nothing happened (I tried 7-8 two times in case of corrupted download)
9) I try to reboot and still hangs on the mytouch screen
10) Attempt to flash the 2.2.1 RUU for kicks. error says Main version is older! Update fail!
11) Decide to connect using super easy 5 min ADB process provided by TrueBlue_Drew [my thought here is that somehow I could push something this way?]
12) Device not shown when i type /adb devices
13) I troubleshoot 12 by switching computers, no go. Then I hook my wife's mytouch up, and voila, I see her device.
My thoughts: I can't check eMMC type because my phone won't turn on.
I can't turn on USB debugging (for ADB connection) because my phone won't turn on. But it should have been on from the original Visionary attempt.
I was running 2.3.4 with new latest software update that had been released in mid December.
Here is the info from the hboot:
GLACIER PVT SHIP S-ON
HBOOT-0.89.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC- boot
Jul 15 2011, 16:45:17
My two ideas were to 1) reflash using the sd card [which failed see step 8], and 2) connect with adb [which failed see step 12].
Any other ideas before I say "oh well, faulty eMMC chip?"
Thanks

Wow.
1. You can read. You followed saranhai's guide. I'm speechless. No one ever reads. They just go OH MY GOD! HEEEEEELP! Nice job.
2. It sounds like you got unlucky buddy. I have 2 MT4G's with the "bad" chip. Both are rooted. Both are fine. What a drag. You aren't an idiot. Just unlucky.
Edit: Did the rep at T-mobile enter anything into your account info saying your warranty is void? If not, I'd call em and say it crashed is acting crazy. They may send you another.
Sent from my HTC Glacier using XDA App

Ended up getting a new phone
So if anyone cares...
I called T-mobile and even though I'm out of warranty (14 months), they are going to send me a new (or like new) phone, with only a $20 restocking fee.
Go T-Mobile

doctorjay15 said:
I attempted to root my 2.3.4 phone using visionary. I didn't check the eMMC code before starting. I'm an idiot, I know. Now it freezes on startup and hard reset, without ever turning on. I can get into hboot. Here's what happened:
1) Attempt temp root using visionary
2) Visionary quits before finishing and doesn't restart. Terminal emulator says permission denied when I type su, thus temp root has failed.
3) Phone totally laggy so I restart.
4) Bootflops on round "my" ball screen
5) Attempt hard key reset, freezes on mytouch 4g screen
6) Went to Tmobile store (found I'm no longer in warranty -game on-
7) Attempt to flash 2.3.4 RUU from saranhai's anti-bricked guide
8) Loads the ROM, checks it, goes back to hboot as if nothing happened (I tried 7-8 two times in case of corrupted download)
9) I try to reboot and still hangs on the mytouch screen
10) Attempt to flash the 2.2.1 RUU for kicks. error says Main version is older! Update fail!
11) Decide to connect using super easy 5 min ADB process provided by TrueBlue_Drew [my thought here is that somehow I could push something this way?]
12) Device not shown when i type /adb devices
13) I troubleshoot 12 by switching computers, no go. Then I hook my wife's mytouch up, and voila, I see her device.
My thoughts: I can't check eMMC type because my phone won't turn on.
I can't turn on USB debugging (for ADB connection) because my phone won't turn on. But it should have been on from the original Visionary attempt.
I was running 2.3.4 with new latest software update that had been released in mid December.
Here is the info from the hboot:
GLACIER PVT SHIP S-ON
HBOOT-0.89.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC- boot
Jul 15 2011, 16:45:17
My two ideas were to 1) reflash using the sd card [which failed see step 8], and 2) connect with adb [which failed see step 12].
Any other ideas before I say "oh well, faulty eMMC chip?"
Thanks
Click to expand...
Click to collapse
you know, there's a reason i made that guide... Please read before acting next time.
Anyhow, I'm glad you got a replacement. Treat it well lol
Sent from my HTC Glacier Sense 3.5 using xda premium

doctorjay15 said:
So if anyone cares...
I called T-mobile and even though I'm out of warranty (14 months), they are going to send me a new (or like new) phone, with only a $20 restocking fee.
Go T-Mobile
Click to expand...
Click to collapse
Alright! Hopefully you get a good screen. Lol
Sent from my HTC Glacier using XDA App

Sorry I just saw your thread.
I didn't see in your description that you attempted as simple a thing as factory reset your phone. If you did and the phone still didn't boot up - yes, you're out of luck, because you need some basic ADB functionality to allow temp-rooting. If you didn't - well, pity, but you're lucky to only spend $20, so it doesn't matter much.
Just for people who might read it further: you didn't do anything to your eMMC, because you never got to run gfree. If it failed - which is completely unclear, since without factory reset you won't know - it failed with unfortunate timing, but without any connection to your rooting attempt.
The thing that should have been done, is just temp-rooting and reflashing misc partition while having adb shell during bootloop, so you could have downgraded easily - and it would also either solve the bootlooping problem or confirm dead eMMC by showing "Fail-PU".
And factory reset can be done from a stock bootloader.

I had a very similar problem and fixed it
I'm up and running again !! I found a PD15IMG.zip file on the t-mobile support website that worked specifically for the latest 2.32.531.1 update !! After downloading it, renaming it to PD15IMG.zip, copying it to the MicroSD card and booting into HBOOT, it found the file, loaded and checked it and asked me if I wanted to update. Everything is working since. Here is the download link (I've uploaded it to megaupload): http://www.megaupload.com/?d=X1EAIPBJ
This is what happened: I bought two MyTouch 4G's on craigslist from the same seller (a couple) and his phone works fine, only hers was corky, it wouldn't go past the MyTouch 4G screen. Both HBOOT screens are identical too, I checked his software version and it is the latest one (2.32.531.1), so I assume that hers is the same, it also shows the same date, July 15 2011 and the same radio 26.13.04.19_M in HBOOT. After trying both different PD15IMG.zip files (2.3.4 and 2.2.1), I've been getting the "main version is older" errors on both. No Fail-PU though, so that made me hopeful that there was a solution. I'm thinking that she updated to the latest version and somehow it got corrupted, that is why the phone was stuck at the MyTouch 4G loading screen and wouldn't go any further.

Congrats! Are you planning to root, because downgrading is a bear.
Sent from my HTC Glacier using XDA App

estallings15 said:
Congrats! Are you planning to root, because downgrading is a bear.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Absolutely !! Rooting is the only way to go I LOVE Virtuous Unity 2.39.0 with Beats Audio and the working Genius Button Fix and they are selling like Hotcakes on Craigslist The battery life is about twice as good as with a stock ROM too and it has Sense 3.0 The downgrading to 2.2.1 was actually not that bad, I had done it twice before and I followed the instructions on this thread, it took me about 15 minutes per phone. ADB is not that hard, I was a little bit hesitant at first but if you make sure that you don't have any typos in the commands it's pretty easy. http://forum.xda-developers.com/showthread.php?t=1178912

Well, awesome! Haha.
Glad your enjoying your phone.
Sent from my HTC Glacier using XDA App

Cool man! That sounds EXACTLY like what would have fixed my problem. Glad you were able to figure it out

doctorjay15 said:
Cool man! That sounds EXACTLY like what would have fixed my problem. Glad you were able to figure it out
Click to expand...
Click to collapse
I'm all woman my friend I don't think there are too many gals out there who are into this kind of technical stuff but I definitely love figuring things out, making things work again and help others. I buy MyTouch 4G's on eBay and Craigslist, I fix them, root them and install a custom ROM and resell them on Craigslist for a nice profit LOL Besides that I'm a computer tech

Ok, i know that i am a little late to the party but if you want to root the Mytouch 4g on gingerbread, there is a massive process....trust me. You have to know how to use ABD and u gain temproot through that, not visionary, which doesn't work on gingerbread. Then you have to change the version value for gingerbread so it think that it is updating to froyo. Then you downgrade and use visionary and gfree. I have a "bad" emmc too phone is still going strong though.
Bring you MT4G to the DARKSIDE.

PCLiteratesJax said:
I'm all woman my friend I don't think there are too many gals out there who are into this kind of technical stuff but I definitely love figuring things out, making things work again and help others. I buy MyTouch 4G's on eBay and Craigslist, I fix them, root them and install a custom ROM and resell them on Craigslist for a nice profit LOL Besides that I'm a computer tech
Click to expand...
Click to collapse
My bad, WOman!!! That's awesome you are able to get this little side hobby going. If I have questions during root once I get my new phone, I will know who to ask!

So the refurb phone I got from Tmobile had an inferior display and another "bad" emmc. So I called them up and told them the display sucked, and they are sending me another, overnight, for the 5 dollar warranty return fee. The guy said there was no way to make sure that I get a good display, but he seemed to understand the display issue. I'm just hoping for the "good" emmc as well. I'll keep you guys updated

If I were you, I wouldn't worry about the "bad" eMMC. You can read some of my posts to understand, why I'm saying it.

@ PCLiteratesJax
Can you please post the rom you found again or lmk where you found it? Thanks!

Updated Link
sudeepr71 said:
@ PCLiteratesJax
Can you please post the rom you found again or lmk where you found it? Thanks!
Click to expand...
Click to collapse
I've uploaded it to 4shared, here is the link: http://www.4shared.com/folder/xDsyJF52/_online.html
and here is another link: http://www.filestube.com/daPzJ4uvoe...0-27-26-13-04-19-M-release-227522-signed.html
Don't forget to rename it to PD15IMG.zip before you copy it to the SD Card

No Luck
Thank PCLiteratesJax for uploading the files.
However, it did not work. I downloaded the file, changed the name to PD15IMG.zip (I tried both files). When installing, they both bypassed [8] TP, but each reported that the installation was sucessfull and indicated that I should press the power button. After pressing the power button, I am taken to a screen like this:
GLACIER PVT SHIP S-ON
HBOOT-0.89.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC-boot
JUL 15 2011, 16:45:17
FASTBOOT
and then a few other options.
Any ideas?

Tried gingerbreak?
Sent from my HTC Glacier using XDA App

[Q] What have I done :( Just me and my hboot...

So I have a MyTouch 3g w/ the 3.5mm... I'm no noob but obviously I'm farrr from expert because I've effectively softbricked my phone.
Can't get past splash screen (stuck in a boot loop @ the HTC logo). I can bring up hboot and I have fastboot access.. but that's about it. No ADB drivers, no goldcard, no recovery, nada.
When trying to push anything useful (like a recovery image) through fastboot, I get "failed: remote not allowed."
As for how I got into this mess, it started when I mixed up two SD's and ran an update.zip meant for a different phone. Ouchies Instead of immediately coming for help, I thought I could fix it by just unrooting back to cupcake. Ugh.. I seriously don't know what I was thinking.
Is there any hope left for me?
Info.....
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.03
Thanks so much in advance for any advice. Love this forum btw, long-time lurker & first time poster here

Update: I have recovery. I've tried factory reset, wiping cache, loading several different update.zip files.
When trying to load a recovery image through update.zip I get a verification error. Still can't load a rom.
I can get past the HTC logo now, but only the menu bar loads.. the rest of the UI doesn't, and I get a repeating "The process andriod.process.acore has stopped unexpectedly" error, along with a few other errors.... then it will shut down and go to HTC logo again, and bootloop. I have to factory reset to get past the bootloop again.
How can I load a custom recovery through recovery? I'm guessing that's my only solution right now.

Just flash 2.10.531.4 T-Mobile USA DRD35 RUU. It is official ROM (sure, your data will be deleted)

UPDATE 2: Okay, I think I know what my problem is, but I'm stuck once again.
This phone was originally rooted and running cyanogen. i mixed up two sd cards accidentally flashed a motorola rom when i was trying to reset, which was the big dumb mistake that led to me trying to fix it by unrooting, which may have been an even dumber decision lol... i know i know
i think ive got a radio/spl mismatch going on? and i still cant fix anything with no adb or debugging. and fastboot's not flashing anything... i'm about to take downtown and have someone look at it, but i really don't want to spend the $.. but the work im missing over this is $$ too haha. >_<
5[Strogino] said:
Just flash 2.10.531.4 T-Mobile USA DRD35 RUU. It is official ROM (sure, your data will be deleted)
Click to expand...
Click to collapse
Thanks.. I just tried that last night, fastboot won't pick it up, recovery is giving me errors. the exe won't do it either (but i'm not sure if that's related to the lack of adb drivers?) seems to be a permissions problem.. do i need s-off?

shortcat87 said:
i think ive got a radio/spl mismatch going on?
Click to expand...
Click to collapse
If you still have same hboot / radio as in your first post - you DON'T have mismatch
shortcat87 said:
I just tried that last night, fastboot won't pick it up
Click to expand...
Click to collapse
What error did you get?
You can run ruu but navigate into temporary directory and search for rom.nbh, copy to folder with fastboot.exe and close RUU
Then go into fastboot-mode and run
Code:
fastboot flash nbh rom.nbh
shortcat87 said:
do i need s-off?
Click to expand...
Click to collapse
NO

5[Strogino] said:
If you still have same hboot / radio as in your first post - you DON'T have mismatch
Click to expand...
Click to collapse
Thanks, that's good to know
What error did you get?
Click to expand...
Click to collapse
When flashing in hboot (goldcard and otherwise) - No error, just goes through initial loading of SAPPIMG.zip and then goes back to hboot screen like nothing happened
...in recovery - Displays E: can't open cache/recovery/command, allows to apply update.zip but then gives a failed verification error
...in fastboot - Remote: not allowed error, aborts installation
You can run ruu but navigate into temporary directory and search for rom.nbh, copy to folder with fastboot.exe and close RUU
Then go into fastboot-mode and run
Code:
fastboot flash nbh rom.nbh
Click to expand...
Click to collapse
Thanks, will try, though i haven't had success in fastboot yet
Found this post and will try that first & let you know how it goes. If nothing works, I'm looking to sell a MT3G 1.2 for someone to play with, because I can't afford to spend any more time messing with it myself

Phone will not boot. Bootloader works. Factory reset&recover do not.

I've gone through a few threads already looking for more information. A week or so ago I tried to install the OTA update and for whatever reason it failed. Since then the phone has been a little funny and I had to factory reset it twice. Anyway, last night the phone locked up, turned off and went into a boot loop. I can communicate with the phone via fastboot and that's about it. I've tried updating via PD15IMG.zip but it fails and gives me a -pu problem which I'm assuming is partition related.
fastboot flash recovery recovery.img returns Failed(remote: image update error). And erasing it returns Failed (remote: erasing error!). boot recovery doesn't work either.
I've also tried fastboot erasing different sectors, but they all fail giving me a Failed (remote: erasing error!). I cannot fastboot format either.
I'm not sure if any of this information is relevant but:
Glacier PVT ENG s-off
Hboot - 0.85.2007 (PD1510000)
Microp-0429
Radio-26.03.02.26_m
emmc-boot
oct11 2010, 12:44:44
Image CRC
hboot: 0x812FF6d3
boot: 0xb2031a3f
recovery: 0x5cf7d794
system:0x8ed37a0e
Is this phone a lost cause or does anyone have any suggestions on any other things I may be able to try? Thanks!

For what I've read, fail PU means your phone is bricked (emmc fail).
I didn't see any solution for this.

You didn't, because there is none. OP, if you have "Fail-PU", your phone is dead. I believe you're read it enough times in enough threads, but wanted to make sure, so here, it's certain.

Time to sell it on eBay for what ever you can get... probably around 50
Sent from my SGH-T999 using xda premium

md1008 said:
Time to sell it on eBay for what ever you can get... probably around 50
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Wow, had no idea I could sell it. Any idea on what I'd need to replace in order to have a working phone again?

Main board, or just eMMC. But the replacement of eMMC is BGA resoldering - a procedure that can cost you up to $100. Preprogrammed eMMC costs around $20, but I didn't see any for MT4G, only for Desire S (which might be partition-compatible and might not). Search the net for the terms you're not familiar with, and you'll see what needs to be done.

Word. I already looked to see if I can find a main board, though it doesn't look like they're very easy to come by. I guess my best bet would be to find a phone whose screen broke and go that route. My phone as in great condition other than the emmc going bad.