By mistake I did an Advanced Wipe of my HTC and wiped everything. Now to install a new ROM I need to put the ROM on the phone, and for that I tried mounting the data from TWRP 2.8 recovery but ADB showed no devices attached. I tried ADB sideload but the progress bar was stuck for about half an hour. I also tried flashing CWM recovery but couldn't mount from there too.
Can someone please help me mount the phone?
P.S. - I am using Ubuntu 14.04
rahulwadhwani said:
By mistake I did an Advanced Wipe of my HTC and wiped everything. Now to install a new ROM I need to put the ROM on the phone, and for that I tried mounting the data from TWRP 2.8 recovery but ADB showed no devices attached. I tried ADB sideload but the progress bar was stuck for about half an hour. I also tried flashing CWM recovery but couldn't mount from there too.
Can someone please help me mount the phone?
P.S. - I am using Ubuntu 14.04
Click to expand...
Click to collapse
have you tried an older version of TWRP? maybe it's a bug in 2.8.0.0
(i haven't tested it, so can't say for sure)
nkk71 said:
have you tried an older version of TWRP? maybe it's a bug in 2.8.0.0
(i haven't tested it, so can't say for sure)
Click to expand...
Click to collapse
I flashed CWM and it worked like a charm for me.
Maybe TWRP was buggy.
Edit : grammatical error
rahulwadhwani said:
I flashed CWM and it worked as a charm for me.
Maybe TWRP was buggy.
Click to expand...
Click to collapse
could be i haven't tried it (yet?), but I recommend you stick with
TWRP 2.6.3.3 (good for Sense based ROMs; CWM will most likely fail for 4.4+ ROMs due to missing SELinux support)
TWRP 2.7.1.1 (but this will erase the firmware version text from your "getvar all") but is needed for CM11 and possibly other ROMs that need a recovery with by-name support
TWRP 2.7.1.2+ (but be careful about possible factory reset this)
---------- Post added at 05:59 PM ---------- Previous post was at 05:19 PM ----------
rahulwadhwani said:
When I was trying to push the Rom to my phone, it was not happening with TWRP, that's why I switched to CWM and not it isn't booting up.
What do you suggest doing now?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
first off stick with one thread, so let's stay here, let the other one die out
as i mentioned, you'll need to go with TWRP 2.6.3.3 or higher depending on the ROM
if you are going for ARHD 81.0, then use TWRP 2.6.3.3, it's working fine for me
also please check the faq sticky http://forum.xda-developers.com/showpost.php?p=53270352&postcount=21
let me know if you encounter other problems, by posting back here.
check the device manager. That was the problem in my case. The windows device manager did not recognize the driver. After updating this one it worked
leoncornelissen said:
check the device manager. That was the problem in my case. The windows device manager did not recognize the driver. After updating this one it worked
Click to expand...
Click to collapse
I am on Ubuntu 14.04 and not on Windows.
nkk71 said:
could be i haven't tried it (yet?), but I recommend you stick with
TWRP 2.6.3.3 (good for Sense based ROMs; CWM will most likely fail for 4.4+ ROMs due to missing SELinux support)
TWRP 2.7.1.1 (but this will erase the firmware version text from your "getvar all") but is needed for CM11 and possibly other ROMs that need a recovery with by-name support
TWRP 2.7.1.2+ (but be careful about possible factory reset this)
---------- Post added at 05:59 PM ---------- Previous post was at 05:19 PM ----------
first off stick with one thread, so let's stay here, let the other one die out
as i mentioned, you'll need to go with TWRP 2.6.3.3 or higher depending on the ROM
if you are going for ARHD 81.0, then use TWRP 2.6.3.3, it's working fine for me
also please check the faq sticky http://forum.xda-developers.com/showpost.php?p=53270352&postcount=21
let me know if you encounter other problems, by posting back here.
Click to expand...
Click to collapse
The problem now is that I am not able to mount the device. Adb says "Device not found" (tried all USB ports) and ADB Sideload also isn't working. It has been stuck with the progress bar for almost 10 minutes.
How should I transfer the ROM to the phone now?
rahulwadhwani said:
The problem now is that I am not able to mount the device. Adb says "Device not found" (tried all USB ports) and ADB Sideload also isn't working. It has been stuck with the progress bar for almost 10 minutes.
How should I transfer the ROM to the phone now?
Click to expand...
Click to collapse
which recovery are you using?
nkk71 said:
which recovery are you using?
Click to expand...
Click to collapse
TWRP 2.6.3.3
Related
I used to run TWRP 2.5.0.0 without any problems, since the OTA 4.3 update the touchscreen in TWRP 2.5.0.0 no longer works. for some reason TWRP 2.5.0.0 is the only recovery that would work with usb-otg and ADB, does anyone know how to either wipe and install a new rom only using ADB commnds in twrp, or how to get my USB-OTG and ADB working in TWRP 2.6.3? the phone currently is listed as M7WLS in the device manager while in any recovery besides TWRP 2.5.0.0
did you try adb sideload (nameofrom).zip ? using sideload in twrp.
i cant seem to get my OTG USB to work at all. it will not mount the usb no matter what i do.
only twrp 2.5.0.0 works with adb or usb otg
rchris494 said:
did you try adb sideload (nameofrom).zip ? using sideload in twrp.
i cant seem to get my OTG USB to work at all. it will not mount the usb no matter what i do.
Click to expand...
Click to collapse
sideload does not work since the phone is improperly recognized as m7wls in device manager on any recovery besides twrp 2.5.0.0
I had the same issue with twrp & otg on 4.3. I updated to twrp 2.6.3.0 & still had issues sideloading after a complete wipe in twrp. I just read that flashing philztouch from bootloader helped someone to sideload a rom. I haven't tried it yet-so fill us in if you have any luck with philztouch. I love twrp, but i'll use anything that works. We are all learning, so ur best bet is to always take the time to backup before u try anything.
Sent from my HTCONE using Tapatalk 4
tonyrance said:
I had the same issue with twrp & otg on 4.3. I updated to twrp 2.6.3.0 & still had issues sideloading after a complete wipe in twrp. I just read that flashing philztouch from bootloader helped someone to sideload a rom. I haven't tried it yet-so fill us in if you have any luck with philztouch. I love twrp, but i'll use anything that works. We are all learning, so ur best bet is to always take the time to backup before u try anything.
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
DNasingh has a 1.29 touch panel thread with a flashable zip in the general section. Flash the zip in your bootloader, then flash twrp 2.5.0.0.
Hope that helps
Sent from my HTCONE using XDA Premium 4 mobile app
---------- Post added at 09:32 PM ---------- Previous post was at 09:24 PM ----------
thanosart said:
DNasingh has a 1.29 touch panel thread with a flashable zip in the general section. Flash the zip in your bootloader, then flash twrp 2.5.0.0.
I use otg cable a lot and this worked to get back to twrp 2.5.0.0
Hope that helps
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my HTCONE using XDA Premium 4 mobile app
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
thanosart said:
DNasingh has a 1.29 touch panel thread with a flashable zip in the general section. Flash the zip in your bootloader, then flash twrp 2.5.0.0.
Hope that helps
I use my otg cable a lot and this solved that issue.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanosart said:
DNasingh has a 1.29 touch panel thread with a flashable zip in the general section. Flash the zip in your bootloader, then flash twrp 2.5.0.0.
Hope that helps
Sent from my HTCONE using XDA Premium 4 mobile app
---------- Post added at 09:32 PM ---------- Previous post was at 09:24 PM ----------
Sent from my HTCONE using XDA Premium 4 mobile app
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
thanosart said:
DNasingh has a 1.29 touch panel thread with a flashable zip in the general section. Flash the zip in your bootloader, then flash twrp 2.5.0.0.
Hope that helps
I use my otg cable a lot and this solved that issue.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do u mind sharing that link please? I'd like to check it out. Does the touch screen still work?
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
Touch screen in twrp 2.5.0.0 will work. Can't post a link right now but the thread is in the general section. Look for 1.29 touch panel firmware
Sent from my HTCONE using XDA Premium 4 mobile app
TravisAnthony07 said:
I used to run TWRP 2.5.0.0 without any problems, since the OTA 4.3 update the touchscreen in TWRP 2.5.0.0 no longer works. for some reason TWRP 2.5.0.0 is the only recovery that would work with usb-otg and ADB, does anyone know how to either wipe and install a new rom only using ADB commnds in twrp, or how to get my USB-OTG and ADB working in TWRP 2.6.3? the phone currently is listed as M7WLS in the device manager while in any recovery besides TWRP 2.5.0.0
Click to expand...
Click to collapse
Same problem to me. Solution= Install CWM recovery 6.0.3.1 Touch. work perfect!!!
TWRP 2.5.0.0 the only working recovery with usb otg/adb sideload
still no good, i have tried all versions of CWM including philZ and TWRP but TWRP 2.5.0.0 is the only recovery that will let me use usb-otg or adb sideload (would love to fix this if anyone knows how) and i am unable to set S-off because i can not push revone, for some reason my phone says adb device offline even with debugging enabled
TravisAnthony07 said:
sideload does not work since the phone is improperly recognized as m7wls in device manager on any recovery besides twrp 2.5.0.0
Click to expand...
Click to collapse
You have to update the driver when in recovery.. or else it will show up m7wls
Sent from my HTCONE using Tapatalk 2
TravisAnthony07 said:
still no good, i have tried all versions of CWM including philZ and TWRP but TWRP 2.5.0.0 is the only recovery that will let me use usb-otg or adb sideload (would love to fix this if anyone knows how) and i am unable to set S-off because i can not push revone, for some reason my phone says adb device offline even with debugging enabled
Click to expand...
Click to collapse
usb-otg work on CWM 6.0.4.3 but you not gonna see a usb-otg. Just plug-in the usb-otg and automatic mount /storage/usbdisk
im sorry!! i said CWM 6.0.3.1 in my last post. I mean CWM 6.0.4.3 I www.clockworkmod.com/rommanager. look for htc one (sprint) and flash the IMG.
new CWM works
Pacemaker2 said:
usb-otg work on CWM 6.0.4.3 but you not gonna see a usb-otg. Just plug-in the usb-otg and automatic mount /storage/usbdisk
im sorry!! i said CWM 6.0.3.1 in my last post. I mean CWM 6.0.4.3 I www.clockworkmod.com/rommanager. look for htc one (sprint) and flash the IMG.
Click to expand...
Click to collapse
the new CWM was able to mount my usb automatically and my problem is solved, ty. But i wonder, why is every other recovery but the newest CWM and TWRP 2.5 unable to use the usb?
Didn't find out about this issue until it was too late
I decided to back everything up onto my laptop and wipe the phone clean including the internal card and then install a new ROM from the USB-OTG
Problem is I didn't realize until I tried it that TWRP 2.6.3 won't mount or recognize USB to either install the ROM or push another recovery onto the phone
Help would be greatly appreciated.
jmp485 said:
I decided to back everything up onto my laptop and wipe the phone clean including the internal card and then install a new ROM from the USB-OTG
Problem is I didn't realize until I tried it that TWRP 2.6.3 won't mount or recognize USB to either install the ROM or push another recovery onto the phone
Help would be greatly appreciated.
Click to expand...
Click to collapse
I have done the same exact thing. Any help would be greatly appreciated as well.
Fixed mine
kpahl1973 said:
I have done the same exact thing. Any help would be greatly appreciated as well.
Click to expand...
Click to collapse
I was able to flash the CWM recovery through fastboot then install my ROM the way I wanted to originally. I'm uploading my files now
jmp485 said:
I was able to flash the CWM recovery through fastboot then install my ROM the way I wanted to originally. I'm uploading my files now
Click to expand...
Click to collapse
Just did the same thing. Rom is booting up now. Thanks for the suggestion!
Hi, I have a ATT HTC One I got yesterday. Was rooted, had an old ROM on it, unlocked, s-off, hboot 1.44. I tried to flash a PGe rom on it and it became stuck in TWRP. I can get adb, but sideloading a rom doesn't work. It says it flashes but will not boot. Can get into the bootloader, but can't get fastboot. Really frustrated, any help would be much appreciated. Thanks!
i was also got same problem with you
and to boot to TWRP i use CMD : Fastboot boot recovery.img
and then i can successfully go to TWRP settings
fndfendy said:
i was also got same problem with you
and to boot to TWRP i use CMD : Fastboot boot recovery.img
and then i can successfully go to TWRP settings
Click to expand...
Click to collapse
I can get into TWRP no problem. And I can get adb there, but can't flash a rom, always fails. Anyone else have any ideas?
schufly said:
I can get into TWRP no problem. And I can get adb there, but can't flash a rom, always fails. Anyone else have any ideas?
Click to expand...
Click to collapse
have you tried pushing rom instead of sideloading it??
got to recovery and try this
adb push rom.zip /data/media/0/
or
adb push rom.zip
Harish_Kumar said:
have you tried pushing rom instead of sideloading it??
got to recovery and try this
adb push rom.zip /data/media/0/
or
adb push rom.zip
Click to expand...
Click to collapse
I will try that. I am also using a windows 8 laptop, which may be part of my issue in getting the phone recognized in fastboot. I am trying to locate a windows 7 computer to use. I am also downloading the correct Guru file for it, but can't try it till I get home tonight because I can't install HTC drivers on my work computer.
I have been rooting phones since I had my HTC Hero and never had this much trouble or bricked a phone, let alone had to leave one down overnight. I am humbled......lol
I was also considering trying to load a nandroid backup. IF I do, and I can push it, what location does it need to go to??
schufly said:
I was also considering trying to load a nandroid backup. IF I do, and I can push it, what location does it need to go to??
Click to expand...
Click to collapse
what TWRP version are you using, and what are you installing?
If you're flashing a 4.4 ROM, then you will need TWRP 2.6.3.3, otherwise it will bootloop.
and for GPE 4.4 you also need S-Off.
nkk71 said:
what TWRP version are you using, and what are you installing?
If you're flashing a 4.4 ROM, then you will need TWRP 2.6.3.3, otherwise it will bootloop.
and for GPE 4.4 you also need S-Off.
Click to expand...
Click to collapse
Was about to say same, except if it's a 4.4 ROM it will fail install, not bootloop...........TWRP 2.6.3.4 is available now also.
CaelanT said:
Was about to say same, except if it's a 4.4 ROM it will fail install, not bootloop...........TWRP 2.6.3.4 is available now also.
Click to expand...
Click to collapse
havent had a chance to check, but is .4 stable? iirc it didnt work for someone for 4.4 but .3 did.
nkk71 said:
havent had a chance to check, but is .4 stable? iirc it didnt work for someone for 4.4 but .3 did.
Click to expand...
Click to collapse
I flashed Insertcoin with 2.6.3.3, but haven't tried 2.6.3.4 with 4.4 as it was released after. Using 2.6.3.4 on my phone now with no other issues though. I know to never assume, but I did assume that later revisions than 2.6.3.3 should also work. Maybe someone can clarify.
<edit> Here ---> http://forum.xda-developers.com/showpost.php?p=48364016&postcount=1107
CaelanT said:
I flashed Insertcoin with 2.6.3.3, but haven't tried 2.6.3.4 with 4.4 as it was released after. Using 2.6.3.4 on my phone now with no other issues though. I know to never assume, but I did assume that later revisions than 2.6.3.3 should also work. Maybe someone can clarify.
<edit> Here ---> http://forum.xda-developers.com/showpost.php?p=48364016&postcount=1107
Click to expand...
Click to collapse
Thanks, downloading
---------- Post added at 06:23 PM ---------- Previous post was at 06:10 PM ----------
CaelanT said:
I flashed Insertcoin with 2.6.3.3, but haven't tried 2.6.3.4 with 4.4 as it was released after. Using 2.6.3.4 on my phone now with no other issues though. I know to never assume, but I did assume that later revisions than 2.6.3.3 should also work. Maybe someone can clarify.
<edit> Here ---> http://forum.xda-developers.com/showpost.php?p=48364016&postcount=1107
Click to expand...
Click to collapse
so i checked, but it doesn't say why it's under m7ul now. any reason it wouldnt work with an m7u?
I'm stuck with TWRP 2.6.3.0 unfortunately.....
Solved my problem. Used a Windows Vista computer, and a different cable, was able to get fastboot to work and used a RUU to get back to stock. Got rid of TWRP and put on the newwest CWM recovery and a new rom. Thanks to all that helped!
For some stupid reason I thought I had S-Off. Installed a rom that required S-Off.
Phone boots to the "select language screen", then reboots itself. Does this continuously.
Can't mount my phone to my computer either. Any ideas?
Phone is unlocked and rooted.
Didn't do a backup either.
You can install roms with s-on. Boot into recovery and install another rom. If problem continues you can fastboot erase cache.
Sent from my iPad using Tapatalk
I don't have any other roms on my phone.
Nawzlew said:
I don't have any other roms on my phone.
Click to expand...
Click to collapse
do you have custom recovery? TWRP?
---------- Post added at 09:20 PM ---------- Previous post was at 09:13 PM ----------
flash TWRP recovery 2.6.3.3 for M7 if you have international M7
Reboot into recovery.
Now make a Wipe of the phone like when you installing new ROM.
Now Select mount
Tick DATA and just data. System and Cache must be unchecked. Leave it there for now.
Now download new ROM you want and put it into your fastboot folder with adb.exe and fastboot.exe files in it if you know what i mean.
Now start fastboot and write following adb push rom.zip /sdcard/. and hit enter. Wait a couple of minutes until you see that files are transfered.
now go back from mount in TWRP until you see the rom file. FLASH the ROM...
Tried two roms and it fails when trying to flash.
I'll try and download some others ...
Nawzlew said:
Tried two roms and it fails when trying to flash.
I'll try and download some others ...
Click to expand...
Click to collapse
Did you flash the recovery i said to you?
Wich roms are you trying to flash?
Nevermind, I kept flashing the same rom and it worked.
THANK YOU so much.
Nawzlew said:
Nevermind, I kept flashing the same rom and it worked.
THANK YOU so much.
Click to expand...
Click to collapse
No problem. Glad you fixed it. Remember you can allways push a rom into a HTC ONE if you wiping **** out of it.
Just be sure to be on custom recovery like TWRP 2.6.3.3 or 2.6.3.4
Good luck
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
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