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] MT4G stuck in boot loop, tried everything

Ok, I've looked across a bunch of forums and can't figure this out. I bought a MT4G off ebay. The phone has a problem in that it wont pass the boot screen. I have tried reinstalling the PD15IMG.zip, tried doing a factory hard reset and tried just re-installing CM7. nothing is working. on the PD15IMG.zip, i get the fail-pu on everything, then it gets to the radio, updates to about 95% and stays there. Waited an hour and it didnt move. Any ideas on how to get this thing running?
Phone Info on Boot:
Glacier PVT Ship S-OFF
HBOOT - 0.86.000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
when trying to install cm7 update, i get an
E:Error in /sdcard/update-cm-7.0.3-glacier-signed.zip
(Status 1)
Installation aborted.
thanks!

your phone is bricked. fail-PU means that the radio update failed because the eMMC chip failed.
http://forum.xda-developers.com/showthread.php?t=1081243 check your eMMC chip here.
probably the M4G2DE.
sorry bro..
but sending it back to tmobile is ok.. they still let me replace mine and many others i heard.
good luck with replacement.

Sorry, the person sold you a bricked phone. Getting the Fail-PU error message when attempting to flash PD15IMG.zip means there is no hope.

TeeJay3800 said:
Sorry, the person sold you a bricked phone. Getting the Fail-PU error message when attempting to flash PD15IMG.zip means there is no hope.
Click to expand...
Click to collapse
awesome.... you think its worth a shot at calling tmo or htc for a replacement?

oblivious91 said:
awesome.... you think its worth a shot at calling tmo or htc for a replacement?
Click to expand...
Click to collapse
yea its ok.
i got my replacement just fine.

called tmobile and made the mistake of telling them i bought the phone off ebay. you know if they will record it so that if i call again and change my answer they will know?

[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] Desire Z unbootable and unflashable

Hey xda crew,
I am pretty sure my Desire Z is up sh*t creek now without a hope. As such I am here with my begging on... Help please!!
Last night I went through the app library and manually updated about 7 apps simultaneously. At some point the phone hung, and wouldn't respond. I pulled the battery and booted it back up, and it simply hung again as soon as it connected to wifi. It ran fine without a data connection however.
So this went on and on. I booted, connected to wifi and tried to kill each download asap before it hung again (can't access the market to kill the d/l w/o connection!). Inevitably it would hang each time and then i'd repeat. Finally though it simply got stuck on the HTC boot screen and never went any further.
I've tried everything googleable so far, but unfortunately no love. Here are my specs:
Desire Z, stock standard, no modding, ever.
Vision pvt ship S-ON
HBOOT-0.85.0013
Microp-0425
Radio-26.10.04.03_M
eMMC-boot
Apr 11 2011
I have tried the following to recover the phone:
Leave it loading on HTC screen (30+ mins): Never loads
Factory reset in HBOOT: Hangs
Recovery in HBOOT: Goes to HTC screen, then the green recovery icon, and then blacks out. As soon as the screen goes black it vibrates fiercely 7 times in anger and then dies.
Fastboot w/ RUU_Vision_Gingerbread_S_hTC_Asia_TW_2.42.709.10_Radio_12.56.60.25_26.10.04.03_M_release_201045_signed.exe: RUU sees phone but cannot reboot into bootloader, times out.
Flash manually using PC10IMG.zip, (rom.zip) from the RUU above: Initially didn't work due to CID invalid warning in HBOOT, however have made a gold card manually on PC and gotten past that warning. The ROM reads and verifies fully in HBOOT but upon verification just goes back to HBOOT screen without the option to flash.
With the intent to wipe everything: Flash the HBOOT with an engineering version from here: virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html: As per the RUU Rom, HBOOT reads and verifies successfully but never gives the option to flash.
Erase cache from fastboot command line: Hangs
Beyond that I don't know what else to try. I can't use adb as I cannot boot and don't have any custom recovery roms installed that will allow it. Likewise I can't flash with fastboot due to S-ON.
So because warranty ended a month ago, it goes in the bin tomorrow unless someone has an alternative Even if it is a highly dangerous method, I don't really care, it's good as dead anyway...
Interestingly enough it seems there are a few people with the same issue, all posted within about a week of each other. Everyone was doing the same thing... updating a bunch of apps!
Thanks in advance

When I rooted mine, I simply followed the instructions provided over at CyanogenMod ( http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread) ) doing the firmware downgrade and then the rooting exploit, from there I actually upgraded the radio (thread in my signature) and then got the EliteMod rom.
PS: My Bootloader screen is basically:
VISION PVT ENG S-OFF
HBOOT-0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.13.04.19_M
eMMC-boot
Aug 20 2010,16:51:01
Just not entirely sure how you're going to go bout the fr3vo method without least a stock rom to exploit into.

