Related
Hello,
I need some help with my Nexus 7. I had Pure AOKP (http://forum.xda-developers.com/showthread.php?t=1843201) installed on the device.
Then I installed the latest Faux Kernel Unlimited Max (http://forum.xda-developers.com/showthread.php?t=1804374).
There was no issues.
Then today when I tried to turn on Netflix the screen went black and won't turn on anymore.
Any help would be greatly appreciated
Thank you,
Everything is solved. I booted up and restored a nandroid.
Thank you
Did you try holding power, vol up and vol down all together for about 10 sec?
joep229 said:
Did you try holding power, vol up and vol down all together for about 10 sec?
Click to expand...
Click to collapse
I've tried just volume down and power. I will try all three.
My god.
Thank you sooo much. I was like "**** now I have a 250 dollar glass paperweight
joep229 said:
Did you try holding power, vol up and vol down all together for about 10 sec?
Click to expand...
Click to collapse
Did a similar thing myself; Tried to flash a ROM that i read about in Nexus 7 Dev forum that turned out NOT to be for a Nexus 7. Luckily for me, the flash failed.
Well now my new issue Is I can get to my fastboot but I can't get into recovery. It just stays at the screen that says Google and has an unlocked padlock on the bottom
joep229 said:
Did a similar thing myself; Tried to flash a ROM that i read about in Nexus 7 Dev forum that turned out NOT to be for a Nexus 7. Luckily for me, the flash failed.
Click to expand...
Click to collapse
No guarantee, but when I was stuck in a boot loop after flashing a particular ROM. That worked for me and got me into recovery, where I was able to re flash a working ROM
---------- Post added at 02:24 AM ---------- Previous post was at 02:19 AM ----------
joep229 said:
No guarantee, but when I was stuck in a boot loop after flashing a particular ROM. That worked for me and got me into recovery, where I was able to re flash a working ROM
Click to expand...
Click to collapse
Try the 3 finger thing again, but keep holding it.
Yes I lost manual recovery. I've tried many many times; with the power off I hold the volume up and the power button at the same time. As soon as I see the "little blue letters" on the left upper corner I let go. I've also tried volume up + home + power... However the cel vibrates again and does a normal system reboot.
I Odin it back to stock, factory reset...same deal.
I can reboot to recovery with Goomanager, but I can't understand why it won't manually.
Any help will be appreciated!
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
You mentioned GooManager so I'm guessing TWRP? Hold the home and vol up buttons just a little bit longer (few seconds) before you let them go.
If nothing else works try to flash OUDHS (CWM). Make sure you read the thread and follow the directions. Of course, anything you do to your phone has risk and it is your responsibility.
scott14719 said:
You mentioned GooManager so I'm guessing TWRP? Hold the home and vol up buttons just a little bit longer (few seconds) before you let them go.
If nothing else works try to flash OUDHS (CWM). Make sure you read the thread and follow the directions. Of course, anything you do to your phone has risk and it is your responsibility.
Click to expand...
Click to collapse
thanx...I tried holding the buttons a little longer but it will do a normal launch.
I already tried solving the issue by installing cwm, nice rainbows btw. It installed well but in order to use cwm I had to reboot recovery thru goo...
The manual download works though....
Sent from my SAMSUNG-SGH-I337 using xda premium
Edit
I have thus problem too. I'm just using goo manager right now.
You really need to wipe and start from scratch.
Odin stock rom, then boot to the rom, do complete device reset. Root, then load the recovery of your choice...15min procedure. Or keep trying things, and waste time. Can do this with my eyes closed as I have done this many times. Good luck.
TheAxman said:
You really need to wipe and start from scratch.
Odin stock rom, then boot to the rom, do complete device reset. Root, then load the recovery of your choice...15min procedure. Or keep trying things, and waste time. Can do this with my eyes closed as I have done this many times. Good luck.
Click to expand...
Click to collapse
I did... no dice. Thanx for your time, I appreciate it.
Sent from my SAMSUNG-SGH-I337 using xda premium
irl9000 said:
It prolly got revoked cuz u reneged on bounty?? gotta feed the gods??
sent le skyblu duex
Click to expand...
Click to collapse
Ouch!
---------- Post added at 08:54 PM ---------- Previous post was at 08:52 PM ----------
paleman27 said:
I did... no dice. Thanx for your time, I appreciate it.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Are you giving up? Because maybe you missed a step..because it WILL work.
---------- Post added at 08:57 PM ---------- Previous post was at 08:54 PM ----------
paleman27 said:
thanx...I tried holding the buttons a little longer but it will do a normal launch.
I already tried solving the issue by installing cwm, nice rainbows btw. It installed well but in order to use cwm I had to reboot recovery thru goo...
The manual download works though....
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I am telling you the boot partition is corupt. It has bs from both recoveries. Oh well. Might want to read up on odin and use the partition tools. Major sh$$ happening here. Just throwing ideas at you. I love these challenges. Wish I had the problem. Serious. I maybe wrong.
I'm wondering if there is something going on now. Normally 99.9% of these types of troubles are user error, but I've seen several people now (in the AT&T S4 forums) claiming they can not manually enter into recovery. Now I am assuming CWM hasn't been updated since the auto-loki version and I know it works correctly. So I am wondering (if there is a problem) if the problem might be with a change that was recently made to TWRP or maybe one of the new installation methods that have been developed to install CWM /TWRP? Even the people that are having the same trouble with CWM seem to have had TWRP installed first.
So, people that are having trouble please list the recovery you are using, the version, when it was flashed, and which method you used to flash it.
Or maybe it is still just all user error.
---------- Post added at 11:19 PM ---------- Previous post was at 11:08 PM ----------
paleman27 said:
thanx...I tried holding the buttons a little longer but it will do a normal launch.
I already tried solving the issue by installing cwm, nice rainbows btw. It installed well but in order to use cwm I had to reboot recovery thru goo...
The manual download works though....
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
So what recovery are you on now? I have a feeling you might be holding the power button a little to long. As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them. This is from someone that had the same problem as you (from another thread):
krypticsoul said:
I just figured it out...its still the vol up+power. I just pressed the buttons too long, so it just reboot everytime.
So basically, as soon as i see the message "recovery bootin....", i let go the buttons right away.
Click to expand...
Click to collapse
Give it a try, maybe it will work for you as well.
paleman27 said:
Yes I lost manual recovery. I've tried many many times; with the power off I hold the volume up and the power button at the same time. As soon as I see the "little blue letters" on the left upper corner I let go. I've also tried volume up + home + power... However the cel vibrates again and does a normal system reboot.
I Odin it back to stock, factory reset...same deal.
I can reboot to recovery with Goomanager, but I can't understand why it won't manually.
Any help will be appreciated!
Click to expand...
Click to collapse
Have you tried a normal reset while holding volume and home. This is what I do since I am to lazy to take the extra steps and use Goo. Been working on extended power menu for odex'd rom but I am doing something wrong and can't get it to work.
Tapped from the Shear Galaxy Near You!
I used motochopper and running the latest version of twrp. I can boot just fine using goo manager and once I'm in I have no problem at all flashing files or making a back ups. So I believe it may be something wrong with twrp recovery.
waternut13134 said:
I used motochopper and running the latest version of twrp. I can boot just fine using goo manager and once I'm in I have no problem at all flashing files or making a back ups. So I believe it may be something wrong with twrp recovery.
Click to expand...
Click to collapse
When you try to manually boot into recovery are you holding the "power", "volume up", and 'home key' until you first feel the phone vibrate and then immediately release the "power" button but continue to hold the other button until the first splash screen and then let them go. I think a lot of people are holding the power button too long or the other buttons not long enough.
scott14719 said:
When you try to manually boot into recovery are you holding the "power", "volume up", and 'home key' until you first feel the phone vibrate and then immediately release the "power" button but continue to hold the other button until the first splash screen and then let them go. I think a lot of people are holding the power button too long or the other buttons not long enough.
Click to expand...
Click to collapse
You sir are correct! I just tried it and it works. Kinda feel stupid now. Thank you so much!
seems so complicated... try just volume up.
For mine (ATT 1337, on OUDHS Recovery (cwm))
if your phone is on and while the screen is on, just hold power and select reboot. as soon as it vibrates, press and hold volume up (just volume up, nothing else, maybe wait till custom firmware padlock screen shows up), and wait for the blue text at the top left of the screen... let go vol up.
if for some reason u r frozen. press power (just keep holding) til it forces reboot, then after vibrate (or maybe padlock if its too soon), press n hold just the volume up.
I would restore via KIES instead of using ODIN,
It will reset everything, just like from factory.
I've had this happen to me several times while playing around with flashing. Basically (without fail in my experience), hold power+volume up+home as you'd normally do until you see the booting recovery message and let go. It will do one of two things - boot into recovery- or - restart and vibrate-. If it restarts and vibrates, immediately hold power+volume up+home until the booting recovery message pops up again and let go. It should then boot into recovery and you shouldn't have trouble in subsequent attempts.
It took me a while to figure this out and I actually thought I had permanently bricked my phone as the phone wouldn't boot and I couldn't get into recovery. Hope this helps.
Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
scott14719 said:
I'm wondering if there is something going on now. Normally 99.9% of these types of troubles are user error, but I've seen several people now (in the AT&T S4 forums) claiming they can not manually enter into recovery. Now I am assuming CWM hasn't been updated since the auto-loki version and I know it works correctly. So I am wondering (if there is a problem) if the problem might be with a change that was recently made to TWRP or maybe one of the new installation methods that have been developed to install CWM /TWRP? Even the people that are having the same trouble with CWM seem to have had TWRP installed first.
So, people that are having trouble please list the recovery you are using, the version, when it was flashed, and which method you used to flash it.
Or maybe it is still just all user error.
---------- Post added at 11:19 PM ---------- Previous post was at 11:08 PM ----------
So what recovery are you on now? I have a feeling you might be holding the power button a little to long. As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them. This is from someone that had the same problem as you (from another thread):
Give it a try, maybe it will work for you as well.
Click to expand...
Click to collapse
YAY!!!!!!! BINGO!!!! "As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots".
A world of thanx!
kennyglass123 said:
Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
Thank you for moving the thread; I have had much better response here! I even got my problem solved! :good:
EDIT. Thanx for getting rid of that clown.
So .... I flashed the mantaray-lrx21p image from Nexus Factory Images on my Nexus 10 (16GB Wifi) and now it's stuck in a bootloop.
No problem, I thought, I can get into recovery and fix it, right? Maybe do a wipe and try again? Yeah, not so fast. I get the bootloader screen, but the only option is 'Start' which just boots into the system that bootloops.
That's OK, I'll just use fastboot to wipe it. Nope. Fastboot doesn't detect a device.
I've tried both ADB and fastboot on Mac & Linux. Same issue (neither fastboot nor adb detect a device).
Ideas?
Observations
In case you think I'm just being impatient, it has been doing the boot animation for about 25 minutes now.
It doesn't like to stay off. If I hold the power button for 10 seconds it turns off, but it turns itself back on in about 5 seconds.
If I power it on while holding the volume button closer to the power button, I can get into a half-assed bootloader ... meaning that I can only push the power button again to 'Start'. I cannot cycle through the options with the volume buttons.
During the mentioned (half-assed) bootloader screen, fastboot does not detect a device.
During the boot animation, adb does not detect a device.
copolii said:
So .... I flashed the mantaray-lrx21p image from Nexus Factory Images on my Nexus 10 (16GB Wifi) and now it's stuck in a bootloop.
No problem, I thought, I can get into recovery and fix it, right? Maybe do a wipe and try again? Yeah, not so fast. I get the bootloader screen, but the only option is 'Start' which just boots into the system that bootloops.
That's OK, I'll just use fastboot to wipe it. Nope. Fastboot doesn't detect a device.
I've tried both ADB and fastboot on Mac & Linux. Same issue (neither fastboot nor adb detect a device).
Ideas?
Observations
In case you think I'm just being impatient, it has been doing the boot animation for about 25 minutes now.
It doesn't like to stay off. If I hold the power button for 10 seconds it turns off, but it turns itself back on in about 5 seconds.
If I power it on while holding the volume button closer to the power button, I can get into a half-assed bootloader ... meaning that I can only push the power button again to 'Start'. I cannot cycle through the options with the volume buttons.
During the mentioned (half-assed) bootloader screen, fastboot does not detect a device.
During the boot animation, adb does not detect a device.
Click to expand...
Click to collapse
The reason starts the only option is because your only holding volume up when going into fastboot. Hold power and volume up AND DOWN. All at the same time. Trust me I had the same issue but googling helped me find out you gotta hold both buttons
Sent from my VS980 4G
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
supermamie said:
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
Click to expand...
Click to collapse
I launched a 3rd flash while I downloaded the sdk and this one worked...
Absolutely no idea why.
I finally got it to boot.
boot into bootloader (hold vol-up+vol-down+power)
choose reboot bootloader
choose shutdown
turn it back on
Seems like it needed to be shut completely off not just rebooted after the flash. Perhaps a reboot maintains weird memory fragments or something? Crazy talk, I know.
Edit: you shouldn't have to wait long to see if it works. Mine jumped to the "Upgrading apps ..." screen straight away.
The very first boot on my n7 and n10 took about 20 min, after that they have normal boot time, I believe this may have something to do with encryption but never bothered to check as I just did something else while it booted
Side note, the n9 has an initial boot time of at least 5-10 min (can't recall but it took forever it felt like) and this is optimized hardware for the software so no surprise that there is a huge long boot time on the first go
Also I flashed both manually erasing all partitions first through fastboot then flashing each one individually... Just another side note
supermamie said:
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
I launched a 3rd flash while I downloaded the sdk and this one worked...
Absolutely no idea why.
Click to expand...
Click to collapse
Ive tried to connect to the device in adb, fastboot, I can only get it to adb sideload mode.
Sideloading gives the message Wrong footer instalation aborted.
How did you manage to flash the image? All drivers did install properly it seems.
Boot loop
thedarksavant said:
I finally got it to boot.
The same was happening to me, after unlocking it it began to loop, even after I wipe it was still looping.
I followed your steps of going into reboot recovery then power off. -- issue resolved!!
Thanks!
******
Click to expand...
Click to collapse
Hi
I flashed bootloader and modem and then my phone got stuck at Samsung Galaxy S7 Edge logo with Recovery not seandroid enforcing at the top.
Power + home + vol down reboot, but holding do not enter download mode. Power+home+vol down and when reboot, then up does not enter recovery.. Anyone know what to do?
Thanks in advance
hold the power + volume down to reboot it and as soon as the screen goes off click the home + volume down..
if you still having trouble try to connect with the laptop with volume up as you should hear the connection sound on the laptop and help you to time it better
Hi,
I tried to flash the latest BL to my phone and got stuck at the splash screen. (Samsung Galaxy S7 Edge, powered by android).
Now, I can't go to download mode or the recovery.
---------- Post added at 01:04 PM ---------- Previous post was at 12:41 PM ----------
halitusta said:
Hi,
I tried to flash the latest BL to my phone and got stuck at the splash screen. (Samsung Galaxy S7 Edge, powered by android).
Now, I can't go to download mode or the recovery.
Click to expand...
Click to collapse
I fixed it, what I did was Hold Vol - Home and Power key constantly. It rebooted few times again in the splash screen. And then it took me directly to recovery. I updated bootloader again, put a new recovery. Everything is back to normal. Man, I was worried.
halitusta said:
Hi,
I tried to flash the latest BL to my phone and got stuck at the splash screen. (Samsung Galaxy S7 Edge, powered by android).
Now, I can't go to download mode or the recovery.
---------- Post added at 01:04 PM ---------- Previous post was at 12:41 PM ----------
I fixed it, what I did was Hold Vol - Home and Power key constantly. It rebooted few times again in the splash screen. And then it took me directly to recovery. I updated bootloader again, put a new recovery. Everything is back to normal. Man, I was worried.
Click to expand...
Click to collapse
I LOVE YOU
i thought i ****ed up my phone but holding volume down home and power key constantly worked.
u the man mate.
Hi! I'm having the same problem, but also interested in how do you update the bootloader and put a new recovery, and which ones
Thanks in advance
halitusta said:
Hi,
I tried to flash the latest BL to my phone and got stuck at the splash screen. (Samsung Galaxy S7 Edge, powered by android).
Now, I can't go to download mode or the recovery.
---------- Post added at 01:04 PM ---------- Previous post was at 12:41 PM ----------
I fixed it, what I did was Hold Vol - Home and Power key constantly. It rebooted few times again in the splash screen. And then it took me directly to recovery. I updated bootloader again, put a new recovery. Everything is back to normal. Man, I was worried.
Click to expand...
Click to collapse
halitusta said:
Hi,
I tried to flash the latest BL to my phone and got stuck at the splash screen. (Samsung Galaxy S7 Edge, powered by android).
Now, I can't go to download mode or the recovery.
---------- Post added at 01:04 PM ---------- Previous post was at 12:41 PM ----------
I fixed it, what I did was Hold Vol - Home and Power key constantly. It rebooted few times again in the splash screen. And then it took me directly to recovery. I updated bootloader again, put a new recovery. Everything is back to normal. Man, I was worried.
Click to expand...
Click to collapse
having the same problem here, i did all what u suggested but no luck. tried the vol - home button and constantly clicking the power button but still no luck. i have on the screen " Set warranty Bit: Kernel
anyone help guys. any help would be very much appreciated. thanx in advance
halitusta, thank you so much. Thought i had bricked my new phone
can only access system revovery and factory test mode, how can i access recovery mode? ive tried Vol+power keys it flashes the zte screen then goes to system recovery or just goes to start up. Z839 7.1.1 Blade Vantage....it is frp locked, bootloader locked cant access developer opts and dial short cuts wont work either and no root permission....any ideas
64GB USA XT1575.
Unlocked bootloader. Loaded TWRP 3.1.1.
Loaded AICP 10/8/2017, and OpenGapps mini.
No root; No Magisk.
Functioned fine.
Did dirty upgrade to a November version.
Phone had been glitch since in function, and reboots.
It has deteriorated to reboots and never finishes animation.
I cannot get the phone off, then to bootloader.
If I disconnect battery, wait a few hours, and reconnect:
I cant connect the battery and quickly hold power and vol down and get bootloader.
I get warning Boot loader unlocked screen, then an AICP loading animation that never ends.
If I hold in power button, it reboots to the same scenario.
Even holding in power/vol down during process wont get to bootloader .
What would deteriorate phone into not being able to get into bootloader, but phone is not hard-bricked with no boot at all?
I need to get to TWRP so I can fully wipe this phone and whatever is causing all of this.
Any ideas?
Do we have an unbrick "loader" for the sdcard like the XT1572 folks do?
IDK about the unbrick tool, but I have had a constant boot up, turn the phone off and it quickly reboots again. For me what worked is all about timing! I power the phone off and as soon as the screen powers down I hold power and volume down until bootloader screen! It takes some time to get it right on time, but it's worked for me in the past on my moto x pure edition. I'm stock 7.0 now but the issues occurred running custom roms, so really the same situation. Good luck and hope you get it. And I hope you have a backup to restore once you get into twrp?!?!
"If I hold in power button, it reboots to the same scenario.
Even holding in power/vol down during process wont get to bootloader ."
On bootloop:
Hold power key only, when screen goes black - hold vol- only. It should go to BL screen.
AICP doesn't work at Nougat modem(radio/baseband).
You need to flash MM modem or reflash full Stock Nougat and stay on it.
@hometech99
dzidexx said:
"If I hold in power button, it reboots to the same scenario.
Even holding in power/vol down during process wont get to bootloader ."
On bootloop:
Hold power key only, when screen goes black - hold vol- only. It should go to BL screen.
AICP doesn't work at Nougat modem(radio/baseband).
You need to flash MM modem or reflash full Stock Nougat and stay on it.
@hometech99
Click to expand...
Click to collapse
I never went ota 7.0, root, or Magisk.
On bootloop:
Hold power key only, when screen goes black - hold vol- only. It should go to BL screen.
/It always work, sometimes it's hard to find the right moment - vol-/
Go to twrp, wipe all and restore or flash last good version.
---------- Post added at 06:45 AM ---------- Previous post was at 06:44 AM ----------
@hometech99
Why didn't you ask in aicp thread?
---------- Post added at 06:49 AM ---------- Previous post was at 06:45 AM ----------
Here you wrote that you updated to stock N:
https://forum.xda-developers.com/showpost.php?p=75009801&postcount=129
AICP doesn't work at N modem.
dzidexx said:
On bootloop:
Hold power key only, when screen goes black - hold vol- only. It should go to BL screen.
/It always work, sometimes it's hard to find the right moment - vol-/
Go to twrp, wipe all and restore or flash last good version.
Not working..tried it many times.
---------- Post added at 06:45 AM ---------- Previous post was at 06:44 AM ----------
@hometech99
Why didn't you ask in aicp thread?
This is beyond an AICP problem....it might be caused by AICP, but not getting into bootloader is even lower level problem.
---------- Post added at 06:49 AM ---------- Previous post was at 06:45 AM ----------
Here you wrote that you updated to stock N:
https://forum.xda-developers.com/showpost.php?p=75009801&postcount=129
AICP doesn't work at N modem.
Click to expand...
Click to collapse
I have 3+ of these phones. MY personal one works fine . This is a different unit of mine with this problem that was working fine before.
Fixed--one of the issues (others reported also) with later AICP is cant charge phone. We had that issue with this phone also.
On a hunch, I went to my Moto X Pure graveyard basket, and took out another battery, and put it in.
Viola--I can get into boot loader. The original battery must have deep-cycled so bad, it was dead, and even plugged in, cant get to bootloader.