Hi, I'm struggling to root my new OP2 however i've tried to unlock oem as the tutorials say but the screen of fastboot remains like that and nothing changes unless y hard reboot the device and then I go back to the point where I started also i've checked if my device is unlocked and the flag is marked to "true" but i'm unable to install TWRP and Su.
Related
Previously I have unlocked the bootloader using
Code:
fastboot oem unlock
and it worked just fine. Using
Code:
fastboot oem device-info
both the "tampered" and the "unlocked" bit were set to "True".
Recently, and I have no clue why (possibly a program I tried to use for work that ended up not working), both of these bits are now set to "False"
I cannot flash a new recovery using fastboot, though my original TWRP recovery is still there.
I can still adb sideload update my OS, have root access, etc.
Now running
Code:
fastboot oem unlock
reboots into TWRP recovery with no effect on the bootloader status
I have already tried a few things suggested around here to no avail.
The only thing I can think of to do now is to treat it as a hard brick and completely reset everything and install a stock ROM to start from scratch following something like this thread.
If I can avoid this that would be preferable...
I had the same issue. For some unknown reason my partitions were all messed up so I was getting "bootloader locked" every time, witch is basically what they call a hard brick.
I've used that recovery tool and did fresh start with the latest TWRP and a new ROM. All back on track! Working well since over a month now.
I know it's a pain doing a factory reset and all but I think it's the only thing you can do...
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.
SOLVED
I unlocked my bootloader and flashed twrp to recovery (after first temporarily booting to twrp to make sure my bootloader was unlocked), I tried flashing Resurrection Remix, which resulted in some sort of error, I reread the instructions and realized I hadn't factory reset my device (though it was wiped by unlocking the bootloader), and went to my stock system and factory reset it, which seems to have been a huge mistake as now twrp seems to be completely gone and my device isn't getting recognized by adb or fastboot.
I have a small message in the top left of my screen between the boot animation and any boot from power off saying "bad key", fortunately my device is still usable as a stock device but now it seems I've locked my device from ever using a custom ROM now, is this correct?
I realize that I've made some huge mistakes here and should've known better.
Sounds like you should have flashed the dm verity opt encrypt zip. Factory reset is not the step. You were supposed to format data in twrp, format, not wipe.
Did you make any sort of backup before you started flashing ROMs?
Tokoroth said:
I and went to my stock system and factory reset it, which seems to have been a huge mistake as now twrp seems to be completely gone and my device isn't getting recognized by adb or fastboot.
* I have mediatek so excuse some differences but one thing is certain ..if you factory reset ..you RELOCK the bootloader +++ revoke USB debug authorization & turn off OEM unlock
I have a small message in the top left of my screen between the boot animation and any boot from power off saying "bad key", fortunately my device is still usable as a stock device but now it seems I've locked my device from ever using a custom ROM now, is this correct?
I realize that I've made some huge mistakes here and should've known better.
Click to expand...
Click to collapse
* I have mediatek so excuse some differences but one thing is certain ..if you factory reset ..you RELOCK the bootloader +++ revoke USB debug authorization & turn off OEM unlock
*When you say you can use your phone as stock nothing is wrong ....
You can flash full stock & start process over ..by enabling Dev settings then OEM unlock & debug
Connect to computer & give adb authorization
THEN YOUR PHONE WILL BE RECOGNIZED
# very important#
If you factory reset stock it usually relocks bootloader
++ AS madbat pointed out you will need to flash the noverity.zip when booting into twrp the first time.
Thanks for the help, I should've read a bit more before diving in, thank you for the pointers, I now have RR up and running finally!
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
TL;DR: Do I need to unlock OEM bootloader to boot into TWRP on the SM-J530f?
A friend of mine own a Samsung J5 (J530F), and she broke her screen (of course, USB debugging is not enabled), and she really would like to recover some files & contacts. I tried to blindly unlock the screen with an OTG keyboard, but for now, I'm not very successful (it's even harder when you never used a phone to blindly unlock it ), so I also tried to flash this TWRP recovery. (my hope is to get access to ADB shell after booting TWRP) Using heimdall, I didn't see error that looks fatal, just a minor (?) error during the session ending:
HTML:
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
However, after rebooting with Power+Volume up+Home, nothing special happens (at least given that I can't see the broken screen). And "adb shell" can't find the device.
So do you think I just did something wrong, or do I really need to unlock the bootloader to boot TWRP on the SM-J530f? If I do need to unlock the OEM, is there some signed image that could let me boot something with ADB access? If not, any other idea?
Thanks!
Odin
Hey !
I don't really understand but I could advise you to use Odin for Samsung instead ADB shell (if you use it, think to uncheck auto reboot). If you don't use it maybe try to install samsung usb drivers.
For the OEM unlock, It depend of your android version. I am not sure but you can unlock it in the dev options in the settings in Android Oreo or Nougat but not in Pie or Ten.
In theory, you can access to the device storage in recovery mode by using a computer.
I think it is all,
Cheers.
Thanks for your answer, but unfortunately I can't access the dev settings because the screen is broken. If I could go in dev settings, I'd just enable usb debugging directly.