Database Users

[Q] recovery isnt working

i installed a rom (royal ginger), it loads but after it loads it reboots the phone and does the same thing all over again, i rent to recovery to do a full wipe and re install and it comes up with "E: Cant open /cache/recovery/log" and some more errors, how do i fix this problem? i hope i havent bricked my phone

lanceydavid said:
i installed a rom (royal ginger), it loads but after it loads it reboots the phone and does the same thing all over again, i rent to recovery to do a full wipe and re install and it comes up with "E: Cant open /cache/recovery/log" and some more errors, how do i fix this problem? i hope i havent bricked my phone
Click to expand...
Click to collapse
What exactly did u do to get that error??? Did u wipe data,cache,delvik & format system,i always format sd card also in case the sd card has a currupt file... did it automatically give the errors once u flashed?? Did u check the mdsum on the file to make sure u had a full zip file??? What recovery did u use 3.0.2.4 or 3.0.0.6??Sorry need to ask questions in order to help lol.... Ive heard of people fixin their phones with the part7backup-xxxxx.bin file & the pd15 file....just stick those to the root of the sd card go into recovery & let the phone to its thimg..

@cmdmilitia13 Thanks so much for even trying to help! i have clockworkmod recovery 3.0.0.5 .... i flashed, worked perfectly, installed the rom the last night, woke up in the morning, phone wouldnt turn on, took out battery, and when it finally loaded, it kepts rebooting back to the loading screen.... i went back to recovery, tried to wipe data and cache, wont work, did delvik, and didnt say if it was successful or not but i formatted sd card, as soon as i try to format system it says:
E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log and etc.
as soon as i try a wipe it says the similar

lanceydavid said:
@cmdmilitia13 Thanks so much for even trying to help! i have clockworkmod recovery 3.0.0.5 .... i flashed, worked perfectly, installed the rom the last night, woke up in the morning, phone wouldnt turn on, took out battery, and when it finally loaded, it kepts rebooting back to the loading screen.... i went back to recovery, tried to wipe data and cache, wont work, did delvik, and didnt say if it was successful or not but i formatted sd card, as soon as i try to format system it says:
E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log and etc.
as soon as i try a wipe it says the similar
Click to expand...
Click to collapse
Royalginger requires recovery 3.0.0.6 or 3.0.2.4....3.0.0.5 was mainly for cm7 but clockwork updated to flash froyo & gingerbread now... I believe u can dwnload a cm7 rom to the sd card frm the pc then try to flash that if that dnt wrk then if u rooted by using gfree method & have the 0.85.2007 bootloader it should of created a part7xxxx.bin file & that will help unrootin the phne & startin frm scratch again...

Theres a couple threads on here that could help u out,ur not fully bricked tho... I had this issue about 3 months ago when there barely was a fix now at least u have a chance..

i have the 0.86.0000 bootloader, will that be a problem? if not if i google how to unroot i should be able to find it easily?

i also downloaded cm7 tried to install, and the same rom and issues still pop up, so i guess my only choice is to unroot, but how do i unroot without using terminal?

lanceydavid said:
i also downloaded cm7 tried to install, and the same rom and issues still pop up, so i guess my only choice is to unroot, but how do i unroot without using terminal?
Click to expand...
Click to collapse
I believe u need to have that 0.85.2007 bootloader but look around the Q&A threads & look for the subjects that says bricked or I think im bricked,those would help u out,im headin to wrk so cnt helo u now sorry...

lanceydavid said:
i also downloaded cm7 tried to install, and the same rom and issues still pop up, so i guess my only choice is to unroot, but how do i unroot without using terminal?
Click to expand...
Click to collapse
If you rooted with gfree, go back to the thread that guided you. It has instructions on how to unroot. Basically you want to place part7backupxxxxxx.zip on the root of your SD, download PD15IMG.zip, place on root of SD, then load bootloader and let it do it's thing, responding when prompted. If you can't mount the card you're going to have to find a way to mount it outside of the phone, either with an adapter or a card reader.

darinmc said:
If you rooted with gfree, go back to the thread that guided you. It has instructions on how to unroot. Basically you want to place part7backupxxxxxx.zip on the root of your SD, download PD15IMG.zip, place on root of SD, then load bootloader and let it do it's thing, responding when prompted. If you can't mount the card you're going to have to find a way to mount it outside of the phone, either with an adapter or a card reader.
Click to expand...
Click to collapse
Doesnt he need the eng 0.85.2007??

