Could someone please provide the pd15diag.zip and pd15Ingram.nbh files for me. In dire need. Done forum searches as well as googled em with no result. If someone could locate these files and provide a download I would be ever so much grateful. I will post this on development as well. Thnx to all.
G
did you ever find these files
Have been with the mt4g since dec and have never heard/seen anyone post these files for our phone...pretty sure if google can't find it, it doesn't exist ;-)
grhand82 said:
Could someone please provide the pd15diag.zip and pd15Ingram.nbh files for me. In dire need. Done forum searches as well as googled em with no result. If someone could locate these files and provide a download I would be ever so much grateful. I will post this on development as well. Thnx to all.
G
Click to expand...
Click to collapse
Ok, I think your a little ****fussed.
What you are looking for is the PD15IMG.zip depending on what you are trying to do there is the stock 2.2.1 and the latest 2.3.4.
it will factory reset your phone and S= on if you use the latest 2.3.4 there isn't a way to root it yet.
http://forum.xda-developers.com/showthread.php?t=1217237
dave5777 said:
Ok, I think your a little ****fussed.
What you are looking for is the PD15IMG.zip depending on what you are trying to do there is the stock 2.2.1 and the latest 2.3.4.
it will factory reset your phone and S= on if you use the latest 2.3.4 there isn't a way to root it yet.
http://forum.xda-developers.com/showthread.php?t=1217237
Click to expand...
Click to collapse
Nope..i want diag not img
I noticed that bootloader checks fire this file and began wondering what its purpose may be.
Since diag is in the file name I assumed it me be a diagnostic/service software that may assist with hard bricked phones
androph said:
Nope..i want diag not img
I noticed that bootloader checks fire this file and began wondering what its purpose may be.
Since diag is in the file name I assumed it me be a diagnostic/service software that may assist with hard bricked phones
Click to expand...
Click to collapse
The two files that you are looking for is related to the PD15IMG.zip. It's the native firmware to restore the phone back to a 100% OE fashion. EVERY phone looks for those when we boot into hBOOT and if you have them on your SDcard you will not be able to use hBoot effectively. The phone will boot, look for those files, then ask you to update. If you do, it'll return your phone back to stock. If you don't it'll reboot the phone. Thus eliminating the use of the options in hBoot.
I asked this very same question when i first got my MyTouch4G and was told those files are not needed unless you want to go back to 100% stock. And even then all you need is the PD15IMG.zip, as mentioned above.
If you phone is truely hard bricked and you cannot get into Recovery or hBoot, then the phone is truly bricked. If you can get into hBoot, have a good eMMC chip, the PD15IMG.zip will restore the phone.
androph said:
Nope..i want diag not img
I noticed that bootloader checks fire this file and began wondering what its purpose may be.
Since diag is in the file name I assumed it me be a diagnostic/service software that may assist with hard bricked phones
Click to expand...
Click to collapse
Ok let me try this again. What the bootloader is looking for is an update zip this zip has to be named PD15IMG.zip for it to be recognized. The diag files are already in the bootloader that's what is looking for the PD15IMG.zip. You shouldn't be messing with your bootloader if you don't know how it works.
Related
I've been doing some searching around but am unable to find a definite answer to my questions regarding the recovery. Following the Non-Tmobile 32B instructions for installing Cyanogen, I have flashed Amon_RA 1.6.2G as my recovery image and I am not in any way unhappy with this, just curious.
As per the instructions, prior to flashing the Amon_RA recovery permanently to the phone, I made a nandroid backup. If I were to restore this backup, would the stock recovery image be restored?
In the case of the answer being no I have been searching for the file for the stock recovery image with little success. Many people asking for it, seemly noone getting it. So where is it? Does anyone have it or can point me to where to get it?
After digging further I downloaded a file meant for the Google ION device (signed-google_ion-ota-150275.zip) out of pure curiousity, which has the same SPL as my device. Taking a peek inside the archive there is a recovery.img file in there. Is this the same recovery image that was stock on my phone? If not, how does it differ?
I know there are a lot of questions there, but after 2 days of forum reading and searching and countless google searches my questions have built up to this point. The answers just don't seem to be right there (maybe the blondeness is to blame), and I'd like to know that I can undo everything that has been done, just in case of needing repairs to whatever.
If anyone has the answers I will be most appreciative.
If you install the OTA ROM from your carrier, it will install the custom recovery and and basically revert all changes made since the day you set your hands on that phone.
A lot of people have to send in their phones for warranty and that's the quickest way to revert it.
There are instructions for T-Mobile US at:
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
You can use them except use your carriers sappimg.nbh
Mo0oSaH said:
If you install the OTA ROM from your carrier, it will install the custom recovery and and basically revert all changes made since the day you set your hands on that phone.
A lot of people have to send in their phones for warranty and that's the quickest way to revert it.
There are instructions for T-Mobile US at:
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
You can use them except use your carriers sappimg.nbh
Click to expand...
Click to collapse
Thanks for that but it looks like that file is totally useless to my phone, as I said above I'm looking for the image for my provider/country/whatever. I would imagine that the build number would be different in some way (correct me if I'm wrong) to the vodafone one and thus would be a bit of a mistake to claim warranty and have them find Tmobile stuff on it.
But thanks so much for the link, it's reassuring to see that the process could be rather painless, so long as I get the right files in the end. I'll cross my fingers that some clever person has what I'm searching for and it magically appears in my inbox one day lol
alliekhat said:
Thanks for that but it looks like that file is totally useless to my phone, as I said above I'm looking for the image for my provider/country/whatever. I would imagine that the build number would be different in some way (correct me if I'm wrong) to the vodafone one and thus would be a bit of a mistake to claim warranty and have them find Tmobile stuff on it.
But thanks so much for the link, it's reassuring to see that the process could be rather painless, so long as I get the right files in the end. I'll cross my fingers that some clever person has what I'm searching for and it magically appears in my inbox one day lol
Click to expand...
Click to collapse
The problem is that you're probably trying to flash the T-mobile 32B SAPPimg.nbh to your vodafone. You need the vodafone SAPPimg.nbh. Put it on your SD card, power down your phone, hold the volume and power buttons at the same time until your phone powers on. It should take you to a white screen and load the nbh file. It will ask if you want to proceed with the update. Just confirm and let the update COMPLETE FULLY. This nbh file will return you to 1.5 stock cupcake, but from here you will be able to receive OTA updates from your provider. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=580631
You will find the Vodafone nbh link at the top of this thread.
sombionix said:
The problem is that you're probably trying to flash the T-mobile 32B SAPPimg.nbh to your vodafone.
Click to expand...
Click to collapse
I'm not trying to flash anything, like I said in my first post, I'm happy with what I have done to my phone, I'm running cyanogenmod and have no intention of going back to stock unless I have a problem.
I'm just trying to find answers. Namely the fact that I have a nandroid back up of prior to flashing the new recovery and am wondering if restoring this will replace the recovery with the stock one, and whether the recovery images are all the same no matter where they come from.
My friend gave me his Evo to try to fix. It isn't rooted so S-on. I tried put a recovery file on to see if I can change the rom, but it just won't recognize it. Someone else posted a similar problem, but he got is to work. I tested the card and file and my evo asked if I wanted to update, but his phone will not work. It is stuck in boot loop. Not sure how he got stock on that. He doesn't mess with phones. There was an unbrick program I tried and it didn't seem to work, but I probably wasn't using it correctly since it kept changing the rom to the same rom from what I could tell.
It boots up sometimes to seem to work for a minute then boots again. I get the red triangle when I try to go into recovery. It probably doesn't have a recovery img since we haven't tried to root it.
ask your friend what exactly was he doing prior to this happeing, also whats the info when you go into the bootloader? i only ask cause the more info you provide the better chances are someone can help solve this issue. also you cant put a recovery or a custom rom on till your rooted.
ok
dzee206 said:
ask your friend what exactly was he doing prior to this happeing, also whats the info when you go into the bootloader? i only ask cause the more info you provide the better chances are someone can help solve this issue. also you cant put a recovery or a custom rom on till your rooted.
Click to expand...
Click to collapse
I can hold the power and down vol and go into bootloader. It goes through the zip file loading instructions and can't find the PC36IMG image and never asks if I want to update. I think I read a post where someone was told their bootloader is "locked".
if your bootloader is S-on, then yes; your bootloader is locked and you can't flash any custom roms. what you might be able to do is download an RUU rom and flash from your computer.
Look at the bootloader version and tell us what that says..
ok
Hypeo said:
if your bootloader is S-on, then yes; your bootloader is locked and you can't flash any custom roms. what you might be able to do is download an RUU rom and flash from your computer.
Look at the bootloader version and tell us what that says..
Click to expand...
Click to collapse
I believe it was version .79 or something like that. I'll check it when I get home.
As soon as he gets back from China I'll ask him what he did when started bootlooping. The phone might work for 30 seconds before going into reboot over and over so RUU might not work. But I can go into bootloader and into fastboot and was able to get a unbrick program to run and it seemed to be able to install another rom, but the rom it said it was installing was the same that was on the phone so maybe they needs S-off to function.
If you find your phone is rooted and can turn it on long enough to download an app from the market called Flash Image GUI, in the description it will say for the EVO 3d but it works on the og as well, you can also download off the devs xda thread just google (flash image GUI xda) and it should pop up, another thing make the file is on the root of your sd card and not in a sub folder. Good luck.
Sent from my PC36100 using xda premium
Oh and you can't flash custom roms with s on period, if it is on that's your problem there.
Sent from my PC36100 using xda premium
here it is
Hypeo said:
if your bootloader is S-on, then yes; your bootloader is locked and you can't flash any custom roms. what you might be able to do is download an RUU rom and flash from your computer.
Look at the bootloader version and tell us what that says..
Click to expand...
Click to collapse
S-on
HBOOT-0.79.0000
MICROP-041f
RADIO-1.39.00.04.26
Apr 14 2010, 15:41:34
Does this give any idea of what I can do.
Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this
wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day
You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.
Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now
I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?
sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
ok so i used this: themikmik dot com/showthread.php?11114-GUIDE-WIP-How-to-achieve-S-OFF-after-unlocking-2-18-HBOOT-with-HTCDev-com-No-More-Watermark
after using the HTCDEV to unlock.
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
i am stuck in between step 10 and 11.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
i downloaded su, root checker,and busy box. root checker says the phone is rooted. i know i need to get the h boot to a lower level inorder to do the unrevoked3 program.
tried flashing the recovery and says "cant open /sdcard/pc36img.zip (bad)"
made sure it wasn't zip.zip and it was so i fixed that and still wouldn't work.
the only thing i am not sure of is step 10 and wether i did it right :Once the misc partition has been updated, you can downgrade your Bootloader and HBOOT to a non-watermarked version rootable with unrevoked.
does the partition auto update or do i need to do something to make it update? i didn't see any option for this. eveything up to this point went exacty liek it should have so now i am lost. i have searched numerous forums and found similar problems but none that were exactly the same. and none of the solutions worked for me. i tried all the basics rebooting, etc and nothing. any info would be greatly appriciated.
the only other thing that i may have done wrong that i can tell is what file i am trying to make the pc36img. at the bottom of post # 1 it has 2 attachments listed as pc36img files those are the ones i am trying to use. when i try to click the hyperlinks thru the rest of the post i get an error message from that site thats says " This account's public links are generating too much traffic and have been temporarily disabled! " so i dont know if that site has the same zip files or i am completely using the wrong zip file.
sorry for the long winded post i know the noob video says make it brief but i figured the more info the better.
thank you.
sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
Click to expand...
Click to collapse
Oh brother was it!
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
Click to expand...
Click to collapse
Your S-On,so your not rooted.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
Click to expand...
Click to collapse
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.
Diablo67 said:
Oh brother was it!
Your S-On,so your not rooted.
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.
Click to expand...
Click to collapse
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
when i check with root checker it says i am rooted and have su. maybe it just means unlocked? busy box also says rooted?
pc36img is in all caps.
thanks for the quick response!
evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible
evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible
Click to expand...
Click to collapse
Ok,thanks for clearing that up,serious dudes i hate giving the wrong info when trying to help someone and i don't mind admitting when i'm wrong,lol.Your never to smart or old to learn something new.
Sent from my Dell computer.
I can probably help here.
If all you want is to be rooted, then you are. There's no reason to do the rest, especially if you're out of warranty. Since you already have a custom recovery installed, you can feel free to flash a custom ROM, and not even worry about the rest of the process.
The Dropbox links thing should be fixed now. I had to move them all to 4shared.
As far as the misc partition flashing, as long as you didn't get any errors when in the command prompt/adb shell, then I'm sure it flashed successfully. The only way to tell is if the Froyo PC36IMG.zip flashes successfully without a "main version fail."
I can assure you the PC36IMG works, as I've used it many times myself. Did you confirm the md5? Is it possible your SD card got corrupted somehow? Those are the only reasons it wouldn't pick it up.
thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?
98tib said:
thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?
Click to expand...
Click to collapse
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .
Captain_Throwback said:
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .
Click to expand...
Click to collapse
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.
98tib said:
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.
Click to expand...
Click to collapse
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.
This is what's cool about this forum a noob asking a question and you get 4 big time contributors helping out!
Sent from my PC36100 using xda premium
Captain_Throwback said:
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.
Click to expand...
Click to collapse
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem
98tib said:
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem
Click to expand...
Click to collapse
What kind of sd card are you using? You might want to try a different card, or reformat the stock card, if that's what you're using. That's the only other reason it wouldn't pick up the file, provided it's named correctly. And I assume you verified the md5 and it's good? And you're certain the file is on the root of the sd card as well? I cant think of anything else that could be causing the problem. Let me make sure my bootloader reads the file just to make sure.
EDIT: Scratch everything I said above. If your phone still says "unlocked" at the top of the bootloader, the misc partition wasn't updated successfully. Did you already complete that part, with no errors? You need to reconnect the device while booted up, with USB Debugging enabled, and run those commands from the command prompt from the folder with adb in it. Make sure you have the files "flash_image" (extracted from zip file) and "mtd-eng.img" (extracted from zip file) on the root of your sd card. If you're using Windows 7, run Command Prompt as an administrator. Let me know the output of those commands before continuing. If you got any errors on that part, that would be why you can't flash the Froyo ROM.
I saw you mentioned that in your OP, but I guess I didn't realize you skipped that part. That'a really the most important part of the process. It's the part right before the sentence you mention about the misc partition being downgraded. That last command flashes the mtd-eng.img file to the misc partition.
both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.
98tib said:
both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.
Click to expand...
Click to collapse
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".
Captain_Throwback said:
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".
Click to expand...
Click to collapse
thank you, you are my savior! its always the dumb things that you think you did right that you did wrong! lol. thank you again!
now i'm off to screw something else up!
I got my hands on a mytouch that I am trying to fix. I am not 100% on the original condition but I was told it was stock and never touched. The owner went to sleep and woke and the phone will now only boot into the boot loader screen. Says S-ON, HBoot 0.89.0006, radio 26.13.04.19_m. It is completely unresponsive and none of the buttons do anything. When I plug it in the pc notices it and the phone changes to fast boot usb. I have tried placing the pd15img thing on the sdcard and it doesn't really seem to notice it. Adb doesn't seem to detect it either. Any ideas?
i really am wondering how many people actually read my brick guide...
saranhai said:
i really am wondering how many people actually read my brick guide...
Click to expand...
Click to collapse
i read your guide. Did you miss the part in my first comment where i said I tried the pd15img file on the sdcard but that the phone doesn't seem to notice it.
"For S-On users:
Q: help! my phone is stuck on the Mytouch logo screen!
A: pull the battery, and see if you can get into the bootloader using volume down+power buttons
if you can get into the bootloader:
1) see if you can wipe data/do a factory reset in bootloader.
2) flash the stock Glacier PD15IMG.zip file choose from either
Android 2.2.1 OR Android 2.3.4
rename both files to PD15IMG.zip if not already.
-put both files in the ROOT of your SDcard, reboot into bootloader/hboot, and follow the onscreen instructions
note: if you are still unclear on what to do, read the "HOW TO RESTORE TO STOCK" section"
I PUT THE FILE ON THE CARD AND IT JUST SITS THERE TOTALLY UNRESPONSIVE. None of the buttons work and the only thing I can do is pull the battery out.
Now thanks for the "help", but do you have any real suggestions?
rage2wrath said:
i read your guide. Did you miss the part in my first comment where i said I tried the pd15img file on the sdcard but that the phone doesn't seem to notice it.
"For S-On users:
Q: help! my phone is stuck on the Mytouch logo screen!
A: pull the battery, and see if you can get into the bootloader using volume down+power buttons
if you can get into the bootloader:
1) see if you can wipe data/do a factory reset in bootloader.
2) flash the stock Glacier PD15IMG.zip file choose from either
Android 2.2.1 OR Android 2.3.4
rename both files to PD15IMG.zip if not already.
-put both files in the ROOT of your SDcard, reboot into bootloader/hboot, and follow the onscreen instructions
note: if you are still unclear on what to do, read the "HOW TO RESTORE TO STOCK" section"
I PUT THE FILE ON THE CARD AND IT JUST SITS THERE TOTALLY UNRESPONSIVE. None of the buttons work and the only thing I can do is pull the battery out.
Now thanks for the "help", but do you have any real suggestions?
Click to expand...
Click to collapse
Sounds like you have yourself a paperweight, OP.
Also, don't be rude to Saranhai, please. About 4.5 out of 5 of the "Help my phone is bricked" threads we get could have been prevented by the person reading his guide. No kidding.
If the volume up and down keys don't respond and the bootloader doesn't scan for the PD15IMG.zip file, then it sounds like your bootloader is corrupted or in some other way damaged. If the phone just decided to do this, literally, overnight it's probably a failed eMMC.
Anybody else want to chime in? I honestly hope I'm wrong.
Sorry op, it is most likely bricked, send it back to tmo or htc if you can. Also, estallings is right, please don't be rude to saranhai, he has helped a lot of people pull their phones from the brink.
Thanks for a real reply. I was afraid it was just dead but I thought someone might have a trick or 2.
I got nothing against Saranhai, but for some reason he was trying to be an ass to me. He could have said nothing but instead he implied I don't understand how use a forum or look through guides or research a problem before begging for help.
And his "awesome" unbricking guide not only has dead links to megaupload files its also written very unclear in certain points.
"2) flash the stock Glacier PD15IMG.zip file choose from either
Android 2.2.1 OR Android 2.3.4
rename both files to PD15IMG.zip if not already.
-put both files in the ROOT of your SDcard,"
What does that even mean? So do I get to choose, or do I have to download both? It doesn't really matter because one of the links is dead anyway.
rage2wrath said:
Thanks for a real reply. I was afraid it was just dead but I thought someone might have a trick or 2.
I got nothing against Saranhai, but for some reason he was trying to be an ass to me. He could have said nothing but instead he implied I don't understand how use a forum or look through guides or research a problem before begging for help.
And his "awesome" unbricking guide not only has dead links to megaupload files its also written very unclear in certain points.
"2) flash the stock Glacier PD15IMG.zip file choose from either
Android 2.2.1 OR Android 2.3.4
rename both files to PD15IMG.zip if not already.
-put both files in the ROOT of your SDcard,"
What does that even mean? So do I get to choose, or do I have to download both? It doesn't really matter because one of the links is dead anyway.
Click to expand...
Click to collapse
Place one on there at a time. At least with the name PD15IMG.zip. The name has to be very exact and the bootloader is suppose to scan for the file whenever it loads.
I would suggest the GB (2.3.4) file. Does that link work?
rage2wrath said:
Thanks for a real reply. I was afraid it was just dead but I thought someone might have a trick or 2.
I got nothing against Saranhai, but for some reason he was trying to be an ass to me. He could have said nothing but instead he implied I don't understand how use a forum or look through guides or research a problem before begging for help.
And his "awesome" unbricking guide not only has dead links to megaupload files its also written very unclear in certain points.
"2) flash the stock Glacier PD15IMG.zip file choose from either
Android 2.2.1 OR Android 2.3.4
rename both files to PD15IMG.zip if not already.
-put both files in the ROOT of your SDcard,"
What does that even mean? So do I get to choose, or do I have to download both? It doesn't really matter because one of the links is dead anyway.
Click to expand...
Click to collapse
Maybe I went off on you the wrong way, sorry about that. Its just that so many posts lately are from idiots who don't read anything at all..and they come here wining and crying. Maybe you could've posted that you read around next to
As for my guide: I will try to fix the links and make it more clear...
-Saranhai