Hi everyone. So I am having a little bit of trouble using the Mount feature in TWRP. I have tried two versions (v2.6.3.4 and v2.7.0.4b) and neither allowed me to use mount.
One thing I have noticed is when I boot into recovery, there is a missing driver showing in my Device Manager. I'm not sure if that has anything to do with it. And when I tried to manually install the HTC Sync driver, it just says couldn't find driver.
Any help would be greatly appreciated! Thanks.
Specs:
HTC One M7 32GB AT&T
Android Version: 4.4.2
HTC Sense Version: 5.5
Software Number: 4.18.502.7
HTC SDK API Level: 5.68
Baseband Version: 4A.25.3263.21_10.38x.1157.04L
Rooted, S-OFF, and SuperCID
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guys I could really use some help with this. My phone's rom messed up and so I went into recovery to wipe and reinstall it. Only, I forgot that I'd removed the rom.zip from my storage while I was putting content on the storage a few days prior.
So now, I can't install a rom to my phone, I can't boot into a rom because there is no rom installed, I can't mount my phone to the computer in recovery because it doesn't see it in ADB.
All I have is fastboot and I don't know if I can copy a rom to the phone using fastboot.
Some help would be really appreciated.
ericc191 said:
Guys I could really use some help with this. My phone's rom messed up and so I went into recovery to wipe and reinstall it. Only, I forgot that I'd removed the rom.zip from my storage while I was putting content on the storage a few days prior.
So now, I can't install a rom to my phone, I can't boot into a rom because there is no rom installed, I can't mount my phone to the computer in recovery because it doesn't see it in ADB.
All I have is fastboot and I don't know if I can copy a rom to the phone using fastboot.
Some help would be really appreciated.
Click to expand...
Click to collapse
Just get a USB to SD card adapter and put the ROM back on the card from your PC.
Solarenemy68 said:
Just get a USB to SD card adapter and put the ROM back on the card from your PC.
Click to expand...
Click to collapse
The HTC One doesn't have a micro sd card.
It seems my only options are to use an OTG cable and mount it from a flash drive or find a system.img and boot.img.
I found a solution to recovering my device and my original question. XDA search saved me a long night of stress.
After installing this universal ADB driver, ADB was recognizing the phone in Recovery. It wouldn't let me mount the internal storage or use sideload, but I was able to push my rom.zip to /data/media/0/ and voila problem solved.
slayaman22232 said:
Hey guys,
I'm having a lot of trouble with my AT&t HTC One. I was trying to update it to android revolution v62 and by accident i wipe my entire internal sd card and I have no rom on the phone to boot into right now. I know you can sideload a rom or put a rom on your sd card via this guide http://forum.xda-developers.com/show....php?t=2318497. But the problem is I can not get my computer to recognize my phone. I have the android sdk installed with all the updates. I have the HTC drivers installed as well. I just need my computer to recognize my phone. It only shows up in device manager when i put it into fastboot mode. I tried to do the RUU but it couldn't recognize the phone. Also when I try to do adb devices, it also shows that no devices are connected I think it's a driver issue. Also I'm on windows 7 64 bit. Thanks so much!
Also my phone is
S-off
unlocked
EDIT:
I finally figured out how to fix it.It was a driver issue the whole time. The HTC drivers were not working and what I ended up doing was using this driver download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above) and then i just pushed the rom to my sd card and installed it. I hope this helps anyone else out there.
Click to expand...
Click to collapse
Related
Just wondering if anybody has had this issue before. I searched around a bit but haven't found a clear answer yet. After flashing a kernel through Kernel Manager Pro, the phone rebooted, checked sdcard as usual, then popped up that there was an error and sdcard was mounted as "read only". I had made a backup right before flashing the kernel like I usually do so I restored that backup but got the same error. I booted into recovery and wiped data and cache and so on and rebooted into android. No luck with that either, so I tried a backup of a different rom I had. Still the same issue (also wiped between restoring backups for good measure). Plugging it into the computer would work because it would not recognize the sdcard as a removable drive (had the "use as disk drive" option chose on my phone to clarify). Finally I had to boot into recovery, mount usb storage, right click on the drive that my phone was, and click "check and fix for errors". After a very long wait it finished and I unmounted usb storage and rebooted into android again. That finally fixed it (whew), and now I have a folder on my sdcard that is titled "FOUND.0000", and there are text files in it with names such as "FOUND.0000CHK, FOUND.0001CHK" and so on. Do I need these files anymore or is just showing me what was wrong and fixed on my sdcard? Will it cause any issues if I delete the folder? Sorry if all this is confusing or stupid. I just have never had an issue like this before and I have rooted and used quite a few android phones and tablets. Im not a noob but I definitely do not know that much about this kind of stuff so any help would be greatly appreciated! TIA
Travis
TMYINC said:
Just wondering if anybody has had this issue before. I searched around a bit but haven't found a clear answer yet. After flashing a kernel through Kernel Manager Pro, the phone rebooted, checked sdcard as usual, then popped up that there was an error and sdcard was mounted as "read only". I had made a backup right before flashing the kernel like I usually do so I restored that backup but got the same error. I booted into recovery and wiped data and cache and so on and rebooted into android. No luck with that either, so I tried a backup of a different rom I had. Still the same issue (also wiped between restoring backups for good measure). Plugging it into the computer would work because it would not recognize the sdcard as a removable drive (had the "use as disk drive" option chose on my phone to clarify). Finally I had to boot into recovery, mount usb storage, right click on the drive that my phone was, and click "check and fix for errors". After a very long wait it finished and I unmounted usb storage and rebooted into android again. That finally fixed it (whew), and now I have a folder on my sdcard that is titled "FOUND.0000", and there are text files in it with names such as "FOUND.0000CHK, FOUND.0001CHK" and so on. Do I need these files anymore or is just showing me what was wrong and fixed on my sdcard? Will it cause any issues if I delete the folder? Sorry if all this is confusing or stupid. I just have never had an issue like this before and I have rooted and used quite a few android phones and tablets. Im not a noob but I definitely do not know that much about this kind of stuff so any help would be greatly appreciated! TIA
Travis
Click to expand...
Click to collapse
This is very interesting. I've never had a problem with the SD card. Is this the same SD card that shipped with the phone?
When you, "right click on the drive that my phone was, and click "check and fix for errors" is that a windows command? Does the picture below represent the action you took?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you end up deleting those files? If so, what happened?
I am having some weird errors with my SDcard myself. I went from a flashed kernel on CM7 off to another ROM. Rebooted and SDcard errors out the wazoo. I am getting MD5 mismatches on a lot of my backups at that. If I can get a ROM that fully boots, I will likely wipe the sdcard and start over to see if it isn't from a corrupt file or something.
The same exact thing happened to me. I mounted my SD card from recovery and windows auto fixed it.
If that didn't work I was going to wipe backup. wipe, and reformat.
I was trying to install Cyanogenmod 9 earlier and updated my CWM. Now I can't get it to view anything on my SD card and I have no ROMs on my internal, what do?
KosanRio said:
I was trying to install Cyanogenmod 9 earlier and updated my CWM. Now I can't get it to view anything on my SD card and I have no ROMs on my internal, what do?
Click to expand...
Click to collapse
what did you update on CWM?
cant you mount your phone thru cwm, to be seen on your pc to copy a ROM over to install/flash?
Are you still trying to install CM9?
if all else fails you can use one of the "one click to stock" then put cwm (i use touch), then put a ROM to flash on...
all tools and ROMs are listed here:
http://forum.xda-developers.com/showthread.php?t=1740367
Holy that's a pickle
This Public Service Announcement brought to you by a pimped out At&t gNote rocking *The Collectives* AOCP CP1...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just because your in recovery and no roms show in your files doesn't mean your stuck. Just hit reboot system now and it'll take you back
Biggest dog on the block, NOTE!! ICSed AOKP
also you can try to mount the SD while in recovery then hook up to pc via usb cable and copy the ROM
note i haven't checked CWM recently so the option to mount SD might no longer be there
Teufel Hunden said:
Just because your in recovery and no roms show in your files doesn't mean your stuck. Just hit reboot system now and it'll take you back
Biggest dog on the block, NOTE!! ICSed AOKP
Click to expand...
Click to collapse
That would be the dumbest thing to remove...It's in mounts and storage...like always
I was recently in the same boat.
It all else fails you can use Odin to push a kernel or rom or what ever. This assumes you can get into download mode.
How can I push from ODIN please? I am looking but not sure.
zeddock
I just did this to my phone. I flashed the new CWM on from Rom manager and then booted to recovery. I cleared all the sys data and caches to flash a new rom and then none of my system files will show up and my phone also wont go into download mode. Kies and my computer wont recognize my device now that im stuck in recovery either. No idea how im going to fix it....
tmb993 said:
I just did this to my phone. I flashed the new CWM on from Rom manager and then booted to recovery. I cleared all the sys data and caches to flash a new rom and then none of my system files will show up and my phone also wont go into download mode. Kies and my computer wont recognize my device now that im stuck in recovery either. No idea how im going to fix it....
Click to expand...
Click to collapse
I am really stuck.
Tried to root, looked good.
flashed CWM... looked good.
Tried to flash CM9...
whoa.... things went pretty weird.
Now, I cannot get sdcard mounted, or formatted.
I guess I had a corrupted .zip file, but now how do I get the file onto the phone. (ATT Note without external SD)
And now... I cannot even browse to a zip file to install in CWM... bounces back to menus.
Please help?
zeddock
Go into download mode on your device by holding the volume down and power at the same time. Then use odin on your computer to flash a stock rom or use the emergency recovery method.
-Once you go NOTE, you'd say 4 inches a Joke
NOTE user:
"take a deep breath, make sure to get a good look at it, relax and slowly take it in, the size is overwhelming at first but you will have a happy ending afterwards".
Woman:
I have the TF201 unlocked with the tool ASUS put out a while ago. I was running a JellyBean ROM, the specific one is escaping me. It was running pretty stable tho i was never able to get it to back up the ROM, it would create a file but it would have no MD5 and fail. Anyways, it ran out of battery the other day and now when i turn it on it stops at the ASUS splash screen with the "The Device is Unlocked" in the top corner. It will stay like that until the battery runs out or I reset with (power + v down). I can enter ClockworkMod Recovery so I put the latest CM10.zip on a micro SD to install but i get "No FIles Found" - Any idea if this is recoverable?
Sorry this is a repost, i moved before i was able to really get into the steps that the last people suggested and when i tried i ran into problems...
Thanks for your help
cassato said:
I have the TF201 unlocked with the tool ASUS put out a while ago. I was running a JellyBean ROM, the specific one is escaping me. It was running pretty stable tho i was never able to get it to back up the ROM, it would create a file but it would have no MD5 and fail. Anyways, it ran out of battery the other day and now when i turn it on it stops at the ASUS splash screen with the "The Device is Unlocked" in the top corner. It will stay like that until the battery runs out or I reset with (power + v down). I can enter ClockworkMod Recovery so I put the latest CM10.zip on a micro SD to install but i get "No FIles Found" - Any idea if this is recoverable?
Sorry this is a repost, i moved before i was able to really get into the steps that the last people suggested and when i tried i ran into problems...
Thanks for your help
Click to expand...
Click to collapse
first thing to try is to install the latest TWRP that will read both sd cards and download AOKP jelly bean unoficial rom(what an awesome rom). put that on your removable storage then try and install through TWRP and all should be good.
neckbonest said:
first thing to try is to install the latest TWRP that will read both sd cards and download AOKP jelly bean unoficial rom(what an awesome rom). put that on your removable storage then try and install through TWRP and all should be good.
Click to expand...
Click to collapse
I tried to flash twrp via fastboot using the command -i 0x0b05 flash recovery twrp.img. It says it finishes successfully and there is a solid blue bar on the tablet but it is frozen. i hard reset then enter recovery and i end up in ClockworkMod Recovery still, any idea what i am doing wrong?
not that you will have to use it yet but did you do the nv-flash before going to jelly-been?
cassato said:
I tried to flash twrp via fastboot using the command -i 0x0b05 flash recovery twrp.img. It says it finishes successfully and there is a solid blue bar on the tablet but it is frozen. i hard reset then enter recovery and i end up in ClockworkMod Recovery still, any idea what i am doing wrong?
Click to expand...
Click to collapse
Extract the attached file and boot into fast boot on your Prime. Run the .bat file and it automagically flashes the latest version of TWRP for the Transformer Prime.
McJesus15 said:
Extract the attached file and boot into fast boot on your Prime. Run the .bat file and it automagically flashes the latest version of TWRP for the Transformer Prime.
Click to expand...
Click to collapse
Tried that and got some errors... ran as admin as well with no luck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is there a way to install twrp directly onto the microSD card from your computer? When i flash it, i get the Finished message in command prompt and the blue bar on the tablet shows up but when i take the card out of the tablet and pop it in my computer it is empty
My understanding is recovery images are internal sd only. Back ups are on the sd card.
Sent from my Zio using xda app-developers app
McJesus15 said:
My understanding is recovery images are internal sd only. Back ups are on the sd card.
Sent from my Zio using xda app-developers app
Click to expand...
Click to collapse
Thanks, i didnt know that... any other suggestions on getting twrp on there then?
i flashed the twrp ICS blob and it finally put twrp on there. after that i was FINALLY able to flash the AOKP rom and it works, thanks everyone
My fellows and friends,
One of these days, I received an update from LineageOS and when installing it from OTA ( using TWRP ), the first lines ( about 10 to 15 ) from the istallation sequence activities were all red, showing that something went wrong. Immediately I removed the batery to stop the process and installed the first version of the custom rom, using the TWRP. It worked fine and I received some notifications about the new revisions of the rom. I skipped the one that caused problems and accepetd the download the one on the Nov, 17, 2018 of the rom, and had installed. It appeared to me that everything was ok but, one day I turned the phone off during thje night. The next morning, I tryed to boot the phone without success. It started an infinite loop situation..... So, I tryed to repeat the same procedure to install the very first version of the rom using TWRP at the recovery mode. When I was using the TWRP to perform the advanced wipe, the dalvik cache, data and system could not be wiped. The answer about the problem was shown as : failed to mount /efes ( inavlid argument ).
I got the information that, in cases like that, the stock rom should be installed. I downloaded it from www.stockrom.net and had it istalled with the use of Odin. Unfortunately, the boot loop was there again.
What was worse now was that no TWRP was installed and Odin could not recognize the phone, although I had installed the newest set of drivers from Samsung, applicable to any devices from them.
Please I need your help to see if there is a possible solution to solve this case. Phone Model: GT-i9300 SSN -I9300GSMH - in Brazil
The message I got from the phone: E: failed to mount /efes ( inavlid argument )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thank you in advance any help from you guys,
Gilberto Leite
Flashing a stock ROM will always replace TWRP with the stock recovery.
Are you trying to flash the latest stock ROM?
Do you have a backup of the EFS directory? It's an important directory as that is where a lot of information, including the IMEI is stored.
Hi Audit 13, thnaks for replying.
No I don't have the back up for the folder you mentioned. I was trying to install the last stock rom downloaded from www.stockrom.net, which I suppose was the last one. The worst part is that to computer does not recognize the phone since then.... I do not know what to do. I suppose that there is not a way to back up the folder you mentioned. I think that I have to install something from the very begining, as if the phone was to receive the installation of the very first program, as if it was just coming from the factory, totaly clean. Is that so? Am I right? And, how to do it? I tryed to download the stock rom from Samsung, but I think it was difficult and could not have it accomplished.
Thanks a lot and I'm still waiting instructions of how to solve this problem.
You should try using different USB cables and different USB ports to recognize the phone.
I assume you are using Windows since you mentioned Odin. When you connect the phone, do you see any new devices appear under Device Manager?
What is the phone's model # in download mode?
Is the the ROM you used: https://www.stockrom.net/2015/11/stock-rom-original-de-fabrica-samsung_19.html ?
Did you try using Odin 3.07?
Hi Audit13!
Thanks a lot for your help! I've already got hte files you mentioned and am preparing for trying to do the procedure you taught me.
Thanks again and soon, I hope, to be back to confirm whether it succeded.
Bie....
Hi Audit13,
Unfortunately the computer is not recognizing the SGS device.
I was ready to install the sock rom you suggested, had downloaded the Odin 3.07. I use Windows 10 and the latest drivers have been installed. The phone was in the download mode and tryed all available USB port. I've waited some minutes in each USB port for recognition with no success.
I thank you for your help. Is there any other method we could try? If you could please indicate, I thank you again.
Is there a method available using ADB procedures?
Hope there is.
Thanks, anyway for the help.
Hi Audit13
I think that the situation got a little worse. I tryed to do some recovery on the emergency recovery mode, but none of them succeeded. Now, what I get when tryng to get to the recovery mode is an android robot with an open belly with a red triangle coming out of it.... It gets to thedownload mode, but no recognition from the computer. This happened after trying to ionstall the stock rom obtained from the site you mentioned. The only thing that I could do was through the Universal-Android-Diag-Enabler-V2, what made the qualcomm start. Is there a way to make a comand to the phone that could star the USB debbuging? I tryed the various ODIN versions but with no success.
There is another problem - I'm using Windows 10 and the PowerShell uses different command lines not recognized by adb. I tipped devices and the program indicated that there was an mistake.
Is ther an Instructions Booklet for Odin?
What is your opinion? Do you think that there still exists a solution for my phone's case? If so, what to do?
Please, I ask you to help me on solving this problem.
Thanks in advance...
Hi All,
My son brought his Tablet to me yesterday and told me "It's not working". I looked at it and it was stuck on the Lenovo screen. I booted into recovery but it looks like its messed up here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
image of issue -> ibb.co/1zCLyYr
After some probing my son tried to unlock it and load a rom, then restore stock rom and it was the last that caused the issue.
Now generally being able to get to recovery is a good thing but in this case it looks completely messed up and nothing will mount including the SD card.
It looks like adb is no longer enabled, it is not rooted and USB debugging is no longer enabled.
So it says
E:failed to mount block devices /dev/block/mmcblk1p1
E:remount block devices /dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /cache
And so on.
This means I can't actually get to the SD Card with any update on it if I go to apply update from sdcard there is nothing showing in the sdcard directory
Have tried the following
- Apply from ADB (Device does not connect)
- wipe/factory reset,
- wipe cache
- reboot to bootloader
I can't get into any download mode either.
I did get it at least to make a mounting noise temporarily in Windows 10 but couldn't actually get to it or browse from there and haven't been able to repeat this.
Just wondering if there is anything I can do, or whether I should just forget it, surely there is some way to connect to it.
Cheers
Dan
Interestingly I plugged it into my mac and first it booted to a charging screen which hadn't happened last night.
Also if I leave it plugged into my mac for a little while Android file transfer eventually pops up and tries to connect but then says "Could not connect" but there is some life there at least.
A little more probing and I plug it into my Ubuntu rig and it starts to be recognized as Android but then get "Cant load MTP Device" if I try to browse it.
Looking into dmesg gives me
idProduct=78e8 (This is a Qualcomm powered device)
It then tries to mount it all but ends up mounting it as a Lenovo CD-ROM.
I can't seem to probe it past that, thinking its a futile effort but hoping for a miracle
Further update got it to the point where if I go to "apply update from ADB" the device is recognized and I try sideload but it just fails out on xfer 0.0
Silvertails said:
Further update got it to the point where if I go to "apply update from ADB" the device is recognized and I try sideload but it just fails out on xfer 0.0
Click to expand...
Click to collapse
You CAN NOT sideload an official ROM / OTA update with a modified device. You must have stock recovery and be non-rooted or it will fail every single time.
jwoegerbauer said:
You CAN NOT sideload an official ROM / OTA update with a modified device. You must have stock recovery and be non-rooted or it will fail every single time.
Click to expand...
Click to collapse
I cant do any kind of stock recovery, sideload is the closest I can get to anything, I think he must have put a different rom in there that has stuffed it up.
Is there anything I can do any steps I can take?
Windows won't recognise it so the QPST/QFIL method won't work
any steps or help would be appreaciated I have trawled every thread I can find here an across the internet
@Silvertails
ADB Sideload is a special mode that internally makes use of / runs Android's recovery binary ( AKA Stock Recovery ).
You test whether this mode is ready or not by simply running on PC the commands
Code:
adb devices
adb reboot recovery
If successful then you in Recovery select option "adb sideload" and on PC run
Code:
adb sideload <FILE-NAME.ZIP>
There's a very good thread on XDA here that deals with this model and recovering from bricks.
https://forum.xda-developers.com/thinkpad-tablet/general
Finally got this to work.
Ordered a cable that could get me into deep download mode as jumping the pins on the mobo was not working, the cable didnt get me into download mode, but what i discovered was that if I uninstall it being recognized as a CD ROM and messing about a bit I eventually got it to recognize as an Android Bootlader Interface using the lenovo drivers. I managed to use fastboot even though the device wasn't properly recognized to install TWRP. I got a success message and managed to reboot into TWRP recovery. The device then mounted as Lenovo but a different one, but at least it was mounting.
I still couldn't copy anything over to it, so I put the OTA default ROM on an SDCard and managed to get it to install from there and update to latest versions, and now its all working again.