cmdmilitia13 said:
Doesnt he need the eng 0.85.2007??
Click to expand...
Click to collapse
Nope. I'm on 86 and have rooted and unrooted this phone about 30 times helping people and trying stuff.
Sent from my HTC Glacier using XDA App

cmdmilitia13 said:
Doesnt he need the eng 0.85.2007??
Click to expand...
Click to collapse
You need the engineering bootloader to use adb, both will run the PD15IMG.zip.

darinmc said:
You need the engineering bootloader to use adb, both will run the PD15IMG.zip.
Click to expand...
Click to collapse
Thanks good to knw,i just thought u needed it since everyone talks about it...

cmdmilitia13 said:
Thanks good to knw,i just thought u needed it since everyone talks about it...
Click to expand...
Click to collapse
The reason we talk about is pretty simple. .85 allows you to use ADB commands and flash stuff via the HBoot engine. Where .86 does not allow you to. So if you get in "semi-brick" mode you can 9/10 times get your self up and rocking.
had it happen earlier today as a matter of fact.
http://forum.xda-developers.com/showthread.php?t=1040463
and this one rings a bell....
http://forum.xda-developers.com/showthread.php?t=1035413
They were both what most people would call bricked, but since they had the .85 engineering screen we could get them up and running.

CWM Cache error [STRIKES AGAIN!]

[Solved!!]
When I open CWM I always get this error (see attached image) I have tried flashing an older version of CWM and I still get it... I have searched a TON to find the answer to this and it seems really common on Nexus S owners but I haven't found a solution... But because of this I can no longer flash anything.
Any ideas? I have fastboot erased EVERYTHING even tried fastboot flashing a Nandroid that I KNOW is a good backup... it seems to work but when I go to boot the device I get stuck that the bootscreen :/
[Solved!!!]
Anyone ever runs into this issue, flash CWM 2.X.X.X go to mounts, mount cache then format it. I couldn't mount cache in 3.X.X.X but it worked in 2.X.X.X. Not sure why this worked but whatever! lol
UPDATE!!!
SO the CWM Ghost is back, once again. Still nothing out of the ordanary done on my part, just started getting random FC's and boom there it's ugly mug is when I go to CWM to fix permissions...
BUT, here is the problem, I'm trying to fix it how I did last time and when I go to flash the new recovery in Fastboot via ADB I get this error:
sending 'recovery' <4000 KB>... OKAY [15.390s]
writing 'recovery' ...FAILED <remote: image update error>
I have tried a few different CWM recovery downloads... any ideas?

dcwiker05 said:
[Solved!!]
When I open CWM I always get this error (see attached image) I have tried flashing an older version of CWM and I still get it... I have searched a TON to find the answer to this and it seems really common on Nexus S owners but I haven't found a solution... But because of this I can no longer flash anything.
Any ideas? I have fastboot erased EVERYTHING even tried fastboot flashing a Nandroid that I KNOW is a good backup... it seems to work but when I go to boot the device I get stuck that the bootscreen :/
[Solved!!!]
Anyone ever runs into this issue, flash CWM 2.X.X.X go to mounts, mount cache then format it. I couldn't mount cache in 3.X.X.X but it worked in 2.X.X.X. Not sure why this worked but whatever! lol
Click to expand...
Click to collapse
You know, even though you solved it, I still think you should send a note to koush... the creator of CWM....

faux123 said:
You know, even though you solved it, I still think you should send a note to koush... the creator of CWM....
Click to expand...
Click to collapse
I sent him a private message detailing what led up to the error (and may or may not have caused it) as well as a link to this thread.

dcwiker05 said:
I sent him a private message detailing what led up to the error (and may or may not have caused it) as well as a link to this thread.
Click to expand...
Click to collapse
glad you fixed it, as many ppl have had this issue and have yet to recover from it!!! also, since you had fastboot set up i am assuming you have the 85.2007 engineering bootloader, correct?
i saw this preview post and all i could say is the cwm ghost got another one but it seems you got lucky!!!

