Hello,
So, I got my Nexus 10 today. Super nice tablet. I wanted to root it and unlock the bootloader - unlocking the bootloader went fine, and I managed to flash CWM recovery. However, I forgot the enable USB Debugging under developer tools before I started all this..
My question now, how do I get this thing to boot again? And what is the smartest move now to root it?
Thanks!
What method did you use?
I keep linking these same posts lately. lol
http://forum.xda-developers.com/showpost.php?p=37019359&postcount=10
http://forum.xda-developers.com/showpost.php?p=37020134&postcount=3
If you're stuck in a boot loop after unlocking the bootloader, you may have to perform a factory reset from recovery. I had to do this to get mine booting again after I unlocked it. After the reset, everything worked great.
Of course, this is also assuming you unlocked your bootloader using fastboot , and not a toolkit. Solution might be the same though either way. May be worth a shot.
I also borked the original ROM after unlocking it, before I even flashed a custom recovery using the nexus toolkit (http://forum.xda-developers.com/showthread.php?t=2015467)
However, it is quite easy to reflash the software (you will loose the data though) through the same toolkit. After that I was able to flash TWRP recovery and CM10.1
Thank you all for your help! Got it working using the linux toolkit and perform a factory reset
Related
When I go into recovery on my Nexus 4 running Android 4.3. I get no more then a black screen.
It was working before and last thing I did was flashing FOTAKILL.
Now booting in recovery isn't working for me anymore.
My device is rooted and no other problems.
Weird thing is that my device says secure boot = enabled.
Lockstate = locked
I locked the bootloader with "bootunlocker". So for one of those it's true.
This last one should say "disabled" with root access right?
Still device has proper root.
EDIT:
Flashed CWM recovery instead... No use, still getting black screen when booting into recovery.
Both CWM Revocery and TWRP are not working for me anymore.
Still managed to make a NANDROID backup, just in case.
Send from my Nexus 4
DecypherT said:
When I go into recovery on my Nexus 4 running Android 4.3. I get no more then a black screen.
It was working before and last thing I did was flashing FOTAKILL.
Now booting in recovery isn't working for me anymore.
My device is rooted and no other problems.
Weird thing is that my device says secure boot = enabled.
Lockstate = locked
I locked the bootloader with "bootunlocker". So for one of those it's true.
This last one should say "disabled" with root access right?
Still device has proper root.
EDIT:
Flashed CWM recovery instead... No use, still getting black screen when booting into recovery.
Both CWM Revocery and TWRP are not working for me anymore.
Still managed to make a NANDROID backup, just in case.
Send from my Nexus 4
Click to expand...
Click to collapse
You did unlock your bootloader to flash CWM, didn't you?
What version did you flash? You're sure it was for the Nexus 4, right?
What did you use to flash it? Fastboot commands?
Yes i unlocked and then flashed. I was in bootloop after i tried to "OEM Unlock"
I flashed the TWRP 2.6.0.0 Mako version for the N4.
I used Wug's Nexus Toolkit for the flashing.
As typed i just tried CWM Recovery and that one is also not working.
Weirdest thing is that is was working without a flaw. 2 weeks back i booted into recovery and flashed FOTAKILL.
I can't understand why it wouldn't be working anymore now. I didn't mess with system files or anything else.
DecypherT said:
Yes i unlocked and then flashed. I was in bootloop after i tried to "OEM Unlock"
I flashed the TWRP 2.6.0.0 Mako version for the N4.
I used Wug's Nexus Toolkit for the flashing.
As typed i just tried CWM Recovery and that one is also not working.
Weirdest thing is that is was working without a flaw. 2 weeks back i booted into recovery and flashed FOTAKILL.
I can't understand why it wouldn't be working anymore now. I didn't mess with system files or anything else.
Click to expand...
Click to collapse
where did you grab FOTAKILL? it wasnt in the n4 threads, was it?
No it was in one of the treads about the "google data usage".
But i never read anything about different FOTAKILL versions for different phones.
Many people used it and i never read any flaws with FOTAKILL regarding recovery. I doubt FOTAKILL is the issue here.
bump
Send from my Nexus 4
DecypherT said:
bump
Send from my Nexus 4
Click to expand...
Click to collapse
Try flashing a recovery manually through fastboot
fastboot flash recovery path_to_recovery.img
Problem is solved. I flashed it again using the toolkit and miraculously it boots into recovery now.
Maybe it was because i manually re-locked the bootloader that caused the flashing to fail.
DecypherT said:
My device is rooted and no other problems.
Weird thing is that my device says secure boot = enabled.
Lockstate = locked
I locked the bootloader with "bootunlocker". So for one of those it's true.
This last one should say "disabled" with root access right?
Still device has proper root.
Click to expand...
Click to collapse
Secure boot has nothing to do with root or the bootloader. It has to do with the boot chain of the APQ8064 SoC. It will always show enabled (unless someone has figured out how to disable it, which I don't think has happened yet).
Lockstate shows the lock state of the bootloader, and having root or a custom recovery has no impact on that. It will show locked or unlocked.
Sent from my Nexus 4 using Tapatalk 4
Hi everyone,
While trying to upgrade my device to stock Android 7.1.1, I've forgotten to flash the boot image. All the other components have been correctly flashed (system, bootloader, radio, etc.), but I was not careful enough and I forgot to flash the boot image. The problem is I've decided to relock my bootloader (silly me) right afterwards and now the device is in a bootloop (as the current boot image comes from the custom ROM that was installed previously). Naturally, I cannot unlock my bootloader again as it says "OEM unlock is not allowed". Am I screwed? Any ideas on how to unlock my bootloader? After many years of flashing, this is the first time I'm in a real trouble. Thanks for your help!
Yup u may at a lose if the Bootloader is locked then I don't think u can flash anything that's why it's recommended not to Relock the Bootloader bc if you phone doesn't boot for some reason then there's nothing u can do but to RMA it if u still have warranty. If not then sell as parts
Sent from my Pixel XL using Tapatalk
Thanks for your input! I will have it RMA'ed, so it's not a huge deal, but I was wondering whether there was a way of troubleshooting this. But I guess that's not possible. Cheers!
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work
I have a 6P running 7.1.1 that has never been rooted or modified in anyway other than unlocking the bootloader. When I first got the phone I unlocked the bootloader so I could root the phone later if I wanted to without wiping the contents. I never rooted it.
Now Android Pay doesn't work with an unlocked bootloader. I would like to relock it. I understand that this will wipe my device. My question is, can I just press the button in NRT that says "OEM Lock" and it will take care of any flashing or resetting that needs to be done? I was more up to speed on all this when I had my Nexus 5, but the 6P hasn't really required me to get that involved.
Thank you for any help or advice.
Yes, OEM Lock will work, it just sends the ADB commands to your phone. Yes it will (unfortunately) factory reset the phone so to be sure to backup what you need, or at least be sure the Google backup feature is enabled for your apps.
Couldn't you just flash a custom kernel to get AP working again? For example, ElementalX has the bootloader check removed from the kernel. Use fastboot to boot into latest official TWRP without flashing it to the device and use that to flash EX kernel.
v12xke said:
Yes, OEM Lock will work, it just sends the ADB commands to your phone. Yes it will (unfortunately) factory reset the phone so to be sure to backup what you need, or at least be sure the Google backup feature is enabled for your apps.
Click to expand...
Click to collapse
Thanks for the feedback. I knew I was going to lose everything, I just didn't want to brick it someway because it was 7.1.1.
Had some issues with my camera recently and decided to do a nandroid restore. Restore didn't turn out well and I ended up with a factory reset device and here's where things get confusing for me.
1. I'm using the A2017G with B03.
2. TWRP installed and phone rooted, but bootloader LOCKED. Previously followed tenfar's guide back in August 2016.
3. Now my phone still has TWRP installed but no longer has root access. I wish to revert everything back to stock (i.e. stock recovery, everything) and do the proper method according to this guide but I do not know where to start as I don't even know the current state of my phone due to the locked bootloader. I fear that if I proceed with Controllerboy's consolidated guide, I may just brick my phone.
Appreciate any help rendered!
Scandiacus said:
Had some issues with my camera recently and decided to do a nandroid restore. Restore didn't turn out well and I ended up with a factory reset device and here's where things get confusing for me.
1. I'm using the A2017G with B03.
2. TWRP installed and phone rooted, but bootloader LOCKED. Previously followed tenfar's guide back in August 2016.
3. Now my phone still has TWRP installed but no longer has root access. I wish to revert everything back to stock (i.e. stock recovery, everything) and do the proper method according to this guide but I do not know where to start as I don't even know the current state of my phone due to the locked bootloader. I fear that if I proceed with Controllerboy's consolidated guide, I may just brick my phone.
Appreciate any help rendered!
Click to expand...
Click to collapse
You can use the MiFlash file to unlock the bootloader just like Controllerboy says in his guide. You don't need to do the TWRP part since you already have it xd
There shouldn't be any trouble since, if you read his guide, you flash TWRP before unlocking the bootloader.
Edit: sorry he doesn't use MiFlash xd. Should still be the same, just use those images he provides to unlock it.
Otherwise you should be able to use MiFlash with some files that the Russians made, there's one called A2017U_FASTBOOT_UNLOCK_EDL which besides from probably unlocking your device, gives you Fastboot if you are on A2017G.
I want to make a clean Install of factory image (Android 8.0 Oct) on my Nexus 6P with TWRP.
Should wipe Dalvik, Data, System and Internal storage, then move the stock zip file (That I downloaded from google's web) from my computer to my phone and just install in TWRP? Will it work?
Device is unrooted, only has an open boot loader, I just want to make a clean install of Android 8.0
If you wipe your internal all your downloads and your factory image are gone.
Sure you can flash the unpacked *.img with twrp, but don't try to flash the bootloader or radio with twrp.
If you really want a clean start and wipe everything, then you should flash the factory image with fastboot. This will update your bootloader and radio too.
coremania said:
If you wipe your internal all your downloads and your factory image are gone.
Sure you can flash the unpacked *.img with twrp, but don't try to flash the bootloader or radio with twrp.
If you really want a clean start and wipe everything, then you should flash the factory image with fastboot. This will update your bootloader and radio too.
Click to expand...
Click to collapse
Hi coremania, I have a few questions towards this method.
1. If the stock image is stored in either external SD card OR USB OTG, even then will there be any problem installing the the stock rom back using TWRP?
2. If the boot loader is unlocked, should one has to re-lock it first before reinstalling the stock rom either thru' TWRP or thru' Fasboot commands?. and finally,
3. Is it not advisable to flash the stock rom from the full factory image using TWRP rather than Fastboot?
(As I think it is easier to flash thru TWRP than typing those ADB commands in Fastboot).
Thank you for your inputs.
AndroMani said:
Hi coremania, I have a few questions towards this method.
1. If the stock image is stored in either external SD card OR USB OTG, even then will there be any problem installing the the stock rom back using TWRP?
2. If the boot loader is unlocked, should one has to re-lock it first before reinstalling the stock rom either thru' TWRP or thru' Fasboot commands?. and finally,
3. Is it not advisable to flash the stock rom from the full factory image using TWRP rather than Fastboot?
(As I think it is easier to flash thru TWRP than typing those ADB commands in Fastboot).
Thank you for your inputs.
Click to expand...
Click to collapse
If you decide to flash and test some stuff the bootloader should be always unlocked. If anything will went wrong and your bootloader is locked you're mostly f***ed. Never relock your bootloader until you want to sell your device.
I mostly use flashfire to flash stock and custom roms, TWRP is ok too, but it's easier to keep root and TWRP with flashfire by flashing stock images. Do not flash bootloader and radio with flashfire, never ever !!! There are TWRP flashable zips for bootloader and radio here on XDA, you only should use these with TWRP, but the safe way for bootloader and radio is fastboot for sure. Fastboot is the safest way for flashing stock,
but not absolutely necessary, you have to decide this for yourself.
Edit: to your first question, I never flashed with USB otg on the n6p, but I think yes it should be fine.
I hope someone here can help answer this question. I also want to flash factory image version 8.1.0 on my nexus 6P. But somehow my phone is not recognized by any computers I tried to plug it in. When I plug in the usb cable to the phone, it doesn't pop up the usb notification to choose MTP for file transfer. Then I try with Developer tab in Settings to choose it manually (USB debugging is enable) but it still doesn't work. My laptop has been updated with android usb drivers and other stuffs. I have a second phone (Oneplus 1) and it's recognized by my laptop the moment I plug it in. Please suggest any solutions to fix this. Thanks everyone.
sinjok said:
I hope someone here can help answer this question. I also want to flash factory image version 8.1.0 on my nexus 6P. But somehow my phone is not recognized by any computers I tried to plug it in. When I plug in the usb cable to the phone, it doesn't pop up the usb notification to choose MTP for file transfer. Then I try with Developer tab in Settings to choose it manually (USB debugging is enable) but it still doesn't work. My laptop has been updated with android usb drivers and other stuffs. I have a second phone (Oneplus 1) and it's recognized by my laptop the moment I plug it in. Please suggest any solutions to fix this. Thanks everyone.
Click to expand...
Click to collapse
Check your cable, or try a different with different port.
In the Dev options you can reset the debugging options, i guess a reboot is necessary afterwards.
coremania said:
If you decide to flash and test some stuff the bootloader should be always unlocked. If anything will went wrong and your bootloader is locked you're mostly f***ed. Never relock your bootloader until you want to sell your device.
I mostly use flashfire to flash stock and custom roms, TWRP is ok too, but it's easier to keep root and TWRP with flashfire by flashing stock images. Do not flash bootloader and radio with flashfire, never ever !!! There are TWRP flashable zips for bootloader and radio here on XDA, you only should use these with TWRP, but the safe way for bootloader and radio is fastboot for sure. Fastboot is the safest way for flashing stock,
but not absolutely necessary, you have to decide this for yourself.
Edit: to your first question, I never flashed with USB otg on the n6p, but I think yes it should be fine.
Click to expand...
Click to collapse
Thank you for the clarification. So, far I have not faced a situation to flash my custom recovery either thru' TWRP or thru Fastboot. Instead, I am using my Nandroid backups taken from TWRP and using it to restore my system after I try a custom rom OR upgrade my system with the latest Magisk version for a systemless root. So far there are no issues. But, I wanted to be aware of the methods to go back to stock (without any user installed apps/data) if need be. I read in some forums that we need to re-lock the unlocked bootloader if we want to go back to stock rom using fastboot. Otherwise, the system will not be installed alright and might cause a bootloop.
That's why I wanted to clarify.
Thanks again for your inputs.
AndroMani said:
Thank you for the clarification. So, far I have not faced a situation to flash my custom recovery either thru' TWRP or thru Fastboot. Instead, I am using my Nandroid backups taken from TWRP and using it to restore my system after I try a custom rom OR upgrade my system with the latest Magisk version for a systemless root. So far there are no issues. But, I wanted to be aware of the methods to go back to stock (without any user installed apps/data) if need be. I read in some forums that we need to re-lock the unlocked bootloader if we want to go back to stock rom using fastboot. Otherwise, the system will not be installed alright and might cause a bootloop.
That's why I wanted to clarify.
Thanks again for your inputs.
Click to expand...
Click to collapse
You don't need to ever relock your bootloader. If you want to try stock and use TWRP try SuperXe 8.1. It's just flaahable stock with some extras you can opt out of your not intereseted.
AndroMani said:
Thank you for the clarification. So, far I have not faced a situation to flash my custom recovery either thru' TWRP or thru Fastboot. Instead, I am using my Nandroid backups taken from TWRP and using it to restore my system after I try a custom rom OR upgrade my system with the latest Magisk version for a systemless root. So far there are no issues. But, I wanted to be aware of the methods to go back to stock (without any user installed apps/data) if need be. I read in some forums that we need to re-lock the unlocked bootloader if we want to go back to stock rom using fastboot. Otherwise, the system will not be installed alright and might cause a bootloop.
That's why I wanted to clarify.
Thanks again for your inputs.
Click to expand...
Click to collapse
I can't confirm the relock and unlock method to go back to stock. Senseless to me.