Related
So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?
As far as I know the only fix is the one in that link but it does require custom recovery. I'm assuming the fastboot boot command doesn't work when locked but I've never tried, if it does then you could temp boot into twrp. Worth a shot I guess.
Hindsight's 20/20 but NEVER touch anything other than your data or cache partition with a locked bootloader. Google's security jump with lollipop has caused nothing but havoc for us.
ChaosDr0id said:
So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?
Click to expand...
Click to collapse
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info
or, you can grab the factory image of whatever version of android that you were on, "unzip" it, grab the system.img, and flash it via fastboot. its the same thing as if was a "custom recovery", youre just reflashing the rom, and wont lose your data
first thing id do is flash a custom recovery and unlock my bootloader, and make a backup in recovery.
AlkaliV2 said:
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info
Click to expand...
Click to collapse
Hi, thanks for the reply.
It says
'device info' is not a supported oem command. See fastboot oem help.
FAILED <remote failure>
However I'm fairly certain the bootloader is still locked as I was unable to flash TWRP, or a stock image of android, as it tells me to unlock before doing those things.
AFAIK when you have this problem together with a stock recovery and a locked bootloader means bricked. >repair
Your bootloader is lock and you can't boot android to enable OEM unlock to unlock it. You have ruined your phone and there is no known fix.
RMA time for you.
Literally no solution unless you can invent one on your own.
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
yes
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc?
Click to expand...
Click to collapse
Absolutely. Otherwise anybody with a notebook could swipe your phone, download everything you've got on it, then return it without you knowing, and that would mean more nekkid selfies on reddit.
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
The entire concept of a locked bootloader is that you can't flash images through it.
Hey people, first time in this section so I'm gonna go straight to the chase...
I've been having some troubles unlocking this phone's bootloader
http://www.gsmarena.com/asus_zenfone_go_zb452kg-8097.php
Here's the thing
I've already enabled "Enable OEM unlock" in Developer Options
I've already unlocked many devices and this is the first time i got this problem
When going in bootloader and doing
Code:
fastboot oem unlock
It's stuck in
Code:
...
waited for 5 mins... NONE, still stuck
Reboot and did nothing, bootloader still locked
So I'm gonna need some help in this freakin phone :fingers-crossed:
How were you able to "Enable OEM Unlock"?
My ZB452KG has the developer mode activated, but there's no option to Enable OEM Unlock...
BallisticSmith said:
How were you able to "Enable OEM Unlock"?
My ZB452KG has the developer mode activated, but there's no option to Enable OEM Unlock...
Click to expand...
Click to collapse
Downgrade to the very first firmware version
veez21 said:
Downgrade to the very first firmware version
Click to expand...
Click to collapse
Yeah, i tried doing that through adb, but the phone don't let me install an older ROM version on top of this one
BallisticSmith said:
Yeah, i tried doing that through adb, but the phone don't let me install an older ROM version on top of this one
Click to expand...
Click to collapse
flash the very first stock recovery(find it in facebook groups) through flashify and then flash the very first firmware
veez21 said:
flash the very first stock recovery(find it in facebook groups) through flashify and then flash the very first firmware
Click to expand...
Click to collapse
if I can download the very first firmware Asus Zenfone Go ZB452KG from the website ASUSTek?
Sorry for my bad english
Str1kman said:
if I can download the very first firmware Asus Zenfone Go ZB452KG from the website ASUSTek?
Sorry for my bad english
Click to expand...
Click to collapse
You can download it, then flash(needs root) the very first stock recovery and then you can flash the firmware?
this thread has continued to be unaswered for several years now.
only tested 2 phones... and it seems they both have bootloader status is unknown. i can do fastboot and recovery mode on the 2 phones but on fastboot mode.. only shows blank screen... idk why it's like that. i downgraded both phones to 12.2.0 version. and bootloader status is still unknown. it can be recognized by the computer in fastboot mode using fastboot devices command but you can't do anything to it. fastboot oem device-info does not work only shows .......... , fastboot oem unlock ....., only one working is fastboot adb_enable .. kinda useless. .. i gave up on unlocking the bootloader for this phone.. im too noob for this.
yankee77 said:
this thread has continued to be unaswered for several years now.
only tested 2 phones... and it seems they both have bootloader status is unknown. i can do fastboot and recovery mode on the 2 phones but on fastboot mode.. only shows blank screen... idk why it's like that. i downgraded both phones to 12.2.0 version. and bootloader status is still unknown. it can be recognized by the computer in fastboot mode using fastboot devices command but you can't do anything to it. fastboot oem device-info does not work only shows .......... , fastboot oem unlock ....., only one working is fastboot adb_enable .. kinda useless. .. i gave up on unlocking the bootloader for this phone.. im too noob for this.
Click to expand...
Click to collapse
I opened this thread when I was still "noob-ish". The device's bootloader can't be unlocked. Unless someone hacks into it's bootloader (like LG L Fino), it might be possible.
Mr.haikal
veez21 said:
I opened this thread when I was still "noob-ish". The device's bootloader can't be unlocked. Unless someone hacks into it's bootloader (like LG L Fino), it might be possible.
Click to expand...
Click to collapse
I found a way to unlock bootloader on this device. Just run this commands:
Code:
fastboot oem adb_enable 1
fastboot reboot-bootloader
fastboot oem unlock
Also compiled a TWRP recovery:
TWRP: https://github.com/Displax/android_.../download/3.2.3-0/twrp-3.2.3-0-ASUS_X014D.img
Sources: https://github.com/Displax/android_device_asus_ASUS_X014D
Displax said:
I found a way to unlock bootloader on this device. Just run this commands:
Also compiled a TWRP recovery:
TWRP: https://github.com/Displax/android_...s/download/master/twrp-3.2.1-0-ASUS_X014D.img
Source: https://github.com/Displax/android_device_asus_ASUS_X014D
Click to expand...
Click to collapse
Cool, I'll try it when I get the device on my hands. I don't have it anymore.
EDIT: It works wew ?
Displax said:
I found a way to unlock bootloader on this device. Just run this commands:
Code:
fastboot oem adb_enable 1
fastboot reboot-bootloader
fastboot oem unlock
Also compiled a TWRP recovery:
TWRP: https://github.com/Displax/android_.../download/3.2.3-0/twrp-3.2.3-0-ASUS_X014D.img
Sources: https://github.com/Displax/android_device_asus_ASUS_X014D
Click to expand...
Click to collapse
+1 worked after i installed the drivers from Asus PCLink. Anyone has a custom kernel or ...
BallisticSmith said:
Yeah, i tried doing that through adb, but the phone don't let me install an older ROM version on top of this one
Click to expand...
Click to collapse
I got root access with KingRoot and then flashed TWRP with Flashify.
Somehow that gave me access to bootloader without the necessity to downgrade the firmware.
Hi guys, if you are like me trying to lock the bootloader to get Android Pay, or Netflix back up and running without much fuss, I found a way to lock the bootloader.
WARNING: This will do a factory reset to your device, so do backups...
Requires:
- Official OOS flashed (Download here the full zip file for the latest OOS, you can flash through TWRP or stock Recovery)
- Latest Fastboot drivers and SDK file
- Basic knowledge of Fastboot commands
Guide:
- Boot the device into Bootloader mode (power the device with Volume up + Power Button)
- Connect to the PC
- Run the command "fastboot flashing lock"
- On the device, using the volume keys select "Yes" to lock the bootoader
And that's it, the 1st boot will take longer, but just wait.
Hope this helps =)
@hugoprh
It should be
Code:
fastboot oem lock
instead of
Code:
fastboot flashing lock
as OnePlus still uses the older LK. Only Nexus 6P & Pixel/Pixel XL have updated LK that includes these changes.
You should also mention that this procedures factory resets the device i.e. the internal memory is wiped.
Titokhan said:
@hugoprh
It should be
Code:
fastboot oem lock
instead of
Code:
fastboot flashing lock
as OnePlus still uses the older LK. Only Nexus 6P & Pixel/Pixel XL have updated LK that includes these changes.
You should also mention that this procedures factory resets the device i.e. the internal memory is wiped.
Click to expand...
Click to collapse
Hi, thanks for your feedback, but I did try "fastboot oem lock", as other XDA Oneplus 5 users have tried as well, without success, so I tried the Nexus 6p way "fastboot flashing lock" and it worked and this is the reason I decided to make this guide and I did write a "WARNING" about this procedure doing a factory reset, it's written in bold and underlined, please read carefully.
hugoprh said:
Hi, thanks for your feedback, but I did try "fastboot oem lock", as other XDA Oneplus 5 users have tried as well, without success, so I tried the Nexus 6p way "fastboot flashing lock" and it worked and this is the reason I decided to make this guide and I did write a "WARNING" about this procedure doing a factory reset, it's written in bold and underlined, please read carefully.
Click to expand...
Click to collapse
Let me explore the firmware - it would a curious case of hybridization then.
Regarding the warning: Yah, my bad... missed it somehow.
Trying to relock my bootloader, everytime I get to the fastboot screen I scroll through to "START" and select it using the power button the phone shuts off and reboots. Having a hard time getting into fastboot. any suggestions?
rgreene1971 said:
Trying to relock my bootloader, everytime I get to the fastboot screen I scroll through to "START" and select it using the power button the phone shuts off and reboots. Having a hard time getting into fastboot. any suggestions?
Click to expand...
Click to collapse
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
rgreene1971 said:
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
Click to expand...
Click to collapse
+1
rgreene1971 said:
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
Click to expand...
Click to collapse
You need to turn on OEM Unlocking in Developer Settings. If for any reason OEM Unlocking is freezed, flash Magisk and then turn on OEM Unlocking. Flash the stock recovery and the lock bootloader command. It should work flawless!
Don't forget the backup!
Why lock? Why not just use Magisk? That works fine with Android Pay.
You don't need to lock your bootloader to use Netflix
nagorimayank said:
You need to turn on OEM Unlocking in Developer Settings. If for any reason OEM Unlocking is freezed, flash Magisk and then turn on OEM Unlocking. Flash the stock recovery and the lock bootloader command. It should work flawless!
Don't forget the backup!
Click to expand...
Click to collapse
I am getting the same error saying that Flashing Lock is not allowed.I did what you said to do but the i can't turn on the OEM Unlocking in Developer Settings since it is greyed out.
What should i do?
mullafabz said:
I am getting the same error saying that Flashing Lock is not allowed.I did what you said to do but the i can't turn on the OEM Unlocking in Developer Settings since it is greyed out.
What should i do?
Click to expand...
Click to collapse
What I did was install custom ROM, the option isn't greyed out. Then try again. But make sure you install stock ROM and recovery before bootloader lock.
beache said:
What I did was install custom ROM, the option isn't greyed out. Then try again. But make sure you install stock ROM and recovery before bootloader lock.
Click to expand...
Click to collapse
I managed to lock back the bootloader but now am stuck in an bootloop.
mullafabz said:
I managed to lock back the bootloader but now am stuck in an bootloop.
Click to expand...
Click to collapse
You have to format data in recovery
Hay soo i wanted to relock bootloader after failing to install custom recovery (both) i turned off oem unlocking in developer options and did fastboot oem lock. Now the phone is looping in "your device can't be checked for corruption. Please lock the bootloader" and it reboots and says the same again.
When i try to unlock the bootloader with fastboot oem unlock i get "FAILED (remote: Flashing Unlock is not allowed)
I really dont know what to do and i need a phone for comunication. Please help!
You should only lock the bootloader after installing the stock ROM, otherwise your device will be bricked and the only way you'll get it back working is by flashing the EDL test points near the phone's battery and reflashing the stock ROM back in EDL mode.
Try downloading this tool then try to unlock oem, flashing and flashing critical.
Yepi69 said:
You should only lock the bootloader after installing the stock ROM, otherwise your device will be bricked and the only way you'll get it back working is by flashing the EDL test points near the phone's battery and reflashing the stock ROM back in EDL mode.
Try downloading this tool then try to unlock oem, flashing and flashing critical.
Click to expand...
Click to collapse
Noted. Thanks!
I really messed up here. The problem is i toggled allow oem unlocking off and to top it all off i did oem lock. Now its bootlooped (check the video). Does xiaomi fix this by warrenty? I really dont want to open the device up because i am afraid i will do more demage and void the warrenty and the device wont ever be fixed.
NotCat_ said:
Noted. Thanks!
I really messed up here. The problem is i toggled allow oem unlocking off and to top it all off i did oem lock. Now its bootlooped (check the video). Does xiaomi fix this by warrenty? I really dont want to open the device up because i am afraid i will do more demage and void the warrenty and the device wont ever be fixed.
Click to expand...
Click to collapse
I have seen another guy who did this. How is this possible that you turn off the unlock bootloader option when you've already unlocked it? The option gets greyed out and becomes non-functional.
Anyways I guess the best option is to give your phone to Xiaomi for the fix.
Njaiker said:
I have seen another guy who did this. How is this possible that you turn off the unlock bootloader option when you've already unlocked it? The option gets greyed out and becomes non-functional.
Anyways I guess the best option is to give your phone to Xiaomi for the fix.
Click to expand...
Click to collapse
It wasn't grayed out for me. I'm thinking of test pointing the device because i dont really want to wait few months until i get my phone back from service. (There is no xiaomi service in my Country)
But i'm afraid if i open the device i will void my warrenty for future.
NotCat_ said:
It wasn't grayed out for me. I'm thinking of test pointing the device because i dont really want to wait few months until i get my phone back from service. (There is no xiaomi service in my Country)
But i'm afraid if i open the device i will void my warrenty for future.
Click to expand...
Click to collapse
I don't think you will since you don't need to disassemble the device, all you need to do is remove the aluminum back cover carefully with damaging it and you'll find the test points right besides the battery
Yepi69 said:
I don't think you will since you don't need to disassemble the device, all you need to do is remove the aluminum back cover carefully with damaging it and you'll find the test points right besides the battery
Click to expand...
Click to collapse
will try to do that. all tho i think screen goes off first thanks for your help and sparking some hope into me and my phone <3
It finally booted up! After having some hard time shorting test points i finally did and it booted up just fine! Big thanks to @Yepi69
use custom rom
NotCat_ said:
Hay soo i wanted to relock bootloader after failing to install custom recovery (both) i turned off oem unlocking in developer options and did fastboot oem lock. Now the phone is looping in "your device can't be checked for corruption. Please lock the bootloader" and it reboots and says the same again.
When i try to unlock the bootloader with fastboot oem unlock i get "FAILED (remote: Flashing Unlock is not allowed)
I really dont know what to do and i need a phone for comunication. Please help!
Click to expand...
Click to collapse
since your device is already unlocked i recommend you using havoc os need instructions? instagram hsghumaan01
honey ghumaan01 said:
since your device is already unlocked i recommend you using havoc os need instructions? instagram hsghumaan01
Click to expand...
Click to collapse
Yes i do want to flash that rom, but i can't get twrp to boot on my unit. When i do fastboot boot "recovery name".img it says everything went fine, but i get black screen and thus can't get it to work nor install.
try other slot
NotCat_ said:
Yes i do want to flash that rom, but i can't get twrp to boot on my unit. When i do fastboot boot "recovery name".img it says everything went fine, but i get black screen and thus can't get it to work nor install.
Click to expand...
Click to collapse
try on both slots
honey ghumaan01 said:
try on both slots
Click to expand...
Click to collapse
Whats the fastboot command to change slots?
Mtp works fine tho.
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set-active {a or b}
To see what slot you current is on,
fastboot getvar current-slot
the command to chang slot with fastboot is
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set_active a/b
---------- Post added at 12:44 PM ---------- Previous post was at 12:41 PM ----------
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set_active a/b not sure can be fastboot set-actve a/b , you should use pitch black recovery instead of simple twrp
---------- Post added at 12:45 PM ---------- Previous post was at 12:44 PM ----------
honey ghumaan01 said:
try on both slots
Click to expand...
Click to collapse
dm me on instagram hsghumaan01
honey ghumaan01 said:
fastboot set_active a/b
Click to expand...
Click to collapse
That command doesn't seem to work on my pc :/ cmd just gives out all commands when i type
fastboot set_active B (on pc)
And nothing happens :/
Are there any particular adb/fastboot files i need to download?
MarcusMario0605 said:
fastboot set-active {a or b}
To see what slot you current is on,
fastboot getvar current-slot
Click to expand...
Click to collapse
Took a screenshot of your comment for later, thanks!
Are there any particular adb/fastboot files i need to download?[/QUOTE]
use this tool; https://mega.nz/#!cr4SUIqY!Rzlftk2OFun8XIkNQb2aXRtP7-t3f4DB92vMIl90pgw
(this tool,can disable driver signature,Install all drivers,qcom,etc)
https://forum.xda-developers.com/showthread.php?t=2588979
Download SDK Platform-Tools for Windows ; https://developer.android.com/studio/releases/platform-tools
QDLoader HS-USB Driver ; https://mega.nz/#!EqJwTIzB!KJF3CldYq_u7KylaL0iO6rs05RWs2_dcUfaENjJcDpU
fastboot edl (useful) ; https://mega.nz/#!x6BkXY5A!hx8SXoBwd4-fW1UkZ1poHc7p-MFDaQ85FYH7Yk8bLZ8
See and here how to use adb & fastboot from any directory on pc ; https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
all of these are useful tools,that you must to have on pc
sry for english
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
daitalos said:
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
Click to expand...
Click to collapse
I already flashed the phone with edl test points. I'm running havoc os +hex
daitalos said:
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
Click to expand...
Click to collapse
Why not use oem unlock?
Hey guys, i have MI A2 cellphone, and after auto update programmed to three hours the smartphone show "AndroidONE" logo and then shutdown, i tried "Fastboot oem unlock", but it is my output:
PHP:
C:\Users\Lucas Daniel>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.000s
. I'm desperate, I do not know what to try anymore, I believe I do not have unlock OEM activated, someone can help me?
Sorry for bad english, i'm from brazilian.
@LukeSkyPTBR
It's a well-known issue. One update was revoked as soon as Xiaomi has found out about phones bricking once it's installed. There's no way you can fix it by yourself except if you have ordered your phone from China (and so no warranty you have) and have experience in disassembling phones. There's a thing called test-point, do some research if you are self-assured in that area. Otherwise let your authorized service center make everything for you. It is a warranty case, either way.
sas.mar said:
@LukeSkyPTBR
It's a well-known issue. One update was revoked as soon as Xiaomi has found out about phones bricking once it's installed. There's no way you can fix it by yourself except if you have ordered your phone from China (and so no warranty you have) and have experience in disassembling phones. There's a thing called test-point, do some research if you are self-assured in that area. Otherwise let your authorized service center make everything for you. It is a warranty case, either way.
Click to expand...
Click to collapse
Thanks, looks that, unfortunately, my unique solution is test-point for activate EBL Mode... I will leave the topic open for the case of i get other solutions... after 3 days, if not get, i will close and the unique solution will really test-point.
Try rebooting it a couple of times and see if it boots. Or plug it to a charger and try booting it once it starts to charge successfully. If all fails, flashing via EDL might be your only option.
Try rebooting more than couple of time. Phone is supposed to switch to the other slot of A/B where original ROM (before update) resides. When it finally boots, get developer rights, switch on ADB Debugging and OEM unlock, thus next time update soft-bricks your phone you'll be able to unlock (or even better unlock immediately after successful boot not to loose your data in future).
Isnt Fastboot OEM Unlock command deprecated ? Shouldn't you use the unlock / unlock critical command ?
Tianhe said:
Isnt Fastboot OEM Unlock command deprecated ? Shouldn't you use the unlock / unlock critical command ?
Click to expand...
Click to collapse
What is it command?
Aerobatic said:
Try rebooting more than couple of time. Phone is supposed to switch to the other slot of A/B where original ROM (before update) resides. When it finally boots, get developer rights, switch on ADB Debugging and OEM unlock, thus next time update soft-bricks your phone you'll be able to unlock (or even better unlock immediately after successful boot not to loose your data in future).
Click to expand...
Click to collapse
How can I do it? I leave the phone in the charger for a long time? Or do you need the power button for a long time?
I tried to press the power button for 2 minutes and nothing happened.
When i leave the smartphone on the charge, after 50 minutes, show for me 100% percent, so, i pressed power button and the screen stayed lock in "AndroidONE", nothing happened, until try again press power button.
The problem original comebacked to me
LukeSkyPTBR said:
What is it command?
Click to expand...
Click to collapse
I tried, the same ploblem happenned... don't work, unfortunely... :/
LukeSkyPTBR said:
What is it command?
Click to expand...
Click to collapse
fastboot flashing unlock
fastboot flashing unlock_critical
Can't you just enter fastboot mode by holding power and vol- keys with phone connected to a PC?
(Or power and vol+, can't remember)
Phil_Smith said:
fastboot flashing unlock
fastboot flashing unlock_critical
Can't you just enter fastboot mode by holding power and vol- keys with phone connected to a PC?
(Or power and vol+, can't remember)
Click to expand...
Click to collapse
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
LukeSkyPTBR said:
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
Click to expand...
Click to collapse
If you can enter fastboot then you can go to EDL mode by typing 'fastboot reboot edl' and then use QPST to flash the latest stock rom.
LukeSkyPTBR said:
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
Click to expand...
Click to collapse
Do as tabun1994 said.
This will hopefully get the system up again.
The commands I wrote would unlock the bootloader. What else could I have meant?
If you succeeded with tabun's method, then you probably would only need to enable "USB debugging" and "OEM unlocking" in the ROM's developer options (which you'll enable by hitting "build number" in settings like 10 times or so).
Then you would connect the device and accept the 'trust this device' warning.
After booting to fastboot now, the commands I wrote should work and unlock the bootloader (if you even want that when your system is running again).
tabun1994 said:
If you can enter fastboot then you can go to EDL mode by typing 'fastboot reboot edl' and then use QPST to flash the latest stock rom.
Click to expand...
Click to collapse
This command needs OEM Unlock :/
this is my output: fastboot: usage: unknown reboot target edl
The test point method is actually easy , you have to dissasemble the display , easy procedure , remove the battery and short the two test points with tweezerz or something ,and in the meantime you plug the usb cable into the computer. It should install the Qusb_Hub drivers , and with miFlash you should be able to reflash the firmware . I bought a phone that was in this state and fixed it using these steps.
No more solutions, I will do the test point method, thanks to everyone who tried to help otherwise.
LukeSkyPTBR said:
This command needs OEM Unlock :/
this is my output: fastboot: usage: unknown reboot target edl
Click to expand...
Click to collapse
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
tabun1994 said:
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
Click to expand...
Click to collapse
Okays, thanks for this solution, i will get the smartphone tomorrow, if the technical assistance not resolved my problem, i will try. Thanks very much!
LukeSkyPTBR said:
Okays, thanks for this solution, i will get the smartphone tomorrow, if the technical assistance not resolved my problem, i will try. Thanks very much!
Click to expand...
Click to collapse
I execute bat archive but nothing happens in Mi A2 .-
tabun1994 said:
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
Click to expand...
Click to collapse
What is your smartphone?