irrelephant said:
glad you fixed it, as many ppl have had this issue and have yet to recover from it!!! also, since you had fastboot set up i am assuming you have the 85.2007 engineering bootloader, correct?
i saw this preview post and all i could say is the cwm ghost got another one but it seems you got lucky!!!
Click to expand...
Click to collapse
I would say "lucky" as well. but i'm wondering if the 2.x recovery image might be the fix for this problem. If one could "brick" their phone with the same symptoms as this phone. Then flash the 2.x recovery and see if it fixes the problems.

Yeah I have 85. Bootloader, because I read to flash CM7 it was best to have that installed. As for me fitting lucky yeah I guess I did, I didn't realize this was one of those "end all" errors lol. Specially since I really have no clue what possessed me to flash the old clock work. Basically I felt there had been known issues with 3.X. so I thought "what would it hurt?" Turns out it helped!!! I'm using the phone now and everything is 100%
Sent from the depths of hell cuz XDA's app is THAT good!!

dcwiker05 said:
Yeah I have 85. Bootloader, because I read to flash CM7 it was best to have that installed. As for me fitting lucky yeah I guess I did, I didn't realize this was one of those "end all" errors lol. Specially since I really have no clue what possessed me to flash the old clock work. Basically I felt there had been known issues with 3.X. so I thought "what would it hurt?" Turns out it helped!!! I'm using the phone now and everything is 100%
Sent from the depths of hell cuz XDA's app is THAT good!!
Click to expand...
Click to collapse
Nice i'm going to remember this thread.

TOPSIDE for some new developments. See OP for update...

I believe TrueBlue_Drew has a flashable zip for CWM 2.5.1.2 Have you tried that?

hello i need that recovery 2.___ for fix my problem same that! where i cant find_

vabeach454 said:
I believe TrueBlue_Drew has a flashable zip for CWM 2.5.1.2 Have you tried that?
Click to expand...
Click to collapse
I think I found what you are talking about HERE but from what I gather that needs your phone able to boot cuz it changes the recovery via Rom Manager. Sadly my phone doesn't boot, all I have is hboot and the 3.1.2.4 recovery available to use, both of which are basically broken. Thanks for the help and the idea though I really hope we come up with a way to fix this somehow. Any dev who needs a phone to experiment on, hit me up.

dcwiker05 said:
I think I found what you are talking about HERE but from what I gather that needs your phone able to boot cuz it changes the recovery via Rom Manager. Sadly my phone doesn't boot, all I have is hboot and the 3.1.2.4 recovery available to use, both of which are basically broken. Thanks for the help and the idea though I really hope we come up with a way to fix this somehow. Any dev who needs a phone to experiment on, hit me up.
Click to expand...
Click to collapse
Download zip from thread. Extract it to desktop or location of your choice. Go into the folders and find the recovery img that has 2.5.1.4 in the name. That is actually the 2.5.1.2 recovery. You can then re-name it to what ever you need to and push it to your device.
Hope this helps.

