Related
Ok, I have been thrown for a loop and need some help....
I had a Sprint Hero Rooted on 2.1 the .5 sprint update
Tried to run the new update but it kept getting corrupt.
Did a Nandroid backup
So I reverted back to the .5 RUU
Then it wanted me to update to the old .6 update, so I did
Hoping then I would upgrade to the new .6 but it was not able to find a new update?
Wanted to restore my nandroid update.
When I try to boot into the recovery mode I get a picture of a phone with a red Explanation mark in a triangle.
There is a bunch of people on the net that say they have seen or gotten it, but no one says how to get rid of it? So I can not get in to recovery mode at all.
Tried the home+power boot
Tried the volume down + power then home
always ends in the same screen with no recovery.
Tried multiple times to install the .5 RUU
Reset phone
never can get back there to the recovery?
Phone will boot fine into 2.1 and run fine..
Anyone have any ideas, I have tried everything I can think of.
Thanks
Did u try placing the recovery on ur SD card and flashing it threw terminal on ur phone
Root-Hack-Mod-Always™
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
ASimmons said:
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
Click to expand...
Click to collapse
Thanks, I can't believe I missed that! I had never tried a backup before root, so I did not think about that. Now I know and hopefully this will help someone that googles this issue, as there is never a clear answer until yours.
Thanks again...
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Also If you ever run an ruu on your phone you can kiss your root good bye no matter what version you do. but if you have nand backups you can reroot your phone and then restore one of your backups since there stored on your sdcard.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
Correction: If you see this symbol, it means you don't have a custom recovery image in the phone. You can actually be rooted and still get that symbol if you haven't yet flashed a custom recovery after you rooted. You need to have a custom recovery (that requires root) to avoid getting that symbol when you try to boot into recovery.
Most rooting methods on here automatically include flashing a custom recovery as one of the steps, so this isn't really a big issue....but I just wanted to clarify the specifics of this for anyone else who reads.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
brisuth said:
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
Click to expand...
Click to collapse
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
ASimmons said:
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
brisuth said:
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
Click to expand...
Click to collapse
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
chromiumleaf said:
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
Click to expand...
Click to collapse
just had a friendly member point out what i was starting to suspect the problem lies with the custom recovery being flashed back to stock on every restart, the shell command here
/system/etc/install-recovery.sh this stops any custom recovery on reboot. any advice on what tools to edit or remove
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
I always had root that was where the confusion was, what i did not know was the script was running with every boot of the handset and removing the recovery that was there as it was identified as unofficial and exclamation mark could be down to me using many methods to flash i may have renamed original recovery so when it goes to exclamation it is because cant find original recovery whether handset is rooted or not.
danaff37 said:
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
would that have worked? i thought about it many many times but as i had never flashed before was unsure how many times phone would reset and if it did before it was installed could i lose my recovery.
on the plus side the 2 months i have spent trying to solve this i have a much broader view of the workings of my handset and without the many members like yourself who take the time to reply and try to help others i would have given up a long time ago.
Brian
I'm sure if you deleted that script a custom recovery would have stuck
Sent from my HERO200 using XDA App
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.
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.
So i rooted my phone, had a custom rom on it, erased it, i put in a new rom and my phone froze, battery pulled it and went into recovery and now it says it cant mount
This all happening after i erased my old rom, I cant load a new one on it cause it always aborts it. What can i do to get it back to stock to re-root it, or get CW recovery to work right again :-/
FML......
tongtaihuo said:
So i rooted my phone, had a custom rom on it, i put in a new rom and my phone froze, battery pulled it and went into recovery and now it says it cant mount
This all happening after i erased my old rom, I cant load a new one on it cause it always aborts it. What can i do to get it back to stock to re-root it, or get CW recovery to work right again :-/
FML......
Click to expand...
Click to collapse
Go to the bootloader. Then go to system info. What does it say on the eMMC line? Does it say Samsung or Sandisk?
Sent from my HTC Glacier using xda premium
hboot-0.86.0000
microp-0429
Radio-26.11.04.03_M
Radio-26.11.04.03_m
emmc-boot
tongtaihuo said:
So i rooted my phone, had a custom rom on it, erased it, i put in a new rom and my phone froze, battery pulled it and went into recovery and now it says it cant mount
This all happening after i erased my old rom, I cant load a new one on it cause it always aborts it. What can i do to get it back to stock to re-root it, or get CW recovery to work right again :-/
FML......
Click to expand...
Click to collapse
You erased the rom? How in the world you that? There's no way to erase the rom.
Sent from my HTC Glacier using xda premium
i deleted it through CW and tried to install a new rom, but it aborted before it could finish
flash the PD151IMG.zip file through bootloader, THIS WILL ERASE ALL OF YOUR DATA, AND RETURN YOU TO STOCK MT4G 2.2.1. this is so you can root again.
download link here: http://www.megaupload.com/?d=V4NAODYZ
once you have it downloaded:
1) move to ROOT of sdcard (not in any folders)
2) make sure fastboot is OFF
3) reboot phone into bootloader by holding power and volume down buttons.
4) the phone should find the file, and ask if you want to "update"
5) select yes, and let it do it's thing. BE PATIENT
6) hit the thanks button (IMPORTANT )
7) after returning to stock, get the phone rooted again and flash a rom on there.
WARNING: IF IT SHOWS FAIL-PU, THE PHONE IS BRICKED.
Fail-PU means that the partition update has failed, due to the fact that the phone cannot write to the eMMC chip anymore, because the chip has died.
it shows fail on everything, but when it gets to TP it says bypass and its still updating radio_V2
tongtaihuo said:
it shows fail on everything, but when it gets to TP it says bypass and its still updating radio_V2
Click to expand...
Click to collapse
ok, tell me if radio fails or not...
it vibrated like 6-7 times and its still updating
tongtaihuo said:
it vibrated like 6-7 times and its still updating
Click to expand...
Click to collapse
ok, pull the battery, and try again. if it gives Fail-PU again, then the phone is bricked.
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.