Hi,
I have an issue while updating my phone with 4.2.2 on OTA.
in recovery, I have this message :
E: Invalid Command Argument
E: Unknown volume for path *name of the update*
E: Can't mount DATA *name of the update*
Error mounting / External_SD
I tried to look for the zip file for installing manually, I can't find it.
any idea ?
Hi there,
You can get the stock 4.2.2 update from the stock ROM thread and then simply flash it through recovery to avoid such errors
Sent from my HTC One using xda premium
flashing with recovery stock resolved my issue, but I have a new one.
I'm updating my phone with 4.2.2 stock, but it's kinda blocked, the update began 50 minutes ago and it's only to the quarter ...
is it possible to restart the phone and try again without issue ?
any idea?
Hi guys, I've been working on my ATT m7 for a day or so now.
Story:
I was on CWM recovery and CyanogenMod 11 M7 without any issues for a long time, rooted, S-OFF, etc. Phone all of a sudden got a bunch of force closes and errors such as "com.google.gapps has encountered an error and needs to close" it would repeatedly appear. I tried killing apps, force closing apps, etc to no avail.
I restarted the phone and it froze on the HTC logo. Hard reset, same thing. Wouldn't go past HTC logo. No big deal, went into recovery, cleared cache, Dalvik, reboot, hangs on HTC logo. Kept trying this, same result. Decided to just factory wipe and try that. Used adb to pull my files off the phone, then factory wiped, still no luck, hangs on HTC logo. Tried reflashing previously working CyanogenMod zip, no luck.
Flashed TWRP recovery and tried all of the above again, still no luck. Strangely, TWRP says it looks like my phone is not rooted and asks to install su. I verified root through adb shell, but TWRP still reports no root. Also verified in TWRP going to console and "whoami" gives "root" so not sure what's going on there.
Tried an RUU that looked like it was working, but then randomly failed out ERR 155.
Then I just happened to notice my bootloader says I now have S-ON! Wtf?
Not really sure what to try at this point, you guys have any suggestions?
Edit:
Just tried flashing a stock ATT Sense OTA zip but TWRP gives errors:
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Installing '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Error flashing zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Updating partition details
E: Unable to mount '/cache'
eguh.
wingman358 said:
Hi guys, I've been working on my ATT m7 for a day or so now.
Story:
I was on CWM recovery and CyanogenMod 11 M7 without any issues for a long time, rooted, S-OFF, etc. Phone all of a sudden got a bunch of force closes and errors such as "com.google.gapps has encountered an error and needs to close" it would repeatedly appear. I tried killing apps, force closing apps, etc to no avail.
I restarted the phone and it froze on the HTC logo. Hard reset, same thing. Wouldn't go past HTC logo. No big deal, went into recovery, cleared cache, Dalvik, reboot, hangs on HTC logo. Kept trying this, same result. Decided to just factory wipe and try that. Used adb to pull my files off the phone, then factory wiped, still no luck, hangs on HTC logo. Tried reflashing previously working CyanogenMod zip, no luck.
Flashed TWRP recovery and tried all of the above again, still no luck. Strangely, TWRP says it looks like my phone is not rooted and asks to install su. I verified root through adb shell, but TWRP still reports no root. Also verified in TWRP going to console and "whoami" gives "root" so not sure what's going on there.
Tried an RUU that looked like it was working, but then randomly failed out ERR 155.
Then I just happened to notice my bootloader says I now have S-ON! Wtf?
Not really sure what to try at this point, you guys have any suggestions?
Edit:
Just tried flashing a stock ATT Sense OTA zip but TWRP gives errors:
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Installing '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Error flashing zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Updating partition details
E: Unable to mount '/cache'
eguh.
Click to expand...
Click to collapse
you can not flash OTA, these are patches, not complete rom and when flashed over the appropriate rom version, must be done using stock recovery, not twrp.
What version of twrp are you using? CM11 need block:by-name support in the recovery kernel.
For your s-on issue, you probably have used 'fastboot oem writesecureflag3' command by mistake
alray said:
you can not flash OTA, these are patches, not complete rom and when flashed over the appropriate rom version, must be done using stock recovery, not twrp.
What version of twrp are you using? CM11 need block:by-name support in the recovery kernel.
For your s-on issue, you probably have used 'fastboot oem writesecureflag3' command by mistake
Click to expand...
Click to collapse
Thanks for the info... do you recommend trying a stock rom or CM11? I'm on the latest TWRP, it's v2.8.0.2.
And regarding the command 'fastboot oem writesecureflag3' I've never seen it before, and certainly haven't issued it by hand. Whether the command was issued by some tool or file I've tried, I don't know.
EDIT:
I think the reason for the RUU failure may be due to the version, I believe it was trying to flash 1.xx over 3.xx. Does that sound right? Also, is it correct that I need stock recovery and locked bootloader for a RUU??
wingman358 said:
Thanks for the info... do you recommend trying a stock rom or CM11? I'm on the latest TWRP, it's v2.8.0.2.
And regarding the command 'fastboot oem writesecureflag3' I've never seen it before, and certainly haven't issued it by hand. Whether the command was issued by some tool or file I've tried, I don't know.
EDIT:
I think the reason for the RUU failure may be due to the version, I believe it was trying to flash 1.xx over 3.xx. Does that sound right? Also, is it correct that I need stock recovery and locked bootloader for a RUU??
Click to expand...
Click to collapse
Well somehow I was able to flash a stock ROM ([ROM][4.4.2] - AT&T 4.18.502.7 Stock Rooted from this thread). Then flashed PA_gapps over (with dalvik and cache wipe before and after flashes).
On boot, it cleared the HTC logo (finally!). Then it hit me with "Google search has stopped unexpectedly" and goes back to the HTC logo... wtf... then it popped up "Dialer has stopped unexpectedly"... then the home screen came up, and it rebooted itself.
After rebooting, I swiped to unlock the screen and it showed the dreaded white HTC logo... ugh, then it hits me in quick succession with "Hangouts has stopped" "Google Play Music has stopped" "Youtube has stopped" and so on. If I hit the screen off button then turn it on, it showed the lock screen. The lock screen seemed fine, the clock worked, and swiping to unlock worked, but when it unlocked instead of the home screen it showed the white HTC logo. Eventually it rebooted itself. After I think the third time rebooting itself, the android setup/configuration came up. "_____ has stopped" keeps popping up.
I was able to restore contacts and stuff by signing into my google account, but I am almost continually getting "_____has stopped" pop-ups, and if I let the phone sit for a few minutes it reboots itself maybe every 5 minutes or so. Also I don't think I have cell service (it just shows an X with no bars). It seems normal aside from those (not much home screen lag, apps open, wifi seems to work).
I did a permissions fix from recovery which completed without errors, but it didn't seem to help.
wingman358 said:
Well somehow I was able to flash a stock ROM ([ROM][4.4.2] - AT&T 4.18.502.7 Stock Rooted from this thread). Then flashed PA_gapps over (with dalvik and cache wipe before and after flashes).
Click to expand...
Click to collapse
Why flashing gapps over a stock sense rom?
alray said:
Why flashing gapps over a stock sense rom?
Click to expand...
Click to collapse
Great question... I've been in the habit of always flashing gapps after flashing rom, does gapps come with stock rom??
wingman358 said:
Great question... I've been in the habit of always flashing gapps after flashing rom, does gapps come with stock rom??
Click to expand...
Click to collapse
Yes, wipe everything and reflash the rom
alray said:
Yes, wipe everything and reflash the rom
Click to expand...
Click to collapse
That did it! Wiped, reflashed, and no more force closes, not one. Thanks a bunch alray!!!
I tried installing http://forum.xda-developers.com/showthread.php?t=2189373&page=2 and it installed successfully as of TWRP and rebooted. After that it was stuck in a bootloop, at the HTC Logo only no animation. I went and relocked the bootloader and then tried to do the Sprint_HTC_One_m7wls_1.29.651.10_RUU but it was at 'Sending' for over an hour. I then unlocked the bootloader again and installed TWRP and now TWRP cannot mount /cache or /data when I try to install ROM from my OTG cable. I've tried so much and still haven't gotten anywhere with it. I'm running out of options..:crying:
drakem132 said:
I tried installing http://forum.xda-developers.com/showthread.php?t=2189373&page=2 and it installed successfully as of TWRP and rebooted. After that it was stuck in a bootloop, at the HTC Logo only no animation. I went and relocked the bootloader and then tried to do the Sprint_HTC_One_m7wls_1.29.651.10_RUU but it was at 'Sending' for over an hour. I then unlocked the bootloader again and installed TWRP and now TWRP cannot mount /cache or /data when I try to install ROM from my OTG cable. I've tried so much and still haven't gotten anywhere with it. I'm running out of options..:crying:
Click to expand...
Click to collapse
The RUU you are trying to use is very old try the latest...RUU is the only thing that will fix the problem.
BD619 said:
The RUU you are trying to use is very old try the latest...RUU is the only thing that will fix the problem.
Click to expand...
Click to collapse
Where the hell would I find it? I have a Sprint HTC One and haven't been able to find any RUU for it, unless I'm looking in the wrong direction
Look here
http://forum.xda-developers.com/showthread.php?t=2795856
Sent from my HTCONE using XDA Free mobile app
so firstly, let me make this clear, i had Android 6 stock rom working initially, i installed TWRP and rooted the phone with SU
All was working fine until i decided to try and wip the phone to test either a lineage os build or the new EMUI 5
However after performing factory reset, the /data partition is now broken.
I know i'm not the only one that has encountered this issue, but i would at least like a straight forward answer in order to resolve the problem.
Stock recovery now doesn't seem to be an option as when i send it to the phone, i reboot and TWRP still exists.
i have tried via fastboot and from within TWRP, i still get the /data partition error if trying in TWRP to flash recovery.
surely there is a proper solution for this, as this is a software issue not a hardware issue.
i would appreciate your assistance and can provide whatever required information necessary.
i did not pay $500 for this phone for it to be a useless brick
I noticed something here about modaco-rc3 recovery, which i am downloading to try, if it flashes properly, as i suspect this /data partition issue is preventing much of anything from being modified now.
i look forward to your responses and will reply to this with an update after trying to flash modaco recovery if successful
The data partition of the EMUI roms are different than what for example lineageos needs (I think because of encryption).
You need to flash the stock recovery via fastboot, then wipe and format data from there, then TWRP should be able to mount the partition again. In TWRP you can format the partition again to the format according to what is necessary for the rom you want to install.
christopherpfister said:
You need to flash the stock recovery via fastboot, then wipe and format data from there, then TWRP should be able to mount the partition again. In TWRP you can format the partition again to the format according to what is necessary for the rom you want to install.
Click to expand...
Click to collapse
I am just downloading 4.1 stock rom i found finally on Huawei website after much buggering around last night, clearly it was a long day.
Will get this flashed with the stock recovery that I was able to put back on thanks to SRKTool
Will update again shortly, thank you for the reply.
failed to mount system for rom install
now this is just getting silly...
so i was able to restore stock rom with the dload folder procedure and EMUI recovery restored with SRKTool
successfully then unlocked bootloader, put on twrp-3.0.2-0-eva-modaco-rc3, did the data wipes and tried to install lineage os zip.
(the original problem of going back to stock rom is solved, but this is still ongoing as to now why a custom rom will not load)
now i get the infamous ERROR: 7
after
could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4
mount: failed to mount /dev/block/bootdevice/by-name/system at system: no such file or directory
....this is all seeming far too difficult to install any custom rom on this unit, what is happening?
same issue
I'm having a similar issue, any updates?