I have a problem guys. while i was trying to restore a nandroid backup of cyanogenmod via clockworkmod recovery after trying out Fusion, i noticed that the rom would not go past the mytouch white screen... I wiped data and cache prior to doing so to have no issues but it wouldnt boot. So i boot up in recovery to find this....
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
As far as i know, i never messed with such directory so im puzzled
Can anyone tell me how to get up and running? Because no matter what i try to flash, it seems like something goes wrong since it wont go past the white screen
thnx
Lots of threads about this in the Q&A section. A few have been able to come back from it. This has been happening so much that I almost don't want to flash anything...
EDIT: http://forum.xda-developers.com/showthread.php?t=1071881
Hope that helps and please keep us updated.
lowandbehold said:
Lots of threads about this in the Q&A section. A few have been able to come back from it. This has been happening so much that I almost don't want to flash anything...
Click to expand...
Click to collapse
I flash ROMs frequently. Not to i say i'm immune to it. But i think alot of it might be tracking back from trying to use the "flash option" in the application.
And it must be something the end user is doing. You've never seen a developer have these problems. And if they did i'm sure they'd post their fix.
just my 2 cents
mike21pr said:
I have a problem guys. while i was trying to restore a nandroid backup of cyanogenmod via clockworkmod recovery after trying out Fusion, i noticed that the rom would not go past the mytouch white screen... I wiped data and cache prior to doing so to have no issues but it wouldnt boot. So i boot up in recovery to find this....
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
As far as i know, i never messed with such directory so im puzzled
Can anyone tell me how to get up and running? Because no matter what i try to flash, it seems like something goes wrong since it wont go past the white screen
thnx
Click to expand...
Click to collapse
Were u using recovery 3.0.2.4,3.0.0.6 or 3.0.0.5? Did u try formatting system via recovery before flashin the bckup?
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
I agree that it probably has to do with user error as well...I would just feel much better about it if we could figure out what causes it. I haven't followed the threads closely, but with the engineering bootloader is there a known fix?
neidlinger said:
I flash ROMs frequently. Not to i say i'm immune to it. But i think alot of it might be tracking back from trying to use the "flash option" in the application.
And it must be something the end user is doing. You've never seen a developer have these problems. And if they did i'm sure they'd post their fix.
just my 2 cents
Click to expand...
Click to collapse
I belive that also cause it happened to me while tryin to flash cm7 via the app & never recovered,learned frm my mistake tho lol
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
lowandbehold said:
I agree that it probably has to do with user error as well...I would just feel much better about it if we could figure out what causes it. I haven't followed the threads closely, but with the engineering bootloader is there a known fix?
Click to expand...
Click to collapse
Its a yes & no...people have recovered & others havent,so theres really not a way to tell what causes this & why some phones recover & others dnt
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
i had 3.0.2.4 version.
im gonna check out the link to see if i can fix it. thanx guys.
ill keep u posted
something is not right.... im flashing the zip and get this in the progress...
Parsing... [SD ZIP]
[1] BOOTLOADER -FAIL-PU
[2] BOOT -FAIL-PU
[3] RECOVERY -FAIL-PU
[4] SYSTEM -FAIL-PU
[5] USERDATA -FAIL-PU
[6] SPLASH -FAIL-PU
[7] TP
[8] TP -BYPASSED
[9] RADIO_v2 -UPDATING
[10] RADIO_CUST
its not done yet, but wanted to know if its normal to have the fail results, because its beginning to worry me
Do you have the engineering bootloader?
lowandbehold said:
Do you have the engineering bootloader?
Click to expand...
Click to collapse
i dont think so. I has root s-off using gfree methid
mike21pr said:
i dont think so. I has root s-off using gfree methid
Click to expand...
Click to collapse
boot into hBoot and see if you have the .85 screen or the .86 screen.
neidlinger said:
boot into hBoot and see if you have the .85 screen or the .86 screen.
Click to expand...
Click to collapse
.86
10 char
no bueno...
lowandbehold said:
no bueno...
Click to expand...
Click to collapse
so, this means im boned?
mike21pr said:
so, this means im boned?
Click to expand...
Click to collapse
I wouldn't say "boned". it just means the [solved] problems using the Engineering screen will not help since you do not have it.
Have you tried running the PD15IMG to restore back to 100% stock?
neidlinger said:
I wouldn't say "boned". it just means the [solved] problems using the Engineering screen will not help since you do not have it.
Have you tried running the PD15IMG to restore back to 100% stock?
Click to expand...
Click to collapse
yes. and it gives me the FAIL-PU after most steps
God dame, like someone else said, I'm getting scared flashing my phone too now. FAIL-PU, a lot of people have been getting those, and it seems to be the ones with the GFree method without the eng hboot. I remember another member saying that it's done and you have to get a warranty exchange as the motherboard needs to be replaced.
Don't quote me on anything I said above but that's what I think.
xdviper said:
God dame, like someone else said, I'm getting scared flashing my phone too now. FAIL-PU, a lot of people have been getting those, and it seems to be the ones with the GFree method without the eng hboot. I remember another member saying that it's done and you have to get a warranty exchange as the motherboard needs to be replaced.
Don't quote me on anything I said above but that's what I think.
Click to expand...
Click to collapse
Yea i saw that too... oh well, ill sell it as-is cheap to get me another phone or get a replacement. i guess i have made my peace with it lol. thanks for the help guys
keep me posted if anyone finds anything out
No, don't just give up yet. Did you try connecting it to your computer and wiping the whole phone via ADB? Try that, but I really don't know if it'll work with the stock bootloader or not and then try flashing PD151 image again.
Related
Can somebody tell me how to root a my touch 4g ? I'm kinda new at this and want to learn.
chitopr said:
Can somebody tell me how to root a my touch 4g ? I'm kinda new at this and want to learn.
Click to expand...
Click to collapse
Google VISIONary (r14) place it on your device, install it then run it. Temproot is for temporary rooting your device, its gone after a reboot, permaroot is for good, unless you use the unroot option.
Its safe, fast and easy. I use temproot option so I can use some root only apps. This is the first device I have felt no need to add a custom rom to or anything so VISIONary was the choice for me. If you want the long harder way directions can be provided. I do recommand you learn the long hard way at some point, its good to know your way around just in case.
chitopr said:
Can somebody tell me how to root a my touch 4g ? I'm kinda new at this and want to learn.
Click to expand...
Click to collapse
first of all rooting is not for everyone. I can name a few people in a few forums that do not run a rooted phone for one reason or another. Rooting your phone gives you possibilities that are not even considered when you are in a stock form. But on the other hand you can seriously damage your phone, with the possibility of it ending up a 500.00 paper weight.
The safest and easiest thing to do is download VISIONary.apk and just use temp root. That will give you the ability to do everything you need to do in a root status w/o risking FUBARing anything. You can wi-fi tether, run Titanium Backup and stuff like that.
If you are wanting to go full blown and root it w/ s=off and do the
you can do it the real way and follow Cyanogen's method
Or you can do via the TheUnlockr for a simpler way.
If I temp-root it, would I have to temp-root it every time I want to run the wifi-tether program? Or just on installation?
http://forum.xda-developers.com/showthread.php?t=858996
I have been trying to get visionary r14 but i have no idea where to get it. I google visionary r14 and use the first link like many people have said but whenever i click download it says firefox can't find the page. Does anyone know of some other way to get visionary ?
Nickoro said:
I have been trying to get visionary r14 but i have no idea where to get it. I google visionary r14 and use the first link like many people have said but whenever i click download it says firefox can't find the page. Does anyone know of some other way to get visionary ?
Click to expand...
Click to collapse
There is a link in the post 4 above this one.
does anyone know if this method will work on a htc glacier thats flashed to a network other then t-mobile.
http://forum.xda-developers.com/showthread.php?t=858996
its my friends phone and he is on simple mobile. i have rooted quite a few phones and know what i am doing but wanted to make sure it wouldn't conflict with his network
mdrentz said:
does anyone know if this method will work on a htc glacier thats flashed to a network other then t-mobile.
http://forum.xda-developers.com/showthread.php?t=858996
its my friends phone and he is on simple mobile. i have rooted quite a few phones and know what i am doing but wanted to make sure it wouldn't conflict with his network
Click to expand...
Click to collapse
Any rooting method will work on any phone it was designed for.
Hi guys, I just follwed the method by the unlocker... but at the end when I go to better terminal I'm not getting the # sign... So I recon that it didn't work, right? What might the problem be?
My bad, wasn't writing SU... OPPSSS!!!
I think I screwed something. I just noticed that my CW version is 3.0.2.4 and everybody I see is talking about 3.0.0.5. Is this something bad? I'm having trouble flahing gapps and I got another strange problem, If I put a ringtone and reboot the phone it reverts to the original one, and if I copy something to the SD card it gets deleted. Strange? Please can anyone tell me if I screwed this and how can I resolve?
mindwarp1571 said:
I think I screwed something. I just noticed that my CW version is 3.0.2.4 and everybody I see is talking about 3.0.0.5. Is this something bad? I'm having trouble flahing gapps and I got another strange problem, If I put a ringtone and reboot the phone it reverts to the original one, and if I copy something to the SD card it gets deleted. Strange? Please can anyone tell me if I screwed this and how can I resolve?
Click to expand...
Click to collapse
3.0.0.5 is the older one. 3.0.2.4 is the newer one.
What error are you getting when you flashed the g/apps?
how the eff is stuff getting deleted from the SDcard. the recovery image doesn't natively delete anything from the SDcard.
neidlinger said:
3.0.0.5 is the older one. 3.0.2.4 is the newer one.
What error are you getting when you flashed the g/apps?
how the eff is stuff getting deleted from the SDcard. the recovery image doesn't natively delete anything from the SDcard.
Click to expand...
Click to collapse
I don't really know, this is a new 32 gig class 6 sandisk memory, the original 8gigs is out ot the phone. I left last night transfering from my pc 20 gigs of music and today after i disconnected it from the pc it was gone.
I'm testing the ringtones to determine what the heck is going on, more on that later....
Gapps... starts to install and...
finding update package...
opening update package...
e:cant open /sdcard/gapps-gb-20110307-signed.zip
(bad)
Installation aborted
This is the 4th time I download this... Maybe permissions?
mindwarp1571 said:
Gapps... starts to install and...
finding update package...
opening update package...
e:cant open /sdcard/gapps-gb-20110307-signed.zip
(bad)
Installation aborted
This is the 4th time I download this... Maybe permissions?
Click to expand...
Click to collapse
Their has to be something wrong with (a) the recovery image or (b) the g/apps.
Are you sure you are downloading the correct g/apps for our phone running CM7. They have their own g/apps....If you are 100% sure it's for our phone then i'd suggest .....
... is attempting to manually flash the recovery image to make sure you do not get a blip in the system. Personally, i do not trust flashing recovery images with Clockwork ROM manager. I've seen a-lot of errors come out of it. This might be one of them.
Have you tryed the 8gig sdcard to install the g-apps? the 32gig may be bad
I just removed the sd card and put it on my laptop and copied a folder with music... after taht turned on the phone and it is gone! strange!
Gonna test the 8gigs..
Put the 8 gigs, and it installed... Hmmm...
NOw, after it finishes the setup of the apps I will format the 32 and test it...
Every time I try to download the Visionary.apk from the above posts, it downloads, then tells me the file has a virus... what's going on? Are they false positives?
_Allan_ said:
Every time I try to download the Visionary.apk from the above posts, it downloads, then tells me the file has a virus... what's going on? Are they false positives?
Click to expand...
Click to collapse
Its false so don't worry about it and go with VISIONary+
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?
I need some help with this one.
I received a Mytouch 4g and have the following errors:
It will not boot past the Mytouch 4g logo screen. However; I can boot into Hboot and recovery just fine.
It is running CWM 3.0.2.4 which is supposed to be a 2.3 recovery. Whenever entering recovery or moving around and trying to flash something it says the following:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
The radio is 26.03.02.26_M which is supposed to be a 2.2 radio.
I have tried to flash the 2.3 radios but they all seem to freeze up at the very end. I have let them sit for 15+ minutes.
I have tried to flash a 2.3 rom and receive an error when flashing it. Also, I cannot format system under recovery, I receive an error saying: Error formatting /system! (Helpful I know)
I have also tried factory resets to no avail. I am currently going to try to get back down to a 2.2 recovery and go from there.
Please help as it is greatly needed and appreciated!
Mickyyy said:
I need some help with this one.
I received a Mytouch 4g and have the following errors:
It will not boot past the Mytouch 4g logo screen. However; I can boot into Hboot and recovery just fine.
It is running CWM 3.0.2.4 which is supposed to be a 2.3 recovery. Whenever entering recovery or moving around and trying to flash something it says the following:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
The radio is 26.03.02.26_M which is supposed to be a 2.2 radio.
I have tried to flash the 2.3 radios but they all seem to freeze up at the very end. I have let them sit for 15+ minutes.
I have tried to flash a 2.3 rom and receive an error when flashing it. Also, I cannot format system under recovery, I receive an error saying: Error formatting /system! (Helpful I know)
I have also tried factory resets to no avail. I am currently going to try to get back down to a 2.2 recovery and go from there.
Please help as it is greatly needed and appreciated!
Click to expand...
Click to collapse
all those cache errors definitely mean you have a bricked phone, with a bad emmc chip likely being the problem. currently, there isnt a way to recover from this brick
aznprodgy said:
all those cache errors definitely mean you have a bricked phone, with a bad emmc chip likely being the problem. currently, there isnt a way to recover from this brick
Click to expand...
Click to collapse
Ouch. Is there absolutely no possibility of anything? I'd be content with a stock rom at this point... If it's already bricked I could be a test dummy for anything risky that might work.
Mickyyy said:
Ouch. Is there absolutely no possibility of anything? I'd be content with a stock rom at this point... If it's already bricked I could be a test dummy for anything risky that might work.
Click to expand...
Click to collapse
not that I know of, I havent heard of anyone recovering their bricked phone with the bad emmc
Answered my own question. Any other ideas feel free to post away :/
HEY guys i saw the title and thought it should be appropriate to post here, sorry if i deviate from the original question but I recently flashed 2 Mytouch 4Gs and everything worked out great i used the instructions provided by grankin01 for true perm root using gfree method through adb with visionary for perm root unlock etc etc but i didnt flash the engineering bootloader as far as i know not really sure I flashed cm7 on both devices now one of the phones has given me trouble the other is still working.
The issue is that the defective phone worked for about 2 weeks, the owner said she accidentally let the phone use all battery and die, and after that the phone would get stuck at the cm7 boot animation. I rebooted into recovery just fine and reflashed the rom. That got it working for several minutes. Then it started crashing randomly and kept freexing at boot animation, i tried a cm7 kernal and that didnt work either so i flashed virtious unity sense 3.0 rom. That seemed to work but it was freezing when i tried to install certain games well long story shorter i finally ran fix permissions for apps from rom manager and that seemed to fix problem, the phone stabilized and actually worked flawlessly after so i gave it back.
The phone worked for about another week, owner tells me that she was trying to install games (8 at a time ) and the phone was not working, so she tried reboot and the phone wouldn't reboot at all in fact it dosent even go into recovery light up or show any signs of life except when i plug it in to my computer asks for this driver QHSUSB_DLOAD so i guess its not completely dead but adb does not recognize it with adb devices command but i am totally stuck dont know what to do please help and sorry for the huuuge post!
Read the Glacier Wiki, Troubleshooting guide. Link in my signature.
It'll answer the OP.
It would be wise to look for it before posting.
For the second answer - if the phone doesn't start booting, there's nothing you can do.
Yup +1 on the brick with the bad emmc chip, classic symptoms...
I sent this...
Yup guess so. I've been trying to at a minimum get the stock recovery back on but that seems impossible at this point. Can't flash from adb or even wipe/flash from fastboot.
Argh
Okay so apparently it is going back to HTC for repair.
My problem is that now I cannot seem to get CWM off of it or anything. I tried flashing the PD15IMG to stock but receive the fail-pu. I tried with ADB but had an error. Fastboot gave me an error as well.
Are there any recommendations? I would just send it like it is since it wasn't the rooting or flashing but a manufacture defect on the emmc it seems, but I am afraid they would reject and charge me to repair. Even if I declined, there would be a $35 fee for their hassle.
I would like to have it out the door tomorrow morning if possible, so please instruct me on any possibilities. I thank you all in advance.
There's nothing you can do besides trying to brick it completely - loading PD15IMG and pulling the battery while radio update is in progress.
or fry the thing and make it unbootable lol
aznprodgy said:
or fry the thing and make it unbootable lol
Click to expand...
Click to collapse
How would go about doing that? I can't seem to make it fully bricked by pulling while flashing a radio :/
aznprodgy said:
I had a spare charging USB cable so I just cut the end off of it. CAREFULLY took the phone apart and touched the hot wire to the motherboard, but only for a short amount of time. I wouldnt really recommend this, as you could electrocute yourself if not done properly or you could cause damage to the phone possibly making it unreturnable. but hey, times get hard sometimes...**not responsible for any damage done to you or your phone, should be done at YOUR OWN risk**
Click to expand...
Click to collapse
from another thread-----^^
Hey Everybuddy,
I have a mt4g that has been sitting for a while, because I think its semi bricked and everytthing that I tried to do to fix it wasnt helping untill a friend told me about this forum, I read around and you guys seem pretty good and helpful
My phone wont boot up and its stuck on the t-mobile screen, Im able to access CWM. fastboot and hboot, I tried flashing pd15img true sd card and it just hangs in there till the phone battery dies and it says update in progress...
an other issue is that when im in CWM I keept getting these errors
E: Can't mount /cache/recovery/commad
E: Can't mount /cache/recovery/log
E: Can't open /Cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Glacier PVT ENG S-off
HBOOT-0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.08.04.30_M3
eMMC-boot
Oct 11 2010, 12:44:14
Please guys any help would be much appreciated, I love this phone and I cant stand not using it, please ive beed up everynight for the past 3 days tryin to find a fix
I'm tired.
http://forum.xda-developers.com/showthread.php?t=1394238
Jack_R1 said:
I'm tired.
http://forum.xda-developers.com/showthread.php?t=1394238
Click to expand...
Click to collapse
I trieed all that PD15IMG doesnt update it gets stuck at update in progress ...
If you can get to cwm just flash another rom
--sent from my glacier.
it's a full brick. If its stuck in Update in progress for more than in 10, 15 minutes then you have a dead eMMc Chip. Sorry bro.
rockstarar said:
If you can get to cwm just flash another rom
--sent from my glacier.
Click to expand...
Click to collapse
I tried 3 different roms and when I try to start the phone it just stays at the tmo screen.
alfadog77 said:
it's a full brick. If its stuck in Update in progress for more than in 10, 15 minutes then you have a dead eMMc Chip. Sorry bro.
Click to expand...
Click to collapse
oh i hope not
rockstarar said:
If you can get to cwm just flash another rom
--sent from my glacier.
Click to expand...
Click to collapse
I tried 3 different roms and when I try to start the phone it just stays at the tmo screen.
alfadog77 said:
it's a full brick. If its stuck in Update in progress for more than in 10, 15 minutes then you have a dead eMMc Chip. Sorry bro.
Click to expand...
Click to collapse
oh i hope not
He's right. Sorry bro
--sent from my glacier.
rockstarar said:
He's right. Sorry bro
--sent from my glacier.
Click to expand...
Click to collapse
Im pretty sure its not a brick
its not a full brick and it aint fried for the fact that i have many phones that i root and all that but i do now have a mytouch 4g and it have your exact issue... here's what i did but it wont fix
i used a button combo of just pushing power and volume up and letting go of power and tapping it...
it might not work but i was able lots of times to go in and use the phone but the minute i pluged my charger in it would shut off
with that i did it again plugged in long process but was able to charge and use the phone again
If you don't understand what you're writing, you would be better of reading.
There are 2 or 3 sticky guides that the OP failed to read and/or understand, that are written to deal with this situation.
Read them.