Database Users

Please help! Nexus 10 stuck on google X during failed root :(

Hey guys
I tried the one-click root toolkit for mac from android rootz.
Something apparently has gone wrong during the root and I got some error messages and it didn't proceed. Next thing I know the nexus is stuck on google X logo and that's it. It won't load. I tried to recover through the recovery mode a couple of times but now I get the red warning sign when I go into recovery mode. This is only the second day I've had the nexus for. I feel like crying. Please Help

When the red sign appears press the volup down buttons and power button randomly until you get into recovery then factory reset

My 7 and 10 both did that. Just hold power until it turns off, then boot a recovery, wipe everything except system and reboot. It'll come up ok.
Sent from my Nexus 10 using Tapatalk HD

I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.)
I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd.
I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop.
I managed to get it unlocked. However, I'm unable to flash anything to straighten it out...
Any help would be great.

scooterbaga said:
I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.)
I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd.
I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop.
I managed to get it unlocked. However, I'm unable to flash anything to straighten it out...
Any help would be great.
Click to expand...
Click to collapse
Watch this video starting at the 6:30 mark.
http://www.youtube.com/watch?v=YtLvlrUDB04

bg1906 said:
Watch this video starting at the 6:30 mark.
http://www.youtube.com/watch?v=YtLvlrUDB04
Click to expand...
Click to collapse
Thanks for the info. My situation wasn't quite the same as my CWM was the real issue, which wouldn't run long enough to allow for the factory reset boot-loop solution. Kept at it and managed to get CWM to finish the individual formats/resets one at a time.
With a now bootable device, I'm off to replace the recovery... Thanks again.

HELP! Bricked Nexus 7, cannot boot into boot loader

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.

