I cannot get into regular bootloader. It just either sits and stalls, goes to HTC screen, or just straight to recovery. This has happened on and off before but I was always able to get it after a few tries. I've been trying for 2 days since the new ICS was released by Sprint but it's been no go.
I believe I have 1.5 Hboot, but I can't tell for sure because I can't access it. I had to take the long route when I had to root with the HTC unlock thing, etc.
I've tried to get to HBoot using QuickBoot app and using the menu option within TWRP 1.1 and now 2.2 (thought that might be the problem, but guess not)...still just stalls and nothing happens after reset
I've been using only rooted OTA's on my phone and only rooted for bloatware removal and wifi tether. No custom roms. No ICS leak.
The buttons of course work. As soon as I take my finger off of the Down volume button, the phone will activate and boot up normal in some cases.
I don't know if this is causing other issues with my phone as it self reboots or freezes a few times a week. I was looking forward to ICS update because I was hoping it would fix the reboots and freezing. Everything else works fine with the phone.
Any help would be greatly appreciated.
try "adb reboot bootloader" and see if your phone gets into bootloader.
mnomaanw said:
try "adb reboot bootloader" and see if your phone gets into bootloader.
Click to expand...
Click to collapse
Don't you have to be in Bootloader to get the adb commands to work? I tried using fastboot to connect and no go.
brokenmouse said:
Don't you have to be in Bootloader to get the adb commands to work? I tried using fastboot to connect and no go.
Click to expand...
Click to collapse
Look under settings/battery or power saver and uncheck fastboot?
Then you can actually get into hboot.
AFAIK, adb commands work in android, fastboot commands work in bootloader.
just make sure USB DEBUGGING is checked in settings.
When that happens to me, I remove the battery for about a minute, put it back in, hold down volume down, then hold power. It will boot right to bootloader.
Save the Drama for your Mama with Tapatalk 2
coal686 said:
When that happens to me, I remove the battery for about a minute, put it back in, hold down volume down, then hold power. It will boot right to bootloader.
Click to expand...
Click to collapse
This caused a lot of trouble for me trying to flash MeanRom and Tribulattifather's ICS OTA with 4EXT because it kept trying to go into bootloader after the install to do the "smart install" or whatever. The phone would just black out upon reboot and sit there or if I tried doing bootloader manually, it would go straight to recovery again. I was up until 4 in the morning trying to get my phone to fully boot last night...never did.
Brought my phone to work today and left it off nearly all day. I thought I was seriously screwed and would have to do a RUU update/unbrick from work. Lo and behold it went into bootloader first try.
I'm restoring a backup now through TWRP 2.2 (because it doesn't have the smart install feature). We'll see if
What do you think is causing these problems? I don't want anything crazy...just a solid ICS rom or rooted OTA. Most ROMs I read suggest using 4EXT to flash, but I'm afraid of running into this again. Any suggestions or thoughts?
as mentioned above, installed the TWRP 2.2 from bootloader and restored a backup (that worked a long time ago). Now i'm having the same issue I had last night. It won't boot up at all except to recovery again.
For most people, being s-off is the best thing to do. S-on and ICS tend to bootloop. For some reason, 4ext and flash image GUI don't seem to work well in ICS either for some.
Have you tried flashing a GB ROM?
Save the Drama for your Mama with Tapatalk 2
I'm going to have to figure out how to get back to complete stock. Everytime I flash a rom...doesn't matter what it is, the phone will say the flash is done, then reboot to...NOTHING...just a black screen. I've let it sit and nothing happens.
Followed a guide on androidcentral that had a nice restore to stock guide. Did the RUU from my computer and now it's acting normal again. It must've been really messed up because when I had it talking to ADB and did the reboot reloader command (as someone stated), the screen was solid black, though the RUU still saw it.
Related
First off let me start by saying this, I have looked at the other threads, I have been searching for the past 6 hours and the other threads about their Rezounds not booting are all different. Last night I unlocked my phone and flashed amon Ra, made a back up, wiped almost all of the data, and then flashed the ROM Nils' Business ICS 4.0.3 Sense 3.6. After doing so my phone rebooted, it made it past the white HTC screen but once it was at the black screen it does not do anything. I am able to get it into the bootloader, however I can not go into recovery after I hit recovery it loads for a little while and then it has a picture of a phone with a red triangle with an exclamation mark in it, I did not flash the RUU (i overlooked that part) and when i try to flash or do anything i am not able to because the way i learned how (from my computer) i am unable to do so because when i type "adb devices" it does not recognize any devices (even if i am in the bootloader with fastboot) i have tried taking the sd card out, doing a factory rest, and I am fairly certain all i have to do is flash a new kernel but i have no idea how to do that when i am not able to get into recovery or when my computer doesnt recognize it as a device, Let me know if I should leave any more information for you guys and any help you guys could offer would be much appreciated
Try this:
Pull the battery
Put the battery back in and hold power + volume down
This should boot you into HBOOT.
Plug into your PC
If you need to, relock (fastboot oem lock)
Run the RUU
Re-unlock
Re-install AmonRa
Re-ROM
If you want to go back to an old ROM.
Make sure you don't have a PH98IMG.zip on your SD,
Go into recovery
Flash your ROM/backup
Flash the kernel in HBOOT
Reboot
How can I run the RUU? Is there a way to get it on my phone now? After i connected it and typed in a command for the phone in the command line it said "waiting for device" and it stayed in that state for a long time, before, when i tried a command it kept saying "no device found" immediately , so there was a bit of improvement!
galloway2323 said:
How can I run the RUU? Is there a way to get it on my phone now? After i connected it and typed in a command for the phone in the command line it said "waiting for device" and it stayed in that state for a long time, before, when i tried a command it kept saying "no device found" immediately , so there was a bit of improvement!
Click to expand...
Click to collapse
Are you in HBOOT? Does the phone say "FASTBOOT USB" ? If so, are you using the fastboot commands vs adb commands?
I was not in fastboot now the fastboot commands work!(i only tried "fastboot reboot-bootloader" but im assuming the rest will work) but how would i install RUU from the command line? sorry i just started researching how to put ROMs on and Root my phone yesterday and decided to jump into it before fully knowing what i was doing...needless to say that caused an unnecessary problem
Ok, so have you removed your SD Card and put made sure you don't have a PH98IMG.zip on the root? That would be a possible reason you can't get into recovery. I would try that before anything else because you'd still have the same issue later. If you don't have another device to clear the SD card you might have to wipe the SD.
i do not have a PH98IMG file, I tried to reinstall the Amon ra, and i was able to get to recovery, I restored my phone with the backup i had!! So i am basically back to square 1 (well square 2, at least i am unlocked still) But i have NO service at all, normally i even have 4g where i am, will that be fixed if i install a new Rom? and a little off topic (sorry) but what Rom would you guys suggest?
Rezrom... lllboredlll is an android developing beast. Some of the "other" roms the systemui doesnt report battery % correctly
galloway2323 said:
i do not have a PH98IMG file, I tried to reinstall the Amon ra, and i was able to get to recovery, I restored my phone with the backup i had!! So i am basically back to square 1 (well square 2, at least i am unlocked still) But i have NO service at all, normally i even have 4g where i am, will that be fixed if i install a new Rom? and a little off topic (sorry) but what Rom would you guys suggest?
Click to expand...
Click to collapse
No service is probably either having the back cover off(antennas are located there) or by having the wrong kernel ver.
I would suggest Scott's or Nils or Team BAMF's ROM as they're very well tested and stable.
Alright thanks to everyone who replied and helped me out! I was thinking of BAMF so i will give that a try, Any idea why they would put the antennas in the back cover? that was the issue but i have never heard of the antennas being in the cover, that just sounds strange to me...?
I had the same thing happen to me, it wasnt till a day later i figured it out. I kept the battery out because i assumed i screwed up the flash. Finnally i was like screw it, threw it all together and went a buddies house where i looked at my phone and i had perfect signal
Sent from my INCREDIBLE, faster than a THUNDERBOLT, REZOUND!
galloway2323 said:
Alright thanks to everyone who replied and helped me out! I was thinking of BAMF so i will give that a try, Any idea why they would put the antennas in the back cover? that was the issue but i have never heard of the antennas being in the cover, that just sounds strange to me...?
Click to expand...
Click to collapse
The antenna connection are on the back plate so that the least amount of material is in between the signal and the antenna. It actually makes really good sense lol. And works well best signal I have ever had on a phone is my rezound I always have service even when my wife's tbolt dont.
Sent from my ADR6425LVW using XDA
Haha well when it is put that way, it makes a lot of sense to have it on the back cover, the more I think about it, I dont think i have lost service(accept for when the back cover is off) since I got the Rezound!
Hi Everybody-
Last night I went to unlock my phone, and it froze. I'm running leaked ICS firmware, and it has been working fine for weeks. So, pulled battery, restarted, and it would not boot past the white HTC screen.
So far I have tried-
F
lashed a new kernel in fastboot
Restoring a backup (and flashing appropriate kernel)
Re-installing the rom and reflashing kernel
Still won't boot past white HTC screen.
I'm on the new firmware, so I thought I'd try to reflash the RUU. I have the PH98.. file on the SD card, it reads it but won't give me the option to flash, just returns to bootloader.
At this point i'm stuck, is there a way to force the RUU to flash? Should I think about getting S-OFF and trying to flash back to the GB RUU?
Thanks for any help!!!!!
Do s-off. DO NOT UNLOCK AFTER S-OFF. Then run gb ruu twice. Try booting back up after if no luck on the ruu then run in fastboot mode fastboot oem writesecure 3 and send in for a warranty replacement
Sent from my ADR6425LVW using XDA
Thanks! I appreciate the response. I still want to try to get the RUU to take without s-off, not sure what's up with that. Good call on not unlocking after s-off, maybe that will make the RUU take.
You could try running the ruu exe on windows if you haven't tried it yet.
Sent from my HTC Vigor
So, an update-
I flashed the RUU through fastboot (thanks, con247), it went fine but it still just shows the white HTC screen, goes black, then shows the white HTC screen again.
I am going to try unlocking again, flashing a new recovery and reinstalling a basic rom. At this point though, I have a bad feeling.
Has anyone seen anything like this!?!?!? It seems like something internal tweaked, but what would cause only that part (i guess \system, \data or something) to fail?
Thanks all for any help!!!
iaRIVR said:
So, an update-
I flashed the RUU through fastboot (thanks, con247), it went fine but it still just shows the white HTC screen, goes black, then shows the white HTC screen again.
I am going to try unlocking again, flashing a new recovery and reinstalling a basic rom. At this point though, I have a bad feeling.
Has anyone seen anything like this!?!?!? It seems like something internal tweaked, but what would cause only that part (i guess \system, \data or something) to fail?
Thanks all for any help!!!
Click to expand...
Click to collapse
Can you get back to fastboot by holding power and volume down? If so get to command prompt through platform-tools then type fastboot boot boot.img
that should hopefully get you to your rom. Thats what worked for me anyway.
If that fails
iflawdya said:
Can you get back to fastboot by holding power and volume down? If so get to command prompt through platform-tools then type fastboot boot boot.img
that should hopefully get you to your rom. Thats what worked for me anyway.
Click to expand...
Click to collapse
if you dont know the button combination use ADB
ENTER
ADB REBOOT FASTBOOT
or try
ADB REBOOT RECOVERY
then press your home key for a few seconds. choose wipe data. then reboot
hope this helps.
I helped him last night and the issue was resolved.
con247 said:
I helped him last night and the issue was resolved.
Click to expand...
Click to collapse
You the man!
con247 said:
I helped him last night and the issue was resolved.
Click to expand...
Click to collapse
Having the same problem with a friends phone...could you give some instruction on what you did?
If your on the GB firmware, run the Ruu.exe, you should be able to pull the battery and run from fastboot.
If your on an ics leak, con worked some magic so I could s-off, then run the GB Ruu. Check to see if wifi works, mine is c still broken and I will have to get a clnr. The easiest fix might be to just call for a replacement.
Sent from my ADR6425LVW using Tapatalk 2
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
lithium630 said:
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
Click to expand...
Click to collapse
Get one of the old GB RUU's and run it on your phone. Start again. If your phone was truly bricked, it wouldn't power on and you wouldn't get an LED light when it was plugged in.
lithium630 said:
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
Click to expand...
Click to collapse
This is an easy one, or would have been when you were on the black screen. Well the internal storage fix scares me, but hopefully that wont matter. Typically all you need to do is get the PH file from your rom and place on sd card, boot into hboot, and run the update I believe, then reboot.
This title needs to be edited as it's misleading.
lithium630 said:
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
Click to expand...
Click to collapse
Relax. The S-off process blows out your recovery. You didn't brick your phone.
Put a recovery image on your SD card, go into hboot (from a powered down state, power button and volume down) and let 'er reload recovery. If you can't get the file on your SD card through your phone, pop the SD card into a card reader attached to your PC and stick it on there that way.
Once that's done, remove the image file from your SD card, put your fav ROM on it, and install it from recovery.
You may need to fix your SD card's mount points. Within the thread on S-off, there's a link to the process.
None of the commands work because the phone is not recognized. I cannot boot to hboot. Uh oh.
I had the same screen. Pull the battery and reboot into hboot, volume down+power and run the s-off program again. Something didn't finish and it will pick up where it left off in my experience.
lithium630 said:
None of the commands work because the phone is not recognized. I cannot boot to hboot. Uh oh.
Click to expand...
Click to collapse
What happens when you press power+volume down?
Edit: Also, if you're phone turns on, you're not bricked. It's pretty hard to brick this phone.
tekhna said:
What happens when you press power+volume down?
Edit: Also, if you're phone turns on, you're not bricked. It's pretty hard to brick this phone.
Click to expand...
Click to collapse
Yeap just pull the battery and power on with power and volume down.
This kinda stuff you'll be fine with. Just don't get too creative with "repairs" that aren't posted in here.
tekhna said:
What happens when you press power+volume down?
Edit: Also, if you're phone turns on, you're not bricked. It's pretty hard to brick this phone.
Click to expand...
Click to collapse
As I understand it, the only way to brick a phone is to bork a radio installation.
Dude...pull your battery, put it back in, then power and volume down at the same time. If you can get to hboot, life is good.
After about 30 battery pulls I was able to get to hboot. I have no idea what the issue was. Finally got the phone booting now. I appreciate the replies.
lithium630 said:
After about 30 battery pulls I was able to get to hboot. I have no idea what the issue was. Finally got the phone booting now. I appreciate the replies.
Click to expand...
Click to collapse
Awesome, glad to hear. Did the s-off work?
tekhna said:
Awesome, glad to hear. Did the s-off work?
Click to expand...
Click to collapse
Sure did. Took me a little while to get the wire trick right. I just noticed the sd card is not recognized. I see the fix on the thread. That will be tomorrows project.
Constant reboots
I am able to install roms, but I get constant reboots, every few minutes at best. I tried a few different ICS ROMS. I am running the latest firmware. I BELIEVE with s-off I shouldn't have to flash PH98IMG.zip. I tried fixing permissions also but it has not helped.
How did you get the latest firmware and radios without running the PH98IMG.zip? The ics roms you are installing won't update your firmware.
Sent from my ADR6425LVW using Tapatalk 2
Chillerman said:
How did you get the latest firmware and radios without running the PH98IMG.zip? The ics roms you are installing won't update your firmware.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I relocked the phone and updated it a couple weeks ago. Maybe I need to try it again.
lithium630 said:
I relocked the phone and updated it a couple weeks ago. Maybe I need to try it again.
Click to expand...
Click to collapse
Well the newest leak came out 5/7 and the one before that 5/2 so only a week ago. I would download the newest from Android Police and follow the instructions they give to install, then flash a recovery and install a rooted Rom for this firmware like Scott's.
Sent from my ADR6425LVW using Tapatalk 2
lithium630 said:
I relocked the phone and updated it a couple weeks ago. Maybe I need to try it again.
Click to expand...
Click to collapse
I don't know why you relocked...I think there's a thread about not so good things happening to those who relock after S-off. I downloaded and installed the 5/5 leak as PH98IMG after I S-off'd and reflashed the recovery.
I'm pretty sure my hboot said "locked" straight out of the gate after I did the S-off deed.
douger1957 said:
I don't know why you relocked...I think there's a thread about not so good things happening to those who relock after S-off. I downloaded and installed the 5/5 leak as PH98IMG after I S-off'd and reflashed the recovery.
I'm pretty sure my hboot said "locked" straight out of the gate after I did the S-off deed.
Click to expand...
Click to collapse
Nothing bad happens, you just don't ever get back to "locked" without doing S-off again. You're just at "relocked" like the old days. S-on with an eng hboot on the other hand will brick your device.
That aside, there's no need to unlock if you're S-off. Either flash a patched hboot or just flash a PH98IMG.zip of AmonRa if you don't need fastboot commands (I did the latter).
I flashed the last firmware before S-off. I followed the instructions given. I flashed the latest firmware today and this damn thing still reboots constantly. I flashed the 5-7 firmware then the Venasaur Rom.
lithium630 said:
I flashed the last firmware before S-off. I followed the instructions given. I flashed the latest firmware today and this damn thing still reboots constantly. I flashed the 5-7 firmware then the Venasaur Rom.
Click to expand...
Click to collapse
You need to try installing the radio firmware or just install the complete RUU again. And install a clean copy of the rom, not a nandroid backup. Wipe data, cache, dalvic cache, and system before flashing the rom.
Send me a private message if you would like and I'll help you get it figured out on gtalk.
first off, I'm an idiot with this whole thing and shouldn't be doing it probably. i just don't know enough about it to be playing with expensive phones like this so i understand I deserve whatever i get.
i was running a custom rom on an S-ON phone. i forgot the name of the rom (was made by TEAM COOL or something). But I wanted to unroot and go back to normal stock ROM and download the JB update. First, in the SU app, I did a complete unroot. that did nothing except not let me use the app anymore.
then I tried doing the RUU way of going back, but when it would go to the loading bootloader portion, the usb would disconnect and it would fail with error 171.
so then, and i don't know how i got here, but i went into recovery and did a factory reset and now i have no rom. I have tried installing meanrom but it fails after some line regarding a kernal. my phone won't do anything except boot to the white HTC screen or into the bootloader.
i have no idea what to do, I just want it working at this point.
i've been searching forums like crazy but all the solutions are things I already have done or things that won't work for me.
If you haven't done so yet, you need to relock the bootloader before running ruu. Put your phone in fastboot and using SDK or ADB Tools, type fastboot oem lock
om4 said:
If you haven't done so yet, you need to relock the bootloader before running ruu. Put your phone in fastboot and using SDK or ADB Tools, type fastboot oem lock
Click to expand...
Click to collapse
thank you for your help! however, whenever i do this, it just says < waiting for device >
so i finally got a rom to install--clean rom. that is the one i used to have. but when i reboot, it gets stuck on a black screen and won't go any further.
I had the same thing happen. Had to run a boot.img flash utility i found on another thread elsewhere on xda. The flash utility was updated for jb. If i can locate where i found it then i will get back to you.
Sent from my EVO using Tapatalk 2
I was curious if you ever found that rom or if anybody can help me? The phone is still out of commission. It's been tough to make it through the holidays especially since my laptop was stolen the very next day that all this happened
bump again. I'm assuming the phone is bricked for good if the brightest minds on the subject don't even know
i'm using my dad's old evo 4g for now.
unclefarkus said:
bump again. I'm assuming the phone is bricked for good if the brightest minds on the subject don't even know
i'm using my dad's old evo 4g for now.
Click to expand...
Click to collapse
Have you tried meanbean? It has the boot.img flash tool baked in for s-on, just follow the instructions to the tee in the OP... It's in the Android development thread... Good luck
Sent from my EVO using xda app-developers app
Sounds like you need to flash a Rom that has the s-on installer or fastboot flash the kernel for the Rom you have installed
Most roms come with the kernel installer built in now days. just keep trying to flash em. fyi if your phone turns on , even a little bit , you are not bricked
I am trying to flash meanbean. I wiped the cahes and did factory reset, then flashed the ROM. It's been on "Installing /system..." for about 30 minutes now. Something seems wrong. I'm scared to interrupt it in case that's normal or if interrupting it will break it for good.
Well, I think that might be because my twrp version is really old...2.1.8. I tried updating but had no luck.
Now nothing flashes. It gets to 'verifying partition sizes' then fails. Tried this on several roms that would previously flash, just not work.
unclefarkus said:
Well, I think that might be because my twrp version is really old...2.1.8. I tried updating but had no luck.
Now nothing flashes. It gets to 'verifying partition sizes' then fails. Tried this on several roms that would previously flash, just not work.
Click to expand...
Click to collapse
Update twrp through goomanager, its in the market, then try again.
Sent from my EVO using xda premium
mrlakadaddy said:
Update twrp through goomanager, its in the market, then try again.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
lol how could he do that if he dont have any rom installed...dafuq?
You need to FASTBOOT install it:
Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery TWRP.img
Boatiy said:
lol how could he do that if he dont have any rom installed...dafuq?
You need to FASTBOOT install it:
Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
Don't forget the clear cache commands
Sent from my EVO using xda app-developers app
I have given this a go, however, as I should expect by now, nothing happens.
It says "waiting for device" and that's it
Upon typing "adb devices" nothing shows up.
Furthermore, when I go to Fastboot, Fastbook usb does show up, but I get a message on the computer saying the usb device has malfunctioned.
unclefarkus said:
I have given this a go, however, as I should expect by now, nothing happens.
It says "waiting for device" and that's it
Upon typing "adb devices" nothing shows up.
Furthermore, when I go to Fastboot, Fastbook usb does show up, but I get a message on the computer saying the usb device has malfunctioned.
Click to expand...
Click to collapse
Can you get into bootloader? If so go to the TWRP website and download the hboot zip. Put on external sd card and enter bootloader.
Sent from my EVO using Tapatalk 2
Perhaps what is happening when you try oem lock and get that error is that adb is still running from a prior attempt or because of some other program. Try opening your task manager and ending all processes of adb and other programs that connect to the phone. Then try oem locking again and go from there.
Sent from my EVO using xda premium
I made a little bit of progress!
I determined that Windows 8 was the reason I get the usb malfunctioning message. I obtained a Windows 7 computer and it worked like a charm.
That said, I'm not out of the woods yet.
I relocked the phone using fastboot and then have been attempting to flash a stock RUU now that the usb issue is sorted out.
That seems to work but it gets stuck at "sending....." for as long as 35 minutes. I've tried about 4 times, giving between 20-35 minutes and it won't go beyond sending.
I can at least fastboot now; but the phone is locked. Which is fine; I just want back to stock anyways.
Tampered
Re-locked
S-On
Hboot-1.19.0000
Radio-1.12.11.0809
OpenDSP-v29-1.0.45.0622
eMMC-boot
Aug 9 2012
I flashed the 2.13.651.1 RUU by the way.
Any new advice haha?
I loaded a PJ img via sd card and it's alive and updating to JB OTA right now! Thanks for all the help over the past month folks
I relocked my phone, did the stock RUU.exe, went back to a stock Rom, got the update and no matter what I try I can't get unlocked again. Is there a way to uninstall the Update
You can try rerunning the RUU with admin privileges see if that works. Also you can try unlocking bootloader before the update then OTA updating see if that works
Sent from my ViperDNA infected with ViperBlue DNA
EchoX860 said:
I relocked my phone, did the stock RUU.exe, went back to a stock Rom, got the update and no matter what I try I can't get unlocked again. Is there a way to uninstall the Update
Click to expand...
Click to collapse
Did you not read the guide I posted here?
Also try flashing your unlock token a few times some people it works the first time others 10 times later
Sent from my HTC6435LVW using XDA Premium HD app
turn phone completely off, then boot straight in to bootloader by holding power and vol down. then run unlock.bin. works every time.
EchoX860 said:
I relocked my phone, did the stock RUU.exe, went back to a stock Rom, got the update and no matter what I try I can't get unlocked again. Is there a way to uninstall the Update
Click to expand...
Click to collapse
It took 5 attempts for me to unlock. Pain in the rear, I know, but it'll eventually work. Good luck to you. BTW, update DEF improves bluetooth & beats. Major difference, at least, for me there is.:victory:
Forgot to Flash the Kernel Modules, so now I'm having Boot Loops, and am unable to do the Stock.RUU exe because I took the update. I am 90% I'm screwed. Command prompt is also giving me the device not found error. Backups aren't working either, get the same boot loop
EchoX860 said:
Forgot to Flash the Kernel Modules, so now I'm having Boot Loops, and am unable to do the Stock.RUU exe because I took the update. I am 90% I'm screwed. Command prompt is also giving me the device not found error. Backups aren't working either, get the same boot loop
Click to expand...
Click to collapse
i had this problem took two days of pluging and unpluging trying adb sideload and everything under the sun uninstall re install just keep trying and it will connect again just takes a while for it to reconnect