I am stuck on the TWRP screen after I went into the Bootloader.
My problem is that the soft keys on my Nexus 4 stopped working a few months ago. How do I get out of the TWRP screen?
EDIT: Never mind. I panicked. Just held Power + Volume Down and rebooted. Sorry.
abpat2203 said:
I am stuck on the TWRP screen after I went into the Bootloader.
My problem is that the soft keys on my Nexus 4 stopped working a few months ago. How do I get out of the TWRP screen?
EDIT: Never mind. I panicked. Just held Power + Volume Down and rebooted. Sorry.
Click to expand...
Click to collapse
What do you mean soft keys don't work?
In TWRP? You should reflash the recovery, or a newer version.
The Home, Last Apps and Back soft key on my Nexus 4 stopped working a few months ago. Seems like a borked digitizer that has been plaguing a lot of Nexus 4 owners. Only that 1 cm area of the screen doesn't work.
So instead of having to pay to replace it, I decided it would make more sense to get a Gesture Control app that would allow me to use the same functions as that offered by the soft-keys, albeit anywhere on the screen. As most of these apps need a root, I started rooting my phone using the Nexus Root Toolkit.
Everything was fine until I went into FastBoot and the TWRP screen came up. While the toolkit was displaying "Waiting for device" and I foolishly clicked on one of the options on the TWRP screen and it took me into the File Directory. Now I could not find a way to get out of it as the only option seemed to be click on the "Back" soft key, which is not working on my phone. Hence the panic and the post.
Related
Ok so I just got my Nexus 7 unlocked and rooted no problem, I have done this on a few Galaxy Nexus phone without issue.
Now here is the strange part, if I adb into bootloader then select boot into recovery it works (CWM Touch) however if I manually go into the bootloader, hold volume keys and select reboot into recover it will just hang at the google screen.
I can get out of that bu holding power until the deivce reboots back to the OS.
I can do this as much as I want, from using adb into bootloader and get into recovery, but not manually. What can i try?
I have already tried flashing stock recovery, and other CWM non touch and all act the same way, what am I missing?
I had the same issue completely stock. No idea what causes it, and I've still not fixed it either.
Good to know I am not alone.
same here! even with 6.0.1.0
Sent from my Nexus 7 using xda premium
I rooted a week ago and this problem drove me nuts. I was paranoid enuff not to wanna flash anything. Within the last few days it was found that you can do the 3 button thing, get into the bootloader and select recovery ONLY if the N7 is plugged into something with a powered usb port. It seems any computer will work, and I read where one guy tried assorted ports like tvs, direct tv box, xbox, etc. These also allowed the buttons to activate bootloader & select recovery. There must be something within the port which requires power in order to get past that Google screen? It doesn't matter whether your on cwm 6.0+ or TWRP. It seems to be a hardware issue as far as I know at this point.
I read where a guy said that during a bootloop, hold power + volume down and wait, sometimes as long as 50 seconds. Eventually it has always worked for him. I've had one bootloop and didn't try that method. I just connected usb cable to the laptop, held the buttons and was in. That is a summary of what I know as of now.
Sent from my Galaxy Nexus using Tapatalk 2
I can confirm that it only works if you have USB plugged in.
Anyone able to get past the red triangle? It seems to just hang there for me
Its a bug with the early CWM Official Port i think, try TWRP Recovery
The only way I was able to get into CWM was to use ROM Toolbox or ROM Manager to boot into recovery. :\ Hangs for me while holding down volume and power.
I had rooted my 8 gig Nexus 4 and decided to go back to stock. I downloaded the correct image files from the google website and flashed them using fastboot as I have done many times before with my GN and Nexus S models.
After I flashed the files and do a re-boot, the phone just hands on the nexus (X) startup logo?
I tried booting back into recovery and I get the upside-down android with the red triangle, at this point I have tried holding the volume up key and pressing the power key, but I can't get the menu screen so I can do a factory reset??? I have tried holding the volume down and power keys, both the volume keys and power keys, but no luck getting the menu screen?
I am totally disgusted with this LG product, I NEVER had this issue with any of the previous samsung nexus products. Am I BRICKED?, any help would be appreciated please.
I even tried re-flashing the google system files again and no such luck.
If the phone turns on it isn't bricked. It also has nothing to do with it being an LG device.
Sent from my Nexus 4 using Tapatalk 2
Which recovery are you using?
Sent from my AT100 using xda app-developers app
I finally got it to go into the menu screen and did a factory reset and I am fine now. This was one of the worst ones I have worked with trying to flash back to stock. If they would have had a battery you could pull out, I think that would take care of some of the issues. Oh well, I am up and running.
Same problem. Downloaded and installed the Google Nexus 4 image and it said it installed OK, but when I restarted the phone it was stuck at the Google screen.
EDIT: Rebuilt all software on the phone and it is working OK again.
Hello everyone, I'm new in this forum and have just bricked my Nexus 7 .
I was not very happy with my Nexus 7 with JB version 4.2.1, it lagged and took long time to load apps etc. I used the Nexus 7 toolkit to unlock my bootloader, flash recovery and then tried a few custom roms. I eventually flash the official 4.1.2 firmware from google but the constant notification for firmware update annoyed me and I decided to root and get rid of the firmware update notifications by installing fotakill.apk.
But when I tried to root using the Nexus 7 toolkit, I chose the option to sideload the zip files for rooting automatically. It asked to flash my boot loader to a lower version (3.34, mine was 3.41) and afterwards it rebooted the device and eventually got stuck at a screen with these lines:
now send the package you want to apply
to the device with adb sideload <filename>
after a long time without anything happening, I suspected that things went wrong and pressed the power button for a few seconds and the device turned off. Now I cannot turn it back on, when plugged in it doesn't show the charging battery, also I cannot boot into fastboot mode by holding Volume down + Power button. The screen stays black the whole time.
I even tried to open the back power and pull the battery out and in again and try to turn on the tablet, nothing happens. I remember the battery level was like roughly 90% the last time the tablet was working, so I don't know what went wrong .
Hold power + vol down button about 30 seconds
Sent from my Nexus 7 using XDA Premium HD app
semeru said:
Hold power + vol down button about 30 seconds
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I tried that but nothing happened .
Press all buttons on the side simultaniously untill fastboot/bootloader mode appears. This should work, no matter if your device is booted or not, or soft bricked or whatever. Then: http://forum.xda-developers.com/showthread.php?t=1907796 .
If it doesn't work however (like after 30-60 seconds), then connect your nexus 7 to your PC. Go to device manager and identify your device. Does it say apx-mode or something like that? Then your device is possibly hard bricked and you might find some answers here: http://forum.xda-developers.com/showthread.php?t=1879228 .
Your should not have used rootkits. Most of these topics appear after people using toolkit. Learn to use fastboot. It's the only program you'll need for the nexus 7. Yes, it's a command line tool but at least it forces you to think before flashing. For example, it was not necessary to downgrade your bootloader. I really don't get why you did that. Also, if you want to run a stable 4.1.2 without the annoying update messages, you can, for example, flash cyanogenmod 10. It's stable, very smooth, and way better than stock.
Westervoort said:
Press all buttons on the side simultaniously untill fastboot/bootloader mode appears. This should work, no matter if your device is booted or not, or soft bricked or whatever. Then: http://forum.xda-developers.com/showthread.php?t=1907796 .
If it doesn't work however (like after 30-60 seconds), then connect your nexus 7 to your PC. Go to device manager and identify your device. Does it say apx-mode or something like that? Then your device is possibly hard bricked and you might find some answers here: http://forum.xda-developers.com/showthread.php?t=1879228 .
Your should not have used rootkits. Most of these topics appear after people using toolkit. Learn to use fastboot. It's the only program you'll need for the nexus 7. Yes, it's a command line tool but at least it forces you to think before flashing. For example, it was not necessary to downgrade your bootloader. I really don't get why you did that. Also, if you want to run a stable 4.1.2 without the annoying update messages, you can, for example, flash cyanogenmod 10. It's stable, very smooth, and way better than stock.
Click to expand...
Click to collapse
Thanks I did a search and finally found an answer. I was running fine on my N7 with PACMan and suddenly it got stuck booting up. So I booted into recovery and reflashed the ROM, and wiped dalvik and cache. When I rebooted it went to "Android is upgrading" like usual after wiping dalvik, then it got stuck there. So I rebooted again and nothing. Just a blank screen. Your suggestion of holding all the buttons down for 30-60 seconds awoke my Nexus. I'm going to wipe everything and start over.
A few months back, I broke the digitizer on my AT&T G2, and the bottom 5th of the screen stopped registering touches. Which sucks when you have on screen buttons. I was on CM11 at the time, so thankfully I was able to unlock the screen just fine and use screen rotation (combined with the Rotate app) to do almost everything I needed. One time I even did a wipe and clean install of CM11 and was able to use screen rotation to re-set up my phone to how I needed it.
Today I did a clean wipe and flashed CloudyProII 2.0 onto my phone, assuming I could do a similar set-up. Everything went well until the first screen, which has a next button at the bottom and doesn't rotate. I'm not able to pull down the menu bar, and since this is a clean install, ADB is off, and my google account isn't set up. So I decided to just reboot to recovery and re-flash CM11. Only for some reason the LG G2 button combo to reboot to recovery isn't working (maybe CloudyProII removed my custom recovery?), though the Download Mode combo is (and confirms I'm rooted still).
So now I'm stuck with a phone I can't use, and I'm sure there's an easy solution that will get me up and running again. If anyone can offer any advice, I'd be tremendously grateful!
EDIT: I was able to get into recovery and all is good now! Nevermind!
milespordeo said:
A few months back, I broke the digitizer on my AT&T G2, and the bottom 5th of the screen stopped registering touches. Which sucks when you have on screen buttons. I was on CM11 at the time, so thankfully I was able to unlock the screen just fine and use screen rotation (combined with the Rotate app) to do almost everything I needed. One time I even did a wipe and clean install of CM11 and was able to use screen rotation to re-set up my phone to how I needed it.
Today I did a clean wipe and flashed CloudyProII 2.0 onto my phone, assuming I could do a similar set-up. Everything went well until the first screen, which has a next button at the bottom and doesn't rotate. I'm not able to pull down the menu bar, and since this is a clean install, ADB is off, and my google account isn't set up. So I decided to just reboot to recovery and re-flash CM11. Only for some reason the LG G2 button combo to reboot to recovery isn't working (maybe CloudyProII removed my custom recovery?), though the Download Mode combo is (and confirms I'm rooted still).
So now I'm stuck with a phone I can't use, and I'm sure there's an easy solution that will get me up and running again. If anyone can offer any advice, I'd be tremendously grateful!
EDIT: I was able to get into recovery and all is good now! Nevermind!
Click to expand...
Click to collapse
you can always get a usb otg + mouse and us your phone like that or replace the screen
So I have a nexus 10 32gb that I got yesterday that I updated to 4.4.4 and I wanted to root it so I could get some apps that I love to use. Here's what happened:
Everything was going smoothly with nexus root toolkit. I set up adb and all of the drivers. Everything with that was working and I made sure to check nexus 10 with 4.4.4 in the drop down. I press the unlock bootloader button and the device says it's going into bootloader mode, but it just goes to a black screen. Then a message pops up saying I have to factory reset if i'm on 4.4.4, but that never shows up on the tablet, so I just hit OK. Then the device supposedly reboots, but now it's stuck in a bootloop and whenever I hold down the buttons to go into the bootloader the screen will turn black and the device will vibrate once after I hold the buttons for a while, then it tries to reboot again and gets stuck bootlooping. Then I try the factory reset method through the nexus root toolkit, but fastboot fails to see the device since I can't get it into the bootloader! It also doesn't show up as the correct device when it is bootlooping and connected to my computer.
Am I scewed if i can't get to the bootloader? I don't know what went wrong. I just got it yesterday and assumed it would be super easy to root since it's a nexus device. :'(
Any help/ suggestions would be great.
You are correct, nexus devices are super easy to root especially without a toolkit, most rooting issues I've seen on any nexus device has been due to the use of a toolkit so I would advise not to use it.
Currently you need to get into bootloader so you can flash a custom recovery with fastboot and then flash ROM of choice from there
Try adb reboot bootloader while in bootloop but I have a feeling this won't work. So if not try powering on holding volume down, even try with volume up, just keep trying button combos to get it to boot into bootloader.
For further help try here
http://forum.xda-developers.com/showthread.php?t=2670400
But keep trying to get into bootloader
Sent from my Nexus 4 using XDA Premium 4 mobile app
Try power and both volume buttons at the same time if you haven't already.
sfobrien said:
Try power and both volume buttons at the same time if you haven't already.
Click to expand...
Click to collapse
I have actually been trying that. I just let it die while it was bootlooping, so hopefully when it gets a little charge I can try to get it to go into the bootloader again. I have a feeling there's a bigger issue than that though.