I was running the 2.99 PA rom on my Nexus 7 with m-kernel without any issues until 2 days ago, when my device rebooted and entered a bootloop, got stuck on the Google screen first, then I managed to get into the twrp recovery and erased cache and dalvik cache. Then it booted until the "X" screen and got struck there until I resetted the device by holding the power button for a while. Since then, the screen is totally dead, the only response I can get is the Windows usb device connected sound. I've tried each and every button combination and also pulled the battery but it did not help. The tablet shows up as an APX device in the device manager. I have searched the forums and I only found other people who have accindentally erased their bootloaders and then got stuck in APX, but this is not the case with my nexus as there wasn't any bootloader tinkering involved at all.
Do you have any suggestions on what I should do/try to do?
Should take 18 seconds or so.
You can get to the bootloader (fastboot mode) FROM ANY STATE.
Read that again - from any state.
See "bootloader interrupt" in this thread:
[REF] Nexus 7 Button Combinations
cheers
bftb0 said:
Should take 18 seconds or so.
You can get to the bootloader (fastboot mode) FROM ANY STATE.
Read that again - from any state.
See "bootloader interrupt" in this thread:
[REF] Nexus 7 Button Combinations
cheers
Click to expand...
Click to collapse
I've read that thread and tried the methods listed there but it didn't help. Maybe there's something else that went wrong while the device was bootlooping and corrupted the bootloader?
wasab said:
I've read that thread and tried the methods listed there but it didn't help. Maybe there's something else that went wrong while the device was bootlooping and corrupted the bootloader?
Click to expand...
Click to collapse
Quite possibly. From my limited understanding of the Tegra3 boot process, it sounds freakishly complicated. And complicated is the same thing as "lots of opportunities for bug expressions".
Also, it sounds like you had a spontaneous failure that was not temporally coincident with a flashing operation. That smells like a hardware problem, but it's hard to be certain though as you were using a dev kernel and custom ROM.
If you plug it in to the PC and then hold down the power button for an extended period of time, do you see any activity in the Device Manager that suggests that Windows is seeing a hardware state change (even if it rolls right back into APX mode?)
I'm not aware of any rescue methods at this time via APX on the Nexus 7 at this time (apparently they do exist for other Tegra devices, but the N7 experimenters using those methods have come up empty-handed so far).
bftb0 said:
Quite possibly. From my limited understanding of the Tegra3 boot process, it sounds freakishly complicated. And complicated is the same thing as "lots of opportunities for bug expressions".
Also, it sounds like you had a spontaneous failure that was not temporally coincident with a flashing operation. That smells like a hardware problem, but it's hard to be certain though as you were using a dev kernel and custom ROM.
If you plug it in to the PC and then hold down the power button for an extended period of time, do you see any activity in the Device Manager that suggests that Windows is seeing a hardware state change (even if it rolls right back into APX mode?)
I'm not aware of any rescue methods at this time via APX on the Nexus 7 at this time (apparently they do exist for other Tegra devices, but the N7 experimenters using those methods have come up empty-handed so far).
Click to expand...
Click to collapse
Holding the power button for around 10 seconds causes it to disconnect and then reconnect 4-5 seconds later. Holding the power button with any(or both) of the volume buttons has the same effect.
I did read that apx recovery thread too before posting.. What do you recommend, should I try to get it repaired in warranty as the guys in that thread did, or is it a no-go because of the custom rom and kernel?
wasab said:
Holding the power button for around 10 seconds causes it to disconnect and then reconnect 4-5 seconds later. Holding the power button with any(or both) of the volume buttons has the same effect.
Click to expand...
Click to collapse
Uh-Oh. When you do the power-button-hold-thing with a tab that behaves normally (and is plugged into the PC) you see exactly that timing: APX disappears right around 10 seconds, and then the bootloader screen pops up about 4-5 seconds later. Good news is that your tab knows you are pressing the power button - bad news is the bootloader doesn't appear at the moment it should.
wasab said:
I did read that apx recovery thread too before posting.. What do you recommend, should I try to get it repaired in warranty as the guys in that thread did, or is it a no-go because of the custom rom and kernel?
Click to expand...
Click to collapse
I can't speak from experience, but my guess is there is a technician sitting someplace with a pile of returns, and his/her bosses are breathing down his/her neck to increase the number of units turned per day. They won't be doing a forensic examination; that isn't a cost-effective way to do business. More than likely they will be replacing the motherboard if their diagnostics show the smallest hint of trouble. But I don't know for sure.
Either that or you can take this as a gauntlet thrown down and become the person that cracks open APX for the N7
bftb0 said:
Uh-Oh. When you do the power-button-hold-thing with a tab that behaves normally (and is plugged into the PC) you see exactly that timing: APX disappears right around 10 seconds, and then the bootloader screen pops up about 4-5 seconds later. Good news is that your tab knows you are pressing the power button - bad news is the bootloader doesn't appear at the moment it should.
I can't speak from experience, but my guess is there is a technician sitting someplace with a pile of returns, and his/her bosses are breathing down his/her neck to increase the number of units turned per day. They won't be doing a forensic examination; that isn't a cost-effective way to do business. More than likely they will be replacing the motherboard if their diagnostics show the smallest hint of trouble. But I don't know for sure.
Either that or you can take this as a gauntlet thrown down and become the person that cracks open APX for the N7
Click to expand...
Click to collapse
Thanks for your help! I think that I will try to solve this the easy way, but if I have no luck with that then I'm sure that I'll do some serious digging about the apx recovery.
Hello all,
Recently I have had a major issue with my nexus 7. About a week ago, it died (ran out of battery) while I was using it. When I attempted to turn it on after charging it, I would get the screen that says google, with unlocked lock icon. The tablet would be frozen at this screen. I left it running until it died again. I was running the latest stable release of cyanogenmod 10 with no problems before when this happened.
By now I had realized that the nexus may have been bricked. I did some googling and found that this is an issue other users have been having when their battery died on android 4.2.2. I attempted to restore the nexus. At this time I was able to access bootloader on the device by holding down all of the buttons at the same time. However, I decided not to restore the nexus, and wait until a time where I would be able to turn all of my attention to the problem. But when I tried to restore the device yesterday, I was not able to access bootloader! I connected the device to my PC (running win8) and it is not recognized. Similarly, trying fastboot restart-bootloader gives me "waiting for device". I am afraid that the bootloader may have been corrupted somehow.
My question is, how can I fix this? Is there a way to reflash the bootloader, or is there something that I am missing? Is there a hardware operation that needs to be performed on the device (battery pull, etc)?
Thanks.
AW: [Q] Help! Nexus 7 not working, may be bricked
I doubt your nexus is bricked. Most likely you entered the APX mode. Hold down the power button for about 6-10 seconds, then it should exit from there.
http://forum.xda-developers.com/wiki/APX_mode
Sent from my Nexus 7 using xda app-developers app
Not working
AndDiSa said:
I doubt your nexus is bricked. Most likely you entered the APX mode. Hold down the power button for about 6-10 seconds, then it should exit from there.
http://forum.xda-developers.com/wiki/APX_mode
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
When I hold down the power button, the device just turns off and comes back on again. The google boot logo shows for a few seconds, then I get a black screen.
patil215 said:
When I hold down the power button, the device just turns off and comes back on again. The google boot logo shows for a few seconds, then I get a black screen.
Click to expand...
Click to collapse
If you get a Google logo, that is a good sign - it means the bootloader is at least partially intact, possibly even in perfect shape.
I would proceed assuming that your battery is completely discharged.
Put the device on the charger overnight and then try starting it up while it is still plugged in to the charger. Hold the vol-down button and the power button continuously until at least one second after the Google logo flashes - this should put the device into fastboot mode if the bootloader is intact.
Something to remember is that Li-Ion batteries have a safety feature that prevents them from charging if the battery voltage gets too low. This is part of the reason why they are shipped with a 50% charge - they can sit that way for months and months only self-discharging at a very very slow rate.
OTOH, if you discharge the battery deeply and then let it sit for a long time afterward - especially if there is something like APX mode draining current - the battery voltage can fall below this "safety threshold voltage" and (even though it is still a "good battery" it can no longer be charged).
I'm not sure it the N7 can be started up while plugged in to only the charger; if it can, disconnecting the battery and trying to power up the device might be a way to discriminate "dead device" from "unchargeable battery".
good luck
I've tried this before
bftb0 said:
If you get a Google logo, that is a good sign - it means the bootloader is at least partially intact, possibly even in perfect shape.
I would proceed assuming that your battery is completely discharged.
Put the device on the charger overnight and then try starting it up while it is still plugged in to the charger. Hold the vol-down button and the power button continuously until at least one second after the Google logo flashes - this should put the device into fastboot mode if the bootloader is intact.
Something to remember is that Li-Ion batteries have a safety feature that prevents them from charging if the battery voltage gets too low. This is part of the reason why they are shipped with a 50% charge - they can sit that way for months and months only self-discharging at a very very slow rate.
OTOH, if you discharge the battery deeply and then let it sit for a long time afterward - especially if there is something like APX mode draining current - the battery voltage can fall below this "safety threshold voltage" and (even though it is still a "good battery" it can no longer be charged).
I'm not sure it the N7 can be started up while plugged in to only the charger; if it can, disconnecting the battery and trying to power up the device might be a way to discriminate "dead device" from "unchargeable battery".
good luck
Click to expand...
Click to collapse
I've tried this before. I still get a google screen, even after fully charging it. Does this mean that the battery has become unusable? How can I fix this?
Then try it again. It takes less time than typing a post into XDA.
There are two ways to try it.
1) Hold both Power & Vol-Down simultaneously, and keep holding them down until at least 4 seconds after the B&W "Google" text appears on the screen
2) Hold only the Power button down continuously, but be ready! Press the Vol-Down button as soon as the Google logo appears! - you only get less than a second to do this. (If you are late, the bootloader tries to boot the boot partition). Also, you need to keep holding the Power button down (3 or 4 seconds) after this - wait long enough that you are convinced that the fastboot screen is not going to occur.
As for the battery, you can pop off the back case and use a voltmeter to CAREFULLY measure the open-circuit voltage. The normal 0%-to-100% voltage range is about 3.6v - 4.15v. Obviously if it won't take a charge then there is a battery issue. BE CAREFUL - avoid doing anything which could short the terminals even momentarily.
bftb0 said:
Then try it again. It takes less time than typing a post into XDA.
There are two ways to try it.
1) Hold both Power & Vol-Down simultaneously, and keep holding them down until at least 4 seconds after the B&W "Google" text appears on the screen
2) Hold only the Power button down continuously, but be ready! Press the Vol-Down button as soon as the Google logo appears! - you only get less than a second to do this. (If you are late, the bootloader tries to boot the boot partition). Also, you need to keep holding the Power button down (3 or 4 seconds) after this - wait long enough that you are convinced that the fastboot screen is not going to occur.
As for the battery, you can pop off the back case and use a voltmeter to CAREFULLY measure the open-circuit voltage. The normal 0%-to-100% voltage range is about 3.6v - 4.15v. Obviously if it won't take a charge then there is a battery issue. BE CAREFUL - avoid doing anything which could short the terminals even momentarily.
Click to expand...
Click to collapse
I've tried holding down the buttons in various configurations at least 50 times already. As for the battery, there is current flowing, so I don't think this is a battery issue. Also worth noting is that if the device completely dies and I plug it in again, the charging battery sign appears (an empty battery slowly filling with white bars). Sometimes the device will give a black screen with little white sparks flickering randomly on it.
Well there have been several posts on here with identical symptoms, where the affected owner later reported that their tablet mysteriously started operating normally.
Unfortunately nothing consistent seems to have emerged from those reports.
You could try disconnecting the battery for a few minutes and reconnecting it to see if that makes any difference.
But whatever you do, you're gonna eventually have to press some buttons & the procedure I suggested is diagnostic for the bootloader, even if the boot or /system partition are borked.
BTW In my experience that battery charging graphic shows the charge state of the battery - does yours show closer to empty or full?
bftb0 said:
Well there have been several posts on here with identical symptoms, where the affected owner later reported that their tablet mysteriously started operating normally.
Unfortunately nothing consistent seems to have emerged from those reports.
You could try disconnecting the battery for a few minutes and reconnecting it to see if that makes any difference.
But whatever you do, you're gonna eventually have to press some buttons & the procedure I suggested is diagnostic for the bootloader, even if the boot or /system partition are borked.
BTW In my experience that battery charging graphic shows the charge state of the battery - does yours show closer to empty or full?
Click to expand...
Click to collapse
Mine shows the battery going from empty to full, like an animation. Also, I'm considering sending in the device for repair but I know that since the bootloader is unlocked it probably wouldn't be free.
Also can you link me to any posts related to this? They might be useful in solving my problem.
Thanks
Were you able to get your computer to recognized your Nexus when you connected it? I had to jump through a bunch of hoops with my Win8 machine to get the driver installed, because it didn't pass Microsoft's signature check. Maybe you can use Wug's toolkit to try to fix it, or at least re-lock the bootloader before sending it in for repair?
codehunter2000 said:
Were you able to get your computer to recognized your Nexus when you connected it? I had to jump through a bunch of hoops with my Win8 machine to get the driver installed, because it didn't pass Microsoft's signature check. Maybe you can use Wug's toolkit to try to fix it, or at least re-lock the bootloader before sending it in for repair?
Click to expand...
Click to collapse
After spending a few hours, I was able to get an adb driver installed onto my computer, I also had to jump through a lot of hoops (I run win8 too). Running adb devices shows the nexus in recovery mode. However, I can't access the bootloader whatsoever. Typing fastboot reboot-bootloader just hangs, and I've tried several toolkits but they just hang. I'm not sure if I can do anything unless I can access bootloader. If you know anything I can do please tell.
patil215 said:
Mine shows the battery going from empty to full, like an animation. Also, I'm considering sending in the device for repair but I know that since the bootloader is unlocked it probably wouldn't be free.
Click to expand...
Click to collapse
By coincidence I was charging mine right now (82%), so I shut it down and looked at that battery animation. (I have the v4.18 bootloader & Dec '12 hardware) First the "lightning bolt" symbol shows up in the battery icon, and the a little later, it performs a "filling the battery up" animation. But here's the important part: when that animation runs on mine, it starts from nearly, but not quite full (mostly white, not all black)- about 82%.
Can't tell exactly from the way you described your situation, but this (again) sounds like your battery is either not charging, or the bq27541 charge controller is reporting the wrong battery state.
Unplug the battery and let it sit for a while before reconnecting. If you have a safe way to measure the battery voltage, do so. You'll know right away if the battery is charged and the charge controller chip is lying.
---------- Post added at 08:14 PM ---------- Previous post was at 07:37 PM ----------
patil215 said:
After spending a few hours, I was able to get an adb driver installed onto my computer, I also had to jump through a lot of hoops (I run win8 too). Running adb devices shows the nexus in recovery mode. However, I can't access the bootloader whatsoever. Typing fastboot reboot-bootloader just hangs, and I've tried several toolkits but they just hang. I'm not sure if I can do anything unless I can access bootloader. If you know anything I can do please tell.
Click to expand...
Click to collapse
That is completely bizzare. The only way that a recovery can be started is via the bootloader. If the bootloader doesn't run, nothing can run. (The recovery is a booted kernel just as with the regular OS). Moreover, you saw the battery screen light up - if a recovery was (still) running, you would think something would show on the screen (although I guess recent versions of TWRP does screen blanking now). Very weird.
bftb0 said:
By coincidence I was charging mine right now (82%), so I shut it down and looked at that battery animation. (I have the v4.18 bootloader & Dec '12 hardware) First the "lightning bolt" symbol shows up in the battery icon, and the a little later, it performs a "filling the battery up" animation. But here's the important part: when that animation runs on mine, it starts from nearly, but not quite full (mostly white, not all black)- about 82%.
Can't tell exactly from the way you described your situation, but this (again) sounds like your battery is either not charging, or the bq27451 charge controller is reporting the wrong battery state.
Unplug the battery and let it sit for a while before reconnecting. If you have a safe way to measure the battery voltage, do so. You'll know right away if the battery is charged and the charge controller chip is lying.
---------- Post added at 08:14 PM ---------- Previous post was at 07:37 PM ----------
That is completely bizzare. The only way that a recovery can be started is via the bootloader. If the bootloader doesn't run, nothing can run. (The recovery is a booted kernel just as with the regular OS). Moreover, you saw the battery screen light up - if a recovery was (still) running, you would think something would show on the screen (although I guess recent versions of TWRP does screen blanking now). Very weird.
Click to expand...
Click to collapse
Can I have the links that you mentioned about users having identical symptoms that "fixed themselves"?
I really don't want to send it in for repairs if it's going to cost me. I'm a student with not much money to spare . One of the reasons I bought the nexus 7 in the first place.
bftb0 said:
By coincidence I was charging mine right now (82%), so I shut it down and looked at that battery animation. (I have the v4.18 bootloader & Dec '12 hardware) First the "lightning bolt" symbol shows up in the battery icon, and the a little later, it performs a "filling the battery up" animation. But here's the important part: when that animation runs on mine, it starts from nearly, but not quite full (mostly white, not all black)- about 82%.
Can't tell exactly from the way you described your situation, but this (again) sounds like your battery is either not charging, or the bq27451 charge controller is reporting the wrong battery state.
Unplug the battery and let it sit for a while before reconnecting. If you have a safe way to measure the battery voltage, do so. You'll know right away if the battery is charged and the charge controller chip is lying.
---------- Post added at 08:14 PM ---------- Previous post was at 07:37 PM ----------
That is completely bizzare. The only way that a recovery can be started is via the bootloader. If the bootloader doesn't run, nothing can run. (The recovery is a booted kernel just as with the regular OS). Moreover, you saw the battery screen light up - if a recovery was (still) running, you would think something would show on the screen (although I guess recent versions of TWRP does screen blanking now). Very weird.
Click to expand...
Click to collapse
I also fully charged the nexus 7 overnight. The battery icon now showed no animation because the battery was full (it first showed a picture of the lighting bolt battery, then a picture of a full battery) so I believe that the battery is working correctly.
patil215 said:
Can I have the links that you mentioned about users having identical symptoms that "fixed themselves"?
I really don't want to send it in for repairs if it's going to cost me. I'm a student with not much money to spare . One of the reasons I bought the nexus 7 in the first place.
Click to expand...
Click to collapse
I didn't make a record of them - you will need to search. What sounded very familiar was when you had said
patil215 said:
...black screen with little white sparks flickering...
Click to expand...
Click to collapse
What I recall - probably imperfectly - was that most of those cases seemed to spontaneously resolve when the owner charged their battery. And since your story started out with "black screen and little white sparks flickering", and "low battery" it sounded quite similar.
The various folks who mentioned this said things like "white lines flashing", "like sparks", or "like snow on an old-fashioned TV screen". Don't know if that will help you search, but they are in this forum (Q&A).
I also don't know if their tablets were in one particular mode or another (judging from a PC connected to the tablet - a black screen on the tab doesn't tell you anything) - I don't think any of them reported this.
As I said previously, that Black and White Google logo is produced by the bootloader. I just started my tablet in APX mode right now, and while the "charging battery" icon shows up when using the APX cold-start sequence (Vol-Up+Power), that B&W Google (text) Logo does not show up on the screen - the tablet goes directly from battery charging to APX mode (detected by looking at the PC - device shows up under "Other devices -> APX" in the device manager; VID/PID pair USB\VID_0955&PID_7330&REV_0103
)
So, my point is that it sure seems like your bootloader is there and capable of at least starting up at least part way.
What if your Vol-Down button was not working and you had a borked "boot" partition? If you had that combination, the bootloader wouldn't go into fastboot mode, as it would never see the Vol-Down keypress... and if your boot partition was borked, then you would never get any boot accompanied by a black screen.
At this point I think you should try observing the behavior of the USB port from the PC while trying to start it up... and even though you've tried it before, see if you can get the fastboot screen to appear. Perhaps there is something funky going on with your Vol-down button.
good luck
bftb0 said:
I didn't make a record of them - you will need to search. What sounded very familiar was when you had said
What I recall - probably imperfectly - was that most of those cases seemed to spontaneously resolve when the owner charged their battery. And since your story started out with "black screen and little white sparks flickering", and "low battery" it sounded quite similar.
The various folks who mentioned this said things like "white lines flashing", "like sparks", or "like snow on an old-fashioned TV screen". Don't know if that will help you search, but they are in this forum (Q&A).
I also don't know if their tablets were in one particular mode or another (judging from a PC connected to the tablet - a black screen on the tab doesn't tell you anything) - I don't think any of them reported this.
As I said previously, that Black and White Google logo is produced by the bootloader. I just started my tablet in APX mode right now, and while the "charging battery" icon shows up when using the APX cold-start sequence (Vol-Up+Power), that B&W Google (text) Logo does not show up on the screen - the tablet goes directly from battery charging to APX mode (detected by looking at the PC - device shows up under "Other devices -> APX" in the device manager; VID/PID pair USB\VID_0955&PID_7330&REV_0103
)
So, my point is that it sure seems like your bootloader is there and capable of at least starting up at least part way.
What if your Vol-Down button was not working and you had a borked "boot" partition? If you had that combination, the bootloader wouldn't go into fastboot mode, as it would never see the Vol-Down keypress... and if your boot partition was borked, then you would never get any boot accompanied by a black screen.
At this point I think you should try observing the behavior of the USB port from the PC while trying to start it up... and even though you've tried it before, see if you can get the fastboot screen to appear. Perhaps there is something funky going on with your Vol-down button.
good luck
Click to expand...
Click to collapse
UPDATE!:
Not sure if this will help at all. But I ran adb -d reboot bootloader, and the device just turned off. Completely. I turned it on again by holding power for 15 seconds but I got the exact same thing as before (google with black screen following). Once the device was on and I connected it to Windows, windows said "Windows detected malfunctioning device". But I couldn't duplicate the results again. Running adb -d reboot bootloader just hangs.
patil215 said:
UPDATE!:
Not sure if this will help at all. But I ran adb -d reboot bootloader, and the device just turned off. Completely. I turned it on again by holding power for 15 seconds but I got the exact same thing as before (google with black screen following). Once the device was on and I connected it to Windows, windows said "Windows detected malfunctioning device". But I couldn't duplicate the results again. Running adb -d reboot bootloader just hangs.
Click to expand...
Click to collapse
Incredibly, extra-ordinarily bizzare. ADB on the tablet side is a daemon process that runs in userspace. You would need a completely functional kernel to be running on the tablet, and a functioning ramdisk too in order to communicate with the tablet. ADB does not talk to fastboot mode, nor any other mode of the bootloader.
IF YOU ARE REALLY SHUTTING YOUR DEVICE OFF AND THEN SOMETIME LATER YOU ARE ABLE TO TALK TO THE TABLET BY USING THE adb COMMAND (not fastboot), THAT MEANS THAT THE BOOTLOADER IS SUCCESSFULLY BOOTING SOME (unknown) LINUX KERNEL.
That truly beggars the question of why you are seeing anything on the screen after the google logo. Did the previous ROM not have a splash-screen?
Well, if you can communicate with ADB it might be appropriate to try:
adb reboot recovery
and see what this does.
If you can find the device in the Windows device manager, what would be really, really helpful would be the device VID/PID pair.
The way you do this is like this:
1) Identify the device in device manager; right-click on it and select "Properties"
2) Select the "Details" tab
3) In the "Property" Combo-box pulldown, select the Property Name"
Hardware Ids
If you can get those values we can identify exactly which mode the device is in. There is a decoder ring at the end of the first post in this thread
OK, I'm starting to get fatigued, as I offer up both things to attempt as well as avenues of exploration, and you seem to simply ignore all of it.
I know you have tried it several times, maybe even a million times. Please try both methods of starting the tablet to try and intercept the initial phase of the bootloader startup and see if you can get the tablet to go into fastboot mode.
It's OK to try it and fail. But in all this back-and-forth, not once have you said, "yes I tried it again and it still failed". Try it and report the result, even if it fails.
Please try it again - both methods. In the second method where you click the Vol-Down button only after you see the B&W "Google" text, you need to do it really quickly - and not let your finger off the Power button either for several seconds.
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
PS
The "-d" option to the adb command should only be needed if you were running an emulator via the Google SDK on the same PC.
If that were the case, when you ran the command
Code:
adb devices[/url]
you would see multiple lines of output indicating multiple devices on the machine - one for each running emulator, and one for the actual hardware device (so long as it is actually booted into a recovery or OS and you have the right drivers installed).
bftb0 said:
Incredibly, extra-ordinarily bizzare. ADB on the tablet side is a daemon process that runs in userspace. You would need a completely functional kernel to be running on the tablet, and a functioning ramdisk too in order to communicate with the tablet. ADB does not talk to fastboot mode, nor any other mode of the bootloader.
IF YOU ARE REALLY SHUTTING YOUR DEVICE OFF AND THEN SOMETIME LATER YOU ARE ABLE TO TALK TO THE TABLET BY USING THE adb COMMAND (not fastboot), THAT MEANS THAT THE BOOTLOADER IS SUCCESSFULLY BOOTING SOME (unknown) LINUX KERNEL.
That truly beggars the question of why you are seeing anything on the screen after the google logo. Did the previous ROM not have a splash-screen?
Well, if you can communicate with ADB it might be appropriate to try:
adb reboot recovery
and see what this does.
If you can find the device in the Windows device manager, what would be really, really helpful would be the device VID/PID pair.
The way you do this is like this:
1) Identify the device in device manager; right-click on it and select "Properties"
2) Select the "Details" tab
3) In the "Property" Combo-box pulldown, select the Property Name"
Hardware Ids
If you can get those values we can identify exactly which mode the device is in. There is a decoder ring at the end of the first post in this thread
OK, I'm starting to get fatigued, as I offer up both things to attempt as well as avenues of exploration, and you seem to simply ignore all of it.
I know you have tried it several times, maybe even a million times. Please try both methods of starting the tablet to try and intercept the initial phase of the bootloader startup and see if you can get the tablet to go into fastboot mode.
It's OK to try it and fail. But in all this back-and-forth, not once have you said, "yes I tried it again and it still failed". Try it and report the result, even if it fails.
Please try it again - both methods. In the second method where you click the Vol-Down button only after you see the B&W "Google" text, you need to do it really quickly - and not let your finger off the Power button either for several seconds.
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
PS
The "-d" option to the adb command should only be needed if you were running an emulator via the Google SDK on the same PC.
If that were the case, when you ran the command
Code:
adb devices[/url]
you would see multiple lines of output indicating multiple devices on the machine - one for each running emulator, and one for the actual hardware device (so long as it is actually booted into a recovery or OS and you have the right drivers installed).[/QUOTE]
Sorry for not indicating the results of all of your suggestions.
Believe me, I have probably tried both of your button combinations at least two dozen times already. And I have gone down every avenue of exploration that you've suggested.
I've even tried every single one of the button combinations in the thread of nexus 7 button combinations. When I do anything from when the device is on, after 5 seconds or so the device turns off. Then the tablet shows the Google screen for about 5 seconds, no matter what I do. After the google screen comes a blank black screen (I can tell the device is still on because it's illuminated black, different from if the device was dead or powered off). There's not even a way I can get the tablet to power off - it just automatically restarts even if it's not connected to power, so I have to let it die or do a battery pull if I want to fix it. The black screen remains there indefinitely (until the battery runs out of course).
I've tried disconnecting the battery, leaving it disconnected for 30 minutes, connecting the device to power with the battery disconnected, having the buttons held down and connecting the tablet to wall power and USB pc, and different chargers. Nothing gives me a different result. The battery is alive and working, and the voltimeter did give me a current, sorry for not posting that earlier. About the random sparks/snow, there is really no pattern to when these appear, although they might be more frequent (but it might just be me) after a battery pull or full battery discharge.
Remember, I used to be able to access the bootloader but that stopped working for some reason. I'm kicking myself right now for not restoring the tablet when I was able to access bootloader, but I was busy at the time.
I've had some experience with rooting, locking, and unlocking other android devices, but this is something extremely weird.
Also, I should have posted the hardware ID's of the device before. I had done the exact same thing as you suggested when I was trying to install an adb driver for the nexus 7 (had to jump through a lot of hoops to get it working on win8, goddamn win8). The hardware ID's are USB\VID_18D1&PID_D001&REV_9999 and USB\Vid_18D1&PID_D001. According to the guide this means the device is in custom recovery, which makes sense because I was running Cyanogenmod 10 with clockworkmod recovery. If normally booting into the OS, the tablet should be giving me the default animated Cyanogenmod splash screen. Perhaps this issue is a bug with clockworkmod recovery?
I know that -d is to target a specific device, however I pulled up adb and went through each command methodically (really tedious) to see which ones would work. For some reason adb -d reboot-bootloader was the only thing that gave me a response, and even that won't do anything anymore (it just hangs, same with any other adb command). adb reboot recovery hangs also, and any fastboot command gives me waiting for device. Since I've installed a driver for it, in device manager the device shows up as Android phone and Android Composite ADB Interface. Windows tells me it's working properly (really? I'm not so sure windows).
I'd like to apologize for not indicating the results of trying your suggestions. Believe me, I have been trying them! I've spent probably a total of 12 hours trying to get this damn tablet fixed.
I'd also like to thank you. Without people like you this forum would not be any good. I am really grateful for any advice even if it does not work.
I know this is a hell of a problem. No goddamn clue how this happened. I love android but I sincerely hope that this is a clockworkmod recovery problem because otherwise that would make it a mistake on Google's (and therefore android's part). I know that the battery issues are quite frequent on android 4.2.2, but I have yet to find another user with my symptoms.
Lastly, do you know of some way to lock the device or destroy evidence of having the bootloader unlocked without being able to access the bootloader, in case this can't be fixed and I have to send it in for repair?
Click to expand...
Click to collapse
patil215,
Whew. That took you some time to write - thanks for all the details.
The USB\VID_18D1&PID_D001 USB Device Id sure does look like the custom recovery. I will assume - unless you say differently - that you would see this VID/PID pair any time you had the "black screen but with the backlight on".
Android uses this thing called the "BCB" (Boot Communications Block) to write instructions for the bootloader about what it should do when it starts up the next time. In the absence of seeing this, no doubt the bootloader has a default behavior. But basically, the way this works is that a "reboot" command eventually causes the kernel to write into this non-volatile memory area, and then a soft hardware reset occurs. The bootloader is aware of the BCB, and under normal circumstances, it will read it and attempt to follow the indicated boot mode - and then either erase the BCB or fill it with the "default booting instructions" just prior to booting a kernel or special-purpose mode previously indicated. In this way it will return to it's default behavior the next time it is booted.
The reason I mention it is that I have seen on other devices that got borked (HTC Droid Eris) in a way that sometimes those phones would always jump into a particular booting mode - and ignore any hard-button presses that would normally cause the bootloader to follow a different path. The Eris had/has "bootloader", "fastboot", and "OEM" modes and sometimes borked devices would not boot into anything other than the OEM mode.
So, since you apparently are seeing some evidence that a partially-functioning recovery is running, that sounds like a very similar scenario - the Asus bootloader is always booting to your (damaged?) recovery.
So, that's materially different (I think) than what other folks might have experienced it. The first time I've seen it here, although TBH I've only been looking in here for a little less than 3 months.
I don't know what else to suggest - it sounds like maybe you've tried things like "adb shell" commands?
If the bootloader can't be forced into fastboot mode, that (possibly damaged) recovery mode is the only privileged thing you have left. It seems to me that if you can't get into that somehow - adb being the most obvious route - then there is little left to do.
No, I don't know how to relock the bootloader without using the bootloader. That's probably something that can only be done with factory methods (possibly in APX mode).
Sorry.
I've run into a problem with my S4. I'm rooted, and running Hyperdrive 15.
My phone refuses to boot quite often. Sometimes it will boot up perfectly fine and run for a day - day and a half, or it'll lockup and then refuse to boot up again, OR it will just not boot at all. My power button seems to be unresponsive, and the only way that I can get some action out of the phone is by reseating the battery in the well.
What I think it is, could be 1 of a few things, or a combination of them - i'm not sure.
Scenario 1: While playing with the Hyperdrive tweaks, my phone was hung after running the Zipalign tool for over 20 minutes and I had to pull the battery.
Scenario 2: I'm deployed on a ship currently, and I have my phone in a high-salt enviornment and I'm afraid that there might be salt corrosion inside of the power switch or the USB connection - shorting it out. I took my phone apart tonight and cleaned both items with isopropyl alcohol ( the switch itself on the main board ) but that didn't seem to produce any new results.
Scenario 3: I was recently rooting a Kindle Fire HD 7" for a friend out here, and I was dumb and didn't realize that I was pushing boot loader files that were designed for the Kindle Fire and not for my Galaxy S4. I have since tried to enter recovery, but with little avail. Download mode is also out.
A description of what my phone does when I reseat the battery: My phone will vibrate, the Galaxy S4 logo will show for 1.5 to 2 seconds ( same for download mode ) and if I hold the appropriate button, ' Recovery Booting.... ' will display as well. At that point, my phone will shutoff and the power button will become unresponsive.
If anyone can give me a bit of guidance on how to proceed to repairing my phone, I'd be super grateful.
Scenario 3: I was recently rooting a Kindle Fire HD 7" for a friend out here, and I was dumb and didn't realize that I was pushing boot loader files that were designed for the Kindle Fire and not for my Galaxy S4. I have since tried to enter recovery, but with little avail. Download mode is also out.
This sounds like the most plausible reason.
You will need something like JTAG to really fix it.
Lennyz1988, thanks for the quick reply. Internet out here is slow at best, and sometimes unusable.
As far as your JTAG option, I believe that would work, except that I dont have access to that kind of hardware right now. Sending my phone out at this point entails a month of transit time on each side of the turnaround time required for someone to re-flash my phone, and I wholly believe that I can do this.
As an update to my phone, it will not charge the battery anymore. I'll use someone elses phone to charge my battery soon. If anyone can give me a direction to go as far as how to completely reflash my phone IF it turns on, i'd be grateful beyond belief. I dont want to believe that if I can get it to start up again, that it is a total brick and completely useless - if it turns on again, i need someway to push new boot loader files to it. Really hoping someone can help.
Thanks again in advance.
Hi all,
my Gylaxy M30s rebooted itself yestarday, and now is stuck at the very first screen (the one showing "SAMSUNG Galaxy M30s" in the center and "Powered by android" at the bottom).
Vol down + power results in a reboot attempt (screen goes black, vibration), but the phone is stopping at the same screen again.
I am not able to turn the phone off.
Switching from Vol down to Vol up immediately when screen goes black does not enter recovery mode.
Vol down + power while charging sometimes leads to the charging symbol being shown on the screen, but without the percentage in the middle.
Charging over night did not help.
The phone cannot be connected to a Win PC.
Any suggestions what I can try?
Thanks,
Alchemist
Try volume down+volume up and while pressing those buttons, plug your phone into your computer. Tell me the results of that.
Nothing happening...
I mean trying those combinations immediately after using power+ volume down to reboot.
What did you do with your phone? Died suddenly when normally using?
Yes, phone died during normal usage.
Ah, I see - a screen comes up warning me that downloading a custom OS might harm the phone.
Also, the PC makes this "USB connected" sound when I then press Vol up, but I do not see a new drive connected, I think.
I am slightly optimistic now?
Press volume up.Then install Samsung usb drivers(search on Google)
Ugh, just wanted to do this, but now the phone is completely dead. No response to any button or charging. Will hang it on the charger for a few hours, but my optimism is gone...
OK, now it works again. I am in the screen with the colourfull stuff and the phone waits for some download.
Driver is installed on PC. Is there anything supposed to happen - the phone is still not accessible via PC, or is it?
Install Odin (search in Google 'odin samsung' and download)
Download stock firmware(android os) at www.samfw.com , after downloading you will see files like AP-M505xxxxxxx.tar.
Select, from the stock ROM AP-M305xxxxx.tar for AP in odin CSC-M305xxxxx.tar for CSC, and so forth then click start .
OK. All data will be lost, right? Is there some way to access the internal storage to rescue some files before flashing the new firmware?
Sorry to tell you that you cannot have data restored bad news for you sorry
Sorry. If you only see one file(make sure it is .tar or .tar.md5 file) after you extracted the .zip firmware, install it to the AP slot.
Any chance I could fix this issue with tools like dr.fone, UltFOne, ReiBoot?
I do not have any experiences with these - no idea if the just want to make money with desparate customers? ...
These could possibly brick your phones even more ( anyways flashing with Odin could also brick your phone). However, it in some cases can fix your device.
If you HAVE to have your data back and you don't mind paying, visit a service center and tell them: 'Hey my phone died and i HAVE to have the data back '.(I know, your warranty is expired probably, but they might still do the things for you with paying.)(if those stores closed during lockdown then I don't know any way to fix it.)
OK, another thing I have observed: The screen goes black after about 30 sec to 5 min when not charged - the shorter it was charged, the quicker the screen goes black. Buttons do nothing when screen is black. When reattached to charger, phone tries to boot and is then stuck at said screen - no button pressing needed for the phone to try to start. The longer the phone has been without charger, the longer it takes until the phone tries to boot.
Maybe it's just the battery that is dead - or would the phone with a dead battery boot normally when attached to charger?
If that is the case, open up your phone, put in a replacement battery, and try to boot up(yes, you need to. it will be a frustrating process.). Your phone could be having a faulty battery and nothing else, to cause this issue.
Im having the same problem mentioned above. The samsung service centre says to replace the motherboard which costs almost half the price of the actual phone..
Mystic_Jamdam said:
Im having the same problem mentioned above. The samsung service centre says to replace the motherboard which costs almost half the price of the actual phone..
Click to expand...
Click to collapse
Truth to be told: The guy in the repair shop opened the phone and wanted to change the battery - when he saw that water must have come into the phone, corroding the motherboard. So yeah, all data lost, but... no backup, no mercy. I now have set up a NAS for all computers and devices in our family... ;-)
If it really is a hardware problem then the quality must have been really bad.