OK...so have had my phone for about a week and wanted to flash my system back to stock due to a few force closes I couldn't get rid of...
After fastboot flashing everything where it needed to be I fastboot boot'd twrp and wiped data and sdcard...clicked reboot and chose slot b to boot from (thought slot b was where I flashed system but it turns out that where I flashed system_other). Now my phone is stock on a black screen and nothing I do will change that! My computer makes a sound when its plugged and unplugged but I can't get the screen to do anything but stay black (no backlight)! Do I have to RMA this thing or is there something in haven't found in searching that I can do to fix this?
I have tried holding the power button till it hard reboots and when its plugged in to my computer, you can't hear the it reboots but back to the black screen when the computer makes the sound that its plugged in. (Just trying to make sure I have all info here so we can hopefully find a solution fast)
Has anyone had this issue and recovered from it?
I had a similar issue back when the HTC One first came out. I had TWRP installed but for some reason it wouldn't flash any ROMs or stock images. It especially sucked because there was no removable storage to ad any other files, ROMs, stock images, etc and I had inadvertently wiped the phone.
For one reason or another, TWRP itself was the issue, so I installed CWM recovery and was able to reflash everything without a problem. If possible, try and change your recovery and reflash
---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------
magnumtripod said:
I had a similar issue back when the HTC One first came out. I had TWRP installed but for some reason it wouldn't flash any ROMs or stock images. It especially sucked because there was no removable storage to ad any other files, ROMs, stock images, etc and I had inadvertently wiped the phone.
For one reason or another, TWRP itself was the issue, so I installed CWM recovery and was able to reflash everything without a problem. If possible, try and change your recovery and reflash
Click to expand...
Click to collapse
Actually I just re-read your post and my issue was not similar, but regardless, at the time, TWRP was giving me all kinds of problems. I'm not sure if theres another recovery out there yet, but try one if there is and see what happens
My pixel is on stock recovery and I can't even boot fastboot to get to recovery....screen just stays black...now that the battery finally died, I get a red led when I plug it in but when it tries to power up the led stops blinking red and it just stays at a black screen
Related
My phone is rooted with stock rom. The only changes are listed below
Froze bloat that was safe
changed bootanimation to stock samsung
replaced some apps with inverted versions of themselves (ex. google +, stock messaging)
Here goes:
I was using navigation and I noticed that my phone was off after I had finished. Nothing worked at all, I could not boot into recovery or download. I connected the phone to a charger and red led flashes and an empty battery appears. The battery was full. I could reboot the phone while on the charger, but it would shut off as soon as it got to the homescreen. While off, If I pressed the home button, the green battery would appear as if it were charging. From here I could boot into recovery and download mode. The phone will only boot into these modes while connected to the charger. Here is where it went bad. I attempted to restore a backup while the phone was on the car charger and my car charger got pulled out in the middle of a restore. No charger meant that the phone shut off mid restore. Now, when I plug in the phone, the red led appears and the empty battery with a circle inside appears and then goes away. This repeats itself over and over and the phone buzzes when the empty battery reappears. I can still boot into download mode but not recovery. If I try to flash the stock samsung rom via odin, it says that it passes, however upon automatic reboot the samsung appears and nothing else. After the samsung appears the phone just continues to buzz every 5 seconds or so as if it is trying to do something. Could it be a bootloop? I have done a ton of searching here and now I am resorting to help! Your time is appreciated and beers on me if you can help me get my phone back to normal.
I had an issue close to yours and I had to use KIEs to flash back to a stock rom and restore the phone to its factory settings.
This might be the only thing you can do, and it will take some time.
I'm not sure what to make of the whole battery thing as that's not an issue I've seen or even heard about...
As for recovering things, it looks like Odin is going to be the way to go. What exactly did you flash? Was is the system image, the boot image, some combination? It seems as though multiple partitions are damaged. There is a combination Odinable tar around somewhere (I think invisiblek put it together) with basically all the partitions including the entire boot chain, system, and recovery. That's where I'd start...unless of course you already tried that. If you can't find it, I can get it to you tomorrow. Good luck.
---------- Post added at 02:16 AM ---------- Previous post was at 02:09 AM ----------
Couldn't edit for some reason. Here's the file I mentioned. It's the combination one.
http://goo.im/devs/invisiblek/i535
Thanks, I will try it with Kies first now.
Odin said setup connection and dont goes further (maybe wrong cable or wrong device, dont know).
The easiest were for me to solve this issue with the recovery, but if Kies now can help, I can start from the beginning, and thats better than a full brick
Lots of people are having problems with the Android 4.2 update. They lose root or they can't get back into recovery. So BEFORE you flash 4.2 or if you already did and are having issues. Download this utility I whipped up. It will flash (or reflash) the 4.2 update (Including system, kernel and bootloader). It'll flash the latest 4.2 compatible ClockworkMod Touch Recovery. And then it'll get you all set up to re-root your N7 within the latest CWM. Instructions are included in the README file. PLEASE READ IT!
You DO NOT need to be on a stock rom to run this and it will NOT erase your data. But it is recommended when you get into CWM recovery for obvious reasons.
If anyone is having any issues and you get caught at the Google splash screen. You can use Power, Vol - to hard shut down the tablet, then Power, Vol +, Vol - to get into the bootloader. From here you can install the factory images from google. Once you're back up and running, you can run this tool to gain root and CWM back.
Updated 11/14/2012: Replaced SuperSu.apk with the latest version designed for 4.2
Updated 11/14/2012 14:41EST: This package will now contain 3 different runme files. One of them will not erase your data, one will erase your cache only and the last one will erase your data and cache. It seems people coming from some roms are having bootloops or hangs because of a lack of data wipe. You can attempt to run the one with no data wipe, but if you run into trouble, try one of the others. Some have made it through with only a cache wipe. See what works for you.
Updated 11/14/2012 16:53EST: Removed full data erase option as I forgot it will erase your SD card and therefor erase the root zip before it gets a chance to flash. There is only 1 runme file now and it will erase your cache, but leave your data alone. If you're having problems, or you want to avoid problems. Erase your data in CWM before you flash the supersu zip included in the package.
For Now - Windows ONLY, Sorry.
Linux version, on the way
Anyway:
Download and PLEASE READ the Read Me!
Saweet
Sent from my Nexus 7 using xda premium
Just trying to make it easy
im on 4.2 already ,can i use this to root?
Thanks for putting this together tucstwo, it was super helpful and easy for a lot of us here
Ok, I tried this and got stuck on the boot screen. Guess Ill try it again. I was on AOKP before.Can I just run this from there? I should I have wiped before?
edit
Ok it worked once I wiped it when it booted in CWR.
Great job. Now just have to test if it is still rooted
Im not getting something. After I press runme.bat my Nexus goes to clockwork recovery, its not touch, I have to choose from options like Start, Recovery Mode, etc. It doesnt match the instructions. Im super confused, any help?
Ugh. now my device is stuck at the google start screen, and not going anywhere. Android is too complicated sometimes for dumb people like me...
Solange82200 said:
Im not getting something. After I press runme.bat my Nexus goes to clockwork recovery, its not touch, I have to choose from options like Start, Recovery Mode, etc. It doesnt match the instructions. Im super confused, any help?
Click to expand...
Click to collapse
Its booting you in fastboot. just follow the instructions in the window that comes up when you run the runme.bat.
When it boots in fastboot just hit the space bar. It will take a couple times of hitting the spacebar before you reach the CWR stage where you flash the PlaceMeOnYourSDCardSuperSu.zip
When I click runme, it opens up the cmd window, starts the daemon, and then just sits there with a blinking cursor. Tried this few times already, nothing is happening.
EDIT: My nexus 7 is connected and has usb debugging turned on.
Hasan10 said:
When I click runme, it opens up the cmd window, starts the daemon, and then just sits there with a blinking cursor. Tried this few times already, nothing is happening.
Click to expand...
Click to collapse
Do you have ADB set up on you computer?
Did you make sure you have USB debugging selected on your nexus 7 in developer options?
trusteelfan said:
Do you have ADB set up on you computer?
Did you make sure you have USB debugging selected on your nexus 7 in developer options?
Click to expand...
Click to collapse
Figured it out. My computer recognizes the Nexus 7 as a portable device, but not recognizing it in the usb debugging mode (shows "Nexus" under Other Devices with a yellow triangle). Tried to update the driver, but it failed.
Thanks, it wasn't clear to me for some reason when I was doing it. It just kept saying after the black screen press continue, but something stopped along the way. I cant do it again because my device wont get past the Google startup screen, so I guess Im just going to flash from stock or something. Thank you for the quick help though, much appreciated!
Solange82200 said:
Thanks, it wasn't clear to me for some reason when I was doing it. It just kept saying after the black screen press continue, but something stopped along the way. I cant do it again because my device wont get past the Google startup screen, so I guess Im just going to flash from stock or something. Thank you for the quick help though, much appreciated!
Click to expand...
Click to collapse
You can run it again if it got stuck. I had to run it twice
---------- Post added at 10:04 PM ---------- Previous post was at 10:03 PM ----------
Hasan10 said:
Figured it out. My computer recognizes the Nexus 7 as a portable device, but not recognizing it in the usb debugging mode (shows "Nexus" under Other Devices with a yellow triangle). Tried to update the driver, but it failed.
Click to expand...
Click to collapse
The Nexus 7 toolkit will put the right drivers in place if you need them.
OK, I will try that.
By the way, I am currently on Android 4.1 with unlocked BL and CWM Recovery running Franco Kernel. Is this utility safe to use with this setup?
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
OK So I have finally got the drivers, and then ran the runme. It booted me into fastboot mode and now it says sending 'bootloader' <2096 KB>... and seems to be stuck on it. I havent touched anything on my nexus 7, didn't press any buttons yet.
Unplugged it and then plugged it back in. It failed to flash the bootloader and went straight to boot and system flashing. It has now booted into Android 4.2, but I am assuming it still got the older bootloader. I think I will have to re-run the whole process to ensure new bootloader gets flashed eh? Or is there a 4.2 bootloader floating around that I can just flash using CWM and save myself the trouble?
Hasan10 said:
OK, I will try that.
By the way, I am currently on Android 4.1 with unlocked BL and CWM Recovery running Franco Kernel. Is this utility safe to use with this setup?
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
OK So I have finally got the drivers, and then ran the runme. It booted me into fastboot mode and now it says sending 'bootloader' <2096 KB>... and seems to be stuck on it. I havent touched anything on my nexus 7, didn't press any buttons yet.
Unplugged it and then plugged it back in. It failed to flash the bootloader and went straight to boot and system flashing. It has now booted into Android 4.2, but I am assuming it still got the older bootloader. I think I will have to re-run the whole process to ensure new bootloader gets flashed eh?
Click to expand...
Click to collapse
It takes it a few minutes to run the process. You should have just waited
trusteelfan said:
It takes it a few minutes to run the process. You should have just waited
Click to expand...
Click to collapse
No I realized it didn't install the fastboot drivers before the process began. So it was actually not able to send the bootloader. Anyways, can you please read my edited post above and advise me with that to do?
EDIT: I went ahead and re-ran the process. Since all drivers were in place, the total process took less than 5 mins, arguably faster than an OTA. Still have all of my data and the goodness of 4.2.
Thanks a lot OP for this great utility.
trusteelfan said:
Ok, I tried this and got stuck on the boot screen. Guess Ill try it again. I was on AOKP before.Can I just run this from there? I should I have wiped before?
edit
Ok it worked once I wiped it when it booted in CWR.
Great job. Now just have to test if it is still rooted
Click to expand...
Click to collapse
What was it that you wiped? Just to make sure I do exactly what you did. I'm stuck on the glowing nexus logo.
essay708 said:
What was it that you wiped? Just to make sure I do exactly what you did. I'm stuck on the glowing nexus logo.
Click to expand...
Click to collapse
I had to wipe my data. It didnt like coming from AOKP
Nevermind, I wiped cache and dalvik cache and it worked for me too.
Everything is good over here. Rooted with twrp instead tho. Anyway something weird is going on with my battery, and yo seem pretty knowledgeable so I thought I'd run it by ya and see if you couldn't shed some light on the issue. Anyway my battery stats are showing that the device isn't awake.. When clearly it is and in the stats it says the screen is even on.. But not awake. Also the screen seems to brighten and dim at odd times idk if that has anything to do with it. But I flashed an ota update.. Bootloader and all. Kept root with supersu. You think something might have been corrupt or something? Here's a screenshot of the issue.. Hmm another issue, whenever I try to take a screenshot.. With more than one app, it takes a pic of an earlier point when I was on twrp getting ready for the 4.2 update. Some really strange things are going on..
It was working great for a while, after a trip from the US to the UK the phone immediately powers down after boot. It displays the graceful "powering down" message, but simply refuses to actually let me into the OS.
I've tried:
- Factory reset (just user data)
- Full phone wipe (including OS)
- Reinstalling a rom
- Formatting again
The battery is at ~65%, so it can't be that, but I'm at my wits end - I have no clue why it just powers down like that and I've formatted everything the phone will let me format.
It will, however, stay alive if I hangout in TWRP. It will stay on in that all day. The minute I boot into the OS it shuts down.
Anybody have any ideas?
Pull the battery yet ?
I'd flash the 4.4.2 factory image and see if you still have the problem. If you do it's hardware and I'd rma it.
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
insytez said:
Pull the battery yet ?
Click to expand...
Click to collapse
You ever try to pull the battery on a n5?
insytez said:
Pull the battery yet ?
Click to expand...
Click to collapse
?!
Dude, its a unibody. You can't pull the battery.
Can you point me to the stock rom? I've had some trouble finding one.
Also, interestingly - when I try to flash droidkang and cm11 it gripes at me saying it couldnt flash the zip, but when I flash minimalist v4 it flashes just fine.
Why would it be able to stay on forever while in TWRP, but gracefully shut down when in the OS? If it was a hardware problem, wouldn't it make no difference about what state it was in when on?
I've tried going to developers.google.com, fetching the restore files (https://developers.google.com/android/nexus/images#hammerheadkot49h) and running through them.
Every combination of running through that, unlocking, relocking, tried new radios, flashed old radios.
Could dropping it have caused an issue? I can't figure out why it shuts itself off right after boot.
It also appears to have trouble charging. Left it plugged in and powered down all night - only charged ~3%
Managed to get a friend to help me with a custom boot.img that doesnt require keys to run adb during boot - managed to get a logcat during boot.
I'm seeing a lot of readonly filesystem errors, but I'm not familiar enough with android to make a lot of sense from the log.
Can anybody help me make sense of this?
viss said:
Managed to get a friend to help me with a custom boot.img that doesnt require keys to run adb during boot - managed to get a logcat during boot.
I'm seeing a lot of readonly filesystem errors, but I'm not familiar enough with android to make a lot of sense from the log.
Can anybody help me make sense of this?
Click to expand...
Click to collapse
i guess a battery defect.
So I have OnePlus One screen problems. First I dropped it and the screen cracked, so I had it replaced. After it got replaced I now have it back, but before screen worked and touch didn't, and now touch works and screen doesn't. The screen doesn't turn on at all, but when it is plugged in I know it is turned on and I can browse through the filesystem of the OnePlus One via my computer and also when I swipe I can hear the unlocking sound. However, data, WiFi and ADB is disabled so I can't get into there. However, saying Ok Google I can hear the response it gives me so I tried calling a friend but the call never went through. It's running CyanogenMod 12S with TWRP and Xposed flashed if that helps any. I did try following the guide using ColorOS to restore it as if it's hard bricked, but since it never seems to boot into fastboot (spamming fastboot devices in cmd never shows anything) I can't seem to do anything. I tried this on both of my computers running Windows 7, and it never shows up in fastboot, so I don't know which COM port it is to finish the guide, because it wouldn't show up abnormally. Can anyone help me figure out how to get the phone into fastboot? Thank you all so much! Also I don't really have any pictures or videos because I don't have another phone/camera to take them with. Sorry!
Update: I was able to get it into fastboot by getting it into recovery and then typing adb reboot bootloader, but that's about the extent of it. I have Bacon Root Toolkit and stuff and I'm willing to wipe my phone (because there isn't anything that I don't have a backup of) but all I really want is a solution to fix it. It did show up a few times as QHSUSB_BULK (twice, actually) but it also seems to be working, because if I take a screenshot, then reboot to recovery, I can pull the screenshot from the memory to my computer. For some reason the phone isn't showing up at all except in fastboot and recovery now.
I had the same issue with my OPO on Exodus, what I did was I pressed the power button to open the screen then unlocked the screen like usual and then brought the notification bar down and change the brightness by pressing on auto brightness button multiple times and in this whole process my screen was black then I successfully turned on my phone's screen. It also work if you just reboot the phone.
---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------
Also this issue was in the ROM itself and it was fixed in an update.
So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
So during fastboot, the screen actually doesn't go black. I am still able to remain communication and That is when I tried flashing the factory image. How do you make sure that the checksum is correct? I didn't receive any errors during the flash indicating that it didn't flash properly.
If you're using Windows, Hashtab is a good, free checksum program with a GUI.
Download
Info/Review
On Google's image download page, copy the SHA-256 listed, and compare it to what you have locally (which you used to flash onto your phone).
how to boot into twrp? almost the same issue to you, adb cant find my phone.
jcd173339 said:
So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!
Click to expand...
Click to collapse
bush911 said:
how to boot into twrp? almost the same issue to you, adb cant find my phone.
Click to expand...
Click to collapse
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.
post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
It looks like your freezer method works. Putting it in the freezer actually gets the phone to boot completely into google's factory image. its usuable for about a minute until the problem of freezing and turning off reoccurs. It feels like the phone warms up while running so maybe i have a hardware problem rather than software.
I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??
thank you sir, I have twrp installed previously. but the screen doesnt turn on so I can't choose the recovery model. and try to hold the power button for a while the phone will become warm. no other response:crying:
jcd173339 said:
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.
Click to expand...
Click to collapse
Thufail19 said:
I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??
Click to expand...
Click to collapse
Maybe try locking the bootloader? I might try to do that since you and i both are experiencing the same problem with an unlocked bootloader. But i can't see why that would impact anything.