Hi everyone,
I wanted to start using CM 11 on my HTC One S when I realized my firmware was too ancient to run it.
Following this thread , I managed to upgrade my firmware and reach the point where I could access my recovery but could no longer see my sdcard and could no longer mount it.
I've been searching hours for a solution, but no avail, and any solutions that involve adb commands do not work for me. When I run an adb devices command my device doesn't show up, however it does in fastboot.
Currently I'm on HBOOT 2.15, S-on. unlocked
Can anyone shed any light on this?
Thanks in advance!
Update: FIXED, I tried the method in this thread the CWM recovery from this fix allowed me to adb push my ROM and fastboot flash boot boot.img , even though the SD card didn't mount. Booted up phone and all worked Seems only this recovery allowed me to adb push.
Related
I cannot mount /sdcard.
Phone history: AT&T One X
Rooted--forget which method
Followed "everything you need to know" how to pdf by PerterHTC to upgrade to 1.85 from 1.73 then change cid and unlock bootloader. Loaded CWMR. then loaded cleanrom 2.0.
security policy for work wanted encryption enabled so after a few tries I also got that to work. everything fine for a couple of weeks. then after a restart the phone could not access /sdcard (yes I put in the proper decrypt code after each bootup)
Tried a factory wipe to remove the encryption and start over. during the wipe it could not mount the sdcard so it failed.
current state:
locks after boot amimation
I can get into fastboot and cwmr
cannot mount /sdcard which means I cannot format, partitioin or anything.
adb cannot connect to device.
most of the solution I have seen either need adb or remove sdcard and put in computer---can't do that here
I have tried various adb and fastboot commands none work because it cannot find phone. same with RUU.
I have tried wiping from cwm and fasboot
In the device manager I can see the phone on the device list in device manager on PC.
I have hope it is not bricked because I can get into cwm and fastboot but I have hit the edge of my knowledge.
Any help would be great...Thanks.
I was able to get it to respond to fastboot and re-lock the boot loader. Then I was able to run the 1.85 installer from my pc.
Woot, all good now.
Sent from my HTC One X using XDA
Hi!
First of i got a Htc one S from sweden and have been using utb rom for the last weeks with CWR Touch. After hearing that Cyanigenmod 10 was not as buggy as i thought i decided to use it.
This is what i did:
Downloaded the rom with rom manger - the phone restarted and viped everythig and started to install. It then aborted because of something wrong with the file.
Now i dont have a rom on my phone and i cant acces my SD card where i got other roms waiting for me to install.
When i try to use any ADB commands like "adb devices" nothing shows up under devices.
I tried "adb kill-server" and "adb devices" still nothing. When i use "fastboot devices" my device shows. I have tried both Hboot and Fastboot.
I tried to use one guide i found where someone used "all in one toolkit" to go back to stock recovery, delete space, re-enter recovery but that did not work for me.
I tried to adb push roms to my phone but still, no luck because my phone cant be found.
I tried to use the software "quick adb pusher" and with it i could se my device show and i could acces the storage, but there is a folder named "error device not found".
I tried to use "all in one toolkit" so i atleast could get CWR back on my phone, it flashes and finds my device, but when i try to rebot to recovery nothing happens anymore.
Do anyone have a fix for this? 7h later and im out of ideas.....what ever small ammount of knowledge i have about this ended hours ago and google cant help me anymore.
I even tried to download a ruu to try and install it but keeps telling me its the wrong version and then the installation aborts.
i have htc sync and htc usb drivers.
I also downloaded....well atleast 15 diffrent drivers and tried them still no adb device found.
I tried to download android atk but it complains about me not having java runtime but i installed it.
Im using windows 7 x64 bootcamp and osx
aasterix said:
Now i dont have a rom on my phone and i cant acces my SD card where i got other roms waiting for me to install.
Click to expand...
Click to collapse
In fastboot you can flash boot images and recoveries.
You can only use ADB when booted (which you can't) or when in recovery.
If you are unable to mount /sdcard in recovery, check the sticky on how to fix unmountable sdcard. It's here in Q&A.
Once you can mount /sdcard in recovery, you can adb push roms to it. You have to be in recovery for that, not in fastboot. First flash the boot image for your rom from fastboot, then boot into recovery and push and flash the rom. Wipe your data and cache.
You can do this either on windows or osx but on osx you dont need drivers so you can't have the wrong ones.
Good hunting,
-Jobo
The CWM version shipped with all-in-one doesn't work. CWM doesn't mount the sdcard anyway. I'd suggest TWRP because it can mount the sdcard and also has other features that CWM lacks.
Just boot into bootloader and in fastboot:
fastboot flash recovery twrpfilename.img
Then do as jobo said within the recovery.
Sent from my HTC One S
Pheroh said:
CWM doesn't mount the sdcard anyway.
Click to expand...
Click to collapse
What I meant, and what I think aasterix meant as well, is not mount the sdcard onto your computer over usb, but just mount the sdcard onto the root filesystem in recovery on the device.
If that doesn't work, you have to fix that first using '[HOW-TO] Fix soft brick & error mounting sdcard'. Once you can mount /sdcard in recovery (any custom recovery will do) you're good to push and flash your favorite rom.
I see that there are other threads for this and I have read through them but they don't seem to be helping. I was in the middle of using the Nexus Toolkit to install a Rom when the program temporarily booted TWRP after it removed old os and then it stopped working and I went to reboot from the temporary boot when it told me I had no OS. Because I do not have a ROM my computer does not detect ADB status so I cannot seem to get anytging on the device. I also can seem to get the sideload to work. I am not quite sure how to use the CMD for this and I have used other threads suggestions like starting cmd in the folder that has the rom i want to flash and the typing the adb commands but it doesn't seem to work. Can someone help please?
STOP USING TOOLKITS!
If you can't get adb to work, I suggest following this thread to get it working: http://forum.xda-developers.com/showthread.php?t=2588979
Thank you, but my adb drivers are installed. my device can only enter fastboot and recovery so even now with that tool I dont know how to install an os back on my device.
Just flash the images from fastboot. There are a thousand posts on how to do this here.
"fastboot flash system system.img"
Hi there, long time reader, possibly posted before but I cant remember my account name so I suppose I am a newbie.
1) Unlocked boot loader fine
2) Installed TWRP fine
3) Rooted fine
4) Installed CM11 and Gaaps
5) Restored all my apps from Titanium
Yaaaay ready to rock or so I thought. Only to be faced with "mobile network not available" so my intention was to flash another CM11 or other CM if it was possible to get it actually working to make phone calls. In my attempts to do this I cleared everything, so no OS. I can get into the bootloader and recovery mode still but that
ADB thing refuses to work. So as of now my PC cannot see the device to copy the rom files onto it.
Am I right in thinking if I get a USB OTG and put a rom on it, I can flash it from there??
I would settle for any custom rom at this stage that functions and doesnt have bloatware.
Failing that, would it be allowed here to ask for an image of a working htc one mini m4 to be uploaded somewhere that I can work with?
I wont be able to do anything until i get the USB OTG. Ive tried everything with ADB.
Your help would be so much appreciated.
hi,..
So first I´m not quite sure if an otg will work but it´s really worth to try it...
But after a (maybee) sucsessful flashing of a ROM via OTG there is no way around to get adb and fastboot to work.
Next I have to say is you should post some information about your phone.
h-boot Version
OS version
CID-Number if you know.
Only with this information sombody here can help you to find the right ROM.zip for flash trough recovery.
(if the firmware and the ROM do not match you are running in to multiple issues)
greets
Thank you
*** tampered ***
*** unlocked ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.24.40e.00.26
OpenDSP-V19.2.0268.0927
OS--
eMMC-BOOT 1024MB
So,.....
It would be very interessting what firmware was on your device..
But as we can see the bootloader shows "OS- " so I suppose with h-boot 2.21.0000 it was 3.10.xxx.x.
I ran in same Problem a few weeks ago.
Recovery write: Can´t mount sd card and can´t mount data
I formated data in TWRP-recovery....(formated not only wipe...deletes everything on device).
As far as I remember after that adb returns to work and I sideloaded a new system.
I recommend you to flash first a stock or stock "near" system then and try to get s-off (to get rid of your problems)
But your first goal is to get a working OS on your device and get adb to work
A little help could be:
In fastboot mode :
"fastboot erase cache"
then reflash TWRP 2.7.1.1 with "fastboot flash recovery recoveryname.img"
If this don´t work out the only way is USB-OTG cable.
greets
edit: honestly I think the CM11 thing is a story after getting device back to life...
an other question ....what do you get if you type in adb when device is in recovery mode: "adb devices"
If needed here you can find a working sense 5.5 rooted stock rom (should work with your frimware) to start with:
http://androidfiles.org/getdownload...Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip
could help also:
http://forum.xda-developers.com/htc-one-mini/general/adb-fastboot-device-try-t2800519
shivasrage said:
So,.....
It would be very interessting what firmware was on your device..
But as we can see the bootloader shows "OS- " so I suppose with h-boot 2.21.0000 it was 3.10.xxx.x.
I ran in same Problem a few weeks ago.
Recovery write: Can´t mount sd card and can´t mount data
I formated data in TWRP-recovery....(formated not only wipe...deletes everything on device).
As far as I remember after that adb returns to work and I sideloaded a new system.
I recommend you to flash first a stock or stock "near" system then and try to get s-off (to get rid of your problems)
But your first goal is to get a working OS on your device and get adb to work
A little help could be:
In fastboot mode :
"fastboot erase cache"
then reflash TWRP 2.7.1.1 with "fastboot flash recovery recoveryname.img"
If this don´t work out the only way is USB-OTG cable.
greets
edit: honestly I think the CM11 thing is a story after getting device back to life...
an other question ....what do you get if you type in adb when device is in recovery mode: "adb devices"
If needed here you can find a working sense 5.5 rooted stock rom (should work with your frimware) to start with:
http://androidfiles.org/getdownload...Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip
could help also:
http://forum.xda-developers.com/htc-one-mini/general/adb-fastboot-device-try-t2800519
Click to expand...
Click to collapse
Thanks. adb devices will sometimes show the serial number I think, adb push CMupdate.zip I get "cannot read cmupdate.zip"
Fastboot flash recoery recovery.img works.
I have ordered a USB OTG so hopefully by friday I will have it. Im not sure how to show you the firmware? I thought I listed everything needed?
No, its not your fault...
Normaly firmware ist listed in bootloader under OS-3.10.401.3 (for example).
But sometimes after a bad flash when the partitions are messed up or so OS dissapears from bootloader like we can see in your case.
I know from HTC ONE M_7 that there are also some releases of TWRP-recovery that make dissapear OS-Numer from bootloader
but I don´t know if this is similar to the HTC One Mini.
If you get a a serial nuber from adb in recovery mode.. adb should work.....
Do you know how to sideload a ROM via adb and have you allready tried it?
greets
shivasrage said:
So,.....
It would be very interessting what firmware was on your device..
But as we can see the bootloader shows "OS- " so I suppose with h-boot 2.21.0000 it was 3.10.xxx.x.
I ran in same Problem a few weeks ago.
Recovery write: Can´t mount sd card and can´t mount data
I formated data in TWRP-recovery....(formated not only wipe...deletes everything on device).
As far as I remember after that adb returns to work and I sideloaded a new system.
I recommend you to flash first a stock or stock "near" system then and try to get s-off (to get rid of your problems)
But your first goal is to get a working OS on your device and get adb to work
A little help could be:
In fastboot mode :
"fastboot erase cache"
then reflash TWRP 2.7.1.1 with "fastboot flash recovery recoveryname.img"
If this don´t work out the only way is USB-OTG cable.
greets
edit: honestly I think the CM11 thing is a story after getting device back to life...
an other question ....what do you get if you type in adb when device is in recovery mode: "adb devices"
If needed here you can find a working sense 5.5 rooted stock rom (should work with your frimware) to start with:
http://androidfiles.org/getdownload...Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip
could help also:
http://forum.xda-developers.com/htc-one-mini/general/adb-fastboot-device-try-t2800519
Click to expand...
Click to collapse
shivasrage said:
No, its not your fault...
Normaly firmware ist listed in bootloader under OS-3.10.401.3 (for example).
But sometimes after a bad flash when the partitions are messed up or so OS dissapears from bootloader like we can see in your case.
I know from HTC ONE M_7 that there are also some releases of TWRP-recovery that make dissapear OS-Numer from bootloader
but I don´t know if this is similar to the HTC One Mini.
If you get a a serial nuber from adb in recovery mode.. adb should work.....
Do you know how to sideload a ROM via adb and have you allready tried it?
greets
Click to expand...
Click to collapse
Yes side load does not work.
I have a serious headache now. I tried so many roms and none of them let me make or recieve calls. The 3g mobile data is working. Would this work if the IMEI was blocked?
I also tried to update the firmware and ran into problems error 155 and error 132. I am really close to giving up.
I'm running Ubuntu CLI only and am running into a little problem.
When I have my phone booted into cm11/cm12 and I run adb devices I can see my oneplus one, however when I reboot to the bootloader andd see the fastboot icon displayed on the phone i no longer see my phone when I run adb devices.
This isn't a huge problem as long as I have a rom saved to the emulated sdcard, however if I run into problems and loose a backup rom how would I go about pushing a rom to my onplus one since I cannot see the onplus in fastboot?
Thanks for any and all help, and I hope I have provided enough info!
nevermind
Im and idiot... I booted into recovery and adb worked there, I'm used to always pushing from the bootloader so didn't even think to try this.
Adb doesn't work in fastboot mode, only fastboot works in fastboot mode.
Transmitted via Bacon