Was running Clean Rom 4.1 & decided to try a new rom. Flashed Xi40, after install & upon reboot, phone got stuck in boot screen (was black). Went into recovery & tried to restore from a nanadroid back up & now im getting a MD5 Mismatch. Tried several times & the same thing.
When I try to just reboot the phone normally it gets stuck on the white htc splash screen & thats as far as it goes. Then tried to just RUU & am getting a USB connection error. Checked my pc for connnected devices & my phone isnt showing up. Yes I have all the drivers, never had an issue connecting my phone to pc before now. I can get into recovery but thats about it. Cant nandroid or ruu. Im running out of ideas & phone is usless right now, this sucks any help is greatly appreciated. Thanks
doin-it said:
Was running Clean Rom 4.1 & decided to try a new rom. Flashed Xi40, after install & upon reboot, phone got stuck in boot screen (was black). Went into recovery & tried to restore from a nanadroid back up & now im getting a MD5 Mismatch. Tried several times & the same thing.
When I try to just reboot the phone normally it gets stuck on the white htc splash screen & thats as far as it goes. Then tried to just RUU & am getting a USB connection error. Checked my pc for connnected devices & my phone isnt showing up. Yes I have all the drivers, never had an issue connecting my phone to pc before now. I can get into recovery but thats about it. Cant nandroid or ruu. Im running out of ideas & phone is usless right now, this sucks any help is greatly appreciated. Thanks
Click to expand...
Click to collapse
Did you try a factory wipe then reflashing?
gunnyman said:
Did you try a factory wipe then reflashing?
Click to expand...
Click to collapse
Yes a few times, rom installs but upon reboot screen just goes balck & never boots any further.
doin-it said:
Was running Clean Rom 4.1 & decided to try a new rom. Flashed Xi40, after install & upon reboot, phone got stuck in boot screen (was black). Went into recovery & tried to restore from a nanadroid back up & now im getting a MD5 Mismatch. Tried several times & the same thing.
When I try to just reboot the phone normally it gets stuck on the white htc splash screen & thats as far as it goes. Then tried to just RUU & am getting a USB connection error. Checked my pc for connnected devices & my phone isnt showing up. Yes I have all the drivers, never had an issue connecting my phone to pc before now. I can get into recovery but thats about it. Cant nandroid or ruu. Im running out of ideas & phone is usless right now, this sucks any help is greatly appreciated. Thanks
Click to expand...
Click to collapse
Boot into the bootloader, enter fastboot mode, and then run the RUU.
can you still access recovery? I wouldnt think there's a need to ruu if you still can get into it. wipe cache, dalvik, and do factory reset and try flashing a different rom perhaps. If you want to ruu then you'll need the drivers installed and be in fastboot on the bootloader. You may need to relock the bootloader as well in fastboot, but by doing that then your only option will be to ruu.
rohan32 said:
Boot into the bootloader, enter fastboot mode, and then run the RUU.
Click to expand...
Click to collapse
Tried this the RUU starting to work was happy for a minute but then half way through it failed ! ugg this isn't looking good.
doin-it said:
Tried this the RUU starting to work was happy for a minute but then half way through it failed ! ugg this isn't looking good.
Click to expand...
Click to collapse
did you relock the bootloader? you need to do that before running ruu.
rohan32 said:
Boot into the bootloader, enter fastboot mode, and then run the RUU.
Click to expand...
Click to collapse
xaey said:
did you relock the bootloader? you need to do that before running ruu.
Click to expand...
Click to collapse
Ahh that was it had to relock then the ruu worked. Thanks alot was starting to sweat for a minute lol At least i have a working phone again. Now to do everything else all over...
Related
I've had a good search for this stuff and I'm having a hard time. Now my phone wont boot.
I have rooted the phone using the HTC One X all in one tool, but then couldnt get it to install Clockwork touch 5.8.2.4 which is included with that.
I found the CWM section in here that linked me to a one click install for Clockwork touch 5.8.3.1 which installed ok, and allowed me access.
I then attempted to install from zip the menubarmod to remove the 3 Dot menu.
After that, the phone makes it past the first htc screen, the telstra screen and then hangs on the second htc one screen after the animation...
So I'm freaking out a little...
Device is a stock HTC ONE XL on Telstra.
Try to do a factory reset in CWM. After that, try to boot the phone. If it doesn't boot, relock the phone and flash the RUU.
Put your phone into fast boot mode by turning it off, holding down the volume down button, and turning it on while still in fast boot mode.
Download the RUU from here: http://forum.xda-developers.com/showthread.php?t=1691295
Then connect your phone to the PC and start the .exe you just downloaded. Follow the steps it tells you exactly.
Bucky Barnes said:
Try to do a factory reset in CWM. After that, try to boot the phone. If it doesn't boot, relock the phone and flash the RUU.
Click to expand...
Click to collapse
How do I re lock my phone?
rohan32 said:
Put your phone into fast boot mode by turning it off, holding down the volume down button, and turning it on while still in fast boot mode.
Download the RUU from here: http://forum.xda-developers.com/show....php?t=1691295
Then connect your phone to the PC and start the .exe you just downloaded. Follow the steps it tells you exactly.
Click to expand...
Click to collapse
Just tried that. It errors on the first time through, then if I put it back into fast boot it errors again. Second error is (155) unknown.
wollow86 said:
How do I re lock my phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1675888
You need to re-lock to flash the RUU.
Bucky Barnes said:
http://forum.xda-developers.com/showthread.php?t=1675888
You need to re-lock to flash the RUU.
Click to expand...
Click to collapse
Looks like thats working now. Thanks heaps!
Can you shed some light on where I went wrong? Essentially I'm trying to remove the 3 dot menu that appears on some apps that havent been updated properly for ICS and the one X.
I have a feeling it was to do with the unlock method I used being for the one x not the one xl on telstra?
Hi,
I have a rooted device and installed CM9 for testing. Then I went into recovery and wiped everything, set to factory defaults and erased sdcard. Now the Sensation boots and hangs when the HTC Logo appears. I cannot get into recovery anymore and when plugged into my computer the device is not recognized even though I have the fastboot driver installed and the normal usb_drivers.
How could I get my device working again? Thanks
Heinzelrumpel
heinzelrumpel said:
Hi,
I have a rooted device and installed CM9 for testing. Then I went into recovery and wiped everything, set to factory defaults and erased sdcard. Now the Sensation boots and hangs when the HTC Logo appears. I cannot get into recovery anymore and when plugged into my computer the device is not recognized even though I have the fastboot driver installed and the normal usb_drivers.
How could I get my device working again? Thanks
Heinzelrumpel
Click to expand...
Click to collapse
when I plug in the device when it ist shot off, I get this
c:\adb>adb devices
List of devices attached
SH19PV801767 recovery
Click to expand...
Click to collapse
When I try to do a "adb reboot -bootloader" oder " adb reboot -fastboot" only the HTC Logo with white background appears. Windows does not recognize the device. In device manger it only say "Android". I tried to give it another driver, but the system complain, that it is the wrong one. I have tried to install drivers from different sources. Nothing.
Are you s-off or s-on?
Sent from my HTC Sensation using Tapatalk 2
heinzelrumpel said:
Hi,
I have a rooted device and installed CM9 for testing. Then I went into recovery and wiped everything, set to factory defaults and erased sdcard. Now the Sensation boots and hangs when the HTC Logo appears. I cannot get into recovery anymore and when plugged into my computer the device is not recognized even though I have the fastboot driver installed and the normal usb_drivers.
How could I get my device working again? Thanks
Heinzelrumpel
Click to expand...
Click to collapse
if you are SON ..then after flashing the ROM ..do the extra 1 step from this guide
ganeshp said:
if you are SON ..then after flashing the ROM ..do the extra 1 step from this guide
Click to expand...
Click to collapse
Unfortunately that won't work, because the relies on the the fact, that I am in fastboot. I cannot get into fastboot. I read that EXTRA1, which suggests in my case to go to EXTRA4.
P.s. I do not now if I have s-on or off. Sorry, but I forgot to look it up before I wiped eveything
Sory, I was wrong. I am now in fastboot
Great. Everything works fine again. Thanks
i recently started another thread asking for help with my soft bricked stock htc one s.
i was basically playing a game, exited then rebooted and got stuck in a boot loop. tried to install various ruus but was unable to find the proper version/cid to install.
today i got the bright idea of unlocking the bootloader and installing recovery to avoid the issue of my apparent o/s corruption and just installing a custom rom.
unlocked the bootloader successfully, installed cwm successfully then try and boot into recovery, screen goes white with the htc warning about being for developers for 30seconds or so then it restarts into the boot loop at the htc quietly brilliant screen. though maybe there was a problem with the cwm so i tried twrp with the same problem.
does this mean im looking at a hardware fault or does anyone think it could still be software related? im kind of worried now as i probably just voided any chance of getting warranty from htc...
A recovery and unlocked bootloader will not help you get out. Now flash a custom ROM. Don't forget to flash the boot.img
Sent from my locked, tampered ville
---------- Post added at 07:20 AM ---------- Previous post was at 07:18 AM ----------
Oh and don't start two threads!!
Sent from my locked, tampered ville
Is there a way to flash a rom from Fastboot? I've tried fastboot flash system romname.zip and fastboot flash boot boot.img without any luck, appears I've made it worse as the bootloop loads to fastboot now...
I can't get adb to recognize the device, only fastboot commands work. It's weird though, I checked the log of the failed ruu installs and it seems to recognize the phone with adb during the install attempt. I've also tried mirroring the commands from the ruu log but I can't replicate the ability to access adb. I was able to get that black htc screen that pops up during the ruu install though, I dunno if that's a special mode for running adb commands or what it's for but I wasn't able to connect then either...
fastboot flash zip rom.zip
then
fastboot flash boot boot.img
i broke down and spent $20 on a official ruu for my phone. it installed successfully but the phone is still stuck looping the white htc screen.
hoping htc honors my warranty, i unlocked my bootloader trying to fix this problem but its starting to look hardware related... unless there is another partition of software on the phone that could have become corrupted...
mikeinaus said:
i was basically playing a game, exited then rebooted and got stuck in a boot loop.
Click to expand...
Click to collapse
It happens sometimes, you should have just gone into the stock recovery and did a factory reset. But it's too late lets move on...
unlocked the bootloader successfully, installed cwm successfully then try and boot into recovery, screen goes white with the htc warning about being for developers for 30seconds or so then it restarts into the boot loop at the htc quietly brilliant screen. though maybe there was a problem with the cwm so i tried twrp with the same problem.
Click to expand...
Click to collapse
Sounds like the kernel didn't get put, you know the part where you are supposed to do fastboot flash boot boot.img. But it's too late lets move on...
does this mean im looking at a hardware fault or does anyone think it could still be software related? im kind of worried now as i probably just voided any chance of getting warranty from htc...
Click to expand...
Click to collapse
As long as you can get to bootloader you can recovery the phone (as least that's my experience)
mikeinaus said:
Is there a way to flash a rom from Fastboot? I've tried fastboot flash system romname.zip and fastboot flash boot boot.img without any luck, appears I've made it worse as the bootloop loads to fastboot now...
Click to expand...
Click to collapse
Yeah you made it worse, since it only loads to fastboot now, most likley you caused a problem with your recovery. But that's real easy to fix.
I can't get adb to recognize the device, only fastboot commands work. It's weird though, I checked the log of the failed ruu installs and it seems to recognize the phone with adb during the install attempt. I've also tried mirroring the commands from the ruu log but I can't replicate the ability to access adb. I was able to get that black htc screen that pops up during the ruu install though, I dunno if that's a special mode for running adb commands or what it's for but I wasn't able to connect then either...
Click to expand...
Click to collapse
That's a real mess, just stop whatever you're trying to do there.
mikeinaus said:
i broke down and spent $20 on a official ruu for my phone. it installed successfully but the phone is still stuck looping the white htc screen.
Click to expand...
Click to collapse
Where did you spend the $20? File Factory? An RUU shouldn't fail to the fix the problem. I would suggest you just unlock it, install a recovery and then your rom of choice. Even if it's just a rooted stock ROM.
If I was in your spot, I would do this.
1. Unlock Bootloader
2. Install TWRP - Do a factory reset, then wipe system.
3. Flash a custom rom
4. Boot into bootloader - fastboot flash boot boot.img.
5. Reboot
If I was in your spot, I would do this.
1. Unlock Bootloader
2. Install TWRP - Do a factory reset, then wipe system.
3. Flash a custom rom
4. Boot into bootloader - fastboot flash boot boot.img.
5. Reboot
Click to expand...
Click to collapse
1. have done so
2. tried it as well as cwm, phone will not boot into a recovery, doing so just loads into the loop
3. tried without luck
4. tried this as well after flashing rom and still same problem
running the ruu removed the "tampered" message from bootloader as well as stopping the loop from loading into fast boot, it also removed the red developer text from popping up when booting. however the phone is back to its original problem of looping the htc quietly brilliant screen. ive run the ruu twice now without any change.
if the ruu cant fix the problem im doubtful messing around with custom roms will. there is clearly some kind of problem with the phone causing the loop. as far as i understand a ruu completely wipes all the data on the phone and reinstalls all the partitions from scratch.
ive just sent htc an email seeing if theyll cover it for warranty, hopefully they will stand behind their product, as i was not the cause of this problem...
i got the ruu from football, he is the one who posted the thread with all the stock ruu's and he was able to track down the proper one for my phone...
mikeinaus said:
1. have done so
2. tried it as well as cwm, phone will not boot into a recovery, doing so just loads into the loop
3. tried without luck
4. tried this as well after flashing rom and still same problem
running the ruu removed the "tampered" message from bootloader as well as stopping the loop from loading into fast boot, it also removed the red developer text from popping up when booting. however the phone is back to its original problem of looping the htc quietly brilliant screen. ive run the ruu twice now without any change.
if the ruu cant fix the problem im doubtful messing around with custom roms will. there is clearly some kind of problem with the phone causing the loop. as far as i understand a ruu completely wipes all the data on the phone and reinstalls all the partitions from scratch.
ive just sent htc an email seeing if theyll cover it for warranty, hopefully they will stand behind their product, as i was not the cause of this problem...
i got the ruu from football, he is the one who posted the thread with all the stock ruu's and he was able to track down the proper one for my phone...
Click to expand...
Click to collapse
You're in a ****ty spot then. There might be one or two ways to still recover but it sounds like your chances are getting slimmer. I've seen a few other reports of completly stock One S's taking a ****. I hope HTC fixes it for you.
htc said this regarding unlocking the boot loader when i asked about coverage with my problem. looks like they may still cover it. im betting there gonna take the easy way out and just say its not covered when its all said and done though. ive read horrible things about htc customer service...
Not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty. There are several possibilities of what may have caused this issue, that are covered by the warranty, in which the unlocking of the bootloader would not be a problem. We advise you to contact our tech specialists as they will let you know if this procedure will be covered by the warranty.
Click to expand...
Click to collapse
So, today I trade my HTC One for a RAZR XT925, $350, and a water proof 32GB Sandisk ultra sd card on Kijiji. I thought it was kinda weird to get all of this stuff, but it seemed fine at the time. Afterwards however, I found out that every time you turn off or reboot the phone, it tried to go into recovery mode or something with the android guy and a bar at the bottom in a loop and always factory reset the phone, so no matter what, every time you turned it off, it'd reset it. After hours and hours of work, I have the bootloader unlocked, rooted, CWM installed, and Cynogenmod also installed. It no longer factory resets it (I think, but i sent a text to a random number and when I rebooted it was still there), however, everytime i power off and power on, it goes into recovery mode. This is very annoying and will make it very hard to sell again, but if I can fix this last thing, I'll have a solid phone until the waterproof S4 comes out as well as having made like $100.
So basically, I need to know what to do to make it boot into the rom by default and not the recovery. Also, I searched it up and someone else had a problem where they kept booting into AP fastboot mode I think, I tried that line, it said successful, but it didnt work. For me, it's booting into the recovery by default.
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
recovery
jmcdonald58 said:
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
roguezz said:
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
Click to expand...
Click to collapse
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
recovery
jmcdonald58 said:
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
Click to expand...
Click to collapse
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
roguezz said:
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
Click to expand...
Click to collapse
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
coldtech said:
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
Click to expand...
Click to collapse
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
coldtech said:
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
Click to expand...
Click to collapse
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
mentose457 said:
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
Click to expand...
Click to collapse
is there an alternative to flash the stock ROM on a locked device?
coldtech said:
is there an alternative to flash the stock ROM on a locked device?
Click to expand...
Click to collapse
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
Thanks for the hint, will give it a try. RSDLite just completed flashing, but the odd behaviour of the phone is still the same. Guess I might just have a broken phone... :/
mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
coldtech said:
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
Click to expand...
Click to collapse
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
mentose457 said:
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
Click to expand...
Click to collapse
the fb_mode_clear was the culprit, thanks a lot!
and the error says: "downgraded security version. update gpt_main version failed. preflash validation failed for GPT" - which is still keeping me from flashing stuff via fastboot.
since I can't fastboot flash at the moment: do you happen to know where I can get the german modem image so that I can flash it using CWM? I think through all the flashing and trying I have a corrupt or wrong modem file (probably the US version). I can not log into the carrier network right now. it asks me for my SIM PIN and unlocks the SIM, but that's it. so I can't make phone calls or anything right now.
Hello
I´m going crazy here.. So I wanted to try Android 5 and long story short my phone is without a rom and apparently won´t install one.
I got the "sdcard wont mount" error but got that fixed by flashing stock recovery and reflash TWRP 2.8.4.0.
But now I cant get any rom to boot. It seem to install just fine but then ether stops at the "white" screen or at the black that comes after.
I tried "Candy5" with "gapps nano" and all seems fine but it wont boot up. Then I tried a CM10.2.0 witch is 4.4.3 but I cant get gapps to install on that one.
Info:
HTC One S s4
Old rom that I had before = Unknown Blackbean version
Hboot = 2.15
Radio = 1.11.50.05.28
Might be because I don´t know how it works but I cant get ADB Sideload to work ether.
Says "Starting ADB sideload feature. . ." in console. And then adb can´t find the device when i run a "adb devices" command.
Hope someone can help me
Edit:
Found a RUU that worked So the phone should not be completely broken.
So I unlocked the bootloader again and flashed the latest TWRP. Things still work at this point!
Then I tried the CM11 rom again and it´s still the same.. White HTC screen (whitout the red text for some reason) then the screen goes black and nothing happens.
Am I doing something wrong when I install the roms? Did it the same way with my old Galaxy s plus yesterday and it worked first try. From 2.x straight to 5.0.2.
How I´m doing it:
Wipe - Data, Cache and Dalvik
Install rom
Reboot phone
Edit 2:
Restored the backup I did after I got the phone running with the RUU. And that also worked as i should.
So why can´t i get any custom rom to work :crying:
Edit3:
I somehow got it to work and is now running LiquidSmooth on 5.0.2
This thread can be locked or deleted now I think.
I have the same probable but I can't even get RUU to work.
Do you have T Mobile phone? Where did you download RUU from?
No I´m not on T-mobile.
I got the RUU from:
androidruu.com/?developer=Ville
twiifm said:
I have the same probable but I can't even get RUU to work.
Do you have T Mobile phone? Where did you download RUU from?
Click to expand...
Click to collapse
I'm in the same boat, I got my recovery to work fine but I can not get any roms to install. I can not find a ruu, my software ver is 3.16.661.5 Telus. I have tried about 4 diff roms. I get stuck on the white HTC screen. boot is unlock but s is on, can not turn it off because adb debug is not on. have no os to load in to, so I can get adb
1st edit
looked around abit if you flash the boot img your rom will load if you have s on.
Dklcp said:
I'm in the same boat, I got my recovery to work fine but I can not get any roms to install. I can not find a ruu, my software ver is 3.16.661.5 Telus. I have tried about 4 diff roms. I get stuck on the white HTC screen. boot is unlock but s is on, can not turn it off because adb debug is not on. have no os to load in to, so I can get adb
1st edit
looked around abit if you flash the boot img your rom will load if you have s on.
Click to expand...
Click to collapse
I had to relock and flash stock recovery in order to get RUU to work. Now my phone is at least working but I still cant flash any roms. I also used rumrunner to get s-off
If you're S-On, have you separately flashed the boot.img via fastboot?