Related
I unlocked the bootloader and flashed a custom recovery. I then rebooted the device. Now it is stuck at the bootloader (white Google logo on black background) and I can't get it to do anything else. I've rebooted it a bunch of times including with the vol + and vol - buttons held down to no avail. I've also let the battery run out and then tried to boot it up again and the same thing happens. adb nor fastboot see the device and it doesn't show up in the logs on my machine (Mint 13) as coming online at any time.
Most of the times I reboot it with the power switch it reboots to the Google logo even without me letting go of the power button. Sometimes I can get it to fully power off but I haven't figured out what combination of vol keys and reboot does that.
Anyone have any ideas what could be wrong? Any help would be much appreciated!
You are not bricked if you can still get into the bootloader.
Download the factory image from here, and flash it with fastboot. If you don't know how to do that, read this thread.
I wish I could get fastboot to see it then I could definitively flash that img.
I can't get into the bootloader and can't get fastboot or adb to see it. It's stuck at the Google logo now and when i hold the power key it reboots back to the Google logo with the unlock logo at the bottom.
Thanks for the help
You've tried holding volume down+power for 10+ seconds? That should power off the device, then hold both vol up+down down and power up
Ya I've tried to hold vol + and power for 10+ seconds and it reboots back to the Google logo even if I don't off the power key. Same happens with all the other combinations of keys being held with the power button. I can't get it to turn off now unless I let the battery die
Press and hold power till screen goes black. Then quickly press power+volume down and HOLD.
Sent from my Nexus 7
Tried that and still stuck at the Google logo. I have to go to work for a couple hours and then will hack on it when I'm back. Hope I don't have to deal with Googles rma process seeing how disorganized the rest of that company is
Sent from my HTC one s
No luck with any button combos but the vol + and power actually turned it off. All out of ideas over here. I'm thinking it really is bricked
I'm in the same spot. I can get it into recovery occasionally but once there it locks up after trying to flash or clear the cache.
I'm wondering if a contributing issue is CMR v6.0.0.6? I updated it from 6.0.0.4 that was running fine. But no fastboot or adb so that is doubtful.
This is frustrating and not a great start with this N7.
thank you
giveen said:
Press and hold power till screen goes black. Then quickly press power+volume down and HOLD.
Sent from my Nexus 7
Click to expand...
Click to collapse
this worked. you have to be fast. as soon as screen goes black release power button then quickly, very quickly repress along with vol up and down.
You will still be able to get into the bootloader! Force kill the tablet by holding the power button for ages. Then hold volume up and volume down and the power button together, which will boot to fastboot.
It looks like a CWM bug as I feared. Anyone in the same boat try here - http://forum.xda-developers.com/showthread.php?t=1782932
Nothing has worked and I've literally tried everything that those three buttons can do. Thanks again for all the help guys. Had a great time trying to resurrect it but guess it's time for it to go back home
Just as I suspected. Google puts out buggy junk once again.
I just wanted to report a similarly event. I have a rooted, unlocked Nexus 7, with TWRP recovery. I have previously rebooted without issue. Tonight I booted into bootloader mode to check something and the hit power button to choose start. I got stuck on the boot logo. After finding this thread, I started with the simplest combination and held power button until screen went dark, then added volume down and once again in bootloader. This time choosing start led to a regular system boot. It's as if the device froze and needed a hard reboot.
Sent from my SCH-I535 using Tapatalk 2
I was attempting to boot into recovery and kept getting the 'Google' logo (I am unlocked/rooted with twrp recovery). I wasn't aware that one had to be plugged in via usb in order to *not* hang....
Any way around this?
Once I plugged it in and attempted to boot into recovery it worked fine.
I had a similar issue after using the Nexus Root Toolkit to flash to nakasi 4.2 with CWM recovery - just got stuck on the nexus boot screen, flashing in a loop for over 15 minutes.
I ended up powering down the device, holding power for about 5-10 seconds - then QUICKLY holding both the power and volume up+down keys, it then went into the fastboot screen.
After it was there, plugged it into my PC.
Now, this should work for you - assuming you have all the fastboot/usb driver stuff installed.
I extracted the contents of nakasi-jop40c-factory-6aabb391.tgz into the same directory as the fastboot.exe provided by WugFresh with his Nexus Root Toolkit (google search or xda search for this if you dont have it, i dont think i can post links due to my low postcount) - typical filepath: C:\Program Files (x86)\WugFresh Development\data
By the files in there, I mean drilling down inside the tgz to where the image files were inside so that files like bootloader-grouper-4.13.img, image-nakasi-jop40c.zip etc were extracted into the directory and sitting alongside the fastboot.exe - NOT in a subfolder.
Once its all here, running flash-all.bat (this is provided by google in the nakasi-jop40c-factory-6aabb391.tgz) from the command line or by double clicking on it from explorer should kick off the process. After about 2-3 minutes, it was complete, and my Nexus then booted up within about 3 minutes after that.
Also worth noting, device remained unlocked, but I lost root/root binary
Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
pjrj said:
Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
Click to expand...
Click to collapse
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
SteadyQuad said:
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
Click to expand...
Click to collapse
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
pjrj said:
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
Click to expand...
Click to collapse
Maybe I should rephrase: the vol-up should already be pressed once the vibrate starts. For a timing-insensitive, fool-proof (no pun intended) way you can enable bootloader (like you did before: you get the Downloading... screen). Then keep vol-up and power pressed together, after 15 seconds the device reboots hard, keep both keys pressed until you see TWRP 'curtain' screen, then release.
Did you try to use the YotaFlasher Windows application to reinstall an official ROM and restore factory defaults? You can get it from here, also download a ROM for your region here.
I recently updated my Samsung Galaxy Tab A T280 to the latest firmware and I lost my root. So this afternoon I re-rooted it. Or I attempted to, anyway. Everything seemingly went fine, and I booted into TWRP just fine. I went to flash the ROM and I also selected wipe cache/davlik cache to be done as well, and tapped reboot. My device then turned off and when it started the reboot, it got stuck on the Samsung Galaxy Tab A logo screen and would not move or power off by holding the power button (I tried for a LONG time by using a rubber band to hold it down so I didn't have to, with no luck), and every other combination of buttons wouldn't do a thing, except for holding power + vol down, which made it turn off and back on, but it wouldn't finish rebooting and it just got stuck at the Samsung Galaxy Tab A logo again. So then I thought that maybe plugging it into a charger might not be a bad idea, and after holding down power + vol down again, it turned off and turned on and showed a battery with a charging symbol. I've had it plugged in for an hour and it does not show a charge or do anything except for go back to that boot logo if I unplug it from the charger and again hold down power and volume down separately.
I know it's not hard bricked because it is somewhat responsive so I think there's a chance to fix it, hopefully. I just want it to turn on and fully reboot into anything or in any way that will allow me to be able to fix the issue. My computer will not recognize the device so ADB is not an option right now unless I'm wrong.
Thanks a lot guys, I am so confused and could really use some advice.
What firmware did you install
Try to install original firmware via software "Samsung Smart Switch" on your PC with connected tablet.
I too recommend that you try installing the last firmware that you were on via Odin. Also, when you hit that screen lock issue after a firmware flash, where only the Samsung logo appears do this:
1. press and hold Home + volume up and volume down along with power button (that's all 4 buttons). Hold it there for at least 20 seconds and it should power off.
2. Once the device powers off keep holding the buttons but let go of the volume down button.
3. Once the tablet starts to power back up again release the power button and then in about 1 to 2 second release the rest of the buttons.
This should get you back into recovery. You should at least be able to restore any backup, that you should have already, on your external micro SD.
Good luck.. : )
"Chance Favors the Prepared"
the above post is 100% right. Reboot back into recovery and you'll be good to go. Also twrp has a option to reboot back to recovery so this doesn't happen, just a fyi for future knowledge. Best of luck..
You tried to flash a rom with twrp?
You need to flash stock firmware with odin.
Hi all,
I was really happy with Lineage OS 14.1 running on my Storm. Today, I decided to flash the latest nightly, just leaving me with a bricked phone.
What happens right now, is:
- the phone is stuck in a boot loop. I only see the Wileyfox logo screen with "powered by android", written on the bottom of the screen.
- occasionally, the screen becomes black and the device reboots, just to get stuck again.
- pressing vol+ and power, vol- and power makes the device reboot quicker (with or without usb attached), but it immediately gets stuck again.
- I can't even turn off the phone by holding power down for 30+ seconds -- the device keeps on rebooting over and over again
Can anybody tell me how to get out of here? Just turning of the phone would help in the first place ...
Thank you, best regards!
TheWater2 said:
I decided to flash the latest nightly, just leaving me with a bricked phone.
Click to expand...
Click to collapse
How did you flash it? I got this "update" via OTA and my phone became a soft-soft brick - everything loads normally but the touchscreen doesn't work at all.
In your case, I think, there is something wrong with bootloader (but how? in LOS updates they never touch this thing) or maybe the battery is totally discharged.
I've got 2 Storms and I've seen them stuck in endless bootloop when the battery was 0% and I tried to charge them with bad charger or low-quality cable. So maybe the battery drained while updating
~FNWL~ said:
How did you flash it? I got this "update" via OTA and my phone became a soft-soft brick - everything loads normally but the touchscreen doesn't work at all.
In your case, I think, there is something wrong with bootloader (but how? in LOS updates they never touch this thing) or maybe the battery is totally discharged.
I've got 2 Storms and I've seen them stuck in endless bootloop when the battery was 0% and I tried to charge them with bad charger or low-quality cable. So maybe the battery drained while updating
Click to expand...
Click to collapse
I sideloaded the downloaded nightly. There were no error messages in TWRP log, and the battery was almost completely full.
What can be done with a wrecked bootloader? It seems I can't even get into fastboot.
(this is my real account, was unable to post out of tapatalk yesterday)
The only way is playing with vol+ and power buttons. I entered TWRP after almost 20 attempts... It's really difficult to enter fastboot or recovery via button combinations.
Flashing LOS via TWRP doesn't touch the bootloader. You can see the contents of LOS update zip-archive - there is no bootlader file, only system and kernel (boot.img). So please try using key combinations once again.
Also, constant bootloop occurs when the touchscreen is cracked, but that's not your case
~FNWL~ said:
The only way is playing with vol+ and power buttons. I entered TWRP after almost 20 attempts... It's really difficult to enter fastboot or recovery via button combinations.
Flashing LOS via TWRP doesn't touch the bootloader. You can see the contents of LOS update zip-archive - there is no bootlader file, only system and kernel (boot.img). So please try using key combinations once again.
Also, constant bootloop occurs when the touchscreen is cracked, but that's not your case
Click to expand...
Click to collapse
Thank you very much for your feedback -- highly appreciated.
After some hours of trying, I still desperately get back to you. What exactly do you mean by "playing with vol+ and pwr buttons"? Holding them together infinitely? Pressing and releasing quickly? Holding one while pressing and releasing the other?
I still have not succeeded any further from the previous stage, unfortunately ;(
krustyzy said:
What exactly do you mean by "playing with vol+ and pwr buttons"? Holding them together infinitely? Pressing and releasing quickly? Holding one while pressing and releasing the other?
Click to expand...
Click to collapse
I can't understand exactly how to get into these modes, because I can enter them only after "playing" several times. I hold 2 keys together and then the phone vibrates and I have to release them immediately, and after that it enters fastboot or recovery. But not from the first time! Sometimes it reboots again and again.
Try "playing" and if there is no result - only service would help.
If your phone doesn't enter into fastboot or recovery it may mean two things. First - you press keys in wrong way, so "playing" would help. Second - bootloader is broken or some hardware problems (e.g. cracked touchscreen, broken pwr or volume key etc.)
I hope that's the first, and finally you will enter fastboot or recovery mode.
Also you may try plugging charger.
Entering bootloader :
Press togheter vol+ and power when you see wileyfox screen release power
Entering recovery:
Vol- and power same thing for release power....
If phone don't boot ( loop ) press and hold 30 sec or more power then press vol+ or -.
Try bootloader, booting twrp on ram then flash what you want.
Fastboot boot your_recovery.img, use twrp 3.0 or 3.1
Enjoy...
Inviato dal mio Wileyfox Storm utilizzando Tapatalk
Hi together,
thanks especially to xyz` and k4y0z for your effort and your contributions! This is amazing!
I have an Amazon Fire HD 8 (karnak) with FireOS 6.3.1.2 which I want to root, unlock and install LineageOS on.
With 6.3.0.0 on another tablet, I already performed this procedure successfully.
As k4y0z writes in https://forum.xda-developers.com/hd...nlock-fire-hd-8-2018-karnak-amonet-3-t3963496 that a hardware-change in combination with the soft-brick method could lead to a real brick rendering the device unusable, I went for the hardware method.
What I did:
1. Disconnect tablet
2. Run "bootrom-step.sh"
3. Shorten CLK to GND and at the same time connect the tablet to USB
4. I get the message to remove the short and confirm with ENTER
--> flashing occurs and I find myself in fastboot mode (the tablet also shows up when I do a "fastboot devices")
5. Run "fastboot-step.sh"
--> flashing of recovery and misc occurs, followed by a reboot
Then I see the "Amazon" logo flashing shortly and then the screen stays black. I tried pressing power and the volume-keys shortly, twice, for a long time, ... nothing happens.
If I disconnect and reconnect USB I see the "Amazon" logo flashing again. The device is not in fastboot mode, ("fastboot devices" shows no device) nor is it in adb mode ("adb devices" also shows no device).
Luckily the steps below can be performed again and the flash procedure happens again so I can always get into fastboot mode but then I'm stuck flashing the TWRP with the fastboot-step.sh...
I tried the files from karnak-3.0, karnak-3.0.1 as well as the original amonet-v2, all with the same issue.
Can anybody please shed some light here? What am I doing wrong? Is there anything else I can try or is the tablet unusable now (which I cannot believe as there is fastboot access).
I am in fact running Debian 10 on a VirtualBox on my MacBook with USB forwarding to the Virtual Machine but I'm not sure if that can be the issue as all the flashes are working just fine.
Thanks for your support!
How old is the tablet? Anything bought January or newer is potential unlock-blocked....
Thanks for your answer, Michajin.
The tablet was bought in February 2020. Does that mean I'm out of luck getting LineageOS to run on this tablet?
Would the error I am seeing fit the unlock-block? I had the feeling that all the installing went through just fine, just TWRP is not loaded correctly, right?
Thanks!
Michajin said:
How old is the tablet? Anything bought January or newer is potential unlock-blocked....
Click to expand...
Click to collapse
freddy40 said:
Thanks for your answer, Michajin.
The tablet was bought in February 2020. Does that mean I'm out of luck getting LineageOS to run on this tablet?
Would the error I am seeing fit the unlock-block? I had the feeling that all the installing went through just fine, just TWRP is not loaded correctly, right?
Thanks!
Click to expand...
Click to collapse
If the fastboot-step finishes as success you have TWRP (fastboot step is just the flashing of twrp replacing stock recovery). You should be able to hold the volume down and press the power button, this will boot the device into recovery.
Thanks, Michaejin! That did the trick. Pressing those buttons yesterday didn't help as the tablet was somehow turned on, now I disconnected and reconnected the battery and pressed VolDown + Power and got into TWRP!
Great! Thanks again!
Michajin said:
If the fastboot-step finishes as success you have TWRP (fastboot step is just the flashing of twrp replacing stock recovery). You should be able to hold the volume down and press the power button, this will boot the device into recovery.
Click to expand...
Click to collapse
freddy40 said:
Thanks, Michaejin! That did the trick. Pressing those buttons yesterday didn't help as the tablet was somehow turned on, now I disconnected and reconnected the battery and pressed VolDown + Power and got into TWRP!
Great! Thanks again!
Click to expand...
Click to collapse
You can also hold the power button for about 10 seconds to force a power down, so you should have to pull the cover off in case something goes wrong. Likely the device was stuck in preloader or bootrom.