I have just now realized that, on my Android 4.3 Nexus 10, clockworkmod recovery might have been corrupted somehow, so I can't go into regular recovery mode. When I upgraded to 4.4 earlier today, it got stuck in an infinite loop of, when starting up, the screen flashes. ANYWAY...I put the nexus 10 in download mode in hopes of flashing the 4.4 image onto it. My computer isnt recognizing the tablet and instead says, "Gadget Serial." I installed Kies in hopes of, seeing as the nexus 10 is a samsung device, to get the drivers, but now it doesnt even show the device. It didnt work to say the least. XDA, can you help me out with this problem...I need the drivers.
I have the same problem. After i click update to 4.4 device restart, showed the logo Google and then starting flashing. I have no rooted device. Only pure product. With power + vol down + vol up a cant go to recovery mode. It restarts device and started flashing again. Restart Bootloader changes nothing. The flashing can be turn off only with power + vol up + vol down and set POWER OFF. I dont know what to do...
Related
Before I begin I must say I've never used an android device in my life so this is all completely new to me. The only experience I've had was rooting and installing CM or something similar to an iphone 3gs a few years ago.
I'm aware a lot of people are having problems with their nexus 7 hanging at the animated rainbow-colored X screen. I've seen the suggestion to hold power and vol up/down to get to the restore factory default settings - but that doesn't show. Mine just shuts off. I've tried going to the bootloader screen via power+vol up/down while the machine was off but nothing ever happens. The nexus just stays powered off. Also, if I hold power while it's hanging on the rainbow X, nothing happens - it doesnt even shut off. In order to turn it off I have to hold power+vol up/down.
I have not rooted or installed any ROMs on this android yet. But I do want to. I am curious if I can somehow root and flash my nexus.
If someone can point me in the right direction on how to start this from a basically dead nexus 7, please enlighten me. I've read through a few instructional threads so far but they all start off with the nexus 7 being able to fully start.
Please advise.
Thanks!
Also, pic of device manager w/ error msgs from n7:
(can't post links with under 10 posts on account, so i broke up the link. remove the asteriks (*) and replace with periods.
i42*tinypic*com/2lnj0i8*png
[Info] Guide to entering safe mode, bootloader, stock recovery
Go into recovery and choose wipe data factory reset.
sfhub said:
[Info] Guide to entering safe mode, bootloader, stock recovery
Go into recovery and choose wipe data factory reset.
Click to expand...
Click to collapse
Thanks for the link. I tried entering safe mode, didn't work
- Press/Hold Power button until Google screen shows up, RELEASE Power button
- Press/Hold VolDn until Android has booted up
The device doesn't even boot up in safe mode. Still hangs on the rainbow x.
Got into bootloader using these instructions while n7 off:
- Power+VolUp while booting to enter recovery
- You can release buttons after you see Google on screen
selected Recovery.
It turned off then on, showed the Google screen, and now shoes an android fallen over with "No command." shown underneath and am continuing..
edit: wiped and restarted. can now finally root. thanks bud.
Hi guys, skipping the introductions, I somehow unrooted my F320S (I have no idea how!) and am currently unable to use even the download mode to get back to stock ROM.
Technical details:
F320S, Korean LG G2.
Was rooted since October
Lao Hong rom (before the upgrade)
The story behind it:
1) I upgraded my phone to 4.4 on "Rom VDT-V9 Cho LG G2 4.4 Kitkat" and found myself unable to access the recovery menu. I thought it was an outdated TWRP (2.6.3.2) causing the inability to access the recovery and decided to flash CWM (6.0.4.4), but was still unable to access the recovery. Even though I had flashed CWM, it did not cause any problems as I used the phone as normal during the week up until today.
2) Wanting to remove the navigation bar, I messed with the build.prop file and caused the system to "brick", and being unable to access recovery, I went to download mode (yes this isn't the first time I bricked the G2) and went through the mobile support tool hoping to revert to stock.
3) However, I got stuck in a bootloop on the boot animation screen and read on a reply to the thread (http://forum.xda-developers.com/showpost.php?p=49822996&postcount=1794&nocache=1&z=448867873440083) to do a hard reset on the device (Press vol down and power, then press power when the LG logo shows) but the confirmation failed to appear.
4) Now, I'm stuck in an endless bootloop, unable to access recovery (as I suddenly became unrooted) or do a hard reset (hard keys do not work) and unable to use the download mode to revert to stock (endless boot loop after the upgrade completes).
edit: It seems like when I'm doing the upgrade in download mode, the phone finishes the upgrade before the mobile support tool. I don't remember this happening last time I did it...
hamisgood said:
Hi guys, skipping the introductions, I somehow unrooted my F320S (I have no idea how!) and am currently unable to use even the download mode to get back to stock ROM.
Technical details:
F320S, Korean LG G2.
Was rooted since October
Lao Hong rom (before the upgrade)
The story behind it:
1) I upgraded my phone to 4.4 on "Rom VDT-V9 Cho LG G2 4.4 Kitkat" and found myself unable to access the recovery menu. I thought it was an outdated TWRP (2.6.3.2) causing the inability to access the recovery and decided to flash CWM (6.0.4.4), but was still unable to access the recovery. Even though I had flashed CWM, it did not cause any problems as I used the phone as normal during the week up until today.
2) Wanting to remove the navigation bar, I messed with the build.prop file and caused the system to "brick", and being unable to access recovery, I went to download mode (yes this isn't the first time I bricked the G2) and went through the mobile support tool hoping to revert to stock.
3) However, I got stuck in a bootloop on the boot animation screen and read on a reply to the thread (http://forum.xda-developers.com/showpost.php?p=49822996&postcount=1794&nocache=1&z=448867873440083) to do a hard reset on the device (Press vol down and power, then press power when the LG logo shows) but the confirmation failed to appear.
4) Now, I'm stuck in an endless bootloop, unable to access recovery (as I suddenly became unrooted) or do a hard reset (hard keys do not work) and unable to use the download mode to revert to stock (endless boot loop after the upgrade completes).
Click to expand...
Click to collapse
Try this...Hold the vol down and power and have it reboot at which point hold just the power button till it turns off. At that point try the volume down power till LG logo and then just power and see if that lets you access the recovery. I fought many times with the buttons to try and get into recovery and the easiest way was always with the phone off to start with.
staticx57 said:
Try this...Hold the vol down and power and have it reboot at which point hold just the power button till it turns off. At that point try the volume down power till LG logo and then just power and see if that lets you access the recovery. I fought many times with the buttons to try and get into recovery and the easiest way was always with the phone off to start with.
Click to expand...
Click to collapse
I've been trying to get into hard reset this way for the past hour or so, but I think it might be a different key combination for the Korean models? Accessing recovery mode was vol up+power for mine too. I tried with both vol up and vol down, holding vol down all the way and releasing it after the lg logo boots, but i still have yet to find the right combination.
Thankfully I'm not fully crippled as I have my trusty S3, but I'd like to get the G2 up and running.
Just wondering if the fact that it was unsyncronized while in download mode affected anything? My G2 shut off before the download mode was at 100% complete, and I don't recall that happening the last time I used download mode to unbrick my phone.
Hi
Nexus 4 wont boot to bootloader/recovery after bootloop even with h/w button combos. Heres what happened:
It was a rooted and unlocked phone running 4.4.4. It couldnt update via OTA. So i thought of unrooting + flashing the stock but with the latest lmy48m using WUG's Nexus Root toolkit. After installation it went on to boot (4 dots flying) . It went on for 10 minutes and thought that it went to bootloop again( ive tried similar things on it before and waited for a night etc. ) . So i tried the hardware button combination (power off then Vol - & Power button combo for bootloader mode and Vol + & - & Power) to go to bootloader/recovery mode but all it does is get to the Google boot screen and go to the bootloop mode. . Then i left it to boot again overnight and its still the same.. I tried a lot of times to get to the bootloader mode and recovery mode with no hope. My pc doesnt recognise in fastboot or adb since then.. Just as MTP device in boot or android device when charging. Searched through a lot of forums but nothing worked.. Tried to remove the back cover and then pressing the button combos - still the same.. What to do next?
Please Help!
Thanks
Sriksm
ohmsree said:
Hi
Nexus 4 wont boot to bootloader/recovery after bootloop even with h/w button combos. Heres what happened:
It was a rooted and unlocked phone running 4.4.4. It couldnt update via OTA. So i thought of unrooting + flashing the stock but with the latest lmy48m using WUG's Nexus Root toolkit. After installation it went on to boot (4 dots flying) . It went on for 10 minutes and thought that it went to bootloop again( ive tried similar things on it before and waited for a night etc. ) . So i tried the hardware button combination (power off then Vol - & Power button combo for bootloader mode and Vol + & - & Power) to go to bootloader/recovery mode but all it does is get to the Google boot screen and go to the bootloop mode. . Then i left it to boot again overnight and its still the same.. I tried a lot of times to get to the bootloader mode and recovery mode with no hope. My pc doesnt recognise in fastboot or adb since then.. Just as MTP device in boot or android device when charging. Searched through a lot of forums but nothing worked.. Tried to remove the back cover and then pressing the button combos - still the same.. What to do next?
Please Help!
Thanks
Sriksm
Click to expand...
Click to collapse
there is an option of soft-brick/boot loop in toolkit. have you tried it ?
hi.. Yeah.. But the device wasnt being detected at all.. also it required the phone to boot into the bootlader/recovery which i am not able to
Did you happen to save the NRT Log from your attempted flash? Might be helpful to see.
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.
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Conrad-007 said:
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Click to expand...
Click to collapse
Hi, Conrad-007...
This is very strange - your Nexus 7 is clearly 'bootable' (sort of), with a functioning bootloader, ie., it's not hardbricked... or you wouldn't be seeing the Google logo.
In the distant past, back when I used to experiment with custom kernels on my Nexus 7, it sometimes required the POWER BUTTON+VOL DOWN buttons be pressed and held down for a good 30 seconds or more, to generate the necessary 'interrupt', and force the device into the bootloader.
My first instinct, is to suggest you may possibly have a problem with your VOL DOWN button, and maybe it's stuck somehow or not making contact.
It also occurred to me, that you might be able to access the bootloader with...
Code:
adb reboot bootloader
...or possibly...
Code:
adb reboot fastboot
...and even...
Code:
adb reboot recovery
But unfortunately, I'm pretty sure you need to be running fully booted Android or booted into a custom recovery (eg., TWRP) before you can issue ADB commands. I haven't tinkered around in this area of Android for a couple of years now, so my memory of the specifics is a little hazy.
Anyhow, here's a fairly comprehensive listing of Nexus 7 button presses/interrupts, which maybe of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
--------------------------------
Anyway, just some thoughts that might give you some clues/ideas, that may resolve your problem.
Good luck, and I hope you find something that works.
Rgrds,
Ged.
Thanks Ged for the detailed answer.
Unfortunately it seems that my Nexus is not booting complete (not finishing the booting sequence due to corrupted bootloader?) and so I cannot send to it any adb or fastboot command...
I read in the meantime that holding the VOL up button while powering up the Nexus, it will bring it in the APX mode (whatever this mean) and indeed, my computer recognize it as "APX" device.
I hope at least that this is a good sign and a first step to bring my Nexus back to life... but I have no idea what is the APX mode and what can I do in this mode to attempt to save my device...
Do you (or somebody else) have (has) an advice or tutorial for me concerning this?
Regards,
Conrad
Hi Conrad.
I'm in exactly the same situation (I've mistakenly posted a duplicate thread here https://forum.xda-developers.com/nexus-7/general/bricked-tilapia-t4005149). Let's continue here. So:
1. I spent 4 hours trying all possible button press combinations, including VERY long presses. I didn't notice any APX device or Uknown device connected to Windows. I might have missed it, you gave me hope. I will check again.
2. APX mode enables low level access to the chipset via nVidia tool nvflash. You probably came accross these threads here on xda:
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-using-t3342364
https://forum.xda-developers.com/showthread.php?t=2564615
https://forum.xda-developers.com/showthread.php?t=2455927
https://forum.xda-developers.com/showthread.php?t=2340237
I haven't so far, as I was not aware of the visibilty of the tablet in Windows. I will check again.
Well, I must have been blind not to have seen all the posts here on xda and everywhere else. I went through the threads and now I know:
1. I can see the tablet in APX mode in Windows. Possibly I could correctly set up the driver.
2. This would be totally useless, since I hadn't backed up necessary blob.
I have a new paperweight