Related
When trying to restore/unroot my One S something bad happened. I'm not sure, but I or the program I tried to use somehow erased the memory and completely removed the phone OS. What should I do to get my phone back to life?
EDIT:
My phone is back to life!
The solution that worked was a mixture of a few previously posted on xda.
I followed this tutorial: http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#ROM_Flashing
Under ROM flashing I did steps 4-7 and then flashed the boot.img for my chosen Rom(Currently UTB: http://www.connect-utb.com/utb-rom-for-the-htc-one-s/) via CMD. Then I powered down, waited for a bit, and started the phone again. The phone finally worked as it was supposed, I got past boot image and entered the normal phone configuration.
The reason I chose UTB Rom was because someone else have had positive results with this Rom
(http://forum.xda-developers.com/showthread.php?p=25557817#post25850720 post #8),
which also proved correctly for me as I tried to install another Rom without success just a few mins later. (To get it to work again I followed my own instructions above, and it worked)
Thanks for your help! And I hope this solution will guide and help others with similar problem in the future!
-Heart
HeartOfFart said:
When trying to restore/unroot my One S something bad happened. I'm not sure, but I or the program I tried to use somehow erased the memory and completely removed the phone OS. What should I do to get my phone back to life?
Click to expand...
Click to collapse
Hello,
If you can get to the bootloader then you should relock it and flash the RUU for your phone. That will return it to stock and you can reroot or do whatever.
Rsotbiemrptson
You could also just reflash the ROM of your choice by going into TWRP custom recovery, mounting your sd card and copying the ROM over.
Then flash the ROM, and dont forget to also fastboot the relevant boot.img for that rom.
TWRP recovery is better than CW as it does allow you to mount your sd card. So download TWRP (google it) and fastboot flash recovery <filename>.img
then load the recovery then mount sd card. You should be good to go from there, unless your SD Card is corrupted. If that is the case, then check http://forum.xda-developers.com/showthread.php?t=2086156
Rsotbiemrptson said:
Hello,
If you can get to the bootloader then you should relock it and flash the RUU for your phone. That will return it to stock and you can reroot or do whatever.
Rsotbiemrptson
Click to expand...
Click to collapse
Yes, I can get into bootloader, but can't find the right RUU for my version.
Thanks guys, it's awesome that you help me!
Didn't find the correct RUU, so I get an error..
The other method posted will be tried out tomorrow!
AKToronto said:
You could also just reflash the ROM of your choice by going into TWRP custom recovery, mounting your sd card and copying the ROM over.
Then flash the ROM, and dont forget to also fastboot the relevant boot.img for that rom.
TWRP recovery is better than CW as it does allow you to mount your sd card. So download TWRP (google it) and fastboot flash recovery <filename>.img
then load the recovery then mount sd card. You should be good to go from there, unless your SD Card is corrupted. If that is the case, then check http://forum.xda-developers.com/showthread.php?t=2086156
Click to expand...
Click to collapse
I'm trying, but it doesn't work for me. Will give some more effort into this tomorrow. Does anyone have a good way to find the right RUU?
So I think I made some mistakes upgrading to Cyanogenmod 10.1 -- here's what I did:
I used Hasoon2000's HTC One X All-in-One Kit to unlock my bootloader via the xfactor exploit and the HTCDev method. Then I flashed a custom kernel and cyanogenmod 10.1. It's very buggy, reboots constantly, disconnects from AT&T's data network on a whim, etc. Someone suggested that the problem was that I didn't upgrade my hboot first. I'm currently on hboot 1.14, and after running the all-in-one kit, I now have supercid.
After that, I got the bright idea that maybe I could upgrade to a jelly bean firmware (hboot) after the fact. I followed a guide for upgrading hboot at guidingtech.com. Of course, since my cid is now 11111111, I couldn't verify that my cid was correct, but being a noob, I decided to try anyway. I got through to this command: fastboot flash zip firmware.zip, but that failed. I couldn't flash the new firmware. So I though, "Oh well, I'll just keep using my phone as is until I can figure out how to get back to stock." But then I got stuck in a boot loop where all I could do was get back to the bootloader. I used hasoon's kit to force my phone into recovery to try wiping dalvik/cache. I managed after some finagling to boot back into my broken cyanogen 10.1, but now that phone can't access internal storage. So I can't easily just flash a new rom. I suspect the internal storage is corrupted?
I know many of these questions have been answered piece-by-piece, but I don't know how all of these actions combine. Is it easy to get back to stock now? Can I use an RUU to do so? Can I use an RUU with supercid? Any help would be appreciated.
ddevil5 said:
I followed a guide for upgrading hboot at guidingtech.com.
Click to expand...
Click to collapse
Never even heard of that website. Where did you dig that up? I'd caution against using guides and mods from random websites. At a minimum, other websites are often poorly organized, and might get you installing a mod for the quad core One X, which may lead to a brick. Lots of websites just steal content from XDA, anyway. All you need is here, so may as well get it straight from the source.
I'll agree that you probably did a lot of needless, and possibly dangerous steps. I don't recommend trying anything else, unless an experienced user here tells you to do it. Playing with a smartphone is not a trial-and-error activity for n00bs.
Sounds like you corrupted your SD card by trying to do a factory reset in hboot. You should be able to connect the phone to a PC, go to Device Manager, and it should give you the option to format the SD. Format it FAT32, and that particular issue should be resolved.
Can you get into recovery?
What hboot version does it say you are on now?
What kernel did you try to flash? I would have just tried to revert to the stock CM10 before you did all this other stuff. I don't think what you were experiencing originally was related to hboot version.
redpoint73 said:
Never even heard of that website. Where did you dig that up? I'd caution against using guides and mods from random websites. At a minimum, other websites are often poorly organized, and might get you installing a mod for the quad core One X, which may lead to a brick. Lots of websites just steal content from XDA, anyway. All you need is here, so may as well get it straight from the source.
I'll agree that you probably did a lot of needless, and possibly dangerous steps. I don't recommend trying anything else, unless an experienced user here tells you to do it. Playing with a smartphone is not a trial-and-error activity for n00bs.
Sounds like you corrupted your SD card by trying to do a factory reset in hboot. You should be able to connect the phone to a PC, go to Device Manager, and it should give you the option to format the SD. Format it FAT32, and that particular issue should be resolved.
Can you get into recovery?
What hboot version does it say you are on now?
What kernel did you try to flash? I would have just tried to revert to the stock CM10 before you did all this other stuff. I don't think what you were experiencing originally was related to hboot version.
Click to expand...
Click to collapse
I do get prompted to format my drive whenever I plug in my phone. If I format the internal storage will that erase my rom?
I do admit, I'm a total noob, and I should have done a lot more research before messing around with the guts of my phone. I'm on hboot 1.14. I honestly don't know which kernel I tried to flash. My friend suggested to me what I used. It was from an official cyanogenmod guide for flashing 10.1 to my AT&T One X.
Now that I understand how woefully unprepared I was, I'd like to get back to how my phone came out of the box, if that's possible.
ddevil5 said:
I do get prompted to format my drive whenever I plug in my phone. If I format the internal storage will that erase my rom?
Click to expand...
Click to collapse
No, it just formats the SD partition (think of it as a virtual SD card). Anything that was on it will be gone, but its corrupted anyway, so its already gone. The partition with the ROM will not be formatted, nor will hboot, recovery, or radio partition.
Can you get into recovery? If so, after the SD is formatted, mount the SD memory USB, move the CM 10.1 zip file to the SD. Reflash in TWRP, reboot and see what happens. Don't flash a custom kernel, just use the stock CM10.1 kernel (flashes automatically when you flash the ROM).
redpoint73 said:
No, it just formats the SD partition (think of it as a virtual SD card). Anything that was on it will be gone, but its corrupted anyway, so its already gone. The partition with the ROM will not be formatted, nor will hboot, recovery, or radio partition.
Can you get into recovery? If so, after the SD is formatted, mount the SD memory USB, move the CM 10.1 zip file to the SD. Reflash in TWRP, reboot and see what happens. Don't flash a custom kernel, just use the stock CM10.1 kernel (flashes automatically when you flash the ROM).
Click to expand...
Click to collapse
So, what about hboot? Does that need to be upgraded from 1.14 to be compatible with jelly bean?
ddevil5 said:
So, what about hboot? Does that need to be upgraded from 1.14 to be compatible with jelly bean?
Click to expand...
Click to collapse
Absolutely not. Heck, I'm on hboot 1.09, and running Jellybean without a glitch.
That's why I mentioned, I doubt hboot has anything to do with it, and leave it alone.
redpoint73 said:
No, it just formats the SD partition (think of it as a virtual SD card). Anything that was on it will be gone, but its corrupted anyway, so its already gone. The partition with the ROM will not be formatted, nor will hboot, recovery, or radio partition.
Can you get into recovery? If so, after the SD is formatted, mount the SD memory USB, move the CM 10.1 zip file to the SD. Reflash in TWRP, reboot and see what happens. Don't flash a custom kernel, just use the stock CM10.1 kernel (flashes automatically when you flash the ROM).
Click to expand...
Click to collapse
Argh, the problems keep mounting. Whenever I plug it in, I can't even access usb storage. I hit "turn on usb storage" and I get a spinning circle. The only way I can mount anything is if I go into TWRP and use the mount menu. And it give me four tick boxes: 1. mount system 2. mount data 3. mount cache and 4. mount sd card.
Unfortunately the only check box I can't check is the sd card. I can mount the other three. And then I get prompted in Windows to format. But in that case, I obviously will format everything I don't want to format. So I feel kinda stuck.
What about using an RUU? Can that help me get back to stock? My ultimate goal is just to go back to stock. Maybe I'll ROM again in the future but right now, I just want my phone back in a fully functional package!
Any other help out there? I can't get anywhere with this problem.
ddevil5 said:
Argh, the problems keep mounting. Whenever I plug it in, I can't even access usb storage. I hit "turn on usb storage" and I get a spinning circle. The only way I can mount anything is if I go into TWRP and use the mount menu. And it give me four tick boxes: 1. mount system 2. mount data 3. mount cache and 4. mount sd card.
Unfortunately the only check box I can't check is the sd card. I can mount the other three. And then I get prompted in Windows to format. But in that case, I obviously will format everything I don't want to format. So I feel kinda stuck.
Click to expand...
Click to collapse
Did you try to format the SD like I previously mentioned? It won't mount in TWRP (or with the phone fully booted) if its still corrupted. It sounds like you just need to format it. Your problems are mounting, its just the same problem as before, that you haven't fixed yet.
---------- Post added at 09:25 AM ---------- Previous post was at 09:21 AM ----------
ddevil5 said:
What about using an RUU? Can that help me get back to stock? My ultimate goal is just to go back to stock. Maybe I'll ROM again in the future but right now, I just want my phone back in a fully functional package!
Click to expand...
Click to collapse
I think using the RUU to go back stock is just a lot of extra unnecessary work. You wanted to be rooted and be able to flash custom ROMs to begin with, so let's keep it that way.
I don't think it would be that hard to get up and running again (without running the RUU). You just need to do it right.
redpoint73 said:
Did you try to format the SD like I previously mentioned? It won't mount in TWRP (or with the phone fully booted) if its still corrupted. It sounds like you just need to format it. Your problems are mounting, its just the same problem as before, that you haven't fixed yet.
---------- Post added at 09:25 AM ---------- Previous post was at 09:21 AM ----------
I think using the RUU to go back stock is just a lot of extra unnecessary work. You wanted to be rooted and be able to flash custom ROMs to begin with, so let's keep it that way.
I don't think it would be that hard to get up and running again (without running the RUU). You just need to do it right.
Click to expand...
Click to collapse
But how do I format it when my computer won't recognize it?
ddevil5 said:
But how do I format it when my computer won't recognize it?
Click to expand...
Click to collapse
It won't read it as an Android device, or it won't read it at all.
Does it still come up as a bulk storage device or something like that?
bump. Any options for me?
Do you know what adb and fastboot is. It sounds like the prob you having is actually simple to fix. You need to make sure twrp is on your device for recovery for starters if not than flash it through fastboot. Make sure you have HTC drivers ok. You can download HTC sync then uninstall it and it will leave drivers on pc or go to HTC website and get them. 1hr of googling and appling what you learn should get you back on track, if not you need to find a mentor to hold your hand and show you, it may seem overwelming but you will get it.
Sent from my HTC One X using xda premium
I have the same issue right now. i can not mount my sd card at all. im running the cm 10.1. i had to ADB sideload my rom to bring my phone back and now i cant load my gapps. any help would be great! my phone works but no apps etc.
artsonex said:
i have the same issue right now. I can not mount my sd card at all. Im running the cm 10.1. I had to adb sideload my rom to bring my phone back and now i cant load my gapps. Any help would be great! My phone works but no apps etc.
Click to expand...
Click to collapse
fixed my own issue! Just follow the steps above and you should be good!!
Nothing big
Hi, seems like my One S's sdcard partition has corrupted. been using TWRP 2.500 and recently upadted to 2.6.30 to use the new Maximus Rom. During the rom installation, I wiped the sdcard sectrion by mistake so I couldn't get to flash the zip file, then, I've tried multiple times of recovery.img flashings via RUU mode or on the bootloader screen. Finally when I got the TWRP recovery mode again, it says the sdcard folder only accepts 48 MB so I cannot push any custom roms since they are bigger than 500MB... Any ideas? Should I send it to the repair shops? Please Help!! Thank you!
FYI, my phone was
Tampered, Unlocked, S-off
also, when I press mount button on TWRP, this list appears
Cache
Data
Internal SDcard
System
USB-OTG
but I select Internal SD, the computer says the removable disk has only 48MB of available space.(I wiped it multiple times!)
puwa said:
Hi, seems like my One S's sdcard partition has corrupted. been using TWRP 2.500 and recently upadted to 2.6.30 to use the new Maximus Rom. During the rom installation, I wiped the sdcard sectrion by mistake so I couldn't get to flash the zip file, then, I've tried multiple times of recovery.img flashings via RUU mode or on the bootloader screen. Finally when I got the TWRP recovery mode again, it says the sdcard folder only accepts 48 MB so I cannot push any custom roms since they are bigger than 500MB... Any ideas? Should I send it to the repair shops? Please Help!! Thank you!
FYI, my phone was
Tampered, Unlocked, S-off
also, when I press mount button on TWRP, this list appears
Cache
Data
Internal SDcard
System
USB-OTG
but I select Internal SD, the computer says the removable disk has only 48MB of available space.(I wiped it multiple times!)
Click to expand...
Click to collapse
Omg. Why the people dont read op before they are going to flash new Rom. Just follow the instructions.
Sent from my HTC One S
tominozh said:
Omg. Why the people dont read op before they are going to flash new Rom. Just follow the instructions.
Sent from my HTC One S
Click to expand...
Click to collapse
Could you please tell me at least it's repairable or not? I want your help..
Also, I wonder what part I missed so it happened...hmm
puwa said:
Could you please tell me at least it's repairable or not? I want your help..
Also, I wonder what part I missed so it happened...hmm
Click to expand...
Click to collapse
Yes, don't sweat it. It is repairable.
It's hard for my to tell what you missed, because you didn't write what you did. So just follow installation instructions in the first post of maximus Rom. (flash new firmware, modified recovery, then Rom).
Sent from my HTC One S
tominozh said:
Yes, don't sweat it. It is repairable.
It's hard for my to tell what you missed, because you didn't write what you did. So just follow installation instructions in the first post of maximus Rom. (flash new firmware, modified recovery, then Rom).
Sent from my HTC One S
Click to expand...
Click to collapse
thank you! so, for flashing a new firmware, what would be a good firmware to start? any recommendations? i tried the firmware.zip in the install kit but not worked. same 48MB limit on the /sdcard/. any ideas?
:laugh:
Just follow this. It worked for almost all of us..
http://forum.xda-developers.com/showthread.php?p=45621060
gelo01 said:
Just follow this. It worked for almost all of us..
http://forum.xda-developers.com/showthread.php?p=45621060
Click to expand...
Click to collapse
GRT!! Thanks so much for saving my LIFE!!
gelo01 said:
Just follow this. It worked for almost all of us..
http://forum.xda-developers.com/showthread.php?p=45621060
Click to expand...
Click to collapse
All of these steps work for me except flashing the recovery as a ZIP. I get the wrong CID error (code 42 if i remember correctly). Thing is, I flash the .img directly usign fastboot flash recovery and that works but then the install process says, in android, transfer ROM. At this point, I don't have access to the SD card and the ROM is not in my sd card (it was wiped anyway?)
*EDIT*
Ok I changed my CID to 1111111 and now it works to flash the firmware. I still get partitions errors it seems though.
What I did is flash the stock recovery, clear storage, factory reset, reflashed the firmware given in Maximus thread, then the TWRP given and still, I get problems with my sdcard not mounting?
GabeyC said:
All of these steps work for me except flashing the recovery as a ZIP. I get the wrong CID error (code 42 if i remember correctly). Thing is, I flash the .img directly usign fastboot flash recovery and that works but then the install process says, in android, transfer ROM. At this point, I don't have access to the SD card and the ROM is not in my sd card (it was wiped anyway?)
*EDIT*
Ok I changed my CID to 1111111 and now it works to flash the firmware. I still get partitions errors it seems though.
What I did is flash the stock recovery, clear storage, factory reset, reflashed the firmware given in Maximus thread, then the TWRP given and still, I get problems with my sdcard not mounting?
Click to expand...
Click to collapse
if you are talking about mounting usb storage in recovery, then no, you cannot do that on Maximus HD rom. (it's a modified TWRP to work on the new firmware)
You can sideload in TWRP or ADB push the rom to your sdcard.
I would give you a link to a page describing it, but search is unavailable right now, have to try later.
But just search that thread with keyword sideload. There you will find the exact commands to load the rom onto your sdcard.
tivofool said:
if you are talking about mounting usb storage in recovery, then no, you cannot do that on Maximus HD rom. (it's a modified TWRP to work on the new firmware)
You can sideload in TWRP or ADB push the rom to your sdcard.
I would give you a link to a page describing it, but search is unavailable right now, have to try later.
But just search that thread with keyword sideload. There you will find the exact commands to load the rom onto your sdcard.
Click to expand...
Click to collapse
Yea, that's exactly what I ended up doing... it's not clear on any thread though...
Thanks
I went back to CM, didn't like maximus so much and it didn't fix my EDGE only problem so
It went back to 48mb
Hi i had the same problem with my htc one s.So i paniced and for some reason i put s-on(I deleted the os from the pc using mount storage) I managed to fix it by installing the recovery as zip. Then i tried to adb sideload a rom but it didn't work. So i went to boot loader then to fast boot and did fastboot flash zip Energyrom.zip. That gave me an error so i went back to recovery to try to side load the rom again, but my sdcard went back to 48mb.I reflashed the recovery (the one from install package) same thing . What do i do????? I need help asap i want my phone back (IM ONLY 12) Please reply asap.
cyberusman said:
Hi i had the same problem with my htc one s.So i paniced and for some reason i put s-on(I deleted the os from the pc using mount storage) I managed to fix it by installing the recovery as zip. Then i tried to adb sideload a rom but it didn't work. So i went to boot loader then to fast boot and did fastboot flash zip Energyrom.zip. That gave me an error so i went back to recovery to try to side load the rom again, but my sdcard went back to 48mb.I reflashed the recovery (the one from install package) same thing . What do i do????? I need help asap i want my phone back (IM ONLY 12) Please reply asap.
Click to expand...
Click to collapse
I think the easiest way is to flash the stock recovery and then do a sdcard wipe then a factory reset.
After that, you go through the process as described in the maximus rom thread, you will have to flash with sideload. That should work afterward
I am doomed
Hi guys,
Yesterday I decided to try MaximusROM 10.0.0 HD on my HTC One S, which is s-OFF and with superCID. The problem is: I didn't flashed first the rom as it was said, and I just used the Installation Package, installing directly the firmware.zip and the modified recovery. I tried to follow the steps written before, but now my phone works with the stock rom but it says that there are only 48mb in sd card, and that means that I can't even take photos, because I have no memory left. I found out that my phone, when is booted up, in settings says that I have 15,96GB of space for applications. What can I do?
GabeyC said:
I think the easiest way is to flash the stock recovery and then do a sdcard wipe then a factory reset.
After that, you go through the process as described in the maximus rom thread, you will have to flash with sideload. That should work afterward
Click to expand...
Click to collapse
I think I need to to that process my sdcard appears to be 10 gig only. Do you have a link for stock recovery? mine is S4.
48 mb storage = new 3.16 firmware
fix = flash custom 2.6.1 twrp
Sent from my HTC One S using XDA Premium 4 mobile app
lost sd card 48mb
Hi I have big problem with my HTC one s I decided to install maximus hd but I need super cid and s-off facepalm metod everything I do original cid cange to 1111111... Get s-off acses and and install Rom then firmware and when Rom but Rom loads very slowly and sometimes
Black screen and not won't load Rom. And I decided to back s-on and back to original CID HTC_111 and install tricdroid beta 10.0 and then my sdcard 48mb. I try everything flash stock recovery delete all data and wipe but still 48mb try changing a few recovery cmrecovery all types and Twrp recovery but work one prefect Twrp 2.6.1.0 this recovery show me 12gb but I installed Rom on pc 48 I try again flash firmware from maximus hd but failed bicose I change my cid and back to s-on then. I try to go to s-off and change my cid to 11111111.
Noting happen my cid still htc_111 I can't do s-off my hboot is 2.16.0000 I read this forums I find many solutions but no-one don't help my. Try install three roms trickdroid magiobeta and source v14 still 48 I just want get my sd card please somebody. I try many thing relock boot loader try with ruu but still 48
help
dcvc said:
Hi I have big problem with my HTC one s I decided to install maximus hd but I need super cid and s-off facepalm metod everything I do original cid cange to 1111111... Get s-off acses and and install Rom then firmware and when Rom but Rom loads very slowly and sometimes
Black screen and not won't load Rom. And I decided to back s-on and back to original CID HTC_111 and install tricdroid beta 10.0 and then my sdcard 48mb. I try everything flash stock recovery delete all data and wipe but still 48mb try changing a few recovery cmrecovery all types and Twrp recovery but work one prefect Twrp 2.6.1.0 this recovery show me 12gb but I installed Rom on pc 48 I try again flash firmware from maximus hd but failed bicose I change my cid and back to s-on then. I try to go to s-off and change my cid to 11111111.
Noting happen my cid still htc_111 I can't do s-off my hboot is 2.16.0000 I read this forums I find many solutions but no-one don't help my. Try install three roms trickdroid magiobeta and source v14 still 48 I just want get my sd card please somebody. I try many thing relock boot loader try with ruu but still 48
Click to expand...
Click to collapse
Someone may be help me with this trouble :crying::crying::crying::crying::crying::crying::crying::crying::crying:
:crying::crying::crying::crying::crying::crying: Thanks for the help :crying::crying::crying::crying::crying:
same here what should we do i have managed to install magiorom but windows shows only 48mb all i want is to get back to stock but i messed up my cid i am on roger001 but i cannot find a correct rom as i have mi mid pj4010000 please help me get back to stock
I tried to install the Maximus ROM from the dev thread, everything was fine until I had to flash the firmware and the recovery. After that, the phone restarted but was stuck at the loading screen, hence I could not mount the sdcard and transfer the ROM into it.
After that, I could not mound the sd card from recovery. I've tried numerous stuff, notably, flashing the stock recovery, clear storage, factory reset and then reinstalled a custom recovery and I still get a problem. Either I get a 0mb sd card in recovery or a 48mb but in both cases, there's errors while mounting them.
I'm not sure exactly how I could fix this problem now, I have read that the easiest is to flash an RUU but I have never did that and I'm not sure if my current setup is compatible with my RUU (which is Rogers).
Since I'm superCID, can I flash any RUU? If so, which one should I flash?
With supercid you can't flash OTA ZIP, you get bricked device.
This thread might help you with RUU's:
http://forum.xda-developers.com/showthread.php?t=2179513
GabeyC said:
I tried to install the Maximus ROM from the dev thread, everything was fine until I had to flash the firmware and the recovery. After that, the phone restarted but was stuck at the loading screen, hence I could not mount the sdcard and transfer the ROM into it.
After that, I could not mound the sd card from recovery. I've tried numerous stuff, notably, flashing the stock recovery, clear storage, factory reset and then reinstalled a custom recovery and I still get a problem. Either I get a 0mb sd card in recovery or a 48mb but in both cases, there's errors while mounting them.
I'm not sure exactly how I could fix this problem now, I have read that the easiest is to flash an RUU but I have never did that and I'm not sure if my current setup is compatible with my RUU (which is Rogers).
Since I'm superCID, can I flash any RUU? If so, which one should I flash?
Click to expand...
Click to collapse
Are you soff?
Sent from my HTC One S
tominozh said:
Are you soff?
Sent from my HTC One S
Click to expand...
Click to collapse
I ended up working it out, it was a partition problem.
Also, no where on the thread of Maximus does it state that you can't mount in recovery and have to use sideload to make it work. Kind of confusing IMO as my device was not mounting anyway after the boot.
Thanks guys
GabeyC said:
I ended up working it out, it was a partition problem.
Also, no where on the thread of Maximus does it state that you can't mount in recovery and have to use sideload to make it work. Kind of confusing IMO as my device was not mounting anyway after the boot.
Thanks guys
Click to expand...
Click to collapse
How did you work it out? I have the same problem, im attempting to install and older ruu.
Just follow the instructions, instal all stuf from the first post and it will work fine
Sent from my HTC One using xda app-developers app
I have a weird issue occurring, and am apparently not alone - but what worked for others has not worked for me.
I decided to try out the new CandyKat ROM and wanted to "clean" the phone first (it's been awhile since the last uncluttering). I ran the AT&T Stock 3.18 RUU and then decided to upgrade to the latest TWRP 2.7.0.0 as well. However, after flashing the 2.7.0.0 recovery, I found that I was unable to mount the SD card to copy over the new ROM and Gapps. I had already done a full wipe, so I re-ran the stock RUU and tried again just with a factory reset - same results. I searched the forums for a while and found another thread in Q&A regarding the same issue, but going back to TWRP 2.6.3.x solved the problem for the other user. I flashed the unofficial TWRP 2.6.3.0 w/ SELinux (which is what I had prior to updating to 2.7.0.0), but still had the same issue. The weird thing is that I can mount USB storage from within the ROM and it works just fine. But, from within the recovery, it will say the USB mount successful, but Windows will not recognize the device and bring up the sd card storage. The phone is recognized in Device Manager, but I have no options to explore the SD card.
I've tried several things, all to no avail:
- uninstalled HTC Sync, then downloaded and installed latest version from HTC's website (thinking it might be a driver issue)
- tried to mount, no luck
- updated hboot to 2.18
- tried to mount, no luck
- downgraded hboot from 2.18 to 2.15
- tried to mount, no luck
- uninstalled phone from Windows Device Manager, then unplugged and plugged phone back in (Windows will recognize the Android phone in Device Manager, but will not access the internal storage)
- tried to mount, no luck
Everything was working correctly until I updated to TWRP 2.7.0.0 earlier today. All ADB and fastboot functionality still works fine. I find it very odd that I can mount USB storage all day long while the ROM is running, but not from recovery. I am at a loss on what else to try and am down to two options: (1) using fastboot to erase the current recovery before flashing a new one, or (2) letting Windows reformat my internal storage.
Thoughts? Suggestions? I am out of ideas other than the two above...
Mark
HTC One X (AT&T)
hboot 2.15
S-OFF and Unlocked
SlimKat Unofficial Beta 2.3
To be honest I have never seen this issue before.. so we will check every detail of your flash.
Did you check md5 of the recovery's prior to flashing?
Did you do a fastboot erase cache after flashing the custom recovery?
While you answer these questions, I will see if I can recreate the issue myself. I don't run windows though so if something to do with the OS is the problem, I surely won't be able to recreate it.
No, I did not check the MD5 of 2.7.0.0. The other two recoveries I have tried are from prior downloads stored on my computer that have worked fine prior to the flash today.
Yes, I did do a fastboot erase cache.
I appreciate the help and inquiries...
-Mark
mawoods75 said:
No, I did not check the MD5 of 2.7.0.0. The other two recoveries I have tried are from prior downloads stored on my computer that have worked fine prior to the flash today.
Yes, I did do a fastboot erase cache.
I appreciate the help and inquiries...
-Mark
Click to expand...
Click to collapse
There's another thread already discussing the problem you're facing, if you search our forum you'll find it along with the solution that's been posted.
Sent from my Evita
timmaaa said:
There's another thread already discussing the problem you're facing, if you search our forum you'll find it along with the solution that's been posted.
Sent from my Evita
Click to expand...
Click to collapse
damnit, I just flashed and tested it for nothing lol Was working fine for me though.
timmaaa said:
There's another thread already discussing the problem you're facing, if you search our forum you'll find it along with the solution that's been posted.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, but searching was the first thing I did. If you are referring to this thread, or this one, those are what led me to try two of the things I tried (reverting back to an older recovery, which was a no-brainer, and trying to uninstall and reinstall through Windows Device Manager). Unfortunately, none of the things mentioned in those threads worked for me.
I was finally able to resolve the issue, though, just a little while ago. I re-ran the 3.18 stock RUU, then let Windows format my internal storage. After which, I ran the stock RUU again, pushed recovery switcher to my phone, and then flashed the modified 2.6.3.0 from within Recovery Switcher. It took about 30 seconds, but Windows finally recognized the phone when I mounted USB storage from recovery.
I was seeing a couple of weird things throughout it all, like getting [remote not allowed] when trying to "fastboot erase recovery", even though other fastboot commands worked fine, including the devices command. Also, would periodically get a "unable to mount \cache" when formatting within recovery. Oh well, after the Windows re-format of the SD, everything seems to be working fine. I appreciate everyone's assistance and suggestions.
-Mark