OK so I have an issue that I just cannot seem to fix. I've followed Max Lee's guide to unlocking the bootloader, obtaining root, and getting twrp. I've followed the written and video instructions to the t and a few guides in here, I have installed and updated the proper drivers and sdk tools, but my hitch is when I type the "fastboot oem Unlock" command, it says it finishes but my device doesn't reboot and ask if I want to proceed to unlock my bootloader, instead it just stays on the fastboot logo and does nothing until I restart it. This happens on both my mac and my pc so I'm not sure what the issue is I have usb debugging enabled and the allow oem Unlock slider is in the on position, any help or advice 8s greatly appreciated, thank you.
Sent from my ONE A2005 using Tapatalk
do you run an actual version of sdk-tools? fastboot recognized your phone, right? You can test it with following command: fastboot devices
Output is something like this:
33a0cde4 fastboot
Click to expand...
Click to collapse
nevermind i just fixed it, thanks
Hai all , I am new here.
I need some help to unbrick my device. i tried almost all method and still no luck. the only method i havent tried is DFC, but i dont prefer to do it since its pretty complicated.
My device run rom Global Stable Miui 7 and i flashed Developer rom Global using EDL download mode.
there was an error and now my device stuck in Mi logo. I can still access Mi bunny fastboot ( vol down + power)
So far I have tried 3 methods
Method 1: reboot to fastboot mode, plug to pc, open ADB cmd prompt and type fastboot oem EDL. But no success because device is still locked bootloader.
Method 2: reboot to fastboot mode, plug in to pc, download fastboot EDL cmd from xda forum, unzip then run edll.cmd, device reboot to mi logo again.
Method 3: in Mi logo, plug in to pc, open cmd prompt, type Adb reboot edl, press enter but device cannot reboot to edl mode because it says I need to tap on confirmation dialog on device. But its not possible since device only load up to mi logo
Download the latest stable fastboot ROM from here http://en.miui.com/a-234.html then flash it.
Sent from my Redmi 3S using Tapatalk
If only it was that easy. I've tried 3 methods above but still no luck. Use Adb reboot edl, fastboot oem.
How to flash if its only stuck at mi logo
Because I had this exact same thing happened before. What I did was while it kept bootlooping at the Mi boot splash I held down Vol - + power until fastboot mode pops up. Then you'd be able to flash.
Sent from my Redmi 3S using Tapatalk
Trovies said:
If only it was that easy. I've tried 3 methods above but still no luck. Use Adb reboot edl, fastboot oem.
How to flash if its only stuck at mi logo
Click to expand...
Click to collapse
First off you cannot just unlock the bootloader easily, like in fastboot or anyhow, you need to follow the guides. And this is possible by the way only with a working Dev rom.
Well so now, you've to get miflash tool and flash either stock rom, or dev rom.
You simply hold power and volume down as long (can take some time) as it will show "fastboot" and some android art.
Then you follow the guides to flash either stock rom or dev rom using fastboot, and you're good to go.
I don't see why this wouldn't be working for you, try to stick exactly to what i said. If you don't know how to use Miflash then search at en.miui.com
Trovies said:
Hai all , I am new here.
I need some help to unbrick my device. i tried almost all method and still no luck. the only method i havent tried is DFC, but i dont prefer to do it since its pretty complicated.
My device run rom Global Stable Miui 7 and i flashed Developer rom Global using EDL download mode.
there was an error and now my device stuck in Mi logo. I can still access Mi bunny fastboot ( vol down + power)
So far I have tried 3 methods
Method 1: reboot to fastboot mode, plug to pc, open ADB cmd prompt and type fastboot oem EDL. But no success because device is still locked bootloader.
Method 2: reboot to fastboot mode, plug in to pc, download fastboot EDL cmd from xda forum, unzip then run edll.cmd, device reboot to mi logo again.
Method 3: in Mi logo, plug in to pc, open cmd prompt, type Adb reboot edl, press enter but device cannot reboot to edl mode because it says I need to tap on confirmation dialog on device. But its not possible since device only load up to mi logo
Click to expand...
Click to collapse
Did you unlock developer mode as in my case I am also stuck in bootloop and fastboot oem edl is not working as developer mode is disabled thus oem is also disabled.
Hey!
I had the same Problem.
Flashing with Miflash was unsuccessfull and then EDL was locked. You can check this when the device is in fastboot and send "fastboot oem edl". Then there may be the message that EDL is locked. In that case you have to build a "deep flash cable". It is pretty easy. You can check this tutorial:
http://en.miui.com/thread-310325-1-1.html
But I would build it another way: Just cut a USB cable and reconnect all wirepairs with the open copper. Now you can just put "ground" and "data+" togehther and follow steps 7 to 9. At point 10 you can just disconnect the wires "ground" and "data+" again, so that all wires are connected normally again. Now you are in EDL and can flash with MiFlash.
Hi guys,
I'm having problems unlocking bootloader.
The phone enter into fastboot mode but when I type "fastboot oem unlock-go" in the cmd of windows it doesn't recognize my device.
I have installed Minimal ADB and Fastboot and I have installed ADB Driver installer too but it doesn't recognize the device.
Can anybody help me with this please?
I need to unlock it because I want to root it.
Thanks
Have you tried unplugging and replugging when the phone goes into fastboot mode?
I just got my pro 3, did the OTA to the .19 software and unlocked and rooted just today and my girlfriend's very very fresh windows 10 install.
If that doesn't work just delete the adb driver, replug the device and windows should install the same drivers I used.
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable
I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.
SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553
Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .
I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse
bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.
After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818
I had rooted my Moto G5 plus a couple of months back, I had to relock the bootloader and install the stock recovery and rom due to some reasons. I followed a thread on this website which had all the files and commands given to restore stock rom. Later, I decided to unlock the bootloader again. I followed the steps to unlock the bootloader but, my device isn't appearing under adb devices so, I am not able to do anything. I have installed all the moto adb drivers and checked oem unlocking and usb debugging under developer options but, my device doesn't appear under adb.
I used the following thread-
https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738
Everything in that guide is done in fastboot, so if you're in fastboot when you're trying to find your phone, try "fastboot devices" instead of "adb devices"
So, how do I follow the steps on moto's website to unlock the bootloader?
ReckerRex said:
So, how do I follow the steps on moto's website to unlock the bootloader?
Click to expand...
Click to collapse
For some reason,
Code:
adb devices
didn't work for me right away.
I skipped that command and just ran
Code:
fastboot oem get_unlock_data
and that worked and I was able to continue with the process. Perhaps try that and see what happens.
Drivers must be installed too. This thread helped me:
https://forum.xda-developers.com/g5-plus/how-to/unlock-bootloader-lenovo-motorola-moto-t3581133
Another thing that didn't work for me:
USB Dev settings must be disabled in order to mount USB File Transfer Mode (MTP). After updating to latest version, it seems that has been fixed so I don't have to do that anymore.