So I flashed a new recovery, TWRP 2.6.0. When I try flashing a new ROM now, I'm getting the following error "Could not create file for updater extract in /tmp/updater." And for some reason, the ROM I had installed previously, TrickDroid 10, is no longer there, so there is no longer a bootable OS on my phone. I tried reinstalling the recovery I had before, TWRP 2.3.3, but I can't get my phone to connect to adb or fastboot. I installed the drivers, but neither command is recognizing my phone, even when in the bootloader.
I would really appreciate some help as I am completely stuck right now. No OS, not able to flash any ROM.
EDIT: I am not using S-OFF, and my hboot is 1.09.0000. I understand I have an outdated hboot, and newer ROMS such as the latest CM nightlies won't flash, but not even older roms, like CM 10.0 are flashing.
Also, to clarify my fastboot issues, Whenever I am in fastboot mode in recovery, it will only change to "FASTBOOT USB" if I scroll up or down - this happens regardless of if it is plugged in to the USB port or not. This used to work on my old comp, so I don't know why it isn't right now.
i think im having the same problem, can you access your sd card through your pc ?
If the "Fastboot USB" come red and you do not have plug in, then the bootloader could be mess up or you charge port "stuck". Does you phone charge, when plug in?. I would try to run RUU and see what happen.
Best bet would probably be to factory reset the whole phone. I had this happen once and I used a recovery I found on here, that puts it back to the stock recovery and let's you reset. From there you can do everything again
Related
I have a 2.2.0 hboot 1.14 unlocked, tampered CID1111111 One XL from AT&T. I was trying to try my first cooked ROM Friday night and I think I may have totally screwed up. I did a "factory reset" from the bootloader instead of from TWRP 2.3.1. My phone gets to "initiating Swagger" and gets stuck. I tried to re-ROM but TWRP can't find the directory. Everything appears to have been over-written. I tried to use the 2.2.0 RUU to start over, but now my computer doesn't recognize the device in HTCsync. I tried to re-image the hboot with a stock 2.2.0 image to see if that would at least start up so that I could use the RUU. It doesn't appear to have helped. HTCsync still doesn't recognize my phone although it now alerts me that the device "MyHTC" is now on the computer. I tried to mount the USB with TWRP and the computer tells me that the drive is "unformatted" and asks to "format?" So far I've cancelled out of that.
Is this device borked beyond repair?
Update: The solution was very sinple. Reformatted SD in FAT32. Re-downloaded AOKP and Gapps. Extracted the boot.img file from AOKP. Copied zipped AOKP and Gaaps to newly formatted SD. Flashed the boot.img file in fastboot using the Team Nocturnal tool. Everything booted normally and runs great!
Many thanks to area51avenger and crappyvate!! You guys are what makes this community rock! Keep up the good work.
I believe I had this problem yesterday when trying to install AOKP, I didn't flash the boot.img before I ran the .zip in TWRP. I was stuck in the boot screen and then wiped all my data. Couldn't mount SD from TWRP, had to install HTCSync on my computer, relock the bootloader, and run the RUU of what I was previously on. I tried to go to 1.85, but it didn't allow me because I was previously on 2.20, getting the RUU for 2.20 and running it gave me back stock Sense, and I re-unlocked my bootloader and was able to successfully install AOKP after flashing the boot.img.
Don't factory reset from bootloader.
Format card to fat32, mount usb storage in twrp, copy aokp over.
Install as per the 1000 threads here
sdimock said:
I have a 2.2.0 hboot 1.14 unlocked, tampered CID1111111 One XL from AT&T. I was trying to try my first cooked ROM Friday night and I think I may have totally screwed up. I did a "factory reset" from the bootloader instead of from TWRP 2.3.1. My phone gets to "initiating Swagger" and gets stuck. I tried to re-ROM but TWRP can't find the directory. Everything appears to have been over-written. I tried to use the 2.2.0 RUU to start over, but now my computer doesn't recognize the device in HTCsync. I tried to re-image the hboot with a stock 2.2.0 image to see if that would at least start up so that I could use the RUU. It doesn't appear to have helped. HTCsync still doesn't recognize my phone although it now alerts me that the device "MyHTC" is now on the computer. I tried to mount the USB with TWRP and the computer tells me that the drive is "unformatted" and asks to "format?" So far I've cancelled out of that.
Is this device borked beyond repair?
Click to expand...
Click to collapse
So you can actually reboot in recovery ? reformat your sd card (fat32). Try to flash the boot.img of the rom you're on, reflash the romzip and see where that takes you. Note: there seems to be some issue with htc sync while you flash so make sure to disable htc sync.
After trying to install CM10 Via TWRP my phone hung on the CM10 splash page.
I have tried to reinstall CM10 and I keep having the same problem.
I'm able to access TWRP but for some odd reason I can't mount my sd card properly. I'm not able to click "Mount sd card" on the "mount" page in TWRP. That being said I can't backup my phone from a previous backup.. Any help would be greatly appreciated.
Now my phone won't even turn on.. HELP
undergrad said:
Now my phone won't even turn on.. HELP
Click to expand...
Click to collapse
Have you tried holding down the power and volume down button for longer then 10 seconds or longer? this should force restart your phone, get into TWRP and try an other Rom for now, also did you try an international rom? international roms will not work.
UPDATE: I'm guessing your also can't recover your last back up because your on HBOOT 1.14 S-ON? 1.14 will not recover boot.img's
If you manage to get it to mount to your computer (Check your drivers are installed also, EG htc sync usb drivers) then look for a "one click boot img flash" unless you know how to flash them using fastboot commands, whenever you are to flash a room, extract the boot.img from the zip file, flash that in fastboot, THEN go to recovery and flash a rom. same goes for backups. S-off is a hassle.
My computer recognizes that the phone is being plugged into the computer but it can't install the proper drivers.
Sadly I can't get my phone to go into recovery either.
undergrad said:
My computer recognizes that the phone is being plugged into the computer but it can't install the proper drivers.
Sadly I can't get my phone to go into recovery either.
Click to expand...
Click to collapse
when in twrp recovery.
1. delete cache, dav. cache, and system restore.
2. reinstall the gapp files and the CM10 zip file.
3. reboot
The issue is that I can't get into TWRP
what did you do to it? phones don't just die and cm10 didn't kill it. are you sure you flashed cm10 for the evita?
also try flashing this version of twrp openrecovery-twrp-2.3.3.1-evita.img
also run "fastboot erase cache" after flashing then try going into recovery and wiping cache,dalvik, and external
I'm trying to fix it by using the HTC Android Phone ROM Update utility, but I keep getting the follow error.. "ERROR [140]: BOOTLOADER VERSION ERROR...
I'm not currently able to boot into TWRP to install a new ROM.
undergrad said:
I'm trying to fix it by using the HTC Android Phone ROM Update utility, but I keep getting the follow error.. "ERROR [140]: BOOTLOADER VERSION ERROR...
I'm not currently able to boot into TWRP to install a new ROM.
Click to expand...
Click to collapse
well if you've unlocked your bootloader you cant upgrade with anything to do with htc and that's sure to mess with it. you're on your own sources of updates, no OTA nothing. You need to install htc sync and adb drivers for your phone if that still doesnt detect then its a usb brick and I'm of no hope but others may be
Lemagex said:
well if you've unlocked your bootloader you cant upgrade with anything to do with htc and that's sure to mess with it. you're on your own sources of updates, no OTA nothing. You need to install htc sync and adb drivers for your phone if that still doesnt detect then its a usb brick and I'm of no hope but others may be
Click to expand...
Click to collapse
I managed to relock my bootloader, but installing the stock RUU is still another story..
I can only get my computer to recognize that the phone is connected to my computer if I'm in Fastboot mode.
If you can't mount from recovery the sd got corrupted happened to me they have a fix if you do a few searchs. If you locked the bootoader and the computer only recognizes in fastboot that is good now run a RUU like 1.85
Sent from my HTC One X using xda premium
Hello,
I got this HTC One X from AT&T (->evita) and tried to get CM 10.2.1 running on that.
The steps I made:
Boot into bootloader, go to fastboot, then get the identifier, get unlock token via htcdev and unlocked it with fastboot.
I then flashed CWM 6.0.4.6 for evita via "fastboot flash recovery *filename*". Now I booted into CWM (recovery) and wiped everything instead of first trying to copy the cm.zip onto the sdcard. (I also didnt do this when the stock ROM was still running...)
Now I can access the phone via fastboot in the bootloader but I can not use adb or the USB mount when in CWM. Whenever I plug the phone into my computer (or laptop, doesn't matter. Also tried switching between USB 2 and 3 ports!) Windows keeps making the "unplugged" sound every second.
Reinstalling the latest HTC drivers did not change anything.
Anyone here knows a way how I can stop that or get the zip file on the memory? I also tried flashing the boot.img on boot and tested if I can copy the file then through CWM but that did not work.
Hoping,
NyphoX
Not sure if it'll work but try using TWRP recovery instead:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita
Installed the most recent version.
I get into the recovry and when I plug it into a computer Windows will keep making the "unplugged"-noise.
I can see the sdcard-directory perfectly when I hit install in both, TWRP and CWM but when I want to mount it via USB it will not change anything and I cannot access it on my PC.
adb doesn't list any device either.
Also, TWRP and CWM keep telling me that my phone is not rooted, when I try to power off or restart. Is that normal?
My other HTC One X (non AT&T) just works fine with cwm 5.*.*.*
It's normal for the recovery to inform you that you're not rooted, it'll suggest that you install superuser but there's no point doing that in your case because you have no working OS installed. Did you at any point perform a factory reset from the bootloader? If so, you've corrupted the internal storage (known bug on modified Evitas) and will need to wipe it with TWRP.
Sent from my Evita
Saw that in your Q&A.
I wiped the internal_sd and tested it after but it still did not work. I also tried a factory reset through TWRP but that did not help either.
Both recovery programs keep telling me "E:Unable to mount '/cache'.
Still not working. Q_Q
Update: I got like the oldest laptop I ever owned and installed the most recent HTC drivers there and tried to mount it. It told me in device manager that the "evita" is not recognized. When I let Windows search automatically it installed the drivers and I am now able to access the memory.
I can only assume what the problem was but it seems like the HTC One X (endeavoru) driver and the evita don't like each other...
TL;DR trying to install now. Will edit.
//EDIT: Windows still screws when I plug the phone to the other computer/laptop, so I just have to use the old machine now. Still thanks for your help, timmaaa!
//EDIT: It does work when I booted CM and enable the USB storage at the other two machines.
Quick note: I'm very new to all this so I don't really know entirely what's going on.
Alright, basically I'm trying to install the Paranoid Android ROM and I've run into a bit of an issue. I've unlocked the bootloader and flashed the ClockworkMod Recovery. The problem I've ran into is that when I go into the CWM recovery and attempt to do anything with ADB it comes up with "error: device not found"
What am I doing wrong?
Sidenote: ADB can find my phone if it's booted up normally, it's only when I boot to the CWM custom recovery that it can't find it...
I think you are doing it wrong way buddy..
Boot in to Bootloader mode not in CWM Recovery, then try with fastboot and check again..
I did boot into bootloader, then went to CWM and tried to push the ROM using ADB but it wasn't recognising my phone.
Doesn't matter now anyway. I got around it by literally just drag and dropping the zip files onto my phone's internal memory when it was booted up normally and connected to my PC. Then I rebooted into the bootloader, flashed CWM and installed from ZIP. That method was far easier than messing around with ADB etc.
Hey Guys
[Update] I've managed to get Fastboot to work properly after flashing an ever older version of a MTA-Full-PV file. I have gotten TWRP re-installed & I'm trying to flash the latest stock but it's not writing.
I've seen some people talk about only flashing system/boot/vendor, and others say you can flash the full update.zip(which is not working for me). I've also tried to unpack the update file, remove the reovery.img & repackage but same issue.
Can anyone give me a guide to flashing stock via TWRP? Flashing just the system/boot/vendor failed.
I was attempting to go back to stock(like many other people here recently) and I didn't know I could use TWRP to update, so I flashed 360 via dload method.
Something didn't work properly as it flashed, and I can boot, but I'm missing something things in the rom, like their built-in updater. I've attempted to load a newer version via dload without success, 360 is the only version that seems to want to flash. If I try to re-flash it, or the companion zip, nothing happens. It doesn't wipe the existing rom or anything. I've tried doing a factory reset.
I still have my unlock code & I'd like to re-unlock the bootloader & install TWRP, however my device will not connect via USB. It will enter charge mode, but I cannot get it to be recognized by the PC.
Dev settings says it's in MTP mode. USB debug = enabled. I'd also tried enabled ADB during charge, but the PC still won't recognize it. I've had no issues with the PC/device combo previously.
I'm trying to find a better version to flash, but nothing seems to work. God knows when 8.0 will be released for US, so I would like to figure out what's going with USB. Once USB is working, I can unlock bootloader, flash TWRP, then flash a newer update.zip ?
It's very odd that no PC will recognize the device in MTP mode. I've ever tried rebooting into Fastboot mode(volume down at boot) but still nothing. I've tried multiple cables/pcs & Windows/Linux.
Any ideas why I ADB/MTP will not function? I don't believe it's a driver issue on the Windows 10 PC as it's not listed in device manager when I do a scan, even as an unknown device. Seems to enter charge mode just fine while connected to a PC, so I assume it's a software issue somewhere.