Related
Ok idk exactly what it is called but I know it has 777 in it. The file that is created on your SD card when you root using GFree. I saw someone had it posted on here somewhere a while ago but now I can no longer find it. Anyone have a link to that file? Please and Thank you! I think it may be my last chance at saving my myTouch with that stupid Cache error! The other way I fixed it last time isnt working this time
dcwiker05 said:
Ok idk exactly what it is called but I know it has 777 in it. The file that is created on your SD card when you root using GFree. I saw someone had it posted on here somewhere a while ago but now I can no longer find it. Anyone have a link to that file? Please and Thank you! I think it may be my last chance at saving my myTouch with that stupid Cache error! The other way I fixed it last time isnt working this time
Click to expand...
Click to collapse
part7backup-000000000.bin is created in root of your /mnt/sdcard/~ when you ran the gfree. If you lost it then sorry I don't think anyone ease's would work as I am not 100% sure if that is device specific but it may be leading to that.
Far as the cache error goes I hope it works out for ya as thats the closest soft-brick we have. But do you have adb installed? If so push and flash the CMWR2.5.1.2 manually. I didn't isolate the issue if it's gfree related as we still need data to verify those who are effected are only gfree users or folks who just simply did root.sh without gfree.
TmpUsr said:
part7backup-000000000.bin is created in root of your /mnt/sdcard/~ when you ran the gfree. If you lost it then sorry I don't think anyone ease's would work as I am not 100% sure if that is device specific but it may be leading to that.
Far as the cache error goes I hope it works out for ya as thats the closest soft-brick we have. But do you have adb installed? If so push and flash the CMWR2.5.1.2 manually. I didn't isolate the issue if it's gfree related as we still need data to verify those who are effected are only gfree users or folks who just simply did root.sh without gfree.
Click to expand...
Click to collapse
Yeah I know I had this stupid cache crap before and it was a b**ch to fix here is the link to my thread
http://forum.xda-developers.com/showthread.php?t=1043459
And I have ADB and EBL (Hboot 85.2007) and last time pushing the old CWM worked but this time no dice I get Write FAILED everytime. So I hear that the PMG15.IMG can possibly fix this issue as well but I need that part7 file and I dont have mine anymore thanks to CM7 killing my SD card a while back anyhow I have seen it posted for DL here before and I think it worked for the guy who used it, I mean its worth a shot. It's not like I can do ANYMORE damage to the phone! lol
dcwiker05 said:
Yeah I know I had this stupid cache crap before and it was a b**ch to fix here is the link to my thread
http://forum.xda-developers.com/showthread.php?t=1043459
And I have ADB and EBL (Hboot 85.2007) and last time pushing the old CWM worked but this time no dice I get Write FAILED everytime. So I hear that the PMG15.IMG can possibly fix this issue as well but I need that part7 file and I dont have mine anymore thanks to CM7 killing my SD card a while back anyhow I have seen it posted for DL here before and I think it worked for the guy who used it, I mean its worth a shot. It's not like I can do ANYMORE damage to the phone! lol
Click to expand...
Click to collapse
BTW it was me who posted the CMWR2.5.1.2 flash leak on another forum as I was here on XDA manually hacking the SLC-EUDA emmc block trying to replicate the issue the first person in MT4G to have in here. But if all you get now is fail partition update (fail-pu) then there is nothing else you can do. I still need more data to isolate if this is just gfree user based and not those who has s-off with eng boot without gfree. I try to do more test today but I can't roll the gfree maybe I am lucky? but ill post my finding if I ever able to get it and replicate the conditions. Only known meth to fix this is replacing the motherboard for now.
So you're saying PMC15.IMG wont fix this either? I don't understand why last time I was able to ADB push CWM 2.5.1.2 via Fastboot and then go into Recovery, Format cache and it was fine phone booted. I reflashed CWM 3.1.2.4 and went about my business...now it happens again and I can not flash CWM via recovery this time and thus I'm boned?? FML I JUST got this phone...my last ones screen peeled away, it was a referb from insurance so it was replaced with this one.
I work for T-Mobile so I really don't wanna bork my phone enough to hide root then send it in for a warrenty replacement cuz I don't think its right to screw my own company but damn I don't want to be out a phone, my back up phone's menu button doesn't work so it's really freaking annoying , guess I will deal till the Sensation 4g!
i dont rememeber which unroot thread but one of them has it, and supposedly it works with any mytouch 4g. not just the one it was created on
Well once you have fail-pu on hboot when you try to revert back to PD15IMG (rom/radio) both update will fail as you can't write to the partition block. Now far as I know this is only seen in CMWR3.0.0.0+ which at the time I flashed it manually though terminal. At this point there is way to many variables to consider mostly we need community input as those who is effected did use gfree as it could mean why the emmc simply gets -ro access now I am aware its using slc-euda so you can't low level format it this is the reason they replace the motherboard. We are not just talking about single partition here as it seems the recovery partition is first thing to be effected. I need to do some more work and atm I only have 1 phone and I don't feel like hacking it and end up with dead as I don't have any backup phones as I gave it away. Let me see if I can get another MT4G cheaper from ebay/cl and I can test on it.
VibrantOwnr said:
i dont rememeber which unroot thread but one of them has it, and supposedly it works with any mytouch 4g. not just the one it was created on
Click to expand...
Click to collapse
Thats the gfree revert meth which is the only place you use part7backup and then if you want to roll back to stock eng bootloader you do the unroot.sh which flash the eng.nb0 and turns S-OFF.
Alright so let me get this all played out in my terms so I can see if I understand it.
1. Do I actually need that part file? I rooted with gfree so I figure yes
2. Will PMG15.IMG work at all or no?
3. Should I just say F it all and try anyhow? If so anyone wanna throw me a link to the part file?
4. I STILL don't get why this happened the first time! And why the way I fixed it the 1st time isn't doing $hit the 2nd time...
UGH! Damn it why couldn't this happen the end of May closer to when the Sensation 4G is suppose to launch... :'( damn you CWM ghost...
I understand that there are similar threads out there but I still can't seem to figure it out. I apologize ahead of time for any wrong terminology, I'm pretty new to all of this. To give a background on what happend, I started my day off by rooting my phone with the following link (I had tried a different method with visionary plus and terminal but it wouldn't work)
http://forum.xda-developers.com/showthread.php?t=858996
this method worked just fine and gave me s=off, currently what I have is as followed:
Glacier PVT ENG S-OFF
HBOOT-0.85.2007 (pd1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
After gaining my root I was excited to try and flash a new rom. I installed the clockwork rom manager from the market, flashed the recovery then backed up my current in case of future problems.
Next step for me was to flash a new rom. for this I followed
http://forum.xda-developers.com/showthread.php?t=1070444
everything seemed to be going fine, phone restarted and I sat waiting (since I read the first boot could take 10min or so) after at least an hour I began to worry. Nothing happened, just stayed on the mytouch 4g startup screen and never changed.
I rebooted into recovery to try again, I can get into my hboot and into clockwork Mod Recovery v3.0.2.4 just fine. but there are a whole bunch of errors I cant fix. When clockwork starts I get the errors
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
If I try to format anything (cache, system...) it will say
Formatting /cache... (or system depending on what I am trying)
Error formatting /cache! (or system)
If I try to restore to a previous time it will start to do the restore, it will first do the boot which goes fine, but when it tries to format the system during the restore it fails just like if trying to format it individually.
At this point I would just like to get my phone working, any help would be much appreciated. (please try and use details so I can follow... still trying to learn alot)
I hate to be the bring of bad news, and remember don't kill the messenger, but it sounds as if your phone is truly bricked. There have been several threads on this already. As i know you are aware of. And very few, if any, have recovered.
There is a thread Posted here that boils down to the fact if the VISIONary.apk & root.sh method do not work then you have a bad eMMC.
Since it appears your phone does have a bad eMMC, hope you have insurance on it.
neidlinger said:
hope you have insurance on it.
Click to expand...
Click to collapse
neidlinger- i happen to have bought the insurance for 6 bucks a month or whatever it was - they said it extends the mfr warranty another year and then it gives you drop-in-toilet etc insurance with around a 120$ deduc.
I'm with t-mobile and got the phone thru the mail. If I take this back to a local TMO store for warranty claim, there's no difference is there? (i.e. you dont have to follow the mail route just because that's how you got it originally)
also- would these cache mount or failed -pu errors, essentially beyond repair - are we getting these to be recognized as hardware failure (i.e. no deductabel and counted as a mfr defect) or are these coming up as TMO insisting on counting them as some user fault, requiring the deductable to be paid??
acsi007 said:
neidlinger- i happen to have bought the insurance for 6 bucks a month or whatever it was - they said it extends the mfr warranty another year and then it gives you drop-in-toilet etc insurance with around a 120$ deduc.
I'm with t-mobile and got the phone thru the mail. If I take this back to a local TMO store for warranty claim, there's no difference is there? (i.e. you dont have to follow the mail route just because that's how you got it originally)
Click to expand...
Click to collapse
9/10 times if you buy a phone through the mail you will have to exchange it through the mail they will not allow you to walk into a store and do the exchange. I ran into that with my blackberry 9700.
acsi007 said:
also- would these cache mount or failed -pu errors, essentially beyond repair - are we getting these to be recognized as hardware failure (i.e. no deductabel and counted as a mfr defect) or are these coming up as TMO insisting on counting them as some user fault, requiring the deductable to be paid??
Click to expand...
Click to collapse
nope there is not way around it. once the eMMC fails it's down for the count.
neidlinger said:
I hate to be the bring of bad news, and remember don't kill the messenger, but it sounds as if your phone is truly bricked. There have been several threads on this already. As i know you are aware of. And very few, if any, have recovered.
There is a thread Posted here that boils down to the fact if the VISIONary.apk & root.sh method do not work then you have a bad eMMC.
Since it appears your phone does have a bad eMMC, hope you have insurance on it.
Click to expand...
Click to collapse
Is there any way to tell if the eMMC is bad. the visionary install went fine, just using the terminal to do the sh root.sh command wouldnt work, it would just keep saying failed (function not implemented) which is why I switched to visionary and adb gfree method... which worked like a charm, not a single hickup with it. the problems didnt start coming until after the rom instillation didnt work
hiddentalnt said:
Is there any way to tell if the eMMC is bad. the visionary install went fine, just using the terminal to do the sh root.sh command wouldnt work, it would just keep saying failed (function not implemented) which is why I switched to visionary and adb gfree method... which worked like a charm, not a single hickup with it. the problems didnt start coming until after the rom instillation didnt work
Click to expand...
Click to collapse
i see you didn't read the thread i posted.
The link i posted is to a thread here @ XDA, called "Post your eMMC serial number". It has alot of information regarding this very subject, including how to tell if your eMMC is indeed a faulty one [ by serial number ].
it really doesn't matter when the problem happens. it just matters that it happened.
./gfree is basically forcing the rooting process to happen while the root.sh is asking for it to happen. If the root.sh process doesn't allow you to proceed, then you may have a faulty eMMC. you forced the phone to root and opened up a bee hive in the process.
yeah sorry, I posted and then was just reading that forum as you replied... sorry about that.
hiddentalnt said:
yeah sorry, I posted and then was just reading that forum as you replied... sorry about that.
Click to expand...
Click to collapse
no need to tell me your sorry, . If you want to make me mad tell me Popeye's Chicken is out of business. we all start out somewhere. Just be willing to read prior to doing anything or asking anything. Chances are there is an answer somewhere. Sometimes we like what we read and sometimes we don't either way it's out there.
Hiddentalnt, please post your eMMC serial. We need people who have recovery errors to post what serial they have so we can actually pinpoint the problem being the chip. Thanks. The instructions are posted in the thread neidlinger posted above. Thanks
xdviper said:
Hiddentalnt, please post your eMMC serial. We need people who have recovery errors to post what serial they have so we can actually pinpoint the problem being the chip. Thanks. The instructions are posted in the thread neidlinger posted above. Thanks
Click to expand...
Click to collapse
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
hiddentalnt said:
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
Click to expand...
Click to collapse
after you got ADB installed and you punch in adb devices does it give you a serial number?
hiddentalnt said:
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
Click to expand...
Click to collapse
nevermind... just got it M4G2DE
so from what Im reading...theres no coming back from this, the chip is dead?
hiddentalnt said:
nevermind... just got it M4G2DE
so from what Im reading...theres no coming back from this, the chip is dead?
Click to expand...
Click to collapse
pretty much.
I do know one guy was able to via flashing an older recovery image via the hBoot, but you have to have the .85 engineering screen. Which you do not have.
neidlinger said:
pretty much.
I do know one guy was able to via flashing an older recovery image via the hBoot, but you have to have the .85 engineering screen. Which you do not have.
Click to expand...
Click to collapse
what is the .85 engineering screen, i do have hboot - 0.85.2007 but im assuing thats different.
So its time to call up TMO and have them send me out a new phone? do I need to unroot first so they dont find it?
hiddentalnt said:
what is the .85 engineering screen, i do have hboot - 0.85.2007 but im assuing thats different.
So its time to call up TMO and have them send me out a new phone? do I need to unroot first so they dont find it?
Click to expand...
Click to collapse
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
neidlinger said:
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
Click to expand...
Click to collapse
sorry for asking so many questions. but you really have been a great help. do you have any idea where i can find the 2.5.x.x recovery image, I've been trying to look but I cant find it, just didn't know if you already knew of a forum that had it.
hiddentalnt said:
sorry for asking so many questions. but you really have been a great help. do you have any idea where i can find the 2.5.x.x recovery image, I've been trying to look but I cant find it, just didn't know if you already knew of a forum that had it.
Click to expand...
Click to collapse
I've got it store on my Lunix computer at home. I do not have it on my phone or on my work computer.
sorry. I can post it later on tonight.
neidlinger said:
I've got it store on my Lunix computer at home. I do not have it on my phone or on my work computer.
sorry. I can post it later on tonight.
Click to expand...
Click to collapse
Thanks, I appreciate it. I'm off to class anyways so I have to put a pause on trying to fix it till then.
neidlinger said:
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
Click to expand...
Click to collapse
I would be that ONE case where this option did work. And the difference I have seen between the first time when flashing CWM worked and the second time (when it DIDN'T work) is the COMMAND error. If your CWM says anything about COMMAND error then flashing the old CWM isn't gonna work.
Here is a link to a post I made with a download for the old CWM
http://forum.xda-developers.com/showthread.php?p=14069400#post14069400
have any questions PM me if needed. Hit the Thanks button to if any of us have helped you at all.
Good luck man, I have a 450 dollar batter charger right now, so you'll need it :/
dcwiker05 said:
I would be that ONE case where this option did work. And the difference I have seen between the first time when flashing CWM worked and the second time (when it DIDN'T work) is the COMMAND error. If your CWM says anything about COMMAND error then flashing the old CWM isn't gonna work.
Here is a link to a post I made with a download for the old CWM
http://forum.xda-developers.com/showthread.php?p=14069400#post14069400
have any questions PM me if needed. Hit the Thanks button to if any of us have helped you at all.
Good luck man, I have a 450 dollar batter charger right now, so you'll need it :/
Click to expand...
Click to collapse
I'm not sure I fully understand your directions in the other thread. So when i download the zip, i get inside it and go all the way to recoveries to get out one of the disc image files. which one do I want, there is a 2.5.1.3 and 2.5.1.4 and a 3.0.0.5 but I'm assuming thats not it... but once I get one of those I rename it recovery.img then i use abd to push it... what is the command to push it? and i have to be in hboot then fastboot to push it?
Hi everyone,
I am in a big problem it seems. This is what happened: My phone was working fine with CM7 and latest version of CW Mod but suddenly everything started force closing. So what I did was to factory reset the phone from recovery wiping cache and davlik cache. After doing factory reset it stopped at splash screen itself and not booting up. Does factory reset removes rooting for mt4g?
After that, I tried to install ADB and root again but adb devices doesnt show my device when I am in recovery. But when I go to fastboot it, fastboot devices cmd shows my device.
I then tried to go back to stock by applying PD15IMG and it successfully applies it but now it gets stuck at "my"splash screen. What should I do now?
Thanks in advance.
Uh oh... Sounds like bad eMMc chip which no, can't be fixed. I'd see if you can check your eMMc but if not I believe your screwed and will have to send back to tmo.
Sent from my HTC Glacier using XDA Premium App
Do you get any cache errors in recovery when wiping?
Did you upgrade your radio to a version other than stock before attempting to restore to factory using PD15IMG?
It's starting to sound like a bad eMMC at this point though. Those things are starting to fail left and right!
I will check eMMC and post it here. But yes, while wiping cache I get error E: cant open /cache/ or something like that so i assumed that it might be because i got unrooted and I wanted to root again (but i cant adb). When applying ROM, it exits saying Status 1. No, I didn't upgrade radio images.
Fc followed by bootloop followed by cache errors...definitely eMMc
Sent from my HTC Glacier using XDA Premium App
Because of applying PD15 image I got original h-boot version (not engineering h-boot) so couldn't check eMMC. But I have radio version which is 26.03.02.26_M
If I assume that eMMC is gone then, Is there any other option of doing ANYTHING except sending it to TMobile as I am using it outside US.
sagarparmar said:
Because of applying PD15 image I got original h-boot version (not engineering h-boot) so couldn't check eMMC. But I have radio version which is 26.03.02.26_M
If I assume that eMMC is gone then, Is there any other option of doing ANYTHING except sending it to TMobile as I am using it outside US.
Click to expand...
Click to collapse
Bootloader version has nothing to do with being able to check eMMC version.
http://forum.xda-developers.com/showthread.php?t=1081243
Somewhere in there there's instructions for checking without root if you've lost it already.
Thanks for the link but I can't adb. fastboot shows my device but adb doesn't. I don't know if there is any problem with my drivers. because when i plug the phone in is shows ADB Interface in Device manager. Still I will check them again will try to put eMMC version ASAP.
sagarparmar said:
Thanks for the link but I can't adb. fastboot shows my device but adb doesn't. I don't know if there is any problem with my drivers. because when i plug the phone in is shows ADB Interface in Device manager. Still I will check them again will try to put eMMC version ASAP.
Click to expand...
Click to collapse
Someone posted some instructions a while back that allowed you to check your eMMC version using terminal commands, so you could do it without root or ADB, but for the life of me I can't find them! I thought they were in the main eMMC serial thread, but maybe not. I'll keep looking.
TeeJay3800 said:
Someone posted some instructions a while back that allowed you to check your eMMC version using terminal commands, so you could do it without root or ADB, but for the life of me I can't find them! I thought they were in the main eMMC serial thread, but maybe not. I'll keep looking.
Click to expand...
Click to collapse
This is the terminal cmd it seems:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
But right now, my phone is not even booting up. how would I go to terminal emulator?
sagarparmar said:
This is the terminal cmd it seems:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
But right now, my phone is not even booting up. how would I go to terminal emulator?
Click to expand...
Click to collapse
I'm suffering from brain fade today. I forgot about the fact that your phone wasn't booting. If memory serves, there is a terminal option in CWM recovery. If your recovery is still usable, try selecting the terminal feature and enter those commands there. Honestly though, this would only serve to confirm what we already know. Your eMMC has failed, so there's isn't much hope. The good news is most people have had no trouble doing a warranty exchange, even when sending in a rooted phone. Good luck!
As I tried to flash PD15IMG it is now into stock recovery. Need to flash CWM using fastboot but dont know whether it would work or not because last time I tried (before applying PD15) it failed saying Status 1. Need to check that.
But you know what the bigger problem is, I bought it from Swappa.com and I don't even know whether I can exchange it or not. I will have to send it to my friend who is in the US as I am outside.
Do they give warranty card or something when you buy (I dont know as I am not the original buyer ) ??
TeeJay3800 said:
I'm suffering from brain fade today. I forgot about the fact that your phone wasn't booting. If memory serves, there is a terminal option in CWM recovery. If your recovery is still usable, try selecting the terminal feature and enter those commands there. Honestly though, this would only serve to confirm what we already know. Your eMMC has failed, so there's isn't much hope. The good news is most people have had no trouble doing a warranty exchange, even when sending in a rooted phone. Good luck!
Click to expand...
Click to collapse
There's a terminal in cwm...? Since when?
Sent from my HTC Glacier using XDA Premium App
Nope, bought mine from eBay and htd fixed it when mine quit. Just called for a rma, advised it was bootloopimg then went blank, shipped it and got another or it back fixed. Call it won't hurt.
sagarparmar said:
As I tried to flash PD15IMG it is now into stock recovery. Need to flash CWM using fastboot but dont know whether it would work or not because last time I tried (before applying PD15) it failed saying Status 1. Need to check that.
But you know what the bigger problem is, I bought it from Swappa.com and I don't even know whether I can exchange it or not. I will have to send it to my friend who is in the US as I am outside.
Do they give warranty card or something when you buy (I dont know as I am not the original buyer ) ??
Click to expand...
Click to collapse
knothead said:
Nope, bought mine from eBay and htd fixed it when mine quit. Just called for a rma, advised it was bootloopimg then went blank, shipped it and got another or it back fixed. Call it won't hurt.
Click to expand...
Click to collapse
Hey I'm in the situation where my phone won't even turn on now... I called HTC already and they're actually mailing in a battery thinking that it's the reason the phone won't charge or turn on...
What were the steps you went through to get the to take it in? Did you end up getting a new one or the one you sent in for repairs? You paid for shipping or any repair fees? Any input would be useful... let me know!
Thanks!
Nicgraner said:
There's a terminal in cwm...? Since when?
Click to expand...
Click to collapse
It doesn't. As I said in that post, I wasn't sure. It turns out I was thinking of Amon-RA's recovery which does have a terminal option.
TeeJay3800 said:
It doesn't. As I said in that post, I wasn't sure. It turns out I was thinking of Amon-RA's recovery which does have a terminal option.
Click to expand...
Click to collapse
CWM does have adb shell though.
Sent from my HTC Glacier using Tapatalk
knothead said:
Nope, bought mine from eBay and htd fixed it when mine quit. Just called for a rma, advised it was bootloopimg then went blank, shipped it and got another or it back fixed. Call it won't hurt.
Click to expand...
Click to collapse
Yeah, It would be great if you tell the procedure. You directly called HTC guys or TMobile? What else do you need to ship along with the phone?
Flashing CWM??
Guys,
As I described my phone is in a boot loop but I can see it in fastboot but when i go to recovery it jst goes to bad state and have to remove battery. Is there a way to flash CWM recovery and opening adb shell as I might want to see what is eMMC and need to try this out http://forum.xda-developers.com/showpost.php?p=15299273&postcount=66 and http://forum.xda-developers.com/showthread.php?t=1039504&page=2
I know we can flash recovery from fastboot but when i tried that it gave me an error saying you remote not allowed (android sdk on Win 7).
You weren't in fastboot mode, but in hboot mode.
Choose "fastboot" to be able to flash.
Hello, xda-developers,
I have a myTouch 4G that was updated to the 2.3.4 Gingerbread software and wanted to root it. In order to do so, after many research, it states that there is no root for the 2.3.4 Gingerbread software and for it to be rooted you'll have to downgrade it.
The reason why I wanted to root it is because I am having a problem with the WIFI connectivity in my home and was wondering if it will fix it. Same reason why I update it to the 2.3.4 Gingerbread software in the first place. The myTouch 4G that I have will "RARELY" connect to my wireless router in my home but for some reason it doesn't fail me when connected to other wireless routers outside of my home even when having the same router. But this is now not the problem.
As you can read, the title says it all. My problem now is that I just soft bricked my myTouch 4G after a downgrade that I followed here: http://forum.xda-developers.com/showthread.php?t=1178912# Like the noob always say when something goes or went wrong, "Boohoo, I don't know what I did wrong. Someone, please, help me." But I THINK I know what I did or went wrong.
I followed the guide strict and carefully hoping I don't brick it but then I said to myself, "It's a 99.9% chance I won't, I think... what can possibly go wrong?" Everything went well. I did everything it says and once the update bar fills up to the top, BAM! It hits the "T-Mobile myTouch 4G" boot screen. I was happy. Very happy because I felt accomplished and one step closer to excitingly freeing my phone. But my hopes went down when it stayed like that for hours on end. I pulled the battery out and reboot it and nothing was fixed. Although it was stuck, I still can access the bootloader. I pulled out the battery again and boot it to the bootloader and re-updated it again and nothing was fixed. I yanked out the battery one last time and deleted the PD15IMG.zip file from the SD card to keep it from asking to update everytime I boot it to the bootloader so I can factory reset it but, still, that didn't help.
Like I said. I think I know what I did or went wrong. Examine the guide. The "Gaining Temp Root" part I did right. The "Changing Version Number to Allow Downgrade" I did correct and the results on the command prompt came out the way it stated it should come out. THEN! I yanked out the battery to reboot it after that. When I've done so I continued to the next procedure and everything went how it says it should go but, instead of the end results, I got it stuck on the "T-Mobile myTouch 4G" boot screen after the update. I think that's where I messed up. When I yanked out the battery to reboot it after the "Changing Version Number to Allow Downgrade" part. I believe it kicked it out from root. It is a temp root by the way and I read it somewhere that said, "Once you're rooted you CAN downgrade it." Something like that which made me think it wasn't rooted after that reboot and the downgrade wasn't a success. I also have two other guesses in which I think soft bricked the phone. I either have a bad eMMC-boot or the PD15IMG.zip was bad. These are my thoughts in what went wrong. I'm asking for your help. So can you help me find the solution to this problem?
Thank you very much in advance for your time and effort into reading this and helping me out. I really appreciate it.
-Victor​
P.S. Here's the information on the myTouch 4G's bootloader:
GLACIER PVT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Apr 14 2011,13:18:22
Again, Thank you.
wow, same thing happened to me.
You could try updating it back up to the 2.3.4 RUU. If that works, nothing lost at least.
You used a wrong PD15IMG, most probably.
If you have used the correct one, your bootloader would be 0.86.0000, but it isn't.
Please re-download the correct PD15IMG and try again. When it works, if it throws any messages - write them here, so someone will be able to help you. If you see "Fail-PU" - your phone is dead.
Your mistake might have been removing the battery instead of typing "adb reboot bootloader". Yanking the battery off a working phone can destroy its eMMC. If that's what happened to you - well, you can replace your phone under warranty and follow the instructions better next time.
It was definitely the part where you yanked out your battery. You lost temp root then. Why you did it, not sure. But it's already been done so Let's not linger.
Have you tried starting over from step one?
Sent from my HTC Glacier using XDA App
You used a wrong Rom to downgrade or it is corrupted during download.
Download the official 2.2.1 rom, put it to the root of your sdcard, and try to update.
The original bootloader is 0.86.0000
You can download it here
Rename it to PD15IMG.zip before updating.
Do what he said
Do what the last guy said and rename the image and flashing.
Here is what has happened, you were probably installing a signed downgrade to a previous version. Either you got the wrong file, your download was corrupt (THANKS TO CHROME), or you didn't clear your cache dalvik needs to be clear if you run a different kernel. The main cause of hanging at the bootscreen is the incorrect cache either regular or dalvik. Thats what I've noticed from threads and just in general.
You don't appear to be running clockworkmod recovery. If you are going to mess with the system, DO IT ALL THE WAY! Don't get confused with this one... if you are planning to write radios, flash updates, or do anything YOU WILL NEED ROOT. This is because something could go wrong and you could be locked out. If you aren't willing to commit to basic root privileges, do not attempt to downgrade. Either go all the way, or don't go at all. That's just some friendly advice cause people will make the misconception if they just downgrade thats fine, but getting root is more dangerous... not true! If you have root, you can actually gain control of the phone and restore even a 'broken' one.
ROOT is mostly gained from within the phone in the operating system. You use an APP to gain root privileges. Once you get root, you need to get SU a program to grant privileges to programs that request them. Then you need to get clockworkmod rom manager so you can flash a recovery (internet and market access is required unless you can install from the .apk and use adb). ONCE YOU HAVE THAT RECOVERY you can downgrade, upgrade, flash, flex, backup, restore all with a simple push of a button, no expertise required!!
You can even revert to stock easier when you have root.
Once you get that recovery installed then look for ways to turn s-off and unlock your sim so you don't have to worrry about stuff.
And remember, they might not honor your replacement phone if you hack or modify it... but if you lose the phone they will replace it for you.
Big Thanks For the Help!
Hello, xda-developers,
Thank you, all, for your help! I've figured out the problem.
It was because of the PD15IMG.zip file. It was a bad one and I figured it out by downloading another one BUT, instead of downloading it from the same site I got it from, I downloaded it from a different site. I've barely figured this out and I could have fixed this problem way earlier if I had checked back my post.
Big thanks, again, to you guys for taking your time and helping me figure out this problem. It has been a month since I've been "Android-less" and now I am going to treasure it more than usual and I can not lie... I miss its awesomeness.
My phone is now back and it is officially perm-rooted! Love this phone more than ever with all the things it can do now. Rocking this phone out now with the Virtuous Unity rom and it blows... me... away!
-Victor​
Well..... at last you figured it out.....Iam happy for you....Try Virtuous Unity 2.39 you will really love it.
By the way, where did you get the PD15IMG.zip file???? Can you post the link, so that it will be easy for others with similar problem.
Thanks! You're right, I am trying out Virtuous Unity 2.39 right now and I love it. I was actually looking for an android "bone-stock" gingerbread rom but I can't seem to find one without the customization. Then I bumped into this one. They say sense 3.0 were only made to work on dual-core phones... they were wrong. I really love this rom and I'm sticking to it. Until I find a stock gingerbread rom that has been perfected for the myTouch 4G. You know, the one without the customization.
Oh! Here's the link where I got the radio (PD15IMG.zip) from: www1240.megaupload.com/files/89ce9e2eeb86bb659eceb64baa356c4b/PD15IMG.zip
Since I'm a new member of the xda-developers forum, I couldn't post a link. So, instead, here's the address.
So have you tried the link in my post? Did it work for you?
The link for the PD15IMG.zip radio? Nope. I went onto googling it and finding one myself. The link for the stock myTouch 4G 2.3.4 rom? Nope. Not a big fan of the myTouch 4G's overlay.
OK I'm not new to rooting or xda but I am new to this phone.
I'm not just jumping on here and asking either , I have been searching for the best root method and so far this looks like the best howto I can find.
http://wiki.cyanogenmod.com/wiki/HTC_Glacier:_Full_Update_Guide
I would just like to get a little info from a few people who have rooted this phone.
Also I've been reading about the bad emmc chip and that it may or may not have anything to do with the root method that is used , any thoughts on this would be great.
Any input would be great and or a link to a better guide to root this phone if there is one.
I just like to know as much as possible before I root.
TIA for any help or replies.
Edit: Forgot to mention I'm on 2.3.4 btw.
The guide you linked is the correct answer. Just be sure to follow the section on downgrading to 2.2.1, which is needed to permaroot.
If you're experienced with this stuff it takes about 15-20 minutes (if that) from start to finish.
It's a pretty painless experience.
The one catch you might run into is using ADB to push the update file to the phone. Sometimes it doesn't send the entire file, it leave off like 50 bytes for some oddball reason. So make sure to check the MD5SUMS and the exact file length. Or just avoid that part altogether by copying the file to your SD card in another way before starting the root process.
As for the eMMC chip, I'm convinced it's an overblown problem. If you have the 'bad' one it might break. It might not. I had the bad one and flashed it repeatedly and it never gave me a problem. Then I had the 'good' one and it borked the chip on my first attempt to flash. So while there's a higher probability of the 'bad' one breaking, it's not a guarantee nor is the good one immune. You can check it with a simple script in terminal emulator that's available somewhere in the forum but I forget where.
Skipjacks said:
The guide you linked is the correct answer. Just be sure to follow the section on downgrading to 2.2.1, which is needed to permaroot.
If you're experienced with this stuff it takes about 15-20 minutes (if that) from start to finish.
It's a pretty painless experience.
The one catch you might run into is using ADB to push the update file to the phone. Sometimes it doesn't send the entire file, it leave off like 50 bytes for some oddball reason. So make sure to check the MD5SUMS and the exact file length. Or just avoid that part altogether by copying the file to your SD card in another way before starting the root process.
As for the eMMC chip, I'm convinced it's an overblown problem. If you have the 'bad' one it might break. It might not. I had the bad one and flashed it repeatedly and it never gave me a problem. Then I had the 'good' one and it borked the chip on my first attempt to flash. So while there's a higher probability of the 'bad' one breaking, it's not a guarantee nor is the good one immune. You can check it with a simple script in terminal emulator that's available somewhere in the forum but I forget where.
Click to expand...
Click to collapse
OK so I can just put the update zip on the root of the sd card and just flash that from the bootloader from the phone?
Also is there another recovery for the my touch or is cwm the best one?
Edit: One more thing how often does this root method fail and if it does and the chip goes is the phone bricked ?
Yes, you can just put the file in the root directory of the SD card. That's all ADB does via the terminal on your computer as far as putting the file on your card. (It does a lot more in the overall process)
But no. You cannot just use the bootloader. You have to do steps 1-6 on the Wiki guide you linked first.
So basically....copy the PM15IMG.ZIP file to the root directory of the SD card.
Then do steps 1-6.
Skip step 7 because you've already done it.
Then do steps 8 and on.
And you don't have to do it this way. Sometimes ADB will push the entire PM15IMG file. But if you try to flash the update (downgrade) and it doesn't work, then try copying the PM15IMG in another way.
As for this root method failing, there are a couple ways to brick the phone.
If you pull the battery during the radio update....phone will be VERY bricked. Like won't even power to bootloader kind of bricked. So don't do that.
If the PM15IMG file just doesn't work for some reason, the phone will recognize that the file is bad and basically stop itself from updating. So it's pretty fool proof in terms of getting a corrupt file. Even if it goes through the update process and loads all the way but the phone still doesn't work (gets caught in a boot loop, sticks on the animation screen, has various other problems, etc) you're still good as long as you can get to the bootloader. You can always do a factory reset and start over. Or you can retry the update process and see if it works better the second time.
As for ClockworkMod, I love it. It gives you a lot of options in recovery to fix all or parts or things. It'll let you flash ROMs from the recovery screen so if you louse up a ROM install and can't get the phone to boot you can flash a new ROM from the recovery without having to go through the ADB console on your computer.
That's been helpful more than once. I tried to update a CM ROM. Something went wonky and the phone would just get stuck in the boot animation. So I restarted and went into recovery and reflashed my saved ROM backup and viola! Back to a working phone. That's handy because you can fix major ROM problems when you're away from home far away from your computer.
As fro the chip, if it breaks, the phone is dead. There is no fixing it. I have no idea what the actual odds are. But sometimes you've got to live a little and take your chances.
Enjoy! It's a great phone with a lot of great ROM options.
it's PD151IMG.zip
also, please read my guide here: http://forum.xda-developers.com/showthread.php?t=1388962
and also neidlinger's, posted in my thread.
Thanks guys I'm going to give it a go also I know all about recovery and flashing I just used Amon Ra recovery on my evo over cwm only cause cwm always gave me issues thats why I was wondering if there was something better.
I'll post back how it goes, I'm installing everything from scratch cause I lost my computer so I have to set up the sdk, adb and fastboot all over and now adb doesn't want to work LOL but it always works like that.
First you'll need to downgrade via this guide.
Then once you've done that you can either root via the root.sh method or the gfree method.
Good luck!
Follow macksters advice
Sent from my HTC Glacier using XDA App
Thanks for the ripples I still haven't got the chance to root yet but I did find out that I have the bad emmc chip, now I've never had a phone with one of these things in it and I'm wondering is this thing going to crap out on me?
I'm going to root it either way ad soon as I get the time.
Also I got my son the same phone and his has the bad chip as well what are the chances of that.
"bad" is just a name that people gave it. There might be roughly half of all existing MT4Gs with that chip.
Jack_R1 said:
"bad" is just a name that people gave it. There might be roughly half of all existing MT4Gs with that chip.
Click to expand...
Click to collapse
So its just more likely that those chips are the cause of people bricking their phones or just a couincidence?
Also I'm still not rooted yet and I'm having a few issues with the phone like apps fcing and the touch screen gets a little crazy at times like a ghost is messing with my phone, now is that just the stock ROM or can that be do to the "bad labeled" chip?
"Bad" chip has a bit higher failure rate, which means - statistically, if you take 100 people with "bad" chip and 100 with "good" chip, root their phones, and you'll get 1 total failure (probably less, but it's not number-accurate, just for demonstration) of "good" chip that will fail after rooting, and 2-3 failures of "bad" chip.
Again, chips that are really prone to failure ultimately WILL fail - rooted or not. Rooting just stress-tests them.
Jack_R1 said:
"Bad" chip has a bit higher failure rate, which means - statistically, if you take 100 people with "bad" chip and 100 with "good" chip, root their phones, and you'll get 1 total failure (probably less, but it's not number-accurate, just for demonstration) of "good" chip that will fail after rooting, and 2-3 failures of "bad" chip.
Again, chips that are really prone to failure ultimately WILL fail - rooted or not. Rooting just stress-tests them.
Click to expand...
Click to collapse
Not the process of rooting. It's the stuff you do AFTER rooting, flashing ROMs, themes, mods, radios etc that will speed up the process of the chip dying. This is because when you flash something, big chunks of data get written to the eMMC chip, and if you keep doing it constantly, there is a possibility that the chip will die. This is the reason behind the chips dying, not the actual rooting process, but the stuff that you do AFTER rooting it.
Sent from my HTC Glacier Sense 3.5 using xda premium
saranhai said:
Not the process of rooting. It's the stuff you do AFTER rooting, flashing ROMs, themes, mods, radios etc that will speed up the process of the chip dying. This is because when you flash something, big chunks of data get written to the eMMC chip, and if you keep doing it constantly, there is a possibility that the chip will die. This is the reason behind the chips dying, not the actual rooting process, but the stuff that you do AFTER rooting it.
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
From what I understand, it's the gfree exploit that stresses the eMMC and causes the fail.
But to the OP, what I've noticed is that people with the bad eMMC chip tends to fail rather shortly after they root. Many people that have had bad chips, including myself at one point, had it rooted and was flashing ROM's weekly for months with no issue. I think if it doesn't fail shortly after you root, you should be in the clear. But that's just my speculation.
mackster248 said:
From what I understand, it's the gfree exploit that stresses the eMMC and causes the fail.
Click to expand...
Click to collapse
It was pretty clearly defined, with help by the guy who wrote gfree, how gfee has nothing to do with it.
saranhai said:
Not the process of rooting. It's the stuff you do AFTER rooting, flashing ROMs, themes, mods, radios etc that will speed up the process of the chip dying. This is because when you flash something, big chunks of data get written to the eMMC chip, and if you keep doing it constantly, there is a possibility that the chip will die. This is the reason behind the chips dying, not the actual rooting process, but the stuff that you do AFTER rooting it.
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
Yes, this is correct, of course.
The rooting itself does only one potentially (arguably?) dangerous thing - it power-cycles the eMMC to intercept its initialization and prevent setting the read-only mode. eMMC seem to be sensitive to power-cycling while they're being accessed, some of the eMMC failures of both "good" and "bad" kinds were reported after pulling the battery on a working phone stuck in the middle of writing something. In any case there's nothing to do to avoid this power-cycling, though - any method of root has to include it.
This is sounding worse and worse lol.
I'm going to root no matter what but how does t-mobile insurance work I'm new to t-mobile but I'm paying for the insurance, or would it be possible to get a replacement through the warrant if this chip goes?
You call t mobile and tell them your new phone stopped working. Act like a dunce who doesnt know tghe difference vetween a phone and your butt and they will send you a new one.
Sent from my HTC Glacier using XDA App
Yeah I'm not usually a crook but they shouldn't really sell a phone with a faulty chip in it either.
This chip (the specific eMMC model) exists in at least 3 another phone models - Desire HD, Desire S, T-Mobile G2.
These chips fail in all of the phone models. There is one in my wife's Desire S (of course, rooted).
Their failure rate is VERY low. The problem is that on the forum you won't see the 99.99% of people that it works for them, you'll most probably see the 0.01% that has failures.