Database Users

Kindle Fire NEVER ROOTED OR TAMPERED WITH in boot loop!

Ok so I have been reading around and most of what I found about my specific problem (boot loop with never putting any custom restore or root or ANYTHING on it) was pretty much was useless. I am not a complete beginner I have put custom mods on many of my devices, defy, atrix, dell streak, ect, and I have used ADB among other things (not that I am a pro at it mind you!)
I realize theres a thread up for this here
http://forum.xda-developers.com/showthread.php?t=1356257
but I want to know if this will work or is for people WHO HAVE NEVER DONE ANY MODIFICATIONS TO THEIR KINDLE FIRE
If it is then I will give it a shot.
What happened is (to my knowledge) my daughter was playing with it, and the next morning, it was boot looping, and quickly. So when I turn it on, it shows kindle fire then goes black, then repeats or once in a while will make it to the slide to unlock but 2-3 seconds after goes black and continues the bootloop
ANY HELP GREATLY APPRECIATED!

I recommend giving Amazon a call and get the device replaced.... If you still have a warranty?

AustinFire said:
I recommend giving Amazon a call and get the device replaced.... If you still have a warranty?
Click to expand...
Click to collapse
Why would I even try to fix it if I had a warrant? .... thanks anyways...
so ive downloaded the drivers and its basically not working, and the method for deleting the drivers (the one some idiot posted at least) will only work IF THE DEVICE STAY CONNECTED... Which it obviously isnt... and the 3-4 seconds of it saying KINDLE FIRE isnt long enough for me to find it in the device manager... by the time that updates its already rebooting...
so please anybody.... i dont understand why it would be so difficult.... I JUST NEED A RECOVERY I DONT NEED ANY OF MY STUFF

I have tried running ADB shell it says device not found....

If it is a hardware problem, then flashing is pointless. It did this on its own. Processor or board issue. Given the variety of things I see posted, hardware is an issue at least 1/3 of the time, my guess.
Sent from my Amazon Kindle Fire using xda app-developers app

Ixthusdan said:
If it is a hardware problem, then flashing is pointless. It did this on its own. Processor or board issue. Given the variety of things I see posted, hardware is an issue at least 1/3 of the time, my guess.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I would agree with you but i had installed some apps prior that seemed to make it glitchy and slow, and my daughter probably just triggered something (she is 3 and just constantly opens and taps things, i caught her in settings before) ... im pretty positive its software, especially since I read a few people with the same exact symptoms of mine... (it shows logo then reboots repeatedly, but sometimes makes it to the slide screen for like 4 seconds then it goes back to boot loop) Im sure I could fix it but I need help with getting my ADB in order or im screwed xD

I have also read several places that my problem could be fixed with a factory cable...

Have you tried a hard reset (hold the power button down for 30 seconds then power back on)? That should clear any stuck apps. It also sounds similar to a low power boot loop. If you haven't tried charging it you might want to put it on the charger overnight and see what that does. Other than that I don't know why a stock KF would bootloop.
Sent from my Amazon Kindle Fire using xda premium

Dead Battery
This is covered in a sticky post
http://forum.xda-developers.com/showthread.php?t=1623244

JimCo06 said:
Have you tried a hard reset (hold the power button down for 30 seconds then power back on)? That should clear any stuck apps. It also sounds similar to a low power boot loop. If you haven't tried charging it you might want to put it on the charger overnight and see what that does. Other than that I don't know why a stock KF would bootloop.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I have tried all of that, many times in fact. I also think its odd that it got stuck in a bootloop but from what ive read stock KF do that sometimes and its usually as simple as changing the way it boots which is why I think the factory cable is what I really need...

kinfauns said:
This is covered in a sticky post
http://forum.xda-developers.com/showthread.php?t=1623244
Click to expand...
Click to collapse
like i said... thats why i think i need a factory cable (fastboot)... but the problem here is i dont have a factory cable... lmao!
so basically im stuck at the fact that the drivers arent working, thus the KF is not being recognized, making fastboot impossible, or am i wrong? somebody please clarify...

Untraumatized said:
like i said... thats why i think i need a factory cable (fastboot)... but the problem here is i dont have a factory cable... lmao!
so basically im stuck at the fact that the drivers arent working, thus the KF is not being recognized, making fastboot impossible, or am i wrong? somebody please clarify...
Click to expand...
Click to collapse
You don't know whether or not your fastboot drivers are working because you must first put the device into fastboot mode to see if Windows will load the appropriate drivers.
Your problem is that on a stock device unable to boot into the system, 2 out of the 4 possible ways of putting the KF into fastboot mode are unavailable to you. The remaining options are to use a factory cable or to crack the case open to get access to the motherboard.
http://forum.xda-developers.com/showthread.php?t=1668159
There's another thread on the forums here about someone who disconnected the battery and hardwired it to a charger, but that seems like a really bad idea to me. A factory cable is your best/safest first step to getting out of your situation.

Won't boot - strange colors

Nexus 7 was working fine and then I pulled it out and notices a gray screen. Restarted it and I get a slight blue shadow to the Google and Padlock boot screen. Then it begins to change crazy colors and ends up fading to a gray screen. Can't boot into recovery from fastboot. Help?
Here are some pictures in order of boot.

