i got a rooted mytouch 4g with clockwork 3.0.2.4 and miui rom and everything was fine till today it just froze on me and i toke the battery out to restart and i just stayed on the my touch 4g screen so i toke the bat out and went into recovery and its giving me this error
E:cant mount /cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
i tried wipe data/factory settings and reinstalling the rom and it still says that and i still get stuck on the my touch 4g screen
i also tried to restore and still getting that and getting stuck in the my touch 4g screen
does anyone know how i can fix this
what do i need to do
thank you
There dozens of threads on this issue now. Do a little search and you'll find a lot of information on the problem. I'm sorry to say, but it sounds like you have a bad eMMC and it's essentially bricked.
thanks for the reply im a noob when it comes to this but i followed all the steps in rooting and installing roms everything was working fine for a good 3months i used to have cm7 and then switched to miui and had that ever since
so im pretty much screwed lol
i googled and i cant find nothing on how to fix :-/
drocha86 said:
thanks for the reply im a noob when it comes to this but i followed all the steps in rooting and installing roms everything was working fine for a good 3months i used to have cm7 and then switched to miui and had that ever since
so im pretty much screwed lol
i googled and i cant find nothing on how to fix :-/
Click to expand...
Click to collapse
Unfortunately nobody has been able to fix this yet. You could attempt to exchange it at t-mobile.
well now i think i got a full brink i tried doing the pd15img.zip trick and the only thing that turns on is the orange led wtf lol
if i send it back will they know that i rooted it can i just say i dont know what happend lol ??
Related
I was running CM7.0.3 and had flashed on a different kernel. It started to run stably for a few days and then started locking up. I had it over clocked to 1.7ghz using setcpu. I decided to use Kernel Manager to put the original CM kernel back on. After it did it I got stuck in a boot loop so I went in to recovery and tried to restore the backup I had from a couple weeks before. It goes through it until it gets to /system and says cant mount /system status 1. I did a little searching and tried using PD15IMG. When I click update everything it goes through says FAIL-PU until it gets to Radio and then just sits there saying updating and never goes any farther. Can I fix this or is my phone ruined? Thanks for any help.
gamershadow said:
I was running CM7.0.3 and had flashed on a different kernel. It started to run stably for a few days and then started locking up. I had it over clocked to 1.7ghz using setcpu. I decided to use Kernel Manager to put the original CM kernel back on. After it did it I got stuck in a boot loop so I went in to recovery and tried to restore the backup I had from a couple weeks before. It goes through it until it gets to /system and says cant mount /system status 1. I did a little searching and tried using PD15IMG. When I click update everything it goes through says FAIL-PU until it gets to Radio and then just sits there saying updating and never goes any farther. Can I fix this or is my phone ruined? Thanks for any help.
Click to expand...
Click to collapse
This issue has cropped up a lot recently. I'm sorry to say it but you might have bricked it. There is a chance though. 2 questions:
1. did you use gfree to root?
2. do you have the engineering Hboot? (.85.2007?)
I did use gfree to root. and i dont have the engineering Hboot.
gamershadow said:
I did use gfree to root. and i dont have the engineering Hboot.
Click to expand...
Click to collapse
Unfortunatly at this time there is no way to fix your situation with out an eng spl. So I hate to be the bearer of bad news but the phone is done.
Sent from my Faux powered Glacier
mark manning said:
Unfortunatly at this time there is no way to fix your situation with out an eng spl. So I hate to be the bearer of bad news but the phone is done.
Sent from my Faux powered Glacier
Click to expand...
Click to collapse
Thanks even if it is bad news. I've only had the phone 10 days. Think tmo would exchange it?
gamershadow said:
Thanks even if it is bad news. I've only had the phone 10 days. Think tmo would exchange it?
Click to expand...
Click to collapse
Ya you shouldn't have a prob
Yeah, they should give you a brand new in the box, depending on which state you're in, you have either 14 days or 30 to return the phone
Sent from my HTC Glacier using XDA App
I'm stuck as well.
Don't know WTF happened. Was running Iced Glacier for a couple of months, then decided to try one of the new ROMs, so took CM7 for a spin, then went to RoyalGinger for a day or two. Things were working, but RG started freezing up, etc. so tried going back to CM7. Once I started through the flash process I hit an error when trying to format /system.
Now when I even attempt a wipe (or most anything) via CWM I continuously get errors like:
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
...and this latest time, I now got this as well:
E:\Can't mount /cache/recovery/command
I had CWM 3.0.2.4 through all of this, so should be able to flash 2.2 and 2.3 ROMs, as I understand. I can only get into CWMR and HBOOT.
I used gfree to root & have engineering HBOOT (.85.2007).
I can't get device listed in ADB, but can under fastboot. Tried flash command using fastboot to try and re-flash CWM (no idea if it would do any good), but it says cannot open the .img file.
The ONLY thing I got to work was mounting SD to USB in CWM and putting PD15IMG.zip in the root of the SD card, then rebooting and letting it run an auto update as it looks for this by default. That worked and took me back to stock...nothing else I tried would work.
Now I'm afraid of doing anything else or risk creating an expensive @ss paperweight.
Any help or suggestions appreciated as to HOW this happened, and next steps.
I was using my mytouch 4g rooted and everything running the virtuous fusion rom when it shut off. When I tried to reboot the phone but it just went to the mytouch 4g screen and froze. I took the battery out and tried again several times but the same result was the phone being stuck at the mytouch 4g logo. I can get into the recovery but when I try to boot the rom up again it just says installation aborted. I also tried to run another rom (RoyalGinger) but it still froze at the mytouch 4g logo. I am very nervous, is my phone bricked?
Thank you for any answers possible,
Justin
Are you getting cache errors in recovery? Try wiping the cache partition for example, and see if that completes successfully. If you get the typical cache errors, that means your eMMC has failed and unfortunately the phone is indeed bricked.
Post your bootloader info please, that might help solve this
Sent from my Acer Iconia Tab A500 using XDA Premium App
GLACIER PVT ENG S-OFF
HBOOT- 0.85.2007 - (PD1510000)
MICROP-0429
RADIO-26.09.04.26_M
eMMC-boot
Lol so who is having the problem mohammed? You or holiday? Need to know what's going on with you phone?
Sent from my Acer Iconia Tab A500 using XDA Premium App
I have the same problem with the phone.
mohamed_moscow said:
I have the same problem with the phone.
Click to expand...
Click to collapse
TeeJay3800 said:
Are you getting cache errors in recovery? Try wiping the cache partition for example, and see if that completes successfully. If you get the typical cache errors, that means your eMMC has failed and unfortunately the phone is indeed bricked.
Click to expand...
Click to collapse
Cache errors?
I too am having cache errors....any solution to fix the issue? I cant flash anything, but I can get into fastboot just fine.
Teejay - question for you since I have read alot of your posts concerning cache errors....in mohammeds case, since he does have the engineering bootloader, cant he use fastboot to flash the stock pd15img.zip and get rid of cache errors? As long as he does not have fail pu? I believe I read of members successfully doing that in the emmc thread....It seems logical to be able to do that, reroot, and reflash cwm recovery but i could be wrong...
Sent from my Acer Iconia Tab A500 using XDA Premium App
bochocinco23 said:
Teejay - question for you since I have read alot of your posts concerning cache errors....in mohammeds case, since he does have the engineering bootloader, cant he use fastboot to flash the stock pd15img.zip and get rid of cache errors? As long as he does not have fail pu? I believe I read of members successfully doing that in the emmc thread....It seems logical to be able to do that, reroot, and reflash cwm recovery but i could be wrong...
Click to expand...
Click to collapse
That's the only solution, but unfortunately in most cases it has not worked. Sometimes they get the "Fail-PU" error when flashing PD15IMG, and sometimes even though it seems to flash successfully, the phone still bootloops and produces cache errors in recovery. I think I've read only one or two accounts of the phone becoming usable again once those cache errors appear in recovery. However, I've read probably a dozen or more accounts of nothing working.
I have PU-failed
mohamed_moscow said:
I have PU-failed
Click to expand...
Click to collapse
Yeah sorry man, but there's no hope at that point.
I am having the same issue. I loaded Beast Version 4 on mine. It was working fine and then it froze. I pulled the battery put it back in powered it on and it booted to the loading screen for the ROM (Green Android guy) I then pulled the battery again. Booted and it froze at the MT4G screen. So I botted into the Hboot. I run the wipe data/factory reset, wipe cache partition. Which both say success (Data Wife Complete,Cache Wipe Complete) and then its like it is trying to run recovery but it says:
E:Can't mount /cache/recovery/log
E: Can't Open /cache/recovery/log
E: Cant mount /cache/recovery/last_log
E: Can't Open /cache/recovery/last_log
Is this the cache errors you were talking about? Also when I tried to re-inatll the ROM it gives me an error but when I try re-loading Royal Ginger it loads it fine no errors.. Until I try to go back to previous screen to reboot then I get the error as seen above. I reboot and then it stops again at the MT4G splash screen. Am I bricked.. or is there fix for this. And if so is it the one listed above or is my issue slightly different.
Please help - Crossed Fingers.
I'm sorry, I know it sucks, but the phone is bricked. You can try restoring back to stock using this thread. Rename that file to PD15IMG.zip, put it in the root of your SD, and boot into the bootloader. If the file flashes successfully, there might be hope, but if you get the Fail-PU error, then it's definitely done.
OK thank you for your help. Crossing fingers but betting I am finicio :-(
I am very sorry to be bothersome. I clicked the link and it took me to a place to download the file (File Factory), but the file to download isnt there. Has it been move and by chance will you post the link to it. Again I am sorry.
I'm fairly sure that the file in this thread is the same file, and appears to be still available for download. Give that one a try.
Thank you again I am downloading now. Also it is highly appreciative how quickly you have responded. Again thank you so much.
tommyz182 said:
Thank you again I am downloading now. Also it is highly appreciative how quickly you have responded. Again thank you so much.
Click to expand...
Click to collapse
Sure thing, I hope it works for you. If not and you have T-Mobile insurance, most people have had no problem exchanging their phones for a new one when this happens. Also, don't forget to hit the thanks button if I've been helpful.
Yeah did any of you use the Gfree method of rooting? Because that's the one
I used.
I've had my wife's Samsung Fascinate rooted from the beginning and running various roms. I recently went to CM7. Everything worked fine until I tried to update the kernel. The phone would not but past the opening screen, No problem I had some backups. Unfortunately now when I try to do anything in CWM I get the following errors.
ClockworkMod Recovery v4.0.1.0
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
Essentially at this point CWM is useless. I've tried to restore using Odin but Odin will not install anything. I have used Odin in the past to recover this phone with no problem.
Any thoughts?
You cant reboot using the hardware buttons in cm7, you need to hold the power button, select reboot, and select recovery for it to work.
Sent from my MIUI SCH-i500
Problem is I can't even get into cm7 anymore.
Well I've got most of my problem solved. I just need a kernel that is compatible with cyanogenmod 7. Anyone have any recommendations.
schnyd said:
Well I've got most of my problem solved. I just need a kernel that is compatible with cyanogenmod 7. Anyone have any recommendations.
Click to expand...
Click to collapse
Glitch kernel is by far the best kernel I've ever used, IMO. Compatable with cm7 and MIUI.
Sent from my SCH-I500 using XDA App
tripacer99 said:
Glitch kernel is by far the best kernel I've ever used, IMO. Compatable with cm7 and MIUI.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I tried glitch kernel and the phone wouldn't boot using it. Any particular version I should check out.
There have been some problems with the Glitch Kernel and the newest Cyanogen nightlies causing it to Bootloop. The Glitch developer is aware and working on it. I had to revert back to stock and start over. For now im staying at CM7 nightly 35 and using Glitch.
schnyd said:
Well I've got most of my problem solved. I just need a kernel that is compatible with cyanogenmod 7. Anyone have any recommendations.
Click to expand...
Click to collapse
I am having exactly the same problem as you had, though I got my problem from flashing a custom rom. I am on a Desire S with ClockworkMod 5, how were you able to fix it?
Hey guys my MyTouch 4g froze while updating flash lastnight
I was runnung the stock deodexd bloatware removed updated rom that is in
the dev section (Icannot remember who it belongs to)
I rebooted the phone and it frove on the splash screen
I rebooted into the bootloader
It wont let me do a factory wipe, and 4ext touch will not finish
installing any of the 4 backups I have on the sd card
I was finally able to flash CWM Recovery 2.5.0.7 but cannot get anywhere
To top it off my phone will not connect to my computer so I can
use adb. All I can do is place files on the sd card and try to push them from recovery
When I boot into recovery I get the following error
booting into safemode...
please format all partitions
after 7 minutes it says
E:Cant open /cashe/recovery/log
E:Cant open /cashe/recovery/log
E:Cant open /cashe/recovery/last_log
E:Cant open /cashe/recovery/last_log
cannot mount system, sdext, sd card, or MISC
can't mount /dev/block/mmcblk0 or mmcblk0p1
Would someone mind helping me out. I also tried to flash the
PD15IMG.IMG...nothing.I dont know if the partitions are jacked or what
S-OFF
HBOOT-0.85.2007
emmc-samsung 2151mb
rooted
Hi,
I guess in your frustrated mood, like many before you, you also need a dedicated, special confirmation that you're not an exception to the rule, and just reading "if this and that - your phone is screwed" doesn't work for you. So I'll honor your feelings by writing it 10000th time again.
Look at Glacier Wiki, section "Troubleshooting". Or at the topmost sticky in General section. Or in Q&A. Or search for any part of the error message you're getting. You'll receive the same reply:
If you flash PD15IMG and it either doesn't complete or shows you Fail-PU on one of the partitions - YOUR PHONE IS DEAD, AND THERE IS NO WAY BACK.
Have you tried wiping dalvik and cache and rebooting recovery? Make sure you unmount cache also. My phone did this before too, and that's what I did to fix.
Sent from my HTC Glacier using xda premium
did you even read before posting?
if you did, you would've found this...
http://forum.xda-developers.com/showthread.php?t=1394238
saranhai said:
did you even read before posting?
if you did, you would've found this...
http://forum.xda-developers.com/showthread.php?t=1394238
Click to expand...
Click to collapse
Yes, yes I did along with a lot of other posts re the same topic.
BTW your link for the PD15IMG.zip is dead due to our wonderful government
and must I refer you to your post about you being mean to others ;p j/k
If I could get my phone to connect to my computer I could use adb no problem. But something with the driver is stopping it from connecting.
Ok thanks to PCLiteratesJax I was able to dl a good PD15IMG.zip. Phone is now stock and running good
Hiya,
So I just rooted my Nook Color (1.4.3) for the first time yesterday, it went great. I followed this guys guide: youtube /watch?v=7cP27ABgGjE and I got it rooted (Thanks btw). However, I got greedy and I kerfuffled my Nook color. I wanted android 4.0 on me Nook and so I followed this guys guide: youtube /watch?v=Tl_bKxhPbeo&feature=relmfu . Long story short, I installed CM9 alpha 0.05 zip with CMR. It installed fine (or so I thought) and rebooted.
Upon doing so, I rebooted and now I can't get past the grey Nook color "n" logo. Everytime I reset I can't get past that logo. When I run the CWR off the sd card (I used 1gb_clockwork-3.2.0.1-eyeballer, btw), I get 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
Any time I try to format the cache or data or anything from the "mount and storage" option, it just gives me an error. The only thing that doesn't give me any error is i mount/unmount the boot. When I go back (press power) I get the same string of errors.
I've looked around the net looking for a solution to no avail. I've tried the 8x boot fail thing and when I get to the installer, it fails...Much like me
Am I doing something wrong here? I'll be honest, I understand less then half of what people talk about on these boards, but I know enough that I'm not completely new at this either (Ah, old age). I need help, I'm frustrated... and cold... and a little hungry. I need any help, any at all on how to get my nook working again. Even if you tell me I own a fancy door stopper now, I just need something... something.
angelstark said:
Hiya,
So I just rooted my Nook Color (1.4.3) for the first time yesterday, it went great. I followed this guys guide: youtube /watch?v=7cP27ABgGjE and I got it rooted (Thanks btw). However, I got greedy and I kerfuffled my Nook color. I wanted android 4.0 on me Nook and so I followed this guys guide: youtube /watch?v=Tl_bKxhPbeo&feature=relmfu . Long story short, I installed CM9 alpha 0.05 zip with CMR. It installed fine (or so I thought) and rebooted.
Upon doing so, I rebooted and now I can't get past the grey Nook color "n" logo. Everytime I reset I can't get past that logo. When I run the CWR off the sd card (I used 1gb_clockwork-3.2.0.1-eyeballer, btw), I get 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
Any time I try to format the cache or data or anything from the "mount and storage" option, it just gives me an error. The only thing that doesn't give me any error is i mount/unmount the boot. When I go back (press power) I get the same string of errors.
I've looked around the net looking for a solution to no avail. I've tried the 8x boot fail thing and when I get to the installer, it fails...Much like me
Am I doing something wrong here? I'll be honest, I understand less then half of what people talk about on these boards, but I know enough that I'm not completely new at this either (Ah, old age). I need help, I'm frustrated... and cold... and a little hungry. I need any help, any at all on how to get my nook working again. Even if you tell me I own a fancy door stopper now, I just need something... something.
Click to expand...
Click to collapse
The problem is that rom was for the Nook Tablet, not the Nook Color. So it really should not have installed. It has checks in it to make sure it does not install to the wrong device. Are you sure your device is a Nook Color? The Nook Tablet has a silver bezel and the Nook Color has a black one.
Yea, It's the Nook color. I bought it when I first came out. I actrually tried istalling it twice. The first time it didn't install and gave me an error (can't remember what it was), So I tried it again and it installed with no prob.
Sorry, didn't see that you had alread confirmed it was a NC.
angelstark said:
Yea, It's the Nook color. I bought it when I first came out. I actrually tried istalling it twice. The first time it didn't install and gave me an error (can't remember what it was), So I tried it again and it installed with no prob.
Click to expand...
Click to collapse
Well, you really messed it up if you installed that Nook Tablet rom on your color. I'm not sure how to get it fixed. It puts all the wrong stuff on the wrong partitions. You will probably have to search for how to repartition it and try to re-install stock. Try looking here:
http://forum.xda-developers.com/showthread.php?p=27902129
You might be able to just forget about emmc and install cm to SD and use it that way. But even with SD it tries to verify you have a nook color and you may have messed up emmc so much that it cannot verify it.
Sent from my NookColor using Tapatalk
I had the same thought. I tried it off the sd card but once the little penguin pops up and the code runs it stops and gives me an error and asks me to power down. I tried the partition thing from clockwork recovery, it looks like it runs fine but it's still boot looping at the "n". I used this guide: http://forum.xda-developers.com/showthread.php?t=1094371
*sigh* This is it isn't it? Any other suggestions
angelstark said:
I had the same thought. I tried it off the sd card but once the little penguin pops up and the code runs it stops and gives me an error and asks me to power down. I tried the partition thing from clockwork recovery, it looks like it runs fine but it's still boot looping at the "n". I used this guide: http://forum.xda-developers.com/showthread.php?t=1094371
*sigh* This is it isn't it? Any other suggestions
Click to expand...
Click to collapse
That one does not re-partition enough partitions. Follow DizzyDen's directions in the thread I last referenced.
Sent from my NookColor using Tapatalk
Hallo again,
So upon looking at dizzys post... i got really confused. lol. I downloaded all the files and it looks like (to me atleast) that I need to use the adb shell in order to use those files. Only problem is my device isn't linked up with that and for some reason my pc isn't recognizing my device.
I could be wrong and am just a complete idiot. (I'll actually betting on that last part). Any advice on that, would help. (not on being an idiot, the other thing...the partition thing)
I did however install the dual boot from this thread: http://forum.xda-developers.com/showthread.php?t=1448186 onto my sd card and I am able to boot up cm9 off the sd card. (kinda awesome)
I apparently i can no longer boot from my emmc (folders empty, don't know if that important), but I guess this sd mount will have to do.
Still, any further thoughts would be appreciated. Thanks.
Yes, you do have to ordinarily use adb to do what dizzy said. But you are lucky that you got the dual boot sd to work because you can do it from there.
Just boot to cm9 and go to terminal. Type su <enter>. You shoud have a # prompt. Now you can do the commands that dizzy wanted you to do from there. You should put those img files you downloaded from dizzy into /sdcard. Then do those dd commands dizzy had in his partitions.txt (one at a time). Hopefully that gets you back to an older stock on emmc.
Do you know exactly how awesome you really are leapinlar? No, cause I'm gonna tell you... your freaking AMazing... with a capital A and M, cause the A cannot contain the awesomeness of you so it had to spilled over to the M.
I ran dizzys .img files though the terminal just like you said, rebooted and now I'm back baby!!!
You don't understand how good I feel right now, I owe you a steak and a beer. lol
I'm glad it worked for you. I was hoping it would because I am working on a method to do the same thing with much smaller files to download. You were my tester and you did not even know it. Lol. Thanks for the feedback.
hahahaha. Glad I could help. lol