Related
Ok, here is the problem:
I unlock bootloader over htcdev and flash latest CM7. Before unlocking bootloader, i din't have rooted DHD and i didn't S-OFF it...
Therefore, I just have unlocked bootlader.
After 7 days on CM7, DHD started sporadically to show FC on some applications, but I didn't pay attention on that, try to start app again and it's worked.
After few days, FC was a very frequent and become very, very frustrating...
I did full wipe, wipe cache and Dalvik cache and restore CM7. Result was better but can't say that I solve my problem. After one more day of usage I cant start any app on phone. Try to flash again Cm7 wasn't succesful. Recovery started to show messages:
Code:
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
I couldn't wipe cache, factory, dalvik, couldn't restore or flash new ROM. Nothing. It said that can't mount format /data, /cache, /system
I send it to service where I bought phone, but after 7 days they don't know what is problem. Unbelievable! They said that that will try to solve my problem in next 45 days because they have that clause in warranty What to do 45 days without phone?
I try everything what is common with my problem from XDA but without success The only thing which I didnt tried is that replace SD card with new one...
What you think, can SD card make phone to stuck on HTC logo
PS. I have M4G2DE eMMC chip
Bloody hell!
mikronac.ns said:
Ok, here is the problem:
I unlock bootloader over htcdev and flash latest CM7. Before unlocking bootloader, i din't have rooted DHD and i didn't S-OFF it...
Therefore, I just have unlocked bootlader.
After 7 days on CM7, DHD started sporadically to show FC on some applications, but I didn't pay attention on that, try to start app again and it's worked.
After few days, FC was a very frequent and become very, very frustrating...
I did full wipe, wipe cache and Dalvik cache and restore CM7. Result was better but can't say that I solve my problem. After one more day of usage I cant start any app on phone. Try to flash again Cm7 wasn't succesful. Recovery started to show messages:
Code:
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
I couldn't wipe cache, factory, dalvik, couldn't restore or flash new ROM. Nothing. It said that can't mount format /data, /cache, /system
I send it to service where I bought phone, but after 7 days they don't know what is problem. Unbelievable! They said that that will try to solve my problem in next 45 days because they have that clause in warranty What to do 45 days without phone?
I try everything what is common with my problem from XDA but without success The only thing which I didnt tried is that replace SD card with new one...
What you think, can SD card make phone to stuck on HTC logo
PS. I have M4G2DE eMMC chip
Bloody hell!
Click to expand...
Click to collapse
Ok, relax...with an unlocked bootloader (HTCDEV) you have to flash the rom in CWM and after you will have to flash the boot.img file inside that zip folder.
Find the boot.img file inside the rom folder and put it in somewhere u can find it in the PC.
Open a cmd as admin or terminal as root in the PC
Navigate to where the boot.img file is located
Type adb devices to check that u have connectivity (usb debugging and charge only have to be set)
If the above was succesfull, type: adb reboot-bootloader (it will boot in fastboot usb)
In cmd navigate to where the boot.img is located (it should read something like c:\users\your_user\desktop)
Type: fastboot flash boot boot.img
ENJOY
glevitan said:
Ok, relax...with an unlocked bootloader (HTCDEV) you have to flash the rom in CWM and after you will have to flash the boot.img file inside that zip folder.
Type adb devices to check that u have connectivity (usb debugging and charge only have to be set)
Click to expand...
Click to collapse
I cant start phone. It stuck at on htc logo. I CAN NOT enable usb debugging, ok?
I tried to flash boot.img, file is sent to phone but it report me an error that flashing cant be done...
mikronac.ns said:
I cant start phone. It stuck at on htc logo. I CAN NOT enable usb debugging, ok?
I tried to flash boot.img, file is sent to phone but it report me an error that flashing cant be done...
Click to expand...
Click to collapse
Ok, then u will have to re flash the RUU...in fastboot you should be able to flash the boot.img
If that is failing then something else is wrong.
Tried to flash RUU. Tried everything
mikronac.ns said:
Tried to flash RUU. Tried everything
Click to expand...
Click to collapse
ok, the ruu wont flash with an unlocked bootloader....do you have your official ruu??
Do you have CWM or the stock recovery?
glevitan said:
ok, the ruu wont flash with an unlocked bootloader....do you have your official ruu??
Do you have CWM or the stock recovery?
Click to expand...
Click to collapse
Ops, I did't know that RUU cant be flashed with unlocked BL
I have CWM recovery...
mikronac.ns said:
Ops, I did't know that RUU cant be flashed with unlocked BL
I have CWM recovery...
Click to expand...
Click to collapse
ok...if you have the official RUU for your phone then relock the bootloader...do you know how to do that?
and then just flash it the usual manner (PD98IMG.zip)...
glevitan said:
ok...if you have the official RUU for your phone then relock the bootloader...do you know how to do that?
and then just flash it the usual manner (PD98IMG.zip)...
Click to expand...
Click to collapse
Now, it is late, phone is on service... They told me that they will flash it with "HTC BOX", and if that fail, then I have problem with fried eMMC or CPU.
mikronac.ns said:
Now, it is late, phone is on service... They told me that they will flash it with "HTC BOX", and if that fail, then I have problem with fried eMMC or CPU.
Click to expand...
Click to collapse
ok...if your emmc chip was corrupted there is no other way to fix but to have the Motherboard replaced...
glevitan said:
ok...if your emmc chip was corrupted there is no other way to fix but to have the Motherboard replaced...
Click to expand...
Click to collapse
If they replace motherboard, will my IMEI be changed or it will stay the same? How to check if my MB changed or not?
mikronac.ns said:
If they replace motherboard, will my IMEI be changed or it will stay the same? How to check if my MB changed or not?
Click to expand...
Click to collapse
They will tell you...or ask them...I don't think that the imei will change but not sure about that.
Original thread
For over a month, I ran SinLessROM flawlessly on my Verizon HTC One (M8). Last week, I woke up with a slow and laggy phone which abruptly shut down after a few seconds of bizarre behavior. Since that time, I have not been able to boot the device past the initial ROM splash screen. I am running TWRP 2.7.1.0 and I am still able to boot into the recovery partition. However, once I am in TWRP, I cannot mount '/data' and the internal storage displays a capacity of 0 MB. Furthermore, no matter what I try, I am unable to modify anything in the phone's memory contents. Write operations such as a reformat are reported to be successful, but upon inspection of the phone's memory, nothing is actually changed. I suspect this to be a NAND failure. Below is a list of everything I've tried so far:
Rebooted countless times
Allowed phone to idle in recovery for prolonged periods of time
TWRP - Erased cache+dalvik; flashed ROM via USB-OTG
TWRP - Erased cache+dalvik; flashed ROM via ADB sideload
TWRP - Erased cache, dalvik system, and data; flashed ROM via USB-OTG
Erased cache via fastboot; re-flashed ROM via USB-OTG in TWRP
Fastboot - Erased cache and re-flashed TWRP
Fastboot - Erased cache and flashed philz touch (did not change recovery partition; still boots to TWRP)
Fastboot - Attempted to boot to RUU (resulted in boot loop)
Hboot - Flashed stock RUU per instructions found in this thread (option 2)
TWRP - File system repair
TWRP - Fix permissions
TWRP - Format data
TWRP - Factory reset
TWRP - Locked + unlocked bootloader per instructions found in this thread (with reboot in between)
Fastboot - Changed from Verizon CID to SuperCID (command executed successfully, but CID was unchanged)
When I attempted to change the bootloader flag in memory via the dd command, everything executed without error. However, I decided to use the dd command again to read from that same address and the value was unchanged. Since that point, I've been pretty much convinced that this has to be a memory hardware issue. I would love to be proven wrong and if anyone has any advice or input, I would be greatly appreciative to hear it. Thanks in advance.
Ok are you currently s-on or s-off?
also what are the stats on your boot screen? OS? Hboot version so on.
Hmm. Writing up a list of what you tried is very helpful, kudos to that. I had the whole "unable to mount /data, /internal storage the other day in twrp, and tried a plethora of " solutions". The only one for me that worked was twrp > wipe > format data.
I see you have not tried the RUU why not give that a go? Vzw doesn't have a full RUU available but the one we have in vzw android dev is more than enough for most people
If that fails why don't you try formatting the phone in windows device manager? (Someone from these forums reported that this fixed their unable to mount data options although I can't guarantee the results.)
agentbardall said:
Ok are you currently s-on or s-off?
also what are the stats on your boot screen? OS? Hboot version so on.
Click to expand...
Click to collapse
I'm S-off.
Here' what Hboot says:
Code:
*** UNLOCKED ***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 1 2014,00:26:53.197
wtoj34 said:
Hmm. Writing up a list of what you tried is very helpful, kudos to that. I had the whole "unable to mount /data, /internal storage the other day in twrp, and tried a plethora of " solutions". The only one for me that worked was twrp > wipe > format data.
I see you have not tried the RUU why not give that a go? Vzw doesn't have a full RUU available but the one we have in vzw android dev is more than enough for most people
If that fails why don't you try formatting the phone in windows device manager? (Someone from these forums reported that this fixed their unable to mount data options although I can't guarantee the results.)
Click to expand...
Click to collapse
I actually did try the RUU several times. It's listed in the first post. It didn't change anything on my system. I did try to format the phone through windows, but unfortunately it doesn't show up in my disk management.
ok as ur Verizon my knowledge is very limited as I am GSM but i had problems with RUU until i tried this method
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
i know it says GSM but im sure i read in the comments people have done it with Verizon too as long as you have the right firmware
Internal memory mount/write issues seem to be a recurring problem on TWRP (but not for everyone). You can also try CWM, as I've seen some folks solve this issue by flashing CWM recovery.
agentbardall said:
ok as ur Verizon my knowledge is very limited as I am GSM but i had problems with RUU until i tried this method
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
i know it says GSM but im sure i read in the comments people have done it with Verizon too as long as you have the right firmware
Click to expand...
Click to collapse
I will try this and report back soon.
redpoint73 said:
Internal memory mount/write issues seem to be a recurring problem on TWRP (but not for everyone). You can also try CWM, as I've seen some folks solve this issue by flashing CWM recovery.
Click to expand...
Click to collapse
I already tried flashing an alternate recovery (philz touch which is based on CWM). It flashed successfully via fastboot, but it had no effect on my recovery partition. I'm still stuck with TWRP.
i thought ud have better luck this way as it only involves the External SD not the internal your having issues with
agentbardall said:
i thought ud have better luck this way as it only involves the External SD not the internal your having issues with
Click to expand...
Click to collapse
Thanks. Appreciate the help. I just flashed the firmware twice. Then in TWRP I ran 'format data' and wiped the cache, dalvik, system, and data partitions (the wipe failed). Finally, I re-flashed the ROM via USB-OTG and rebooted. Unfortunately, I'm still having the exact same issues.
Does anyone know how I can confirm this to be a NAND failure?
I'm leaning toward shipping this back to HTC. Is there anyone out there who can help me confirm this is a NAND failure?
With all the buzz about Android 5.0 lately I hastily decided to flash across the latest and greatest. So of course it turned out I needed S-Off for something (because it never gets to be easy) so after running various hacks in an attempt to get S-Off I noticed that I couldn't boot into Android. So I opened up the recovery and tried to sideload across a stock HTC KitKat ROM. When I turned on the sideloading function I got the following error: "failed to open driver control: No such file or directory". And this wasn't the first or last error that I would get. for example, if I tried to access my /sdcard partition I would receive the error message: "E: Can't mount /sdcard". To me this seems like either my partitions have been deleted or corrupted.
Other directories I also cannot mount are:
/data
/firmware/radio
/firmware/adsp
/firmware/wcnss
/sd-ext
Note: I am running PhilZ touch as my recovery.
Hi,
I think you should try to upgrade your bootloader with a Lollipop compatible one (4.16.1540.8 for example).
Maybe during the upgrade the partitions will be recreated.
john_matrix said:
Hi,
I think you should try to upgrade your bootloader with a Lollipop compatible one (4.16.1540.8 for example).
Maybe during the upgrade the partitions will be recreated.
Click to expand...
Click to collapse
Wouldn't this require me to have S-Off? Which is the problem in the first place, when I tried to get S-Off I bricked my phone.
But did you have S-OFF now?
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.
Hi there, so I'm having a bit of a problem. I tried to revive my old M9. I remember flashing it with a custom ROM (Android HD Revolution) and everything was fine. I left it since I got a new phone and today wanted to play around with my M9 again.
However, it would be stuck with the HTC Logo while loading, and my TWRP was gone, could no longer boot into it and my download mode was also screwed, as it gave me the error (failed to boot to download mode).
Anyway so I tried restoring to one of my TWRP backups, by mounting a TWRP img file first using my PC. It went fine, after that I booted into system and the HTC logo would be on white background and preventing me from using the screen, although funnily enough the system was functionally normally i.e. the volume keys worked and I could see it change on screen but, it was just as if I had a some kind of overlay and couldn't use the screen itself by touching.
I then tried to flash with the same custom ROM, but after installing it and rebooting the phone it was stuck in a boot loop, where it would shutdown and try to boot again.
So I turned it off using power up and home button, and tried to wipe the partition to install another ROM, using the same TWRP method I did above.
Only this time, I can't do anything: wipe, install, format etc. I get the error "Failed to mount '/data' (Invalid Argument)" "Failed to mount '/cache' (Invalid Argument)" whenever I try doing anything within TWRP. I can't even mount cache, system or Data. It is if they're not there.
And now my phone is back to where it started, i.e. infinite boot screen with HTC Logo and "This build is for etc..." text.
Note: Trying to change file system from ext4 to ext2/3 and back to ext4 does not fix the problem ,as the same errors pop up when trying to change file system.
90% chance the nand is goosed. 10% chance of recovering by flashing a stock firmware in download mode (same version as currently installed, external sd card method).
Twrp has a known issue for bricking devices at random.