Related
Hi, I think this should go into Dev section, but i dont have enough Posts yet... This forum is my last hope. I already did Custom Recovery, Root and Custom Rom on a different phone, but I think this time ive briked my Phone
I rooted my brandnew Play yesterday and landed in a bootloop today, i think i had a wifi Problem, however, I then tried out FrAsErTaG's FTS Customrom and everything worked fine. Afterwards I wanted to flash the DooMLoRD Kernel. Now I cant access my phone anymore... Cant get into Bootloader mode nor into flashmode or anything, the led on the Powerbutton stays black. But when i press the Powerbutton, the phone vibrates for a second and a blue or green light flashes for a millisec. When i do the same while connected via usb, the phone does nothing, and the phone isnt recognized by the pc. any Help PLEASE??? Phone was brandnew
Somehow i can access Fastboot mode now, but though i flashed another rom, the phone wont bootup.. no animation, nothing, just the vibration for a sec again.
arihellmichimich said:
Somehow i can access Fastboot mode now, but though i flashed another rom, the phone wont bootup.. no animation, nothing, just the vibration for a sec again.
Click to expand...
Click to collapse
You need to flash a new kernel/boot.img by the looks of it, maybe try flashing the stock kernel as you know it works, if boot partition is corrupt or badly flashed, flashing a rom wont solve the problem
Sent from my R800i using Tapatalk
I think i now realize what i ve done... While using fastboot, i renamed the img files by numbers - also the ClockWorkMod Recovery from this Post http://forum.xda-developers.com/showthread.php?t=1130639 where it is clearly stated that i should not flash it. I think I mixed up the numbers and flashed it and thats why i cant boot anymore... Stupid me!!! Any Idea??? I could kick my own butt right now!!! By the way, i can access CWM now via Fastboot, but booting up normaly still doesnt work of course...
arihellmichimich said:
I think i now realize what i ve done... While using fastboot, i renamed the img files by numbers - also the ClockWorkMod Recovery from this Post http://forum.xda-developers.com/showthread.php?t=1130639 where it is clearly stated that i should not flash it. I think I mixed up the numbers and flashed it and thats why i cant boot anymore... Stupid me!!! Any Idea??? I could kick my own butt right now!!! By the way, i can access CWM now via Fastboot, but booting up normaly still doesnt work of course...
Click to expand...
Click to collapse
Just flash doomlords kernel from fastboot, that has CWM embedded into the kernel, so you get to keep your recovery and get to boot your phone
just to be safe, use the command "fastboot erase boot" before you flash a kernel, this will format the boot partition so you can make a clean install
doomlord thread:
http://forum.xda-developers.com/showthread.php?t=1176502
Thanks a lot! Right now, when i connect it to the Powercable, the red led flashes every few seconds. I will try as soon, as my battery is charged again..
... I have a really bad feeling again. After the red led stopped blinking, i connected via Fastboot (blue light), erased the Boot partition and flashed DoomLords Boot Image. Sais 1 bad block encountered! (it told me already, that i had 10 bad sectors when i flashed the rom before but i didnt think this was the problem, because it bootet up at that time).
For now, i cant even get into this fastboot mode, only red light blinking.
Any other ideas please???
arihellmichimich said:
... For now, i cant even get into this fastboot mode, only red light blinking.
Any other ideas please???
Click to expand...
Click to collapse
Good luck with this. I basically did the same thing on Sunday. I gave up trying to fix late Sunday night, but when I tried again yesterday evening I'm only getting the blinking orange light. I did leave the device on charge last night, but the light didn't come on to say it was charging. How do you know your battery is charged?
I'll take AH's advice and if I ever manage to get the blue light back I'll erase boot, installed DoomLords custom kernel and then hope recovery can fix the rest.
I'll post back here if I make any progress before you (and please let us know how, if you manage to fix it in the mean time).
Daeron.
I've spent the last couple of days searching the forum, search google, search the forum some more and I've made a bit of progress.
After finding similar threads in the X10 forum I believe the flashing red light is related to the battery. Also my inability to get a fastboot blue light was caused by uninstalling SE Companion while trying to use other drivers for a Flashtool stock image flash (I didn't get that to work either). I have reinstalled SE Companion and can now connect to my PC in fastboot mode (with the blue light).
This is where my progress ends. I have tried using using this and the commandline outputs this
Code:
F:\Xperia Play\Boot Unlock\fastboot>fastboot boot recoveryPLAY.img
downloading 'boot.img'...
(bootloader) USB download speed was 41547kB/s
OKAY [ 0.549s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.003s]
finished. total time: 0.552s
but the phone does nothing except the blue light goes out. Which leads me back to the battery.
After trying to fastboot the recovery image the only thing I can do is disconnect, take out the battery, put battery back and plug into mains charger. The red light starts flashing again for a short while then I can try again with fastboot.
Next step is to leave it on charge for a few hours (only did 30mins last time) and try again. I think the reason the recovery didn't work is the battery won't hold enough charge to boot on its own, so I need a new battery
The only other thing I haven't tried is to erase partitions before booting recovery. I'll give that a go before booting recovery image in a few hours.
D.
When i boot into CWM from the boot image via fastboot. It will shut off the phone. Just unplug the device, wait a sec, and try to enter fastboot again. Usually it hangs and then goes to CWM. And when you flash a new rom, You need to factory reset in CWM clearing data and cache or else it will bootloop. Thats just basic Android rommage right thurrrr. Mine was stuck, and i just flashed the stock system.sin and kernel.sin and erase the /data and /cache with Clockwork.
fastboot flash system system.sin
fastboot flash boot kernel.sin
Sooo sorry, i didnt post before, but i moved out of my flat and had a lot of other stuff to do last week...
In the End this helped for me.
1. FULLY CHARGE YOUR PHONE!!! I was told to remove battery for 30minutes, then put it back in but without sim card and withough SD Card. Then plug the charger back and charge for at least 5-10 hours!!!
2. Connect your Phone in Fastboot mode (blue light) by pressing the searchbutton before connecting.
3. Do the steps of relocking your play through Fastboot
4. Try SE Update again with the official Sony Software, it said software could be updated :-D
So in the end, the blinking red light was just a battery problem, i couldnt imagine it was such a big deal, because i always charged for at least an hour and i thought the usb port of my netbook was at least strong enough to provide power during the flashing progress BUT IT WAS NOT!!!
Thank you soo much for the help!!!
Everything worked out fine that way.
Hey guys, I know this is the 1000th time you've seen this thread. However, I might be a little different.
I've read all the red blinking threads before posting this one.
ROM: CM10 Stable Snapshot
Kernel: Franco r53
Okay, yesterday as I was downloading and I opened a game, my phone screen just turned off completely. I'm assuming it was due to overheating as the phone was getting pretty hot.
So I assumed it died, no big deal. I tried to boot up using power button, no luck.
Then I panicked and started searching XDA for all these red blinking LED of doom threads.
I managed to get the phone to boot up to the Google screen by having it on a wall charger + hold the power button for 10 seconds. But then it just shuts down. I managed to make it stick with bootloader, but only on the wall charger, which isn't much help. On a USB connection with my computer, I'm not able to even open boot loader as it would just open and turn off the phone within a few seconds.
Threw it on the charger over night, no luck.
This morning, nothing has changed.
So what's weird about my situation is, I can get it into fast boot, but only when it's on a wall charger, nothing else. And getting it to Google logo for a few seconds.
Edit: I can't RMA, because when it boots to Google logo, it says bootloader is unlocked (the little icon). And I also bought the phone off Swappa, so it's not attached to my account (is it even possible to claim warranty?)
Interesting this sounds like a hardware problem all right. Simply because you said it works on the mains charger which has an output of 1.2a were as the USB to PC chargers phone at rate of 400ma. I would try getting a replacement if you can. Also are you able to boot into recovery through boot loader if so you could try wiping everything or restoring from back up.
Okay, something weird. I tried a different method of getting into fastboot, and it worked (connected to PC).
Hold volume - (DOWN) by itself WHILE plugging in the USB cable. And now I'm in fastboot. Now I'm just trying to find a way to erase cache via toolkit x)
Edit: Weird, toolkit picks up the ADB device but manual adb doesn't using adb devices command.
I've read another user who fixed this by removing the back, then disconnecting and reconnecting the battery connector. Sorry I can't find the post but I'm sure it was in one of the I bricked my phone threads.
Yeah, I saw that, too. But I don't have the equipments for it, unfortunately
ADB won't recognize my nexus 4.
Toolkit will (so I know that toolkit is installed properly). I tried opening a command prompt through toolkit and I couldn't run anything.
Any suggestions?
draikz said:
ADB won't recognize my nexus 4.
Toolkit will (so I know that toolkit is installed properly). I tried opening a command prompt through toolkit and I couldn't run anything.
Any suggestions?
Click to expand...
Click to collapse
Adb won't work from bootloader, you should have fastboot access though
I'm in fastboot now.
I cannot get into recovery =[ When I select recovery, it would just turn off the phone and the blinking lights begins again.
Try charging overnight with other charger, not stock
Sent from my Nexus 4 using xda premium
Just tried with a nonstock charger. It blinked red. Then the battery charging screen popped up (first time ever). And now it's dead blinking red again.
Hopefully I'll see results overnight.
draikz said:
Just tried with a nonstock charger. It blinked red. Then the battery charging screen popped up (first time ever). And now it's dead blinking red again.
Hopefully I'll see results overnight.
Click to expand...
Click to collapse
That's a good sign! Sounds like it was in some serious deep hibernation! The fact that the battery icon popped up shows u didn't brick it or anything, its just really really dead! However when I had my problem, I had just a red light on all the time, it never blinked
Sent from my Google Nexus 4
Mine is constantly blinking. :'(
And it's probably not dead because I did manage to get it into fastboot. And I got adb to pick up using fast boot.
Every after reflashing recovery, I can't get into anything other than fastboot. When I try to select "Recovery" from the fastboot menu, it just turns off and continues to blink ;[
if you can get it into fastboot while plugged in your pc, scroll down in fastboot to the "power off" option. leave it there to charge up for a bit. you can check if its charging by using adb
Code:
adb shell cat /sys/class/power_supply/battery/capacity
hopefully it comes back to life after you charge it a bit. After it charges I would flash stock images just to be safe.
rayford85 said:
if you can get it into fastboot while plugged in your pc, scroll down in fastboot to the "power off" option. leave it there to charge up for a bit. you can check if its charging by using adb
Code:
adb shell cat /sys/class/power_supply/battery/capacity
hopefully it comes back to life after you charge it a bit. After it charges I would flash stock images just to be safe.
Click to expand...
Click to collapse
Okay, trying that now. It's been on the charger all night.
How does one ADB with the phone "powered off"?
So if the phone died because of heat, didn't it throttle properly? How is this possible?
Why don't you reflash stock images through fast boot? I don't understand why the need to be in recovery?
Sent from my Nexus 4 using Tapatalk 2
Lownita said:
So if the phone died because of heat, didn't it throttle properly? How is this possible?
Click to expand...
Click to collapse
I'm not really sure. I'm just assuming that it died from heat.
joshnichols189 said:
Why don't you reflash stock images through fast boot? I don't understand why the need to be in recovery?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I thought I had to factory reset it first inorder to flash factory image? (Coming from CM and Franco) At least that's how I always done it or it'd get stuck in a boot loop on my old phone.
But it is my last resort as well, because I have some precious data on this phone x)
Oh and Google pulled factory images, do you knows know where I can get a copy of one?
draikz said:
I'm not really sure. I'm just assuming that it died from heat.
I thought I had to factory reset it first inorder to flash factory image? (Coming from CM and Franco) At least that's how I always done it or it'd get stuck in a boot loop on my old phone.
But it is my last resort as well, because I have some precious data on this phone x)
Oh and Google pulled factory images, do you knows know where I can get a copy of one?
Click to expand...
Click to collapse
Mskip tool kit has images. There might be a thread in general section with them
Sent from my Nexus 4 using xda premium
rayford85 said:
Mskip tool kit has images. There might be a thread in general section with them
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I've not flashed stock before for this phone. And I'm afraid it might be different.
So question noob question.... Do I flash the booterloader and radios too? I've read that it's pretty dangerous to flash those.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Any instructions I should do differently?
EDIT: I just flashed stock, nothing happened. Still could only get to fastboot. I am now losing hope.
draikz said:
I've not flashed stock before for this phone. And I'm afraid it might be different.
So question noob question.... Do I flash the booterloader and radios too? I've read that it's pretty dangerous to flash those.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Any instructions I should do differently?
EDIT: I just flashed stock, nothing happened. Still could only get to fastboot. I am now losing hope.
Click to expand...
Click to collapse
IF ur going to rma it don't forget to lock the bootloader :angel:
So i was trying the new beta for PA android and when i was on recovery wiping as usual, the wipe process just froze there for a while, i decided to leave it till it worked again but to no avail it didnt budge at all, so i commited the ultimate sin, and powered it off by holding the power button...
when i tried again tu turn it on the tablet would go thru the google with the padlock screen and then show me a black screen with a little logo of clockworkmod and a version number below, the screen itself has no use since no matter what button i press it does nothing, other than that the tablet keeps rebooting after that.
when i try any combination of buttons to access either the real recovery or the bootloader the tablet just plain ignores that im trying to turn it on, just doesnt work, it just turns on if im not pressing anything besides the power button.
to sum up to all my problems i would love to keep trying and see if at anypoint it will turn to bootloader, i havent seen the notification of the tablet being charged... meaning that i dont know if it has enough battery to last me the remaning ideas i had.
So in a nutshell
-no bootloader
-no fastboot
-no recovery
-cant tell if battery or not
Please if anyone knows how to fix or at least get me to a bootloader i would fix everything else, but i really need the guidance here
Have you tried another charger and cable? A simple idea, but not one to over look.
Without bootloader menu or recovery, not much you can do. I'd work on getting into one of those first. Not much you can do until then.
Osivanlou said:
So i was trying the new beta for PA android and when i was on recovery wiping as usual, the wipe process just froze there for a while, i decided to leave it till it worked again but to no avail it didnt budge at all, so i commited the ultimate sin, and powered it off by holding the power button...
when i tried again tu turn it on the tablet would go thru the google with the padlock screen and then show me a black screen with a little logo of clockworkmod and a version number below, the screen itself has no use since no matter what button i press it does nothing, other than that the tablet keeps rebooting after that.
Click to expand...
Click to collapse
Are you able to get adb to recognize the device with "adb devices"?
KJ said:
Have you tried another charger and cable? A simple idea, but not one to over look.
Without bootloader menu or recovery, not much you can do. I'd work on getting into one of those first. Not much you can do until then.
Click to expand...
Click to collapse
Yeah ive tried 4 other chargers, and nothing new, i know that the os itself takes care of the charging as does the recovery in some cases, but since i have non i dont know if its gonna charge at all or not and trying doesnt sound really appealing since i should save battery in case theres a solution and needs battery power
but thanks for the answer
[email protected] said:
Are you able to get adb to recognize the device with "adb devices"?
Click to expand...
Click to collapse
Dont really know how to check, i mean i could get into the tools and try the command Adb Devices but how should i even begin to test? i mean shouldnt i be in a adb static platform on the device? if i try to get into bootloader it just doesnt turn on, and when it does it goes straight to the black screen with the clockworkmod symbol and numbers
Thanks for the answer
Osivanlou said:
Dont really know how to check, i mean i could get into the tools and try the command Adb Devices but how should i even begin to test? i mean shouldnt i be in a adb static platform on the device? if i try to get into bootloader it just doesnt turn on, and when it does it goes straight to the black screen with the clockworkmod symbol and numbers
Thanks for the answer
Click to expand...
Click to collapse
if you have enough battery and can get pc to see is thru adb. you may be able to fastboot a new rom onto the device. You can from pc Request device to go into bootloader or fast boot from the PC..
This is your only shot.. I Would suggest borrow a friends Nexus 7 Full Battery . If you do not know how to do any of this . Use skips root kit and use the unbrick or factory reset. it will force your device into fast boot and flash a new rom.
Good Luck
erica_renee said:
if you have enough battery and can get pc to see is thru adb. you may be able to fastboot a new rom onto the device. You can from pc Request device to go into bootloader or fast boot from the PC..
This is your only shot.. I Would suggest borrow a friends Nexus 7 Full Battery . If you do not know how to do any of this . Use skips root kit and use the unbrick or factory reset. it will force your device into fast boot and flash a new rom.
Good Luck
Click to expand...
Click to collapse
yeh i know how to use the skip toolkit, yet i hope i have enough battery for the test, because the only friend that i know owns a nexus 7 left the country a few months back, so the battery sounds like its gonna be hard to get. Anyways, as u were saying theres a posibility that while the tablet is rebooting and rebooting it might be able to be found on the adb devices? and use the fastboot, cuz if thats true u would be the hero ive been waiting for...
imma check and tell u later,
thanks for the answer
hi all,
i had the nexus player with me and installed cm12.1, everything was working fine, i had it at the hotel i was staying at. no issues whatsoever. but after i unplugged it and brought it back home, i plugged it back in and it just bootloops on the google logo. the bootloader is unlocked.
i tried pressing the reset button while powering it on, but no luck, the leds dont flash quickly to enter fastboot.
ive tried also keeping the reset button pressed again while powering it on, and eventually the led will blink slowly. i then let go, but then it just brings up the google logo again and will bootloop. tried plugging it into the pc while doing this as well, but adb doesnt detect it either.
pretty cant get into fastboot mode or even the recovery mode. any hints or tips i should try? i dont want it to be dead after just 4 months of usage.
Lol I did the exact same thing in pretty good at getting out of a brick but the nexus player is pretty low on my list its actually been like this for about two months now and I haven't touched it
While the LED is blinking slowly have you checked to see if the device is enumerating over USB at all. I believe slow flash indicates recovery mode. Do you ever see Andy with an exclamation mark?
Sent from my D6503 using Tapatalk
well I was able to get it back up and running by plugging it into my pc and messing with the drivers a little bit, then I used fastboot to flash the stock firmware again and now im putting a custom recovery back on it, all in all its pretty easy to fix so its definitely not dead for good. Sorry im not great with tutorials
howd you end up recovering. i want to get it back up and running. perhaps i can try another pc.
when the led flashes slowly, i have the hdmi cable plugged in, but it just bootloops, never gets to to the android recovery mode. first time ive had a bricked android device.
kewvention said:
howd you end up recovering. i want to get it back up and running. perhaps i can try another pc.
when the led flashes slowly, i have the hdmi cable plugged in, but it just bootloops, never gets to to the android recovery mode. first time ive had a bricked android device.
Click to expand...
Click to collapse
Boot into the bootloader by unplugging the nexus player and then hold the button on the bottom and plug it in. Let the button go when you see the google logo. Then just use fastboot to flash the stock firmware.
Hello
My Nexus 10 stopped booting up and I'm attempting to flash a custom recovery and ROM to see if I can fix it. Since I can't get into Android, I can't enable USB Debugging (which appears to be off since I can access ADB). I tried using the Nexus toolkit but without ADB it doesn't seem to be able to flash a recovery or stock image. I am able to get into fastboot, but not seeing anything there to help me out.
It might just be totally done for as well. The only way I can get it to attempt to boot into the recovery screen is to hold the power, volume up and down and then plug in the pogo charger. USB won't do it, and it won't boot up with nothing plugged in. It might just be a weak battery, but if I unplug it the screen flickers and slowly fades out over 5-10 seconds. It's going to charge overnight to see if that part gets resolved.
Anyone have anything similar and find a fix? It would be much appreciated. I love this tablet and don't really want to get a new one.
Thanks in advance