Database Users

Serious problem.... Need help

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.

[Q] CWM Recovery Errors

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?

[Q] Clockworkmod not Recoverying/Doing anything useful

So I had Cyanogenmod 7.1.0-RC1 flashed on my phone and working fine. Then one day it was all frozen up and wouldn't boot or do anything. So I decided to use Clockworkmod (3.0.2.4) to restore to an old backup I have of Cyanogen 7.0.3. It came up with a silly error saying it could not format /cache, but everything else worked so I shrugged it off and rebooted. Cyanogen 7.0.3 loaded fine, but I could not download apps from the marketplace. (They would never "start" - I even tried installing the new marketplace update). So then I decided to restore the SAME backup again, with the same error, and after struggling I tried restoring to a backup I have of the stock rom. Which worked. Magically. No errors. So then, being stupid and unsatisfied I reflashed the Cyanogen 7.0.3 backup again. This time it said "error while formatting /system!" And now I've been stuck trying to figure out how to fix this error.
I can still boot into ClockworkMod, so I assume my phone is not bricked. I've read that updating to ClockworkMod 3.0.2.5 may actually fix my problem, but I can't seem for the life of me to find a tutorial that can tell me how to flash a new recovery image on the MT4G without Rom Manager (since I can't boot a rom, I can't open rom manager).
Thank you for your time, any help is appreciated. (I also apologize upfront if this error has been reported and solved before, I can't seem to find it though.)

Sorry, but your phone is bricked. Those errors indicate that your eMMC chip has failed. Your only hope is to flash the PD15IMG.zip file from the bootloader. That will unroot your phone and flash the stock ROM. It's unlikely to work, however. Some people will swear up and down that eMMC failure doesn't brick the phone, but I have yet to see anyone save their device once those errors appear in recovery mode.

Thanks for you quick response. I am going to try what you suggested and update what happens.
Do you know what may cause this error? So I can avoid it in the future. Granted, I may not have a phone for a while now.

crebu said:
Thanks for you quick response. I am going to try what you suggested and update what happens.
Do you know what may cause this error? So I can avoid it in the future. Granted, I may not have a phone for a while now.
Click to expand...
Click to collapse
Some MT4G's have a different brand of eMMC chip that is prone to failure after the phone has been rooted. See this thread for a little more info.
Make sure you flash the correct PD15IMG.zip file. Any file flashed in the bootloader has to be named that, so a search could easily turn up a radio. Search the dev section for the stock TMOUS RUU. It will be around ~328MB in size (roughly).

Not every "can't open /cache/recovery/log" error means your eMMC is dead. My phone gave that error after a bad ROM flash. Flashing PD15IMG.zip in hboot fixed it.

TeeJay3800 said:
Some MT4G's have a different brand of eMMC chip that is prone to failure after the phone has been rooted. See this thread for a little more info.
Make sure you flash the correct PD15IMG.zip file. Any file flashed in the bootloader has to be named that, so a search could easily turn up a radio. Search the dev section for the stock TMOUS RUU. It will be around ~328MB in size (roughly).
Click to expand...
Click to collapse
When I try to use Clockwork to update from the zip I get the error
E:Can't open /sdcard/PD15IMG.zip
(bad)
Installation aborted.
Maybe I don't understand the correct procedure for flashing a PD15IMG.zip file?
**EDIT** I'm dumb, I had to boot into the bootloader. Hehe.

crebu said:
When I try to use Clockwork to update from the zip I get the error
E:Can't open /sdcard/PD15IMG.zip
(bad)
Installation aborted.
Maybe I don't understand the correct procedure for flashing a PD15IMG.zip file?
Click to expand...
Click to collapse
In my earlier post I said to flash in the bootloader. Put the file in the root of your SD card, boot into the bootloader, and it will ask you if you want to flash the file.

TeeJay3800 said:
In my earlier post I said to flash in the bootloader. Put the file in the root of your SD card, boot into the bootloader, and it will ask you if you want to flash the file.
Click to expand...
Click to collapse
Thank you so, so much.
What you suggested absolutely worked. I'm not back to the stock rom working seemingly perfectly. Does this mean I don't have a bad eMMC chip? Would it be safe to continue flashing custom ROMS?
Thanks again.

TeeJay3800 said:
In my earlier post I said to flash in the bootloader. Put the file in the root of your SD card, boot into the bootloader, and it will ask you if you want to flash the file.
Click to expand...
Click to collapse
Thank you so, so much.
What you suggested absolutely worked. I'm now back to the stock rom working seemingly perfectly. Does this mean I don't have a bad eMMC chip? Would it be safe to continue flashing custom ROMS?
Thanks again.
Edit: changed "not" to "now". Quite a misleading typo.

crebu said:
Edit: changed "not" to "now". Quite a misleading typo.
Click to expand...
Click to collapse
Haha, yeah it was! I'm glad your phone is not (now) working. As far as where to go from here, find out what eMMC you have. The thread I linked to has ADB instructions in the OP, and there are instructions to run commands via a terminal emulator throughout the thread. If you have the "good" eMMC, there's no reason you can't re-root and start over. Because of the errors you got in recovery, I'm afraid you have the "bad" eMMC in which case rooting is risky. Essentially, once you've rooted a phone with the bad chip, it's only matter of time until it fails and the phone is bricked. It could be a few days, few months, or few years, but the evidence shows it likely eventually will. Good luck!

TeeJay3800 said:
In my earlier post I said to flash in the bootloader. Put the file in the root of your SD card, boot into the bootloader, and it will ask you if you want to flash the file.
Click to expand...
Click to collapse
hi, could you help me on this?
Even if I hboot my phone ( by hold power and vol down), the phone still gets to CWM. Could you help me to boot PD15img.zip in the bootloader.
Thank you so much,

Need (expert?) opinion

Hi guys,
I'm posting here after another afternoon messing with my phone.
Here's how the story goes.. My Nexus 4 fell on the ground and broke the glass, the touch screen wasn't working anymore. So i've decided to order a new screen online and replace it. This is the screen i've ordered. http://www.spareslg.com/lcd-e-touch-lg-nexus-4-lg-e960-acq86270901.html
In retrospect i used a bad guide to change it and kinda freestyled replacing the parts. I forgot to move the power and volume button. I've also wrecked my battery in the process of replacing the screen (twice). So I've ordered a new one. (yeah I'd better followed the guide on the page of the item seller, but what's done is done.. right)
Anyway, after many hours struggling with my phone I'm at this point:
The phone boots and i stuck on google logo with a lock symbol at the bottom. If I press volume down and power button I get in the bootloader.
If in the bootloader I select recovery mode the phone boots into ClockworkMod Recovery v6.0..4.3. I get the menu of CWM but and the bottom of the screen I get the following text:
Clockworkmod recovery v6.0.4.3
E: can't mount /cache/recovery/command
E: Failed closing /dev/block/platform/msm_sdcc.1/by-name/misco (I/O error)
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
E: Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
Click to expand...
Click to collapse
Then I go to "Instal zip" install from sideload:
Sideloading works in my command promt. I get 100%
In the phone this happens after the 100%:
Restarting adb...
E: can't open /cache/recovery/last_install
E: faild to open last_install: No such file or directory
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip (bad)
Installation aborted.
Click to expand...
Click to collapse
When i try to do factory reset I get
--- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure..
E: unknown volume "/sdcard/.android_secure"
Data wipe complete
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
E: Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
Click to expand...
Click to collapse
So I figure something is wrong with my internal memory. Just guessing. That's why I need some input.
So my question is: What's causing this problems preventing me to flash the 4.4.2 stock rom?
Did I destroy some hardware?
Thanks for reading,
Semi

yes, that's clearly a fried eMMC... since the recovery can't do anything about that, try flashing stock images via fastboot (because fastboot is "stronger"). if that didn't work, then... well... i hate to say it to a nexus user....

Riro Zizo said:
yes, that's clearly a fried eMMC... since the recovery can't do anything about that, try flashing stock images via fastboot (because fastboot is "stronger"). if that didn't work, then... well... i hate to say it to a nexus user....
Click to expand...
Click to collapse
Thanks for the quick reply!
I've done "fastboot flash system stockrom" and In command prompt everything goes well until "FAILED: flash write failure"
The eMMC is on the motherboard and that costs 180 euro, not really worth it I guess to buy a new one. Is there any possibility that I made a mistake that's reversible by opening the nexus 4 again?
IF someone else could confirm this theory (which sounds credible) that I should replace my main board in order to get the phone working? No disrespect inteded to Riro Zizo, only want to be 100% sure. Thank you!

sure! you can't be 100% sure until you get others' opinions and experience too... but i say there's no way that that can be fixed by reopening it. not even replacing the eMMC itself could work since the pins are just way too smal to work with.
sorry
Sent from my Nexus 4

There's a small chance the new board isn't fitted quite right and it's shorting out or something, but most likely you've damaged something on the board during the repair.

Riro Zizo said:
sure! you can't be 100% sure until you get others' opinions and experience too... but i say there's no way that that can be fixed by reopening it. not even replacing the eMMC itself could work since the pins are just way too smal to work with.
sorry
Sent from my Nexus 4
Click to expand...
Click to collapse
No problem bro. Thank you.
DrFredPhD said:
There's a small chance the new board isn't fitted quite right and it's shorting out or something, but most likely you've damaged something on the board during the repair.
Click to expand...
Click to collapse
Well yeah, it's the same board that I've moved. Too bad, lesson learned
I wonder one more thing.. When I was googling on possible causes someone somewhere, suggested that the guy needed to repartition his storage space or sth like that. Any chance that's a possible solution? Just to be 100% sure I can let it go LOL

Bummer! :-O I like tinkering and all, except my precious. There's two options, (for me) Service Center or new phone! So far, it's the new phone option that win the game. I know this doesn't help your present issue in one way, but it seems that you might not have a choice. Good luck to you.
Sent with my Nexus® 10 minus 3

You shouldn't need to flash a phone after a mechanical repair. I take it it still booted with the cracked screen? The fact that it doesn't now pretty much proves it's dead.

DrFredPhD said:
You shouldn't need to flash a phone after a mechanical repair. I take it it still booted with the cracked screen? The fact that it doesn't now pretty much proves it's dead.
Click to expand...
Click to collapse
Yeah that makes sense. Thanks alot guys. Appreciated.

Freaking eMMCs! had a similar problem with flashing a dead phone, my GSII, ended up sending it to the repair center, luckily was still under warranty.
And about playing with PIT files, it's usually the hopeless case, but most of the time it doesn't work, and even if it does, the phone doesn't live afterwards much longer, the sd card still unstable.
I'm not an expert though but I guess it's a wise idea to let it go, and get a new android, maybe a N5?

[Q] Hardware failure?

Last night all the apps on my 16gb Nexus 4 crashed inexplicably at the same time. I tried rebooting and the phone just looped the loading animation endlessly. I tried going into recovery mode and doing a factory reset but get the following errors:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
(It repeats these several times before giving up)
This morning I downloaded the Nexus Root Toolkit to try and reflash the stock software, but with no luck. The bootloader is still locked (I never had a need to root this phone... so I thought...) so it won't allow me to flash updates. When I try to unlock using NRT, I just end up in another boot loop.
I've also tried to sideload the stock image through the phone's recovery but get the same errors. If I try the "wipe cache partition" option I get the same errors (but change /log to /last_install) with 1 additional:
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc
(I/0 error)
So my question is, how hosed am I? What have I not done that I should try? Is there a way to flash or sideload just an unlocked bootloader? Any ideas about how to fix this unmountable E:? Or has my phone just exploded?
Thanks in advance for your help!!
Kevin

Just a quick bump of this before I admit complete and utter failure....
Both Google and LG believe it's a ROM failure, but since I hadn't rooted the phone or even installed any apps not from the Play Store, I don't buy it. I've tried pushing and pulling files from adb, tried flashing files through fastboot, used the Nexus recovery tool, the command prompt and even tried the lgnpst. Nothing changes the situation. It just can't seem to read or write to E: This has to be a hardware failure, right? A short circuit or something?
Has anyone sent a Nexus 4 back to LG for repair? I have a feeling their repair, especially if it's more than just reinstalling the software, is going to cost more than my insurance deductible, so unless something miraculous changes today, I'm going to replace it that way... :/
Any ideas are appreciated.
Thanks!
Kevin

Looks like messed up partitions or mmc failure - had a similar problem 2 years ago on SGP 5.0, couldn't mount system (partitions f0oked up)

K'Tag said:
Just a quick bump of this before I admit complete and utter failure....
Both Google and LG believe it's a ROM failure, but since I hadn't rooted the phone or even installed any apps not from the Play Store, I don't buy it. I've tried pushing and pulling files from adb, tried flashing files through fastboot, used the Nexus recovery tool, the command prompt and even tried the lgnpst. Nothing changes the situation. It just can't seem to read or write to E: This has to be a hardware failure, right? A short circuit or something?
Has anyone sent a Nexus 4 back to LG for repair? I have a feeling their repair, especially if it's more than just reinstalling the software, is going to cost more than my insurance deductible, so unless something miraculous changes today, I'm going to replace it that way... :/
Any ideas are appreciated.
Thanks!
Kevin
Click to expand...
Click to collapse
this sure looks like mmc is fried. the repair will change whole motherboard. if you have some kind of fear. write down your serial number that appears on fastboot mode. then send to repair. when it get backs look the new serial. you will see its changed. the imei will also be changed as far i know