cbcampos said:
Nexus 7 was working fine and then I pulled it out and notices a gray screen. Restarted it and I get a slight blue shadow to the Google and Padlock boot screen. Then it begins to change crazy colors and ends up fading to a gray screen. Can't boot into recovery from fastboot. Help?
Here are some pictures in order of boot.
Click to expand...
Click to collapse
Wow, I haven't seen or heard of any defect like that in the N7 yet. I would exchange/RMA the device if I were you. It seems like an easily demonstrable problem, there shouldn't be any reason Google/a retailer wouldn't exchange it.
Sent from my Paranoid Nexus 7

RockNrolling said:
Wow, I haven't seen or heard of any defect like that in the N7 yet. I would exchange/RMA the device if I were you. It seems like an easily demonstrable problem, there shouldn't be any reason Google/a retailer wouldn't exchange it.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
Even with the bootloader unlocked? Or do I need to somehow lock it?

update
cbcampos said:
Nexus 7 was working fine and then I pulled it out and notices a gray screen. Restarted it and I get a slight blue shadow to the Google and Padlock boot screen. Then it begins to change crazy colors and ends up fading to a gray screen. Can't boot into recovery from fastboot. Help?
Here are some pictures in order of boot.
Click to expand...
Click to collapse
It actually seems as if it is partially just a screen issue. I heard a notification of an email on the N7. I believe it has actually booted up, but the display is stuck. If I tap where the notification bar would be, I heard audio feedback.
UPDATE: I suspected something was loose in display connection because of the type of problem. I knocked pretty hard on the device, and the display kicked back in. Doesn't solve the problem of being unable to boot into recovery, but it seems like it could be a display problem. Suggestion still to just get a replacement? and relock bootloader?

cbcampos said:
Even with the bootloader unlocked? Or do I need to somehow lock it?
Click to expand...
Click to collapse
My bad, I skimmed your post and didn't realize you could get into fastboot mode. Try turning off the N7, connecting it to a computer , and getting back to fastboot mode. You should be able to use adb to relock the boot loader. In fact, you should be able to boot into recovery from fastboot since the N7 is connected to a computer.
Good job trouble shooting the display connection! I would still personally recommend exchanging/RMA. You never know when the problem might reappear even if you "fix" it.
Sent from my Paranoid Nexus 7

Take the back cover off and check the display ribbon cable,and all other connections are tight. They won't be able to tell that the back was removed, unless you ding it up. Might find a loose connection. May just save you the trouble of going through RMA.

[Q] Android Lying down with Red Triangle and Exclamation

