Hi.
So, a quick overview. My laptop suddenly stopped recognizing my Nexus 10 while in the midst of transferring some files over. I decided to finally root. I used the cf-autoroot tool for Nexus 10 Lollipop. The last step of the rooting involves an automatic reboot. Now my Nexus 10 is stuck in the boot.
Details:
theunlockr (DOT) com/2014/11/22/how-to-root-the-nexus-10-on-android-5-0/
That is the guide I used, including the linked cf-autoroot. Sorry for the formatting, I don't have enough posts to post links.
My Nexus 10 is stuck on the step where it shows the four circles moving around. Not sure if that's important.
The cf-autoroot appeared to work successfully except for a piece in the middle that reads:
Same problem. The procedure seemed to go well, except maybe the mounting failed? It says:
Mounting...
- System
- Cache
--- Fail
I tried using the tool several times on two computers, and did my best to update drivers directly from Google (it appears the drivers are all up to date).
My Nexus 10 was on Lollipop. As far as I know, it was up to date, so I think that means it was on 5.0.1
Help?
Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s
Khaon said:
Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.
jsgraphicart said:
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.
Click to expand...
Click to collapse
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
Thanks. I just wanted to double check before I went jumping into it. I'm looking forward to tinkering with it when I get home from work.
Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
So I attempted to do all this when I got home yesterday. I found that after unlocking the bootloader, I got stuck in a boot loop. After doing some research I found that this has been an issue with the Nexus 10. Is there a reason for this? I read that locking the bootloader again fixed it, which it did. But I didn't want it locked. So I researched more and found that a a factory reset in stock recovery would fix it. I still had a boot loop. I managed to somehow get everything straightened out with a series of random tries and after installing TWRP and rooting and, again, getting the boot loop I attempted to go back into recovery but accidentally did a simple restart. For some reason, it booted right up after the restart so now I think everything is fine. But why is the Nexus 10 being so difficult? I never had these issues with other Nexus devices. Maybe some of this info will help the OP as well.
Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked
Khaon said:
Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked
Click to expand...
Click to collapse
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.
nexus 10 stuck on bootload up
jsgraphicart said:
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.
Click to expand...
Click to collapse
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom
tomistrouble said:
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom
Click to expand...
Click to collapse
Once you get in recovery mode with the android and the red explanation mark, hit all three buttons (Vol up , down and power) until (It can be tricky keep trying) you get a menu. Then use the volume buttons to select "Wipe Data/Factory rest" let it do its thing and reboot. Allow it to boot for 5-10 minutes.
Good luck
Related
Bought a new Nexus 7 because my wife and I have them and love them. We had bought our daughter a cheap 'funtab' from walmart just so she could play a few games she loves and hopefully leave ours alone, the funtab was a complete POS so it was returned to WM and just bought her a N7 instead.
When booted, the tablet it immediately notified me of the update from 4.1.2 to 4.2.1. Each time it tried to update it would fail partially through, not sure why. So I thought I'd download and use the toolkit to force the update. After unlocking, rooting, installing busybox and so on. I choose the option to flash stock image. The update process started OK there but part way through gave an error, something about needing to be 'X' but is instead 'x' before going back to the home screen. Now the tablet is stuck in fastboot mode, and cant boot to either recovery or android. I think I may be in trouble here.... Any suggestions?
#1 reason why people shouldn't use tool kits to root. You have no idea what went wrong or where the problem occurred.
I'm assuming that your tablet is unlocked so you need to download a custom recovery and install it via fastboot.
Then download the Stock 4.2.1 ROM from the Android development section and flash it in the recovery.
This should give you an idea of how to do it.
http://www.androidcentral.com/how-unlock-bootloader-and-root-your-nexus-7
Sent from my Nexus 7
I've done more research and I'm currently working on getting the android sdk going. I've downloaded it, jdk, the proper factory image (i think I f'd up by accidentally downloading the factory image for the hspa model). My question now is can the factory image be flashed from what appears to be fastboot mode, or do i need to flash custom recovery first (via the sdk)? I can confirm that the bootloaded is unlocked.
Ok so I was able to flash the stock image using the instructions found at http://forum.xda-developers.com/showthread.php?t=1907796
This process went extremely well once I had all my ducks in a row. Thanks for the help.
My OTA update showed up on my old 2012 Nexus 7, I told it to install, and it just sat there bouncing color disks forever after the first reboot. Perhaps something about being rooted and and having TWRP is what screwed it up.
Anyway, I was able to use fastboot to flash the stock kitkat images, so it is back now and even running kitkat. I think I'll leave it alone till I have some reason to root it again.
Same Problem
Claghorn said:
My OTA update showed up on my old 2012 Nexus 7, I told it to install, and it just sat there bouncing color disks forever after the first reboot. Perhaps something about being rooted and and having TWRP is what screwed it up.
Anyway, I was able to use fastboot to flash the stock kitkat images, so it is back now and even running kitkat. I think I'll leave it alone till I have some reason to root it again.
Click to expand...
Click to collapse
I have the same problem, but i can't fix it. Should i flash the KRT16S from JWR66Y zip to make thing right? Thank you for your help
I basically followed the instructions in here:
http://forum.xda-developers.com/showthread.php?t=1907796
But since it couldn't boot to use adb to get to bootloader, I powered it off and then held down power and vol-down to get to the bootloader so I could talk fastboot. Instead of the old image mentioned in that post, I searched for the latest kitkat image for my wifi 2012 Nexus 7 and used it.
Claghorn said:
I basically followed the instructions in here:
http://forum.xda-developers.com/showthread.php?t=1907796
But since it couldn't boot to use adb to get to bootloader, I powered it off and then held down power and vol-down to get to the bootloader so I could talk fastboot. Instead of the old image mentioned in that post, I searched for the latest kitkat image for my wifi 2012 Nexus 7 and used it.
Click to expand...
Click to collapse
Thank you very much! So i have to do the same. But isn't it a problem that i have KRT16S?Do I have to download the KRT16S from JWR66Y? Sorry for asking that much, i'm a newbie.
Claghorn said:
I think I'll leave it alone till I have some reason to root it again.
Click to expand...
Click to collapse
Good move. These devices seem to have a number of issues once rooted. I was rooted, bricked, RMA number, & now stock. Don't see much benefit to rooting, so plan not to re-root for now.
Just bought a new essential phone, it was on android 7, after downloading and installing 9 I restarted it. Now its stuck on the powered by android screen. Here's what I have tried: I followed the instructions on essentials website to unlock bootloader and flash the current build of pie. The FULL factory image, and it still wouldn 't boot past this screen so I tried an earlier version PH1-images-OPM1.180104.166 and its still stuck. Flashing causes no errors and its writing the system to both a and b. So any advice? Thanks
You are certainly jumping around releases, 7 to 9 to 8.
The ROM flashes to one slot per command, and always the opposite (inactive) slot. If "fastboot getvar current-slot" says the bootable slot is 'a' then the fastboot flash will go to 'b'. On the next reboot, the bootloader switches to the new slot, which in this case means 'b' becomes the active slot.
To flash to both slots, you would need to figure out which is the active slot, fastboot flash the image, then switch slots, and flash again.
If you haven't yet, read: https://mata.readthedocs.io/en/latest/
Depending on your knowledge of this device, you'll find useful hints there.
I would start with the first Pie release, which is: August 2018 Release Android 9 Pie, Release 1 - PPR1.180610.091. If you are on windows, make sure your using the essential fastboot (linked on the developer pages).
When I first got my (used) device, I remember having trouble. That may have been due to the timing, when there was a BTS hiccup in the Essential releases. At any rate, I had trouble getting a working device with fastboot flashes. I ended up sideloading the OTA release in recovery.
I'm going to guess that there it's a bootloader incompatibility from your original 7 device to the 9 or 8 ROMs you are flashing. That's why I typically start with the first release of a major upgrade. May just be my superstitions though [emoji16]
The first boot can take some time.
midwest2363 said:
Just bought a new essential phone, it was on android 7, after downloading and installing 9 I restarted it. Now its stuck on the powered by android screen. Here's what I have tried: I followed the instructions on essentials website to unlock bootloader and flash the current build of pie. The FULL factory image, and it still wouldn 't boot past this screen so I tried an earlier version PH1-images-OPM1.180104.166 and its still stuck. Flashing causes no errors and its writing the system to both a and b. So any advice? Thanks
Click to expand...
Click to collapse
Did you wipe using fastboot -w
I suggest that, given all your jumping between versions, you go back to the initial release using sideload. Beforehand, ensure that the essential driver is properly installed (ie remove and replace from a new DL)
Thanks, Everyone!
I was able to get a working device by flashing the initial release!
midwest2363 said:
I was able to get a working device by flashing the initial release!
Click to expand...
Click to collapse
That's a relief [emoji6]. I suspect that means you had a bootloader inconsistency.
Hi guys, a few weeks ago I revived my old 2012 N7 and have been getting some decent use out of it, however after trying to flash one of the Nexus factory images I think I may have bricked the device. I'll get straight to the point and explain more further down.
1. The bootloader is unlocked
2. The tablet boots into this screen - https://i.imgur.com/nzYaXLt.jpg
3. Whenever I boot into the bootloader the screen turns off (I believe the bootloader is the main cause of this issue)
4. Booting to recovery does nothing
5. Fastboot works(at least detects the device - https://i.imgur.com/yUGTVjh.jpg
6. When i try to flash a nexus factory image I get this error, then the tablet boots into the bootloader with a black screen - https://i.imgur.com/Kc9adlJ.jpg
7. Attempting to flash TWRP recovery results in this error - https://i.imgur.com/SHuQZWK.jpg
8. A video of what happens when I try different things: https://youtu.be/JBBT__nGJS8
I'm pretty sure the issues happened because there was some sort of failure halfway through a factory image flash(I flashed quite a few of the factory images but was trying to find the one I liked the most), so I unplugged the tablet( I know:/ ) as the flashing wasn't progressing at all after the error.
If anyone can help it'll be massively appreciated, I hope I've made it clear on what's going on with the device, and I'll be able to further explain things if needed
Sorry to tell you, but it looks to me as if the emmc memory is broken ... bootloader cannot be flashed / updated. If you had done a backup of your binary blobs before as described here there would have been the chance to reformat and to recover from scratch. Otherwise I suppose there is nothing you can do now. Our devices are becoming ancient ...
AndDiSa said:
Sorry to tell you, but it looks to me as if the emmc memory is broken ... bootloader cannot be flashed / updated. If you had done a backup of your binary blobs before as described here there would have been the chance to reformat and to recover from scratch. Otherwise I suppose there is nothing you can do now. Our devices are becoming ancient ...
Click to expand...
Click to collapse
Cheers for the reply It does make sense that the memory is broken as the tablet often fully freezed/switched off randomly during the last 4/5 days of its life. Just a shame because it was actually working surpisingly well before the memory issues! And also, thank you for the 7.1.2 AOSP ROM, definitely the best working ROM I tried as it never seemed to have any issues with it
TheGrade said:
Hi guys, a few weeks ago I revived my old 2012 N7 and have been getting some decent use out of it, however after trying to flash one of the Nexus factory images I think I may have bricked the device. I'll get straight to the point and explain more further down.
1. The bootloader is unlocked
2. The tablet boots into this screen - https://i.imgur.com/nzYaXLt.jpg
3. Whenever I boot into the bootloader the screen turns off (I believe the bootloader is the main cause of this issue)
4. Booting to recovery does nothing
5. Fastboot works(at least detects the device - https://i.imgur.com/yUGTVjh.jpg
6. When i try to flash a nexus factory image I get this error, then the tablet boots into the bootloader with a black screen - https://i.imgur.com/Kc9adlJ.jpg
7. Attempting to flash TWRP recovery results in this error - https://i.imgur.com/SHuQZWK.jpg
8. A video of what happens when I try different things: https://youtu.be/JBBT__nGJS8
I'm pretty sure the issues happened because there was some sort of failure halfway through a factory image flash(I flashed quite a few of the factory images but was trying to find the one I liked the most), so I unplugged the tablet( I know:/ ) as the flashing wasn't progressing at all after the error.
If anyone can help it'll be massively appreciated, I hope I've made it clear on what's going on with the device, and I'll be able to further explain things if needed
Click to expand...
Click to collapse
You still might be able to recover your Nexus with my guide. Go check it out.
I should have left well enough alone.
I was updating things so... I used twrp to install a new rom, magisk etc...
Then just though why not update twrp while I am at it.
I tried installing twrp-3.6.2_9-0-h910.img while inside my old version of twrp (not sure what version...)
Anyway - chose to install the .img file to recovery partition
Went to boot straight away back into my new recovery and got a kernel panic screen.
Booting to recovery gives me kernel panic every time
Regular boot gives me the LG symbol forever - more than 10 minutes
Now seems I am completely ____________'d
Seems I should know what to try next - but it's been a while since I have been doing this...
Thanks in advance.
wantpizza said:
I should have left well enough alone.
I was updating things so... I used twrp to install a new rom, magisk etc...
Then just though why not update twrp while I am at it.
I tried installing twrp-3.6.2_9-0-h910.img while inside my old version of twrp (not sure what version...)
Anyway - chose to install the .img file to recovery partition
Went to boot straight away back into my new recovery and got a kernel panic screen.
Booting to recovery gives me kernel panic every time
Regular boot gives me the LG symbol forever - more than 10 minutes
Now seems I am completely ____________'d
Seems I should know what to try next - but it's been a while since I have been doing this...
Thanks in advance.
Click to expand...
Click to collapse
I think you may need to root your phone again.
h910_root_pkg.zip "DirtySanta root package"
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
Thanks @Darnrain1 . It's been a while. Thanks for the reminder links.
I changed laptops since I did this... Plus I am 99% Linux now but a struggle I am used to.
I also found my initial LGUP before I rooted last time so the nerves have calmed and the tremors have stopped. HaHa. It was too late last night and I SOOOO should not have been flashing in TWRP.
wantpizza said:
Thanks @Darnrain1 . It's been a while. Thanks for the reminder links.
I changed laptops since I did this... Plus I am 99% Linux now but a struggle I am used to.
I also found my initial LGUP before I rooted last time so the nerves have calmed and the tremors have stopped. HaHa. It was too late last night and I SOOOO should not have been flashing in TWRP.
Click to expand...
Click to collapse
No problem.
Another thing you could try and do is flash twrp via fastboot and see what happens.
Update twrp. twrp-3.6.2_9-0-h910.img
With the phone off hold vol down plug USB into phone and computer.
type on your computer:
fastboot flash recovery twrp-3.6.2_9-0-h910.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset.
Thanks a ton @Darnrain1 !!
Yep - that was all I had to do to get TWRP back was fastboot flash it in and now I restored an old backup and have my phone back.
I appreciate it. Happy New Year and all the best.