OK I'm stumped.
I was sick of the OTA updates bugging me so I set about flashing to 4.4.2 on my XT1034. All went along fine till I got to the part where I had to flash system with sparsechunk. It kept giving me a permissions error. I wasn't sure what to do so I decided to try rebooting, clearly that was not the answer. Now my phone shows the unlocked boot loader screen for a few seconds and goes to a black screen. I can tell the screen is on, it's just that the screen itself is showing all black. My computer recognizes that something in there and installs the drivers for the ADB interface and USB composite, but not the MTP device. All commands to adb or fastboot just says waiting for device.
Anyone have any idea?
Edit: Not sure if it makes a difference, but I was on stock 4.3, trying to go to 4.4.2 or in firmware terms...
from Blur_Version.14.14.16.falcon_umts.AWSRetail.en.US
to Blur_Version.172.44.4.falcon_umts.AWSRetail.en.US
If your phone even does not start in fastboot mode then i would say you are pretty much fu***d.
Fastboot Cable?
I just had a thought. I have a fastboot cable from my Droid Razr XT912. I wonder if that might force it into fastboot mode?
I'll have to wait till I get home to try it but I'll update it I make any progress.
Hold power button until phone turns off. Turn phone on while holding volume down.
tapman said:
I have a fastboot cable from my Droid Razr XT912.
Click to expand...
Click to collapse
You have a fastboot cable :fingers-crossed::laugh:
Thats really great!
No my friend, your USB cable will not help you to access fastboot mode.
The first way to access Fastboot is to press Volume Down + Power when the phone is switched off.
The second way to access Fastboot is to boot the phone into Android and then
Code:
adb reboot bootloader
But as you have no operating system on your phone there is only option one for you.
So your fastboot cable will not help you. Try several times to get in fastboot with option one.
lost101 said:
Hold power button until phone turns off. Turn phone on while holding volume down.
Click to expand...
Click to collapse
No luck. When I power it off it just power's itself back on a few seconds later whether I and holding the power button or not and regardless of if it's plugged in or not. I've tried the following combinations:
power off then hold volume down while it powers itself on
power off then power back on while holding volume down
hold power and volume down till it reboots
All have the same result, reboot, unlocked bootloader screen, blank, windows detects new hardware and tries to install drivers but fails on the MTP
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
mokkami said:
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
Click to expand...
Click to collapse
Correct. I'll keep trying :/
Edit: Sweet Jebus it worked! I'm back into fastboot
Thank you so very much!
Could be a coincidence but after taking off my case(otterbox defender) and trying again it worked. Maybe the membrane was causing me to press both volume buttons? Weird but I'll take it.
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
mokkami said:
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
Click to expand...
Click to collapse
Yup back up and running now, no idea why I was getting those permission errors. *shrug*
Thanks again
Related
I'm new to Xoom but gave unlocking and rooting a go. That was todays mistake! I flashed a 3g version of boot.img. Then I tried to flash back to stock img-file. Found out that it also was a 3g img-file. Flashed once more. Now it was a wifi-only boot.img. Now I'm stuck at the Motorola Dual Core logo with Starting RSD mode 3 written in top left corner. I can't shut this thing off or anything else but rebooting back to same screen. I really don't know what to do. I bought it yesterday from a man that bought it in the US a week ago so I can't go to the shop and I don't think there are any shop that can flash it for me because it's not available here in Sweden yet. Please help. I have RSD Lite installed and the correct drivers for the Xoom installed. I'm used to ADB but it can't find the device and fastboot doesn't see it either.
Edit. I can't go into fastboot mode.
Grab the wifi's boot.img off of here:
http://forum.xda-developers.com/showthread.php?t=1017398
http://forum.xda-developers.com/showthread.php?t=973355
This might be helpful. Not sure.
Don't worry you are in good company, even BRD had the same problem. Here's how he fixed it:
While I was in "RSD Mode 3" I did
Code:
fastboot flash boot boot.img
Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img. Finally, I did
Code:
fastboot reboot
and was back in the game.
Guys, I think the moral of the story is to slow down and be careful with fastboot. You can bet i'll be a little more careful
Click to expand...
Click to collapse
Edit: Same advice as linked above by milehighclubAV8R
That doesn't do it. Propably it's some stupid misstake from me but I cannot do this because of " I pressed Vol Down + power until the screen went black". It wont get black. When I press Power + Vol down nothing happens. Am I doing something wrong. I have tried holding the buttons for about 30 seconds and nothing happens.
Did you just press the buttons or did you also enter the fastboot code as suggested?
First cmd command then pressing the buttons. When I reboot using power + vol up it starts into RSD mode 3. When rebooting it with power + vol up then vol down when black it starts into the logo screen without any text in the upper left corner. Can't even shut it down with long press on power button
Can I pull the battery? On my Galaxy S that's the way out if I get in a boot loop or need to redo a failed flash.
Not AFAIK, the unit is sealed and can't access the battery to pull it.
Perhaps ask in this thread - http://forum.xda-developers.com/showthread.php?t=973355, there may be more technical people seeing it there than in the general section.
OK. I will do that. Thank you for trying to help.
Press power+volume up. Hold it til it restarts. Let go of both buttons once you see the motorola logo then just press volume down once, and you should be then able to cycle through 3 different modes. Press volume down to cycle to different modes, volume up to select. Hope that helps.
Sent from my Xoom using XDA Premium App
Sorry but I can't cycle through anything. There are two modes. Either "Starting RSD mode 3" or nothing and RSDLite can't communicate with it so I belive that my xoom is dead. Sending it in for repair tomorrow. I'm giving up.
mine is stuck in the rsd mode 2. if i push and power and the up it will boot cycle if i the down button it says it is the the flashboot protocol mode, but i cannot get it to respond from the cmd window. my computer doesnt think its connected. i have the correct mot drivers. any help or is it bricked
Some people have been getting lucky with ADB commands however others have not been so luck. I myself am in the others category with one of my XOOMS.
Sucks, but some people have been able to get back. I however have not been so lucky with one of the WiFi XOOM's I have and did this purposely to see if maybe something can be done with it. Looks like we have to wait for all the files to be released......
Any day now Moto, util then people will continue to send these devices in and con the stores . For this, I applaud them.
This might work or it might not.
I had a bricked xoom too. no matter what fastboot i entered it wouldnt recognise it. all it would say is "waiting for device"
This is what i did.
Turn the xoom off
Do not connect you USB cable yet
Fastboot reboot-bootloader
It should say "waiting for devices"
Now plug your xoom
Turn on the xoom.
When you see the Motorola logo press volume down till you see "fastboot protocol"
Press volume up.
It recognise my xoom that way
couldnt turn mine off. let the battery run down. plugged it into power booted it up. no help. bricked
stevenege said:
Some people have been getting lucky with ADB commands however others have not been so luck. I myself am in the others category with one of my XOOMS.
Sucks, but some people have been able to get back. I however have not been so lucky with one of the WiFi XOOM's I have and did this purposely to see if maybe something can be done with it. Looks like we have to wait for all the files to be released......
Any day now Moto, util then people will continue to send these devices in and con the stores . For this, I applaud them.
Click to expand...
Click to collapse
I have to admit, I'm one of them. Sure is a nice way to tell Moto to hurry the F up. I can't say I felt great about it but I wasn't about to lose $600 either.
me to one of them
shipped mine back to the factory today. not sure what they can do to it. is there such a thing as a force flash or will they have to replace the firmare chip to make it work? unstable combo tegra and honeycomb, aint messin with mine anymore.
i just recovered mine from this. i flashed recovery with clockwork mod:
at the rsd 3 screen with the usb attached
fastboot flash recovery recovery.img
held the volume down while pressing the power off on until fastboot started flashing the recovery
fastboot reboot
xoom started in clockwork mod, did a restart and it worked
****This happened after attempting to load recovery from rom manager without flashing new recovery image.***
Did you happen to mention in your explanation about what went wrong with your xoom anything about unlocking or relocking?
My power button is broken so I need to take my phone in to get it replaced. Following the instructions to get it unrooted/return to stock, I need my phone to be recognized in fastboot. It's not happening; I've tried it on three PC's and none of them even see a device connected. It's not even a matter of drivers because when I'm in fastboot it's like nothing is connected at all.
I can't use my volume buttons in fastboot, basicaly I can't do anything at all in fastboot...no volume buttons, no power button and it can't be recognized.
Volume buttons work when phone is turned on. I can do anything I want in recovery or when the phone is up, but in fastboot I can't do anything.
Someone please help!!
By the way, ADB works perfectly but obviously fastboot does not because my PC thinks nothing is connected when fastboot is up on my phone and as I mentioned, my phone is completely unresponsive to anything that I do when I'm in fastboot. I can't use the "volume up/volume down" and tap the power button to get into downloading mode either because MY STUPID POWER BUTTON IS BROKEN!!!
Thank you again in advance....you will be my hero if you can help me with this!!!
forumsid987 said:
My power button is broken so I need to take my phone in to get it replaced. Following the instructions to get it unrooted/return to stock, I need my phone to be recognized in fastboot. It's not happening. I also can't use my volume buttons in fastboot, basicaly I can't do anything at all in fastboot...no volume buttons, no power button and it can't be recognized.
Volume buttons work when phone is turned on.
Someone please help!!
Click to expand...
Click to collapse
tap or smack the back of the phone near the power button until the volume buttons let you scroll. thats what i do. at first it took me a long time, but now it takes me seconds.
delete pls , my mistake sry
simms22 said:
tap or smack the back of the phone near the power button until the volume buttons let you scroll. thats what i do. at first it took me a long time, but now it takes me seconds.
Click to expand...
Click to collapse
I have tried that so much I think I'm going to break my phone.
I just need someway to return this phone to stock without expecting fastboot to work because it seems like it is unresponsive since the power button is not working. I know this sounds weird as heck but I have all the correct drivers installed but three different computers don't see any kind of usb device connected when the phone is in fastboot. I sincerely believe it's because while in fastboot my messed up powerbutton is screwing it up because it's thinking that the power button is held down the entire time.
If anyone has any ideas on how I can get back to stock please tell me. I have 100% access on my phone when it's in recovery because I can use the buttons at the bottom and I have 100% access when it's fully booted up but when it's in fastboot I can't do anything and no computer even sees a USB device connected to it.
Pleaseeee help!!
forumsid987 said:
I have tried that so much I think I'm going to break my phone.
I just need someway to return this phone to stock without expecting fastboot to work because it seems like it is unresponsive since the power button is not working. I know this sounds weird as heck but I have all the correct drivers installed but three different computers don't see any kind of usb device connected when the phone is in fastboot. I sincerely believe it's because while in fastboot my messed up powerbutton is screwing it up because it's thinking that the power button is held down the entire time.
If anyone has any ideas on how I can get back to stock please tell me. I have 100% access on my phone when it's in recovery because I can use the buttons at the bottom and I have 100% access when it's fully booted up but when it's in fastboot I can't do anything and no computer even sees a USB device connected to it.
Pleaseeee help!!
Click to expand...
Click to collapse
i believe that my phone thinks my power button is always pressed down too, but fastboot works here. my suggestion is that you try a different usb chord. i had an usb chord that i could charge with fine, but nothing else worked. i thought my nexus one was messed up until i tried another usb chord.
simms22 said:
i believe that my phone thinks my power button is always pressed down too, but fastboot works here. my suggestion is that you try a different usb chord. i had an usb chord that i could charge with fine, but nothing else worked. i thought my nexus one was messed up until i tried another usb chord.
Click to expand...
Click to collapse
I tried 3 cords, I'm going crazy here! USB works perfect everywhere but both fastboot and recovery don't let me use my volume or power buttons...at least I can get by in recovery because of the capacitve buttons but I need fastboot to return to stock to get a new phone. I am so frustrated!!!!
forumsid987 said:
I tried 3 cords, I'm going crazy here! USB works perfect everywhere but both fastboot and recovery don't let me use my volume or power buttons...at least I can get by in recovery because of the capacitve buttons but I need fastboot to return to stock to get a new phone. I am so frustrated!!!!
Click to expand...
Click to collapse
have you tried pdanets website? http://junefabrics.com/android/
go there, download the free download and install it to youre computer. its tethering software. but thats not why you should try it. follow the on screen instructions after its installed and itll install the proper latest drivers for your phone. theres a chance your drivers might be out of date.
oh yeah. Used pdanet drivers and Google drivers. No luck with either. I can adb with both but like I said the deicer is not the issue it's that fastboot is totally unresponsive so it looks like nothing is connected to the pc
Sent from my Nexus S 4G using XDA App
anyone have any other options/ideas for me?? It would be greatly appreciated
Find an Odin package. Put phone into download mode by installing battery, holding volume buttons while connected to USB.
Does anyone know if the 301k ohm resistor jig works for ns?
Sent from my Nexus S 4G using xda premium
ODIN doesn't work because of the gosh darn power button being broken.
I went kinda crazy and erased everything in recovery so now all the phone does is boot straight into fast boot. I deleted the boot.img recovery everything, hahahaha (I laugh but really I'm crying inside).
I need a fix ASAP, I'm officially out of a phone.
simms22 said:
tap or smack the back of the phone near the power button until the volume buttons let you scroll. thats what i do. at first it took me a long time, but now it takes me seconds.
Click to expand...
Click to collapse
Wow, this actually worked for me Thanks Simms!
I just got stuck in the same situation (http://forum.xda-developers.com/showpost.php?p=22884288&postcount=24) so I kept tapping the back of my phone (with the back cover off). Fastboot kept restarting at first, but then my volume keys started allowing me to change options. I selected recovery and nandroid restored my phone. Now all is well *wipes brow*
Funny thing is, my power button now works properly again (it hasn't been working for the past week)
forumsid987 said:
oh yeah. Used pdanet drivers and Google drivers. No luck with either. I can adb with both but like I said the deicer is not the issue it's that fastboot is totally unresponsive so it looks like nothing is connected to the pc
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
have you found any solution? I have the exact same problem here: powerbutton stucks and no usb-recognition in fastboot (no luck with the tapping either) but no problem with adb in normal mode.
would be great to know if you found a way to deal with this. Thanks!
kajik123 said:
have you found any solution? I have the exact same problem here: powerbutton stucks and no usb-recognition in fastboot (no luck with the tapping either) but no problem with adb in normal mode.
would be great to know if you found a way to deal with this. Thanks!
Click to expand...
Click to collapse
Same problem here.... going crazy since the power button just died on me. I think the device thinks the button is pressed all the time, which makes it a hw issue.. any help to retrieve data on phone would be great!
Having the same problem as the OP...
Pls can someone find us guys a solution.:crying:
Thanks
I had a broken power button and had the same problem. I just sent it back to Samsung with no ROM on it and they fixed the power button and put Gingerbread back on it even though I had voided my warranty by unlocking the bootloader ;')
MistaJae said:
Funny thing is, my power button now works properly again (it hasn't been working for the past week)
Click to expand...
Click to collapse
yeah. mine started workin again after installing jb... almost made me believe it was software problem
Sent from my Nexus S using xda app-developers app
caleb1783 said:
yeah. mine started workin again after installing jb... almost made me believe it was software problem
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Mine broke when I installed Jelly Bean. Something fishy is going on. Now I have the same issue as OP.
Hi,
i've do an error with sense 5 rom flash.
I have rebooted the phone before flashing boot.img. I have try to put the one x in fastboot or recovery mode but nothing (this phone have very **** keys). After I shot down phone but now don't start. If I connect to charger red light works, same at PC. Windows recognize phone as HTC mtp devices and show me unity letter but i can't do nothing.
Battery 70%.
Any ideas?
Thank's
Sv22 said:
Hi,
i've do an error with sense 5 rom flash.
I have rebooted the phone before flashing boot.img. I have try to put the one x in fastboot or recovery mode but nothing (this phone have very **** keys). After I shot down phone but now don't start. If I connect to charger red light works, same at PC. Windows recognize phone as HTC mtp devices and show me unity letter but i can't do nothing.
Battery 70%.
Any ideas?
Thank's
Click to expand...
Click to collapse
If you're phone is read as an mtp device that means it's not dead and the rom is loaded. The screen is black I take it and won't come on?
reboot to bootloader
either using adb (adb reboot bootloader)
or
manually (hold power button until capacitive buttons blink a bunch of times and the phone shuts off then let go of power and press and hold volume until bootloader comes on)
If you still can't see the screen while in bootloader, then your screen is dead.
exad said:
If you're phone is read as an mtp device that means it's not dead and the rom is loaded. The screen is black I take it and won't come on?
reboot to bootloader
either using adb (adb reboot bootloader)
or
manually (hold power button until capacitive buttons blink a bunch of times and the phone shuts off then let go of power and press and hold volume until bootloader comes on.
If you still can't see the screen while in bootloader, then your screen is dead.
Click to expand...
Click to collapse
yes, my phone is read but on the control panel there is a yellow icon on driver. and if I push keys phone do nothing
Sv22 said:
yes, my phone is read but on the control panel there is a yellow icon on driver. and if I push keys phone do nothing
Click to expand...
Click to collapse
ok.. did you try what I posted above?
exad said:
ok.. did you try what I posted above?
Click to expand...
Click to collapse
yes, but nothing. ADB show me list devices blank, fastboot no devices.....mmhhhh....I have no word. This morning was alive...
today I have turned on the phone in bootloop.
I have volume down key was not working. Any ideas?
Sv22 said:
today I have turned on the phone in bootloop.
I have volume down key was not working. Any ideas?
Click to expand...
Click to collapse
Are you saying the buttons are actually not working properly?
MTP mode plays havoc with adb, and sometimes fastboot. Of course, if you are not able to access recovery, adb, or fastboot, you are in a very tough spot.
Is the device S-off or S-on?
redpoint73 said:
Are you saying the buttons are actually not working properly?
MTP mode plays havoc with adb, and sometimes fastboot. Of course, if you are not able to access recovery, adb, or fastboot, you are in a very tough spot.
Is the device S-off or S-on?
Click to expand...
Click to collapse
my devices is s-on.
I hate this kind of situation. Very comic......
First of all sorry for my english
I have bricked my inspire 4g eng s-off i was just trying to root my inspire 4g without unlocking bootloader noob i just know nothing about unlocking bootloader i used htc quick root software when the process start the software requested me an hboot image and unfortunatly i located to recovery image and phone turned off now when ever i try to turn it on it gives three vibrates vol down +pwr five vibrates please help m
volume up +voldown+pwr button five vibrates and a stable green led vol down +pwr three vibrates and red blinking led just pwr on button three vibrates red blinking led
If your bootloader wasn't unlocked, I don't see how you could have bricked it. Also, do you know if you had usb debug mode turned on? You couldn't have flashed an image with a locked bootloader and the scripts won't work either since the adb/fastboot utilities cannot talk to your phone if debug mode is off.
At any rate, pull out the battery for a few minutes, reseat the battery, connect the phone to your pc, hold down vol- and power and see if you can get to a bootloader screen. Even if it seems to boot but hangs at the green htc logo, you should still be able to issue adb commands and recover.
Once the phone boots, on your pc, open a command prompt and type the command "adb devices" without quotes to see if your phone is recognized. Let us know the status then.
turboyoshi said:
If your bootloader wasn't unlocked, I don't see how you could have bricked it. Also, do you know if you had usb debug mode turned on? You couldn't have flashed an image with a locked bootloader and the scripts won't work either since the adb/fastboot utilities cannot talk to your phone if debug mode is off.
At any rate, pull out the battery for a few minutes, reseat the battery, connect the phone to your pc, hold down vol- and power and see if you can get to a bootloader screen. Even if it seems to boot but hangs at the green htc logo, you should still be able to issue adb commands and recover.
Once the phone boots, on your pc, open a command prompt and type the command "adb devices" without quotes to see if your phone is recognized. Let us know the status then.
Click to expand...
Click to collapse
the bootloader was lock but eng s-off and there is is no adb no fastboot boot i have tried all methods putting battry out for 15 mints i have checked with another battery with no luck when ever i try to turn on my phone it give three vibrates and my pc recognize it as QUALCOMM DIAGNOSTIC 900e when i press vol down +pwr it gives three vibrates vol down +up+pwr five vibrates is there any way to flash the rom in qualcomm diagnostic mode and the usb debug was on last time kindly help me !!
Branded badmash said:
the bootloader was lock but eng s-off and there is is no adb no fastboot boot i have tried all methods putting battry out for 15 mints i have checked with another battery with no luck when ever i try to turn on my phone it give three vibrates and my pc recognize it as QUALCOMM DIAGNOSTIC 900e when i press vol down +pwr it gives three vibrates vol down +up+pwr five vibrates is there any way to flash the rom in qualcomm diagnostic mode and the usb debug was on last time kindly help me !!
Click to expand...
Click to collapse
Qualcomm mode is what happens when you hold volume down instead of up while booting. A common issue with the inspire is the volume rocker malfunctioning and becoming "stuck". Usually it is volume up that gets stuck. Either way you will have to probably repair the volume rocker by replacing it. With the age of the device though I don't think it's worth it to spend any money on repairs. It's almost 3 years old now. I know it seems concidental to happen at the same time your trying to unlock it but it can happen. If it is something that went wrong while you were trying to unlock it your pretty much in the same boat. If it only goes to Qualcomm mode there is nothing you can do.
Gizmoe said:
Qualcomm mode is what happens when you hold volume down instead of up while booting. A common issue with the inspire is the volume rocker malfunctioning and becoming "stuck". Usually it is volume up that gets stuck. Either way you will have to probably repair the volume rocker by replacing it. With the age of the device though I don't think it's worth it to spend any money on repairs. It's almost 3 years old now. I know it seems concidental to happen at the same time your trying to unlock it but it can happen. If it is something that went wrong while you were trying to unlock it your pretty much in the same boat. If it only goes to Qualcomm mode there is nothing you can do.
Click to expand...
Click to collapse
i have checked the volume rocker and replaceed it with no luck
Branded badmash said:
i have checked the volume rocker and replaceed it with no luck
Click to expand...
Click to collapse
Then something happened when you tried to unlock it. If you can't access the device via fastboot or adb then it is not fixable. Reflashing a boot img or hboot would be what you would want to do if you could gain access.
Hey Guys,
so ive been messing around with this little phone and think i might have managed a hard brick. Any thoughts or advice would be appreciated.
was attempting to relock the bootloader and flashing my local 4.4.2 rom and on the command prompt when i reached flash system.img parsechunk lines, they failed. as it said permission denied.
Tried to continue with no luck. Restarted my phone and now cant get into recovery and no boot, the only screen i see is the white warning bootloader locked screen, get a vibrate and then it turns off again. Any ways to flash without Recovery or Fastboot or am i completely out of luck?
Sorry im new to motorolas, had no problems messing around with my old SGS2
Thanks in advance everybody.
did you try this ?
http://forum.xda-developers.com/showthread.php?t=2542219
the only problem is cant get the phone into fastboot mode. Thanks for the input though!
mackb44 said:
the only problem is cant get the phone into fastboot mode. Thanks for the input though!
Click to expand...
Click to collapse
I've been in a few situations where I thought I had 'bricked' my phone. One way that worked (sometimes) was to long press the POWER button for a very long time(minutes), then release and (sometimes) it would reboot.
The usual way to the fastboot menu is - power off (which yours probably is), then hold vol. down and press power button for 5/10 seconds and release both.
Good luck!
jamsh said:
I've been in a few situations where I thought I had 'bricked' my phone. One way that worked (sometimes) was to long press the POWER button for a very long time(minutes), then release and (sometimes) it would reboot.
The usual way to the fastboot menu is - power off (which yours probably is), then hold vol. down and press power button for 5/10 seconds and release both.
Good luck!
Click to expand...
Click to collapse
Yea tried both options, no luck!
The only screen i can get now is the bootloader unlocked screen or the white charging screen when plugged in. After that the screen will stay on but is completely black.
Success I can get into fastboot now!!!! not sure why i could not before
mackb44 said:
Success I can get into fastboot now!!!! not sure why i could not before
Click to expand...
Click to collapse
yes i had something similar,bootlocker warning and then the screen going dark. i just ended up using fastboot and flashing a stock rom and went from there.
glad your panic is over .
quizmaniac said:
yes i had something similar,bootlocker warning and then the screen going dark. i just ended up using fastboot and flashing a stock rom and went from there.
glad your panic is over .
Click to expand...
Click to collapse
Yea thanks buddy!
just have to wait for it to charge up before it will let me flash using adb, oddly its only showing that it is charging while plugged into usb and not the wall socket