Updating to 4.3 error, no command, is my phone dead? :(

I literally just got the 4.3 OTA update. Phone was fully charged... like 98%. I went ahead and let it update. It rebooted, and it got about 75% into updating and then the icon switched to the sideways android with the red caution symbol and said "Error". I let it sit there for awhile hoping it would do something. It didn't, so I held down power to reboot. It rebooted to the same icon, but now says "No command". I did the vol up/power to get into the wipe/reboot options. I went ahead and rebooted. Every single time... I see the Google logo for like a min, then to the sad android logo w/ "No command". Now I can't even get that far, the indicator light flashes red. I've read that indicates a totally drained battery. Not sure how it can go from full charged to fully drained in a matter of minutes. However on the issue of the error and no command, is my device dead? I've never rooted it or used custom roms. I got the N4 for the pure vanilla stock experience, so I never felt rooting was needed. Any advice? Should I just call Google and request replacement?

I would try a few things first before calling Google. Sometimes the battery doesn't show its correct percentage, it's pretty common on my N4 as far as I can tell. Maybe you've just run out of battery. Let it charge for half an hour or so and then try it again.
If you can't boot to system after that, turn off your phone, press and hold volume down and power buttons at the same time for a few seconds until it boots to bootloader. If you can't boot to bootloader after doing this let it charge for more time, an hour or two.
Sometimes, after the battery has run dry completely it is really hard to turn the phone on (I've even seen this behavior on my 7 years old Nokia). One question, does a charging animation shows up when you plug your phone?

Mercado_Negro said:
I would try a few things first before calling Google. Sometimes the battery doesn't show its correct percentage, it's pretty common on my N4 as far as I can tell. Maybe you've just run out of battery. Let it charge for half an hour or so and then try it again.
If you can't boot to system after that, turn off your phone, press and hold volume down and power buttons at the same time for a few seconds until it boots to bootloader. If you can't boot to bootloader after doing this let it charge for more time, an hour or two.
Sometimes, after the battery has run dry completely it is really hard to turn the phone on (I've even seen this behavior on my 7 years old Nokia). One question, does a charging animation shows up when you plug your phone?
Click to expand...
Click to collapse
It's been charging now for a little over an hour. No animation or indication the battery may be drained other than the red indicator light when I try to go to into the boot loader. Still can't do anything. If I power it on, I see Google logo for awhile, then sad Android icon and "no command". If I try to go into bootloader, just red indicator light and black screen. All while plugged in.
I just don't understand how it went from fully charged to drained in minutes. It was plugged in for hours today. In fact I initiated the OTA update only about 20-30 min after taking it off the charger.

Unplug your device, press and hold the power and volume down buttons for a few seconds until it boots to the bootloader. Now plug your phone again and let it charge.

Mercado_Negro said:
Unplug your device, press and hold the power and volume down buttons for a few seconds until it boots to the bootloader. Now plug your phone again and let it charge.
Click to expand...
Click to collapse
Alright, it's now been charging for 3 hours. I did what you just suggested. All that happens is I see a white Google logo for about 10 seconds, then it goes black. I think the device is off at this point. Stupid question I'm sure... I can't dock my phone to my computer to get any of my data at the "no command" screen can I? It needs to be fully booted, right?

Get into recovery, wipe cache, then it "should" boot.

ksilver89 said:
Get into recovery, wipe cache, then it "should" boot.
Click to expand...
Click to collapse
Like I said above, I'm not able to. I hold down power + vol up and it just shows white Google logo then goes black.

Well hmmm. I just did power + vol down for the hell of it, and I have a menu. Selected "recovery mod" and it just went straight to the sad Android icon with "No command".
I'm not sure what to make of all the stuff I see on this menu...
https://dl.dropboxusercontent.com/u/28754710/20130730_100302.jpg

Here is a short video of what I get from that menu when trying to go into recovery...
https://dl.dropboxusercontent.com/u/28754710/20130730_100936.mp4

For the sake of simplicity, learn how to use Fastboot. You should find more than enough information in the General section.
All you need to do is run this command in bootloader mode.
Code:
fastboot format cache
Edit:
Just saw the video, press vol up + power together in the recovery to access the menu.

ksilver89 said:
For the sake of simplicity, learn how to use Fastboot. You should find more than enough information in the General section.
All you need to do is run this command in bootloader mode.
Code:
fastboot format cache
Edit:
Just saw the video, press vol up + power together in the recovery to access the menu.
Click to expand...
Click to collapse
Again... like I said before vol up + power does nothing. I can take a video if you like.
Disregard the above. Got it into recovery. I guess my pushing was off or something. I took the rigid case off and made it easier to press the vol button. Let's see what happens now.

Alright. Got into recovery, did a wipe data/factory reset, still no dice. This time it rebooted several times, Google white logo each time, then finally a sad Android icon with "No command". Guessing next step is to download it and try updating via ADB?... or just say screw it and call Google and initiate a replacement?

Alright, it is screwed. Long guide here: http://forum.xda-developers.com/showthread.php?t=2010312
Short guide:
1. You need basically 3 things, the factory image, fastboot, and nexus 4 drivers
2. Download and setup all of them.
3. Extract the factory image tgz file TWICE until you see a folder.
4. Place "fastboot" into that folder.
5. Unlock your bootloader, shift + right click inside the folder, Open command window here. Run "fastboot oem unlock" and read the agreement (it's screwed anyway), select Yes if agree.
6. Once unlocked, run "flash-all".
7. Go running around your house for 10 mins.
Warning: This operation will wipe everything in your phone, if there's any crucial data, edit flash-all.bat to remove "-w" flag, and remove userdata.img in the occam zip.
Edit:
Or probably you can just get a toolkit...

ksilver89 said:
Alright, it is screwed. Long guide here: http://forum.xda-developers.com/showthread.php?t=2010312
Short guide:
1. You need basically 3 things, the factory image, fastboot, and nexus 4 drivers
2. Download and setup all of them.
3. Extract the factory image tgz file TWICE until you see a folder.
4. Place "fastboot" into that folder.
5. Unlock your bootloader, shift + right click inside the folder, Open command window here. Run "fastboot oem unlock" and read the agreement (it's screwed anyway), select Yes if agree.
6. Once unlocked, run "flash-all".
7. Go running around your house for 10 mins.
Warning: This operation will wipe everything in your phone, if there's any crucial data, edit flash-all.bat to remove "-w" flag, and remove userdata.img in the occam zip.
Edit:
Or probably you can just get a toolkit...
Click to expand...
Click to collapse
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.

pixelbat said:
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
Click to expand...
Click to collapse
Yes, what he suggested should get you up and running again (if not, then yes your phone needs a replacement). I saw the video and the image. I'm pretty sure your system was wiped somehow and that's why you can't boot to it anymore. If what he suggested fails I can walk you through the steps to flash each factory image separately.

What would you do if the nexus 4 drivers wont install?
I have similar problem, I got the 4.3 update ota and it crashed half way through and now it gets stuck on the X logo. I was trying to follow a guide (http://forum.xda-developers.com/showthread.php?t=2010312) to install 4.3 back onto the device but failed at the first hurdle, when plugin the phone in it fails on the driver software installation - mtp usb device failed.
Is there any other way to do it?

pixelbat said:
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
Click to expand...
Click to collapse
unplug your phone. reboot into bootloader (vol down + power) but don't plug it in
downloaded the file posted in this topic from the google website.
http://forum.xda-developers.com/showthread.php?p=44088784
once you download it, extract it to a folder
then open up flash_all.bat in notepad, and it will say -w near the end. remove that (leaving it would wipe all of your data) and save the file
then run it, it will say waiting for device. plug your phone in and it will start updating

flipfamous said:
What would you do if the nexus 4 drivers wont install?
I have similar problem, I got the 4.3 update ota and it crashed half way through and now it gets stuck on the X logo. I was trying to follow a guide (http://forum.xda-developers.com/showthread.php?t=2010312) to install 4.3 back onto the device but failed at the first hurdle, when plugin the phone in it fails on the driver software installation - mtp usb device failed.
Is there any other way to do it?
Click to expand...
Click to collapse
Which driver did you try to install? Naked Drivers 0.72? What OS (Win8, Win7, etc)?
Plug your device in, go to control panel, click on Device Manager, scan for hardware changes or select the device with a yellow exclamation mark. Click on "Update driver" and search for the drivers in your PC (where you downloaded them). That should work.

Just Boot from a ubuntu live cd, install fastboot with apt-get and get started
Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta

**SOLVED** [Q] My Droid Razr M won't get past the droid eye on boot up

I apologize already if this has already been posted before, I couldn't see one that had my issues so I'm making this thread.
OK, so here is my problem and everything that I can think of that I've done to my phone.
Today I tried to restart my phone as it was getting a bit sluggish. When I did it started booting fine then the animation sound stopped while the droid eye was being put together. Now my phone will not pass the droid eye during the boot phase. I press the power and both volume buttons and after a few seconds it starts itself back up again. I do the power button and down volume buttons and it still does the same thing. I've even performed the factory reset twice and it still won't help.... And no matter what I do it keeps booting itself back up on its own.
What I've done to my phone:
I am rooted but never got the boot loader unlocked since i waited too long and the last update wouldn't allow the boot loader unlock methods anymore. I have used titanium backup app to delete some system apps for example the Verizon football one, slacker radio, and any of those useless apps that I never use. I haven't deleted anything lately and have restarted my phone many times since. I have been delaying the recent update hitting no or not now, whatever it says. I thought that I said no today on the system update as well. Even then my phone was working before I restarted it.
PLEASE I hope that there is something that I can do to fix my phone because I'm forced to use my LG Vortex again and my upgrade isn't for another year..... I don't want to buy a new one since this phone has been great and I'm almost certain that if there was a way to reinstal or flash the droid razr m OS that that would fix my issues.
Thanks in advance for your input and please know that I'm a novice with this kind of thing so you will have to explain the process to me. If i have instructions I can definitely follow them.
THANKS!

You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here http://sbf.droid-developers.org/phone.php?device=8 (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/ .

OK, so I deleted the cashe and still a no go. For the second step of getting the .3 to regain root. would it be possible to get an even earlier version so I can unlock the boot loader? Also when you say flash in RSD, what is that? I know of the AP flash from the first menu, is that something inside of Recovery menu options?
Thanks for your help!
**UPDATE**
THANKS! I was able to eventually figure it out and used the last option that you said and my phone works! Now working on getting root back. Thanks again!! But I really would like to know if I could do the same thing but with an earlier version to unlock the bootloader.

Droid Razr starting up issue
Hi guys, I am facing a weird issue with my Droid Razr and hoping pros to help me sort this out and get my phone running.
I am using Droid Razr but since last one week it is not starting up. Let me elaborate, currently it is switched off and not getting up. While starting it pass through M logo but can't go ahead for startup animation (droid eye animation). Even after leaving on that animation for entire day, it is not going ahead of that.
However, if I connect it to a wall charger (while it is off) it shows battery getting charged. It is taking a usual timing of 90 minutes for full charge.
I have important pictures and data into phone memory is there any way to recover it.
I would appreciate if you can guide me to get my phone up and running as usual.
RikRong said:
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: .
Click to expand...
Click to collapse

Changed a permission now I am stuck in endless reboot

Not sure I am posting in the right spot, but pretty sure the people that can answer are in this section.
After putting it off for months, I upgraded my 6T T Mobile converted to international to OOS 10.3.3 with the ElemetalX kernel, and xxxNoLimits 10.2. Did this several days ago, no problems. Great battery, smooth performance. Even getting 2 days with my VPN on and mock location set to "always".
I went into app ops and noticed almost every app now has "access location from media" and started going through and denying that permission for almost, if not all, the apps. I remember a couple of system apps I did that to. Google play framework being one of them, and, I think, google play services. There may have been 1 or 2 more system apps I did this with also.
I do not have a google account on my phone. I don't want to make it any easier for my pocket tracking device to track me than I have to.
I added an open source mock location app a day or so ago, not problems.
About 5 or so minutes after finishing up in app opps, I went to get the kiddo some food and looked down and noticed my phone rebooting. Now, it is in an endless boot loop.
I can hold power + up volume and get it to power down, but can't get back into TWRP recovery. Figured a quick reflash puts me back to zero and I can start over.....more carefully....but the phone is not cooperating.
I should be able to use adb and flash TWRP that way and use adb to reboot to recovery ( going to have to brush up on the how to before I start though.).
Any thoughts as to WHAT I have done and WHY I am now stuck on endless boot( w XXX animation )??
Is there an easy fix I am overlooking?
Thanks in advance,
JC

Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool
Can you get into fastboot? Then you might be able to boot TWRP again temporarily?

Thanks, that gets my into TWRP, unfortunately, my dumb ass deleted the last OTA update after I flashed it. Should be able to side load it onto the phone, then flash it via TWRP.

Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........

PattayaGlock said:
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
Click to expand...
Click to collapse
Flash twrp recovery via adb commands, you'll find tutorials on several XDA forums or YouTube