Related
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
Tried to S-Off. Something went wrong and now I'm stuck at the Juopunut splash screen on the phone. Can't do anything but access hboot. Not sure what to do and some help would be appreciated...
Re run the juopuntbear program if you want to keep trying. Or flash the boot.IMG from your Rom to get it back running
Sent from my ADR6425LVW using Tapatalk 2
Flash recovery again with fastboot, you can either add it to your sd card as pb31img (or whatever it is) or just use a pc.
Once recovery is back on, boot to it and flash a new Rom, then try the soff procedure again.
You can try to just flash a new boot.IMG, but that never works for me. I've done soff like 5 times now, and when I get stuck at that screen you are on, I just flash a new recovery and Rom then try again.
Sent from my ADR6425LVW using XDA from my ADR6425LVW using XDA
Thanks. I'm able to recover the phone by flashing through fastboot. Finally, S-OFF! Not sure what I was doing wrong as I changed nothing but the program keep on hanging up in the same place everytime like 4 times in a row forcing me to fastboot boot and recovery img's. I guess 5th time's a charm this time! Thanks for the help...
giant22000 said:
Thanks. I'm able to recover the phone by flashing through fastboot. Finally, S-OFF! Not sure what I was doing wrong as I changed nothing but the program keep on hanging up in the same place everytime like 4 times in a row forcing me to fastboot boot and recovery img's. I guess 5th time's a charm this time! Thanks for the help...
Click to expand...
Click to collapse
I had the same happen to me. Run control bear, get stuck, fast boot flash bootbackup and recovery backup, repeat 4-5x, then suddenly success.
Haven't had any problems since.
Congratulations on S-off!
Same problem here. My phone would not reboot when performing he wire trick. I had to battery pull after the wire trick, then it ran all the way through.
Rezound, rooted, loving it.
So I am sending this amaze back to T-Mobile for a warrenty exchange. T-Mobile already sent me the replacement. Not going through HTC or Asuron.
I unlocked bootloader, flashed a recovery, then flashed a new rom. I made a nandroid of my stock rom I had on there before I did the unlock stuff.
So I wiped the custom rom , and restored the stock rom
So now I relocked bootloader and it says relocked and security warning. What exactly does that mean? Is it normal?
T-Mobile doesnt even care about that stuff right? I should only stress it if I was sending it into HTC. I hope lol.
The only problem I am having is when I try to master reset the phone, it takes me to the screen that says bootloader, reboot, reload bootloader, power down and I dont know why. The phone master reset fine the first time I attemped, but I just wanted to do it again. I hold the volume key down and power and the normal screen comes out with Fastvoot recovert factory reset clear storage simlock image crc , but when I click factory reset, it boots for 5 seconds and takes me back to the screen that has bootloader, reboot, reload bootloader etc etc. When I power on and off the phone, it turns on and everything is fine. Normal stock ICS.
Why cant I factory reset it again?
cause you relocked it and yes send it LOCKED
Flash a stock RUU via hboot, it's gonna wipe everything and take it back to complete stock.
Dark Nightmare said:
Flash a stock RUU via hboot, it's gonna wipe everything and take it back to complete stock.
Click to expand...
Click to collapse
It will still say relocked... So not COMPLETELY stock
If htc or tmo get a device that is "relocked" that has software issues, the warranty MAY be in jeopardy... If needed
Sent from my HTC_Amaze_4G using xda premium
But if you s-off, restore to stock, lock bootloader via fastboot and s-on via fastboot, it's gonna all be authentic.
Sent from my HTC Ruby using XDA
glacierguy said:
It will still say relocked... So not COMPLETELY stock
If htc or tmo get a device that is "relocked" that has software issues, the warranty MAY be in jeopardy... If needed
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Not really worried about it. Just wanna send it in normal, even if it says relocked. If they charge, they charge. I doubt it though. How much they charge anyway, tmobile that is. Might be able to just sell it and make some money and still pay back tmobile, seeing its on ebay for 350ish lol. Either way they already sent me a new phone.
Problem is, I did a clean wipe. Just the first one, not the other wipes. I flashed my Nandroid I made before I flashed a custom rom. Everything worked so I relocked it, but when I try to master reset, it automatically takes me to the screen that says bootloader, reboot, reload bootloader, power down and I dont know why
Am I doing something wrong?
For kicks I even downloaded the ota rom and flashed that one after i wiped the other, and when I rebooted that one , it just would flash the HTC sign. So I scratched that idea and redid what I first did.
Same happened to me. I was locking my buddys bootloader on his amaze before I flashed ics on it for him and it deleted his current rom and all of his pics... Everything ...
Learned the hard way. Then I flashed the ics leak in bootloader and it worked fine.
Are u soff? Cuz if u are... Make sure u have jbear or eng hboot flashed
Sent from my HTC_Amaze_4G using xda premium
glacierguy said:
Same happened to me. I was locking my buddys bootloader on his amaze before I flashed ics on it for him and it deleted his current rom and all of his pics... Everything ...
Learned the hard way. Then I flashed the ics leak in bootloader and it worked fine.
Are u soff? Cuz if u are... Make sure u have jbear or eng hboot flashed
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Also not to mention, when I flashed the ICS zip I found on here , when I went into bootloader, all these weird things poped up about not having .imgs
Nah I am S ON.
I just wanna be able to relock the bootloader and it be able to master reset lol. Not worried about it saying relocked. Like I said, everything was working fine, until I tried master reseting and it doesnt allow it. I mean even from the volume down and power method, when I press master reset, it goes right back to that screen that says bootloader, reboot, reload bootloader, power down, without even reseting or rebooting.
Should I try this method even though I am using the ext recovery? ( when unlocked of course)
http://forum.xda-developers.com/showpost.php?p=27058110&postcount=44
ITALIANNYC said:
Also not to mention, when I flashed the ICS zip I found on here , when I went into bootloader, all these weird things poped up about not having .imgs
Nah I am S ON.
I just wanna be able to relock the bootloader and it be able to master reset lol. Not worried about it saying relocked. Like I said, everything was working fine, until I tried master reseting and it doesnt allow it. I mean even from the volume down and power method, when I press master reset, it goes right back to that screen that says bootloader, reboot, reload bootloader, power down, without even reseting or rebooting.
Click to expand...
Click to collapse
Usb debugging is hopefully turned on.
Connect phone to pc and boot into bootloader and go into fastboot.
Open command prompt on pc
Go to the directory where u have the fastboot program (ie "C:\Android\platform-tools" ) and your oem lock token
Type "fastboot OEM lock"
That should relock it.
Then take the PH85IMG and put on root of sd
Boot into bootloader and flash away. U will be good
Sent from my HTC_Amaze_4G using xda premium
glacierguy said:
Usb debugging is hopefully turned on.
Connect phone to pc and boot into bootloader and go into fastboot.
Open command prompt on pc
Go to the directory where u have the fastboot program (ie "C:\Android\platform-tools") and your oem lock token
Type "fastboot OEM lock"
That should relock it.
Then take the PH85IMG and put on root of sd
Boot into bootloader and flash away. U will be good
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Oh yeah? I didnt know I could relock it before flashing it. Where is the ph85img image?
ITALIANNYC said:
Oh yeah? I didnt know I could relock it before flashing it. Where is the ph85img image?
Click to expand...
Click to collapse
Not only can you... You MUST relock bootloadee before flashing ics. U can find the 214.531.3 leak in Footballs thread in dev section... Careful not to get 531.1 leak... That's old
Also... Its a zip package.. not an img file... Don't confuse yourself
Sent from my HTC_Amaze_4G using xda premium
glacierguy said:
Not only can you... You MUST relock bootloadee before flashing ics. U can find the 214.531.3 leak in Footballs thread in dev section... Careful not to get 531.1 leak... That's old
Also... Its a zip package.. not an img file... Don't confuse yourself
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Wow I did not know that. I friggin flashed ICS before I relocked lol. I dont get it though. If I relock it first, wont it not have an OS on it after i wipe when it reboots itself. Do I even need to wipe period. Do I even need to use ext lol
I downloaded the tmobile flashable zip from here
http://forum.xda-developers.com/showpost.php?p=27058110&postcount=44
Meh anyway the one you told me to download is downloading as we speak. 2 hours left wow
and when I hit the HBOOT screen the first thing it does is say some stuff with no image no image no image no image. All ph85 stuff. Wont even allow me to flash anything if I tried. Im thinking maybe its because I havent relocked the boot loader yet? Who knows. Well see what happens when this is finished downloading
To be honest, Tmo doesn't care what you send back to them, you can just brick it if you're insecure, a bunch of people I know sent it droids with CWM and custom roms, they restore it back to stock and change what they have to when you send it in.
After you install that flashable zip, just restore stock recovery via hasoon's tool and delete the superuser.apk from system/app.
ITALIANNYC said:
Wow I did not know that. I friggin flashed ICS before I relocked lol. I dont get it though. If I relock it first, wont it not have an OS on it after i wipe when it reboots itself. Do I even need to wipe period. Do I even need to use ext lol
I downloaded the tmobile flashable zip from here
http://forum.xda-developers.com/showpost.php?p=27058110&postcount=44
Meh anyway the one you told me to download is downloading as we speak. 2 hours left wow
and when I hit the HBOOT screen the first thing it does is say some stuff with no image no image no image no image. All ph85 stuff. Wont even allow me to flash anything if I tried. Im thinking maybe its because I havent relocked the boot loader yet? Who knows. Well see what happens when this is finished downloading
Click to expand...
Click to collapse
That's because its looking for your ph85img.zip file
Once u download and rename the file, and put it on ur sd card, AND relock your bootloader, it will unpack the zip and update
Sent from my HTC_Amaze_4G using xda premium
ITALIANNYC said:
So I am sending this amaze back to T-Mobile for a warrenty exchange. T-Mobile already sent me the replacement. Not going through HTC or Asuron.
I unlocked bootloader, flashed a recovery, then flashed a new rom. I made a nandroid of my stock rom I had on there before I did the unlock stuff.
So I wiped the custom rom , and restored the stock rom
So now I relocked bootloader and it says relocked and security warning. What exactly does that mean? Is it normal?
T-Mobile doesnt even care about that stuff right? I should only stress it if I was sending it into HTC. I hope lol.
The only problem I am having is when I try to master reset the phone, it takes me to the screen that says bootloader, reboot, reload bootloader, power down and I dont know why. The phone master reset fine the first time I attemped, but I just wanted to do it again. I hold the volume key down and power and the normal screen comes out with Fastvoot recovert factory reset clear storage simlock image crc , but when I click factory reset, it boots for 5 seconds and takes me back to the screen that has bootloader, reboot, reload bootloader etc etc. When I power on and off the phone, it turns on and everything is fine. Normal stock ICS.
Why cant I factory reset it again?
Click to expand...
Click to collapse
Just wondering what was the end result of your warranty adventure? Did tmobile end up charging you???
GeOpHmAn said:
Just wondering what was the end result of your warranty adventure? Did tmobile end up charging you???
Click to expand...
Click to collapse
nope
My daughter has a stock Thunderbolt, which has worked since Christmas. All of a sudden a couple weeks ago, she woke up and it was stuck in a boot loop on the HTC splash screen.
I'm still able to get into bootloader, but unable to do a factory reset, or flash a stock RUU. Cannot boot into (stock) recovery. As soon as it tries to load the recovery console, it starts the splash screen looping again. Seems like recovery is corrupt or something
I've tried some unbricking processes, but nothing has worked. If I could get adb to see it, I'd just root it and put cwm on it, but can't get that either.
***LOCKED***
Mecha XD Ship s-on
hboot-1.05.0000
microp-/
radio-1.49.00.0406w_1
eMMC-boot
Jul 19 2011, 14:51:00
Any help is very much appreciated. Verizon store said they can't flash a fresh recovery on it, or the latest RUU...
Nothing? No suggestions?
Maybe something herehttp://androidforums.com/thunderbolt-all-things-root/449138-boot-loop.html will help...
What won't work with the RUU?
It possibly could be caused because of a corrupt sim card and/or a corrupt SD card. Try removing the SD card and see if it will load up. If still nothing, take it to Verizon for another sim card. If you go into a corporate store, they won't charge you for another sim.
Just a couple of my suggestions.
Sent from my ADR6400L using xda premium
I will try that link above.
I brought it into a privately owned verizon store on Thursday, explained to them what was going on, they said they have no idea, and I should bring it to a corporate store, so I did.
I told the guy exactly what was happening. He assumed a read a few things on the internet, so treated me like I've never used a phone before. I have had a G1, Evo, and Evo 3D...all rooted and mega customized, so not like this is my first attempt at using a smartphone.
I've tried booting without the sdcard, same thing. I've tried booting without a sim card, same thing. I tried with another verizon LTE sim card, same thing.
When I try to flash anything, I put the zip on the sdcard, power on to hboot, let it load the zip, then it does nothing, just sits at hboot. I scroll down to recovery to be able to select to restart or power down, press power, it goes to the white HTC splash screen, then the circular arrows above the phone, then to the red X, then back to HTC splash screen and boot loops the splash screen.
I can tell you your recovery is gone. Try downloading the hboot flashable cwm again and flash that in hboot. If you can get into recovery maybe you will be able to flash a rom again. You may also want to reformat your sd card or even try a different one.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
I can tell you your recovery is gone. Try downloading the hboot flashable cwm again and flash that in hboot. If you can get into recovery maybe you will be able to flash a rom again. You may also want to reformat your sd card or even try a different one.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
that's exactly what I told the verizon dude, that recovery is gone and all they need to do is flash it back on, he said that's not possible, handed the phone back to me and said "have a good day".
I knew it was a long shot when I went in there and had to tell them how to boot into hboot, and how to remove the battery.
Don't I have to be S-OFF to flash cwm? Remember, it's stock, unrooted, and S-ON
How didn't the ruu work?
Sent from my ADR6400L using Tapatalk 2
trter10 said:
How didn't the ruu work?
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Because when hboot loaded it, which took a few minutes to load and verify, it then automatically went into recovery to actually flash it, which put it right back into the boot loop.
d0m1n0 said:
Because when hboot loaded it, which took a few minutes to load and verify, it then automatically went into recovery to actually flash it, which put it right back into the boot loop.
Click to expand...
Click to collapse
Now that I think about it, it shouldn't have to go into recovery to flash it, it should have been just fine from hboot....but...after I flashed the RUU, it did reboot into recovery, and started the loop
So did you remember to clear cache and dalvik cache? That would put you in a boot loop every time.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
So did you remember to clear cache and dalvik cache? That would put you in a boot loop every time.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
They weren't installing a rom
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
So did you remember to clear cache and dalvik cache? That would put you in a boot loop every time.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
No...it's stock, stock recovery, stock rom, S-ON...she brought it to me in this condition. It's not a rooting gone wrong. If I could get the laptop to see it, I'd root the damn thing so I can get cwm on it.
When she brought it to me, it was in this exact state. First thing I tried was to boot into recovery, which didn't work. So I googled for 'thunderbolt boot loop' and started trying things.
Before I go any further, I'd like to thank everyone for their input and thoughts. She's 12, and I really don't want to have to buy her a new phone.
d0m1n0 said:
No...it's stock, stock recovery, stock rom, S-ON...she brought it to me in this condition. It's not a rooting gone wrong. If I could get the laptop to see it, I'd root the damn thing so I can get cwm on it.
When she brought it to me, it was in this exact state. First thing I tried was to boot into recovery, which didn't work. So I googled for 'thunderbolt boot loop' and started trying things.
Before I go any further, I'd like to thank everyone for their input and thoughts. She's 12, and I really don't want to have to buy her a new phone.
Click to expand...
Click to collapse
Try redownloading the ruu
Sent from my ADR6400L using Tapatalk 2
I have the exact same problem, I am using a custom rom, killasense.
It loads to HTC splash when I try to connect to computer or try to go into recovery from revolutionary. It says S-OFF on revolutionary, not sure what it means.
Please update if you find a solution, I am trying to do a factory reset, but cannot.
If it says s off that means the phone has been rooted. You're running killasense which is a custom rom.. If you want to go back to stock simply download the most recent ruu, put it on the root of your sd card and rename the file to PG05img. Reboot into the bootloader press the power button to enter fast boot. It will ask you if you want to update select yes. After it completes make sure you rename the file so it doesn't try running the ruu every time you enter the bootloader. Also check the md5 before you try to run it.
Sent from my ADR6400L using Tapatalk 2
I downloaded the 2.1 mecha ruu and tried to load it in hboot, and it said the existing Rom is older. So that mean I can't flash a newer ruu? Gotta be the same or older?
Since I don't have a thunderbolt, I'm not familiar with ruu versions, any way to tell in hboot so I can download the same or older?
Sent from my PG86100 using xda app-developers app
I put a new rom file (BAMF SoaB) into the SD card and renamed it PG05img, went to Revolutionary it said loading PG05img, but after it loaded it did not show a yes or no prompt. It went back to home screen of revolutionary after saying "No image or wrong image", still stuck on boot loop splash screen.
Eksellent said:
I put a new rom file into the SD card and renamed it PG05img, went to Revolutionary it said loading PG05img, but went back to the revolutionary screen without installing I think, still stuck on boot loop splash screen.
Click to expand...
Click to collapse
That means you need to redownload it.
Try this one http://db.tt/z7zbekNa
Sent from my ADR6400L using Tapatalk 2
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.