Last night tried installing SkyDragon v.9. It installed, the phone booted into rom and then started rebooting. Now i cant flash any rom because the phone reboots on the stage of wiping something. I installed newer twrp 2.8.0.2. Now i have these erros: unable to mount data and unable to mount internal storage. I'm S-ON unlocked. Tried ADB Sideload but it says device not found. Have no idea what to do. Saw somewhere that you can relock, unlock and install RUU to unbrick, but im not sure if i should do that. Help please.
OK. So... Try this:
From recovery go into Advanced Wipe, select all and wipe 2 or 3 times.
Reboot into bootloader.
In fastboot mode, make fastboot erase cache.
Then boot into recovery, and try ADB Sideload again or install rom via USB OTG (if you have)
If it also doesn't work try sth like this - it worked for me some time ago.
I saw that my PC recognizes my phone as normal storage when it's booted into TWRP and I don't need ADB Sideload. Try copy ROM like this and install.
If it won't work, you'll have to install RUU
Bruce666 said:
OK. So... Try this:
From recovery go into Advanced Wipe, select all and wipe 2 or 3 times.
Reboot into bootloader.
In fastboot mode, make fastboot erase cache.
Then boot into recovery, and try ADB Sideload again or install rom via USB OTG (if you have)
If it also doesn't work try sth like this - it worked for me some time ago.
I saw that my PC recognizes my phone as normal storage when it's booted into TWRP and I don't need ADB Sideload. Try copy ROM like this and install.
If it won't work, you'll have to install RUU
Click to expand...
Click to collapse
It didn't work Which RUU should i choose? M7-UL, hboot-1.55.0000, radio-4a.21.3263.04. I live in russia so i suppose i need one with "europe" in it's name? And how should i re-lock? Just by using fastboot command?
Give me CID ill try to find ruu 4u
Bruce666 said:
Give me CID ill try to find ruu 4u
Click to expand...
Click to collapse
HTC_A07
http://www.htc1guru.com/2014/03/android-ruu-europe/
Bruce666 said:
http://www.htc1guru.com/2014/03/android-ruu-europe/
Click to expand...
Click to collapse
Thank you very much! Really hope this works.
It must work. If you need help writr here
[email protected] said:
Last night tried installing SkyDragon v.9. It installed, the phone booted into rom and then started rebooting. Now i cant flash any rom because the phone reboots on the stage of wiping something. I installed newer twrp 2.8.0.2. Now i have these erros: unable to mount data and unable to mount internal storage. I'm S-ON unlocked. Tried ADB Sideload but it says device not found. Have no idea what to do. Saw somewhere that you can relock, unlock and install RUU to unbrick, but im not sure if i should do that. Help please.
Click to expand...
Click to collapse
If it reboots immediately when you try to wipe or flash something (i.e instant black screen then reboot)
You can probably fix it with e2fsck.
Boot to recovery select Mount then unmount all partitions return to twrp home screen and connect usb and check adb is working with
Code:
adb devices
You should get an output of your serial no.
Then do this
Code:
adb shell
e2fsck -fvy /dev/block/mmcblk0p35
e2fsck -fvy /dev/block/mmcblk0p36
e2fsck -fvy /dev/block/mmcblk0p37
exit
Now try to flash the Rom again
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
After i installed twrp 2.8.0.2 i can wipe. Well, sometimes it does wipe but sometimes it just writes error: unable to mount data and unable to mount internal storage. When i try flashing rom, for example viperone 7.0.1, it writes "set_perm some changes failed" right at the 0%. I tried installing cyanogenmod 11s and it installed without errors. But when i boot into rom, it says something like "the process android ui crashed".
[email protected] said:
After i installed twrp 2.8.0.2 i can wipe. Well, sometimes it does wipe but sometimes it just writes error: unable to mount data and unable to mount internal storage. When i try flashing rom, for example viperone 7.0.1, it writes "set_perm some changes failed" right at the 0%. I tried installing cyanogenmod 11s and it installed without errors. But when i boot into rom, it says something like "the process android ui crashed".
Click to expand...
Click to collapse
check the Frequently Asked Question sticky page 3
Point D, relates to unable to mount
Point C, relates to permission errors for certain ROMs, 2.6.3.3 should work or 2.8.0.1;
2.8.0.2 is known to have problems with certain ROMs
nkk71 said:
check the Frequently Asked Question sticky page 3
Point D, relates to unable to mount
Point C, relates to permission errors for certain ROMs, 2.6.3.3 should work or 2.8.0.1;
2.8.0.2 is known to have problems with certain ROMs
Click to expand...
Click to collapse
Dude, you are a wizard! Installed 2.6.3.3 and flashed viper without any problems. Yay it's working :laugh: . Couldn't think that recovery can cause these errors. I've been using 2.7.1.1 for quite a long time so i thought it'll work like it always did, but it just kept rebooting on wiping stage. So now it's working prefectly fine :good: Spent 5 hours today looking for sloutions and i have no idea how i missed your post on the faq thread. Thank you very much for your help! And thanks to everyone who responded!
[email protected] said:
Dude, you are a wizard! Installed 2.6.3.3 and flashed viper without any problems. Yay it's working :laugh: . Couldn't think that recovery can cause these errors. I've been using 2.7.1.1 for quite a long time so i thought it'll work like it always did, but it just kept rebooting on wiping stage. So now it's working prefectly fine :good: Spent 5 hours today looking for sloutions and i have no idea how i missed your post on the faq thread. Thank you very much for your help! And thanks to everyone who responded!
Click to expand...
Click to collapse
no problem,
2.6.3.3 is best for most ROMs, unless they require a recovery with "by-name" support (such as CM11), then you need 2.7.0.8 or higher
i've also successfully flashed using 2.8.0.1, but .2 seems to have issues again.
and if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title
Related
Hey guys, long time lurker and now first time poster. Shame it has to be something very stupid.
So anyways, I wanted to flash the latest CM10.2 Unofficial build so I did the usual and downloaded the zip & gapps to my phone. But upon wiping my phone via TWRP I accidentally left the wipe userdata part checked and ... well now I have no OS installed as well as no zip's :/
I have TWRP installed so I thought why not sideload it, however when I go to advanced -> adb sideload it never starts up. This is the log:
Updating partition details...
Starting ADB sideload feature...
Click to expand...
Click to collapse
And it just stays there
I know that my ADB works as I have S-OFF & unlocked the bootloader and flashed the latest 1.54.0000 hboot so I can definitely use it, I just don't understand why it doesn't let me sideload for some reason.
Either way, I have full access to fastboot & TWRP recovery so i'm hoping this is a pretty simple thing to fix ... right?
Can anybody point me to the right direction?
Details:
No OS installed.
Access to TWRP & fastboot.
S-OFF, Modified Hboot 1.54.0000 (SuperCID) & Unlocked bootloader.
Windows 8 64-bit, drivers all work.
Latest SDK with all the binaries installed.
P.S. when I connect and try and use adb devices it doesn't recognise my device, and the cmd window gives the following when I try the sideload command:
Error: device not found.
Click to expand...
Click to collapse
Sounds like a driver issue to me but it doesn't make sense that the drivers would suddenly stop working ???
Here are screenshots of odd device behaviour when switching from fastboot to recovery (please copy & paste, I don't have enough posts to post images yet):
i.imgur.com/V79DFFA.jpg
i.imgur.com/MKD5C9U.jpg
Bump for help
I can't seem to get sideload to work in TWRP at the moment either. CWM works fine though, try flashing that and use the sideload feature.
Sent from my HTC One using xda premium
redbull123 said:
I can't seem to get sideload to work in TWRP at the moment either. CWM works fine though, try flashing that and use the sideload feature.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Tried that already, same issue in not detecting the device. I'm downloading these drivers in a hope to fix something.
Thanks for the reply
EDIT:
Finally got sideloading in TWRP to work, it turns out it was a driver issue :/
Anyways, these are the drivers that worked:
androidfiles.org/hasoon2000/getdownload.php?file=HTC%20Drivers/HTCDriver.exe
why is everyone always wiping their storage these days? just use CWM next time and you wont accidentally do this again..
IINexusII said:
why is everyone always wiping their storage these days? just use CWM next time and you wont accidentally do this again..
Click to expand...
Click to collapse
TWRP is much better for people who know what they are doing. There are more options and also a built in file manager. Also, the wipe button in TWRP wipes the 3 main partitions at once (data/cache/dalvik), so he must have actually selected internal sdcard from the advanced menu, and I have no idea why he would do that...
Doing the slider is all anyone needs to do in twrp to wipe yet I read more posts about people wiping with twrp than any other problem in these forums
So yesterday, I tried installing a custom rom and what happened was that the MD5 sum was incorrect and i wasn't able to boot into system and had no backups so was stuck thinking that it was the end of the world.
What happened next was utter follishness in which I used this command in bootloader -fastboot flash zip rom.zip- what happened then was that the rom was transferred but it tried to install it and failed and a consequence now I cant even reboot into recovery now. It,s like when I start recovery it skips that and progresses to the htc logo.
I relocked the device and unlocked it via the Unlock token I had and again tried to install the recovery and it did but didn't reload into it and skipped to the htc logo screen.
Can anyone please help me with recovering my phone since I just bought it today.
One possible thing that comes to my mind is using the flash command in the fastboot, will it help or any other ways? THANK YOU in advance...
You can adb sideload still. Use adb to reboot into recovery via USB and sideload a known good ROM with a correct MD5 sig. No need to remind you that checking the MD5 is of utmost importance
Sent from my HTC One using Tapatalk 4
bbinder said:
You can adb sideload still. Use adb to reboot into recovery via USB and sideload a known good ROM with a correct MD5 sig. No need to remind you that checking the MD5 is of utmost importance
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Bro, problem is that recovery doesnt work at all n where will i use adb command? In hboot?
Reflash the recovery and after this, do an erase cache:
Code:
fastboot erase cache
.
After you can boot into recovery and use the adb sideload function...
Guich said:
Reflash the recovery and after this, do an erase cache:
Code:
fastboot erase cache
.
After you can boot into recovery and use the adb sideload function...
Click to expand...
Click to collapse
I'm gonna try this and will report back! Thanks
I was able to enter the recovery but I try to install the rom.zip it says that cannot mount data and internal storage
What should be done about this?
With an error like: E:/ enable to mount internal storage?
Guich said:
With an error like: E:/ enable to mount internal storage?
Click to expand...
Click to collapse
yup with both internal storage and data, its not able to mount either of them
So:
- Flash the stock recovery
- Boot into bootloader
- Do a factory reset
- Reflash a custom recovery
- Teoritecally, this will work
Man, it's finally working. Feeling like hitting the thanks button a thousand times. Thank you so much!
:good:
No prob mate
Sent from One with Tapa4
Hi ALL!
First off I'd like to say thanks for such a forum! Its the first go to place for me for anything android.
Yesterday I did something terrible and very careless from my side. I un-intentionally deleted the /system partition on my HTC One while playing with it and now I am paying for my careless mistake. I have been looking for possible solutions here on this forum and elsewhere on the internet. I did manage to do an *adb sideload push* of a custom ROM and tried to install that but for some reason I cant mount some partitions from my sdcard for example /cache.
I tried exchanging between TWRP (latest) and CWM (touch latest) but no solution so far with the adb sideload method. So I have no OS installed on my phone and the phone sometimes hangs in the HTC Quietly Brilliant display page or sometimes it wouldnt even go in to the Recovery mode but keeps rebooting.
I am clueless at this point, please shade some light on my situation.
In the attached pic you'd find the output from the *fastboot getvar all* command and the phone is S-ON and Unlocked just to mention.
I really appreciate it...
What is the exact error when installing the ROM?
What ROM?
sent from my mobile device
SaHiLzZ said:
What is the exact error when installing the ROM?
What ROM?
sent from my mobile device
Click to expand...
Click to collapse
I tried installing Android_Revolution_HD-One_51.0 and One_4.18.401.8_odexed ROMS. I tried installing the Android_Revolution_HD ROM by adb sideload method both for the CWM and TWRP recoveries and it would actually start the AROMA installer and goes on to install but its premature installation. It just finishes fast (sometimes with a success flag but mostly with an error message saying META_INF error -- sorry i havent logged that error, so I am not putting the right wordings).
But now I am downloading the RUU for the 2.24.401.8 OS and I will give it a try. And I will get back to you.
tnx
are u s-off? make sure ur using twrp 2.6.3.3 and not 2.6.3.4, also do a full wipe/factory reset before you try flashing the rom
xnknown said:
are u s-off? make sure ur using twrp 2.6.3.3 and not 2.6.3.4, also do a full wipe/factory reset before you try flashing the rom
Click to expand...
Click to collapse
Hi,
No, I am not S-OFF at the moment. ( I have attached a snippet of my status on the phone from the fastboot getvar all command on my first thread)
So currently I have no OS installed and I am not sure if there is any tool that can do S-OFF without installed OS. I tried rumrunner tool but it didnt help either ( I read that its the option to go for if one has hboot version 1.54, which I happen to have)
So the error messages I am getting are as follows.... ( this is in CWM recovery)
E: Can't open /cache/recovery/last_install
E: Can't open /cache/recovery/log
mount: mounting /dev/block/mmcblk0p36 on /cache failed: Invalid argument
W: failed to mount /dev/block/mmcblk0p36 /File exists)
W: Can't unlink /cache/recovery/command
I appreciate your helps!
If you flash 2.6.3.4 TWRP recovery, and click install, is your SD card size 0?
sent from my mobile device
SaHiLzZ said:
If you flash 2.6.3.4 TWRP recovery, and click install, is your SD card size 0?
sent from my mobile device
Click to expand...
Click to collapse
TWRP 2.6.3.4 recovery is not working correct. It hangs saying "Entering Recovery...". It is something strange.
Fastboot erase cache in fastboot mode
Install the latest twrp by using the fastboot command.
Sideload through adb or store the ROM in your USB, mount USB drive using the usb-otg cable and then flash it from there.
Both methods should work
Sent from my One using XDA Premium HD app
EnIXmA said:
Fastboot erase cache in fastboot mode
Install the latest twrp by using the fastboot command.
Sideload through adb or store the ROM in your USB, mount USB drive using the usb-otg cable and then flash it from there.
Both methods should work
Sent from my One using XDA Premium HD app
Click to expand...
Click to collapse
I have tried Sideload having both latest recoveries of TWRP and CWM. Had problem to mount the cache partition (look earlier post). I will have to resort to the USB-OTG cable.
But I got myself in to a big and real problem now. I locked the oem from the fastboot command line thinking to run RUU.exe but it was a BAD BAD choice! Is there any hope for me now? Now my phone says
*****TAMPERED*****
*****RELOCKED*****
*****Security Warning*******
Oh boy! I am in real trouble. Please help!
SOLVED!
vvolverin said:
I have tried Sideload having both latest recoveries of TWRP and CWM. Had problem to mount the cache partition (look earlier post). I will have to resort to the USB-OTG cable.
But I got myself in to a big and real problem now. I locked the oem from the fastboot command line thinking to run RUU.exe but it was a BAD BAD choice! Is there any hope for me now? Now my phone says
*****TAMPERED*****
*****RELOCKED*****
*****Security Warning*******
Oh boy! I am in real trouble. Please help!
Click to expand...
Click to collapse
HI,
I finally managed to get the phone up and running. Thanks all for your prompt support.
So, what I did was, first I had to unlock using HTCdev unlock and then installed the latest TWRP recovery for the HTC One ( I think its 2.6.3.3 for HTC One and 2.6.3.4 might be for the HTC One X, because I couldn't manage to install it properly and I couldnt find the 2.6.3.4 version in a download list for the HTC One)....anyway after installing the custom recovery I tried installing stock ROM ( latest from Android Revolution HD --- One_4.19.401.8 OS version.
Oh I am so relieved...its been a good learning process anyway but not so nice if one has just one phone to play with. I probably have missed some important phone calls during the time my phone was down
Once again Thumbs up, Kudos for all those who answered to my desperate questions and Mike1986 for the nice work you are doing!
I'm sorry to do this, but I don't know where to start. Here's what I did to get to where I'm at:
- previously running SlimBean flashed using TWRP
- Downloaded ROM Manager and it recommended installing CWM Recovery
- Followed prompts
- It installed CWM 6.0.4.8
- Booted back into ROM and used ROM Manager to attempt to flash SlimKat 4.4.2 build 6
- CWM wiped dalvik but then got hung up
- Now it keeps saying Can't mount /cache/recovery/command
I'm completely stuck. Can't figure out what to do next. Please help!!!
Have you tryed reflashing the recovery to rule out a faulty install of cwm?
I should say, have you tried reflashing cwm *through Fastboot* to rule out a faulty cwm install?
Use TWRP recovery, preferred is 2.6.3.3 although there are newer versions, enter recovery, wipe - format data, basically for some reason, fastboot erase cache wipes the cache into an un-readable format.
note: this will also erase your internal storage too, so if theres anything important you want on there, make sure you back it up first using the adb pull command.
dougeedug said:
Have you tryed reflashing the recovery to rule out a faulty install of cwm?
I should say, have you tried reflashing cwm *through Fastboot* to rule out a faulty cwm install?
Click to expand...
Click to collapse
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
Seanie280672 said:
Use TWRP recovery, preferred is 2.6.3.3 although there are newer versions, enter recovery, wipe - format data, basically for some reason, fastboot erase cache wipes the cache into an un-readable format.
note: this will also erase your internal storage too, so if theres anything important you want on there, make sure you back it up first using the adb pull command.
Click to expand...
Click to collapse
I can't quite risk doing this yet. Only as a last, last resort...
cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
I can't quite risk doing this yet. Only as a last, last resort...
Click to expand...
Click to collapse
whilst your phone is in recovery and plugged into your computer, open device manager, is there a yellow ! where its says android devices or myHTC ?
IGNORE THIS, You got it working whilst I was typing this.
cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed.
Click to expand...
Click to collapse
Use the command "fastboot devices" from the bootloader with "fastbootUSB" highlighted. You can't use adb commands in the bootloader because adb is to interact with android, which is not running while in bootloader. Let me know if you get output with the "fastboot devices" command.
EDIT: I should specify, if you are trying to flash recovery from anywhere but the bootloader using fastboot commands (it sounds like you may be trying to flash recovery with adb commands), you are just doing it wrong. so lets get that sorted first.
cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
Click to expand...
Click to collapse
you flash a custom recovery with fastboot commands not adb commands.
Got it!!! Thank you everyone for taking the time. I have a flight in a few hours and I was panicking!!!!
I grabbed universal drivers from here: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi (remove the brackets around .com)
Then my computer picked up the device and I was able to install TWRP. Clockworkmod recovery still doesn't work, no matter which version I tried. I'll stick with TWRP for now.
Thanks again!
EDIT: Well eff me, it wiped my internal storage. It must have done it after I flashed because that's where I grabbed the zip in the first place. That sucks...
cartisdm said:
Got it!!! Thank you everyone for taking the time. I have a flight in a few hours and I was panicking!!!!
I grabbed universal drivers from here: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi (remove the brackets around .com)
Then my computer picked up the device and I was able to install TWRP. Clockworkmod recovery still doesn't work, no matter which version I tried. I'll stick with TWRP for now.
Thanks again!
EDIT: Well eff me, it wiped my internal storage. It must have done it after I flashed because that's where I grabbed the zip in the first place. That sucks...
Click to expand...
Click to collapse
did you format data inside twrp recovery, like I said above, that will erase your internal storage too, you will need to push a rom over to your internal storage now using adb and then flash it.
Seanie280672 said:
did you format data inside twrp recovery, like I said above, that will erase your internal storage too, you will need to push a rom over to your internal storage now using adb and then flash it.
Click to expand...
Click to collapse
I didn't do so intentionally, but it's possible I did it without paying attention. I'm back to my system now so I'll just live with the loss. I flashed an existing ROM that I had in my Downloads folder once I was able to get into TWRP. It's just weird that folder is empty now.
Hi guys,
Ive not come across this before i'm hoping some of you can help please, i not a complete noob in the fact i've been flashing roms for a few years now but i'm by no means an expert!!
my htc in on latest firmware and was running maximus lolipop 50.0 and im s off.
I was flashing ARHD and had a bad flash. it hung when flashing and I was forced to put it back into bootloader upon attempting to flash again each rom I tried started to fail, ARHD and maximus. I realized TWRP was giving the error unable to mount storage wwhich seemed to be causing the issue. I been looking through XDA for a couple of hours now for a answer and tried lots of different things to fix this re flash twrp , factory reset, tried to sideload roms but that failed and was about to flash stock recovery when I mistakenly flashed twrp 2.6.3.3, I thought I would try to flash the new ARHD lollipop on this recovery even though i thought lollipop require 2.8.4.0 but ive literally just flashed it and it installed fine and ive just set the phone back up.
I want to re-flash recovery 2.8.4.0 but i've got a feeling that im going to run back into the mount storage issue does anyone have any knowledge on this issue? i also found it strange I had the issue with 2.8.4.0 and re-flashing didn't cure it but with older 2.6.3.3 it still said unable to mount storage but flashed the rom without any issues?
any help is appreciated thanks guys.
billyjonstevens said:
Hi guys,
Ive not come across this before i'm hoping some of you can help please, i not a complete noob in the fact i've been flashing roms for a few years now but i'm by no means an expert!!
my htc in on latest firmware and was running maximus lolipop 50.0 and im s off.
I was flashing ARHD and had a bad flash. it hung when flashing and I was forced to put it back into bootloader upon attempting to flash again each rom I tried started to fail, ARHD and maximus. I realized TWRP was giving the error unable to mount storage wwhich seemed to be causing the issue. I been looking through XDA for a couple of hours now for a answer and tried lots of different things to fix this re flash twrp , factory reset, tried to sideload roms but that failed and was about to flash stock recovery when I mistakenly flashed twrp 2.6.3.3, I thought I would try to flash the new ARHD lollipop on this recovery even though i thought lollipop require 2.8.4.0 but ive literally just flashed it and it installed fine and ive just set the phone back up.
I want to re-flash recovery 2.8.4.0 but i've got a feeling that im going to run back into the mount storage issue does anyone have any knowledge on this issue? i also found it strange I had the issue with 2.8.4.0 and re-flashing didn't cure it but with older 2.6.3.3 it still said unable to mount storage but flashed the rom without any issues?
any help is appreciated thanks guys.
Click to expand...
Click to collapse
You may want to post about this in the ARHD thread. Many users are having problems with storage after flashing the Rom with 2.8.4.0. Based on your experience it seems the issue may be with the new TWRP rather than the new Rom. :good:
Anyway if you have successfully flashed the rom. Changing your recovery now should not cause any problems. It seems to be the data wipe in Aroma during the install that causes the issue. In any case TWRP 2.6.3.3 has for a long time and still is considered the most stable and reliable version. A number of users have confirmed it flashes the new ARHD without issues so maybe your better off staying with 2.6.3.3 I know I will be
billyjonstevens said:
Hi guys,
Ive not come across this before i'm hoping some of you can help please, i not a complete noob in the fact i've been flashing roms for a few years now but i'm by no means an expert!!
my htc in on latest firmware and was running maximus lolipop 50.0 and im s off.
I was flashing ARHD and had a bad flash. it hung when flashing and I was forced to put it back into bootloader upon attempting to flash again each rom I tried started to fail, ARHD and maximus. I realized TWRP was giving the error unable to mount storage wwhich seemed to be causing the issue. I been looking through XDA for a couple of hours now for a answer and tried lots of different things to fix this re flash twrp , factory reset, tried to sideload roms but that failed and was about to flash stock recovery when I mistakenly flashed twrp 2.6.3.3, I thought I would try to flash the new ARHD lollipop on this recovery even though i thought lollipop require 2.8.4.0 but ive literally just flashed it and it installed fine and ive just set the phone back up.
I want to re-flash recovery 2.8.4.0 but i've got a feeling that im going to run back into the mount storage issue does anyone have any knowledge on this issue? i also found it strange I had the issue with 2.8.4.0 and re-flashing didn't cure it but with older 2.6.3.3 it still said unable to mount storage but flashed the rom without any issues?
any help is appreciated thanks guys.
Click to expand...
Click to collapse
I don't know what this issue is, but ive noticed a similar problem with TWRP 2.8.4.0, when wiping or restoring a rom I kept getting a error, something like E:Unable to mount internal storage at sector 65547 (cant remember the exact number), I cured it by using TWRP 2.7.1.1, formatting data and a full wipe then re-flashing MaximusHD50 using 2.7.1.1, I think its probably just a problem with TWRP and not your device itself, nothing to worry about.
I appreciate your response guy's, I'll try and update to 2.7.1.1 and see how I get on
Sent from my HTC One using XDA Premium 4 mobile app
billyjonstevens said:
I appreciate your response guy's, I'll try and update to 2.7.1.1 and see how I get on
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So are you still having problems with your storage?
e2fsck in recovery may fix it without you needing to format the device
---------- Post added at 06:19 PM ---------- Previous post was at 06:15 PM ----------
If you want to try it here's how
With the phone in twrp go into mount options and uncheck all boxes, connect your usb cable to your pc and start a cmd window at your Fastboot folder. Then type
Code:
adb devices
To check adb is working. If it is then follow up with these commands
Code:
adb shell
e2fsck -fvy dev/block/mmcblk0p35
e2fsck -fvy dev/block/mmcblk0p36
e2fsck -fvy dev/block/mmcblk0p37
exit
Danny201281 said:
So are you still having problems with your storage?
e2fsck in recovery may fix it without you needing to format the device
---------- Post added at 06:19 PM ---------- Previous post was at 06:15 PM ----------
If you want to try it here's how
With the phone in twrp go into mount options and uncheck all boxes, connect your usb cable to your pc and start a cmd window at your Fastboot folder. Then type
Code:
adb devices
To check adb is working. If it is then follow up with these commands
Code:
adb shell
e2fsck -fvy dev/block/mmcblk0p35
e2fsck -fvy dev/block/mmcblk0p36
e2fsck -fvy dev/block/mmcblk0p37
exit
Click to expand...
Click to collapse
Thanks Danny, I think it's fine but I'll check recovery again, if it's still having issues do I literally type those commands using fastboot ?
billyjonstevens said:
Thanks Danny, I think it's fine but I'll check recovery again, if it's still having issues do I literally type those commands using fastboot ?
Click to expand...
Click to collapse
Basically the same thing yes. Open the command window the same as with fastboot. Only the phone should be in recovery rather than on the bootloader :good:
Bootloader = Fastboot commands
Recovery = adb commands
There's also another fix posted in the ARHD thread here http://forum.xda-developers.com/showthread.php?p=58416746
Great thanks Danny
Danny201281 said:
Basically the same thing yes. Open the command window the same as with fastboot. Only the phone should be in recovery rather than on the bootloader :good:
Bootloader = Fastboot commands
Recovery = adb commands
There's also another fix posted in the ARHD thread here http://forum.xda-developers.com/showthread.php?p=58416746
Click to expand...
Click to collapse
billyjonstevens said:
Great thanks Danny
Click to expand...
Click to collapse
Seems easier to post the fix than a link to it
All you have to do is type in these 2 lines in your terminal emulator on your android device:
Su
restorecon -FR /data/media/0
And your storage will be back to normal
Click to expand...
Click to collapse
Also, I used TWRP 2.8.4.0 and ARHD 90 / Wiped in TWRP and Aroma and never had any problems
clsA said:
Seems easier to post the fix than a link to it
Click to expand...
Click to collapse
Yeah Probably call me selfish but I was waiting for my ride home from work which turned up as I was writing my post so it was easier for me to just grab the link [emoji14]
Danny201281 said:
Yeah Probably call me selfish but I was waiting for my ride home from work which turned up as I was writing my post so it was easier for me to just grab the link [emoji14]
Click to expand...
Click to collapse
yeah yeah excuses excuses ... I figured you had the fix memorized by now it's been around since Lollipop GPe