Just recently purchased a "broken" Nexus 10 off ebay for nearly nothing. Seller showed that it just hangs at "Google" upon startup. Bought it as a project to see what I could do...
So, after a few hours of trying everything I could with NRT I am unable to unlock the bootloader. When I press vol + and then the power button to select it to unlock, it just stays there...it doesn't do anything and freezes until I hard reset it. No love lost if this is a bricked device, I'd only be out $20. Anyone have any ideas? Thanks ahead of time!
Slight update after playing with it for a while this morning... I was able to get it to show the TWRP splash screen, before it fully loads TWRP, in NRT. But, as always it just hangs there while NRT is "Rebooting your device into bootloader mode..." I'm starting to think it has a bad emmc? I'm not too well versed on hardware, but I've tried nearly every option possible I think. Anyone have any other ideas?
CKrzacz said:
Slight update after playing with it for a while this morning... I was able to get it to show the TWRP splash screen, before it fully loads TWRP, in NRT. But, as always it just hangs there while NRT is "Rebooting your device into bootloader mode..." I'm starting to think it has a bad emmc? I'm not too well versed on hardware, but I've tried nearly every option possible I think. Anyone have any other ideas?
Click to expand...
Click to collapse
If you are using the official TWRP app you then you should use the customized version. The omnirom thread got one you can download: https://forum.xda-developers.com/nexus-10/orig-development/rom-t3045066
Direct link: https://androidfilehost.com/?w=files&flid=205355
So I used NRT to attempt to flash 3.1.1 onto the tablet, it froze on the TWRP flash screen showing version 3.0.2-0. I'm wondering now if the recovery that was on it before I purchased went corrupt? I
Update: Did a manual "fastboot boot "PATH TO 3.1.1-0-manta.img" and same thing....it just gets to the splash screen and freezes....
Another update.... "adb devices" shows it in recovery....yet it just shows the splash screen still. This makes NO sense to me lol.... This is the first I've been able to get adb to recognize it, but the bootloader is locked, nor will it unlock (it freezes), so I feel that it's useless that I've got it this far and yet nothing. Ugh...
Update the bootloader (from google's official images) to latest. then TWRP will boot
Pushing "perm-recovery-signed.zip" to your device:
adb push "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\perm-recovery-signed.zip" "/sdcard/!ReadyToFlash/Root_Files/perm-recovery-signed.zip"
100% /sdcard/!ReadyToFlash/Root_Files/perm-recovery-signed.zip
Hash verifying file transfer:
f63500d8c095c0e749cd78851ba409f8 = Local Hash
f63500d8c095c0e749cd78851ba409f8 = Device hash
+ Verified!
Pushing "openrecoveryscript" to your device:
adb push "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\openrecoveryscript" "/cache/recovery/openrecoveryscript"
100% /cache/recovery/openrecoveryscript
Hash verifying file transfer:
7c02d031e244df4f5a47a7cd3297e53f = Local Hash
7c02d031e244df4f5a47a7cd3297e53f = Device hash
+ Verified!
Rebooting your device into bootloader mode...
adb reboot bootloader
Here's the NRT log. It just hangs with the TWRP splash screen still (after reinstalling the bootloader, then reinstalling TWRP) and won't go back into bootloader. When I hard reboot it, it's back to square one with not being able to boot into recovery (locks up at google logo) or allow oem unlock to process (locks up on the unlock screen when I press power button on "yes").
I know this thread is a few years old, but have you been able to solve the problem? I'd like to use my old Nexus 10 as a WiFi picture frame, but it is bricked in the same way as yours. I cannot get past the google splash screen, bootloader unlock won't work even though it is recognized via fastboot. Flashed latest image and bootloader from google, but did not change anything.
Related
So I tried to update to KitKat 4.4 and was never able to get passed the loading screen. I booted into ClockworkMod Recovery and wiped everything and now the device will not go passed the Google loading screen. The device is no longer recognized when I plug into the computer and I cannot access through Wugs.
I called Google and they are sending out an RMA for this device (I did not tell them it was unlocked) and they are sending out a replacement.
Is there anyway that I can remove ClockworkMod Recovery and re-lock this device without being able to access the device through a computer?
BrianXP7 said:
Whoa, RMA's should be only used for last resort bootloader bricks! Since you still have the bootloader ("Google" logo at startup), hold Power + Volume Down to enter Fastboot mode and try reflashing the factory images. Just to be safer, use the Universal Naked Drivers and skip with bootloader image. Don't forget to have the ADB and Fastboot binaries in the same folder. I wouldn't recommend toolkits as they don't expose new users with these situations.
If you need anything else, let me know. If I completely missed on what you needed, sorry about that.
Also, just as long as the bootloader update isn't interrupted or type "fastboot erase bootloader" you should be fine without an RMA.
Click to expand...
Click to collapse
thanks for the reply.
I am able to boot in recovery mode on the device and this is recognized by Wugs as "ADB - device on". When I attempt any flash, it checks Fastboot status and I receive notification that the "Fastboot device was not found". I cannot find a compatible driver when I am in fastboot mode running on a Windows 7 x64 machine.
Any idea on how I can get this N7 to function, return to stock, or at least remove ClockworkMod and lock the bootloader so I can RMA?
***FIXED***
Update:
I was able to resolve this, here is what I've done in case others happen to have the same issue:
Turn on computer volume, reason being I had mine off and even though it appeared to skip over fastboot with the OTG method, it in fact was enabling for a sec or 2 then moving on as I could hear the USB connection chime.
NOTE: I had to press and hold to the LEFT of the Nvidia symbol until I heard the USB pick up chime, once I heard the chime I released my finger.
Prior to plugging in the power cord, I ran "fastboot boot <yourfilename.img>" and it sits at waiting for device...
Device took it and booted me into TWRP, I then flashed the Unofficial TWRP for the SATV, by choosing Image, then finding the .img that I already had on the internal storage
Rooted with SU, rebooted system and everything is now good to go.
Root, custom recovery and also Fastboot stock menu is back.
---------------------------------------------------------------------------------------------FIXED------------------------------------------------------------------------------------------------------------------
Hello All,
Long time lurker, now reaching out.
Just looking for a little help with my SATV Pro 500gb.
Here is the background:
Out of the box today, booted up and enabled ADB and jumped into fastboot for the bootloader unlock
Process took about 2 hours as the info said it would. Device rebooted, perfect working order.
Decided to flash TWRP for SU install along with possible custom roms, etc.
used this tool:
http://forum.xda-developers.com/shi...l-windroid-universal-android-toolkit-t3291266
Device said "please wait...." in fastboot screen, appeared finished and device rebooted into the the OS.
Here is the problem:
I go into command and adb reboot-bootloader, device reboots, I see the Nvidia logo and it boots into the OS, skips right over Fastboot
Shut it down, attempt the OTG, power cord ~3 secs over and over, hangs at logo and then boots in to the OS.
I reset the device, hoping the recovery OS would reflash the fastboot image, appears not to be the case.
Currently I am stuck with no fastboot access, device boots to OS no problems, but as far as fastboot is concerned I cannot access. Appears something went wrong with using that 1 click tool for flashing recovery.
Now before anyone chimes in, adb reboot-bootloader will not boot into fastboot and I've attempted the HW method listed on Nvidias dev site. Its 100% nogo.
Current State of device:
No fastboot
OS boots no problems
ADB works
No Root
Thanks for everyones look and help!
I just got my Moto G5 Plus today, and ran Motorola's official Bootloader unlock guide.
Upon starting up, I am now receiving an error that says "Your device has been unlocked and can't be trusted. ID: bad key"
I confirmed multiple times that I provided the correct unlock_data and entered the correct unique key provided.
Because of this I cannot flash TWRP.
"(bootloader) Image not signed or corrupt"
What can I do here? Is there a way to re-do the unlock?
Do I have to flash stock back to the phone? I cannot seem to find any guide on how to perform that properly.
Are you sure TWRP didn't flash because it gave me that same generic error (because it's no longer stock recovery) but it had installed fine. Did you try selecting 'Recovery Mode' in the bootloader and see if it loads? Hopefully you're following the rooting tutorial in this forum because you need to follow it closely to correctly gain root.
That 'bad key' message on startup is normal after unlocking and can be removed by flashing another 'logo.bin' as shown in this video, so actually seeing it shows that you probably did unlock successfuly.
Correct, as everyone has stated, this is normal for a bootloader unlocked device. You can flash a logo.bin to make your boot up look better
Sent from my Moto G (5) Plus using Tapatalk
Were you able to fix this? I have a similar problem.
I am also having this problem. Everyone saying this is normal, is wrong.
donjuro said:
I am also having this problem. Everyone saying this is normal, is wrong.
Click to expand...
Click to collapse
The "normal" message once it's bootloader unlocked is "Your device is unlocked and can't be trusted...Your device will boot in 5 seconds." - it doesn't say anything about a "key".
EDIT: oh, and where his said "ID: bad key" mine says "ID: n/a"
Yes I found out my problem was that I was using a later version of twrp and you have to first use an initial build on one of the rooting threads.
I'm having the same issue. Got the unlock key from Motorola and successfully unlocked bootloader from CMD. The phone then booted up as if it were new. I access the recovery mode and get "device has been unlocked and can't be trusted". No other option. I've tried manually and through CMD. I've downloaded all necessary files including the kernel, ADB, fastboot and twrp. Nothing works. Phone operates as if I factory reset it.
I just rooted my Moto G5s plus last night...here were my steps:
1.) Do the Motorola unlock B.S.
I had fastboot.exe and adb.exe from the Android SDK installed
I did find that I had to unlock my phone or adb could not see it
2.) After unlocking, you get the "untrusted phone" screen
3.) Use fastboot to flash a new boot image: fastboot flash boot logo.bin (I built a logo with MotoBootLogoMaker), this gets rid of the untrusted screen
4.) I do have the "bad key" message show up during boot, but it hasn't impacted anything...it is in white, my boot logo is in white, so you don't see it.
5.) Get a copy of SuperSU.zip on your sdcard and load into your device
6.) I installed TWRP (twrp-3.11-sanders.img) to the recovery partition, but that caused an issue: fastboot flash recovery twrp-3.11-sanders.img)
* Recovery wouldn't boot after this, so I successfully booted the image directly with: fastboot boot twrp-3.11-sanders.img
6.) TWRP successfully loaded....
7.) Use TWRP to install SuperSU.zip (this roots the device)
* I wiped the dalvik cache, but that hung and I ended up powering off...but fortunately it didn't brick the device
8.) After reboot, I logged in with "adb shell" and did an "su" to prove I was rooted.
9.) I replaced bootanimation.zip with one more to my liking than the Lenovo one (/system/media/bootanimation.zip I think was the location)
That was it...
After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
CanIHelp said:
After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-p9lite/how-to/unified-help-thread-huawei-p9-lite-t3649152
Post 5. Unbricking EMUI 5. Don't take for granted it will work, but considering FRP is locked, this is the only way not needing a unlocked bootloader.
Doesn't work. It's still stuck at the "Your device is booting now..." under the vmall link screen.
Isn't the 3-button method counting on the original recovery being in the recovery partition?
I only have the second recovery working (that eRecovery which only lets you "download and install the latest recovery and system"...and doesn't do anything).
Is there a way to override the frp lock? I saw a couple of tools online claiming to do that, but none worked. I haven't tried DC-Unlocker. If I'm gonna pay for it, might as well go to a service
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Plug your phone on computer.
You see yellow advice? Appears automatically.
Juste after this advice, tip "fastboot reboot bootloader".
After, unlock your bootloader again "fastboot oem unlock YOUR_OEM_CODE"
Ok now shutdown and hold buttons for boot to TWRP recovery, if not appears, flash it on "fastboot flash recovery recovery.img"
Warning command not allowed on fastboot is 90% time du at bootloader unlocked (even if he says it's good)
dariomrk said:
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Click to expand...
Click to collapse
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
CanIHelp said:
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
Click to expand...
Click to collapse
No problem mate, nice to hear you did it without problems.
Hi all,
I had recently unlocked my bootloader on my moto e4 (woods), installed twrp, and install magisk, and everything was going smoothly. Until recently, where i had a OTA update for the device. Me not thinking, i installed the update and then my device refused to boot to system, and only rebooted to twrp. I tried everything to get it to boot, but it just didn't.
I today, found on another thread, that you could reinstall the stock firmware onto the device, and followed the instructions, which were basically just running 'fastboot erase ----' and 'fastboot flash ----'. Everything was going well, until i came to system, which failed to install. I then tried restarting the device (because i wasn't thinking properly), and now the device will show the boot screen for approx 10 seconds then loop again. It has the message of ">device unlocked" at the bottom of the screen, and the moto logo and "powered by android writing on it". I have tried to access the recovery and bootloader on the device by using the hardware buttons, but there was no luck when i was doing it. It would just carry on with it's bootloop. I also tried plugging the device into a windows system, and ran 'adb devices', and 'fastboot devices' but nothing was being picked up. I also checked device manager, and no new devices were being shown.
I am 99% sure that i have indeed hard bricked the device, but i am turning to the amazing people of XDA devs for any help or tips that they can give to possibly get the device back and running.
Anything will be useful, since i can't make the device any less usable now anyway.
Thank you to anyone that replies
just Google the model number and get the original stock firmware and use SP flash tools and the scatter file took a hit to the latest firmware then use fastboot commands to unlock the bootloader flash custom recovery and root the device