Related
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.
Greetings everyone! I have currently two issues where I can't get away from.
I'm currently unable to access download mode and recovery Mode due to Secure Booting Error 1003.
I can't format the phone either.
Only thing that I can do is access fastboot mode via doing recovery mode buttons method.
[470] fastboot_init()
[470] Loading keystore failed status 5 [570] USB init ept @0x8f20b000
[590] udc_start()
[690] -- reset --
[690] -- portchange --
[810] fastboot: processing commands
This is what appears on phone. At first I tried to root phone, didn't work, then I downgraded the phone and was able to root. Then I tried to root TWRP so I could flash the ROM and everything but somehow something didn't work that made me get secure boot error 1003. I tried to use flashify to flash images that probably weren't correct thus led me to be stuck on fastboot now. I downloaded SDK and ADB and I tried to erase laf.img and then try oem unlock with no success because it gave wrong command error.
I also tried LGUP method, the phone while on fastboot mode couldn't be found, even then when phone was on Android 5.0 rooted, It was unknown. So that method apparently didn't work out.
I'm still stuck here. Any help? Any ideas would be highly appreciated.
Try flashtool 2014 . Might not work with mm or higher kdz
I unbricked my G4 when lgup wouldn't recognise it and flashtool worked
Jason_L said:
Try flashtool 2014 . Might not work with mm or higher kdz
I unbricked my G4 when lgup wouldn't recognize it and flashtool worked
Click to expand...
Click to collapse
I gave a shot and it was unsuccessful. It says this:
The phone is disconnected from PC.
Connect the USB cable and wait a moment. Press the Retry button to resume the setting analysis process.
i got that spontaneously when i try to reboot and factory reset.It wasnt rooted so after i remove battery it works fine i'm not sure about that.
Its a 64 gb A1 variant. Everything was stock. It was on stock pie (update via OTA). I never tried unlocking bootloader as well as flashing custom rom.
3 day ago when i using it,suddenly it turn off and stuck at android one logo. I can go fastboot mode by pressing power+volume down.
I try to flash stock rom using mi flash tool,but as my bootloader is locked it show error. :crying:
Please help me out,it is my daily driver. :crying:
Use the fastboot oem unlock command and see what it does.
If the command is succesfully will trigger the factory reset of devices, but maybe you`ll get it to work.\
If the above command not working, maybe you can try to factory reset from recovery if you can boot into it.
In the end maybe a fastboot flash will do the trick.
punktnet said:
Use the fastboot oem unlock command and see what it does.
If the command is succesfully will trigger the factory reset of devices, but maybe you`ll get it to work.\
If the above command not working, maybe you can try to factory reset from recovery if you can boot into it.
In the end maybe a fastboot flash will do the trick.
Click to expand...
Click to collapse
I found this thread after i post this. Hope this will help me, though i am not try yet. I will update what happen. https://forum.xda-developers.com/showpost.php?p=78378088&postcount=43
use miunlock tool to unlock bootloader if you're not familiar with fastboot commands and as punktnet said unlocking bootloader will reset your device and erase your userdata and internal storage then maybe your device works fine if not then reboot it again in fastboot mode and flash stock firmware.
Facing similar issue. Am able to flash via test point method however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Any other solution?
WORKMEISTER said:
Facing similar issue. Am able to flash via test point method however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Any other solution?
Click to expand...
Click to collapse
This occurred to me today aswell :c I tried wiping all the data from recovery but the phone couldn't even end to wipe all. My phone went into a "erasing" screen for almost 1 hour when I decided trying to hold the power button, it rebooted but I still got into the bootloop :l my Xiaomi Mi A1 is not unlocked for bootloader so I can't flash it. I also tried with the mi unlocking but didn't go past 50% when it launched an error. Guess I'll die.
***SOLVED***
so after installing everything following a guide, where as i couldn't open app store after i was done. i decided to uninstall everything and it went great until i restarted my phone after doing so, now i can't exit bootloader and i can only turn my phone off when it's not plugged in, anything returns to bootloader. I have tried several things here to fix it, nothing works as it doesn't show up in the adb commands.
please help me figure anything out
EDIT: I think the issue is that i deleted the cache and then proceeded to reboot my device
EDIT2: and i just locked the oem lovely
EDIT3: i did it
So you are stuck on the fastboot screen? ADB doesnt work on the fastboot screen, only fastboot commands. Careful what guides you follow, and make sure you don't miss any steps. From the fastboot screen you could use the fastboot ROM.
If that doesn't work you can use the MSM tool.
Remember the fastboot ROM will put OOS back on your phone. MSM will put OOS back on your phone and relock the bootloader. So not sure what you were trying to do but you may try and boot TWRP from fastboot one more time if thats what you were trying to do.
OhioYJ said:
So you are stuck on the fastboot screen? ADB doesnt work on the fastboot screen, only fastboot commands. Careful what guides you follow, and make sure you don't miss any steps. From the fastboot screen you could use the fastboot ROM.
If that doesn't work you can use the MSM tool.
Remember the fastboot ROM will put OOS back on your phone. MSM will put OOS back on your phone and relock the bootloader. So not sure what you were trying to do but you may try and boot TWRP from fastboot one more time if thats what you were trying to do.
Click to expand...
Click to collapse
when ever i try to boot the immage it says "PS C:\adb> fastboot boot twrp-3.4.0-0-fajita-Q-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.723s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.731s"
but i'll try to use the MSM tool
EDIT: doesn't seem to work either, same issue "Load Error"
The error means something is wrong, likely just one partition, but Ive never taken the time to figure out which one, just always fixed it with the fastboot ROM. I will say Im not a fan of the 3.4.x TWRP (for this device), I removed it from my LOS guide for several reasons. It still has issues in my opinion.
For the MSM tool, if it doesnt work its almost always a driver issue. Just for clarification for the MSM tool its not supposed to be in fastboot, nothing will be on the screen while using the tool (the phone starts off).
For reference, taken from my guide here:
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
OhioYJ said:
The error means something is wrong, likely just one partition, but Ive never taken the time to figure out which one, just always fixed it with the fastboot ROM. I will say Im not a fan of the 3.4.x TWRP (for this device), I removed it from my LOS guide for several reasons. It still has issues in my opinion.
For the MSM tool, if it doesnt work its almost always a driver issue. Just for clarification for the MSM tool its not supposed to be in fastboot, nothing will be on the screen while using the tool (the phone starts off).
For reference, taken from my guide here:
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Click to expand...
Click to collapse
so i have successfully done the msm, but from here how do i enter stock os, because when ever i try to search for updates it says none found even though i am 9, is it because my oem is unlocked? or am i still rooted? whenever i try to update it using local upgrade it says fail
edit: just read that i should try to update to 9.0.17 and then to latest
OhioYJ said:
The error means something is wrong, likely just one partition, but Ive never taken the time to figure out which one, just always fixed it with the fastboot ROM. I will say Im not a fan of the 3.4.x TWRP (for this device), I removed it from my LOS guide for several reasons. It still has issues in my opinion.
For the MSM tool, if it doesnt work its almost always a driver issue. Just for clarification for the MSM tool its not supposed to be in fastboot, nothing will be on the screen while using the tool (the phone starts off).
For reference, taken from my guide here:
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Click to expand...
Click to collapse
Heya, you sound really experience with regards to this so I was hoping you could save me some time by telling me if I should even bother wasting trying to revive my brick.
I've got a op7pro stuck on the bootloader unlocked screen. Research reveals I hosed it by flashing twrp to the wrong partition. Flashed it to boot instead of recovery.
I've tried to get MSMTool to recognize it by pressing volume buttons on powerup but it hasn't so far. That's pretty much the last resort isn't it? If MSM won't recognize it then I'm outta luck?
Device Manager will see my phone as an unknown device when I boot holding down the volume buttons, but MSMTool and the all-in-one tool won't.
The other time I unbricked using MSMTool I got it to work pressing volume buttons on boot and win10 immediately recognized the device as highspeed qualcomm ports.
But that was on a boot loop, this is stuck on bootloader, a far graver problem it seems. Thanks for whatever advice you could offer this hapless modder.
Hello,
yesterday I accidentally entered fasboot mode by pressing the button combination on boot.
My phone is now stuck in fastboot mode and I can't figure out how to get out.
I've installed fastboot and the appropriate drivers on my computer (W10), but if I try 'fastboot reboot', the phone boots straight into fastboot mode. I tried formatting the cache and rebooting, but still got the same result. If I switch off the phone by holding the power button and then turning it on again (tried with every button combination), it only boots into fastboot. I even tried letting the phone run out of power, but when I charged it a bit and switched it on again, it went to fastboot again.
My phone is unlocked and rooted and has Havoc OS installed.
Any help is greatly appreciated.
Have you tried fastboot continue? You may want to spam that command for good while.
It should be written on the screen how to get out of fastboot mode, press and hold power button to shutdown the device. How exactly can't you boot to the system?
XDHx86 said:
Have you tried fastboot continue? You may want to spam that command for good while.
Click to expand...
Click to collapse
Haven't tried it before.
After typing it, I get an error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: 00000050)
finished. total time: 0.316s
What is located at 00000050?
I probably have to reinstall something, I'm just not sure what. Recovery/Bootloader/OS ?
XDHx86 said:
It should be written on the screen how to get out of fastboot mode, press and hold power button to shutdown the device. How exactly can't you boot to the system?
Click to expand...
Click to collapse
Yes, it says to hold the power button. This switches the phone off, but after starting it again it automatically goes into fastboot.
Thanks for your replies, Slllingy
Slllingy said:
Haven't tried it before.
After typing it, I get an error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: 00000050)
finished. total time: 0.316s
What is located at 00000050?
I probably have to reinstall something, I'm just not sure what. Recovery/Bootloader/OS ?
Yes, it says to hold the power button. This switches the phone off, but after starting it again it automatically goes into fastboot.
Thanks for your replies, Slllingy
Click to expand...
Click to collapse
Your device is bricked as it can't load or authenticate the boot image, you need to unbrick it.
Flashing the stock image should work. Of course don't forget to backup your data through TWRP.
I downloaded the stock firmware from ASUS, but it's a zip file and the only .img contained is boot.img.
I tried erasing all the partitions (chache, data, system, boot, recovery) and flashing the stock boot.img (from ASUS) and the lastest TWRP recovery img (specific to my phone).
I no longer get the "Failed to load image from partition..." error, but after fastboot reboot the screen turns off, then it turns on, warns me that my bootloader is unlocked, shows the android logo, then the asus logo, then it turns off again, then on again, briefly shows the androif logo and goes straight into fastboot. Basically the same happens when I manually switch the phone off and turn it on or with fastboot continue.
I can not access my reccovery.
Where can I find a sytem.img file to flash with fastboot?
Or is there any other way to unbrick my phone?
Thanks again, Slllingy