I am having issues with my S4 overheating when charging overnight. The lock screen is displayed and there are thin white vertical lines on the right side. I also see a couple of dots, like the ones used to indicate which home screen you are on, flashing along with the padlock. After toggling the screen off and on, they go away. I want to exchange my phone but here is the reason for my post.
I rooted using motochopper and installed TWRP. I have run triangle away (don't know if it works on the sprint version) and installed the stock ROM via Odin to unroot.
When I boot to stock recovery I have the Android on his back with his chest open and the red triangle with the exclamation. I just want to know if I anyone thinks I will have any issues when attempting to exchange this device. Should I/can I do anything else to it to get rid of it?

wrx7m said:
I am having issues with my S4 overheating when charging overnight. The lock screen is displayed and there are thin white vertical lines on the right side. I also see a couple of dots, like the ones used to indicate which home screen you are on, flashing along with the padlock. After toggling the screen off and on, they go away. I want to exchange my phone but here is the reason for my post.
I rooted using motochopper and installed TWRP. I have run triangle away (don't know if it works on the sprint version) and installed the stock ROM via Odin to unroot.
When I boot to stock recovery I have the Android on his back with his chest open and the red triangle with the exclamation. I just want to know if I anyone thinks I will have any issues when attempting to exchange this device. Should I/can I do anything else to it to get rid of it?
Click to expand...
Click to collapse
you're good to go. That's what the stock recovery looks like. Android with the red triangle. Go get your new one

shmega said:
you're good to go. That's what the stock recovery looks like. Android with the red triangle. Go get your new one
Click to expand...
Click to collapse
Thanks!!! Appreciate the response. Just in time, as I am about to leave work for the sprint store

wrx7m said:
Thanks!!! Appreciate the response. Just in time, as I am about to leave work for the sprint store
Click to expand...
Click to collapse
as long as you go into settings, under about device, status, at the bottom it says device status official, then you have nothing to worry about. Even if they did somehow find something, what you described is a hardware issue

Got my new phone. Didn't get any hassle. New phone seems to be working fine. I received it with the older firmware so I was able to root it easily and restore my nandroid backup. Flawless Victory. :victory:
Thanks everyone!

wrx7m said:
Got my new phone. Didn't get any hassle. New phone seems to be working fine. I received it with the older firmware so I was able to root it easily and restore my nandroid backup. Flawless Victory. :victory:
Thanks everyone!
Click to expand...
Click to collapse
I used to work for Sprint. When someone came in with any issues, we were encouraged to do whatever it took to make the situation right (IE, replacing phones) if you do however go in again for a replacement, they will ship you a insurance replacement, which is still a working phone, but they were often refurbished. Which, in my opinion anyway, is better than a nonworking phone than no phone at all.
just some helpful advice
happy rooting!

Motorola Droid RAZR/Cyanogen mod problem?

I've had this Motorola Droid RAZR for like two years now and a friend of mine took it and worked on it, adding something called "Cyanogen Mod" and he 'rooted' it I believe? Ever since, phone has worked great. However, today I tapped the home button and the whole screen had a weird visual glitch where the wallpaper was entirely intact but the icons and such were only half appearing, like someone scratched them out with fingernails or something. It would go away and come back so I got frustrated and rebooted my phone. It starts up normally and goes to this screen where you can do different stuff with Cyanogen mod (like changing the rom? or changing boot options) and usually I just continue past that because for 1) I know nothing about it and 2) It always was fine. But when it did the typical boot up, it just skipped back to the first screen you get when you turn the phone on and repeats. It never goes to the second part of the Cyanogen Mod where the words appear and the little thing spins, it simply skips back to the screen you get when you power up and repeats. It keeps doing this and I looked online how to fix it, tried about twelve different things (like restoring different aspects and using different roms or making new roms) and it just didn't work. Eventually it got bugged out where the screen was just black, couldn't get it to do anything but reboot and go back to black. I let it sit until the battery ran dry I believe and now I'm at a brick wall.
Is there a way I can totally just revamp and start fresh? Like remove all of it and reinstall Cyanogen mod/the OS and all that jazz? I don't mind losing everything if I can just keep the phone, I don't pay for a cellphone and I don't want one I just use the droid for texting apps/games/reddit/etc. If anyone could help me save this thing I'd appreciate it.

Hi there,
Please stand by until mods will move this thread to the related forum for Droid RAZR.
For reply or ask other questions you must register an account.
Stand by

Hello? Can Somebody help me out, I've waited a couple days now and no one has said a thing?

You have safestrap installed, correct? If so, what version?

Dr. Mario said:
You have safestrap installed, correct? If so, what version?
Click to expand...
Click to collapse
How would I know if I had it installed? I remember when I booted up the phone something came on with a picture of a little robot that said "Safestrap Enabled" and then when I had this problem it was saying "Safestrap Disabled". I can't get the phone to turn on right now though, is there a way I can check what version I have another way?

Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.

Dr. Mario said:
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Click to expand...
Click to collapse
Just tried booting it up, nothing is working I think the phone is dead. I plug it into the charger and only the notification light on the top left goes on a blueish white and stays on as long as it is plugged into the charger. Nothing will turn on at all and the phone doesn't seem to respond to anything. Is my phone just dead..?

Soft bricked. Try pushing both volume down and up button while plugged into either computer or charger, and hold down power button until it boots. I hope you won't need to buy Motorola factory cable at this point.

Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.

ATTACK said:
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
Click to expand...
Click to collapse
In English please?
Edit: Just plugged it in like you said and instantly the boot screen came on rather than simply that silly light so I think my phone is improving but I still would like to entirely revamp it or redo it or whatever you wanna call it so that everything is fresh and new and my phone is okay.

Good. I think it could be because the battery died somehow. Good thing the protection mechanism on the bootloader didn't have the wild idea of disabling the phone.

[Q] Nexus 10 stuck at bootloader screen, will not do anything else

I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.

razrus said:
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
Click to expand...
Click to collapse
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk

charesa39 said:
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.

razrus said:
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
Click to expand...
Click to collapse
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?

charesa39 said:
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
Click to expand...
Click to collapse
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.

razrus said:
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
Click to expand...
Click to collapse
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?

charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.

charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.

So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.

razrus said:
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
Click to expand...
Click to collapse
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.

charesa39 said:
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
Click to expand...
Click to collapse
Is it possible to flash even though it's not recognized by windows?

razrus said:
Is it possible to flash even though it's not recognized by windows?
Click to expand...
Click to collapse
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.

charesa39 said:
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
Click to expand...
Click to collapse
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.

razrus said:
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
Click to expand...
Click to collapse
That's great to hear. I'm glad it came back to life. :good: Although, I wouldn't suggest using a toolkit. In my experience from what I've seen around these forums, they tend to cause more harm than good. It's good if you understand everything that's going on, and they can prove useful for devices that have really complex unlocking and rooting procedures, but Nexus devices are so easy to unlock and flash manually. I always flash each image file manually so if something goes wrong, I know exactly where it went wrong and how to fix it. The Google Play issue you mentioned is a perfect example. Flashing manually also helped me learn the basics of Fastboot and ADB. So if you want to stay on stock 5.1, I would recommend reflashing the factory image manually. I always use this thread to help me out in case I forget something: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. Although it's for the Nexus 6, it's the same procedure for the Nexus 5, Nexus 10, Nexus 7, etc. That's the real convenient thing about Nexus devices as well, as they are all pretty much flashed the same way. Should all be really simple since you already have the drivers set up from installing the toolkit. Good luck! And have fun with your newly revived N10.