i'm trying to root my J320v but i am unable to flash the boot or recovery images. I have debug mode on, usb debugging enabled, OEM unlock enabled, the official Samsung USB drivers installed. Odin can detect the device but cannot write to it. I'm guessing the bootloader is still locked but from everything i can find the OEM unlock is supposed to disable that.
I'd like to install android 12 on this device so I can use it for app development, at the bare minimum android 10+ so i have access to scoped storage.
USB cable issue. Also turn off FRP lock by removing your google account on ur J3.
Also enable OEM unlock
Verizon / AT&T devices are known as they have locked bootloaders
Related
Hey all,
So Ive tried to unlock my bootloader but its not working, ive followed the steps from this site to unlock it but its stuck on the unlock bootloader screen. I have two options to choose from yes or no I click yes but it doesnt work, yet I click no and it takes me back to choose from fastboot, recovery and normal. My phone is a Alcatel Pixi 4.
I have enabled developer mode enabled usb debugging. I also have confirmed the RSA fingerprint for the computer. Also I have enabled OEM unlock in dev settings. This is what my cmd prompt window loooks like. I will also take a photo of my alcatel frozen on bootloader screen.
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>adb devices
List of devices attached
5HQGTCEQCAVS7TTS device
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootloader
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlock
...
This is what my phone looks like that im stuck on.
https://s11.postimg.org/8e2cjxooj/IM...129_172555.jpg
does anyone know why this is happening or know how to fix?
Issue has been solved as the bootloader is unlocked this process is not necessary.
OEM unlocking and USB Debugging enabled.
ADB never finds the phone in my windows 10 install no matter what drivers I force it to use. - Tried USB 2 and 3.
Fastboot does find it if I manually start it in fastboot mode, but it can't do anything to it
Fails to write when doing oem unlock
Just sits there if I tell it to write the recovery image.
Phone functions fine, I just want root and a 3rd party rom to be rid of any built in spyware.
Any ideas? any way to root it without flashing then I can just have the twrp app flash it?
Nevermind, found a way around it. This dialpad command made it work
Personmans said:
Hope this will help someone with trouble getting ADB/Fastboot to work. I assume you have a similar environment to me: Windows 10, with working ADB drivers on another device (LG G4 in my case)
Set up LeMax2 in developer mode and enable USB debugging as usual.
Plug in usb and dial *#*#76937#*#* check the box that says "Enable AT Port"
The device should immediately give you the approval message for USB debugging.
Note: This will not stick after a reboot.
Once I had this working, I did an adb reboot recovery, but fastboot still did not work. With the device connected and at the stock recovery screen, I had to open device manager, delete the LeMax device, and allow it to detect again. Finally it appeared in fastboot devices and I was able to flash recovery.
Click to expand...
Click to collapse
Hello there. I have a Nokia 6.1 with android 9.0 and i tried to root it. I enabled the developer mode, then enabled usb debugging.
But when i tried to unlock the bootloader, i couldn't because the OEM unlocking option stays greyed out on off. So when i installed adb and fastboot, i tried to boot by adb reboot bootloader but the fastboot can't do anything because it says device is locked.
I even factory reset the device, nothing. Same thing.
What should i do? Preferably not the paid unlock...
Thanks in advance.
Try this (It will wipe the phone, so create a backup of all important files before proceeding):
1. Connect your phone to your PC with an USB cable (make sure you have activated USB debugging in developer options)
2. Run adb
3. Type in adb reboot bootloader
4. Once your phone has rebooted type in fastboot flashing unlock or fastboot oem unlock
You should have unlocked your bootloader and you should be good to go, if it doesn't work then you'll need an unlock key, which unfortunately you'll have to pay for
If you think that you have misunderstood some steps then feel free to reply
I found a tool for windows called "fastboot reset tool v1.2" The tool sees the phone but fails because it couldn't write to folder I don't know how to tell if the bootloader's locked or not When I reboot to bootloader it just says fastboot mode after that but since the phone's frp locked i can't enable usb debugging means I can't connect by adb How can I proceed on Windows or Linux?
You can use this tutorial to bypass frp. The tool is created by Mohit KKC.
I have this phone and now it wont boot. Im thinking there is no OS to boot. It tries and says DM varity disabled at top of screen then says software cant be checked for corruption /bootloader unlocked. When in bootloader there is no recovery to boot into as well when plugged into desktop . ADB devices command is not seeing it. So my question is where do I start to install recovery and make PC (adb/fastboot) recognize device. If I could get adb to identify device shouldn't I be able to fastboot boot (twrp-disc.img) then flash twrp.zip then reboot bootloader and flash factory ROM and kernel or custom? Hate if I sound like a noob im learning all I can. Any help is greatly appreciated!
ADB, Fastboot & Recovery are 3 completely things independent from each other:
ADB program deals with Android OS ( folders / files / settings )
Fastboot program deals with device's bootloader
Recovery is a special bootable partition on device, which contains a recovery application installed in it
If
Code:
adb devices
doesn't show you a connected "device" then either USB debugging isnt enabled or Android OS isn't accessable at all or Android's USB service isn't set to "adb"
If
Code:
fastboot devices
doesn't show you device's mode as "fastboot" then device's bootloader isn't accessable at all.
Back to your "issue", well, it's NORMAL, starting from Android Marshmallow on ALL devices with an unlocked bootloader & disabled "dm-verity" will boot with those warning, so nothing to worry about, and , at the moment it's not possibile to remove those warnings.
When Fastboot is working, then you should be able to boot device into a Custom Recovery, of course only if that is at 100% suitable to the device.