Well, hello. Not new here, but quite new in posting things, was always just reading what these guys are doing and followed their instructions. result was always being able to flash whatever on a selected device. But today i'm coming with a stupid problem that i hope somebody would help me solve.
2 days ago (and i will be full of details here) di flashed ARHD51.0 on my Htc One. everything went well (as usual with those roms) but i wanted to format my whole phone (i had like 5gbs of backups that i could not find (4 months i was xda-ing and googleing solutions for removing invisible backups that cwm made. and then i read this http://forum.xda-developers.com/showpost.php?p=48108231&postcount=2
as you well know, this is a member of trust on this site so i decided to follow those instructions and that backfired on me i must say. what happened next was that my phone was in a bootloop, recovery was dameged and adb (and still) could not read my device, fastboot would on the otherside.
I managed to flash new cwm (philz touch 6.0.4.6.) via fastboot and it worked. but in cwm messages are following (will copy just some of the lines because you will understand the problem)
failed to mount /dev/block/mmcblk0p39 on data ext4 (file exists)
failed to mount /data
failed to mount /cache
then something like failed to install /tmp/update.zip (that message was shown when i was trying to install stock rom)
and i sideloaded stock (fail), arhd (goes to 30%, freezes on writing data&system)
when exiting cwm, it asks me to reinstall the root because it is missing (even when i install it manually via usb otg or sideload and it says done, still root is non existant.
baseline is this: i formated the sd card, and tried to do as much as i could with all the logical things, my partitions are messed up and i'm missing boot.img and system files, unable to mount data/cache/sd card. Now i can do only so much to ask you. I can try to relock the bootloader and use the ruu (but i am s-on) i can try to send boot.img or something (but how when adb push is not working, "device not found") i can format the partitions but do not know how to format them from cmd or cwm.
currently i'm downloading stock deodexed and odexed stock roms and ruu. i already have su, philz touch advanced (planning to try to flash that only because of more options than standard philz cwm) and otg ready cable to use it if there is no help for adb push.
Anybody, please help because i will tryto fix this, but i'm afraid that if i mess the order of things that needs to be done, i could brick this totally, and in this area of damaged partitions i have no exact experiance.
Any help appreciated, and can be (gladly) rewarded on demand
sorry for funky and somewhere incorrect gramatic structure, if something is unclear about it, feel free to ask
kriistofor said:
failed to mount /dev/block/mmcblk0p39 on data ext4 (file exists)
Click to expand...
Click to collapse
HOLD YOUR HORSES!!
post a "fastboot getvar all" (leave the first 2 characters of serial number, IMEI, and MEID, and "xxxx"-out the rest)
and maybe a screenshot of bootloader
you either have a Sprint/Verizon HTC and/or the wrong recovery!!
so stop!!!! and post above needed information
nkk71 said:
HOLD YOUR HORSES!!
post a "fastboot getvar all" (leave the first 2 characters of serial number, IMEI, and MEID, and "xxxx"-out the rest)
and maybe a screenshot of bootloader
you either have a Sprint/Verizon HTC and/or the wrong recovery!!
so stop!!!! and post above needed information
Click to expand...
Click to collapse
sorry,sorry i sounded a bit overexcited and impulsive.
well, i have international htc, but the cwm (even though i downloaded the M7(gsm) version was the biggest problem for the phone (based on the name of the cwm it does not sound logical to me). Also, i used 6.0.4.6 non touch and it also was useless but i managed to solve this after two whole days of mind****ng myself and this phone.
SOLUTION:
relock bootloader (without this you can try anything as i did but it will fail if the problem is the same)
unlock bootloader
install twrp (for some reason after this cwm, no other cwm was able to format partitions or anything)
format data, or full wipe option
stock rom (installed deodexed 4.4.2)
root if want
problem was gone in 4 minutes, it booted faster than any other thing i've put on this phone (like in 2 minutes fully booted into welcome screen).
now it is running arhd 51.0, elementalX and is alive and well.
solution is probably effective wih all of those problems with corrupted or badly formated internal sd on One but i will say that people here are giving solutions that are logical and are working for others with similar problems. this one is for those who have tried all the things with reflashing recovery, rom, with bad adb experiance because of formatted card and are unable to sideload anything.
thank you for help because if I haven't succeded with this leap of faith i would more likely f*c? something up by myself. and thanks for reply, expected no one would give any
Related
Hi,
My new HTC One's vibrate isn't very strong, so the vendor is sending me a new one. I'm rooted though, so thought I'd better start looking at ways to "undo" the root. When looking at options on the HTC One Toolkit, I "somehow" did something to my phone. All I "Thought" I was doing was getting the version information off it, so I could find the correct RUU, but when trying to reboot after that, it just kept going back to the bootloader with some error like "re-locked" and "security warning".
After extensive searches, I learnt I could flash the unlock.bin file again to unlock it. Done...but then it just sat at the "Slim" logo [ROM I was running]. I could still boot into Recovery (CWM) and tried clearing cache and dalvik - but still sat at the "Slim" logo. So I started digging in. I tried to mount the SDcard in CWM, but wouldn't mount. So flashed TWRP, but same thing there. When I try to mount anything, the only folder it will let me select is "System" - nothing else mounts and my "Storage" reads "0 bytes".
So I thought maybe I'd lost root, everything was Read Only and that's why I couldn't write to anything. So using the HTC One toolkit, flashed SuperSu. Still same thing.
I did manage to adb the slim ROM and the gapps to /sdcard, but when I tried to install, nothing would "mount" in order to install it...so all I got was errors saying install failed, and a bunch of directories that couldn't be "mounted". In summary I've done the following with Fastboot:
Flashed Unlock file
Flashed boot.img (from Slim Rom)
flashed Recovery (CWM first, but now TWRP)
Fastboot Clear cache
But after all that, when I boot into Recovery, nothing mounts and I can't get past this. Any help you could provide would be MOST welcome!
Thanks in advance.
-- Edit --
Disregard - got it finally. Using TWRP, I formatted the data directory, and it was writeable again. Not sure if it helped, but I then resubmitted everything I did in the list above, booted to Recovery, and was then able to adb the ROM and Gapps over and it installed fine. Phew.... Still need to figure out how to get it all back to stock though. That's my next task.
Hi developers. I am sorry for posting this. I spent the last week trying to solve it by myself with no hope. This is my second time installing something on a phone, but it is my only phone, so I beg anyone for a help...
-What I did:
Some days ago I downgraded to this ROM C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf to use DoomLord rooting script. I did it with flashtool for linux and I applied his .bat step by step in the terminal since windows would not detect my phone.
It worked. I had root for some days, but I was still annoyed by sony default android. So I decided to install Cyanogenmod.
I unlocked the device with sony official system and wen't straight to this instructions, before the first reboot
wiki.cyanogenmod.org/w/Install_CM_for_yuga
I booted succesfully in CWM, followed everything as it says there. But that's where weird things happened:
-The problems:
-The backup
I tried, it wouldn't mount /sdcard. Since I don't understand much about this, I thought it was normal. The next choice was sdcard1, I backed up there. Or so I thought...
-The factory reset
I factory reset, again, not mounting sdcard. Here is the message that shows when I try this now:
can't mount /data!
Error mounting /sdcard.android_secure
Skipping format...
Data wipe complete.
Since it said it is complete, I went on installing the zip file from my sdcard1. Both CM 10.2.1 (dogo, the right one for my phone) and the appropriate GAPPS.
Now it loops on the CM loop animation and I have to remove the battery...
-The restore problem
It still boots on the recovery mode. So I tried recovering my backup from sdcard1. But the image name is 1970.01.01.00.03.16. And it says "md5 mismatch"
I tried flashing again the stock rom with flashtool. The proccess goes on but nothing happens. I still have CWM and the boot loop.
I read elsewhere someone with a similar problem who solved using sony "emma" software. I installed it, it won't even recocnize my phone.
It recocnizes that there is a phone, but don't know which one.
But that has alway been the case with windows. I haven't been able to do anything in windows other then accessing the sdcard (when the phone worked).
Is there something I can do? I imagine that somehow, for some reason, the /data and /sdcard partitions got corrupted. I imagine I would need to repartition this and install again, but I have no idea how this happens on phones...
I can mount /system /cache and /storage/sdcard1. just /data I can´t. Says "error mounting /data"
This is my only phone and a vey recent $400 thing. I was very stupid to do that withouth a replacement and really need this phone. I greatly appreciate any help...
I found this post forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ searching the internet. Is it possible that this would solve my problem? or would it finish bricking the phone?
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse
Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?
devbro said:
Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?
Click to expand...
Click to collapse
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean. I had a situtation where some things would not mount. data being one of them.. Not sure what else. Then I just mounted /system and everything was ok. Could it be that for some reason system is not getting mounted and you not formatting it besides an empty directory.
YayYouFixedIt said:
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean.
Click to expand...
Click to collapse
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
some corruption seems to have occurred.
perform a hard reset in the 'stock' recovery (this will format /data).
then boot in and re-setup. any userdata you had will be gone (including media/content stored locally, etc.).
in case of /system corruption (after performing the above; you still cannot boot in), you can format that partition separately and re-flash it from the CWM file for the latest posted stock update.
you can find file(s) on droidbasement, as needed.
I belive I have the same probleme, how i could i do it right?
devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
How did you try to format data in fastboot??
That's done in recovery afaik.
nero0345 said:
I belive I have the same probleme, how i could i do it right?
Click to expand...
Click to collapse
What problem do you have? /data not mounting? Format it in recovery but you will loose everything stored on your internal SD.
I finally took my tablet in for a check with asus. They said that I ahve corrupted my boot and since I replace the recovery there is no way to fix it. the only way to fix it is to replace the motherboard at this point. It will cost 190$ to replace!!!!
Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.
devbro said:
Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.
Click to expand...
Click to collapse
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...
berndblb said:
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...
Click to expand...
Click to collapse
When I talked to the tech at their center, there is apparently some special actions that only their recovery can do. These actions are those that allow changing boot table and other low level functions of the tablet which has nothing to do with the built-in memory or system files.
If I did not replace the recovery, then the repair by asus would have only cost 40$.
Ok So I have an HTC One m7. and I had CyanogenMod installed. Then jsut today I decided I would go back to Sense 6. So I download Android Revolution HD 71.1 for m7 install it on my phoen. Then CWM(Which I hate btw and can't uninstall no matter what I do) says your phone is not rooted would you like to root it when I click reboot phone. No matter which I click I get stuck on the HTC logo boot logo. I don't care if I lose my data or anything so I click factory reset, then wipe cache, then wipe dalvik cache. Then I get the error were it constantly says cant mount /cache or whatever. So to fix it i wipe Dalvik Cache again. Then I try sideloading ViperOne Rom. Guess what It give me *failed to write 'protocol fault <no status> *
Then I tried formatting my data with CWM which took 2 hours and still didn't complete so I rebooted(which led to more problems) Now I cant say install from sdcard because it gives me the error E: Can't Mount /sdcard. So that means I cant adb push Viper /sdcard. I have no Idea what to do. Help me please!
radsherwin said:
Ok So I have an HTC One m7. and I had CyanogenMod installed. Then jsut today I decided I would go back to Sense 6. So I download Android Revolution HD 71.1 for m7 install it on my phoen. Then CWM(Which I hate btw and can't uninstall no matter what I do) says your phone is not rooted would you like to root it when I click reboot phone. No matter which I click I get stuck on the HTC logo boot logo. I don't care if I lose my data or anything so I click factory reset, then wipe cache, then wipe dalvik cache. Then I get the error were it constantly says cant mount /cache or whatever. So to fix it i wipe Dalvik Cache again. Then I try sideloading ViperOne Rom. Guess what It give me *failed to write 'protocol fault <no status> *
Then I tried formatting my data with CWM which took 2 hours and still didn't complete so I rebooted(which led to more problems) Now I cant say install from sdcard because it gives me the error E: Can't Mount /sdcard. So that means I cant adb push Viper /sdcard. I have no Idea what to do. Help me please!
Click to expand...
Click to collapse
its simple to fix, your problem is simply cwm recovery, you need to use twrp to flash either of those rom's, so start there, recommended is 2.6.3.3, its the most problem free.
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery, select wipe then format data, push or sideload a rom then flash it.
ViperOne Install Instructions
1. Download the the latest ViperOne full ROM zip from the download section
2. Place the file somewhere on your phone storage. Alternatively, if you have a USB OTG cable (I have this exact one), you can place the rom on a USB key (FAT32, NTFS are all supported).
3. Confirm the MD5 on the download page matches the MD5 of the file on your phone (ES File Explorer will show the MD5 of the file)
4. Reboot to TWRP Recovery
5. Backup current ROM if desired
6. Install ROM using TWRP and select wipe during aroma install if coming from another base
7. Reboot and Enjoy
Seanie280672 said:
its simple to fix, your problem is simply cwm recovery, you need to use twrp to flash either of those rom's, so start there, recommended is 2.6.3.3, its the most problem free.
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery, select wipe then format data, push or sideload a rom then flash it.
ViperOne Install Instructions
1. Download the the latest ViperOne full ROM zip from the download section
2. Place the file somewhere on your phone storage. Alternatively, if you have a USB OTG cable (I have this exact one), you can place the rom on a USB key (FAT32, NTFS are all supported).
3. Confirm the MD5 on the download page matches the MD5 of the file on your phone (ES File Explorer will show the MD5 of the file)
4. Reboot to TWRP Recovery
5. Backup current ROM if desired
6. Install ROM using TWRP and select wipe during aroma install if coming from another base
7. Reboot and Enjoy
Click to expand...
Click to collapse
Ok I'm currently sideloading ViperRom but at first it was stuck at 2% so I cancelled it now it's stuck at 26% for like 30 min
radsherwin said:
Ok I'm currently sideloading ViperRom but at first it was stuck at 2% so I cancelled it now it's stuck at 26% for like 30 min
Click to expand...
Click to collapse
did you format data first ? any unable to mount messages, you could also try advanced wip and select everything in the list.
try pushing it instead
with the phone in twrp main screen only, no sub menu's and the rom in the same folder as adb and fastboot on your computer type:
Code:
adb push (name_of_rom).zip /sdcard/
takes a while and will look unresponsive, but the cmd window will let you know when its done. Make sure you unplug your phone before flashing.
Seanie280672 said:
did you format data first ? any unable to mount messages, you could also try advanced wip and select everything in the list.
try pushing it instead
with the phone in twrp main screen only, no sub menu's and the rom in the same folder as adb and fastboot on your computer type:
Code:
adb push (name_of_rom).zip /sdcard/
takes a while and will look unresponsive, but the cmd window will let you know when its done. Make sure you unplug your phone before flashing.
Click to expand...
Click to collapse
ok I 've been sitting here for a while and the cmd prompt just shows a blinking line under my command. The file is in my sdcard but is it complete?
Seanie280672 said:
did you format data first ? any unable to mount messages, you could also try advanced wip and select everything in the list.
try pushing it instead
with the phone in twrp main screen only, no sub menu's and the rom in the same folder as adb and fastboot on your computer type:
Code:
adb push (name_of_rom).zip /sdcard/
takes a while and will look unresponsive, but the cmd window will let you know when its done. Make sure you unplug your phone before flashing.
Click to expand...
Click to collapse
also it doesnt let me format data wipe. It gives me error like E: Unable to mount '/cache/
radsherwin said:
also it doesnt let me format data wipe. It gives me error like E: Unable to mount '/cache/
Click to expand...
Click to collapse
with your phone in fastboot, type fastboot format cache
Seanie280672 said:
with your phone in fastboot, type fastboot format cache
Click to expand...
Click to collapse
doesn't work either.. I tried everything nothing is working. I can't even get ViperOne Rom on my phone.
anyone? I need help! I'm looking all over the internet for solutions and apparently every has solved their problem but me. HELP!
Seanie280672 said:
with your phone in fastboot, type fastboot format cache
Click to expand...
Click to collapse
anymore help? When ever I try to ADB sideload It gets stuck on 1% forever. Whenever I try to adv push it does nothing and doesnt tell me anything. everytime I try to format It says successful but it still gives me error saying E: / cant mount cache. PLEASE HELP ME
radsherwin said:
anyone? I need help! I'm looking all over the internet for solutions and apparently every has solved their problem but me. HELP!
Click to expand...
Click to collapse
I recommend you start from scratch
from the bootloader / power down
wait a couple min and boot back to fastboot
plug the phone into the PC
from your command prompt type
fastboot devices
see your device serial number
type
fastboot erase cache
type
fastboot reboot-bootloader
now try sideload your rom from TWRP 2.6.3.3 /advanced/sideload
clsA said:
I recommend you start from scratch
from the bootloader / power down
wait a couple min and boot back to fastboot
plug the phone into the PC
from your command prompt type
fastboot devices
see your device serial number
type
fastboot erase cache
type
fastboot reboot-bootloader
now try sideload your rom from TWRP 2.6.3.3 /advanced/sideload
Click to expand...
Click to collapse
when I try fastboot erase cache it says
"******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
finished. total time: 0.293s
So you have CWM / TWRP installed? Try copying a ROM to the external SD card, and install it that way. Clear everything in recovery first, cache, dalvik, etc... I had the same problem with the M8 and it drove me nuts until I did it all from the SD. If not, I would suggest trying the full RUU, it has saved me many a time.
hack14u said:
So you have CWM / TWRP installed? Try copying a ROM to the external SD card, and install it that way. Clear everything in recovery first, cache, dalvik, etc... I had the same problem with the M8 and it drove me nuts until I did it all from the SD. If not, I would suggest trying the full RUU, it has saved me many a time.
Click to expand...
Click to collapse
I have the m7 not the m8. So I have no sd card. What is the RUU method? I have TWRP installed right now.
This is getting on my nerves. Ive been sitting here for 6 hours and I posted 4 times and I still have not fixed this problem!!!!!!!! No one can explain clearly or respond to me even. Half my problems are being ignored. and half the things I say are being ignored.
radsherwin said:
I have the m7 not the m8. So I have no sd card. What is the RUU method? I have TWRP installed right now.
Click to expand...
Click to collapse
Oh that's right dang it. When I had my M7 I converted it to a Dev Edition by changing the CID and then using a file like this:
http://dl4.htc.com/RomCode/Source_and_Binaries/m7ul-3.4.10-g77e9ea0.zip
Mine was an ATT version so MID matched.
---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------
radsherwin said:
This is getting on my nerves. Ive been sitting here for 6 hours and I posted 4 times and I still have not fixed this problem!!!!!!!! No one can explain clearly or respond to me even. Half my problems are being ignored. and half the things I say are being ignored.
Click to expand...
Click to collapse
Hey, hey, hey, patience my friend, we are here to help, ALL of us, we are trying.
Scratch that link, it doesn't like direct posts, find the Brighstar WWE RUU by searching at: http://www.htcdev.com/devcenter/downloads, or find the ATT, or TMobile. Not sure what your carrier is, but the Dev Edition is the way to go.
hack14u said:
Oh that's right dang it. When I had my M7 I converted it to a Dev Edition by changing the CID and then using a file like this:
http://dl4.htc.com/RomCode/Source_and_Binaries/m7ul-3.4.10-g77e9ea0.zip
Mine was an ATT version so MID matched.
---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------
Hey, hey, hey, patience my friend, we are here to help, ALL of us, we are trying.
Click to expand...
Click to collapse
The link just sends me to the htc website. Also what does converting my m7 to dev edition do exactly? Will it help with the Sideload problem or the cant mount cache problem?
And I know you guys are trying to help me. Im just mad because everything I do is not working. Im searching all over the internet and nothing is helping. Errors lead to more errors. Reminds me of the time I tried learning progrramming and I made a simple program but It wouldnt work. I posted it on 3 websites and no one could help me. So I'm sorry for going off like that.
radsherwin said:
The link just sends me to the htc website.
And I know you guys are trying to help me. Im just mad because everything I do is not working. Im searching all over the internet and nothing is helping. Errors lead to more errors. Reminds me of the time I tried learning progrramming and I made a simple program but It wouldnt work. I posted it on 3 websites and no one could help me. So I'm sorry for going off like that.
Click to expand...
Click to collapse
I know it can be frustrating, but nothing you can do to the M7 can hurt it. Try the link above HTC doesn't like direct links.
hack14u said:
I know it can be frustrating, but nothing you can do to the M7 can hurt it. Try the link above HTC doesn't like direct links.
Click to expand...
Click to collapse
ok im doing it right now. Im AT&T btw.
I seem to have fixed the E: Can't mount cache problem. All i did was go to advance and click only on cache. Now all I need is to sideload or pus my ViperOne rom over to my HTC. Then hopefully nothing goes wrong. What do I do once the zip file is done downloading?
That might not be the right one, it should be an exe around 1 GB in size, sorry. Look around for it, if it's not still posted at the HTC Dev site, then it is around here somewhere. There are also some nandroids I have seen that should help you restore to stock. Nonetheless, once you have that Viper Rom on there, you should be able to flash anything you want. A full RUU will restore your phone to the state in which you bought it in, just like brand new.
After unlocking the bootloader, installing TWRP recovery and rooting my phone with SuperSU (v2.82), I was preparing to install a custom ROM (more specifically the Resurrection Remix 7.1.2.) all in all, things ended up going out of hand and I accidentally deleted my internal storage, losing every single bit of my existing ROM, not to mention the RR ROM file as well. Now when I try to wipe, I can't, it usually says "Failed to mount '/data' (Device or resource busy) and "Unable to mount storage".
I tried using ADB sideload but to no success, only the same message. What I can understand is that the previous data is gone, I tried changing the format of data, system and cache to FAT & exFAT but it still did not resolve my issue.
I'm out of options here, I don't want to have to give up this phone because of my stupidity.
I also tried flashing the LineageOS 14.1 ROM to see if anything was different, here is what it said:
Installing zip file '/sideload.package.zip'
Target: HUAWEI/EVA-L09/HWEVA:7.0/HUAWEIEVA-L09/C432B361:user/release-keys
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
detected filesystem exfat for /dev/block/bootdevice/by-name/userdata
mount: failed to mount /dev/block/bootdevice/by-name/userdata at /data: Device or resource busy
unmount of /data failed; no such volume
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Script succeeded: result was [1.000000]
Although it said succeeded it clearly did not work and I am sitting without a ROM. I'm not smart when it comes to these things please help a guy out.
(Is there a way to going back to completely stock EMUI 5.0?)
Cheers.
EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros
zgfg said:
EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros
Click to expand...
Click to collapse
I know this is awkward to ask and all, but how exactly do I go about this, I'm pretty lost and I have minimal experience with this stuff..
I never had to use it but here is their portal (with download info, prices, instructions, etc)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)
zgfg said:
I never had to use it but here is their portal (with download info, prices, instructions, etc)
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)
Click to expand...
Click to collapse
I'm terribly sorry for being THIS stupid. As I'm looking into this even more, I'm conflicted about the credit amount I need, been scrolling through the list and I can't really find my problem involving firmware I suppose.
People usually buy for 15 Euros. It may help you, Chrome will automatically translate from German
https://www.android-hilfe.de/forum/...-wiederherstellung-mit-dc-phoenix.818669.html
I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.
christopherpfister said:
I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.
Click to expand...
Click to collapse
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?
Hexagonal said:
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?
Click to expand...
Click to collapse
UPDATE: I flashed the stock recovery image and it showed me the wipe cache partition and factory data and system reset, I tried both, only the cache one succeeded, the other one failed. I saw a post that directed you to flash boot.img, recovery.img, recovery2.img and then system.img, I did that, but I couldn't boot into my phone - the good thing is however! That I can use my touchscreen in the recovery now.
Obviously the second time booting into EMUI recovery it prompts me to 'Download latest version and recovery', I try to connect to my Wi-Fi, seems okay but then it suddenly fails. More specifically it says 'Getting package info failed'. Save me please :crying:
So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.
christopherpfister said:
So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.
Click to expand...
Click to collapse
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!
Hexagonal said:
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!
Click to expand...
Click to collapse
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.
Hexagonal said:
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.
Click to expand...
Click to collapse
Whats the error? Why doesn't it work? What happens when you try to boot?
christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
That's what I'm trying to figure out, when I try to boot in it's just stuck on a boot loop. Unfortunate..
Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?
christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
christopherpfister said:
Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?
Click to expand...
Click to collapse
I know, but it was flashing the Huawei logo and the unlocked bootloader warning continuously. It was set on EXT4 but as I was saying, it said script succeeded at 50%.
Hexagonal said:
'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Click to expand...
Click to collapse
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.
christopherpfister said:
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.
Click to expand...
Click to collapse
I deliberately set the data partition to EXT4 before installing
Hexagonal said:
I deliberately set the data partition to EXT4 before installing
Click to expand...
Click to collapse
Can you check in TWRP if it actually says /data is ext4?
Which lineage are you trying to install? Don't you need a vendor.zip for some of them?
/data is indeed on EXT4, and I was installing the one that was on the room section.