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.

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

Random bricking Acer A500 (Need help)

By definition its bricked, it will not go past the Acer Logo.
So I bought the tablet used and already unlocked, rooted and flashed with a RE-FLEX 4.0 Rom, I'm not sure which one it was. It has been randomly crashing for the past week or so. The other night it froze and I cut it off and that's when it wouldn't boot past the logo. I can boot in Recovery, below the menu I get the following...
Code:
E:Can't mount /cache/recovery/command
Kernel: thor-kernel_v1.16mini
Updates on TegraOwners.com
Setting CPUO & CPU1 to 1GHz...
Done!
Fixing A500 Boot/Recovery Chechsums...
Running itsmagic
Done!
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
From what I can tell I am running CWM-based Recovery v5.5.0.x (thor2002ro rev1.7) as a recovery.
I have tired to mess around a little seeing if it would let me install a fresh ROM. So I went to install from SD card and internal storage and both says
Code:
E: Can't mount /sdcard/
So with all that information I hope someone can help me out.
Thanks,
I started a new post because most of the other one people don't give enough information to get help or the don't respond to the person trying to help them. Im trying to get this fixed.

Same problem :\
I'm thinking in buy a new mobo is 50-60 dollars on ebay...
http://www.ebay.com/itm/New-Acer-Ic...142349052?pt=Motherboards&hash=item337d1c74fc

Yeah, if I know that will fix the problem I might.
jancarlos1597 said:
Same problem :\
I'm thinking in buy a new mobo is 50-60 dollars on ebay...
Click to expand...
Click to collapse

From what I have read and locked at. Looks like it is a bad MOB. But it requires to or three places be soldered, which is above my pay grade. I dont see dumping $50 for MOB and another $50 to have it installed when its outdated as it it.

I bought a new mother board from that ebay link and replaced it. Of course it works fine now. It didnt need to be soldered like I thought. It just needed a little pressure behind it. So for $50 I got it fixed, not rooted anymore but no big deal there.
Robert417919 said:
From what I have read and locked at. Looks like it is a bad MOB. But it requires to or three places be soldered, which is above my pay grade. I dont see dumping $50 for MOB and another $50 to have it installed when its outdated as it it.
Click to expand...
Click to collapse

[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

Cant flash an OS - "failed to mount partition '/vendor' (invalid argument)"

Hello!
Now, I know this problem is in other threads. But the only reason why I'm posting a new one is if either that thread had died or the solution wasn't applicable to me (it didn't/doesn't work).
So! What happens is when I try to flash a file to the system or vendor I get this error.
Code:
failed to mount partition '/vendor' (invalid argument)
I've tried in TWRP and the bootloader fixes. And now, I currently have no OS.
What I've tried is as follows:
Flashing just the vendor (bootloader/TWRP) - ends with the vendor error.
Flashing .zip ROMs (bootloader/TWRP) - ends with the vendor error.
Trying the usual return to stock procedure - ends with the vendor error.
Repairing partition in TWRP - Says operation completed but the error is still persistent.
Basically. Nothing works because the Vendor partition is unmountable.
What should I do? I have no idea what a fix could be.

Alright, so i've tried some things. I guess I've fixed it but I got a new problem. In the end what fixed it was wiping every parition and rebooting TWRP and then flashing a system image then vendor image. When i say image i mean a manual .img flash instead of a .zip file.
The problem now it that because every was wiped, i no longer have a recovery. When i boot into recovery i get "No command". So now im stuck with stock android 8.1 and a unlocked bootloader that won't do anything. Every time i try and flash a partition i get
Code:
FAILED (data write failure (Too many links))
or
Code:
FAILED (command write failed (No error))
Any tips on getting a recovery installed so i can return to my custom ROM ways.
Thanks for any help in advance.

Nexus Radical said:
Alright, so i've tried some things. I guess I've fixed it but I got a new problem. In the end what fixed it was wiping every parition and rebooting TWRP and then flashing a system image then vendor image. When i say image i mean a manual .img flash instead of a .zip file.
The problem now it that because every was wiped, i no longer have a recovery. When i boot into recovery i get "No command". So now im stuck with stock android 8.1 and a unlocked bootloader that won't do anything. Every time i try and flash a partition i get
or
Any tips on getting a recovery installed so i can return to my custom ROM ways.
Thanks for any help in advance.
Click to expand...
Click to collapse
Try using Nexus root toolkit, I used that today to fix recovery,

jimbomodder said:
Try using Nexus root toolkit, I used that today to fix recovery,
Click to expand...
Click to collapse
Done some research and it seems to be a cable issue of all things with this errors. I bought a new one that should arrive by amazon tomorrow. Will see if that fixes it.
As the nexus toolkit ive been using that a lot. With that i don't even get an error but it never works.

Nexus Radical said:
Done some research and it seems to be a cable issue of all things with this errors. I bought a new one that should arrive by amazon tomorrow. Will see if that fixes it.
As the nexus toolkit ive been using that a lot. With that i don't even get an error but it never works.
Click to expand...
Click to collapse
That's something I have loads of, all seem to connect ok but least you should have it fixed soon.

jimbomodder said:
That's something I have loads of, all seem to connect ok but least you should have it fixed soon.
Click to expand...
Click to collapse
Yeah well, it seemed the cable wasn't the issue. I wouldn't of thought it was myself but yeah. Seems my initial thoughts were right as the cable didn't fix anything. Same errors, same problem. So all my research has lead to nothing. So how can I fix this? I'm out of solutions. I need xposed at least on my phone to be usefull since I can't disable the screen off during calls.

Nexus Radical said:
Yeah well, it seemed the cable wasn't the issue. I wouldn't of thought it was myself but yeah. Seems my initial thoughts were right as the cable didn't fix anything. Same errors, same problem. So all my research has lead to nothing. So how can I fix this? I'm out of solutions. I need xposed at least on my phone to be usefull since I can't disable the screen off during calls.
Click to expand...
Click to collapse
Have you tried wugfresh Nexus tool kit?

Just thought I'd let you know that I have fully restored stock and locked my bootloader, and if I boot recovery I get " no command" too. Seems latest recovery image does f*@k all.

jimbomodder said:
Have you tried wugfresh Nexus tool kit?
Click to expand...
Click to collapse
No, I haven't. BUT!!! I have fixed it...
So the issue that I was having is that I bought a replacement charging board (the PCB for the USB dock.) I replaced it because I had a faulty microphone on it but the USB port was fine. Putting in the old one fixed all the issues I was having. Its meant to be an OEM part so I didn't figure it would be the problem but it was *sigh*... So I take it where I got it from Replacement Base wasn't legit? Ah well, at least my problem is fixed and if anyone gets the same problems they might find this thread.
Thanks for your support thought dude! It was nice to have someone to ask.

Nexus Radical said:
No, I haven't. BUT!!! I have fixed it...
So the issue that I was having is that I bought a replacement charging board (the PCB for the USB dock.) I replaced it because I had a faulty microphone on it but the USB port was fine. Putting in the old one fixed all the issues I was having. Its meant to be an OEM part so I didn't figure it would be the problem but it was *sigh*... So I take it where I got it from Replacement Base wasn't legit? Ah well, at least my problem is fixed and if anyone gets the same problems they might find this thread.
Thanks for your support thought dude! It was nice to have someone to ask.
Click to expand...
Click to collapse
O crap, I got 2 "oem" replacement cameras for my 6p from them and both blurry and don't save pictures,. Glad you fixed it yet.