Hello,
knowing there are a lot of specialist out here, but also that each of You lack time, I hope with this new thread that somebody is able to catch upp and help me with my problem.
HTC One
Firmware 2.24.401.1 (CID HTC__A07)
TWRP 2.6.3.0
Fastboot is working
ADB is working
File copy from PC to phone working (Thanks to Matt !!)
Booting into recovery possible
Booting into system not possible, (TWRP says OS not available), stops at 1st white HTC screen
Wiping is not possible, 'failed', cannot mount /data
Flash .zip is not possible, 'failed', cannot mount /data
Anyone has ideas how this can be solved. I understood it happens more often, but personally I have no knowledge whatsoever how to solve this .
All help highly appreciated.
Regards,
Ruud
As adb is working then side load the rom onto the phone and install from adb
Hi L0rdNes0n,
The Rom is on the phone already, that part was solved.
Can You give me some small guidance as to how adb sideload works, I have no knowledge about it.
Ruud Westerhout said:
Hi L0rdNes0n,
The Rom is on the phone already, that part was solved.
Can You give me some small guidance as to how adb sideload works, I have no knowledge about it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
herwegan said:
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
Thanks, M8, I found the site already, but had to leave somewhere.
When I come back I see You link to the same site, good !
But, I understand that what it actually does is make sure the rom (*.zip file) gets loaded into the phone. As I said, I did that, or better Matt did that for me while he supported me through a teamviewer session.
When I open TWRP and try to install the rom, it will immediately come with the error "failed" and a jumpload of lines telling more or less the same
E:Unable to wipe '/data'
E:Unable to mount '/data'
and such like.
If I understood correctly, adb sideload is no help here, or did I misunderstand this ?
Ruud Westerhout said:
Thanks, M8, I found the site already, but had to leave somewhere.
When I come back I see You link to the same site, good !
But, I understand that what it actually does is make sure the rom (*.zip file) gets loaded into the phone. As I said, I did that, or better Matt did that for me while he supported me through a teamviewer session.
When I open TWRP and try to install the rom, it will immediately come with the error "failed" and a jumpload of lines telling more or less the same
E:Unable to wipe '/data'
E:Unable to mount '/data'
and such like.
If I understood correctly, adb sideload is no help here, or did I misunderstand this ?
Click to expand...
Click to collapse
have you tried to format every partition through the recovery and then sideload again?
herwegan said:
have you tried to format every partition through the recovery and then sideload again?
Click to expand...
Click to collapse
Hi Herwegan,
No I was wondering if I should try the format option in TWRP, but my locig was the following :
-if format is an option, Matt would have offered me to do it
So, if this is an option, I'll do it :
-format, confirmed with yes, := succesfull
-wipe factory := successfull
-opened a cmd window and started adb push rom.zip /sdcard :=succesfull
-TWRP install rom ARHD 20.2
This looks great, I got aroma and it is installing.
Will call back when results are available !!
Ruud
Ruud Westerhout said:
Hi Herwegan,
No I was wondering if I should try the format option in TWRP, but my locig was the following :
-if format is an option, Matt would have offered me to do it
So, if this is an option, I'll do it :
-format, confirmed with yes, := succesfull
-wipe factory := successfull
-opened a cmd window and started adb push rom.zip /sdcard :=succesfull
-TWRP install rom ARHD 20.2
This looks great, I got aroma and it is installing.
Will call back when results are available !!
Ruud
Click to expand...
Click to collapse
ok looks fine, it should work now
herwegan said:
ok looks fine, it should work now
Click to expand...
Click to collapse
For now it is looking like a phone again.
I saw some Google + and Google Play errors flying by, but am not able to understand these yet, maybe later.
Although planned, now I will be spending time with installing all the programs again.
Thanks all for your help.
Ruud
Ruud Westerhout said:
For now it is looking like a phone again.
I saw some Google + and Google Play errors flying by, but am not able to understand these yet, maybe later.
Although planned, now I will be spending time with installing all the programs again.
Thanks all for your help.
Ruud
Click to expand...
Click to collapse
these errors are most probably caused by the new 3.09 base which is only a leak and not a 100% stable one
you're welcome!
Not out of the woods yet.
A restart is giving me the error that I have inconsistent UIDs and recmommended to wipe data partition.
Made a nandroid , copied all files and nandroid to PC, probably will have to do that wipe
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Ruud Westerhout said:
Not out of the woods yet.
A restart is giving me the error that I have inconsistent UIDs and recmommended to wipe data partition.
Made a nandroid , copied all files and nandroid to PC, probably will have to do that wipe
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
From memory this odd effect is often caused by the app Quadrant.
If this app is on your phone then delete it and message goes away.
Sent from my HTC One using xda app-developers app
Did Wipe Data in TWRP, topic solved
But I do not know if Quadrant was on the phone before that wipe. Will never know I guess.
But who cares, now my phone is working nice, hope for a long time no need for flashwork.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Related
My current situation is as follows:
ROM on it is bad and bootloops
Storage was wiped for a pure clean install
TWRP 2.5.0 doesn't seem to have any method to mount while in Recovery
As a result, I cannot boot it up to add the good files and I cannot mount it in Recovery to add the good files
I am at work and as such cannot use ADB.
If I can get it to mount, I can copy over the known good backups or just a known good ROM I can flash. There just doesn't seem to be any way to get it to mount in Windows 7 or 8. Does anyone have any suggestions?
rougegoat said:
My current situation is as follows:
ROM on it is bad and bootloops
Storage was wiped for a pure clean install
TWRP 2.5.0 doesn't seem to have any method to mount while in Recovery
As a result, I cannot boot it up to add the good files and I cannot mount it in Recovery to add the good files
I am at work and as such cannot use ADB.
If I can get it to mount, I can copy over the known good backups or just a known good ROM I can flash. There just doesn't seem to be any way to get it to mount in Windows 7 or 8. Does anyone have any suggestions?
Click to expand...
Click to collapse
Your only option now is to run the Stock ruu and return to stock. Theres plenty of threads on this forum that describe the procedure. You should never wipe the storage just for this reason. its much easier and less time consuming to flash a nandroid backup than having to revert back to stock via the ruu. Good luck and I hope everything works out
wranglerray said:
Your only option now is to run the Stock ruu and return to stock. Theres plenty of threads on this forum that describe the procedure. You should never wipe the storage just for this reason. its much easier and less time consuming to flash a nandroid backup than having to revert back to stock via the ruu. Good luck and I hope everything works out
Click to expand...
Click to collapse
I managed to find a machine I have sufficient privileges on for ADB. I can now push files to it. Do you know off hand what the path needed for TWRP backups is?
rougegoat said:
I managed to find a machine I have sufficient privileges on for ADB. I can now push files to it. Do you know off hand what the path needed for TWRP backups is?
Click to expand...
Click to collapse
should be /mnt/sdcard0/twrp/backups
but you wiped storage. Can you boot into fastboot? if so you can run the fastboot command
fastboot flash nameofrom.zip
you'll have to place the rom zip in the same directory as fastboot but fastboot should interrogate the zip file and flash the correct partitions
wranglerray said:
should be /mnt/sdcard0/twrp/backups
but you wiped storage. Can you boot into fastboot? if so you can run the fastboot command
fastboot flash nameofrom.zip
you'll have to place the rom zip in the same directory as fastboot but fastboot should interrogate the zip file and flash the correct partitions
Click to expand...
Click to collapse
I can get there. The issue is the one zip I have on hand doesn't seem to like being pushed that way. Rather than sit through a gig download I was just going to push a backup of stock I have on hand into the proper folder. At the very least I'd attempt it while downloading a stock+root rom.
rougegoat said:
I can get there. The issue is the one zip I have on hand doesn't seem to like being pushed that way. Rather than sit through a gig download I was just going to push a backup of stock I have on hand into the proper folder. At the very least I'd attempt it while downloading a stock+root rom.
Click to expand...
Click to collapse
ok the correct path according to my phone's file system is /sdcard/TWRP/BACKUPS
if those files don't exsist you can create them from adb shell
mk dir sdcard
cd sdcard
mk dir TWRP
cd TWRP
mk dir BACKUPS
exit out of adb shell by issuing the command exit
the
adb push nameofbackup.win /sdcard/TWRP/BACKUPS
wranglerray said:
ok the correct path according to my phone's file system is /sdcard/TWRP/BACKUPS
if those files don't exsist you can create them from adb shell
mk dir sdcard
cd sdcard
mk dir TWRP
cd TWRP
mk dir BACKUPS
exit out of adb shell by issuing the command exit
the
adb push nameofbackup.win /sdcard/TWRP/BACKUPS
Click to expand...
Click to collapse
Giving it a shot now.
Sorry my syntax was off it's mkdir without a space
Sent from my HTCONE using Xparent BlueTapatalk 2
wranglerray said:
Sorry my syntax was off it's mkdir without a space
Sent from my HTCONE using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
No worries, I'm versed enough commandline wise to know what you were getting at. Unfortunately it seems that random number path for the device chunk has changed since I did my backup(probably because of my wiping and being an overall idiot). The stock+root zip of a rom finished downloading though, so I'm flashing that now. Hopefully that ends this ordeal.
(Edit) Success getting it to be usable again. Now to start from scratch. (/edit)
rougegoat said:
No worries, I'm versed enough commandline wise to know what you were getting at. Unfortunately it seems that random number path for the device chunk has changed since I did my backup(probably because of my wiping and being an overall idiot). The stock+root zip of a rom finished downloading though, so I'm flashing that now. Hopefully that ends this ordeal.
Click to expand...
Click to collapse
good luck! post your results i'd be interested in knowing how it ends up.
Hey rogue.... went through this same problem about four days ago, almost blew my brains out because I thought I would have to smash my phone and return it through the best buy protection plan. Anyways... the ONLY way to fix your problem is to use the Sprint HTC One RUU. Boot your phone into fastboot usb mode and run the RUU. Takes about 10-15 minutes, and will have you COMPLETELY back to stock. From there, you need to start from scratch unlocking and installing the recovery. ViperRom is the only rom that won't bug out your sprint phone atm. Also be sure you relocked your phone before you run the RUU. I'm super busy atm and can't go find the RUU links, but google it and i'm sure you can find it. If not, i'll get you the links later if you pm me. Peace bro and good luck.
---------- Post added at 09:57 PM ---------- Previous post was at 09:51 PM ----------
cburch85 said:
Hey rogue.... went through this same problem about four days ago, almost blew my brains out because I thought I would have to smash my phone and return it through the best buy protection plan. Anyways... the ONLY way to fix your problem is to use the Sprint HTC One RUU. Boot your phone into fastboot usb mode and run the RUU. Takes about 10-15 minutes, and will have you COMPLETELY back to stock. From there, you need to start from scratch unlocking and installing the recovery. ViperRom is the only rom that won't bug out your sprint phone atm. Also be sure you relocked your phone before you run the RUU. I'm super busy atm and can't go find the RUU links, but google it and i'm sure you can find it. If not, i'll get you the links later if you pm me. Peace bro and good luck.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2250904
I know another person suggested this earlier, but failed to mention that sideloading once you're caught in this loop won't work. Run the RUU, unlock, and flash ViperRom.
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Rooted HTC one, no os, don't know how to push rom
I accidently wiped my os while putting a new rom on. I am INCREDIBLY inexperienced with this and really had no business fooling around with it. Regardless, I have the HTC One rooted with TWRP but cant get the new rom on to the phone. I'm on a mac and android file transfer is not recognizing my phone. Any help anyone could give would be great.
Try putting the rom on a usb stick and using an otg cable then mount it under twrp and flash from there?
Sent from my HTC One using xda app-developers app
Good Info
EazyVG said:
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Click to expand...
Click to collapse
Thanks for the Info
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.
Hi there!
I have a TX1085, it is already unlocked and rooted and has the CM Recovery installed. But before the CM Recovery I had the TWRP Recovery installed and tried to use it to flash CM12, which I had put on the SD-Card. It kept on telling me that mounting the system failed. Unfortunately I wiped everything via TWRP Recovery without creating a backup. Then I installed the CM Recovery to try again. Now, if I try to flash via CM Recovery (apply update) it doesn't show anything in my internal storage and I can't connect via adb using Ubuntu (Terminal tells me either "device not found" or "device offline".)
Any suggestions?
Greets
I have no idea what I'm talking about, I'm still learning all this, but in your case, from what I've learnend so far I'd maybe try the "fastboot boot recoveryfile.img" command, loading TWRP or CMrecovery into the ram of the phone and start flashing from there?! (just an idea)
psssss said:
I have no idea what I'm talking about, I'm still learning all this, but in your case, from what I've learnend so far I'd maybe try the "fastboot boot recoveryfile.img" command, loading TWRP or CMrecovery into the ram of the phone and start flashing from there?! (just an idea)
Click to expand...
Click to collapse
Thanks for your suggestion! Unfortunately I don't know how to get access to my phone again via computer, which is - I think - because I deleted the system on it. Or how else could I get into the ram? This is my first time to flash a phone, so I really need some guidance.
pyq said:
Thanks for your suggestion! Unfortunately I don't know how to get access to my phone again via computer, which is - I think - because I deleted the system on it. Or how else could I get into the ram? This is my first time to flash a phone, so I really need some guidance.
Click to expand...
Click to collapse
Go to bootloader first the use the commands fastboot boot recovery.img
Try using twrp, everybody is working with it now.
Sent from xt1096 with Marshmallow!
josuearisty said:
Go to bootloader first the use the commands fastboot boot recovery.img
Try using twrp, everybody is working with it now.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
I tried, but the Terminal gives me that:"cannot load 'recovery.img': No such file or directory". I'm in fastboot, is that correct? Is there another way?
Right now I can't (or don't know how to) switch back to TWRP, but I'll keep it in mind. Thanks for your help!
did you installed android sdk and adb drivers? if yes try to open cmd in sdk directory
pyq said:
I tried, but the Terminal gives me that:"cannot load 'recovery.img': No such file or directory". I'm in fastboot, is that correct? Is there another way?
Right now I can't (or don't know how to) switch back to TWRP, but I'll keep it in mind. Thanks for your help!
Click to expand...
Click to collapse
Look for adb in 15 seconds and install it, go to directory where fastboot is located.
Download twrp image and rename it or something and copy recovery.img to fastboot directory.
If there is no recovery.img in that directory it will fail.
After you copy and rename recovery.img then you will be able to do what I told you.
If you are new at modding, you have to take it easy and ask everything before doing it.
Sent from xt1096 with Marshmallow!
kaktusmaier125 said:
did you installed android sdk and adb drivers? if yes try to open cmd in sdk directory
Click to expand...
Click to collapse
I am using Linux without Android SDK, but I have working fastboot and adb installed.
josuearisty said:
Look for adb in 15 seconds and install it, go to directory where fastboot is located.
Download twrp image and rename it or something and copy recovery.img to fastboot directory.
If there is no recovery.img in that directory it will fail.
After you copy and rename recovery.img then you will be able to do what I told you.
If you are new at modding, you have to take it easy and ask everything before doing it.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
pyq said:
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
Click to expand...
Click to collapse
try to flash stock firmware
kaktusmaier125 said:
try to flash stock firmware
Click to expand...
Click to collapse
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
pyq said:
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
Click to expand...
Click to collapse
see this post http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
what the model you have
---------- Post added at 09:32 AM ---------- Previous post was at 09:26 AM ----------
file factory is slow so try https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
and flow this insturction http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
pyq said:
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
Click to expand...
Click to collapse
Next time, please ask everything you need before doing something.
I have been modding my phones since the Motorola L7 and I always ask for everything on a new device before start modding.
That way I never bricked my phones.
Sent from xt1096 with Marshmallow!
kaktusmaier125 said:
see this post http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
what the model you have
---------- Post added at 09:32 AM ---------- Previous post was at 09:26 AM ----------
file factory is slow so try https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
and flow this insturction http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Click to expand...
Click to collapse
This post seems to be aiming for Windows users, but I am using Linux. Could I still use it? If yes, how?
josuearisty said:
Next time, please ask everything you need before doing something.
I have been modding my phones since the Motorola L7 and I always ask for everything on a new device before start modding.
That way I never bricked my phones.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
That is why I asked you how to get CM installed with TWRP. I had the mounting problem at the very beginning already. How can I get CM installed now?
pyq said:
That is why I asked you how to get CM installed with TWRP. I had the mounting problem at the very beginning already. How can I get CM installed now?
Click to expand...
Click to collapse
The commands I wrote before, use the same steps but instead use the cm recovery.
I hope you understand!
Sent from xt1096 with Marshmallow!
pyq said:
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
Click to expand...
Click to collapse
In the newer versions of TWRP the first screen should show a Mount button. In that screen you should be able to mount any of the partitions.
josuearisty said:
The commands I wrote before, use the same steps but instead use the cm recovery.
I hope you understand!
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
If I use the "fastboot boot CM_recovery.img" command the phone installs it and then starts into TWRP. Except for that nothing changes. How can I continue?
rotorbudd said:
In the newer versions of TWRP the first screen should show a Mount button. In that screen you should be able to mount any of the partitions.
Click to expand...
Click to collapse
If I try to make a tick (as to mount) system the phone vibrates but doesn't tick system, so I can't mount it this way.
pyq said:
This post seems to be aiming for Windows users, but I am using Linux. Could I still use it? If yes, how?
Click to expand...
Click to collapse
Yes you can
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.