UPDATE:
The oem was already unlocked so thats why the command did nothing. (I found it by locking and unlocking it again)
Also I had the wrong SuperSU, I first installed CM14 and than installed the right SuperSU
So I was trying to root my OP2 for the second time (apparently it derooted itself for some reason?)
But now I can't unlock oem from fastboot.
I magicly could flash TWRP and from there I installed SuperSU.
But when I booted my device up, it get's bricked into a boot loop.
I got out of the boot loop and tried again.
So I go into fastboot mode and tried the command again:
>fastboot oem unlock
...
OKAY [ 0.020s]
finished. total time: 0.022s
Click to expand...
Click to collapse
PLEASE do not link me to the unbrick guides - the problem is NOT that it's bricked - The problem is that I can't unlock oem from fastboot and so I can't succesfull root my phone.
What works:
+ getting into the OS
+ getting into fastboot
+ flashing a recovery (even if the device is locked?!)
+ booting into recovery
What doesn't work:
- unlocking via fastboot oem unlock
PepRoween said:
So I was trying to root my OP2 for the second time (apparently it derooted itself for some reason?)
But now I can't unlock oem from fastboot.
I magicly could flash TWRP and from there I installed SuperSU.
But when I booted my device up, it get's bricked into a boot loop.
I got out of the boot loop and tried again.
So I go into fastboot mode and tried the command again:
PLEASE do not link me to the unbrick guides - the problem is NOT that it's bricked - The problem is that I can't unlock oem from fastboot and so I can't succesfull root my phone.
What works:
+ getting into the OS
+ getting into fastboot
+ flashing a recovery (even if the device is locked?!)
+ booting into recovery
What doesn't work:
- unlocking via fastboot oem unlock
Click to expand...
Click to collapse
If you can fastboot flash a custom recovery then your device isn't locked.
When you flashed SuperSU, did you use the stock version and force a systemless installation or did you use a modified version that does this automatically?
If you used the stock version and didn't force a systemless installation, this is probably the reason you're bootlooping.
Spannaa said:
If you can fastboot flash a custom recovery then your device isn't locked.
When you flashed SuperSU, did you use the stock version and force a systemless installation or did you use a modified version that does this automatically?
If you used the stock version and didn't force a systemless installation, this is probably the reason you're bootlooping.
Click to expand...
Click to collapse
Thank you for the advice, maybe I can use it another time.
Related
Hello all,
I tried to root my phone using the twrp-3.0.2-0-taido.img recovery.
I was using the following commands:
Code:
PS C:\Users\username> fastboot flash recovery C:\Users\username\Downloads\twrp.img
PS C:\Users\username> fastboot reboot bootloader
Or
PS C:\Users\username> fastboot reboot-bootloader
N.B. My OEM was already unlocked.
However, everytime I tried to reboot from the fastboot I got this message:
Code:
PS C:\Users\username> fastboot reboot bootloader
rebooting into bootloader...
FAILED (remote: not support on security)
Also, I could not just reboot from the power or volume button so I removed the battery. And when going to the recovery got nothing just normal boot multiple times.
So I tried this commad, as I was in a rush to root the phone for my work:
Code:
PS C:\Users\username> fastboot.exe boot C:\Users\ares\Downloads\twrp.img
I reckon that the above command could be responsible of the mess. Now, I am stucked at the Moto boot image screen (loop).
If anyone could help me it would be a life saver.
P.S: I do not have access to the recovery and I am unable to flash a new one.
EDIT: I finally installed the TWRP recovery properly, the issue was that I tried to install the wrong recovery. Now, I just need to fix the boot partition messed up by the command:
I guess that I now need to find the proper boot.img for Motorola Moto E3 Power XT1700 (my model) and boot on it, right?
Any idea?
Thanks
Try to restore nandroid backup from this post
BTW, Moto E3 Power is XT1706. XT1700 is the 'normal' Moto E3.
how did you install the correct one ive tried and still no joy in accessing twrp
Hi everybody
My Zenfone Selfie after a normal update (never modified) is in bootloop.
So I installed adb and fastboot and I flashed the twrp.
Then I tried in every way to flash a rom. I've tried both with official firmware and with various versions of cyanogenmod. Through fastboot and via adb sideload.
Even if seems to work, when I reboot I get the bootloop problem again.
As far as I can understand the problem it’s that I have the bootloader still locked. The official apk solution I guees it’s not applicable in my case. By fastboot oem unlock i get an error message (probably why i can not enable usb debug).
Do you know of other ways to unlock the bootloader or in general to flick my phone?
Thanks to everyone for the help
Here is a link for selfie's boot, recovery and system images for fastboot flashing
https://mega.nz/#F!Ao1RjT7D!hQ5x60r02WveB9-Hl32B4g!810z0DoQ
You can't unlocked bootloader on fastboot. I hope you can restore your device.
24imelqui said:
Here is a link for selfie's boot, recovery and system images for fastboot flashing
https://mega.nz/#F!Ao1RjT7D!hQ5x60r02WveB9-Hl32B4g!810z0DoQ
You can't unlocked bootloader on fastboot. I hope you can restore your device.
Click to expand...
Click to collapse
i tried evrything from flashing stock image , recovery partition , boot image . but nothing works. same i dont have unlocked bootloader. i am stuck at just rebooting phone. please help
what i messed up?
i have installed custom official cynogen14.1 rom and twrp recovery. everything was working fine.
but i messed up with bootloader. I have locked oem from fastboot mode without enabling option for oem unlocking in developer settings.
Now as my phone have custom rom and twrp installed it went into bootloop and only shows zuk logo and again restart.
What i diid till now?
i have opened backcover so that i can turn of bootloop and phone by disconecting battery.
I can enter into fastboot mode by pressing vol.+ and vol- buttons sumultaneously and connecting usb cable.
But i cannot unlock bootloader as it says unlocking bootloader not allowed. I have tried device specific commads like "fastboot -i 0x2b4c oem unlock" and "fastboot -i 0x2b4c oem unlock-go" but nothing works.
i have stock recovery image but cannot flash while bootloader is locked.
i can enter into adb sideload by following method:
by loading stock recovery by typing "fastboot boot recovery.img" (this does not work with twrp as it says signature varification failed)
and then selecting apply update >> selecting apply fron adb
this much i can do does anyone knows how to recover from such a state.
please help me or my phone will be a waste.
is there any way to install stock recovery i think phone will boot properly if i managed to install stock recovery.
Hi,
I am having a problem trying to relock my bootloader.
i am selling my g4, so needed to remove my custom rom, flash stock and relock my bootloader.
I downloaded and flashed via twrp the stock 8.1 ROM on the g4 plus page. ( stock rom in twrp format)
That went fine.
Then I booted into fastboot , and entered fastboot lock command fastboot oem lock
It said the android image was not valid?
So I then entered fastboot flashing lock
it rebooted fine to the stock android , but now the bootloader warning says ''your device has loaded a different operating system'', and thens boots 8.1.
DO you think I should go back anf flash stock rom ( not a twrp flashable version), using fastboot commands, ending with 'fastboot oem lock' ?
Just dont want to brick it, as it is now sold!
Many Thanks for any help
pootler
P.S. the TWRP I am using is a custom one ( i think )
pootler said:
Hi,
I am having a problem trying to relock my bootloader.
i am selling my g4, so needed to remove my custom rom, flash stock and relock my bootloader.
I downloaded and flashed via twrp the stock 8.1 ROM on the g4 plus page. ( stock rom in twrp format)
That went fine.
Then I booted into fastboot , and entered fastboot lock command fastboot oem lock
It said the android image was not valid?
So I then entered fastboot flashing lock
it rebooted fine to the stock android , but now the bootloader warning says ''your device has loaded a different operating system'', and thens boots 8.1.
DO you think I should go back anf flash stock rom ( not a twrp flashable version), using fastboot commands, ending with 'fastboot oem lock' ?
Just dont want to brick it, as it is now sold!
Many Thanks for any help
pootler
P.S. the TWRP I am using is a custom one ( i think )
Click to expand...
Click to collapse
Use LMSA flash rescue option if you have a Windows machine
(Lenovo) MOTO Smart Assistant (PC)
then see
Relocking the bootloader
sd_shadow said:
Use LMSA flash rescue option if you have a Windows machine
(Lenovo) MOTO Smart Assistant (PC)
then see
Relocking the bootloader
Click to expand...
Click to collapse
THanks for the reply.
Strange, thought I had already updated this
I went back to stock firmware and decided to flash with fastboot all individual files.
At some point, I got the same ''verification failed' but the command line suggested flashing system, boot, and ( something else, cant remember) again.
i did this this, and this time, no errors occured, and I had a complete install, with a locked bootloader, and no bootloader warning screen.!
Yay - result
Thanks again for your advice - I will remember it for the future.
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
How are you trying to boot into download mode, are you trying to do it via fastboot or the hardware buttons?
frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
im having the same problem, i dont have download more or twrp now, all i have is fastboot
i am going to assume going into download mode through fastboot is the only option for the two people posting for help here. from what i see from the posts, both hardware buttons sequence , or the plug in & down volume are the ONLY way to get to fast boot.
and fast boot is the only thing available on the phone.
i have labeled that a soft brick .
i asume one of the two help seekers have used the magisk 20.2 trap?
the release proved to be a problem , there is a tutorial on how to fix it.
i will go look for that and try to edit it into my responce later.
for now, are the two seekers already acomplished in this procedure?
TWRP Installation Tutorial for Linux Mint and Ubuntu users » AndroidGuru.eu
TWRP (Team Win Recovery Project) is an open-source custom recovery image for Android devices. It is a replacement for the stock recovery mode that is installed on most Android devices by the manufacturer. TWRP provides various advanced features and options that are not available in the stock...
www.androidguru.eu
20.2 problem notes and fix
Magisk 20.2 Kills LG V20 (All variants) Boot partition. Reverting to 20.1 fixes issue
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode. https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705...
forum.xda-developers.com
frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
ok i found a way to get into twrp (if ever installed)
1- turn off your phone
2- hold Volume Down + Power button until you see the LG logo
3- When you see the Logo release the power button while still holding the volume down and immediately after release press power button 3 times.
4- you will see a factory reset screen, press yes twice and it will go to twrp.
NOW WE NEED TO FIND A WAY TO FLASH A WORKING ROM THRU TWRP