Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
srk10 said:
Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
Click to expand...
Click to collapse
not sure but it can be possible that some partitions are damaged.
run the latest ruu to restore all the partitions.
twrp 2.5.0.0 have some problems with custom roms,
try twrp 2.3.3.0, it seems that this version has mostly no problems with flashing roms.
do not forget to flash the boot.img after flashing the rom or you will get a bootloop.
before flashing a rom wipe 3x system 3x data 3x cache to be sure that your phone is clean of old system stuff.
here is the link for twrp 2.3.3.0
https://www.dropbox.com/s/pvspwkekl42zkqa/openrecovery-twrp-2.3.3.0-ville.img
Thanks so much for the reply. I downgrade to twrp 2.3 and managed to use the windows utility to reformat my sd card. Wasn't sure that wasn't going to shoot me in the foot, but it worked and I am back in business with a phone that boots.
Related
I hate to post this but after 3 days of trying to get this damned phone serviceable I am seeking higher powers.
I have viewed just about every thread I can, and everytime i think I'm getting close only to be disappointed.
I was attempting to root a Rogers HTC One X for a friend. Ive rooted 3 other devices prior to this one without issue and constantly custom rom my own device (HTC Raider).
As of now, I CAN: Boot to Hboot (1.11.000), Flash Custom Recovery (Have tried TWRP and CWM, can enter successfully cant do much else), flash things via fastboot.
I CANNOT boot to OS. Its apparently gone. so as such, i have no access to the SD-ext. I CAN mount USB in TWRP but while it shows up in windows as a storage device, I CANT see it on the phone, so i cant flash it. I CANNOT mount in CWM.
I have attempted to RUU via fastboot. I have gotten errors for signature, size and model. Even the stock, non-root one (1.94) stated that the size is incorrect. Im also seeing alot of Errors regarding android-info.txt.
I really desperately need to get this running. Which ever rom. i dont care. If i can get stock, fine, if not Custom rom/kernel.
My biggest issue is not having access to the sd-ext and this phone, for some stupid reason, does not have a microSD slot, which would have made this whole issue alot easier.
I dont know if im missing a file or a step. Im really not sure where to go next.
If you have files that will work and can tell me how to do it, I will forever be in your debt.
It seems to me that i SHOULD be able to run fastboot update xxx.zip and just have it fix it but thats when im getting the android-info.txt errors.
If i could manually flash the 3 files through fastboot (system and boot more than recovery), i would think it would work but nooooooo.
Is there any way any of you know how to get me to atleast being able to see my sd-ext on both windows and TWRP so i can flash it that way? ANYTHING?
So, Got it up and running with Team Nocturnals Rom.
What I had to do was wipe SD and caches in TWRP. Flashed CWM from fastboot. Wiped SD and cache AGAIN. Flashed back to TWRP. Wiped SD and Cache. Rebooted to fastboot. Flashed the boot.IMG. Rebooted to recovery. Mounted USB. Windows detected it. Formatted to fat32. Copied the .zip to SD and installed. Problem solved.
Stock 2.20 Rom that's around didn't work, deodexed rooted stock didnts, nor did Android Revolution HD.
I still thank all of you, because even though I got this working myself, it was bits and pieces of every other thread that got me to that point. Thank you all.
Sent from my HTC Velocity 4G X710s using xda app-developers app
Kesler84 said:
So, Got it up and running with Team Nocturnals Rom.
What I had to do was wipe SD and caches in TWRP. Flashed CWM from fastboot. Wiped SD and cache AGAIN. Flashed back to TWRP. Wiped SD and Cache. Rebooted to fastboot. Flashed the boot.IMG. Rebooted to recovery. Mounted USB. Windows detected it. Formatted to fat32. Copied the .zip to SD and installed. Problem solved.
Stock 2.20 Rom that's around didn't work, deodexed rooted stock didnts, nor did Android Revolution HD.
I still thank all of you, because even though I got this working myself, it was bits and pieces of every other thread that got me to that point. Thank you all.
Sent from my HTC Velocity 4G X710s using xda app-developers app
Click to expand...
Click to collapse
Ummmm android revolution is for the international one x.... Maybe that's how u f'd it up in the first place? Idk just be careful the threads are kinda similar ...
No, I didn't even touch Revolution until it was already not working. I was originally just rooting the stock. It wasn't until it softbricked that I attempted any customs.
Sent from my HTC Velocity 4G X710s using xda app-developers app
was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.
So no matter whatever recovery I use (CWM, CWM Touch, TWRP), I always get errors saying "E: Can't open....". I just got this tablet off ebay after wanting it for a long time and I've been looking for the past 5 hours trying all these methods I see online, but I haven't seen this problem before. All I want is JUST root on the STOCK ROM so I can remove what I don't use with Titanium Backup. That's it! But I don't know why this has to be so complicated compared to devices I've owned in the past. SO if ANYONE can give me an idea of what to do, it would be greatly appreciated.
Wallex said:
So no matter whatever recovery I use (CWM, CWM Touch, TWRP), I always get errors saying "E: Can't open....". I just got this tablet off ebay after wanting it for a long time and I've been looking for the past 5 hours trying all these methods I see online, but I haven't seen this problem before. All I want is JUST root on the STOCK ROM so I can remove what I don't use with Titanium Backup. That's it! But I don't know why this has to be so complicated compared to devices I've owned in the past. SO if ANYONE can give me an idea of what to do, it would be greatly appreciated.
Click to expand...
Click to collapse
What bootloader v. are you on & what recovery v. did you flash?
Ti2 said:
What bootloader v. are you on & what recovery v. did you flash?
Click to expand...
Click to collapse
So when I boot into bootloader, it says:
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00e> released by "US_epad-10.6.1.0-20130225" A03"
As for recovery, I've tried all sorts of them to no avail. IF I get a choice in the end of all this, I prefer CWM but if not that's no big deal. Like I said, all I want is the stock ROM with root. That's it. Luckily I haven't bricked it yet... but I've tried about three:
CWM Touch
TWRP 2.5
TWRP 2.3-something?
Currently have CWM NON TOUCH-based v6.0.2.3
If you could provide me with direct links so I don't get the wrong versions that'd be great.
*edit: Also worth noting, with TWRP 2.5, I was able to install zip's AFTER going into MOUNT and mounting /system (BUT NOTHING ELSE WOULD MOUNT!) and then it would read the zip off /system, which APPEARED to be my SD's contents. BUT even though it said "Successful" it actually did nothing because it wouldn't mount.
Wallex said:
So when I boot into bootloader, it says:
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00e> released by "US_epad-10.6.1.0-20130225" A03"
As for recovery, I've tried all sorts of them to no avail. IF I get a choice in the end of all this, I prefer CWM but if not that's no big deal. Like I said, all I want is the stock ROM with root. That's it. Luckily I haven't bricked it yet... but I've tried about three:
CWM Touch
TWRP 2.5
TWRP 2.3-something?
Currently have CWM NON TOUCH-based v6.0.2.3
If you could provide me with direct links so I don't get the wrong versions that'd be great.
*edit: Also worth noting, with TWRP 2.5, I was able to install zip's AFTER going into MOUNT and mounting /system (BUT NOTHING ELSE WOULD MOUNT!) and then it would read the zip off /system, which APPEARED to be my SD's contents. BUT even though it said "Successful" it actually did nothing because it wouldn't mount.
Click to expand...
Click to collapse
did you bother searching or reading before you went to unlock it? i see nothing you posted about the modded recovery for the tf300t . that you need with new jb. sounds to me like your screwed by flashing the wrong recovery with the new boot loader. so unless im wrong i think you got your self a paper weight.
kaos420 said:
did you bother searching or reading before you went to unlock it? i see nothing you posted about the modded recovery for the tf300t . that you need with new jb. sounds to me like your screwed by flashing the wrong recovery with the new boot loader. so unless im wrong i think you got your self a paper weight.
Click to expand...
Click to collapse
Too bad you're wrong.
Finally got it working by flashing this:
http://forum.xda-developers.com/showthread.php?t=2187982
TWRP 2.4.4.0
Wallex said:
Too bad you're wrong.
Finally got it working by flashing this:
http://forum.xda-developers.com/showthread.php?t=2187982
TWRP 2.4.4.0
Click to expand...
Click to collapse
Too BAD he's wrong??
LUCKILY he's wrong!! :good:
I have an AT&T HTC One X that's rooted. I wanted to put Cyanogenmod 10 on it, but I accidently wiped the System files instead of the cache. Now it can't boot up regularly, I've tried using Rom Update Utility but it doesn't seem to work. Factory Reset doesn't seem to work either. I didn't expect this to happen because my friend just flashed his a couple of days ago. I've tried making a backup and restoring but no matter what I can't get the phone to start up normally. Unless I put it in TWRP (Team Win Recovery Project) or the HBoot/Bootloader I really can't use it for anything. Any suggestions? I would greatly appreciate it. Also when bootloader opens it says "Tampered" and under it "Unlocked" because I did root it. It didn't have "Tampered" when I first rooted it.
I don't care about Cyanogenmod 10 anymore I just want to have it working again.
Everything else about the phone is in perfect condition but what I just said is the only problem.
Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.
iElvis said:
Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.
Click to expand...
Click to collapse
Well, I've already flashed it to a few things and so far it hasn't changed anything. Got any links?
Did you fastboot flash boot boot.IMG ? Don't know what hboot you are on, but could be it.
Sent from my Carbon-ize Evita using xda-developers app
I have the Nvidia Shield 16 Gig Wifi tablet and Ive only had it for about 2 months. I wanted to unroot and completely go back to out of the box settings. I flashed the stock recovery, and boot. When i flash system.img it says insufficient space. Im really freaking out over this. I now have CWM running as recovery, but im stuck in a bootloop/softbrick. Ive had this with other tablets before but it was fixable, Im stumped with this one. I really need help here. Please and thank you for help, I need it ASAP.
ProSniper54 said:
I have the Nvidia Shield 16 Gig Wifi tablet and Ive only had it for about 2 months. I wanted to unroot and completely go back to out of the box settings. I flashed the stock recovery, and boot. When i flash system.img it says insufficient space. Im really freaking out over this. I now have CWM running as recovery, but im stuck in a bootloop/softbrick. Ive had this with other tablets before but it was fixable, Im stumped with this one. I really need help here. Please and thank you for help, I need it ASAP.
Click to expand...
Click to collapse
So, basically you left your shield tablet without a rom installed? If you have CWM recovery, you could flash a Full OTA found here http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
It happened to me to. So I downloaded a Philz built in Jan (I googled it)**** and I flashed the full 2.1 ota.
You could flash the TWRP 2.8.5.0 found here:http://forum.xda-developers.com/showpost.php?p=58864006&postcount=90 and then flash the full ota.
Then, Im thinking, you could flash stock recovery. I'd recommend flashing TWRP though, I had a problem with CWM and I could not flash full 2.1 OTA with it.
PS: Did you try wiping system from CWM and then flashing system with fastboot?
****EDIT: I found the Philz I used: https://goo.im/devs/playground/shieldtablet/Philz_Touch-01-02-2015_14.18-TN8-WiFi.zip
but Ive moved forward to TWRP since I couldn't make nandroid backups with it.
NaminatoR1254jaime.sier said:
So, basically you left your shield tablet without a rom installed? If you have CWM recovery, you could flash a Full OTA found here http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
It happened to me to. So I downloaded a Philz built in Jan (I googled it)**** and I flashed the full 2.1 ota.
You could flash the TWRP 2.8.5.0 found here:http://forum.xda-developers.com/showpost.php?p=58864006&postcount=90 and then flash the full ota.
Then, Im thinking, you could flash stock recovery. I'd recommend flashing TWRP though, I had a problem with CWM and I could not flash full 2.1 OTA with it.
PS: Did you try wiping system from CWM and then flashing system with fastboot?
****EDIT: I found the Philz I used: https://goo.im/devs/playground/shieldtablet/Philz_Touch-01-02-2015_14.18-TN8-WiFi.zip
but Ive moved forward to TWRP since I couldn't make nandroid backups with it.
Click to expand...
Click to collapse
Okay I have to thank you a ton for getting my tablet working again. Only problem now, I cant system update anymore, I get an android guy with a red warning sign in him. Any suggestions?
ProSniper54 said:
Okay I have to thank you a ton for getting my tablet working again. Only problem now, I cant system update anymore, I get an android guy with a red warning sign in him. Any suggestions?
Click to expand...
Click to collapse
Probably because you have custom recovery still or you are rooted.
The android red guy happens bc you are rooted (it'll happen even if you have stock recovery).
To system update, you have to be without custom recovery AND unrooted.
EDIT: Im theoretically speaking. I am rooted, therefore, I dont update via OTA.
i tried to recover to factory but i am stuck at system.img which dun seem to be copying into my tablet i manage to flash twrp in and wat else can i do to make it working again?
thanks