{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Warnings
Doing this will void your warranty.
Your phone will be wiped.
I am not responsible for anything that happens to your phone.
Prerequisites
Your phone
USB Cable
Minimal ADB and Fastboot (Download and install it from here)
A working human brain.
Steps To Unlock Bootloader
First, enable Developer Options. To do this, go to Settings>About Phone> Tap on Built Number multiple times until the toast You are a developer now appears.
Now go to Developer Options in Settings and find and enable OEM Unlock by sliding the button. A warning will appear, just confirm that.
Turn off Your smartphone.
Press Volume Down Button and Power button simultaneously and hold it for few seconds. This will boot your device into fastboot mode.
Double-Click the Minimal ADB and Fastboot icon on your desktop.
Connect your device via USB cable. ( Stock Motorola Cable recommended )
Now go to this website. Read the information given if you wish and click on next button to proceed.
The Page will ask you to sign in, complete the process by signing with your Motorola account or Google Account.
Now go the Command Prompt and type fastboot oem get_unlock_data.
Now a new serial code will appear in your command prompt screen you have to copy the entire code.
Now open this link and copy the code in the tool. Then select the entire code and paste that code in point 6 on Moto require Unlock Tool Website.
Now Click on the I Agree Button a Get Unlock Code will appear on the screen.
Click on the button.
An Unlock Code will appear or will be emailed to you.
Now again go to the Command Prompt screen and type fastboot oem unlock ************. (“************” will replace your unique key)
A warning screen will appear in command just retype the same command and hit enter.
Type fastboot reboot and your phone will reboot.
Done! Your bootloader has been unlocked.
I am getting bad id on bootup. No issues afaik but can someone point out the cause of this?
You forgot 'WINDOWS PC"... or can it be done from Ubuntu?
@edilebe: Certainly you can:
Code:
sudo apt update
sudo apt install android-tools-adb android-tools-fastboot
And then in a terminal:
To access adb :
Code:
adb devices
To access fastboot :
Code:
fastboot devices
Rest of the commands go on as usual.
Broadcasted from Zeta Reticuli
Can i relock the Bootloader without warning boot screen?
Get also Bad Key on Bootscreen but its working
Will doing this disable OTA updates?
I apparently did some step wrong, Id: Bad Key shows on Bootscreen and I can't seem to install TWRP recovery, I get the following error
Code:
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
Also when I run ""fastboot getvar unlocked" I get:
Code:
(bootloader) unlocked: not found
getvar:unlocked FAILED (remote failure)
Maybe I put the wrong key, and now I can't try to unlock it again, what should I do?
I'll greatly appreciate some help
Tewisp said:
I apparently did some step wrong, Id: Bad Key shows on Bootscreen and I can't seem to install TWRP recovery, I get the following error
Code:
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
Also when I run ""fastboot getvar unlocked" I get:
Code:
(bootloader) unlocked: not found
getvar:unlocked FAILED (remote failure)
Maybe I put the wrong key, and now I can't try to unlock it again, what should I do?
I'll greatly appreciate some help
Click to expand...
Click to collapse
It says Your bootloader is locked
u may try from beginning to unlock the bootloader
I dud try to unlock it again, but it won't let me do it, i get a invalid state error
...
(bootloader) invalid boot state
I tried to lock it again just in case, installed factory rom but got the same message.
Is there a way to reset the boot state so i could try again to unlock it?
Thanks for answering by the way, I really appreciate it!
Schrotty35 said:
Get also Bad Key on Bootscreen but its working
Click to expand...
Click to collapse
same here as well. but seems to work fine.
need to proceed to root.
bradleyw801 said:
Will doing this disable OTA updates?
Click to expand...
Click to collapse
I would also like to know the answer. Today I will receive a brand new G5S Plus.
If I unlock the bootloader, install TWRP, decrypt data, and install Magisk, will I still receive OTA updates (including in a few months Oreo)?
gewe said:
I would also like to know the answer. Today I will receive a brand new G5S Plus.
If I unlock the bootloader, install TWRP, decrypt data, and install Magisk, will I still receive OTA updates (including in a few months Oreo)?
Click to expand...
Click to collapse
Installing TWRP will certainly prevent you from getting OTAs. Not sure whether simply unlocking the bootloader will disqualify you as well.
revengineer said:
Installing TWRP will certainly prevent you from getting OTAs. Not sure whether simply unlocking the bootloader will disqualify you as well.
Click to expand...
Click to collapse
I like to have my phone rooted (for things like backup, adblocker).
Since the data partition has to be decrypted for TWRP and Magisk, would the following order make OTA possible?
Create backup
Uninstall Magisk
Flash stock bootloader
Reboot
Let OTA install do its work
Reinstall TWRP
Decrypt data partition
Reinstall Magisk
Restore data partition
gewe said:
I like to have my phone rooted (for things like backup, adblocker).
Since the data partition has to be decrypted for TWRP and Magisk, would the following order make OTA possible?
Create backup
Uninstall Magisk
Flash stock bootloader
Reboot
Let OTA install do its work
Reinstall TWRP
Decrypt data partition
Reinstall Magisk
Restore data partition
Click to expand...
Click to collapse
You need original recovery for sure. Flashing bootloader alone is not sufficient. I believe you also need to lock the bootloader. What I do not know is whether you need signed images of bootloader and/or recovery. The firmware floating around here does not included signed images.
revengineer said:
You need original recovery for sure. Flashing bootloader alone is not sufficient. I believe you also need to lock the bootloader. What I do not know is whether you need signed images of bootloader and/or recovery. The firmware floating around here does not included signed images.
Click to expand...
Click to collapse
At the moment I am trying to create a backup of everything in the state directly after unlocking the bootloader.
I booted TWRP without flashing it, so I can create a backup. However, the backup freezes. I could create a backup of all partitions, except system. When I include system, the backup freezes. I tried three times. It froze at 13%, 21% and 1% (posted this here).
revengineer said:
You need original recovery for sure. Flashing bootloader alone is not sufficient. I believe you also need to lock the bootloader. What I do not know is whether you need signed images of bootloader and/or recovery.
Click to expand...
Click to collapse
You don't need signed images, and you don't need a locked bootloader to install OTA.
Signed images are only necessary for locking bootloader. Nothing else should be concerned.
Locked bootloader is only necessary for passing SafetyNet. Alternative is using Magisk, which pretends to the verifying routine the bootloader would have been locked. Then you should pass SafetyNet again, until the checks SafetyNet do are modified. Then it fails, until Magisk is updated to circumvent these checks also ... it is a cat-and-mouse game, and the author of Magisk (topjohnwu) is a fast one. But there probably always will be times where neither PokemonGo nor Android Pay are running fine. If you want root (my personal belief is, if you own a device, you should have the right to access and modify all data on it), you need to deal with it.
OTA update checks some things (system, recovery, boot, oem, maybe some more) are not modified. Mounting system r/w may suffice to mark the partition as changed and prevent installation of OTA. Failed OTA usually reverts to previous state and gives an error message, then you may read the logs to see what went wrong. Your device stays in a usable state in most cases, at least that's my experience.
Disclaimer: I don't own a G5S Plus, but I'm usually recommending it if I'm asked which mobile is currently a good one to buy. What I write here is to the best of my knowledge applying to many Android, at least most Moto devices. Some behaviours may change when Oreo arrives. Always do a complete backup before any action, and don't forget to treat /data/media in a special way if using Nandroid in twrp.
I can't even unlock the bootloader...:crying:, let alone flashing twrp and rooting my device..... I have no idea where i am going wrong, i followed every step you mentioned. i tried running this command:
c:\adb>fastboot oem get_unlock_data
but it did not work, it showed me an error
---
FAILED < command write failed <No error>>
finished. total time: 0.003s
c:\adb>
Can anyone tell why is this happening? I must have done something wrong otherwise it would not happen.
Unable to unlock Bootloader
Phone is unable to boot and ends up on fastboot screen.
Phone has a locked oem. It says software as modified in fastboot screen. Unable to load bootloader.
While trying to get unlock oem data throws data block read error. What can be done? Is there an alternate way to to get device ID so as to get oem unlock code from Motorola website?
This happened all of a sudden. It was running stock, nothing ever altered.
Related
hello guys
i have moto nexus 6 xt1100 int i think its 6.0
i cant unlock boot loader i tried with SkipSoft ToolKit and with nexus root toolkit and with fastboot but not work
any help
thanx
:silly:
Questions that say effectively "I have a problem" but don't say what exactly you've done to resolve it have no chance of being answered.
Start with fastboot. What did you do?
dahawthorne said:
Questions that say effectively "I have a problem" but don't say what exactly you've done to resolve it have no chance of being answered.
Start with fastboot. What did you do?
Click to expand...
Click to collapse
hello sir
thanx to replay
i do
fastboot oem unlock
C:\Users\pc\Desktop\platform-tools>fastboot flashing unlock
...
FAILED (remote: Unknown command)
finished. total time: 0.002s
C:\Users\pc\Desktop\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.006s
C:\Users\pc\Desktop\platform-tools>
The answer is in the output. You must go into Settings > Developer Options and select "Enable OEM Unlock" before you can unlock the bootloader.
i cant go to setting to open oem lock becuase pbone after upgrade ota 60 now cant open still hung google nexus screen plz hlp plz
any one help me plz
Can't you get into twrp and do a restore of made backup? Then after booting go to Developer Options and select "Enable OEM Unlock" then unlock the bootloader and leave it unlocked and leave the OEM Unlock setting in Developer options enabled.
TMG1961 said:
Can't you get into twrp and do a restore of made backup? Then after booting go to Developer Options and select "Enable OEM Unlock" then unlock the bootloader and leave it unlocked and leave the OEM Unlock setting in Developer options enabled.
Click to expand...
Click to collapse
im sorry to late phone is locked plz be fix and not open just google screen not work even after wip frm recvry
Do you have TWRP installed? If so, move a custom rom zip to the phone and flash it in TWRP. After that you can boot the phone and enable OEM unlock and proceed to unlock your phone (and then flash stock or whatever you would like to use). Your phone will be wiped (no way to save your data anyway, unless you have a previous backup), but it'll work.
If you only have stock recovery, you are out of luck and have a nice new desk ornament.
Didgeridoohan said:
Do you have TWRP installed? If so, move a custom rom zip to the phone and flash it in TWRP. After that you can boot the phone and enable OEM unlock and proceed to unlock your phone (and then flash stock or whatever you would like to use). Your phone will be wiped (no way to save your data anyway, unless you have a previous backup), but it'll work.
If you only have stock recovery, you are out of luck and have a nice new desk ornament.
Click to expand...
Click to collapse
No, if he's on stock he can sideloade the N preview one OTA through ADB in stock recovery. Doesn't need fastboot for the OTA zip. The links somewhere here. After that he can enroll in the N preview program and then select the option to either unenroll or roll back I can't remember what it is. It will then push an OTA for the latest 6.0.1.
Harry44 said:
No, if he's on stock he can sideloade the N preview one OTA through ADB in stock recovery. Doesn't need fastboot for the OTA zip. The links somewhere here. After that he can enroll in the N preview program and then select the option to either unenroll or roll back I can't remember what it is. It will then push an OTA for the latest 6.0.1.
Click to expand...
Click to collapse
True... Didn't think of that. That's a good workaround until N is released.
Harry44 said:
No, if he's on stock he can sideloade the N preview one OTA through ADB in stock recovery. Doesn't need fastboot for the OTA zip. The links somewhere here. After that he can enroll in the N preview program and then select the option to either unenroll or roll back I can't remember what it is. It will then push an OTA for the latest 6.0.1.
Click to expand...
Click to collapse
hello sir
again so sorry to late and thanx to replay
i think no bady undrstand my prob my brop is after update ota 60 phone was like photo under long time all day just like this photo oky i do wip data factory reset from recovery not work
and i tried to flash other fimrware from all toolkit nexus but need unlock boot but cant unlock
please can u help me
im here wating every bady
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
please brothers help me
------------------------------------------------------------------------------------
Follow the Instructions on the devices screen to Unlock your BootLoader.
Enable the developer options screen by going to the settings, about screen and
clicking on build number at the bottom 7 times. Then go to developer options and
tick USB debugging so the procedure to continue.
If you get stuck on 'Waiting for USB debugging to be enabled' and have already
enabled USB debugging then just unplug/replug the usb cable and it should proceed.
IF NOTHING HAPPENS TRY PULLING DOWN THE NOTIFICATION SCREEN AT THE TOP LEFT WITH
THE DEVICE CONNECTED, THEN CLICK ON 'CONNECTED AS' AND CHANGE TO PTP MODE.
On Android 4.2 or later when you replug the usb cable after enabling usb debugging
for the first time you will get a popup asking you to authenticate your pc.
Tick 'Always allow' then click 'ok' and everything should carry on as normal.
LASTLY BEFORE STARTING, LOOK IN DEVELOPER OPTIONS IF YOU NEED TO CHECK THE
'ENABLE/ALLOW OEM UNLOCKING' OPTION TO ALLOW THE DEVICE TO BE BOOTLOADER UNLOCKED.
------------------------------------------------------------------------------------
Are you ready to start? Type y[yes] or n[no]:y
Device detected in FASTBOOT MODE
Device Serial Number is: ZX1G4244LL
When prompted, Press the 'Volume up' button to highlight Yes on the screen, then
press the 'Power' button to select it and Unlock your Bootloader. If you are
already unlocked then this will just be skipped and your device will not be wiped.
ERROR: The device cannot be bootloader unlocked in its present state
You need to enable OEM Unlock in developer options in Developer options..
Once the device has rebooted to Android do this and the Unlock routine should work
any help
Ok... You need to stop trying to unlock your bootloader. You can't.
You have a couple of options:
1 - If you have TWRP recovery installed, flash a custom rom and you'll be good to go.
2 - If you do not have a custom recovery, try flashing the N OTA from here: http://developer.android.com/preview/download-ota.html. After that, go here https://www.google.com/android/beta and enroll and then unenroll your device. Soon after (up to a day, probably) you'll get an OTA for Marshmallow.
You might want to unlock your bootloader while you're in the N preview, so you won't have to go through this again...
Edit: Reading your post again I realised you probably don't have TWRP installed, since you wouldn't have gotten that far with an OTA in that case.
C:\android>adb sideload <ota-package>
The syntax of the command is incorrect.
C:\android>
thanx to replay
but not work with me cannot read update zip:crying:
I'm assuming you know the basics here, so I'm not going to go into much detail.
Before starting, make sure you have the ADB drivers installed and have ADB in a directory on the PC.
Rename the OTA file to something simple, e.g. n6ota.zip.
Go here and follow the steps, including the Option 2 instructions here to factory reset the device.
After the factory reset, enter recovery once again and make sure the recovery is set to adb sideload mode. If you don't have it set to this mode the OTA will not install.
Open a command prompt in the directory where ADB is located and type "adb sideload [filename.zip]", replacing filename.zip with the name of the OTA file. For example, using the name I gave above for the OTA file, the command would be "adb sideload n6ota.zip".
Strephon Alkhalikoi said:
I'm assuming you know the basics here, so I'm not going to go into much detail.
Before starting, make sure you have the ADB drivers installed and have ADB in a directory on the PC.
Rename the OTA file to something simple, e.g. n6ota.zip.
Go here and follow the steps, including the Option 2 instructions here to factory reset the device.
After the factory reset, enter recovery once again and make sure the recovery is set to adb sideload mode. If you don't have it set to this mode the OTA will not install.
Open a command prompt in the directory where ADB is located and type "adb sideload [filename.zip]", replacing filename.zip with the name of the OTA file. For example, using the name I gave above for the OTA file, the command would be "adb sideload n6ota.zip".
Click to expand...
Click to collapse
apply update from ADB
not work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UNLOCKING THE BOOTLOADER
WARNING:- UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete
all personal data from your device such as apps, photos, messages, and settings.
INSTRUCTIONS:-
Make sure to take a backup of your entire device data.
Go to Settings>About Phone>Tap build number continuously until you enable developers option,under developers option enable oem unlocking.
Download the Minimal ADB and Fastboot.
Install the latest Motorola USB Drivers.
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
In Search Menu, search for Minimal ADB and Fastboot and open it.
Connect your Phone to PC.
Type this in the CMD prompt window:- fastboot oem get_unlock_data
You will get a return string.The returned string will be used to retrieve your unlock key. Copy it. [Right Click-Mark- Mark the text by pressing the shift key-Now press Ctrl+C]
Paste all the lines together in a notepad. Remove the empty spaces.
Example:-
On a Windows Desktop, the returned string format would be
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Now go to the Motorola Site. Sign in using your Google account or Motorola ID. Scroll down the page and paste the copied string in the field at step #6. Then click on ‘Can my device be unlocked?’, after which a "REQUEST UNLOCK KEY" button will appear at the bottom of page.
To get your unlock key, select the ‘I Agree’ option. Note: You will receive an email with your Unlock Key at the email address you used to log in there.
Important – Copy the 20-character key that Motorola sent you via email. Make sure your device is connected.
Then in CMD type: fastboot devices (To check your device is connected)
Then type: fastboot oem unlock UNIQUE_KEY
NOTE:- In above command, replace the word ‘UNIQUE_KEY’ with the unlock code that you got via email. Then hit enter and the unlocking process should begin.Once done your device will reboot.
RELOCKING THE BOOTLOADER
INSTRUCTIONS:-
Boot into fastboot mode.
Open cmd and type:- fastboot oem lock
Done.
FLASHING CUSTOM RECOVERY
Method 1:
Currently we don't have a separate recovery partition to flash recovery directly,so we have to temporarily boot twrp by the following process.
INSTRUCTIONS:-
Download the lastest TWRP Recovery from here.
Rename the downloaded recovery to twrp.
Boot device into fatboot mode.
Connect device to PC.
Open CMD in the downloaded folder and type:- fastboot boot twrp.img
Done.
Method 2:
Thanks to @lalitjoshi06 for the permanent twrp installer.
Follow the instructions from his thread TWRP INSTALLER
ROOTING THE DEVICE
INSTRUCTIONS:-
Download the latest Magisk Stable/Beta Zip from here.
Boot into custom recovery
Flash the downloaded zip
Reboot
Contributors:-
@rushiranpise
@smyaknti
@dayask
@nageen9211
@lalitjoshi06
@erfanoabdi
Version Information:-
Status:- Stable
Created 2018-10-26
Last Updated 2019-01-15
Join us on Telegram:-
Official Group
Official Channel
Join us on Whatsapp:-
Official Group
is it tested ?
Let me know if anyone tested this method with screenshots.
Sorry If I doing any wrong...
Thanks to the creator of this method..
tnmsrkr said:
Let me know if anyone tested this method with screenshots.
Sorry If I doing any wrong...
Thanks to the creator of this method..
Click to expand...
Click to collapse
Everything is tested. This method works.. Only need to test relocking the bootloader part..
THANK YOU
rushiranpise said:
everything is tested. This method works.. Only need to test relocking the bootloader part..
Click to expand...
Click to collapse
thanks bro
hello guys i am probably stucked between these 3 phones, HONOR 8X, MOTO ONE POWER & POCO F1. but as i see all these Forums ,talking about the unlocking codes which might be hard to find these days ,so i am quite confused which one should i buy? probably the most important thing for me right now is to UNLOCK BOOTLOADER ,ROOT and have some fun. Please suggest!!
Russel Got stucked said:
hello guys i am probably stucked between these 3 phones, HONOR 8X, MOTO ONE POWER & POCO F1. but as i see all these Forums ,talking about the unlocking codes which might be hard to find these days ,so i am quite confused which one should i buy? probably the most important thing for me right now is to UNLOCK BOOTLOADER ,ROOT and have some fun. Please suggest!!
Click to expand...
Click to collapse
Good luck unlocking a Honor device mate.
You can buy a poco but as you're in a Moto thread I guess you've noticed: we have Unlocking and Flashing guides, sooo... you know... Explains your question. If you still cannot decide, buy Poco F1, I heard they allow the fun without voiding stuff people cry about!
smyaknti said:
Good luck unlocking a Honor device mate.
You can buy a poco but as you're in a Moto thread I guess you've noticed: we have Unlocking and Flashing guides, sooo... you know... Explains your question. If you still cannot decide, buy Poco F1, I heard they allow the fun without voiding stuff people cry about!
Click to expand...
Click to collapse
Thanks mate!! I have made up my mind!. I am going for the Poco f1?
Unable to unlock
C:\adb>fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixe: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.001s
Hello I am getting this error, I have enabled OEM unlocking and USB debugging. Also the phone is showing in fastboot boot while typed the command "fastboot devices". Any help ?
DriftClash said:
C:\adb>fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixe: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.001s
Hello I am getting this error, I have enabled OEM unlocking and USB debugging. Also the phone is showing in fastboot boot while typed the command "fastboot devices". Any help ?
Click to expand...
Click to collapse
Try again. It happens sometimes
About flashing recovery shouldn't it be, fastboot flash recovery twrp.img
souvik095 said:
About flashing recovery shouldn't it be, fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Actually fastboot boot twrp.img is used to boot using twrp. It'll only happen once and will leave you stock recovery untouched after next reboot. It just boots the twrp for once. While fastboot flash recovery twrp.img is used to replace stock recovery with twrp.
I think this is the case.
There are some devices that won't let you boot directly like this and others will boot the image in a one go.
Someone correct me if I am wrong.
I'll suggest you to use command "fastboot flash recovery twrp.img" to avoid any problems.
fastboot boot or flash..?
As it turns out, we have a A/B partition setup on moto one power, which means there is no separate recovery and boot partiion.
when we are doing fastboot flash ...| its flashing the boot partion. which in this case will break things, the correct way to do this is
fastboot boot ... and then get twrp installer and take it from there.
This method to unlock bootloader works in moto one xt1941-5?(not moto one power) i suposse yes, but better can secure
how to remove unlocked bootloader warning message
write logo but same
please help
rooting moto one power
i have successfully unlocked my moto one power bootloader..but unable to flash magisk zip..it says unable to verify signature of zip..
kindly let me know step by step if anythg is required to be done after booting twrp and before flashing magisk in step by step..who so evver have successfully done the process..
it would be very helpful..
Does unlocking the bootloader breaks widevine l1 as i have heard in many cases and relocking bootloader doesn't reverse the status all we are left with is widevine l3 can anybody confirm this??
how to check dat?
---------- Post added at 02:10 PM ---------- Previous post was at 02:06 PM ----------
#Tarke
ok can u provide the link for twrl installer zip for moto one power? so that after booting twrp.img i could flash that zip file....if any1 has the file plz provide me the link..
anku11 said:
how to check dat?
---------- Post added at 02:10 PM ---------- Previous post was at 02:06 PM ----------
#Tarke
ok can u provide the link for twrl installer zip for moto one power? so that after booting twrp.img i could flash that zip file....if any1 has the file plz provide me the link..
Click to expand...
Click to collapse
Get in touch with the OP author via telegram. thanks.
anku11 said:
how to check dat?
---------- Post added at 02:10 PM ---------- Previous post was at 02:06 PM ----------
#Tarke
ok can u provide the link for twrl installer zip for moto one power? so that after booting twrp.img i could flash that zip file....if any1 has the file plz provide me the link..
Click to expand...
Click to collapse
Well one way would be to download drm info from playstore
https://play.google.com/store/apps/details?id=com.androidfung.drminfo
Or if by any chance you have netflix check for this hd logo
If it checks even after unlocking the bootloader then widevine l1 was not lost heres a screenshot
Dear friends,
my android device is Honor 9 Lite. Since I bought this phone, I was always able to get into the phone and access my data by using the touch sensor.
But nevertheless, I was forced to add a pattern lock as surrogate solution in case the touch sensor does not work for any reason.
Anyway, last week I hit on a serious problem! I did not know why the device dose not accept the first way (gaining access through fingerprint using the touch sensor) anymore.
It asks me all the time to enter the right pattern lock I set up 6 about months ago. And since I was not asked to enter the pattern lock before, unfortunately I just forgot it :crying:
Therefore, I cant access my device now and I do really have very important files and documents stored on the internal memory, which I do not want to lose by reset my device to factory settings and wiping all the data stored in the internal memory...
So I have searched the Internet - for long hours - for a proper solution that helps me to bypass the pattern lock without being forced to wipe my data.
But unfortunately, I could not find any effective way to gain access again to the internal storage of my phone.
One of the most important problems I hit on while searching the Internet was that there I could not find any way to enable USB Debugging in my locked device since I cannot access the settings....
Unlike some Samsung devices, it seems that there is no way to enter the known Download Mode in new honor devices. When I get to the Recovery Mode, I can see only three options, which are:
Reboot System now
Wipe data / factory reset
Wipe cache partition
The phone is still connected to my home network and my Gmail Account is still working on it. But I also could not find any way where my Gmail Account could be helpful in this case...
Is there any way to bypass the lock screen without losing data on this Honor device?
I hope you can help me to solve my problem and rescue my files...
Waiting for your suggestions :fingers-crossed:
Thank you very much in advance!
Kind regards
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59187
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59184
Sparkrite said:
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
Click to expand...
Click to collapse
Dear Sparkrite,
thank you for your fast response !
I have attached two pictures which show both the EMUI Mode in addition to the Fastboot Mode on my Honor 9 Lite device...
I don´t quite know how to flash TWRP to e-recovery partition, since I cannot reach the device settings and thus I am not able to enable USB Debugging, which seems to be a necessary step to install or flash a new recovery environment on the device!
I also cannot enter the known recovery mode which we know on Samsung devices. I suppose that this has something to do with the operating system (EMUI) the phone is running.
Furthermore, I assume that the EMUI version which is installed on the device is EMUI 8.
I also would like to point out that the known Hisuite Software could´t connect to the device when I tried to connect the device to my Laptop using a USB cable.
Could you perhaps provide me with further information regarding flashing TWRP and gaining access to the data stored on the internal memory.
And is it possible to decrypt the internal data after extracting them from the internal memory?
A possible solution to my dilemma might be that I factory reset the phone and then try to recover the lost data using an Android Data Recovery Software. What would you say about following such a method?
I know that this will be very risky, but do you think that this would be a more effective and guaranteed way to rescue my data?
Thank you very much for your support!
Waiting for your response :good:
Sorry I could not upload the picture direclty from my computer, therefore I add here the links to the images in my album again:
Honor Lite 9 - EMUI Mode:
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59184
Honor Lite 9 - Fastboot Mode:
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59187
I don´t know why the images cannot be opened here. Sorry, this is my first experience on XDA-Developers
The EMUI Version is 8.
And on the fastboot screen there are two lines written in green:
The first line says: PHONE Locked
The second line says: FRP Lock
At the top of the screen I can see the following text:
Fastboot and Rescure Mode
Please connect USB cable to your computer and open HiSuite
Android reboot reason:
AP_S_COLDBOOT 0
NA
volumekey_down_press_process_func
Sparkrite said:
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
Click to expand...
Click to collapse
[/IMG]
Sparkrite said:
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
Click to expand...
Click to collapse
Ok, download and unzip the attached file.
Navigate to the directory 'platform-tools' where you have unzipped the downloaded file.
Open a command (DOS) window within that folder.
Make sure you are in the dir. 'platform-tools.
Enter fastboot mode on the phone and connect to PC,
Type :- fastboot oem get-build-number [ENTER]
Send me the result here and I'll tell you the best method..................
Sparkrite said:
Ok, download and unzip the attached file.
Navigate to the directory 'platform-tools' where you have unzipped the downloaded file.
Open a command (DOS) window within that folder.
Make sure you are in the dir. 'platform-tools.
Enter fastboot mode on the phone and connect to PC,
Type :- fastboot oem get-build-number [ENTER]
Send me the result here and I'll tell you the best method..................
Click to expand...
Click to collapse
Thank you for your support!
I followed the instructions and came to the following result about the build number:
(bootloader) :LLD-L31 8.0.0.144(C432)
OKAY [ 0.006s]
finished. total time: 0.007s
Waiting for your advice
Thank you!
golden.hunter said:
Thank you for your support!
I followed the instructions and came to the following result about the build number:
(bootloader) :LLD-L31 8.0.0.144(C432)
OKAY [ 0.006s]
finished. total time: 0.007s
Waiting for your advice
Thank you!
Click to expand...
Click to collapse
Ok, good, I'll get back to you shortly................
Do you know how to downgrade ?
Do you know how to flash a TWRP and boot to E-recovery ?
NB: e-recovery is a non protected partition and can be flashed with a locked bootloader.
Sparkrite said:
Ok, good, I'll get back to you shortly................
Do you know how to downgrade ?
Do you know how to flash a TWRP and boot to E-recovery ?
NB: e-recovery is a non protected partition and can be flashed with a locked bootloader.
Click to expand...
Click to collapse
Dear Sparkrite,
I have just searched the internet using the key words you have given to me.
It seems that the so called e-recovery is not a common issue for android users. I could barely find anything helpful in this field.
5 years ago, I was thrilled by working and solving problems of android devices. However, in the last 4 years time has changed and I have nearly stopped informing about such issues, since I had too much to do and I have forced too many obstacles with forced me to change my way of life.....
Moreover, my experiences with android devices were also done with Samsung devices. Except from this problem now, I had not worked with Honor devices in the past at all...
Anyway, I have just tried to flash a TWRP file on my Honor 9 Lite device using the known command window after entering the fastboot mode (of course without enabled USB Debugging). But it didn´t work and I have got the following error message:
PS D:\Android files\Honor 9 Lite\platform-tools>fastboot devices
FPMNW18924010946 fastboot
PS D:\Android files\Honor 9 Lite\platform-tools> fastboot flash recovery twrp_honor9_lite_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.650s
How can I flash TWRP on E-recovery without accessing the device settings? and what is the function of downgrading in this context?
What would you advice me to do?
I would be very thankful if you could make me aware on a good video or a helpful article for example, which can help me to get to my aim...
Thank you!
golden.hunter said:
Dear Sparkrite,
Anyway, I have just tried to flash a TWRP file on my Honor 9 Lite device using the known command window after entering the fastboot mode (of course without enabled USB Debugging). But it didn´t work and I have got the following error message:
PS D:\Android files\Honor 9 Lite\platform-tools>fastboot devices
FPMNW18924010946 fastboot
PS D:\Android files\Honor 9 Lite\platform-tools> fastboot flash recovery twrp_honor9_lite_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.650s
How can I flash TWRP on E-recovery without accessing the device settings? and what is the function of downgrading in this context?
Thank you!
Click to expand...
Click to collapse
Well that command is doomed to fail for two very good reasons:-
1. Locked Bootloader.
2. The H9L using Oreo doe NOT have a 'recovery' partition as such.
The command to flash a custom recovery is :- 'fastboot flash recovery_ramdisk twrp.img'.
But as your BL is locked this will not work, however you can flash it to e-recovery using :-
'fastboot flash erecovery_ramdisk twrp.img'.
The advantage of downgrading (to at least B132 you have b144) is twofold:-
1. You could use HCU to get your BL code to unlock. (€4
1a. Or you could get your 'Slock' code to flash to 'unlock' your BL for free.
But unfortunately this would also wipe your phone.
2. Downgrading, using the Dload (Google it) method may well bypass the pattern unlock screen and/or fingerprint working again.
Edit:
Flash a working TWRP and come back to me when you can boot to it.
I may just have a workaround for you.
Sparkrite said:
Well that command is doomed to fail for two very good reasons:-
1. Locked Bootloader.
2. The H9L using Oreo doe NOT have a 'recovery' partition as such.
The command to flash a custom recovery is :- 'fastboot flash recovery_ramdisk twrp.img'.
But as your BL is locked this will not work, however you can flash it to e-recovery using :-
'fastboot flash erecovery_ramdisk twrp.img'.
The advantage of downgrading (to at least B132 you have b144) is twofold:-
1. You could use HCU to get your BL code to unlock. (€4
1a. Or you could get your 'Slock' code to flash to 'unlock' your BL for free.
But unfortunately this would also wipe your phone.
2. Downgrading, using the Dload (Google it) method may well bypass the pattern unlock screen and/or fingerprint working again.
Edit:
Flash a working TWRP and come back to me when you can boot to it.
I may just have a workaround for you.
Click to expand...
Click to collapse
Well thank you for your response!
The locked bootloader on my phone seems to be the most important obstacle which prevents me from installing anything on the device
I have tried to flash the TWRP file to E-recovery using the command window in the file of platform-tools and a custom recovery for Honor 9 Lite. But this didn´t work either...
I always got the error message:
FAILED (remote: Command not allowed)
I know that this error occurs due to the locked bootloader, but I could not find any proper and effective way to unlock the bootloader on my honor device without access to my device settings....
I have also found out that my device belongs to the supported models on HCU-Client-Website. But as I have seen, the process of unlocking the bootloader using this method requires also a certain interaction with the device, which means that the internal files and settings of the phone must be accessible in order to get the code to unlock the bootloader...
Therefore, being unable to unlock the bootloader prevents me from flashing a TWRP. And being unable to unlock the bootloader prevents me also from downgrading the software and installing a custom rom on the device (see for example: https://forum.xda-developers.com/9-lite/development/kangvip-rom-emui-8-0-t3775904)
It is completely OK for me to buy HCU-tool to get the code to unlock the bootloader, if this can help me to gain access to the internal memory without data loss. But does this work in my case, without the ability to open the device.?! And if yes, how does this go or where can I find near instructions to achieve this mission?
And is there any way to downgrade the phone without unlocking the bootloader or flashing a custom recovery? If this was possible, then I would try to flash a custom recovery and delete the password file through a special file called aromafm and with the help of my SD-Card, which was a successful way five years ago when I was able to bypass the pattern lock on the device of my cousin without any data loss....
In the worst case, I would simply factory reset the phone and try to recover the important files using a good recovery software.....
I think, this may be the most appropriate method with minimal time exposure, since I must gird myself to start the new semester at the university...:good:
Waiting for your advice
Thank you once again :fingers-crossed::good:
As I said it is possible to flash TWRP to E-recovery even with a locked bootloader !!!
I have done it many times.
You will NOT unlock BL while on B144, without code.
HCU will NOT work with build numbers above 132.
ALL BL unlocking WILL re-set and wipe phone.
Downgrading using Dload method is possible with locked bootloader !!!
Search here:- https://pro-teammt.ru/online-firmware-database-ru/?firmware_model=lld-l31&firmware_page=0
Make sure it is a Dload ROM, it will say so within instructions in zip.
If you re-set phone, data WILL be gone, remember it is encrypted so no recovery.
My Advice is:-
Persevere with flashing TWRP to Erecovery.
Erecovery_ramdisk is NOT protected.
" fastboot flash erecovery_ramdisk twrp.img "
Sparkrite said:
As I said it is possible to flash TWRP to E-recovery even with a locked bootloader !!!
I have done it many times.
You will NOT unlock BL while on B144, without code.
HCU will NOT work with build numbers above 132.
ALL BL unlocking WILL re-set and wipe phone.
Downgrading using Dload method is possible with locked bootloader !!!
Search here:- https://pro-teammt.ru/online-firmware-database-ru/?firmware_model=lld-l31&firmware_page=0
Make sure it is a Dload ROM, it will say so within instructions in zip.
If you re-set phone, data WILL be gone, remember it is encrypted so no recovery.
My Advice is:-
Persevere with flashing TWRP to Erecovery.
Erecovery_ramdisk is NOT protected.
" fastboot flash erecovery_ramdisk twrp.img "
Click to expand...
Click to collapse
Dear Sparkite,
Thank you for your fast response!
I have been trying to downgrade and install TWRP Recovery on my device for almost three hours now, however, unfortunately without success
I have tried many times to flash TWRP to E-Recovery-Partition exactly as your have described in the last post, but I always got the same error message:
FAILED (remote: Command not allowed)
I have also tried to do the installation using different platforms and different TWRP files and sometimes with light changes in the code, but all my attempts failed...
My trials to downgrade the device to a version under 132 using my SD Card were also frustrating. I always got the same error, after the installation process reached 5%:
Software install failed!
Get help from: http://www.emui.com/emotiondownload.php?mod=restore
I tried to downgrade the device to the versions 8.0.0.0.127 and 8.0.0.0.131 and 8.0.0.0.129, which I downloaded from the website you have given to me. Also without success....
By the way, I could not find any instruction files in the zipped update files which I have downloaded from the website, therefore it was impossible for me to find out whether the downloaded Rom was compatible with the dload-method or not.
Also the program called "HuaweiUpdateExtractor", which I tried to use as an auxiliary means didn´t accept the UPDATE.APP and I always got the following error message:
ERECOVERY_VBMET.img: Invalid header crc - Expected: 33542 Got: 25244
It seems that there is no way out, right?
If there is a certain custom rom you can suggest for me, I would be very grateful.
Maybe I can succeed in flashing TWRP after downgrading the software installed. But I do not know if there is still a method that I didn´t try on this immune system....
Thank you in advanced!
I don't know what you are doing wrong.
It IS possible to flash TWRP to Erecovery as I have said many times before.
Try a different USB lead.
Try a different USB Port.
Try a different 'fastboot'/'ADB' version.
Try a different TWRP. (https://mega.nz/#!wotVWBQZ!ZO9DHD-HBMj-5LCxxW_74IYsDoSrVDeZsaQgMyIvuGQ)
Send me a screen shot of your command(s)
Send me a screenshot of your phone when you are trying to flash.
Sparkrite said:
I don't know what you are doing wrong.
It IS possible to flash TWRP to Erecovery as I have said many times before.
Try a different USB lead.
Try a different USB Port.
Try a different 'fastboot'/'ADB' version.
Try a different TWRP. (https://mega.nz/#!wotVWBQZ!ZO9DHD-HBMj-5LCxxW_74IYsDoSrVDeZsaQgMyIvuGQ)
Send me a screen shot of your command(s)
Send me a screenshot of your phone when you are trying to flash.
Click to expand...
Click to collapse
Dear Sparkite,
I have just tried all the alternative ways you suggested, unfortunately without success and I don´t know where the mistake in hiding
Again and again I hit on the same problem and I always got the same error message:
Command not allowed...
I have attached two pictures that show the fastboot screen of the device in addition to the commands I gave in the command window...
Thank you for your support!
View attachment 4806745
View attachment 4806753
View attachment 4806760
golden.hunter said:
Dear Sparkite,
I have just tried all the alternative ways you suggested, unfortunately without success and I don´t know where the mistake in hiding
Again and again I hit on the same problem and I always got the same error message:
Command not allowed...
I have attached two pictures that show the fastboot screen of the device in addition to the commands I gave in the command window...
Thank you for your support!
View attachment 4806745
View attachment 4806753
View attachment 4806760
Click to expand...
Click to collapse
Here the screenshot of the command window:
View attachment 4806761
golden.hunter said:
Here the screenshot of the command window:
View attachment 4806761
Click to expand...
Click to collapse
My bad, I'm so sorry to have put you through all this, I forgot that I had previously flashed 'slock' to any H9L to enable flashing to Erecovery. Apologies.
However in order to obtain a slock file for your phone you will HAVE to downgrade to at least B132.
Get a Dload firmware from here:- https://androidhost.ru/
When you have successfully downgraded we can go about getting a 'slock' file for you.
Or if you like you could go here on Telegram and join up to get your 'slock' :-
https://t.me/joinchat/I0ghclds9xtiC-5XLKIQrw
NB: Read the welcome message very carefully and follow it to the letter or you WILL get banned.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION:
Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here
Pre-Requisite 3
Your device needs this with unlocked bootloader
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
And now, how to install:
1.Reboot phone to Fastboot mode (via adb -type adb reboot bootloader)
2.Download patched vbmeta and TWRP recovery
3.Extract it to folder with minimal adb and fastboot
4.Open cmd in this folder and type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5.Then type fastboot reboot bootloader
6.Type fastboot flash recovery twrp_3.3.1_decrypt_works_by_alexeei.img
7.Press volume - and select Reboot recovery, then press power button
8.Enjoy
What worked:
All functions (may be if not, please say). Also TWRP now see exFAT microsd.
Thanks wzsx150 for it's TWRP for Lenovo Z5 Pro GT, some decrypt stuff taken from it.
This is f*cking awesome. Thank you for your efforts. Will install asap and bring some feedback.
Is it working ? Any custom roms then ?
Please provide custom ROM the official ROM is no less than terrible and bad.
Finally compiled TWRP with decryption support, added in first post
hammad5507 said:
Please provide custom ROM the official ROM is no less than terrible and bad.
Click to expand...
Click to collapse
There are some "globalised" china roms which are doing a decent job (with notifications sound fixed, chinese bloatware removed and google services installed), I recommend the one made by Francko76.
Also you can try all the treble stuff out there. I only tried two GSIs so far and I went back to Francko´s build.
Anyway I´m like you looking forward z6 pro dedicated custom roms.
descarao81 said:
I recommend the one made by Francko76.
Click to expand...
Click to collapse
Can you share a link to the Roms you mentioned ?
thanks
descarao81 said:
There are some "globalised" china roms which are doing a decent job (with notifications sound fixed, chinese bloatware removed and google services installed), I recommend the one made by Francko76.
Also you can try all the treble stuff out there. I only tried two GSIs so far and I went back to Francko´s build.
Anyway I´m like you looking forward z6 pro dedicated custom roms.
Click to expand...
Click to collapse
benjieb said:
Can you share a link to the Roms you mentioned ?
thanks
Click to expand...
Click to collapse
what rom is Francko´s build? if you have a link, can you share it please?
Sorry to ask, is this vbmeta patched only for this device or can i installed in others device ?
Please share the links
Please share links for the Franko's build.
and also is there any custom pie rom available??
Pls share if any.. I am very unsatisfied with the global rom. Pls help.
@alexei sir, can you make custom kernel or give way to our devices gets exfat support ?
this is twrp for Lenovo Z6 (not pro) ?
geepnozeex said:
this is twrp for Lenovo Z6 (not pro) ?
Click to expand...
Click to collapse
No this is Twrp for Z6 Pro ( L78051 )
Very tempted to get this phone... has anyone try with phh’s GSI? Does under screen scanner works?
alexeei said:
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION:
Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here
Pre-Requisite 3
Your device needs this with unlocked bootloader
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
And now, how to install:
1.Reboot phone to Fastboot mode (via adb -type adb reboot bootloader)
2.Download patched vbmeta and TWRP recovery
3.Extract it to folder with minimal adb and fastboot
4.Open cmd in this folder and type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5.Then type fastboot reboot bootloader
6.Type fastboot flash recovery twrp_3.3.1_decrypt_works_by_alexeei.img
7.Press volume - and select Reboot recovery, then press power button
8.Enjoy
What worked:
All functions (may be if not, please say). Also TWRP now see exFAT microsd.
Thanks wzsx150 for it's TWRP for Lenovo Z5 Pro GT, some decrypt stuff taken from it.
Click to expand...
Click to collapse
At step 4 I'm getting "fastboot: unknown option -- disable-verity"
Any idea?
Thanks
threeeye said:
At step 4 I'm getting "fastboot: unknown option -- disable-verity"
Any idea?
Thanks
Click to expand...
Click to collapse
NVM, just updated the adb tools and now everything is good
Restore stock bootloader?
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
kagoromo said:
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
Click to expand...
Click to collapse
Share screenshot, I think this normal boot step when BL is unlocked on lenovo / Zuk phones.
benjieb said:
Share screenshot, I think this normal boot step when BL is unlocked on lenovo / Zuk phones.
Click to expand...
Click to collapse
Here is the "The boot loader is unlocked..." screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here's the boot loader:
kagoromo said:
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
Click to expand...
Click to collapse
Do you try flash qfil rom after lock bootloader?
Hello everyone, yesterday morning, Sunday 12/15/19, the system message "restart the device to make the system update effective".
So I do as I have always been.
The phone, an Mi A2, goes into bootloop and then a white screen appears on a black background with the title:
"<!> Failed to boot"
"Press the Volume keys to select then the Power button to continue.
RETRY
POWER OFF "
Choosing "RETRY" verifies bootloop 3 or 4 times and then the recovery mode screen appears which says:
"Can't Load Android system. Your data may be corrupted. You should get the message you need to perform at factory data reset and erase all user data stored on this device."
It gives me the choice between:
-Try again
-Factory data reset
Choosing "Try again" returns the same routine as when "RETRY" is selected In the previous black background screen, bootloop and then the black background white screen described at the beginning.
I MUST ACCESS AND SAVE THE VERY IMPORTANT CONTENT. :crying:
I have all the photos and videos of my newborn daughter. I usually backup but this inconvenience suddenly caught me.
I surfed and I saw that many people found this problem after an update .. but I never found any solutions. I called the Xiaomi center in Novara indicated by the site but they told me that they only serve as a collection center to send to the assistance in the company Xiaomi, saying that the assistance resets the phone to restore its functioning and does not save the data. I tried to start the fastboot, the device is recognized by the PC and shows the locked bootloader. The program MiFlash asks me to start to install a set of drivers and then immediately generate an unhandled exception and crash.
Attached the images.
Can you help me? I do not know what to do..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".
Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.
Aerobatic said:
Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.
Click to expand...
Click to collapse
Thank you, can you explain me better what I should try to do?
HTCDevil said:
You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".
Click to expand...
Click to collapse
Is there any guide to do that?
pedrix82 said:
Is there any guide to do that?
Click to expand...
Click to collapse
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.
pedrix82 said:
Thank you, can you explain me better what I should try to do?
Click to expand...
Click to collapse
First you can try to search this forum and read dozens of discussions of the same issue. Meanwhile you can plug in power adapter and reboot several times with pauses, probably sometimes switching to stock recovery and to fastboot mode, and then leave phone powered for a night.
HTCDevil said:
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.
Click to expand...
Click to collapse
Thanks....I will try, I don't remember if I enabled the usb debugging mode, for sure I saw with fastboot that I have the bootloader Locked.
nothing to do...i tried ADB mode, but it is not enabled, only fastboot mode where i can do nothing because the bootloader is locked.
I also tried to install the Xiaomi tool, but it doesnt recognize the device.
i dont know what to do....
Did you try the factory data reset?
1N4148 said:
Did you try the factory data reset?
Click to expand...
Click to collapse
Hello...ehm...not, the aim is to recover all the data, photos and documents that are stored inside...
Same thing happened to me. You should manually switch the active partition in fastboot.
Zedsdeadbaby said:
Same thing happened to me. You should manually switch the active partition in fastboot.
Click to expand...
Click to collapse
Hi, I already tried to do what you suggest, but it is not possible with the bootloader Locked.
Anyway, can you tell me what I have to do to change the active partition? Maybe I don't do it as I should....
@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.
Aerobatic said:
@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.
Click to expand...
Click to collapse
Thanks,
It's really long time that I'm rebooting the mobile since it happened...
But cyclically and alternate I got the two image attached to the main post....
try a "fastboot continue" in adb
hello everyone, update.
unfortunately I was unable to recover anything and proceeded with the factory reset.
The phone has reset and everything is working.
So I thought to try to do a file recovery as you do for deleted files.
for the various recovery applications I need to root the device.
For this phone should be really simple but I'm still stuck in.
I followed one guide, then another, and then another .... all with the same procedures.
the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone.
but from this recovery, even if I install Magisk, with a successful results from the recovery, I do not root the device. I verified root with Magisk manager and rootchecker.
Help.... thanks
pedrix82 said:
... So I thought to try to do a file recovery as you do for deleted files.
Click to expand...
Click to collapse
I do no believe you'll be able to undelete files after factory reset.
pedrix82 said:
... for the various recovery applications I need to root the device. ... I followed one guide, then another, and then another .... all with the same procedures.
Click to expand...
Click to collapse
This guide works for everybody, except that
(1) there is obsolete "fastboot oem unlock" command stated which should better be changed to "fastboot flashing unlock", and
(2) guide does not mention that each unlock step is to be approved on phone, and
(3) guide skips step of patching stock boot.img in phone with MagiskManager, - while exactly this step creates archived copy of stock boot image in /data root, thus allowing to restore images (actually restoring stock boot image) before downloading next OTA, and
(4) only 1st variant - that is booting into patched boot image and then making "Direct Install" is safe - it allows to check that patched boot image is suitable for ROM.
pedrix82 said:
...the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone....
Click to expand...
Click to collapse
IMHO that just means that you did not do your homework (I mean you have not read guides and discussions and Google info with links I provided) well enough to understand that with A/B slots partitions structure there is no separate /recovery partition in phone (instead, recovery is embedded into /boot image), and thus we cannot just "flash TWRP" into MiA2.
Instead, TWRP can only be embedded into boot image (patching previously flashed suitable boot image), which is made by installing TWRP.zip in temporarily booted TWRP.img. Thus, if you want to have both root and permanent TWRP (I still do not see why anybody needs permanent TWRP with rooted stock), first get root with patched boot image, and then install TWRP patching this Magisk-patched boot image once more.
And I do think that "TWRP 4pda edition" is working better than so called "official TWRP".
Found the solution,
First u need to get to the recovery menu by pressing vol up + power, tap it multiple times after retry boot...you have to be quick...and eventually will get to the android robot pic with "no command"....keep pressing till you get to the full recovery menu. (this might take multiple tries)
Then go to update using adb. (you need all the files for adb, usb drivers, latest mi a2 update zip, you can find tutorials in youtube/google )
after updating it should boot up fine with all data intact.
If latest update versions dont boot, try repeating will older version.
Make sure you backup everthing afterwards! and enable oem unlocking &usb debugging for potential future issues.
Hope this helps!