well jtag... not what you wanted to hear I'm sure
not trying to add insult to injury but next phone make sure you root it right away, chances are this all could have been fixed with the right permissions, short of a hardware failure of course
Sent from my HTC Vision using xda premium

Thanks for taking the time to help out mate.
As it stands, there is no way to use adb so I can't downgrade as per the directions in the link.
I have since tried several other newer and older roms as well, still the same thing, it unpacks them and verifies and then does nothing.
Quite sure now it is dead, so I have just bought a new one off ebay.
Poor old thing, I did enjoy that phone!

demkantor said:
well jtag... not what you wanted to hear I'm sure
not trying to add insult to injury but next phone make sure you root it right away, chances are this all could have been fixed with the right permissions, short of a hardware failure of course
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes, you are absolutely right... I was thinking the same thing. Thew new one will be rooted the minute it arrives. The good news i suppose is that desire z's are so cheap now that they are discontinued.
I honestly love the functionality, speed etc.. no need to upgrade whatsoever.

Your bootloader is stock and you are S-On why not just use your warranty ?

[Q] problem upgrading baseband. ADB reports failed <remote not allowed>

Hello, I have been having loads of problems with reception (staying in 2g mode, staying completely offline all day until I notice and toggle airplane mode, etc.), so I really wanted to try a new radio.
I started in this thread: http://forum.xda-developers.com/showthread.php?t=2115197 which was really encouraging. I got all the way up to setting up ADB and having the phone verified to be attached while in bootloader fastboot. However, every time i try to send the command: "fastboot flash radio radio.img" i get this error: failed <remote not allowed>
I have researched that error and came across multiple forums. There weren't many answers, other than that the bootloader might be locked, or isn't in s-off mode. I can confirm that my bootloader reads:"S-OFF" on the top line. So, I am thinking it is locked then?
I will update the bootloader if i absolutely need to, but I was hoping to get some last words of advice before I do. It seems like that should be the very last resort. Especially after reading that I might have to use the bootloader to flash every kernel if I use a new rom with a different kernel than the one i am currently on. I am also worried about bricking the device, although, I am pretty careful. Oh, and I don't care at all about the warranty. This phone is years past that by now.
Also, I have tried renaming the file to PD15img.zip and dropping it in the root of the SD card to attempt flashing it with HBOOT in the bootloader; but it says: "wrong zipped image". I already double and triple checked that the md5 code matched, even after renaming it.
So, any advice? is it possible that there is another way to do this besides using the bootloader? Like using CWM? I am on CWM
touch v5.8.1.0 BTW
Or, could i maybe upgrade the bootloader, use adb fastboot to change the radio, then switch back to the bootloader i am currently on to avoid complications in the future? Or, since I am still a total n00b, is there any chance I am just doing something wrong with ADB?
In case it helps for reference, this is all of the info about my bootloader that I can read while in that mode:
GLACIER PVT SHIP S-OFF
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Sep 27 2010
Thank you so much for anyone who is willing to help me tackle this. This old phone has been all I can afford lately, and it has been my sole source of internet at home via tethering. Having even a marginally better radio reception would make a world of difference.
Cheers!

S off equals unlocked boot loader.
All good there.
Grab the 4ext app from
4ext.net
And install 4ext recovery, much better. Then try flashing whatever you want. Gotta be careful, Some radios can brick if you mess up.
Sent from my iPhone using Tapatalk

Thanks so much for the help. I really did like cwm touch, but I'll switch if 4ext will allow me to do this. Do you think I could mess anything up if I just tried flashing it in cwm? Also, (super n00b question here) should I rename the file to be .zip? I would assume so I just want to be certain.

kinsaturated said:
Thanks so much for the help. I really did like cwm touch, but I'll switch if 4ext will allow me to do this. Do you think I could mess anything up if I just tried flashing it in cwm? Also, (super n00b question here) should I rename the file to be .zip? I would assume so I just want to be certain.
Click to expand...
Click to collapse
Nahh Just install the app and let it do it's work.
The recovery is also touch.