hello everyone this is topic for root redmagic 8 pro easy away
Frist Step Download RedMagic Rom From here
https://rom.download.nubia.com/Europe%26Asia/NX729J/V318/NX729J-update.zip
now open bootloader from developer option
reboot your phone to fast boot then enter this commind
Code:
fastboot flashing unlock
after unlocking boot loader
need to unlock cirital
Code:
fastboot flashing unlock_critical
reboot your phone to fastboot again open fastboot cmd and enter :
fastboot flashing unlock_critical
after finished all setting install magisk apk and patch
init_boot.img and boot.img
copy patch img from phone to windows folder after patch via magisk
now reboot your phone to fastboot and open fastboot cmd enter this cmd
Code:
fastboot flash init_boot_a xxxxxxxx
fastboot flash init_boot_b xxxxxxxx
fastboot flash boot_a xxxxxxx
fastboot flash boot_b xxxxxxxx
replace xxxxx with location patch in windows
I apologize if the explanation is not clear. If you have any questions, ask them here
this way is tested and working 100%
afer download frimware copy to your phone then update via ota local update
topadstore said:
afer download frimware copy to your phone then update via ota local update
Click to expand...
Click to collapse
Have u tried recalibrate fingerprint?
kaiwayne said:
Have u tried recalibrate fingerprint?
Click to expand...
Click to collapse
The fingerprint will not work. Root the device. There are other ways to fix this problem
topadstore said:
The fingerprint will not work. Root the device. There are other ways to fix this problem
Click to expand...
Click to collapse
I already know. The problem is even passing the test, i cant input any screen lock. Everytime i tried this msg appear "Screen lock was already changed. Try again with the new screen lock". Cant pass this step so cant move to fingerprint
topadstore said:
hello everyone this is topic for root redmagic 8 pro easy away
Frist Step Download RedMagic Rom From here
https://rom.download.nubia.com/Europe%26Asia/NX729J/V318/NX729J-update.zip
now open bootloader from developer option
reboot your phone to fast boot then enter this commind
Code:
fastboot flashing unlock
after unlocking boot loader
need to unlock cirital
Code:
fastboot flashing unlock_critical
reboot your phone to fastboot again open fastboot cmd and enter :
fastboot flashing unlock_critical
after finished all setting install magisk apk and patch
init_boot.img and boot.img
copy patch img from phone to windows folder after patch via magisk
now reboot your phone to fastboot and open fastboot cmd enter this cmd
Code:
fastboot flash init_boot_a xxxxxxxx
fastboot flash init_boot_b xxxxxxxx
fastboot flash boot_a xxxxxxx
fastboot flash boot_b xxxxxxxx
replace xxxxx with location patch in windows
I apologize if the explanation is not clear. If you have any questions, ask them here
this way is tested and working 100%
Click to expand...
Click to collapse
You do not need to patch boot.img and flash it, only patching init_boot.img is needed.
kaiwayne said:
I already know. The problem is even passing the test, i cant input any screen lock. Everytime i tried this msg appear "Screen lock was already changed. Try again with the new screen lock". Cant pass this step so cant move to fingerprint
Click to expand...
Click to collapse
Is there this section in the phones settings
Settings > Lock screen & security or Security > Clear credentials.
ugene1980 said:
Is there this section in the phones settings
Settings > Lock screen & security or Security > Clear credentials.
Click to expand...
Click to collapse
Yes but grayed out
kaiwayne said:
Yes but grayed out
Click to expand...
Click to collapse
Did you lock the bootloader again?
Lossani said:
Did you lock the bootloader again?
Click to expand...
Click to collapse
Dont need to ask the same thing everywhere,
Locking bootloader after you rooted = Brick....
Excuse guys, after root is it possible to install a module to enable Hey Google with screen off (or in AOD mode)? Owners said that you can say Hey Google with RM8Pro only with screen on, so sad....
VladimiroCampus said:
Excuse guys, after root is it possible to install a module to enable Hey Google with screen off (or in AOD mode)? Owners said that you can say Hey Google with RM8Pro only with screen on, so sad....
Click to expand...
Click to collapse
The other thing that bothers me is that if you have Google Assistant enabled, it breaks voice dictation. So you can't voice text if you want Google Assistant enabled. So sad!
May be interesting testing this phone with custom roms, like CRdroid or similar... a monster of power but with an operating system with some bugs it's a real shame....
topadstore said:
after finished all setting install magisk apk and patch
init_boot.img and boot.img
Click to expand...
Click to collapse
Thanks for the detailed guide.
But I came across this guide from Mr.PvT https://forum.xda-developers.com/t/root-red-magic-8-pro-v3-18.4556901/
He mentioned "Note: Absolutely do not patch the boot file, you will have a continuous boot error"
I am no expert in this, but will patching the boot.img by Magisk causing the situation Mr.PvT mentioned above?
thanks in advance!
i only patched the init_boot and that is all that is needed
Hi
Fingerprint not work with root? Any solution?
Then which is the command to relock the phone? Uninstalled root and.....
It's pretty easy to root the phone, but it's a more finicky to keep lock screen and finger print functionality. This root guide is more comprehensive and if you read the whole thread you will have success.
What worked for me: Working lockscreen after unlocking + rooting
Just got my set today and started tinkering, managed to get it unlocked and rooted and lockscreen is working (both fingerprint and pin) Here is a summary of what I did, maybe not all steps are needed, but this is what worked for me on the first...
forum.xda-developers.com
Took me a few tries to do it
Somebody said flash boot.img and init_boot
and Somebody said no need for boot.img
Who is more accurate?
And should I flash a and b ? Or just write that command?
fastboot flash init_boot (located file)
Dont_touch7 said:
Somebody said flash boot.img and init_boot
and Somebody said no need for boot.img
Who is more accurate?
And should I flash a and b ? Or just write that command?
fastboot flash init_boot (located file)
Click to expand...
Click to collapse
init_boot is all you need to patch with Magisk to gain root. Just flash it to the active slot. If you dont know your current slot:
fastboot getvar current-slot
DarkestSpawn said:
init_boot is all you need to patch with Magisk to gain root. Just flash it to the active slot. If you dont know your current slot:
fastboot getvar current-slot
Click to expand...
Click to collapse
Based on experience, you just have to run the command:
fastboot flash init_boot <patched_file>.img
It will automatically be flashed on the current active slot.
Related
Hi,
I'm new to Z2 play ROM/TWRP things and here's my issue on a XT 1710-01 (on retca channel):
After unlocking my bootloader, I've installed TWRP 64 bits and did a backup before doing anything else, but for whatever reason, restoring it didn't work. I just thought then that I could re-flash the retail stock ROM available at https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/ , which worked fine (phone boots fine, works fine and is still on retca channel, etc.), except that now, I'm unable to re-lock the bootloader, as I get a message like "signed boot.img required" (or something alike) on "fastboot oem lock" command.
I also get the "bad key" message on the unlock warning at boot time (see attached).
Here are the commands I used to reflash the stock ROM:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
Now, I'm just wondering if I missed something or is it just that the stock ROM I reflashed is not the good one (or just unsigned) . Any help would be appreciate.
Thanks.
Need official signed by Moto image. Not available from any official source unfortunately. I have a same request to lock a bootloader.
it's very important to ask how your parachute Works before you jump off the plane
@KirMit Thanks for the follow-up.
Do you know if it would be an option for me to try to find a complete ROM/backup made by someone with the exact same model (so presumably, with the signed boot.img), flash/restore this backup on my unit and then try to relock the bootloader?
I have the same problem. Cannot find a signed boot.img
If anyone can think of a solution I would be totally interested in hearing about it.
I can live with this phone with the bootloader unlocked, but I may need to sell it, so I need to get rid of that warning screen.
Paulinga said:
I have the same problem. Cannot find a signed boot.img
If anyone can think of a solution I would be totally interested in hearing about it.
I can live with this phone with the bootloader unlocked, but I may need to sell it, so I need to get rid of that warning screen.
Click to expand...
Click to collapse
You can get rid of the warning screen, but you can't get rid of the N/A-Bad Key sign, so you must make your own boot logo (meant to cover those nasty letters with a white background) and ADB flash it as logo.bin... that's if you don't have TWRP recovery; in such case you can use a flashable zip for that matter.
Sent from my Moto Z2 Play using XDA Labs
Please look at this video:
It's in portuguese, but you will understand by just following his steps.
If you want, look at the other videos, all of them will help you(not all are about relocking bl)
If you're on october patch, there is the firmware: https://androidfilehost.com/?fid=11410932744536987421
Thanks to junior passos
xdaVTU said:
Please look at this video:
It's in portuguese, but you will understand by just following his steps.
If you want, look at the other videos, all of them will help you(not all are about relocking bl)
If you're on october patch, there is the firmware: https://androidfilehost.com/?fid=11410932744536987421
Thanks to junior passos
Click to expand...
Click to collapse
Doesn't work on my Z2p. My oem unlock is always greyed out even after trying the instructions in this video with 3 different firmwares.
For anyone who doesn't understand what's going on in the video.
1)flash the firmware.
2)flash twrp, backup boot & system.
3) restore boot and system and reboot
4) go to developer options and, enable oem unlocking
5) return to bootloader and run the lock bootloader bat file.
6)done your locked.
Or if like in my case, it does not work, oem unlocking is still greyed out.
I managed to ungrey oem unlocking but, only by flashing magisk. Somehow magisk ungreys oem unlock? Unfortunately, we cannot lock bootloader with magisk installed. Once magisk is uninstalled, oem unlocking is greyed out again?
I think I know how to get around this, adb pull boot.img that magisk has modified. Full unroot magisk, preferably with magisk uninstall zip. Then fastboot flash the patched boot image and run bootloader lock with the OEM unlock switch set.
---------- Post added at 10:32 PM ---------- Previous post was at 09:49 PM ----------
And I am locked, it worked. I now know how to lock my bootloader even when the video guide above fails to remove the greyed out oem switch.
1)flash the firmware.
2)flash twrp, backup boot & system.
3) restore boot and system
4)flash magisk and reboot
6) back up boot.img to pc
7) flash magisk uninstall zip
8)fastboot flash stock recovery
9) fastboot flash magisk modified boot
10)boot device and enable oem unlocking
11) reboot to bootloader and run bootloader lock bat file
11) oem locked!
By the way, easiest way to back up boot is use the app "partition backup & restore". Be sure to change the setting to save as img and not archive.
Yes! This!
I've never been able to go back to stock and relocking the bootloader because the OEM Unlock was always greyed out. Using the patched boot.img, as @Cupcake 1.5 explains allowed me to lock my bootloader again.
Thank you!
Cupcake 1.5 said:
I managed to ungrey oem unlocking but, only by flashing magisk. Somehow magisk ungreys oem unlock? Unfortunately, we cannot lock bootloader with magisk installed. Once magisk is uninstalled, oem unlocking is greyed out again?
I think I know how to get around this, adb pull boot.img that magisk has modified. Full unroot magisk, preferably with magisk uninstall zip. Then fastboot flash the patched boot image and run bootloader lock with the OEM unlock switch set.
---------- Post added at 10:32 PM ---------- Previous post was at 09:49 PM ----------
And I am locked, it worked. I now know how to lock my bootloader even when the video guide above fails to remove the greyed out oem switch.
1)flash the firmware.
2)flash twrp, backup boot & system.
3) restore boot and system
4)flash magisk and reboot
6) back up boot.img to pc
7) flash magisk uninstall zip
8)fastboot flash stock recovery
9) fastboot flash magisk modified boot
10)boot device and enable oem unlocking
11) reboot to bootloader and run bootloader lock bat file
11) oem locked!
By the way, easiest way to back up boot is use the app "partition backup & restore". Be sure to change the setting to save as img and not archive.
Click to expand...
Click to collapse
TravellingGuy said:
Yes! This!
I've never been able to go back to stock and relocking the bootloader because the OEM Unlock was always greyed out. Using the patched boot.img, as @Cupcake 1.5 explains allowed me to lock my bootloader again.
Thank you!
Click to expand...
Click to collapse
Hi all, ok i'm late unfortunately can you help me ? i have the boot magisk signed and key is ok. But when i'm reflashing recovery stock, there is also a bad key.
So there is still the warning at startup, i think this is due to this issue
smbld said:
Hi all, ok i'm late unfortunately can you help me ? i have the boot magisk signed and key is ok. But when i'm reflashing recovery stock, there is also a bad key.
So there is still the warning at startup, i think this is due to this issue
Click to expand...
Click to collapse
Ha, it's been too long since I used this phone. I can't help, unfortunately.
Even without a custom recovery like TWRP you can get Magisk on your phone.
To do this you need to manually patch the stock boot image and flash that to your boot partition.
However, I've done all of this and with a few steps you'll be rooted.
There's a more detailed guide below.
1) Get bootloader unlock code here
2) Enable "OEM Unlocking", boot into fastboot and type: "fastboot oem unlock your-unlock-code"
3) Download patched ramdisk image here and put it in fastboot directory.
4) Reboot into fastboot and type: "fastboot flash ramdisk patched_ramdisk.img"
(Optional) 5) Flash this to go back to stock ramdisk
[Detailed Guide]
First off, you need an unlocked bootloader. To do this, you need a special code from Huawei, you can request this here:
https://emui.huawei.com/en/plugin.php?id=unlock
With this code, and having "OEM unlocking" enabled in debugger settings, boot in fastboot mode.
Afterwards, open fastboot console and type: "fastboot oem unlock your-unlock-code"
Your device will now reboot.
Now reboot your device back into fastboot mode and open a fastboot console once more.
Download this patched ramdisk partition and place it in the same folder as your fastboot executable.
http://www.mediafire.com/file/9yfz6w9e8q7j5u2/patched_ramdisk.img
Now simply type in the console: "fastboot flash ramdisk patched_ramdisk.img".
Reboot your phone and it is rooted!
Download Magisk Manager to update/configure Magisk.
[REMOVE ROOT]
To remove the root, simply flash this original ramdisk partition, the same way as above. You can also relock the bootloader if wanted.
http://www.mediafire.com/file/4d6w2labc6cmh2o/original_ramdisk.img
WORKS IN ANE-AL00 china model??
When I'm trying to install the patched ramdisk with "fastboot flash ramdisk patched_ramdisk.img" it says "cannot load patched_ramdisk.img".
What's the exactly directory?
@RogerXIII, from which build did you patched ramdisk?
Nick said:
WORKS IN ANE-AL00 china model??
Click to expand...
Click to collapse
Only tested on ANE-LX1, you're welcome to try it though.
r00terb3y said:
When I'm trying to install the patched ramdisk with "fastboot flash ramdisk patched_ramdisk.img" it says "cannot load patched_ramdisk.img".
What's the exactly directory?
Click to expand...
Click to collapse
It has to be in the directory of your fastboot executable.
kilroystyx said:
@RogerXIII, from which build did you patched ramdisk?
Click to expand...
Click to collapse
Version 8.0.0.104 (C185)
Just a clarification. So lite version come with 8.0 ? Not 8.1 ?
otonieru said:
Just a clarification. So lite version come with 8.0 ? Not 8.1 ?
Click to expand...
Click to collapse
Correct
RogerXIII said:
Only tested on ANE-LX1, you're welcome to try it though.
It has to be in the directory of your fastboot executable.
Version 8.0.0.104 (C185)
Click to expand...
Click to collapse
And how do I find out?
r00terb3y said:
And how do I find out?
Click to expand...
Click to collapse
Find out what ? The directory ? Or the compatibilty ?
If the conpatibility, simply try it. And you will know
r00terb3y said:
And how do I find out?
Click to expand...
Click to collapse
I think you mean the directory:
On your computer you have the file "fastboot" that you use for sending fastboot commands to your phone, put the .img file in yhe same folder as that program. If you don't know where it is located, you can download the platform-tools files separately and use those.
Thank you worked very well. I need twrp but i cant find or Build compatibility with p20 do you find any way to get it work?
1) Get bootloader unlock code here
this is giving me a 404 error...
In which compilation (build) did you use this root?
Just got root on ANE-LX1 successfully. Tell me please, should this metod pass SafetyNet or not?
Rooted my ANE-XL3 just fine.
Hi. Huawei P20 lite ANE-LX1 8.0.0.111(C432).
Asking for some advice. Having read several how to guide to root, installed adb on Linux, connected, backup ok, patched ram disk, original ram disk and so on and so on, Running in circles about UNLOCK CODE: OR getting a 404 eng/Chinese, Or logging at Huawei and getting a US page for honor 7/10. Cannot get the unlock page to fill the formulary, although having all necessary info, IMEI, Product ID etc. My region is PT. Request advice, considering returning the phone wich is not so bad at benchmarks... Thank you. Congrats
I payed 5 usd at dc-unlocker and unlocked my bootloader in about 20 minutes. I followed this guide:
https://forum.xda-developers.com/honor-7/general/bl-unlock-dc-unlocker-t3318738
Just got an OTA: ANE-LX1 8.0.0.105(C10). My device OS ver.: ANE-LX1 8.0.0.102(C10). Please tell me, should I apply it? What will happen with root? Will I need to reflash ramdisk after update?
Can someone tell me where to unlock the bootloader? The link gives me only a 404 page
Alucard1238 said:
Can someone tell me where to unlock the bootloader? The link gives me only a 404 page
Click to expand...
Click to collapse
If the link is down you have a paid service, google by DC-unlocker
I just bricked my phone :crying: :crying:
I wanna get back to the official rom, after trying android P (without make it work).
(the rom is from http://en.miui.com/download-354.html)
But I run the wrong script and take the flash_all_lock.img
And my device is stuck on android 8.1 bootloop (It boot, but i get an animated line loop ...)
Any ideas or tricks before i get it back to warranty ?
Thanks
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
BubuXP said:
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
Click to expand...
Click to collapse
But since I flashed the official rom with data whipe, I'm unable to go to dev option and enter OEM Unlocking .... And Fastboot respond me that my device is locked
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
droopeur said:
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
Click to expand...
Click to collapse
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
BubuXP said:
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
Click to expand...
Click to collapse
In fact, both work, but my phone still stucked at the bootloader (infinite line animation in both cases).
BubuXP said:
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
Click to expand...
Click to collapse
Yes I can enter recovery and I have already tried this, but I always end up with the error:
Code:
E: Unknow volume for path [/sideload/package.zip]
Verifying update package...
Update package verification took 17.3 s (result 0)
Installing update...
E:Error il /sideload/package.zip (Status 1)
Installation aborted
BubuXP said:
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
Click to expand...
Click to collapse
Yes of course !
But I revert to stock rom with Mi Flash and I click on Flash all and lock, since the telephone should have been "brand new" it should not have any problems but ...
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
LUNARIO said:
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
Click to expand...
Click to collapse
But since I can't activate OEM I can't unlock bootloader....
try this http://www.xiaomitool.com/ not sure if it works on our phone but maybe can unlock the bootloader so you can use miflash
Have you sideloaded the zip? I think it's better to copy the OTA zip to microSD than ADB sideload.
droopeur said:
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
Click to expand...
Click to collapse
There should be only two methods for entering EDL:
1- request authorization in en.miui.com forum. Sometimes the admins accept requests to give an account one EDL flash permission (but I don't know if it works with AndroidOne devices).
2- finding the test point in the phone's motherboard.
Hi guys,
i tried to install this twrp but it doesnt work...
so i searched on internet and i found another article, i tried to check the current partition and install in another way
for first:
fastboot getvar current-slot
after i do this
fastboot boot_b recovery.img
and then
fastboot set_active b
so nothing to do....but right now my MI A2 lite not boot.
i try again to check my partition but this time i have no replay.
i have unlocked bootloader but i cant go to recovery and i cant boot!!
someone can help me please?
I HAVE THE SAME PROBLEM
everything you said is completely simillar to mine. Can someone help us? Or did you already fix it? Please help me i need my phone working.
I have same problem fastboot flash but after that, it started to reboot automatically. The phone was automatically turning off and on. I again did a "clean all and lock" via miflash tool but still now, no result!
I can boot into recovery without having any problem. But when I boo to setup country date....etc, it starts its auto rebooting process,
Any help ?
droopeur said:
But since I can't activate OEM I can't unlock bootloader....
Click to expand...
Click to collapse
Same situation here. I am desperate!! Did you solve it?
Isso resolve
steledama said:
Same situation here. I am desperate!! Did you solve it?
Click to expand...
Click to collapse
gadgetsfarm.com/download-mi-a2-lite-fastboot-rom-v9-6-4-download/[/url]
How to unbrick?
Hey guys. I bricked my Mi2 Lite as well. Is there any step by step way to unbrick?
had the same problem, was stuck in the bootloop even after I flashed img with MiFlash! NOTE: MY BOOTLOADER WAS UNLOCKED!!! (LUCKLY I DID NOT TRIED FLASH ALL AND UNLOCK!)
headed to this thread
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
did not work, I get error saying FAILED
but after i used
Code:
fastboot oem edl
I went to MiFlash and used "Clean all" option (again note DON'T use "Clean all and lock"!!!). It took around 5 minutes to flash and my notif. light blinked whole the time. After it say "Success" I was able to normaly boot the phone again
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Hi, where i can find MI A2 Lite Tool Kit? i open my device and i can put in EDL mode., my computer detect my pone in EDL mode, but i can not know do.
I like bypass FRP, can anybody help me
Thanks.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse
Hi all,
I also had same problem and I just resolve it.
My phone was in bootloop mode after stock rom flashing...
You don't need apply "fastboot oem edl" !
Just be sure your device is unlocked.
Download first stock rom (V9.6.4.0.ODLMIFF Firmware for Mi A2 Lite). If you flash last ROM, it don't work.
Flash it with XiaoMiFlash tool (don't forget to enable "Clean All") in bottom of the tool.
After reboot, you can apply OTA updates.
Enjoy !
Is there any way to enable back Double Tap to Wake (DT2W), after last update my phone lost this function and in the settings app there is no option for this. Is there any easy way to bring back my phone to June update or to enable dt2w in the last update somehow?
I'm growing tired of xiaomi for being such incompetent in all things related to android one, i kept the phone without root until this day but i really need dt2w, I remember seeing a thread long ago that there was a line in the build.prop to enable or disable it, I'll try to find it and see if it works
sniffviper said:
I'm growing tired of xiaomi for being such incompetent in all things related to android one, i kept the phone without root until this day but i really need dt2w, I remember seeing a thread long ago that there was a line in the build.prop to enable or disable it, I'll try to find it and see if it works
Click to expand...
Click to collapse
But modify system partition will makes system reject the next update.
coolwei1 said:
But modify system partition will makes system reject the next update.
Click to expand...
Click to collapse
It is possible to disable DT2W but you have to root your device.
https://forum.xda-developers.com/mi-a2-lite/help/how-to-disable-dt2w-t3848226
Maybe reverse this tweak to enable dttw ,disable works after reboot phone, i have used rootexplorer to get it done
Nxkealen said:
It is possible to disable DT2W but you have to root your device.
https://forum.xda-developers.com/mi-a2-lite/help/how-to-disable-dt2w-t3848226
Maybe reverse this tweak to enable dttw ,disable works after reboot phone, i have used rootexplorer to get it done
Click to expand...
Click to collapse
Ya, I saw that before. I open the generic.kl file see, the key is not commented out. I also download SetEdit app, the dt2w property is already set to 1.
So I think there is no way to enable it. Is a bug.
I already flash my phone back to 10.0.10.0.
coolwei1 said:
I already flash my phone back to 10.0.10.0.
Click to expand...
Click to collapse
Is that the June update? Please give us a tutorial!
I have theory, I don't know did these updates update or change somehow the kernel but I think the last one had done exactly that. IMHO loadable module or driver responsible for dt2w had been "forgotten" to be built into the kernel.
x0xcdrx0x said:
Is that the June update? Please give us a tutorial!
I have theory, I don't know did these updates update or change somehow the kernel but I think the last one had done exactly that. IMHO loadable module or driver responsible for dt2w had been "forgotten" to be built into the kernel.
Click to expand...
Click to collapse
You can download the 10.0.10.0 image from [FASTBOOT] [daisy] Xiaomi Mi A2 Lite FASTBOOT Images
Then follow steps in How to Flash Fastboot Firmware with Miflash Tool
If you doing this for the first time, you need to learn a lot of things and do a lot of research.
If not careful you could brick your phone and do not know how to get out from bootloop
I stuck in bootloop when flash for the first time, don't know what happened, later found out I just need to switch to another partition.
Code:
fastboot getvar current-slot
fastboot set_active a (if current-slot is b) or fastboot set_active b (if current-slot is a)
Required to download platform-tools inside consists of adb and fastboot
coolwei1 said:
You can download the 10.0.10.0 image from [FASTBOOT] [daisy] Xiaomi Mi A2 Lite FASTBOOT Images
Then follow steps in How to Flash Fastboot Firmware with Miflash Tool
If you doing this for the first time, you need to learn a lot of things and do a lot of research.
If not careful you could brick your phone and do not know how to get out from bootloop
I stuck in bootloop when flash for the first time, don't know what happened, later found out I just need to switch to another partition.
Code:
fastboot getvar current-slot
fastboot set_active a (if current-slot is b) or fastboot set_active b (if current-slot is a)
Required to download platform-tools inside consists of adb and fastboot
Click to expand...
Click to collapse
Fastboot doesnt fint the "set_active a" command.
mariohackku said:
Fastboot doesnt fint the "set_active a" command.
Click to expand...
Click to collapse
Then you can use
Code:
fastboot --set-active=a
https://android.stackexchange.com/questions/203124/fastboot-set-active-command-does-not-exist/203149
On the screen I get: your device is corrupted and cannot be trusted and cannot reboot
Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...
blackhawk said:
Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...
Click to expand...
Click to collapse
Thanks for answering
The device may boot into a bootloader or an error on the screen
EranG90 said:
Thanks for answering
The device may boot into a bootloader or an error on the screen
Click to expand...
Click to collapse
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock
craznazn said:
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thank you
I have now done that and the screens are in the same condition as in the pictures
It is good? Should I keep waiting? (I don't know really what to do, I am new at this. I don't know even if the device got the commend from the pc)
We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.
djsubterrain said:
We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.
Click to expand...
Click to collapse
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper
EranG90 said:
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper
Click to expand...
Click to collapse
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
You need to have previously allowed bootloader unlocking in your developer options (see below)
djsubterrain said:
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
Click to expand...
Click to collapse
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)
EranG90 said:
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)
Click to expand...
Click to collapse
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?
EranG90 said:
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?
Click to expand...
Click to collapse
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.
djsubterrain said:
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.
Click to expand...
Click to collapse
Really really thank you
I have tried all 4 commands (-w, --setactive=a/b and reboot)
all of them after I turn off and back on my phone show me the bootloader
can you send me a link to how I use the MSM tool to restore the phone to factory settings?
You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.
craznazn said:
You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.
Click to expand...
Click to collapse
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this
EranG90 said:
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this
Click to expand...
Click to collapse
try
Code:
fastboot reboot fastboot
and what shows up?
https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat
craznazn said:
try
Code:
fastboot reboot fastboot
and what shows up?
Click to expand...
Click to collapse
thank you for answring
that what show up:
Rebooting into fastboot OKAY [ 0.004s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Shooter7889 said:
https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat
Click to expand...
Click to collapse
Thank you
I will try anything to fix that but I am new in all this
Where I am download the flashall.bat? where I save it? How to run it?
I have download the global version for onplus9pro. What I need to do with it?
https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat
Shooter7889 said:
https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat
Click to expand...
Click to collapse
And honestly, you could prob just download the zip I mentioned, the first one just to get the flashall.bat, and just extract it, plug ur phone in(in bootloader mode) and click the flashall.bat. It would put the EU version of OS on your phone. Use cld then use the loavl update in system settings to switch to ur variant after. Much easier.