[Q] Bricked 2.2 during AOKP flash...help! - AT&T, Rogers HTC One X, Telstra One XL

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.

Related

Help i think I bricked my phone

Hey Guys,
I tried pretty much everything and don't know what else to do. My phone just stays stuck on the android screen. I forget that the "SD card" in this phone is actually part of internal storage, I did a factory reset and lost everything.
I tried flashing different boot.img and getting nothing. I'm afraid I need to get a rom onto the sd card but how is that possible if I cant get my phone to boot up.
Any ideas?
Thanks!
volume down button+power button try this combination until u get in the bootloader then select recovery. once in recovery just restore a backup if you have one, you should have one
i dont have a backup and i have nothing on my "sd" to i can install. I have formatted the ROM and thats why it wont boot..
If you can get into Recovery (CWM) in the advanced settings if i remember, there's a "format sd card" to make it work with the installation of a custom ROM
I posted a tutorial for how to do this:
http://forum.xda-developers.com/showthread.php?t=1667929
brwetz said:
I posted a tutorial for how to do this:
http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
thanks for the guide but im getting error mounting /sdcard. and if i follow cannondale0815 solution for that problem when flashing the stock and cwm I cannot access recovery mode.
Clear Storage in fastboot and re-install CWM then try it. That's how I got mine to work
Ok if your bootloader is locked and you have a custom recovery first flash stock recovery then boot into fastboot and run "fastboot oem lock" After that restart your phone and boot back into fastboot. Then run the RUU for your model and cid. easy.
Follow the steps which might work
1, If you knows something about adb, you can just simply push a rom into the sdcard(You don't need to do this if there is already a flashable rom in the sdcard), flash the kernel in fastboot, go to the recovery, wipe and flash a new rom. Then everything(except your data) should be fine
2, If you are not able to use adb push, or you have never flashed a recovery/3rd-party rom/ or you have other issues:
Using the RUU updater might be safe and simple (of course everything except those in the sdcard will lost)
a, relock the hboot using "fastboot oem lock"(or the RUU will refuse to continue)
b, run the RUU updater, wait for ~10min, your phone will be "refreshed" to something like the 1st day you bought it, except the Hboot will say it is "RELOCKED s-on"(this should be LOCKED s-on at first)
c,unlock your phone again(if you have stored the .bin file for unlock, just push it to your phone in the fastboot mode which is enough already, it is not needed to do the whole process in HTCDEV again.)
IMPORTANT: the RUU updater and the phone must be the same area. for example an Europe's RUU can't be applid to an US's One S
This is also the only method to update the Radio software, unless the hboot is S-OFFed
Bure03 said:
Hey Guys,
I tried pretty much everything and don't know what else to do. My phone just stays stuck on the android screen. I forget that the "SD card" in this phone is actually part of internal storage, I did a factory reset and lost everything.
I tried flashing different boot.img and getting nothing. I'm afraid I need to get a rom onto the sd card but how is that possible if I cant get my phone to boot up.
Any ideas?
Thanks!
Click to expand...
Click to collapse

One S bricked beyond repair?

So, a friend came to me and gave me his newly acquired One S and asked whether or not I could get it back up and running..
Apparently, from what I understand, he got the phone, unlocked the bootloader, but then didnt know that he should install a custom recovery image before attempting to flash CM10, so he used the stock recovery to flash the .zip from the SD Card. After rebooting (I have no idea if the flashing was successful) the phone is stuck on the quietly brilliant screen.
So, I took the phone, rebooted into the bootloader and used fastboot to boot up into a clockwork .img. Everything good so far, however, the problem is that its seemingly impossible to mount the SD card. My friend told me he fiddled around and "tried stuff", so I suspect somehow he must have messed with the sd card partition.
Since the SD card partition isnt actually on a physical removable sd card, I am running out of ideas.
Anyone have any bright tips? All I need is to get the Sd card mounted so that I can flash a ROM properly.
Thanks!
Try running an RUU.
-MobileUS HTC One S running Stock Rooted 2.21.
fmedrano1977 said:
Try running an RUU.
-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
Yeah, but I cant get the RUU on the device, since the SD Card partition is broken..
Untouchab1e said:
Yeah, but I cant get the RUU on the device, since the SD Card partition is broken..
Click to expand...
Click to collapse
Ruu is installed from a computer, flash standard recovery and lock the boot loader and then run the ruu.
Sent from my HTC One S using Tapatalk 2
RUU runs life an exe file on a PC, since your friend didn't install a custom recovery, just relock bootloader and run RUU while phone is plugged in to pc in fastboot mode.
T-MobileUS HTC One S running Stock Rooted 2.21.
Had a similar issue that you can't mount SD from clockworkmod, it mounts ok on TWRP, flash that recovery instead.
fmedrano1977 said:
RUU runs life an exe file on a PC, since your friend didn't install a custom recovery, just relock bootloader and run RUU while phone is plugged in to pc in fastboot mode.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
Aha, right!
However, this still doesnt resolve the issue of a broken SD Card partition..
It probably isn't broken. I've never managed to mount SD through CWM. Try flash TWRP recovery and mount through there.
Dude just listen to everyone and download the ruu and run it only way to fix it I think
Sent from my HTC One S using xda premium
There is a sticky in Q&A on how to fix unmountable /sdcard. (Basically: Flash stock recovery through fastboot, then clear storage in bootloader, then flash your favorite custom recovery again.)
It would not surprise me if this is the same thing a RUU does (except for flashing your favorite custom recovery of course). If so, you don't need to fix your sdcard before running the RUU if you decide to go that route..
Beware that the RUU will also update your hboot, which you may not want.
If you don't want to re-lock, RUU, re-submit token, re-unlock, re-root, just manually fix the sdcard mounting issue. Once you can mount your sdcard in recovery, you can just adb push a rom to it, flash it, (wipe cache), boot it. (Depending on your ROM/hboot/recovery, you may have to flash the boot img through fastboot. The best time to do so is before booting into recovery.)
@djsubtronic: There is some misunderstanding about what 'mounting the sdcard' means.
If you can't mount it onto the root file system in recovery, you have a problem and it must be fixed. In this case you can't push/pull to your sdcard or select a zip from it for flashing. If you can't mount it on your computer over USB from recovery, that's not a problem and you don't really need it as you can still adb push/pull.
Try this
http://forum.xda-developers.com/showthread.php?t=1630459
Sent whit HTC ONE S
dave il barbaro said:
Try this
http://forum.xda-developers.com/showthread.php?t=1630459
Sent whit HTC ONE S
Click to expand...
Click to collapse
Thanks for all the feedback guys! Once my mate responds Ill give it a go!
Unfortunately, so far, no luck..
Booting into the bootloader and selecting "Clear Storage" seemingly did little other than boot up into the stock recovery. After going back to the bootloader and selecting factory reset (which also just booted up stock recovery), I made him do a data wipe/factory reset.. which seemingly ran okay, but the problem still persists.. sdcard partition doesnt mount in neither Clockwork nor TWRP, and the boot is stuck on the HTC quietly brilliant screen..
My next idae I guess is to try and install a RUU.. just need to set up a Windows VM as neither of us runs Windows
I had a situation similiar, when i went to flash, i had the recovery twrp, but something happened when i went to flash, and my sdcard got corrupted,
i cant remember if i formatted the sdcard thru windows, but i think i formatted it twrp, and then was up and running,
or in windows7 disk management i had to fix the partition then formatted...
this happened over a month ago took over an hour...
but i really really really dont think ur phone is bricked... i can be fixed...
get the ruu and go over a friends house who has windows.... hope it works...
Thanks, booted up a Win 7 VM and pushed in the RUU, partition table reconstructed and everything is back to normal.. Thats another One S now kicking CM10
Thanks for the advice everyone!

[Q] Stuck in CWM. Can't mount the sd card. Nothing is backed up.

I tried to install drumlock app and my phone restarted and went into the recovery. I can't mount the sd card either to flash the rom again. I dont have anything backed up. I am really lost and need someone's guidance.
I had the same issue one time what I did is I mounted the phone as a USB drive (don't know if it works with CWM, if not just flash TWRP recovery) and formated the SD card (when I mounted it Windows asked to format the SD card; Format in FAT32!). As you can imagine all data from the SD will be lost but your SD card is mounted again and you should be able to boot again. If booting still doesn't work try putting a ROM on the SD via mount as USB drive function and try to flash it. It should work.
worked but another problem happened :[
.TanTien said:
I had the same issue one time what I did is I mounted the phone as a USB drive (don't know if it works with CWM, if not just flash TWRP recovery) and formated the SD card (when I mounted it Windows asked to format the SD card; Format in FAT32!). As you can imagine all data from the SD will be lost but your SD card is mounted again and you should be able to boot again. If booting still doesn't work try putting a ROM on the SD via mount as USB drive function and try to flash it. It should work.
Click to expand...
Click to collapse
Thanks for that advice. Everything worked. I formatted the cd card and it is now seen in TWRP where I installed the viper one s rom. BUT! Now my phone just keeps on restarting - it shows the htc logo with a red banner under it and just restarts and does it all over again. I can get into boorloader mode If i get lucky pressing it before it restarts, yet the bootloader wont let me get into recovery. I am going to try other methods I guess but I am wondering if there is a way just to use RUU and restore it to stock?
vitality1 said:
Thanks for that advice. Everything worked. I formatted the cd card and it is now seen in TWRP where I installed the viper one s rom. BUT! Now my phone just keeps on restarting - it shows the htc logo with a red banner under it and just restarts and does it all over again. I can get into boorloader mode If i get lucky pressing it before it restarts, yet the bootloader wont let me get into recovery. I am going to try other methods I guess but I am wondering if there is a way just to use RUU and restore it to stock?
Click to expand...
Click to collapse
You must've done something to your recovery when you formatted your sdcard. Try flashing TWRP again. You can easily bring your device back to stock by running the RUU. Info can be found around the forum.
Relock bootloader and run a official HTC RUU (warning: itll update hboot).
what worked but now its stuck
farang4u said:
You must've done something to your recovery when you formatted your sdcard. Try flashing TWRP again. You can easily bring your device back to stock by running the RUU. Info can be found around the forum.
Click to expand...
Click to collapse
I tried that method and flashed utb rom and when i restarted it its stuck on the loading screen...so i tried the different viper one s rom and nothing either. After i locked it i tried the RUU but it gives me the error 150 ...Im on the right track I know...its probably something minor that I keep on overlooking.
gives me error 150
alexeius said:
Relock bootloader and run a official HTC RUU (warning: itll update hboot).
Click to expand...
Click to collapse
I also tried this method but it brings up the error 150. Could this be the recovery that is causing it ?
So you can't even get into recovery even if you flash it over fastboot?
Sent from my HTC Sensation

Bricked After trying to install CM10

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

Stuck on CWM when trying to install CM10.2.1

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.

Categories

Resources