Related
can someone help me out? i was unlocking my phone. i wasnt concentrating and i mixed up 2 diff steps. so basically i have twrp but my bootloader is locked so i cant boot in to cyanogen which i instlled............ any help?
http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 flash the file in TWRP and continue to unlock - you may need to flash CM again when you all done, but if you have TWRP then unlocking should be easy
@tabletalker7 i do have twrp and i did follow those steps but when i am in bootloader and i type fastboot oem unlock i get nothing
i did try that and i have twrp, but when i go to bootloader and i type fastboot oem unlock i get nothing
ok did you try http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 you can flash the correct stock rom file in TWRP
Thanks man i will see if it works
thankfully it did, but i am still unable to unlock, its stuck on waiting for devices
waiting on devices? Did you reinstall TWRP and then flash the D
rakenFX file?
no in adb command window i am unable to unlock it
the fastboot oem unlock command
http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 post one for us version post 100 for EU version - you have to flash a file in TWRP before you can unlock
could you help me with step 6 fbop_lock.img
US version or EU version?
us
ok - before you go to TWRP ensure that the phone is in USB debugging mode and Enable OEM unlock is on
yup done
after that?
boot to TWRP, then plug into PC. Open a command prompt and type "adb devices". You should see the serial number of your device and recovery as it's state
---------- Post added at 10:48 PM ---------- Previous post was at 10:47 PM ----------
When you have that type "adb shell dd if= /dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img" You can even copy from this and paste it in the command prompt
i did that, but after that step 6 idk what that is
When it is done with all that type "adb pull /sdcard/fbop_lock.img"
Hi, I'm new to this phone. Just got it 1 week ago. I tried to find any related information on the bootloader unlock and custom recovery, but it is very limited. I think maybe this phone is not well known. I would appreciate if someone can provide me the way to unlock bootloader, flash TWRP and roots. I can't live without magisk and viper4android. Thanks.
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
thanks
dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
Hi, I've tried numerous timed and it always won't pick up the command of unlocking bootloader. It always stay in the fastboot menu. I've toggled the 'OEM Unlock' function in the developer setting, as well as the USB debugging. Any idea why the device won't pick up that command?
Is it changing to unlock after you enter the command?
If so flash twrp then boot into recovery ...
dantonuci said:
Is it changing to unlock after you enter the command?
If so flash twrp then boot into recovery ...
Click to expand...
Click to collapse
Nope. It doesn't respond to the command in the fastboot. It just shows the fastboot menu. My adb is written 'waiting for device.... '.
Drivers , uninstall all other drivers and try please
dantonuci said:
Drivers , uninstall all other drivers and try please
Click to expand...
Click to collapse
Okay will try again
storytellerz said:
Okay will try again
Click to expand...
Click to collapse
I am also finding this message, what is its solution ???
the same recovery
dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
Hi there, when I flashed the recovery that is always the stock recovery, why?
vins84 said:
Hi there, when I flashed the recovery that is always the stock recovery, why?
Click to expand...
Click to collapse
Not sure what you're asking, did you want to flash TWRP or stock? I was just giving tutorial for how to install TWRP
dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
I'm having the problem. Unlock is not sticking to unlock. The unlock works and the flash works but as soon as you try and reboot into recovery it hangs at a blank screen no twrp. Console says waiting for device and stuck. next time I go into bootloader it says locked. The count is 3 for unlock count is there a limit? 7-6-18 Nubia Z17 NX591J WIn 10.
bmaz121 said:
I'm having the problem. Unlock is not sticking to unlock. The unlock works and the flash works but as soon as you try and reboot into recovery it hangs at a blank screen no twrp. Console says waiting for device and stuck. next time I go into bootloader it says locked. The count is 3 for unlock count is there a limit? 7-6-18 Nubia Z17 NX591J WIn 10.
Click to expand...
Click to collapse
Trouble shoot and experiment with the process it will work, even if it appears not locked after reboot
dantonuci said:
Trouble shoot and experiment with the process it will work, even if it appears not locked after reboot
Click to expand...
Click to collapse
I don't understand? Appears not locked? It is locked. Now I remember when I flashed my Star N997 the developer said that there is a unlock bit that has to be turned on in the process of unlocking. I think this may be the case here since it unlocks until a reboot. I am deep concerned that after a unlock count of 3 the phone will not boot anymore. Do you know anything about these things? Another thought is does the USB C need different drivers and should it be plugged into a USB 3.0 outlet?
TWRP will flash only when it's unlocked so even if it's saying it's locked go by what you can do with TWRP
---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------
I did it several times and never had a problem
i was looking for camera.apk file from Nubia Z17S phone from Stock ROM, can anyone upload it here..it should be located in system / app or app-pvt folder, you can copy using Root Explorer tool.
pls. let me know...
I'm having problems unlocking the bootloader. Has anyone got the proper TWRP for this phone? I can't find it. The one I have says FAILED (remote: Requested download size is more than max allowed). Thanks
hello links no longer works. Someone could give me back the TWRP and minimalb fastboot adb
For anyone's information, TWRP will not boot in recovery while the phone is being charged. Unplug first. You will just get a black screen.
i am also experiencing the same issue.. where can i find the drivers for this phone nx595j? or how do i uninstall the drivers for it?
---------- Post added at 01:21 AM ---------- Previous post was at 01:17 AM ----------
yo can somebody help me install a custom rom on my z17s via team viewer?? im willing to pay for your time
mod please remove this thread
oh hell, i've followed every step exactly and got a bootloop. 1922-5 brazilian model. is it because of the last update?
---------- Post added at 07:20 PM ---------- Previous post was at 07:18 PM ----------
and why does my phone show as a moto e4 now????
---------- Post added at 07:26 PM ---------- Previous post was at 07:20 PM ----------
just a thing: i obviously got some backups and i could revert the bootloop by just flashing the stock boot back into the phone.
if you took the update you have to reflash the updated stock firmware after the update. if need be ill walk you through it ive already done it with one person over facebook messenger and after that they were successful. unfortunately they havent commented on saying so lol or thanked the post. sorry for the late reply also i just got off work lol also if links are dead i got dev access on afh now so ill be putting the new links on here ina bit . also tbh i have no clue why it says moto e4 when we put the twrp recovery on but it doesnt affect anything. it would be nice if we had an official twrp
blowingoff said:
oh hell, i've followed every step exactly and got a bootloop. 1922-5 brazilian model. is it because of the last update?
---------- Post added at 07:20 PM ---------- Previous post was at 07:18 PM ----------
and why does my phone show as a moto e4 now????
---------- Post added at 07:26 PM ---------- Previous post was at 07:20 PM ----------
just a thing: i obviously got some backups and i could revert the bootloop by just flashing the stock boot back into the phone.
Click to expand...
Click to collapse
Moto G6 Play XT1922-3
ninjakira said:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections, ligma,
* thermonuclear war, or your mom getting upset with you for being on the computer all day
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
I've decided to make a new guide for our jeter devices because the other guide is a little sloppy now lol. I have no problem with having this taking down if the op for the original guide decides to clean theirs up. this one should help clear up stuff now at least lol
This has been confirmed to work on:
XT1922-3 Model
XT1922-4 Model
XT1922-5 Brazilian Model
XT1922-7 Boost Mobile
XT1922-9 Model
Please make backups using TWRP IN CASE OF FAILURE.
Original stock firmware can be found here. https://mirrors.lolinet.com/firmware/moto/jeter/official/
The steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first.
Prerequisites:
Unlocked bootloader.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio...platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
Minimal adb/fastboot v1.4.3 installer can be found here. https://androidfilehost.com/?fid=746010030569952951
Step 1.) Download twrp image to the ADB/Fastboot folder on your computer. https://www.androidfilehost.com/?fid=1322778262904017969
Step 2.) Reboot to your bootloader. You can do this by turning on your device and holding power and both volume buttons at the same time.
Step 3.) Once the device reboots to the bootloader type the following from your computer with your phone connected via USB.
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Step 4.) Once TWRP boots from your computer type (it may take a bit to boot because it is trying to decrypt your userdata, but it will fail and prompt for a password. Just click cancel):
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
This will backup your stock boot and recovery images if you to revert to stock later.
Step 5.) Code:
adb reboot bootloader
Step 6.) Run the following command from your computer to install the TWRP image to your device.
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
Step 7.) Use the volume keys on the device to select boot to recovery and TWRP will boot up again. When it prompts for a decryption password select cancel again.
Step 8.) From your computer type the following into your command prompt/terminal from your adb/fastboot folder:
Code:
adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor
Step 9.) Download and extract https://www.androidfilehost.com/?fid=1322778262904017972 this patched fstab.qcom boot image into the ADB/Fastboot folder on your PC.
Step 10.) Run the following command from command prompt/terminal on your computer:
Code:
adb push fstab.qcom /vendor/etc/fstab.qcom
Step 11.) Next click the "Wipe" button in TWRP and slide "Swipe to Factory Reset" THIS WILL WIPE YOUR DATA ON YOUR PHONE. Ensure you have backup.
Step 12.) Download the Magisk Beta 17.2 zip file from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 to your ADB/Fastboot folder.
Step 13.) Run the following command to push the boot image to your device
Code:
adb push Magisk-v17.2.zip /tmp
This will push the Magisk-v17.2.zip to your /tmp folder
Step 14.) Flash Magisk-v17.2.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 15.) Reboot your device
Step 16.) It will say N/A in the top corner of your device for a few seconds. Then it will boot the the Motorola boot screen and you can setup your device as a new phone.
Step 17.) Verify Magisk Manager is installed and the root functionality works. if force encrytion is checked just uncheck it, click install then whatever option magisk recommends then reboot.
step 18.) have fun.
Step 19.)DOWNLOAD STOCK FIRMWARE HERE https://mirrors.lolinet.com/firmware/moto/jeter/official/ UNZIP STOCK FIRMWARE TO YOUR ADB/FASTBOOT FOLDER TO FLASH IT. TO REVERT BACK TO STOCK YOU HAVE TO REFLASH STOCK FIRMWARE FROM THE BOOTLOADER if your device is bootlooped or bricked or not working right you have to reflash the stock firmware your device came with. PLEASE INPUT THESE COMMANDS ONE AT A TIME DO NOT DO THEM ALL AT ONCE. I KNOW ITS A HASSLE BUT IT GUARANTEES A SUCCESSFUL REFLASH. I CANNOT EMPHASIZE THIS ENOUGH
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
if you guys think anything should be edited from this let me know and ill fix it. like im not 100% sure if we still have to use the modified fstabs.qcom i just used it still after i took the update and re-rooted. so if someone can tell me they didnt use the fstabs.qcom and still got the same results please let me know
Credits: @kwiksi1ver for making the original guide. and @topjohnwu for magisk. and @shimp208 for minimal adb/fastboot.
Click to expand...
Click to collapse
It still doesn`t work,i flashed the stock JETER_RETAIL_8.0.0_OPPS27.91-35-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml,code by code with fastboot and gpt.bin,bootloader.img and oem.img fail flashing.
What should i do?
Every time i boot the phone normally or into bootloader it says bad key,and i also dont see my baseband anymore.
Help me!
ninjakira said:
if you took the update you have to reflash the updated stock firmware after the update. if need be ill walk you through it ive already done it with one person over facebook messenger and after that they were successful. unfortunately they havent commented on saying so lol or thanked the post. sorry for the late reply also i just got off work lol also if links are dead i got dev access on afh now so ill be putting the new links on here ina bit . also tbh i have no clue why it says moto e4 when we put the twrp recovery on but it doesnt affect anything. it would be nice if we had an official twrp
Click to expand...
Click to collapse
I could imagine it was because we have no official twrp. what do you mean by updated stock image? I'm oj build opp27.91-87.
You sir need to also use this https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETAIL/. Go to step 19 and follow the reflashing stock firmware instructions. Use the most recent firmware. You can tell which one is new by dates
blowingoff said:
I could imagine it was because we have no official twrp. what do you mean by updated stock image? I'm oj build opp27.91-87.
Click to expand...
Click to collapse
ninjakira said:
You sir need to also use this https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETAIL/. Go to step 19 and follow the reflashing stock firmware instructions. Use the most recent firmware. You can tell which one is new by dates
Click to expand...
Click to collapse
mine is the brazilian one, xt1922-5. the downloads are for the 1922-2. can i use it?
---------- Post added at 05:49 PM ---------- Previous post was at 05:45 PM ----------
oh, I think you didn't understand me. I've already reverted the bootloop, my phone is working. but if I flash magisk, it goes to bootloop
I just got off the phone with Moto they confirm your device is also the aljeter so those firmwares should work for you.
blowingoff said:
mine is the brazilian one, xt1922-5. the downloads are for the 1922-2. can i use it?
---------- Post added at 05:49 PM ---------- Previous post was at 05:45 PM ----------
oh, I think you didn't understand me. I've already reverted the bootloop, my phone is working. but if I flash magisk, it goes to bootloop
Click to expand...
Click to collapse
ninjakira said:
I just got off the phone with Moto they confirm your device is also the aljeter so those firmwares should work for you.
Click to expand...
Click to collapse
great. so i'll flash the firmware and try to root from it
---------- Post added at 06:40 PM ---------- Previous post was at 06:25 PM ----------
well. i got an update. I just flash magisk with no modified boot image, no fstab.qcom and such. just flash twrp and then magisk.
phone rooted, safetynet passed. wow!!!!!!!!!!
blowingoff said:
great. so i'll flash the firmware and try to root from it
---------- Post added at 06:40 PM ---------- Previous post was at 06:25 PM ----------
well. i got an update. I just flash magisk with no modified boot image, no fstab.qcom and such. just flash twrp and then magisk.
phone rooted, safetynet passed. wow!!!!!!!!!!
Click to expand...
Click to collapse
Awesome you just helped confirm a couple things on my end to lol like the fstabs.qcom. I'm glad I could be of assistance to you and I'm glad the guide worked. I'll be removing the fstabs.qcom link since they are no longer needed now
I'm pretty sure there's already a Jeter root guide. What's the point in creating a new one?
Dadud said:
I'm pretty sure there's already a Jeter root guide. What's the point in creating a new one?
Click to expand...
Click to collapse
The other one was confusing people, and starting to cause more harm than anything. I've already helped a couple people in bootloop that tried to use the old guide and couldn't.
ninjakira said:
The other one was confusing people, and starting to cause more harm than anything. I've already helped a couple people in bootloop that tried to use the old guide and couldn't.
Click to expand...
Click to collapse
Seems like those people weren't following the the guide TO A T (very important) /skimming thinking it works the old way. I've seen those types of people all over these forums. You're adding more unnecessary clutter to these already cluttered and poorly moderated forums. I'm also pretty sure you don't have permission from kwiksilver to use his files
I've already talked to a mod about this there looking Into it and trust me man I literally have gone on rants to the people about not skimming before I helped fox there devices. I'm just trying to help everyone the best way I can think of all at once. People before the OTA and after no longer need a patched boot.img because the latest magisk does it. Furthermore we don't need the patched fstabs.qcom as I've recently learned. The device can be unencrypted without all that now thanks to magisk. I've already also told quiksi1ver I'm willing to have mine taking down if he cleans his up and updates it.also a couple devices like the xt1922-3 and 5 are aljeter not Jeter but it seems the xt1922-5 still apply to this guide.
Dadud said:
Seems like those people weren't following the the guide TO A T (very important) /skimming thinking it works the old way. I've seen those types of people all over these forums. You're adding more unnecessary clutter to these already cluttered and poorly moderated forums.
Click to expand...
Click to collapse
Also in my post I put the link for the stock firmware along with the proper adb commands to flash said stock firmware from bootloader which ALOT of people also need
lol this thread is much clearer than the earliest. and also: i've followed the steps from the original thread but i got no response from anyone there. hehhe
blowingoff said:
lol this thread is much clearer than the earliest. and also: i've followed the steps from the original thread but i got no response from anyone there. hehhe
Click to expand...
Click to collapse
Thank you for that lol I just wanna actually try to help out our fellow g6 play users lol
Thanks for creating this new thread, it really is cleaner than before.
Got it working on XT1922-5, brazilian model. Managed to get root and everything is working fine.
But just for curiosity, is there a way to revert it to stock with locked bootloader at all? Already flashed stock rom, my only problem is not being able to relock it.
Hope to see some new roms coming for our device soon!
AcTSkull said:
Thanks for creating this new thread, it really is cleaner than before.
Got it working on XT1922-5, brazilian model. Managed to get root and everything is working fine.
But just for curiosity, is there a way to revert it to stock with locked bootloader at all? Already flashed stock rom, my only problem is not being able to relock it.
Hope to see some new roms coming for our device soon!
Click to expand...
Click to collapse
Removed commands for bootloader relock because they don't work ignore this post
ninjakira said:
I personally have not used this yet to relock my bootloader so I cannot say 100% this will work. So please don't get mad at me if not. If it works for you please let me know and I'll add it to the post
Click to expand...
Click to collapse
Of course not! We are all here to learn, share and have fun with it.
Anyway, it didn't work. Still boots up with the Bad Key at the top and grayed out "unlocked oem" at developer options.
Let's wait and see if (when available around here, not OTA) flashing a new firmware will fix it, perhaps, as it updates the version to 27.91-147 (will confirm it later).
Hello everyone
I got my Mi 9T three weeks ago and I basically haven't used it because I couldn't transfer my backups so Im merely looking to root and install Titanium. The binding period for unlocking the bootloader should end tomorrow and I have a few question to avoid getting stuck on bootloop or break the phone
My device is Global 64gb MIUI 10.3.7.0 and update 10.3.12 is available
1. Which recovery do you recommend to flash on my device/version/MIUI release? Xiaomi-Miui.gr or 4PDA
2. Can I update MIUI and Flash recovery with no issues or are there any issues regarding MIUI version?
3. Do I flash using basic ADB method (phone on fastboot mode, "fastboot flash recovery ***" command") or is there anything I'm missing?
PS/ I did my research so Im aware of basic info
Thanks in advance
You should be fine doing that. I installed the Greek TWRP as well on my Mi 9T with MIUI Global version 10.3.12. Use the latest version available as it has more fixes and support for data encryption/decryption (latest version 3.3.1_12-08-19 as of today: http://www.mediafire.com/file/yuhi6pl5qtjr1nu/twrp_davinci_3.3.1_12-08-19_blue_Ss_new.img/file ).
After flashing TWRP you should format 'Data' first and flash Magisk to prevent the MIUI Global ROM from re-flashing the stock recovery. If you install the MIUI EU ROM or any other custom ROM this is not necessary though.
The bootloop issue is mostly related to the 'Anti-rollback' feature in the MIUI official ROMs. You can check the status by executing 'fastboot getvar anti'. If the result is empty or 1 you can flash whatever you want, but if it's more than 1 you should stick to flashing a MIUI ROM that is the same or higher version than it is now unless you can verify the 'anti' version in that particular ROM is equal or lower than the value in your phone.
You can follow the below video to root the device
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
And if any way you brick the device it can be recovered easily. Follow the below Video for unbricking
rocky29b4u said:
You can follow the below video to root the device
://youtu.be/dIWZGv-jCOA
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
And if any way you brick the device it can be recovered easily. Follow the below Video for unbricking
://youtu.be/JDrH8_yEO28
Click to expand...
Click to collapse
Video is not working. I'm interested since I both mine yesterday.
Sir_gpm said:
Video is not working. I'm interested since I both mine yesterday.
Click to expand...
Click to collapse
Try to open this link separately
https://youtu.be/JDrH8_yEO28
Please don't type english titles if your video will not be in english. This is straight up misleading and bad for everyone.
rocky29b4u said:
You can follow the below video to root the device
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
And if any way you brick the device it can be recovered easily. Follow the below Video for unbricking
Click to expand...
Click to collapse
sanchaz12 said:
You should be fine doing that. I installed the Greek TWRP as well on my Mi 9T with MIUI Global version 10.3.12.....
Click to expand...
Click to collapse
Thank you so much. Your answer clarified a lot of Xiaomi things I was wondering about.
I successfully flashed TWRP. I intended to install MIUI 10.3.12 after unlocking bootloader (im on 10.3.7) but I forgot and flashed TWRP directly. I remembered before flashing Magisk tho. Is the window for updating to 10.3.12 is closed by flashing TWRP?
Also, have you tested EU rom? Should I flash it or stick with stock?
Oh. I got value of 1 after executing "fastboot getvar anti" command
boot.img = ROM
rocky29b4u said:
You can follow the below video to root the device
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
In this video at 5:46 the guy is flashing boot.img as well not just recovery.
In other post I did not see that people were flashing boot.img, is this the firmware? And if its the ROM, is it necessary if I want just root the device or I can stay at stock ROM?
Click to expand...
Click to collapse
We need subs on the video or an english version of it. Don't just paste the video in every step, help us here..
SomniusX said:
We need subs on the video or an english version of it. Don't just paste the video in every step, help us here..
Click to expand...
Click to collapse
Hi,
See I will explain this in very simple steps
1. Download the TWRP image from description in the Video
2. Unlock your phone using MI Unlock Tool
3. Reboot your pone to FastBoot mode again
4. Wherever MiUnlock Folder is present on your computer go to that Folder
5. Right click anywhere on the folder keeping Shift pressed. You will see 'Command Prompt Here' option
6. Select that and Command Prompt will open
7. In command prompt type FASTBOOT DEVICES (This will show connected devices)
8. If device is detected type FASTBOOT FLASH RECOVERY <FULL PATH OF THE RECOVERY IMAGE FILE> (Example if TWRP is in C:\temp then command will be FASTBOOT FLASH RECOVERY C:\TEMP\TWRP.IMG)
9. This time type FASTBOOT BOOT <TWRP.IMG FILE> (This will boot phone to TWRP Forcefully)
10. If 9 doesn't work. Repeat 8 and Skip 9
11. After Step 8 type FASTBOOT REBOOT (Press Volume UP while phone is rebooting)
Phone will boot into TWRP this time.
Hope I was able to explain. If not let me know
rocky29b4u said:
Hi,
See I will explain this in very simple steps
1. Download the TWRP image from description in the Video
2. Unlock your phone using MI Unlock Tool
3. Reboot your pone to FastBoot mode again
4. Wherever MiUnlock Folder is present on your computer go to that Folder
5. Right click anywhere on the folder keeping Shift pressed. You will see 'Command Prompt Here' option
6. Select that and Command Prompt will open
7. In command prompt type FASTBOOT DEVICES (This will show connected devices)
8. If device is detected type FASTBOOT FLASH RECOVERY <FULL PATH OF THE RECOVERY IMAGE FILE> (Example if TWRP is in C:\temp then command will be FASTBOOT FLASH RECOVERY C:\TEMP\TWRP.IMG)
9. This time type FASTBOOT BOOT <TWRP.IMG FILE> (This will boot phone to TWRP Forcefully)
10. If 9 doesn't work. Repeat 8 and Skip 9
11. After Step 8 type FASTBOOT REBOOT (Press Volume UP while phone is rebooting)
Phone will boot into TWRP this time.
Hope I was able to explain. If not let me know
Click to expand...
Click to collapse
In the step 9 you type the name of the file or the whole path of the PC to the file?
rastip said:
In the step 9 you type the name of the file or the whole path of the PC to the file?
Click to expand...
Click to collapse
Its the file name with full path in PC for the Recovery File
rocky29b4u said:
Hi,
See I will explain this in very simple steps
1. Download the TWRP image from description in the Video
2. Unlock your phone using MI Unlock Tool
3. Reboot your pone to FastBoot mode again
4. Wherever MiUnlock Folder is present on your computer go to that Folder
5. Right click anywhere on the folder keeping Shift pressed. You will see 'Command Prompt Here' option
6. Select that and Command Prompt will open
7. In command prompt type FASTBOOT DEVICES (This will show connected devices)
8. If device is detected type FASTBOOT FLASH RECOVERY <FULL PATH OF THE RECOVERY IMAGE FILE> (Example if TWRP is in C:\temp then command will be FASTBOOT FLASH RECOVERY C:\TEMP\TWRP.IMG)
9. This time type FASTBOOT BOOT <TWRP.IMG FILE> (This will boot phone to TWRP Forcefully)
10. If 9 doesn't work. Repeat 8 and Skip 9
11. After Step 8 type FASTBOOT REBOOT (Press Volume UP while phone is rebooting)
Phone will boot into TWRP this time.
Hope I was able to explain. If not let me know
Click to expand...
Click to collapse
Thank you for the reply, and trust me, this text guide is much simpler and useful than trying to decode what you are saying in the video.
SomniusX said:
Thank you for the reply, and trust me, this text guide is much simpler and useful than trying to decode what you are saying in the video.
Click to expand...
Click to collapse
No Problem. Thanks...
Greetings everyone,im facing this error showing on tool,saying number not associated with your phone(already added mi account and was login from the day i got k20)..
please help.
Hello Everyone,
I really need help regarding this matter. I came from Evolution X 3.0 custom rom, now when I flash to stock rom, I flashed the Nougat version instead of Pie.
Now my dilemmas are the following:
1. Stuck in bootloop
2. Unable to unlock bootloader since I'm unable to boot it to the system
3. Tried all the other guide including this post except for number 2, since I don't know how to do that, and number 6, since I'm unable to open it for now: https://forum.xda-developers.com/showpost.php?p=78219944&postcount=224
Since this is the case, should I need to proceed with number 6 or is there any other methods I can use?
kevinzareno said:
Hello Everyone,
I really need help regarding this matter. I came from Evolution X 3.0 custom rom, now when I flash to stock rom, I flashed the Nougat version instead of Pie.
Now my dilemmas are the following:
1. Stuck in bootloop
2. Unable to unlock bootloader since I'm unable to boot it to the system
3. Tried all the other guide including this post except for number 2, since I don't know how to do that, and number 6, since I'm unable to open it for now: https://forum.xda-developers.com/showpost.php?p=78219944&postcount=224
Since this is the case, should I need to proceed with number 6 or is there any other methods I can use?
Click to expand...
Click to collapse
For step 2 you need to install Mi A1 device's drivers first, so you'll be allowed to use fastboot and adb commands from PC to your device.
The command shown on that step is just what you have to type when you open cmd at file's and adb-fastboot folder. Just paste the name of the file you've to load and install "adb sideload thisiswhatiwanttoinstall.zip".
You can find a better way to understand this procedure, by reading those rooting methods with TWRP... obviously not those with 1-click-root ones... look for those that make use of "adb-fastboot", since there, after TWRP custom Recovery is flashed, you're able to sideload Magisk to it to it in order to be also flashed on your device.
It's a pretty easy task once you have managed to install device's drivers well and have "adb-fastboot" tools, to open cmd from it's folder and start to run adb or fastboot commands to your device.
KaaMyA said:
For step 2 you need to install Mi A1 device's drivers first, so you'll be allowed to use fastboot and adb commands from PC to your device.
The command shown on that step is just what you have to type when you open cmd at file's and adb-fastboot folder. Just paste the name of the file you've to load and install "adb sideload thisiswhatiwanttoinstall.zip".
You can find a better way to understand this procedure, by reading those rooting methods with TWRP... obviously not those with 1-click-root ones... look for those that make use of "adb-fastboot", since there, after TWRP custom Recovery is flashed, you're able to sideload Magisk to it to it in order to be also flashed on your device.
It's a pretty easy task once you have managed to install device's drivers well and have "adb-fastboot" tools, to open cmd from it's folder and start to run adb or fastboot commands to your device.
Click to expand...
Click to collapse
I see. We'll will this work even if the bootloader is locked? I can't really unlock it
kevinzareno said:
I see. We'll will this work even if the bootloader is locked? I can't really unlock it
Click to expand...
Click to collapse
First of all be sure you could complete that tutorial you're following.
You're flashing device's firmware, that will put all on its place.
It's not like flashing a ROM, you're trying to unbrick device's software.
if you have enabled oem unlock in Development Settings then you can unlock bootloader by fastboot cmd "fastboot oem unlock" or if it not works try flashing stock pie rom with Miflash tool and if Miflash tool not works try QFIL
just a tip: when you flash stock rom with miflash tool and don't want to relock bootloader just remove the lines with "fastboot flash userdata" and "fastboot oem lock" in flash script "flash_all.bat" or "flash_all_except_storage.bat"
---------- Post added at 05:47 AM ---------- Previous post was at 05:43 AM ----------
just boot into EDL mode and try flashing with MiFlash tool.
i was revive my device with QFIL. QFIL automatically reboot device into EDL mode