Database Info

[Q] CWM wipe s-on Brick

Long time listener, first time caller.
I have the latest hboot 1.45.0013, S-On, Unlocked with HTC Dev Tool.
I used the Hasoon2000 tool to install SU, CWM, and a recovery image. I then used the instructions in the thread (http://forum.xda-developers.com/showthread.php?t=1508556) to install ICS and obtain root installing pyr-o-ice sense 1.1.1 (http://forum.xda-developers.com/showthread.php?t=1469615) Everything worked, created nandroid backup and installed titanium.
Some buttons didn't work, so I looked for updates and found Virtuous ROMs. So, I used CWM to clear dalvic, flashed boot image of the Virtuous Inquisition then used CWM to install zip. Bootloop. ROM just hangs on black screen with white V for 15 to 20 minutes.
MT4GS thread stated that Primadonna and Inquisition were comparable, so I followed the same proceedure, flashed Primadonna boot image then installed ROM through CWM. This time there was tmobile splash screen, but the same system hang.
At this point I tried to restore a recovery, but CWM could not find one. Used Astro to delete all boot images from SD root, assuming this may be the problem, and flashed a Virtuous ROM again. Same problem.
Based on this thread, I thought it might be the kernal, and tried flashing the pyr-o-ice boot image that worked initially. (http://forum.xda-developers.com/archive/index.php/t-1628171.html). No dice. CWM could not install the ROM (error 1)
So, at this point, I used CWM factory reset and wipe all data. And of course that made things worse, because the SD card with recoveries was wiped. I used adb to push the recoveries from Hansoon's toolkit, but stock recovery was not available (red triangle screen hang) and cwm could not mount the SD card.
So, at this point I used CWM to format SD card (blank anyway), and at this point adb failed to recognize the decive and I could no longer fastboot into recovery or hboot through adb. (volume down + power stopped working with pyr-o-ice install)
if i remove the battery and hold power + volume while using an adb reboot hboot command i can get into hboot about every 10th attempt. adb doesn't recognize the device ("waiting on device", or adb devices yields a blank list); however the phone in hboot will transfer to usb fastboot when connected with a cable.
i looked at pushing a zip file through adb to the sd root, but that was ineffective (adb does have write access to the sd root, maybe because i am s-on?). i purchased a second sd card, and copied the recovery images from hansoons toolkit and rebooted into recovery. still went to tmobile splash, followed by V-screen bootloop.
i looked at placing a stock ruu on the sd and naming the file PG59IMG.zip, but because i'm S-on i can't flash radios, so that's out.
So, here we are. Iffy access to fastboot, 2 sd cards, a lot of determination, and a persistent bootloop.
Can someone, PLEASE help me?
Thanks!

AFAIK, you cannot flash the boot.img with CWM if you are S-ON, you *MUST* use Fastboot to flash that. So, before you messed it all up, if you had just extracted the boot.img from the ROM and flashed it using Fastboot, it likely would have worked just beautifully.
Try booting into recovery and doing a regular flash of the ROM, THEN a fastboot flash of the boot.img.

SOLVED!!
Thanks to the folks heading up the HTC Unbricking Project (http://forum.xda-developers.com/showthread.php?t=1627881) ESPECIALLY Dexter93!! who patiently unraveled this for me, and Blue6IX for the Restore to Stock instructions in the Developers Reference Guide (http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24) I'm back to stock, and ready to try it all again!
Can someone send me an apk that automatically clicks the thanks button for selected developers at regular intervals?
Thanks again!

Solved???
Fuzi0719, thanks for your reply. I may have written this inappropriately, but what coded in the command prompt was "fastboot flash boot boot.img".
The ROM zip file was placed on the SD card, and I rebooted into recovery, and used CWM to install zip from SD. I'm new to this so I may have used the wrong term for installing the zip through CWM, the boot image file was always handled through the above command.
I'm back to "stock" at this point, but when I boot into the bootloader, the phone looks for PG59DIAG.zip and PG59DIAG.nbh before PG59IMG.zip.
It then asks if I want to install the update. (This is after I have already installed the "update", and the phone reset itself even with my old wallpaper.) When I got to the home screen there was a white circle in upper left corner of the status bar, with "check content" message. Each time the screen locked (default 30 seconds) unlocking it took me to the mytouch splash screen with the green circle and white background for about 10 seconds before resuming.
Each time I check to see if the phone registers requiring any updates. It doesn't. Two installs of the PG59IMG.zip. "recovery" eliminates the unlock splashscreen, and wiped any customizations. However, the phone will not manually boot into the bootloader; I have to use adb. Hboot reinstalls the PG59IMG.zip as an update every time.
If I accept it reboots within seconds like a fresh doubleshot. If I decline the "update" it reboots to the Tmobile MyTouch 4G Slide text splash screen, then moved to the green circle screen for a few minutes before I get to the homescreen.
Blue6IX was looking for help with these last month (http://forum.xda-developers.com/showthread.php?t=1580077), so maybe they are just extraction files that HTC sends with the OTA update that would prevent my phone from trying to install the "update" every time?
In any case, my question at this point is after coming from such an unstable point with my phone, is this what every relocked bootloader does? Or, is this a problem that means something else is still wrong with the system? Because taking it back to stock has not solved this.
Thanks.

Thanks for clarifying, you wouldn't believe the number of people who fail to follow that one simple step of fastboot flashing the boot.img, so that's why I stated that. So, now you have the phone relocked, and running a stock ROM (the 1.55?), but with CWM 5.0.2.7? Were you wanting to update to the 1.63 ROM? I'm unclear on what it is you want to do. For one thing, if you've already flashed the PG59IMG then I would delete it off the sd card so it doesn't keep trying to load it.

Yup.
It was just that simple.
Mainly I wanted to make sure that my phone was stable before I went back to unlock the bootloader, etc.
Went back to HTC, got a new token (just in case), and I'm creating a nandroid backup right now. Thanks.
I really appreciate it.
Hopefully the next time I get stuck, it's just as simple to fix, but far less embarrassing.

[Help] Installing VenomXL+ on AT&T HTC One X+

Before I get into the gist of my current problem I think it might be relevant to provide some backstory. I decided I wanted to try and root my phone so I could install a new custom ROM. I had done some jailbreaking back when the iPod touches came out, back when jailbreaking was extremely ghetto and unreliable, so I figured I could teach myself this fairly easily. I unlocked bootloader using the htcdev method without an issue, and, following a guide, downloaded something called Rootboot to flash the phone. There was only one step to this portion, so I assumed it would be easy. Running the rootboot started rooting my phone, however after a couple of lines in the command prompt it said something about the adb, failed, and the phone was stuck in a boot loop with no roms on it at all. I stayed up all night with the damn thing attempting to fix it, and at one point, actually got it to load up the stock ROM from the computer using some combination of RUU's and fastboot commands. I have no clue how I did it, all I know is that it was not through adb sideload because the recovery I had at the time wouldn't work with adb sideload for whatever reason. It was the recovery that came with the All-In-One toolkit, for the AT&T / TELUS version. At this point I figured since the phone was working I would just install the VenomROM, and after a few hours of playing around with fastboot and the bootloader trying to get a ROM loaded, I figured I was familiar enough with all of them to load the ROM.
Which is what brings me to my current issue. I KNOW the boot.img is flashed to the device because I used the All-In-One Toolkit to do it, erased the cache, did it again using fastboot commands in the command prompt, erased the cache, and continued to use recovery to install the ROM. I got it to load and install, cleared the darvik cache, data, and cache, but when booting, the phone would get to the lock screen, upon which sliding to unlock, presented me with a white screen that says "htc" on it instead of a launcher. After a couple of seconds of waiting, it says, "setup has quit responding" and gives me the option to close or to wait. Either option results in the phone rebooting wherein I only see a black screen with the notification bar at the top displaying my battery and no internet/network connection. I have gone back and flashed the boot.img again and cleared cache, darvik cache, and data several times and just have no clue what I'm doing wrong to not get this phone to boot with the ROM. I can reflash at any point from my sideload.zip file and the installation process has an option to flash the kernel (boot.img) because it is included in the zip. Any help would be much appreciated. I highly doubt theres anything wrong with the ROM or boot.img, it is probably me just not doing it right.
I am using (or attempting to use) the 1.2.7 version of VenomXL+ on the HTC One X+ along with TWRP 2.5 as the recovery.

I screwed up and now I need help [Can't install any ROM]

Hi there
So about a year ago, some months after getting htc explorer, I rooted it for the sole purpose of installing apks. Yesterday I did a factory reset (I had tottaly forgotten that I should only do it through the recovery) and a ruined my phone
After some digging around I decided that I'd like to try a custom ROM, and I've been trying all day and I can't get it to work. The roms I've tried:
JaggyRom 3.2.1 (lite) : Can Install it just fine, first time boot ok, then after restarting phone it gets stuck at the htc logo (Tried it 3 times)
JaggyRom 4.1: Installed it with no problems too, first boot with sd card in and I get error that some core process has stopped working.
MIUI (latest version): On the first boot it stayed on the "Android" logo forever (at least 30 min) so I gave up.
In all roms I followed the proper instructions (make other ext4 partitions and what not). I think the problem may lie with my recovery. My recovery is "pico cwm-based recovery v5.0.2" and I don't know if it may be outdated. Jaggyjags mentions in his jaggyrom 3.2.1 topic that we should use recovery by yannou90 but I can't install it. When I run the recovery.bat from this topic It gives a "waiting for device" message. I think my pc doesnt recognize when I connect the htc via usb in the fastboot menu because it gives a weird message about some undefined usb device, and when I used to connect through the phone os it was fine.
Anyway, I was hoping that someone could shed some light on me and help me out here.
Best Regards
EDIT:I just noticed that I have the recovery by Yannou90 after all. What am I doing wrong then?

heyjack7 said:
Hi there
So about a year ago, some months after getting htc explorer, I rooted it for the sole purpose of installing apks. Yesterday I did a factory reset (I had tottaly forgotten that I should only do it through the recovery) and a ruined my phone
After some digging around I decided that I'd like to try a custom ROM, and I've been trying all day and I can't get it to work. The roms I've tried:
JaggyRom 3.2.1 (lite) : Can Install it just fine, first time boot ok, then after restarting phone it gets stuck at the htc logo (Tried it 3 times)
JaggyRom 4.1: Installed it with no problems too, first boot with sd card in and I get error that some core process has stopped working.
MIUI (latest version): On the first boot it stayed on the "Android" logo forever (at least 30 min) so I gave up.
In all roms I followed the proper instructions (make other ext4 partitions and what not). I think the problem may lie with my recovery. My recovery is "pico cwm-based recovery v5.0.2" and I don't know if it may be outdated. Jaggyjags mentions in his jaggyrom 3.2.1 topic that we should use recovery by yannou90 but I can't install it. When I run the recovery.bat from this topic It gives a "waiting for device" message. I think my pc doesnt recognize when I connect the htc via usb in the fastboot menu because it gives a weird message about some undefined usb device, and when I used to connect through the phone os it was fine.
Anyway, I was hoping that someone could shed some light on me and help me out here.
Best Regards
EDIT:I just noticed that I have the recovery by Yannou90 after all. What am I doing wrong then?
Click to expand...
Click to collapse
have you wiped cache , data and dalvik before flashing the rom

vijnathin said:
have you wiped cache , data and dalvik before flashing the rom
Click to expand...
Click to collapse
Yes, all 3.

heyjack7 said:
Yes, all 3.
Click to expand...
Click to collapse
try to flash some other rom and , try to use twrp or philz recovery , i too faced the same problem in beginning and what i did is i have changed my recovery , as far as i know the reviews from forum tells that yannou recovery is the best

heyjack7 said:
Hi there
So about a year ago, some months after getting htc explorer, I rooted it for the sole purpose of installing apks. Yesterday I did a factory reset (I had tottaly forgotten that I should only do it through the recovery) and a ruined my phone
After some digging around I decided that I'd like to try a custom ROM, and I've been trying all day and I can't get it to work. The roms I've tried:
JaggyRom 3.2.1 (lite) : Can Install it just fine, first time boot ok, then after restarting phone it gets stuck at the htc logo (Tried it 3 times)
JaggyRom 4.1: Installed it with no problems too, first boot with sd card in and I get error that some core process has stopped working.
MIUI (latest version): On the first boot it stayed on the "Android" logo forever (at least 30 min) so I gave up.
In all roms I followed the proper instructions (make other ext4 partitions and what not). I think the problem may lie with my recovery. My recovery is "pico cwm-based recovery v5.0.2" and I don't know if it may be outdated. Jaggyjags mentions in his jaggyrom 3.2.1 topic that we should use recovery by yannou90 but I can't install it. When I run the recovery.bat from this topic It gives a "waiting for device" message. I think my pc doesnt recognize when I connect the htc via usb in the fastboot menu because it gives a weird message about some undefined usb device, and when I used to connect through the phone os it was fine.
Anyway, I was hoping that someone could shed some light on me and help me out here.
Best Regards
EDIT:I just noticed that I have the recovery by Yannou90 after all. What am I doing wrong then?
Click to expand...
Click to collapse
Try twrp recovery...available in Original android section...
Make ext4 partition as primary...
Before flashing anythng wipe everything except sdcard...
May be you may missed something that you may havent noticed it yet...

Hi,
I think I solved it! At least I manage to install FlyRom and it seems to be running properly. The problem was that in the tutorial It said to creat an ext partition through the recovery, and it said to choose the 4K MB option. I though that it was the Allocation size unit but it was the actual size, but my sd only as 2 GB so you see the problem. I created one with 1GB and now it seems to be running fine.
Thanks all

LOL
heyjack7 said:
Hi there
So about a year ago, some months after getting htc explorer, I rooted it for the sole purpose of installing apks. Yesterday I did a factory reset (I had tottaly forgotten that I should only do it through the recovery) and a ruined my phone
After some digging around I decided that I'd like to try a custom ROM, and I've been trying all day and I can't get it to work. The roms I've tried:
JaggyRom 3.2.1 (lite) : Can Install it just fine, first time boot ok, then after restarting phone it gets stuck at the htc logo (Tried it 3 times)
JaggyRom 4.1: Installed it with no problems too, first boot with sd card in and I get error that some core process has stopped working.
MIUI (latest version): On the first boot it stayed on the "Android" logo forever (at least 30 min) so I gave up.
In all roms I followed the proper instructions (make other ext4 partitions and what not). I think the problem may lie with my recovery. My recovery is "pico cwm-based recovery v5.0.2" and I don't know if it may be outdated. Jaggyjags mentions in his jaggyrom 3.2.1 topic that we should use recovery by yannou90 but I can't install it. When I run the recovery.bat from this topic It gives a "waiting for device" message. I think my pc doesnt recognize when I connect the htc via usb in the fastboot menu because it gives a weird message about some undefined usb device, and when I used to connect through the phone os it was fine.
Anyway, I was hoping that someone could shed some light on me and help me out here.
Best Regards
EDIT:I just noticed that I have the recovery by Yannou90 after all. What am I doing wrong then?
Click to expand...
Click to collapse
lol

To brick or not to brick that is the question

Hi Guys,
I have an AT&T One X that I unlocked and flashed TWRP recovery on. I have been using this for quite some time with a stockish HTC Custom ROM. However I wanted to see what the latest Cyanogenmod was like. So I flashed the latest snapshot after first flashing the specific recovery software linked on the cyanogenmod page. So far so good. Device booted up and was ready for use.
I wanted to install Gapps afterwards so I went to OpenGapps to download the aroma installer. However the Cyanogenmod recovery software doesn't seem to support this. So I wanted to go back to TWRP. Instead of doing the usual flashing in the recovery I decided to use the TWRP Rommanager since it seemed like a quick fix. Ooh how wrong I was.
After installing the recovery through TWRP manager I accepted the request of TWRP manager to reboot to recovery. However my phone greeted me with a black screen afterwards. Up till now I haven't seen anything pop up onscreen anymore and I tried numerous things. The only strand of hope I still have left as that when connecting to my pc I'm still able to see the phone is in fastboot mode.
However when trying to execute a new flash of my recovery partition my phone keeps saying "fastboot error; remote not allowed". I've searched through numerous articles without a solution up till now. Is my phone too far gone to revive?

Doesn't seem like a straightforward fix as no responses are coming in. Maybe an indication if there would be a fix is appreciated as well.

[Completed] HTC One X Trying to install ROM but stuck with problems.

Hi, so recently my HTC One X has been acting up so I decided to install a ROM to make it much faster, so I had to unlock the bootloader. When i've done that I flashed CWM on my device. Then I tried to install a rom that was on the device and it didn't install which leads me to my first problem, the page said I needed to reset everything and use the fastboot command to flash the zip file that worked but when I went to CWM (to install gapps) the device never booted in the ROM just kept going back to CWM. So I googled this and there was multiple things I tired out like adb command etc also it would be easier if this problem was fixed if this button worked (mount USB storage) I press that and it does not work. So then I don't know what to do. I'm stuck here please help me the rom was cm-11-20160815-NIGHTLY-endeavoru.zip.

swarby2 said:
Hi, so recently my HTC One X has been acting up so I decided to install a ROM to make it much faster, so I had to unlock the bootloader. When i've done that I flashed CWM on my device. Then I tried to install a rom that was on the device and it didn't install which leads me to my first problem, the page said I needed to reset everything and use the fastboot command to flash the zip file that worked but when I went to CWM (to install gapps) the device never booted in the ROM just kept going back to CWM. So I googled this and there was multiple things I tired out like adb command etc also it would be easier if this problem was fixed if this button worked (mount USB storage) I press that and it does not work. So then I don't know what to do. I'm stuck here please help me the rom was cm-11-20160815-NIGHTLY-endeavoru.zip.
Click to expand...
Click to collapse
Greetings and welcome to assist. I can see you have already asked your question in the correct forum here
http://forum.xda-developers.com/showthread.php?t=3498222
so I will close this one up
Good luck
Sawdoctor