victorx said:
hello i need that recovery 2.___ for fix my problem same that! where i cant find_
Click to expand...
Click to collapse
Download this navigate to this (C:\Users\YOURUSERNAME\Recovery_2.5.1.2_to_RomManager.zip\sdcard\clockworkmod\download\mirrorbrain.cyanogenmod.com\cm\recoveries\) extract the recovery 2.5.1.2. Rename it recovery.img and try to flash it via adb in hboot (fastboot flash recovery recovery I BELIEVE that is the command I can't honestly remember but a quick google search will yield you a adb guide no problem

TrueBlue_Drew said:
Download zip from thread. Extract it to desktop or location of your choice. Go into the folders and find the recovery img that has 2.5.1.4 in the name. That is actually the 2.5.1.2 recovery. You can then re-name it to what ever you need to and push it to your device.
Hope this helps.
Click to expand...
Click to collapse
I can't push to my device which is the COMMAND problem. Now when I try to push via ADB I get an error saying write---FAILED. I have tried a few other tricks I have been told as well about like repartitionion the cache via ADB and that doesn't work either. So I hope this works for the OP

MT4G stuck at boot

Okay... my MT4G won't boot up.
I rooted my phone. I have s=off. That's not where the problem lies.
The problem is me being a dumbass. I tried getting the Netflix.apk app to work on my MT4G, and I read a guide where you had to mess around with something from the system file to trick the app into thinking your phone was a Nexus S. So, I tried that, and powered down my phone. Now it won't boot up past the "MyTouch 4G" logo.
I tried booting into safe mode, to see if I could go back in and change it, but it won't let me. Any ideas on how to fix this? Tried a factory restore, didn't work. Also not running a custom rom either - was still using the stock rom.

Reflash a stock-type rom?

Driveshaft said:
Okay... my MT4G won't boot up.
I rooted my phone. I have s=off. That's not where the problem lies.
The problem is me being a dumbass. I tried getting the Netflix.apk app to work on my MT4G, and I read a guide where you had to mess around with something from the system file to trick the app into thinking your phone was a Nexus S. So, I tried that, and powered down my phone. Now it won't boot up past the "MyTouch 4G" logo.
I tried booting into safe mode, to see if I could go back in and change it, but it won't let me. Any ideas on how to fix this? Tried a factory restore, didn't work. Also not running a custom rom either - was still using the stock rom.
Click to expand...
Click to collapse
Did you happen to make a backup to restore to? Other than that i think the stock image PD15IMG may be what ya need.

eqjunkie829 said:
Did you happen to make a backup to restore to? Other than that i think the stock image PD15IMG may be what ya need.
Click to expand...
Click to collapse
This will kill root and S=OFF. I wouldnt advise until we know that he OFFICIALLY borked his rom lol
@OP, What exactly did you edit??
Also, if you dont have a backup, i would try flashing this, its the stock rom + root and its debloated.
Also, factory restore would help because it only wipes /data and /cache
whereas you said you edited something in /system
Hope this helps!!

Yeah that sounds like a better idea, just flash a stock like rom after wiping caches data and system. And once you get it fixed make a backup or two, always a good idea to make one before changing anything important in the phones file system.

eqjunkie829 said:
Yeah that sounds like a better idea, just flash a stock like rom after wiping caches data and system. And once you get it fixed make a backup or two, always a good idea to make one before changing anything important in the phones file system.
Click to expand...
Click to collapse
Yep, and with nandroid, if something goes wrong with w/e system edit you are trying, you can restore /system only. opposed to wiping/reflashing or restoring the whole backup.
Basically, skv012a had the right idea here lol

And by stock-type I meant pre-rooted stock, maybe even debloated like Orange Glacier.

JDV28 said:
This will kill root and S=OFF. I wouldnt advise until we know that he OFFICIALLY borked his rom lol
@OP, What exactly did you edit??
Also, if you dont have a backup, i would try flashing this, its the stock rom + root and its debloated.
Also, factory restore would help because it only wipes /data and /cache
whereas you said you edited something in /system
Hope this helps!!
Click to expand...
Click to collapse
Tried to edit the build.prop file in /system - followed this guide and edited what it told me to (ro.product.model=Nexus S, ro.product.manufacturer=Samsung).
Also, tried to follow that guide in the link you posted, but when I go into recovery, I get a red triangle. I have to press volume-up and the power button to get anything to come up. Then when I do, all I get is this in blue text:
Android system recovery <3e>
Use volume key to highlight;
click power key to select
Reboot system now
Apply sdcard:update.zip
Wide data/factory reset
Wipe cache partition
Click to expand...
Click to collapse
And below that in yellow text is:
E: Can't open /cache/recovery/command
Click to expand...
Click to collapse

Driveshaft said:
Tried to edit the build.prop file in /system - followed this guide and edited what it told me to (ro.product.model=Nexus S, ro.product.manufacturer=Samsung).
Also, tried to follow that guide in the link you posted, but when I go into recovery, I get a red triangle. I have to press volume-up and the power button to get anything to come up. Then when I do, all I get is this in blue text:
And below that in yellow text is:
Click to expand...
Click to collapse
uh oh. ok, download pd15img, put it on the root of your sd card, and boot into hboot (volume down and power). it will automatically load the file, hit volume up to confirm when it asks, this will put you back to stock.

JDV28 said:
uh oh. ok, download pd15img, put it on the root of your sd card, and boot into hboot (volume down and power). it will automatically load the file, hit volume up to confirm when it asks, this will put you back to stock.
Click to expand...
Click to collapse
Uh-oh indeed. I did that, and when it went to load it, it said "no image or wrong image". Gives me the same error message it gives this guy (already Googled it to try and find a solution, no luck). I have a 16GB SanDisk memory card, FAT32, only about 1GB left. Would formatting it do the trick? I want to try and avoid that at ALL costs, but if I have to...
Sd Checking ...
Loading ... [PD15DIAG.zip]
No Image!
Loading ... [PD15DIAG.nbh]
No Image or Wrong Image!
Loading ... [PD15IMG.zip]
No Image!
Loading ... [PD15IMG.nbh]
No Image! or Wrong Image!
Click to expand...
Click to collapse
EDIT: Might also be worth a mention - I put my MicroSD card into an adapter, put it into my laptop, and looked around on the SD card. Found the "boot.prop" file that started the problem, opened it in Word Pad, and edited it so the "Nexus S" and "Samsung" were back to "HTC Glacier" and "HTC". Saved it, tried booting, but to no avail.
Which brings me to my next question, I have a boot.prop file in /system on my SD card, and a boot.prop file on the root of my SD card. Should there be two of these files? I looked at one in Word Pad, and it had a lot of mentions of CyangogenMod on it, even though I bought the phone brand new a month ago and NEVER flashed CM on it. Can copy/paste the contents of both boot.prop files and put them on here if it would be any help.

Driveshaft said:
Uh-oh indeed. I did that, and when it went to load it, it said "no image or wrong image". Gives me the same error message it gives this guy (already Googled it to try and find a solution, no luck). I have a 16GB SanDisk memory card, FAT32, only about 1GB left. Would formatting it do the trick? I want to try and avoid that at ALL costs, but if I have to...
EDIT: Might also be worth a mention - I put my MicroSD card into an adapter, put it into my laptop, and looked around on the SD card. Found the "boot.prop" file that started the problem, opened it in Word Pad, and edited it so the "Nexus S" and "Samsung" were back to "HTC Glacier" and "HTC". Saved it, tried booting, but to no avail.
Which brings me to my next question, I have a boot.prop file in /system on my SD card, and a boot.prop file on the root of my SD card. Should there be two of these files? I looked at one in Word Pad, and it had a lot of mentions of CyangogenMod on it, even though I bought the phone brand new a month ago and NEVER flashed CM on it. Can copy/paste the contents of both boot.prop files and put them on here if it would be any help.
Click to expand...
Click to collapse
now the issue unrelated to that file. you are sure you have pd15img.zip on your sd card? it CAN NOT be inside any folders. formatting won't be necessary

Lol, wow. >_> I'm a dumbass. I was unzipping the file, and putting them into the root of my SD card. Not putting just the zip file itself in my SD card.
Deleted all the files off my SD card I put on, re-downloaded the ZIP file, put JUST that on the root of my SD card. It flashed it, saw the bar on the upper-right hand corner do it's work, and pressed the power button when it was done to reboot.
Aaand, still nothing. Phone is still stuck at MyTouch 4G logo, and looping over and over.
'Bout to download this, and try to flash that. Would it matter any? Or have the same effect?

Yea try that then report back GL

Nope, no dice. >_> Couldn't even get hboot to attempt to flash it.

pd15iag.img
Sorry about the double post, just wanted to bump this up and update what I've tried.
1. Someone told me to push a recovery image via ADB
- Tried doing this. ADB recognizes my device, but says it's offline. I'm guessing it's because my phone won't actually boot up. I have to go into recovery mode (still getting red triangle) to get ADB to recognize my device in the first place - once I do that, it just says offline next to it. So I can't push anything via ADB.
2. Tried flashing a stock-like rom
- Last night, I tried flashing PD15IMG and it did nothing. Today, I tried flashing Royal Glacier, but it didn't recognize it. I had it on the root of my SD card (nothing else but that on there now) and it still tries to flash "PD15IAG.img" even though it's not on my SD card and I have no idea what it is. :\
EDIT:
Soooo, yeah. >_> I decided to try a new SD card. Brand new, been sitting around the house for awhile. Bought it at Radioshack when they were on sale. Loaded PD15IMG onto it, put it in, flashed it, and now my phone works. I guess it was a faulty SD card? I dunno. Glad it's working now - thanks everyone for the help.

[Q] Unable to boot/restore/write recovery: E: Can't mount /cache/recovery/command

Hey guys,
I have a MT4G here, i was running CM7 on it. Latest nightly, all was running smooth until somehow i started getting a bunch of FCs and i had to reboot to supposedly fix that. However, when i rebooted the phone was stuck on a bootloop, so i rebooted to recovery instead.
I tried restoring a nand from stock ROM, and i tried restoring a CM7 backup I had made a while ago, but recovery reads the following: E: Can't mount /cache/recovery/command.
I then said, ok, maybe the recovery is borked. So i tried to redownload the recovery img from the official website, and i "fastboot flash recovery recovery.img" - please note i had renamed the recovery file to recovery.img for the ease of typing things. Flashing that was a no-go, i get the following error: "remote: image update error".
So i kept on reading forums, and i came across the PD15IMG.zip, i placed on the root of my SDcard, rebooted to HBOOT, it checks for the update but fails to initiate installation, error says: "Fail - PU"
Do you guys have any ideas as to what can i try? I have the Eng Bootloader.

Hate to be the bearer of bad news, but you're bricked. The emmc chip died.
Sent from my HTC Glacier using XDA App

kimbernator said:
Hate to be the bearer of bad news, but you're bricked. The emmc chip died.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Appreciate the support, but i've seen hard bricks before. I am sure -and hopeful- that i'll be able to get out of this one.
If it serves any purpose, I tried erasing the recovery, rather than overwriting it, and i get the same Remote error. Unable to delete.
EDIT: Ok, so i spent the night reading, and it is not a user-driven failure, but rather a Manufacturer problem. Some eMMCs (labeled: "M4G2DE") may die all of the sudden, and not even necessarily during a ROM change, and/or during a restore. It can also fail inadvertently during day to day usage.
I am moving all my interested to the linked thread, in case anyone is interested.
http://forum.xda-developers.com/showthread.php?t=1079025

edit: whatever

JDV28 said:
This is stupid. You obviously have no idea what you are talking about. The only actual confirmation of a dead eMMC is the fail-pu error.
get the original pd15img.zip, put it on the root out your sd card,.then boot into hboot and follow the on screen instructions to flash it. THEN if you get the fail-pu error,.you know your emmc chip is dead.
Click to expand...
Click to collapse
I did try the PD15IMG.zip and i received the "Fail -PU" while installing.
I have the bad eMMC (tested according to the thread i linked to on my previous post)
I'll try to squeeze a replacement from T-Mo but not sure how lucky I'll be :sadpanda:
Sent from my LG-P999 using XDA Premium App

JDV28 said:
This is stupid. You obviously have no idea what you are talking about. The only actual confirmation of a dead eMMC is the fail-pu error.
get the original pd15img.zip, put it on the root out your sd card,.then boot into hboot and follow the on screen instructions to flash it. THEN if you get the fail-pu error,.you know your emmc chip is dead.
Click to expand...
Click to collapse
Dude, he said in the OP that he got the Fail-PU error.

TeeJay3800 said:
Dude, he said in the OP that he got the Fail-PU error.
Click to expand...
Click to collapse
weird, I lose interest in these long posts. I've answered at least 50 threads about these emmcs

fix this problem in my touch 4g
is the way to fixit i fixit my self is not brick if you can get to bootloader,make sure ti format your sdcard in fat 32 ,and put pd15img in sd card and it will find and update,i hade the sAME PROBLEM AND FIXIT FINALY

duka25 said:
is the way to fixit i fixit my self is not brick if you can get to bootloader,make sure ti format your sdcard in fat 32 ,and put pd15img in sd card and it will find and update,i hade the sAME PROBLEM AND FIXIT FINALY
Click to expand...
Click to collapse
Read the OP man, i tried, and i got "Fail -Pu". The sd card being formatted would not be necessary, i know the card works well.
Thanks for trying though
Sent from my LG-P999 using XDA Premium App

[Q] Challengings for Brain users like me!

Hi guys,
First of all, i apologize if I post in a wrong forum, kind of new in XDA. Wanted to thank you all, because, even though, I didn't register, your forum helps me A LOT with android phones... I'm facing a situation with an HTC, and as I surfed the web, and no one seems to have the same problem, I'm adressing it in this forum.
I bought an refurbished mytouch 4g glacier on amazon. When it came, in addition to be locked (not a big problem), I couldn't enter the settings (the linked program is no longer installed on your phone) and worst, there is no dialpad. I assumed that the owner tried to flash it with a corrupt version...
As it is for me a brain challenge, i decided to try to fix it...
I made a factory reset with the buttons (pwr+vol down), same thing! I tried recovery, I think with the S-ON, it didn't work (red triangle). I tried to use wifi to download things or a file manager, but you'll need to access the settings options, and I don't have access. I download SDK manager, but the phone needs to be usb debugging to be found by pc, and I can't access the settings options. I download an usb debugging apk, put it in the sd card, but as there is no file explorer, I could access it...
This is why I asked your help. This is a Glacier pvt ship s-on, with green fonts, (cyanogen 7?: there were a difference with green fonts and orange fonts...)
Thanks in advance.
STO02

Try flashing PD15IMG in bootloader.
Sent from my HTC Glacier using xda premium

whytry23000 said:
Try flashing PD15IMG in bootloader.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Ditto. If you don't know whether the phone is rooted, I would just flash the PD15IMG of the stock 2.3.4 ROM by loading the file onto the root of the SD card and booting into the bootloader (volume down + power). Then if after you are sure it works you want to root it, you can always go on from there.
In terms of figuring out which ROM you have, since you can't get to the 'about phone', if your boot animation just has the Tmobile MyTouch 4g logo on a white background, followed by a circular green MyTouch logo, then you are probably on the stock ROM. If it was CM7 or anything else, it would usually have a different custom boot animation.
Good luck!

You can also tell which stock version you are running: 2.2.1 has no quick settings tab in the notification drawer while 2.3.4 does.
Sent from my HTC Glacier using xda premium

Re: Challengings
whytry23000 said:
Try flashing PD15IMG in bootloader.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Thank you for your quick answer... I have already done this 5 days ago. I downloaded the PD15img, put it in the sd card (actually, i didn't know which extension to put in the sd card, so i unzip the file and i let the zip one: i put both in the sd assuming the phone will use the best extension it needs!). I use pwr+ vol down, nothing happen.
Any ideas? Maybe if i found an update version of the pd15img?
Thanks for your help

Guys, I'm blessed...Not because I found the solution yet, but because I found you thinking with me!
It seems I have the 2.3.4, because, as you said, I have the quick drawer icon. I have already try the bootloader, but i will try again from the beginning. I will download again the pd15img (if it was a problem while downloading) and revert to you in 2 hours.
Thank you again!

It should be a file named PD15IMG.zip. Any file by that name placed in the root of the sd card will be flashed through the hboot bootloader. Don't unzip it. If it is named exactly that, when you boot into the bootloader via vol down + power, it should scan for it, and if it detects the file, it will ask if you want to update.
Be sure you are using the right PD15IMG.zip file (2.3.4 Stock). There are a lot of files by that name, since it is used to flash all kinds of things (radios, etc.). Looks like it might be available here: http://forum.xda-developers.com/showthread.php?t=1476745&highlight=pd15img&page=10

Re: Challengings
unqualified said:
Ditto. If you don't know whether the phone is rooted, I would just flash the PD15IMG of the stock 2.3.4 ROM by loading the file onto the root of the SD card and booting into the bootloader (volume down + power). Then if after you are sure it works you want to root it, you can always go on from there.
In terms of figuring out which ROM you have, since you can't get to the 'about phone', if your boot animation just has the Tmobile MyTouch 4g logo on a white background, followed by a circular green MyTouch logo, then you are probably on the stock ROM. If it was CM7 or anything else, it would usually have a different custom boot animation.
Good luck!
Click to expand...
Click to collapse
I do have the Tmobile MyTouch 4g logo on a white background, followed by a circular green MyTouch logo. I'm on the stock rom then? Is that make any difference or I can still process with downloading pd15img? Anyway, that's worth the try!
I'll keep you posted

It does sound like you are definitely on stock 2.3.4 since you have the stock boot animation, and the notification bar quick drawer that was introduced with gingerbread 2.3.4.
It only makes a difference if you aren't rooted. If you weren't rooted and flashed a different ROM it probably wouldn't work, and you could get stuck in a boot loop (couldn't get past the hboot menu). But, the fix would be to flash the stock PD15IMG anyway, so you should be fine. Either way, nothing is going to happen unless you flash something, because it sounds like system files have been deleted.
I'm still kind of a noob, but I feel pretty confident with that. I've messed up before and recovered from hboot with a PD15IMG file. Your hboot and recovery sound like they are stock. Just be sure once you have it working that you remove or rename the PD15IMG file from your sdcard, otherwise it will keep trying to flash it when you boot into the bootloader.

Re:Challengings
unqualified said:
It should be a file named PD15IMG.zip. Any file by that name placed in the root of the sd card will be flashed through the hboot bootloader. Don't unzip it. If it is named exactly that, when you boot into the bootloader via vol down + power, it should scan for it, and if it detects the file, it will ask if you want to update.
Be sure you are using the right PD15IMG.zip file (2.3.4 Stock). There are a lot of files by that name, since it is used to flash all kinds of things (radios, etc.). Looks like it might be available here: http://forum.xda-developers.com/showthread.php?t=1476745&highlight=pd15img&page=10
Click to expand...
Click to collapse
I followed your link and downloaded the pd15img from there. i placed it in the sd...It detects it like earlier and still give me the message: sd checking....loading pd15img.zip....no image or wrong file image.
Any more ideas?

Some ideas here: http://forum.xda-developers.com/showthread.php?t=1035044
one person suggested making sure the sd card is FAT32 formatted, seemed to help his issue.
Also, you might want to be sure that even if it gives you that error message, there isn't a loading bar on the right hand side of the screen making progress. If I recall the last time I did it, it wasn't obvious it had worked, and loaded for a few minutes before popping up with 'do you want to update?'

Did you try both the 2.3.4 and the '2.3.4 new' file found on the aforementioned page?
Sent from my HTC Glacier using xda premium

Re:Challengings
unqualified said:
Some ideas here: http://forum.xda-developers.com/showthread.php?t=1035044
one person suggested making sure the sd card is FAT32 formatted, seemed to help his issue.
Also, you might want to be sure that even if it gives you that error message, there isn't a loading bar on the right hand side of the screen making progress. If I recall the last time I did it, it wasn't obvious it had worked, and loaded for a few minutes before popping up with 'do you want to update?'
Click to expand...
Click to collapse
Good and bad news!!!
The good news: It really makes a difference indeed to format the sd in Fat32. Although i formated it many times, as I used to see FAT, I didn't know there were another option for FAT32. Well, after format it in FAT32, i put the file in the sd card: pd15img loads successfully...
Bad news: I hurrily check if I can access the option: "the linked program is no longer installed on your phone".
At least, we know formating sd card in FAT32 does make a difference!.
Maybe I should try another new rom like 2.3.6?
Any ideas is welcomed!
Thank you

Wow, head scratcher. If you were rooted with a custom recovery I'd say you probably need to format the system partition and wipe data and cache before flashing, but obviously you can't do that. Might be worth trying a few times to force it through?
I think this is out of my league at this point. Hopefully someone smarter than me will pop in!
Only other thought is maybe something can be done through fastboot? But I wouldn't know what.

Re:Challengings
whytry23000 said:
Did you try both the 2.3.4 and the '2.3.4 new' file found on the aforementioned page?
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Yes I did! I even try the 2.2.1...All of them load successfully, but still without succes. It's like they are installed somewhere in the phone, but the original that has the problem never moved.
Is that because S is on?

Re:challengings
unqualified said:
Wow, head scratcher. If you were rooted with a custom recovery I'd say you probably need to format the system partition and wipe data and cache before flashing, but obviously you can't do that. Might be worth trying a few times to force it through?
I think this is out of my league at this point. Hopefully someone smarter than me will pop in!
Only other thought is maybe something can be done through fastboot? But I wouldn't know what.
Click to expand...
Click to collapse
Thank you a lot for your help. It's been useful cause I learned a lot, much more than alone. If I get through this, I will post.
My next thinking is to download USB debug apk into the phone, so maybe, it will enable the option and I could use adb. But in order to do that, i should pay to unlock it...(wondering if it worth it). As soon as i put a sim in it, i know my carrier would install the apn settings for me automatically, so i would be online and be able to download. I try the wifi options, but i couldn't connect.
Could you help me with the unlock?
Thanks in advance

I think that recovery file is for 2.2.1......
Get S-Off bro. Doesn't the stock image have a file explorer? I don't remember.