Database Users

Forever Install error

im getting this error: If messages beginning in E: appear, stop! If possible, join IRC for support, when trying to install forever, any ideas how to get around this?

Not sure that's an error. I remember seeing that as well. It's a warning.

bradm23 said:
im getting this error: If messages beginning in E: appear, stop! If possible, join IRC for support, when trying to install forever, any ideas how to get around this?
Click to expand...
Click to collapse
Forever must write to the /cache and/or /misc partitions and if clockworkmod recovery reports errors when you're trying to flash their NAND-hack (what the E:/ squak is all about), they don't want you to reboot with an f-ed up bootloader because you could easily fall into the boot mode 3 (security error) trap -- also known as BRICKED for life, unless you have a JTAG, assuming the Inc has JTAG test points.
So if the install suffered a fatal error terminating with an E:/cache type error, they want you to STOP and contact them ASAP to see if something could be done in adb, I'm assuming. If you just get warnings but the script does not terminate, then you're ok, or both of yeahs would be in dire straits and know it

I fixed this by downloading forever directly from my phone and moving it to sd with astro. I think the files were getting corrupt moving it from my pc to sd card.

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] Mytouch 4g Unbricking help

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-----^^

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