boot loader is unlocked
booted into fastboot
returning to stock image 5.0 LRX21M bye running flash-all.bat
upon completing I wait for reboot and it takes a 5.0 update.
and then I go to "about" in settings menu to encourage the 5.1.1 update.
I reboot to bootloader and "fastboot boot root.img" and then after reboot installed superSU via adb sideload. When I go to update the binarys from with superSU it fails and says reboot and try again. When it goes to reboot it gets stuck on the 4 spinning colored balls.
I tried using WinDroid Universal Android Toolkit v2.4 instead of root.img and performed same steps with same results. Can someone throw me a friggin bone. lol
solved: do not update superSU binaries and remove "google account" for device and add it again. the reason I remove and login re-instate google account is because I would attempt to install apps from play store and they would stay stuck in "installing" and never complete.
rp201 said:
boot loader is unlocked
booted into fastboot
returning to stock image 5.0 LRX21M bye running flash-all.bat
upon completing I wait for reboot and it takes a 5.0 update.
and then I go to "about" in settings menu to encourage the 5.1.1 update.
I reboot to bootloader and "fastboot boot root.img" and then after reboot installed superSU via adb sideload. When I go to update the binarys from with superSU it fails and says reboot and try again. When it goes to reboot it gets stuck on the 4 spinning colored balls.
I tried using WinDroid Universal Android Toolkit v2.4 instead of root.img and performed same steps with same results. Can someone throw me a friggin bone. lol
solved: do not update superSU binaries and remove "google account" for device and add it again. the reason I remove and login re-instate google account is because I would attempt to install apps from play store and they would stay stuck in "installing" and never complete.
Click to expand...
Click to collapse
I have the same issue - I have to sideload the SuperSU and then the binary update fails, and I get stuck on the 4 spinning colored balls. Can you please explain what you did to resolve? Many Thanks!
Please clarify. Stuck at returning to stock or rooting 5.1.1? My post does say not to update binaries at the end under "solved:"
rp201 said:
boot loader is unlocked
booted into fastboot
returning to stock image 5.0 LRX21M bye running flash-all.bat
upon completing I wait for reboot and it takes a 5.0 update.
and then I go to "about" in settings menu to encourage the 5.1.1 update.
I reboot to bootloader and "fastboot boot root.img" and then after reboot installed superSU via adb sideload. When I go to update the binarys from with superSU it fails and says reboot and try again. When it goes to reboot it gets stuck on the 4 spinning colored balls.
I tried using WinDroid Universal Android Toolkit v2.4 instead of root.img and performed same steps with same results. Can someone throw me a friggin bone. lol
solved: do not update superSU binaries and remove "google account" for device and add it again. the reason I remove and login re-instate google account is because I would attempt to install apps from play store and they would stay stuck in "installing" and never complete.
Click to expand...
Click to collapse
rp201 said:
Please clarify. Stuck at returning to stock or rooting 5.1.1? My post does say not to update binaries at the end under "solved:"
Click to expand...
Click to collapse
Mine was sticking on the reboot after the binary update failed on root 5.1.1. I found a workaround on another post where booting a "skiproot" img resolves the issue if it gets stuck on the reboot...
Click here post #23 by mskip
[email protected] said:
Mine was sticking on the reboot after the binary update failed on root 5.1.1. I found a workaround on another post where booting a "skiproot" img resolves the issue if it gets stuck on the reboot...
Click here post #23 by mskip
Click to expand...
Click to collapse
The download link to the files on that page doesn't work, do you know the new location?
dharbinja said:
The download link to the files on that page doesn't work, do you know the new location?
Click to expand...
Click to collapse
No idea, that link was working just the other day...
Related
Hello all,
I initally used the Wugz root toolkit to unlock, install drivers and root my device. I flashed CWM and a ROM. Once I flashed the ROM, it wouldn't boot, but would flash the google logo, go black, then go to the google logo and open up CWM again.
I searched for backups, they were gone. So I tried a few things and now I can't even get to CWM.
All I can get to is the Recovery menu and Stock Recovery. My computer won't recognize the device in adb fastboot but will recognize it when I put it into sideload from the stock recovery.
I've tried to flash the 4.1.2 and 4.2.2 images from the Google developer website but when it verifies the installation package it says installation aborted.
Is there any way I can fix this just from the Stock Recovery sideload? Is this hopelesss?
Take a look at this THREAD
Nico_60 said:
Take a look at this THREAD
Click to expand...
Click to collapse
Thanks. I did try this first, I must have messed it up somewhere. I'll try it again. Not sure if it'll work without the device being recognized under fastboot.
To know if it's recognized type "fastboot devices" but if the driver were already installed it must be ok
Whew got it to work. Thanks.
Hope someone can help. I've tried updating my Nexus 4 to KitKat, and think I've borked it, as it is now stuck in the boot screen with the four coloured spinning circles.
Here's what I did:
Downloaded the 4.4 KRT16O Factory Image for Nexus 4 from Google Developers site
Unlocked the Bootloader on my Nexus 4
Went to Android SDK manager folder and Platform Tools.
Extracted the Factory Image to this folder
Enter comand prompt
Typed fastboot devices to ensure the phone is visible
Typed flash-all.bat
The phone re-boots, I get the spinning circles and nothing more.
I can get back to fastboot, and have tried reinstalling the Jelly bean image, but this also hangs at the boot screen. I've tried both Images and neither seem to get past their relevant boot screens. In both instances I can get back to fastboot.
I haven't installed a custom recovery
What to do?
I'd be grateful of any help.
dreamypuma said:
Hope someone can help. I've tried updating my Nexus 4 to KitKat, and think I've borked it, as it is now stuck in the boot screen with the four coloured spinning circles.
Here's what I did:
Downloaded the 4.4 KRT16O Factory Image for Nexus 4 from Google Developers site
Unlocked the Bootloader on my Nexus 4
Went to Android SDK manager folder and Platform Tools.
Extracted the Factory Image to this folder
Enter comand prompt
Typed fastboot devices to ensure the phone is visible
Typed flash-all.bat
The phone re-boots, I get the spinning circles and nothing more.
I can get back to fastboot, and have tried reinstalling the Jelly bean image, but this also hangs at the boot screen. I've tried both Images and neither seem to get past their relevant boot screens. In both instances I can get back to fastboot.
I haven't installed a custom recovery
What to do?
I'd be grateful of any help.
Click to expand...
Click to collapse
Boot in bootloader, then select "recovery". When you get to an android laying on his back, press "Power+Volume UP" at the same time (don't hold. Just press). A menu should appear. Select "Data wipe/ Factory reset", and reboot.
abaaaabbbb63 said:
Boot in bootloader, then select "recovery". When you get to an android laying on his back, press "Power+Volume UP" at the same time (don't hold. Just press). A menu should appear. Select "Data wipe/ Factory reset", and reboot.
Click to expand...
Click to collapse
I had a thread yesterday on the same topic. http://forum.xda-developers.com/showthread.php?p=47490462#post47490462
hope that helps.
This may work
Hi, I encountered the same problem. I had the LTE baseband radio which was not being accepted in the flash-all.bat and it kept giving me in error in install and wont complete. I used nexus root tool kit to flash the radio img extracted from the 4.4 occam file using the advanced utilities in tool kit. After that I used the tool kit again and again to install the 4.4 but it kept getting stuck in the boot animation even after successful installs. I gave up and as a last resort tried the flashall.bat again. It went through smoothly since it detected the new radio and I let it hang in there for 10-15 mins in the boot animation and viola ! I had it installed.
Hope part of this may work for you.
---------- Post added at 01:40 PM ---------- Previous post was at 01:35 PM ----------
priyab said:
Hi, I encountered the same problem. I had the LTE baseband radio which was not being accepted in the flash-all.bat and it kept giving me in error in install and wont complete. I used nexus root tool kit to flash the radio img extracted from the 4.4 occam file using the advanced utilities in tool kit. After that I used the tool kit again and again to install the 4.4 but it kept getting stuck in the boot animation even after successful installs. I gave up and as a last resort tried the flashall.bat again. It went through smoothly since it detected the new radio and I let it hang in there for 10-15 mins in the boot animation and viola ! I had it installed.
Hope part of this may work for you.
Click to expand...
Click to collapse
Also delete your old folder of ADB, download a new one and reextract. Unzip the tar>tar directly in platform tools folder. Good luck
Follow this i too had the same prob bt got it resolved through this method. jst keep ur phone on bootloader/fastboot mode.. n run this toolkit
http://forum.xda-developers.com/showthread.php?t=2531374
Sent from my Nexus 4 using xda app-developers app
Just search the forum next time this problem is on every page and on every page and thread there is a solution...... You are not the first but hope you get it fixed
Install a custom recovery
clockwork or twrp
Installed 4.4.1 via TWRP this morning, but it is stuck in reboot. Just keeps doing the colliding circles!
Tried rebooting a couple of times. Can get to fastboot, But device isn't seen by adb, and fastboot only shows start (no recovery option)
Any ideas at this point?
RedBullet said:
Installed 4.4.1 via TWRP this morning, but it is stuck in reboot. Just keeps doing the colliding circles!
Tried rebooting a couple of times. Can get to fastboot, But device isn't seen by adb, and fastboot only shows start (no recovery option)
Any ideas at this point?
Click to expand...
Click to collapse
I would recommend flashing the 4.4 stock factory image from here in fastboot mode. Then once your device is booting up properly again I would recommend taking a look at this guide to properly install the 4.4.1 update.
You MUST either side load or safer still, un-root(if rooted) and flash stock recovery and sideload and then re-flash custom recovery and re-root if needed.
If you are able to get to fastboot:
Fastboot flash recovery recovery.img ( use stock)
Fastboot reboot-bootloader
go into to stock recovery - wait for dead droid, one you see him, go into recovery by holding volume+ and power at same time
follow the orange instructions to sideload via adb - which should now work
reboot and validate all is well
reboot into bootloader and re-flash your custom recovery and root (if needed)
Enjoy.
planet_x69 said:
You MUST either side load or safer still, un-root(if rooted) and flash stock recovery and sideload and then re-flash custom recovery and re-root if needed.
If you are able to get to fastboot:
Fastboot flash recovery recovery.img ( use stock)
Fastboot reboot-bootloader
go into to stock recovery - wait for dead droid, one you see him, go into recovery by holding volume+ and power at same time
follow the orange instructions to sideload via adb - which should now work
reboot and validate all is well
reboot into bootloader and re-flash your custom recovery and root (if needed)
Enjoy.
Click to expand...
Click to collapse
Thanks, I eventually got it. I was really puzzled that I couldn't select recovery from the bootloader. All set now though, thanks!
I hae also updated to 4.4.2 but now my N10 is stuck at the Google start page. Please help?
jalize said:
I hae also updated to 4.4.2 but now my N10 is stuck at the Google start page. Please help?
Click to expand...
Click to collapse
If you mean stuck at boot animation, then I suspect you used TWRP to flash?
I found that TWRP was not able to clear caches, so I use CWM instead. Worked like a champ...
RedBullet said:
If you mean stuck at boot animation, then I suspect you used TWRP to flash?
I found that TWRP was not able to clear caches, so I use CWM instead. Worked like a champ...
Click to expand...
Click to collapse
No I used the adb sideload command for the OTA. That all went well but now I'm stuck at the google page even before the animations begin!
jalize said:
No I used the adb sideload command for the OTA. That all went well but now I'm stuck at the google page even before the animations begin!
Click to expand...
Click to collapse
Hold volume up and power to get it to recycle, and immediately hold all three buttons down to get to bootloader. Try clearing your caches from recovery
RedBullet said:
Hold volume up and power to get it to recycle, and immediately hold all three buttons down to get to bootloader. Try clearing your caches from recovery
Click to expand...
Click to collapse
Tried that already, still stuck at Google page before animations. Everything is stock on this tablet with root.
jalize said:
Tried that already, still stuck at Google page before animations. Everything is stock on this tablet with root.
Click to expand...
Click to collapse
Hi,
Try flashing it fresh stock again, factory reset your device from recovery, download the stock image file from here, untar it, then unzip the zip inside the tar and you'll get some files (.img). Copy those files to your fastboot folder and then open a cmd there. (Guessing that you're using Windows)
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
If you're using Linux, do the same, but instead of only fastboot use:
Code:
sudo ./fastboot
Then boot it. I had the same problem when I updated mine to 4.4.1, but I did one thing a little different... Instead of fully "stocking" it again, I flashed back 4.3, flashed 4.4 OTA and then let it boot, without wiping my data, after all it was running like this before. Worked. But as I'm unsure of your situation I think it's more secure and easier to fully stock it again.
Hope this helps,
~Lord
PS.: Remember to put your device in fastboot mode!
Hopefully someone can help me here.
I have the N10 and it is rooted. I flashed the stock recovery and flashed the stock kernel.
So I should have been pretty much stock cause I had the 4.4.4 factory image on it except it was unlocked.
So then I let it do the OTA for lollipop.
When it rebooted into recovery it got about 1/3 and then hit an error (just said error).
Now I can only get it to the recovery screen and the reboot Mode Flag is 'Recovery'
The only thing I can do at that point is hit the power button and it reboots to recovery with a "No Command" error.
Help please!
EDIT: The thing finally booted up on it's own. Should I leave it alone or try to take the OTA update again?
sl2222 said:
Hopefully someone can help me here.
I have the N10 and it is rooted. I flashed the stock recovery and flashed the stock kernel.
So I should have been pretty much stock cause I had the 4.4.4 factory image on it except it was unlocked.
So then I let it do the OTA for lollipop.
When it rebooted into recovery it got about 1/3 and then hit an error (just said error).
Now I can only get it to the recovery screen and the reboot Mode Flag is 'Recovery'
The only thing I can do at that point is hit the power button and it reboots to recovery with a "No Command" error.
Help please!
EDIT: The thing finally booted up on it's own. Should I leave it alone or try to take the OTA update again?
Click to expand...
Click to collapse
Same for me. I'm trying to even manually flash the factory image, but it will not detect fastboot. I'm trying to research this now. The device just keeps restarting itself over and over into No Command.
IT Rider said:
Same for me. I'm trying to even manually flash the factory image, but it will not detect fastboot. I'm trying to research this now. The device just keeps restarting itself over and over into No Command.
Click to expand...
Click to collapse
Hi, I have exactly the same problem after installing Android 5.0 OTA. Please post a solution here if you find it. Thanks!
I didn't try the OTA again. I installed Lollipopalooza from this thread...
http://forum.xda-developers.com/showthread.php?t=1998585
No problem with it so far
sl2222 said:
I didn't try the OTA again. I installed Lollipopalooza from this thread...
http://forum.xda-developers.com/showthread.php?t=1998585
No problem with it so far
Click to expand...
Click to collapse
But I cannot flash any rom as none of ADB commands can be run (device is not connected, though I connected it with OEM cable). I tried factory reset but it didn't help.
Just wanted to share what worked for me after the OTA update failed and flashing stock images didn't work. Put the tablet in fastboot. Installed stock image, tablet wouldn't boot. Restarted went into recovery got the android on its back with the red x coming out of it (did not say bad command at thia point). I presses volume up and power at the same time on this screen. Cleared cache and rebooted then the tablet booted up.
I cannot believe companies still get away with this inadequate device "killing" type of software. Did no-one at the company do any testing before release?????
Rant over, onto solution - for me anyway.
The issue I had was that I could not get ADB to be of any use so switched to fastboot. Should have used fastboot from the getgo. Hohum.
So, into recovery with android on it's back with red triangle and reboot into fastboot.
Connect N10 to PC with USB cable.
Downloaded "Minimal ADB and Fastboot"(MAF)
Downloaded Lollipop for Nexus 10 - image-mantaray-lrx21p.zip and saved to c: drive (this saves loads of typing at command prompt)
File path for update is c:\image-mantaray-lrx21p.zip
Open MAF and ensure folder path points to your MAF install folder..
At command prompt type fastboot update c:\image-mantaray-lrx21p.zip
If you want to wipe device prior to update then type fastboot -w update c:\image-mantaray-lrx21p.zip
This may take a while so go make a drink - or something.
If all goes well, mine did, you should eventually be presented with the lollipop opening screen and a working device.
Just finally got it working!
ROM updates from ADB Sideload or Fastboot failed every time for different reasons.
What I had to do is to flash custom recovery (latest TWRP) with "fastboot flash recovery <recovery.img>" command.
From TWRP flashing the official ROMs also failed. But flashing Lollipopalooza as sl2222 suggested finally succeeded.
Thanks for all the help!
I am having a difficult time rooting my Nexus Player on Marshmallow 6.0 MRA58N
I select the "Root" option and it pushes 3 files to my Nexus Player. Then it boots into TWRP and I plug in my mouse so I can flash:
-beta-supersu-v2.52.zip and
-busybox-signed
Then I reboot system but that's when I get the stuck logo.
I flash the provided files in recovery and then I reboot. However, when I reboot, I just see the animated logo (the one with the balls bouncing from left to right). It is stuck there. What am I doing wrong?
Same problem here, someone help plez.
I haven't even been able to get ADB or Fastboot to detect my NP.
fastboot flash in bootloader (do it manually) and heres all the stuff you will use/need:
http://forum.xda-developers.com/nexus-player/orig-development/marshmallow-mra58n-root-t3256647
I would recommend flashing PureNexus rom if your rooting. Million times better then stock, in my opinion. Its MM and pre rooted too. If your up for that, check it here:
http://forum.xda-developers.com/nexus-player/development/rom-pure-nexus-t3260232
I am unable to sideload PureNexus.
dfl said:
fastboot flash in bootloader (do it manually) and heres all the stuff you will use/need:
http://forum.xda-developers.com/nexus-player/orig-development/marshmallow-mra58n-root-t3256647
I would recommend flashing PureNexus rom if your rooting. Million times better then stock, in my opinion. Its MM and pre rooted too. If your up for that, check it here:
http://forum.xda-developers.com/nexus-player/development/rom-pure-nexus-t3260232
Click to expand...
Click to collapse
Hi I have tried to sideload to PureNexus using the instructions from http://forum.xda-developers.com/nexus-player/development/rom-pure-nexus-t3260232
I am receiving Footer is wrong and Signature validation failure errors.
Unlock your bootloader using fastboot. (fastboot oem unlock)
Flash PureNexus recovery. (fastboot flash recovery "purenexus_fugu_recovery-112515.img")
Reboot Bootloader (fastboot reboot bootloader)
Once in bootloader short press bottom button once until you see recovery option then long press the bottom button.
Once in recovery short press until you get to ADB then long press to get to the ADB sideload screen.
Sideload Rom (adb sideload pure_nexus_fugu-6.0-2015xxxx.zip) where xxxx is the date of the rom you are flashing..THIS IS WHERE I RECEIVE ERROR.
Sideload Gapps (adb sideload purenexus-gapps-mm-x86-leanback-20151202-signed.zip)
Short press until you get to Wipe data/factory Reset then long press (Clears data & cache)
Select reboot now
Once booted setup everything including Kodi
Then go back to recovery and sideload Kodi Mapping zip file. (adb sideload NexusPlayer-kodi-keymap-streaming-fix-signed.zip
Can you please help?
My Nexus Player just upgraded to Android 6.0 using the instructions from, http://forum.xda-developers.com/nexus-player/general/guide-nexus-player-how-to-unlock-t2961989.
Thanks...
dfl said:
fastboot flash in bootloader (do it manually) and heres all the stuff you will use/need:
http://forum.xda-developers.com/nexus-player/orig-development/marshmallow-mra58n-root-t3256647
I would recommend flashing PureNexus rom if your rooting. Million times better then stock, in my opinion. Its MM and pre rooted too. If your up for that, check it here:
http://forum.xda-developers.com/nexus-player/development/rom-pure-nexus-t3260232
Click to expand...
Click to collapse
I installed PureNexus as well, it's pretty nice. I lost adb debugging though, can't get adb to detect the nexus player unless I boot into recovery oddly.