Hey guys, I've been trying to unlock my bootloader so that I can try and root my Maven 3 via Magisk. The problem is, I can't get into the bootloader. If I try to reboot to the bootloader from recovery mode, it just restarts like normal. Same thing when I try using adb commands in the cmd prompt. I am on Windows 7.
I think it could be unlocked trought EDL mode. But we need some expert help
I unlocked my phone with at&t but I think it only unlocked the SIM.
I enabled usb debugging and oem unlock, but when I issue the command (in ubuntu term)
adb reboot bootloader
Click to expand...
Click to collapse
is just boots into the android system.
Any clue on what to do?
I have the same question - bootloader mode will not load when I issue "adb reboot bootloader", nor will it go into bootloader when I go into recovery mode (via POWER + VOLUME UP) and then I choose the "Bootloader" option. The phone just boots into the system. When I use "adb reboot recovery" it does go into recovery mode, and I am able to get a shell and copy files via adb just fine. I am using the latest platform-tools.
This is a ZTE Z835 (Maven 3), AT&T, carrier unlocked phone.
I don't think there is a bootloader... I have not found any fastboot-compatible mode on this device nor have I heard anyone else find one. You have FTM mode (Power + Volume Down) and EDL mode (adb reboot edl). EDL mode lets it work with QFIL, and with QFIL, you can literally dump and modify any partition on the device you want... I'm not sure what else you want. There's a new method for unlocking the bootloader https://www.xda-developers.com/unlock-bootloader-zte-phones/. I found that my devinfo partition was already unlocked, but you may need to check. I'm going to try and figure out how to create a recovery.bin partition able to be flashed in QFIL.
Related
Hey, I'm on A2017U stock B19 bootloader unlocked,
I want to backup my stock recovery and boot using axon7tool (I want to flash twrp after that),
When I type: "adb devices" I get my device number and next to it: "unauthorized",
And when I type "adb reboot edl" I get: "error: device unauthorized."
USB debugging enabled.
What am I missing?
(also when I try to go to edl mode (vol up + vol down + power) nothing happens...)
Thanks
I think u need to be root in order to backup those files using adb and you have to have the bootloader unlocked in order to root even tho theres a thread showing how to root without bootloader unlocked
Thanks,
My bootloader is unlocked...
Is there any other way to backup stock recovery and boot before flashing twrp?
Hello, do you have the proper drivers installed for the phone usb wise and in edl mode it won't do anything, that's normal.
Hi, Thanks,
I think so, as I say, it does recognize my phone number on "adb devices" , and I successfully unlocked my bootloader using fastboot
Hello everyone,
So I've read that I can re-lock the bootloadder and tried to do it.
First I have flashed b10 and flashed the su so I wont loose TWRP. I entered fastboot with adb and then I typed fasstboot oem lock, I got a message on the pc with ok.
Since then I cannot boot to the phone.
The phone shows the zte logo for 0.5 seconds but not booting and with constant red led.
Tried power + vol up, power + vol down, all three buttons, vol up + vol down and then connect to pc - nothing at all. The phone wont get past this 0.5 second zte logo.
In all connections I have listed above the phone shows in device manager as QUSB_BULK. At first it was with yellow acclamation mark and then I installed the zadig driver. Now it is connected "normally".
What can I do?
Please refer me to the right tutorial or guide me.
Thanks
I heard that it is not recommended to relock (although possible) unless strict necessity (RMA, sale...) due to risks.
This said, I suggest two methods:
Method A)
Revert back to bootloader unlocked so you will be back as before.
Your current situation with recognized QUSB_BULK driver is good.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot bootloader" command: anything changed on screen or Device manager sound?
Then try "fastboot devices" command: if you get answer, then OK you are in fastboot mode.
And in fastboot mode you can now issue the command "fastboot oem unlock" to unload the bootloader again.
Then the phone should be back operational again as before.
Method B)
Try to get to recovery (either stock or TWRP preferably). When the phone can boot to recovery
(TWRP if possible), you are saved since with TWRP you can reflash everything.
Your current situation with recognized QUSB_BULK driver is good for (re)flashing recovery in EDL mode.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot recovery": does it boot to recovery?
If not, then my guess is that since the bootloader is locked, unsigned TWRP (as the one you used since normally nobody should use tenfar's signed
TWRP for daily operation) is not accepted.
- so you need to reflash tenfar's signed TWRP mentioned in this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
using EDL mode ("adb reboot edl", then "axon7tool -w recovery" etc..., with file recovery.bin = tenfar recovery).
tenfar's signed recovery is accepted even if the bootloader is locked.
- after that you should be able to boot TWRP (tenfar), by using 'adb reboot recovery', or with Power + Volume-Up: your phone is now under your control!
(reunlock, upgrade TWRP, flash ROM, root...)
dnlilas said:
I heard that it is not recommended to relock (although possible) unless strict necessity (RMA, sale...) due to risks.
This said, I suggest two methods:
Method A)
Revert back to bootloader unlocked so you will be back as before.
Your current situation with recognized QUSB_BULK driver is good.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot bootloader" command: anything changed on screen or Device manager sound?
Then try "fastboot devices" command: if you get answer, then OK you are in fastboot mode.
And in fastboot mode you can now issue the command "fastboot oem unlock" to unload the bootloader again.
Then the phone should be back operational again as before.
Method B)
Try to get to recovery (either stock or TWRP preferably). When the phone can boot to recovery
(TWRP if possible), you are saved since with TWRP you can reflash everything.
Your current situation with recognized QUSB_BULK driver is good for (re)flashing recovery in EDL mode.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot recovery": does it boot to recovery?
If not, then my guess is that since the bootloader is locked, unsigned TWRP (as the one you used since normally nobody should use tenfar's signed
TWRP for daily operation) is not accepted.
- so you need to reflash tenfar's signed TWRP mentioned in this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
using EDL mode ("adb reboot edl", then "axon7tool -w recovery" etc..., with file recovery.bin = tenfar recovery).
tenfar's signed recovery is accepted even if the bootloader is locked.
- after that you should be able to boot TWRP (tenfar), by using 'adb reboot recovery', or with Power + Volume-Up: your phone is now under your control!
(reunlock, upgrade TWRP, flash ROM, root...)
Click to expand...
Click to collapse
I'll try to do it but yesterday tried to go to edl or recovery in cmd no device found. Tried to flash recovery but it hangs on "waiting for device" so I don't thing I can get to these edl, recovery, fastboot status.
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
dnlilas said:
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
Click to expand...
Click to collapse
I'll try all these guides and update with results
dnlilas said:
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
Click to expand...
Click to collapse
So for sure I'm doing something wrong. Can you please guide me with this tool?
Ironically you helped me unlock the bootloader and I need your assistance relocking it.
Edit: I have the 3 files backed up from the unlocking procedure they should help no?
The phone is not recognized in any adb status edl or fastboot
I don't think you can have a modified recovery partition and a locked bootloader. As I understood it, fastboot oem lock will fail or result in brick if you try to flash anything other than authorized files. Can anyone confirm that they have successfully locked their bootloader and retained TWRP?
QuantumFluxx said:
I don't think you can have a modified recovery partition and a locked bootloader. As I understood it, fastboot oem lock will fail or result in brick if you try to flash anything other than authorized files. Can anyone confirm that they have successfully locked their bootloader and retained TWRP?
Click to expand...
Click to collapse
I don't want to keep twrp or anything. I want to sell the phone so all I want.t is to go back to locked stock phone.
I cannot boot to recovery or fastboot or edl. If I could I would use miflash and flash b10 and be done with it
I think that the initial problem arose when you flashed SU and tried to relock the bootloader with TWRP installed
What does Windows Device Manager show when you connect the phone to your PC?
Update: sorry bud. I totally missed that bit in your OP. DOH! Will update.
Update:
Have you seen this?
https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990
https://forum.xda-developers.com/showpost.php?p=70948893&postcount=28
Sorry that I can't be of more help...
I think what went wrong with my device is that after flashing stock b10 I flashed su so I won't lose twrp. Now when I tried to lock the boot loader made a conflict as I could not have locked bootloader and this version of twrp (for unlocked device). Now I just need to find a way to flash stock recovery (I have a backup from the unlocking procedure) without edl or fastboot as I cannot seem to find a way to enter these states (cause I have no recovery) I'm hoping it makes sense (pretty early in the morning)
So no one can help?
I can't believe the phone is beyond repair
@ItsNewDroid
Sorry I do not have solution, just some idea.
It "seems" that you cannot boot to either system, recovery, bootloader, EDL! adb/fastboot commands are not recognized.
There is still hope since your phone is still recognized somehow as QUSB_BULK (not unknown device) with Zadig driver under USB device.
So you can try to uninstall Zadig WinUSB driver and use Qualcomm bulk drivers so that the phone appears under COM port as Qualcomm HS-USB QDLoader 9008.
If you get 9008 then you are in EDL mode, and MiFlash could be used to flash.
Qualcomm bulk drivers, MiFlash... are available from Download center:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
The problem is to find available "EDL packages" recognized by MiFlash to flash.
These packages could be stock recovery, signed TWRP, or full ROM (any version, MM, or Nougat).
This would allow booting to either recovery or system.
The problem is that I did not see many such packages for A2017G, but only for A2017U.
You may have to ask other members how to build such "EDL packages" (for ROM, sometimes it is called "fastboot ROM").
@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
Edit:
Miflash is not recognized in any key combination.
Edit 2: So somehow I booted to fastboot. My boot loader is LOCKED!! What to do now?
ItsNewDroid said:
@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
Edit:
Miflash is not recognized in any key combination.
Click to expand...
Click to collapse
Oh no, you unfortunately got the dreaded DFU (device firmware mode).
Looks like it a serious brick. Some topics and articles:
https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
https://community.zteusa.com/thread/14699
https://www.reddit.com/r/Axon7/comments/5oqgfj/a2017g_bricked_cannot_get_past_dfu_mode/
https://www.youtube.com/watch?v=nqF3nr3y-Eg
@dnlilas
Man there are changes!
So somehow I booted to fastboot. My boot loader is LOCKED!! What to do now?
Excellent! Try to remember how you get to this menu.
Does "adb devices" command recognized? Status "xxx recovery"?
Of does "fastboot devices" recognized? If yes => you are in fastboot mode. Then you can try to unlock (reverse lock operation) with:
"fastboot oem unlock"
It should ask on phone to erase data (like factory reset). Then say yes.
Edit: the screen capture you took is the bootloader menu (equivalent to come into with "adb reboot bootloader").
When in bootloader, I believe you can use Volume-Up and Volume-Down to navigate (to go to recovery, system, bootloader or other mode). Validate with Power button. It is important to remember how to get to this bootloader menu.
dnlilas said:
Excellent! Try to remember how you get to this menu.
Does "adb devices" command recognized? Status "xxx recovery"?
Of does "fastboot devices" recognized? If yes => you are in fastboot mode. Then you can try to unlock (reverse lock operation) with:
"fastboot oem unlock"
It should ask on phone to erase data (like factory reset). Then say yes.
Click to expand...
Click to collapse
I held the 3 buttons not connected to power or pc. As soon as I felt the vibration before zte logo I let go of the vol up button and it booted to fastboot.
I dont want to unlock the bootloader I want to sell the phone ( this is the reason I came to this situation) I tried to boot to recovery from this menu but it could not.
My guess is that I have twrp recovery and as the bootloader is locked it can not boot.
I need either a twrp for LOCKED bootloader or a stock recovery.
I'm searching the forum but could not find.
You are a wizard! Every time you reply I have good news :good::laugh:
@ItsNewDroid
Download tenfar's signed TWRP here:
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446 (download center https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Important: check md5 6eeb1a9d02470a840bc68019184d9a72
A2017G-TWRPrecovery3.0.2.2tenfar.img
to insure correct download.
Note: tenfar's signed TWRP can be flashed even with locked bootloader, using fastboot in EDL mode (bootloader mode).
Important: I believe you need to switch back to Zadig driver first so that axon7tool used below could work.
The most important thing is that "fastboot devices" command must be recognized while you are in EDL (bootloader) mode.
In the directory where resides axon7tool (axon7tool-1.5-win64.exe https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379),
make a copy of it with the name recovery.bin:
copy A2017G-TWRPrecovery3.0.2.2tenfar.img recovery.bin
Put your phone in bootloader mode (EDL mode) as before, then verify that "fastboot devices" command is answered correctly with your device id.
If OK, then issue the command:
axon7tool-1.5-win64.exe -w recovery
If everything is OK, this will write tenfar's TWRP signed recovery and phone reboots (I believe so).
Immediately Use "Power and Volume-Up" until ZTE logo: it should then boot in recovery (TWRP, tenfar version 3.0.2-2).
Good luck to you!
dnlilas said:
@ItsNewDroid
Download tenfar's signed TWRP here:
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446 (download center https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Important: check md5 6eeb1a9d02470a840bc68019184d9a72
A2017G-TWRPrecovery3.0.2.2tenfar.img
to insure correct download.
Note: tenfar's signed TWRP can be flashed even with locked bootloader, using fastboot in EDL mode (bootloader mode).
Important: I believe you need to switch back to Zadig driver first so that axon7tool used below could work.
The most important thing is that "fastboot devices" command must be recognized while you are in EDL (bootloader) mode.
In the directory where resides axon7tool (axon7tool-1.5-win64.exe https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379),
make a copy of it with the name recovery.bin:
copy A2017G-TWRPrecovery3.0.2.2tenfar.img recovery.bin
Put your phone in bootloader mode (EDL mode) as before, then verify that "fastboot devices" command is answered correctly with your device id.
If OK, then issue the command:
axon7tool-1.5-win64.exe -w recovery
If everything is OK, this will write tenfar's TWRP signed recovery and phone reboots (I believe so).
Immediately Use "Power and Volume-Up" until ZTE logo: it should then boot in recovery (TWRP, tenfar version 3.0.2-2).
Good luck to you!
Click to expand...
Click to collapse
So this is the new situation: adb devices phone is not recognized. Fastboot devices device IS recognized. Issuing axon7tool - w recovery I get device not connected failed to connect. Any idea?
I tried with different drivers etc. but its just don't work, i downloaded TOOL ALL IN ONE, but this said that device was found but not said what or which device, only when phone is normally started i see it on the list of "adb devices" and in TOOL ALL IN ONE. Please help thanks in advance =)
Fastboot is an entirely different mode from adb, and as such it requires a different tool. In the console there is a command "fastboot", which is what you need to use to interact with the phone in fastboot mode. You can boot into fastboot mode from power off with the USB to computer plugged in by holding Volume Down, or it might be possible with TOOL ALL IN ONE, I haven't used it much.
Some basic commands:
fastboot flash unlock path/to/unlock.bin # This will flash the unlock bin
fastboot getvar unlocked # This will check if the device is unlocked
fastboot reboot # This will reboot the phone into normal mode, since powering off by holding the power button is a pain
To flash TWRP, there's a more advanced process with some specific requirements, but I'd be happy to share those if wanted.
mwsundberg said:
Fastboot is an entirely different mode from adb, and as such it requires a different tool. In the console there is a command "fastboot", which is what you need to use to interact with the phone in fastboot mode. You can boot into fastboot mode from power off with the USB to computer plugged in by holding Volume Down, or it might be possible with TOOL ALL IN ONE, I haven't used it much.
Some basic commands:
fastboot flash unlock path/to/unlock.bin # This will flash the unlock bin
fastboot getvar unlocked # This will check if the device is unlocked
fastboot reboot # This will reboot the phone into normal mode, since powering off by holding the power button is a pain
To flash TWRP, there's a more advanced process with some specific requirements, but I'd be happy to share those if wanted.
Click to expand...
Click to collapse
Yeah, so I wanted to flash TWRP but it doesen't seem to work i did what was said in many guides but maybe if you tell me how to do it, it will work =) Thanks
So i tried to flash TWRP with the TOOL ALL IN ONE, everything was okey but then error happened called "Unknown device"
First of all, which version of G6 do you have? The US997 one, or the H870?
mwsundberg said:
First of all, which version of G6 do you have? The US997 one, or the H870?
Click to expand...
Click to collapse
H870
For H870 I'm not entirely sure, but I know that for the US997 you have to do a special procedure to make it permanent. Make sure you back up everything first, too.
With the phone in fastboot mode and a computer connected with fastboot installed and the twrp zip downloaded as "twrp.zip" (or whatever you want):
Make sure the bootloader is unlocked: fastboot getvar unlocked (should return "yes" or "true").
Flash the recovery: fastboot flash recovery twrp.zip (replace twrp.zip with the relative or absolute filepath/name).
Unplug the phone from the computer and reboot into recovery by holding Power and Volume Down. When the logo appears, lift your finger off the power button briefly and then continue pressing.
When you get to the factory reset menu hit yes twice, then the phone should boot into twrp (it may flash the LG logo, I've had different behavior on different phones. You won't need to hold the Power-Volume Down combo any more).
In twrp, swipe to allow modification, then in the Wipe menu select Format Data (and enter yes). This will wipe the phone, so make sure everything was backed up beforehand.
From the main menu go to the Reboot menu and select Recovery.
Here it might vary from the US997. Below are suggestions which I think are needed to have it work.
Download the no-verity-opt-encrypt zip, and connect the phone to the computer.
Once it's rebooted into recovery mode: adb push path/to/no-verity.zip /sdcard/
Then from the install menu in twrp install the zip.
Reboot into System from the reboot menu on the homescreen of twrp.
That should do it all.
Here is my situation: I have a A2017U that was running on LOS 14.1 with an unlocked bootloader. The charging pins are wonky and I have to RMA the unit. I did find @DrakenFX files to restore to stock B35, but haven't been successful in relocking the bootloader using the toolkit and other methods. I tried downgrading to B19 using the toolkit but the phone is not recognized in EDL mode. Any help would be greatly appreciated.
@parmar.saab
after all that, what's your current situation?
* you still have twrp
* are you full stock
* did you install QCom drivers? (This is needed for the device to be seen in EDL mode)
post a screenshot of your windows machine " Device Manager " , AFTER booting to EDL
DrakenFX said:
@parmar.saab
after all that, what's your current situation?
* you still have twrp
* are you full stock
* did you install QCom drivers? (This is needed for the device to be seen in EDL mode)
post a screenshot of your windows machine " Device Manager " , AFTER booting to EDL
Click to expand...
Click to collapse
*Yup, I still have TWRP
*Yup, running stock B35 from your zip that I flashed in TWRP
*Installed the drivers from within the toolkit (picture attached)
parmar.saab said:
*Yup, I still have TWRP
*Yup, running stock B35 from your zip that I flashed in TWRP
*Installed the drivers from within the toolkit (picture attached)
Click to expand...
Click to collapse
Last 2 question and I'll give you a little guide to follow.
* You still have access to bootloader/fastboot mode? If so that's all you'll need for what I'm going to reply after your answer here.
* You have my :
- B35 Bootstack
- B35 StockSystem
- B35 stock recovery
If you have all 3 move to them again to sdcard , if you don't have them there already.
P.S. that isn't edl, did you boot to edl using: adb reboot edl ?
DrakenFX said:
Last 2 question and I'll give you a little guide to follow.
* You still have access to bootloader/fastboot mode? If so that's all you'll need for what I'm going to reply after your answer here.
* You have my :
- B35 Bootstack
- B35 StockSystem
- B35 stock recovery
If you have all 3 move to them again to sdcard , if you don't have them there already.
P.S. that isn't edl, did you boot to edl using: adb reboot edl ?
Click to expand...
Click to collapse
I tried booting into EDL mode using the 3 button combo, but I guess it didn't work as I'm on B35. The phone isn't being recognized by the PC because of the wonky charging, and that's why I'm unable to push the command through. I tried pushing the command in terminal emulator but that didn't work either. Is there any other way to boot into EDL mode? If I can just get this thing to boot into EDL mode, I can downgrade to B19 and lock the bootloader using the toolkit, I'm assuming.
parmar.saab said:
I tried booting into EDL mode using the 3 button combo, but I guess it didn't work as I'm on B35. The phone isn't being recognized by the PC because of the wonky charging, and that's why I'm unable to push the command through. I tried pushing the command in terminal emulator but that didn't work either. Is there any other way to boot into EDL mode? If I can just get this thing to boot into EDL mode, I can downgrade to B19 and lock the bootloader using the toolkit, I'm assuming.
Click to expand...
Click to collapse
if you can't send a command through terminal emulator how do you expect to do "fastboot oem lock" let alone flash a full EDL file?
AFAIK it would be as easy as flashing B19 then doing fastboot oem lock. But yeah, no USB means no EDL
parmar.saab said:
I tried booting into EDL mode using the 3 button combo, but I guess it didn't work as I'm on B35. The phone isn't being recognized by the PC because of the wonky charging, and that's why I'm unable to push the command through. I tried pushing the command in terminal emulator but that didn't work either. Is there any other way to boot into EDL mode? If I can just get this thing to boot into EDL mode, I can downgrade to B19 and lock the bootloader using the toolkit, I'm assuming.
Click to expand...
Click to collapse
You're out of luck.
You can't do anything without a computer. You will have to fix the usb port first.
Yeah, but why can't I boot into edl using terminal emulator?
@Oki, any help? When I try the commend "reboot edl" in terminal emulator, it says permission denied.
parmar.saab said:
@Oki, any help? When I try the commend "reboot edl" in terminal emulator, it says permission denied.
Click to expand...
Click to collapse
I think you need root elevated privilege to be able to do any kind if reboot command from terminal emulator.
parmar.saab said:
@Oki, any help? When I try the commend "reboot edl" in terminal emulator, it says permission denied.
Click to expand...
Click to collapse
Again, why do you want to enter EDL if you can't have a decent USB connection to a PC? What do you want to do? Flash a ROM? That takes about 5 minutes and any interruption on the data stream will surely wreak havoc on your device. Same with anything else that you want to try
You need superuser to use the command to reboot to edl. Otherwise you can use the vol+ vol- power combination but you WILL break your device beyond recognition. Total FUBAR.
Choose an username... said:
Again, why do you want to enter EDL if you can't have a decent USB connection to a PC? What do you want to do? Flash a ROM? That takes about 5 minutes and any interruption on the data stream will surely wreak havoc on your device. Same with anything else that you want to try
You need superuser to use the command to reboot to edl. Otherwise you can use the vol+ vol- power combination but you WILL break your device beyond recognition. Total FUBAR.
Click to expand...
Click to collapse
I want to enter the edl/fast boot mode to relock the bootloader. I need to send the phone in for a warranty repair/replacement. The charging port is f in nicky but it isn't bad enough to not let me flash anything if I hold it at a certain angle. I still have twrp, but I'm guessing the faatboot command isn't working as I'm on B35. I feel like I could just brick the phone at this point and send it in to save me the headache.
Currently, I am trying to unlock bootloader using adb.
I installed adb and fastboot and checked everything until the CMD shows my device correctly.
And right after I type
"adb reboot bootloader"
my tablet just restart and does not go into the bootloader mode.
I also tried it manually, by pressing home+up+power button, but it also perform restart and no bootloader mode.
Does anyone knows why?
I checked all the settings in developer mode and cannot figure out why.
rnfkrha88 said:
Currently, I am trying to unlock bootloader using adb.
I installed adb and fastboot and checked everything until the CMD shows my device correctly.
And right after I type
"adb reboot bootloader"
my tablet just restart and does not go into the bootloader mode.
I also tried it manually, by pressing home+up+power button, but it also perform restart and no bootloader mode.
Does anyone knows why?
I checked all the settings in developer mode and cannot figure out why.
Click to expand...
Click to collapse
You can't unlock the bootloader with adb only with fastboot which doesn't work on Samsung. To unlock the bootloader on Samsung you have to enable OEM unlocking in developer options. Also Samsung doesn't have bootloader mode but instead they have Download mode which you can use tools like Odin or SmartSwitch to flash files. To get into Download mode use the command adb reboot download or use the button combination power + volumn down + home.