[ROM] [Android 11] Stock System, Recovery and Boot for Alcatel 1 2021 5033F Android 11 - Alcatel 1X Guides, News, & Discussion

WARNING: I am not responsible for any bricked devices, dead SD cards, or a thermonuclear war!
Click to expand...
Click to collapse
Hello There!​
I have succesfully dumped the system, recovery and boot partition of the Alcatel 1 2021.
So if you need to reinstall your system or recovery for some reason here is how to do it.
Things you will need​
Install MTK Client following the instructions found here
Unlock your devices bootloader:
Open a command promt window in the folder where your MTK Client is​Power OFF your device​Remove the battery​Type the following command: python mtk da seccfg unlock then press enter​After that plug in the USB cable​After it finishes put back the battery, restart your device and your bootloader should be unlocked​
Now that your devices bootloader is unlocked when you turn ON your device you will need to press the power button within 5 seconds or your device will POWER OFF
Install the files​
Install System:
Open a command promt window in the folder where your MTK Client is​Power OFF your device​Remove the battery​Type the following command: python mtk w system system.img then press enter​After that plug in the USB cable​After it finishes put back the battery, restart your device and your system should be installed​
Install Recovery:
Open a command promt window in the folder where your MTK Client is​Power OFF your device​Remove the battery​Type the following command: python mtk w recovery recovery.img then press enter​After that plug in the USB cable​After it finishes put back the battery, restart your device and your recovery should be installed​
Install Boot (Kernel):
Open a command promt window in the folder where your MTK Client is​Power OFF your device​Remove the battery​Type the following command: python mtk w boot boot.img then press enter​After that plug in the USB cable​After it finishes put back the battery, restart your device and your boot (kernel) should be installed​
DOWNLOAD​
system.img
recovery.img
boot.img
If you have any questions, problems or you know how to build/port TWRP for this device feel free to comment or PM me

Hello , is the fm radio enabled in this rom?

DJ HAPPY said:
Hello , is the fm radio enabled in this rom?
Click to expand...
Click to collapse
I dont think it is

Hello. I spend much time to unlock bootloader. Only yours method was usefull.
Thanks for your time.
But after that i got bootloop
i've installed your files:
system.img
recovery.img
boot.img
any idea please?

oh00 said:
Hello. I spend much time to unlock bootloader. Only yours method was usefull.
Thanks for your time.
But after that i got bootloop
i've installed your files:
system.img
recovery.img
boot.img
any idea please?
Click to expand...
Click to collapse
Hi! Your problem might be that you dont press the power button when your device promts you to do so (after you unlocked the bootloader you will always need to press the power button when the device is turning on). If you do press it and your device still boot loops you should try to factory reset your phone. If none of these work for your, one of the phones partitions might be corrupt.

NDXCode said:
Hi! Your problem might be that you dont press the power button when your device promts you to do so (after you unlocked the bootloader you will always need to press the power button when the device is turning on). If you do press it and your device still boot loops you should try to factory reset your phone. If none of these work for your, one of the phones partitions might be corrupt.
Click to expand...
Click to collapse
I did everything with your manual.
Everything was OK. I pressed power button when was asked.
After 3 files uploading I was made a factory reset in stock recovery. But got some errors. I've rebooted to recovery again and there were no more errors.
But it's still bootloop.
Is your software for OT 5033F version?

oh00 said:
I did everything with your manual.
Everything was OK. I pressed power button when was asked.
After 3 files uploading I was made a factory reset in stock recovery. But got some errors. I've rebooted to recovery again and there were no more errors.
But it's still bootloop.
Is your software for OT 5033F version?
Click to expand...
Click to collapse
I think I found your problem, you have an Alcatel 1 2021 5033FR (says on the top of your recovery) while the software I posted is for the Alcatel 1 2021 5033F. The two phones are different.

looks like you are right. I thought there are no difference between
5033D
5033F
5033FR
but there are differences
Your recovery from 5033F is working. So im able to boot recovery only. Any ideas where can i find any working software for 5033FR? i tried to google but no luck. Now i got working UNLOCKED bootloader with working recovery. But i got bootloop. The goal was just unlock the botloader. I spend 2 days for it. Thats why i really apriciate your time.

NDXCode said:
I think I found your problem, you have an Alcatel 1 2021 5033FR (says on the top of your recovery) while the software I posted is for the Alcatel 1 2021 5033F. The two phones are different.
Click to expand...
Click to collapse
i downloaded from HardReset.info: 1 2019 OT-5033F
MT6739 TCL Alcatel 1 2019 OT-5033F RP1A.200720.011 macau vRB3V 20220411
but i cant flash it using SP flash tools
i got error
status_bdrom_cmd_send_da_fail
when i try to flash
python mtk w system system.img
python mtk w recovery recovery.img
python mtk w boot boot.img
from that firmware i downloaded from HardReset.info i got same bootloop
should i try to upload all ~30 files using
python mtk w ..... ?
like
python mtk w dtbo dtbo.img
python mtk w efuse efuse.img
python mtk w gz gz.img
python mtk w loader_ext loader_ext.img
python mtk w simlock simlock.img
python mtk w super super.img
python mtk w swversion swversion.img
....
im not sure

oh00 said:
i downloaded from HardReset.info: 1 2019 OT-5033F
MT6739 TCL Alcatel 1 2019 OT-5033F RP1A.200720.011 macau vRB3V 20220411
but i cant flash it using SP flash tools
i got error
status_bdrom_cmd_send_da_fail
when i try to flash
python mtk w system system.img
python mtk w recovery recovery.img
python mtk w boot boot.img
from that firmware i downloaded from HardReset.info i got same bootloop
should i try to upload all ~30 files using
python mtk w ..... ?
like
python mtk w dtbo dtbo.img
python mtk w efuse efuse.img
python mtk w gz gz.img
python mtk w loader_ext loader_ext.img
python mtk w simlock simlock.img
python mtk w super super.img
python mtk w swversion swversion.img
....
im not sure
Click to expand...
Click to collapse
The ROM you attached is for the Alcatel 1 2019 and not for the Alcatel 1 2021. Again they are also not the same phone.

NDXCode said:
The ROM you attached is for the Alcatel 1 2019 and not for the Alcatel 1 2021. Again they are also not the same phone.
Click to expand...
Click to collapse
looks like there is no place in the internet to download stock firmware.
if i will buy the same phone will i be able to read stock firmware using
Spoiler: spoiler
python mtk r proinfo,nvram,boot_para,recovery,swversion,para,oempersist,expdb,frp,vbmeta,vbmeta_system,vbmeta_vendor,nvcfg,nvdata,protect1,protect2,persist,metadata,oembin,seccfg,sec1,efuse,md1img,md1dsp,spmfw,mcupmfw,gz1,gz2,lk,lk2,loader_ext1,loader_ext2,boot,vendor_boot,logo,dtbo,tee1,tee2,simlock,super,odm,product,vendor,system,preload,oem,cache,userdata,otp,flashinfo
to backup all stock partitions
and then write it to bootlooped?

oh00 said:
looks like there is no place in the internet to download stock firmware.
if i will buy the same phone will i be able to read stock firmware using
Spoiler: spoiler
python mtk r proinfo,nvram,boot_para,recovery,swversion,para,oempersist,expdb,frp,vbmeta,vbmeta_system,vbmeta_vendor,nvcfg,nvdata,protect1,protect2,persist,metadata,oembin,seccfg,sec1,efuse,md1img,md1dsp,spmfw,mcupmfw,gz1,gz2,lk,lk2,loader_ext1,loader_ext2,boot,vendor_boot,logo,dtbo,tee1,tee2,simlock,super,odm,product,vendor,system,preload,oem,cache,userdata,otp,flashinfo
to backup all stock partitions
and then write it to bootlooped?
Click to expand...
Click to collapse
But if you flash all the partitions the phones IMEI number will corrupt.

NDXCode said:
But if you flash all the partitions the phones IMEI number will corrupt.
Click to expand...
Click to collapse
the main goal was to change imei. now i spent too much time for this stupid procedure

Related

[ROOT] EU LMV405EBW - Magisk

I couldn't find any guide for rooting the V40, so I thought I'd write down the steps I took to root my new EUR V40 - LMV405EBW. Maybe it will help others. Sorry if this is somewhat confusing, I didn't have time to make a polished version. It's basically made from my notes during the process with the commands copied from bash history.
-First, unlock the bootloader following LG's instructions here: https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
There's no TWRP for the V40 and the one made for G7 doesn't work. I don't have the time and knowledge to even attempt to compile TWRP for the V40, so I proceeded with just patching an original boot image with Magisk.
You can get the patched boot images that I used from here:
Oreo 10e: boot_a_magisk_patched_10e.img
Oreo 20f: boot_a_magisk_patched_10f.img
Pie 20a: boot_a_magisk_patched_20a.img
Pie 20b: boot_a_magisk_patched_20b.img
Pie 20f: boot_a_magisk_patched_20f.img
Pie 20g: boot_a_magisk_patched_20g.img
Q 30b: boot_a_magisk_patched_30b.img (this requires flashing to the active boot partition).
Q 30c: boot_a_magisk_patched_30c.img (this requires flashing to the active boot partition)
Q 30d: boot_a_magisk_patched_30d.image (this may or may not work with "fastboot boot" and could require flashing to the active boot partition. I haven't tested if live boot still works. I just did fastboot flash boot_x img_file).
You can try to boot it with with fastboot if you have a LNV405EBW and skip the KDZ extraction part.
Installing Magisk:
Flashing this image isn't necessary, just straight boot should be sufficient and safe.
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
Code:
adb reboot bootloader
fastboot boot boot_a_magisk_patched_10e.img
After the phone boots the OS with the external boot image, open Magisk Manager and tap on Install. Select the option to Direct install to the active slot. I played it safe and decided to NOT flash also on the inactive slot. I've left it alone so I can use it in case of need of recovery.
You'll probably notice that you don't have a connection to the carrier. Just ignore it, it will back once the phone is booted normally.
Reboot and you will have permanent root until you switch the A/B slots.
In case my patched boot image doesn't work, you can just make your own.
Tools needed:
Magisk Manager 7.0.0 installed on the phone
LG Bridge installed on a Windows machine.
a Linux machine or VM (I used the latest ubuntu desktop), python3 with the zstandard module installed and kdztools from steadfasterX's repo. Maybe kdztools would work on Windows too, I haven't tried it.
adb, fastboot
You need to procure an original ROM file for your phone model. It can be downloaded easily with LG Bridge. Just connect the phone to a Windows PC, start LG bridge, go to the Software update tab and click on Update error recovery. Wait for the download to start and disconnect the phone. Ignore LG Bridge complains about not being able to flash after the downloading stage is completed. Don't click anything in Bridge and before closing it go to C:\Users\<your_username>\AppData\Local\LG Electronics\LG Bridge\SWUpgrade and copy your KDZ somewhere else. Preferably send it to the Linux VM to the LG work folder, it'll be needed there.
On Linux open a terminal:
Code:
cd ~/Documents
mkdir LG
cd LG
git clone https://github.com/steadfasterX/kdztools.git
cd kdztools
nano undz.py -c
For kdztools to be able to extract the V40 images, I needed to edit undz.py and comment the lines 88-90. So, this block should all be commented or undz will fail to extract the boot partitions.
Code:
#if len(dz_item['pad']) != 0:
# print("[!] Error: pad is not empty", file=sys.stderr)
# sys.exit(1)
To extract, with the KDZ copied to ~/Documents/LG/
Code:
cd ~/Documents/LG/kdztools
./unkdz.py -f ../V405EBW10e_00_OPEN_EU_DS_OP_0109.kdz -x
cd kdzextracted/
List the partitions contents and look for the IDs of boot_a and/or boot_b. In my case they were 44 for boot_a and 63 for boot_b
Code:
../undz.py -f V40510e_00.dz -l
Extract boot_a or boot_b or both, they're identical:
Code:
../undz.py -f V40510e_00.dz -s 44
../undz.py -f V40510e_00.dz -s 63
You can find the extracted boot images in the dzextracted subfolder. Get boot_a.image or boot_b.image or both from there and send them to the phone in a location accessible by Magisk Manager. The Download folder should do fine.
Open Magisk Manager and tap Install, select Patch Boot Image file and patch the image file(s) you extracted. Get the patched_boot.img that Magisk Manager saves in the Download folder and send it to a PC where you have adb and fastboot.
Go to the beginning of the post to the Installing Magisk section.
Damned tempting, but I'll wait until after Pie drops.
Sent from my LM-V405 using Tapatalk
Glad to see this, hopefully it's a start for all of us.
If anything, at least a way to unlock the bootloader via legitimate channels! Gonna be generating that string, next chance I get, to be ready.
Sent from my LM-V405 using Tapatalk
Once runningnak3d gets a hold of this, we should be good with the v40. Cool beans.
Hey do the unlock codes online work for $ 12-15 on sprint? I used to flash phones back in the day and got a great deal on a bad IMEI sprint lg v40, but so far I can see there isn’t a way yet. On top off all that I m in Europe and don’t want to get the error message that I m out of the Region. I would have to go to USA just to unlock the phone.
@runningnak3d
Can't I install the firmware on a different device?
V version can not unlock BL, so envious
Getting a boot image like that works but I find it stupid to not upload it so that the others don't have to do it. Besides only one model can be bl unlocked so there won't be any model mismatch (except firmware versions but keeping up with them is not that hard)
LameMonster82 said:
Getting a boot image like that works but I find it stupid to not upload it so that the others don't have to do it. Besides only one model can be bl unlocked so there won't be any model mismatch (except firmware versions but keeping up with them is not that hard)
Click to expand...
Click to collapse
Or I could find you stupid for not noticing the patched image is in my first post.
DLS123 said:
I find you stupid for not noticing the patched images are in my first post.
Click to expand...
Click to collapse
I recommend labeling the boot images with their firmware since future firmwares won't be able to run the same boot image but other than that I'm really sorry.
LameMonster82 said:
I recommend labeling the boot images with their firmware since future firmwares won't be able to run the same boot image but other than that I'm really sorry.
Click to expand...
Click to collapse
I mentioned in the description 1 line below the link that it's for 10e. There was no other update in a long time. I don't think there can be any confusion for now. I can edit and label the file when there's will be another fw update.
It looks like unlocking the bootloader breaks Widevine L1 on the V40 and downgrades is to L3. No more HD or UHD Netflix.
I couldn't find any other solution than to re-lock the bootloader to restore L1.
This doesn't happen on the V30.
@DLS123
Thank you for all!
I ask you for more details; i'm stuck at flashing first image in adb; it returns an error; have LMV405EBW with 10f. unlocked bootloader of course
Thx again for your support!
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
DLS123 said:
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
Click to expand...
Click to collapse
Thx for answer; i not have too much experience in working with Magisk;
i just folowed your steps:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img
when i run fastboot comand for flash, is runing, but is returning "an error at line x"
i suppose is something wrong in this instructions.
daphix said:
Thx for answer; i not have too much experience in working with Magisk;
i just folowed your steps:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img
when i run fastboot comand for flash, is runing, but is returning "an error at line x"
Anyway; understand now what to do;
Steps are below:
- first install magisk manager
- download magisk zip from magisk site or from magisk manager himself on phone
- download patched_boot_a.img to phone from our good contributor
- use magisk manager and select inslall image of patched_boot_a.img from phone
- magisk manager will generate a magisk patched image
- transfer this magisk patched image (not patched_boot_a.img) to pc in ADB folder
- flash with Adb this magisk patched image from pc to phone.
Thx to our friend!
---------- Post added at 09:53 AM ---------- Previous post was at 09:21 AM ----------
DLS123 said:
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
Click to expand...
Click to collapse
Hi;
using Magisk mamanger and your file was generated a file: magisk_patched.img
pls support; trying to flash that image from PC with adb not work:
fastboot flash partition_a magisk_patched.img
Click to expand...
Click to collapse
@daphix
Whatver you're trying to do, is nowhere in the procedure I used. If you already booted with my boot image why are you making another boot image with Magisk and why are you trying to flash that? I never wrote anything of the sort.
if you booted with my patched image you already have temporary root and can use Magisk Manager to Direct install Magisk itself.
DLS123 said:
@daphix
Whatver you're trying to do, is nowhere in the procedure I used. If you already booted with my boot image why are you making another boot image with Magisk and why are you trying to flash that? I never wrote anything of the sort.
if you booted with my patched image you already have temporary root and can use Magisk Manager to Direct install Magisk itself.
Click to expand...
Click to collapse
Hi , thank you for reply;
I tried many combinations of your commands;
maybe due that am noob, but succesion below simply is not working:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img

[GUIDE] How to unlock bootloader in the Moto E6 Plus + Install TWRP, with Windows and Linux

Hello guys, in this guide I will tell you how to unlock the bootloader of the Moto E6 Plus.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
DISCLAIMER:
Code:
/*
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this system image before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device,
* I will laugh at you.
*
*/
What we will do first is a downgrade to version 76 of firmware since the new versions it's not allowed unlock bootloader, for this we will use SP Flash Tool v5.1916 (since the most current version does not give an error) and later we will flash some files for complete the unlock bootloader besides that we will install TWRP to install some GSI since the stock system it cannot be used.
This process is for 32/2 and 64/4 variant.
Links of download at the end of the post.
WARNING: THIS PROCESS ERASES ALL USER DATA AND VOIDS THE WARRANTY IN ADDITION THAT THE SYSTEM STOCK CANNOT BE USED.
Spoiler: PROCESS OF THE UNLOCK WITH WINDOWS
Prerequisites:
A computer with Windows (bruh)
ADB and Fastboot installed
Have installed the device drivers to be detected in fastboot mode.
Have downloaded the lk, vbmeta and recovery files.
Have downloader SP Flashtool and the ROM to downgrade.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
Once the necessary files have been downloaded the process is the following"
Unpack the SP Flash Tool and open "flash_tool.exe" file.
Once opened the app they will have to press up to the right the section "Options" and select "Option", when i open them they have to uncheck the second option.
Then close the window and in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
fastboot flashing unlock_critical
And press Volume + in the phone to unlock the bootlaoder and DO NOT reboot still
Spoiler: If you logged into the system directly
In case of having started in the system without installing the files, you will have to start in the recovery mode and do a factory format.
After that you can flash the files from fastboot.
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
fastboot flash lk lk.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
Now restart in recovery and go to Wipe > System > Advanced options > Resize.
Without this it would appear that there is 8GB of memory instead of 32/64.​​Now it only remains to flash the GSI.​
​
Spoiler: PROCESS OF THE UNLOCK WITH LINUX
Prerequisites:
A computer with Linux (bruh)
ADB and Fastboot installed
Have downloaded the lk, vbmeta and recovery files.
Have downloader SP Flashtool and the ROM to downgrade.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
Once the necessary files have been downloaded the process is the following
Unpack the SP Flash Tool, and mark as to executable "flash_tool" file and open as superuser, if you don't know the commands are the following:
Code:
sudo chmod +x flash_tool
sudo ./flash_tool
Now in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
sudo fastboot flashing unlock_critical
And press Volume + in the phone to unlock bootloader and DO NOT reboot still.
Spoiler: If you logged into the system directly
In case of having started in the system without installing the files, you will have to start in the recovery mode and do a factory format.
After that you can flash the files from fastboot.
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
sudo fastboot flash lk lk.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash recovery twrp.img
Now restart in recovery and go to Wipe > System > Advanced options > Resize.
Without this it would appear that there is 8GB of memory instead of 32/64.​​Now it only remains to flash the GSI.​
​If you don't know which GSI to try first, I recommend one from Phhusson, Ermitain or Andy.
NOTE: The system will be encrypted, and in this build of TWRP the encryption is not support so the files of internal storage will appear with numbers and letters random, if you want to remove the encryption flash the dm-verity.
NOTE 2: After unlocking the bootloader you can update the firmware to the latest version, but you will have to flash the lk and vbmeta files again (besides of recovery).
NOTE 3: The GSI architectures for each variant are: A64 AB for 32/2 and ARM64 AB for 64/4.
NOTE 4: If you are going to flash a GSI with GApps you will first have to flash a vanilla Phhusson GSI and start in it, after that you have to flash the GSI with GApps WITHOUT wipes and you can use it normally
Links of download:
ROM to downgrade : https://mirrors.lolinet.com/firmware/moto/pokerp/official/RETLA/ (the one that says in the name 32B its for 32/2 variant and the one that says in the name 64B its for 64/4 variant, bruh)
SP Flashtool: https://spflashtool.com/download/ (download the 5.1916 version)
ADB and Fastboot (Windows only): https://androiddatahost.com/uq6us
lk, vbmeta and TWRP files: https://drive.google.com/drive/folders/19wDFLDOoFTIDO-sv3vxWJ-CUEG1Q3sl-?usp=sharing
Credits:
@eluallen to do the first guide of how to unlock the bootloader and vbmeta file.
@Siddk for the recovery.
@LichtEstarossx for lk file and give some development to pokerp ;-;.
Fastoh said:
Hello guys, in this guide I will tell you how to unlock the bootloader of the Moto E6 Plus
DISCLAIMER:
Code:
/*
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this system image before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device,
* I will laugh at you.
*
*/
What we will do first is a downgrade to version 76 of firmware since the new versions it's not allowed unlock bootloader, for this we will use SP Flash Tool v5.1916 (since the most current version does not give an error) and later we will flash some files for complete the unlock bootloader besides that we will install TWRP to install some GSI since the stock system it cannot be used.
This process is for 32/2 and 64/4 variant.
WARNING: THIS PROCESS ERASES ALL USER DATA AND VOIDS THE WARRANTY IN ADDITION THAT THE SYSTEM STOCK CANNOT BE USED.
Spoiler: PROCESS OF THE UNLOCK IN WINDOWS
Once the necessary files have been downloaded the process is the following"
Unpack the SP Flash Tool and open "flash_tool.exe" file.
Once opened the app they will have to press up to the right the section "Options" and select "Option", when i open them they have to uncheck the second option.
Then close the window and in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
fastboot flashing unlock_critical
And press Volume + in the phone to unlock the bootlaoder and DO NOT reboot still
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
fastboot flash lk lk.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
Now reboot to recovery and flash some GSI
If you don't know which try first with the GSI of Phhusson or Lineage of Andy
Spoiler: PROCESS OF THE UNLOCK IN LINUX
Once the necessary files have been downloaded the process is the following
Unpack the SP Flash Tool, and mark as to executable "flash_tool" file and open as superuser, if you don't know the commands are the following:
Code:
sudo chmod +x flash_tool
sudo ./flash_tool
Now in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
sudo fastboot flashing unlock_critical
And press Volume + in the phone to unlock bootloader and DO NOT reboot still
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
sudo fastboot flash lk lk.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash recovery twrp.img
Now reboot to recovery and flash some GSI.
if you don't know which try first with the GSI of Phhusson or Lineage of Andy
NOTE: The system will be encrypted, if you want to remove the encryption flash the dm-verity.
NOTE 2: After unlocking the bootloader you can update the firmware to the latest version, but you will have to flash the lk and vbmeta files again (besides of recovery).
Links of download:
ROM to downgrade : https://mirrors.lolinet.com/firmware/moto/pokerp/official/RETLA/ (the one that says in the name 32B its for 32/2 variant and the one that says in the name 64B its for 64/4 variant, bruh)
SP Flashtool: https://spflashtool.com/download/ (download the 5.1924 version)
ADB for Windows: https://androiddatahost.com/uq6us
lk, vbmeta and TWRP files: https://drive.google.com/folderview?id=19wDFLDOoFTIDO-sv3vxWJ-CUEG1Q3sl-&usp=sharing
Click to expand...
Click to collapse
I've been looking for GSI-Treble support,
And my system drops this.
So in various posts people say "For this phone we have to install GSI aonly-Arm32"
I don't know what Is The Correct One And I Need Help
ShotRomsS6edge said:
I've been looking for GSI-Treble support,
And my system drops this.
So in various posts people say "For this phone we have to install GSI aonly-Arm32"
I don't know what Is The Correct One And I Need Help
Click to expand...
Click to collapse
Ahí te dice en la imagen, las GSIs compatibles son las que son A64 xd // There it tells you in the image, the compatible GSIs are those that are A64 xd
Dont get it, there is way too many fake websites with USB drivers for ADB and fastboot and none of them are working, ive tried your adb driver aswell but once I get into fastboot windows just says: Android device with a 28 error code which means that there is no driver installed, could you give me the link?
EDIT: adb only works when the device has booted.
simbanono said:
Dont get it, there is way too many fake websites with USB drivers for ADB and fastboot and none of them are working, ive tried your adb driver aswell but once I get into fastboot windows just says: Android device with a 28 error code which means that there is no driver installed, could you give me the link?
EDIT: adb only works when the device has booted.
Click to expand...
Click to collapse
What is missing are the drivers, try to download them from this link (is the link that came in the flash tool zip xd): https://androiddatahost.com/276a2
Fixed already ty
.
somebody know how to unlock bootloader moto e6 play xt2029-1? im trying to unlock bootloader and everthing i try it fails, please help me :c
cyanogenmodricky said:
somebody know how to unlock bootloader moto e6 play xt2029-1? im trying to unlock bootloader and everthing i try it fails, please help me :c
Click to expand...
Click to collapse
mmmmm, maybe downgrading to the oldest firmware version you can find
Fastoh said:
mmmmm, maybe downgrading to the oldest firmware version you can find
Click to expand...
Click to collapse
Well, that is what I have tried to do and spflashtools gives me many problems with this model :c
cyanogenmodricky said:
Well, that is what I have tried to do and spflashtools gives me many problems with this model :c
Click to expand...
Click to collapse
try the version of sp flashtool that uses LMSA
in the log it says which version
Fastoh said:
try the version of sp flashtool that uses LMSA
in the log it says which version
Click to expand...
Click to collapse
ohh ok, i will try it and i tell you if works :3
well i get make downgrade to the lowest version i found, now i can't unlock the bootloader with
fastboot flashing unlock_critical
it gives me "waiting device" :c
edit: i install adb, fastboot and moto drivers, now when i wirte fastboot flashing unlock appears "unknow command"
hey hi,i have a problem, so i did everything as you write it but when i did the flashtool thing it didn't recognize the phone, but it was making contact, i installed a lot of drivers until one of them make it work, so when i did the fastboot thing it wasn't recognize the phone again, what can i do? my phone is the 32/2 version
Alejandro2810 said:
hey hi,i have a problem, so i did everything as you write it but when i did the flashtool thing it didn't recognize the phone, but it was making contact, i installed a lot of drivers until one of them make it work, so when i did the fastboot thing it wasn't recognize the phone again, what can i do? my phone is the 32/2 version
Click to expand...
Click to collapse
what SO do you use? windows or linux? because in windows the fastboot mode did not work either ;-;
Fastoh said:
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Click to expand...
Click to collapse
But... How remove battery if this not removable?..
Mortyk said:
But... How remove battery if this not removable?..
Click to expand...
Click to collapse
what ._.? the moto e6 plus has a removable battery, I think you have the e6s instead of the e6 plus
Fastoh said:
what ._.? the moto e6 plus has a removable battery, I think you have the e6s instead of the e6 plus
Click to expand...
Click to collapse
Yeap i'm have e6s. I thought e6 plus have not removable battery also.
Do you know how to flash e6s?
Mortyk said:
Yeap i'm have e6s. I thought e6 plus have not removable battery also.
Do you know how to flash e6s?
Click to expand...
Click to collapse
mmmm, look first trying with lmsa to have as it tells you to do the firmware re-installation, then do the same steps you did in the LMSA but in the flashtool
If you want to downgrade you have to do it with the firmware of the e6s because if you do it with the e6 plus your phone will have birck.

[ROOT][TB-X605F/L] Magisk for those who cant use TWRP!

thanks to yahoo mike for solving the problem with the TWRP not working, you're a saint!
due to the fact that i want to prevent the painful process of trying to find out which twrp works for TB-X605L_S210224_200910_ROW, i will have to point it out to those who have the kind of firmware installed on their Lenovo Tab M10 and try to use TWRP version higher than 4.0 and it doesnt work - TWRP will never work, but there's still a way out for people who want root:
THE MAGISK BOOT.IMG METHOD IN THE FLESH FOR PEOPLE WHOSE TABLETS CANT GET ROOTED THE TWRP WAY!
Disclaimer: the boot.img file which was patched by magisk only works with TB-X605L_S210224_200910_ROW
For other versions you have to use LMSA to snatch the firmware and get the specific files.
This method also works on TB-X605X - same LMSA procedure, same result.
what will you need:
the first and important one - knowledge that i dont care if you couldnt use your 2 brain cells to follow the steps and proceed to brick the device by slapping a boot image on a recovery one and the fact that if you havent started the process yet your data (if theyre not backed up) will be WIPED
Click to expand...
Click to collapse
2 - a tablet, obviously (common sense)
3 - a computer
4 - Android SDK platform tools
5 - boot.img with magisk installed on it
6 (optional) - If you have no ramdisk, LMSA to at least get the recovery.img file
THE STEPS:
if you havent started the rooting process yet:
Spoiler
Code:
1 - Go to device details and tap the serial number 7 times, dev mode should activate
2 - Go to dev settings and activate OEM unlocking and USB debugging
3 - On your computer you should have downloaded SDK platform tools, extract in C:/
4 - Afterwards get into the platform-tools folder, click the path line and type CMD
5 - Type adb devices to see if it installed correctly, your device should appear
6 - Type adb reboot bootloader, wait until the device reboots, you should see FASTBOOT MODE in red text
7 (LAST CHANCE TO BACK UP YOUR FILES, IF YOU PROCEED YOUR UNBACKED DATA WILL BE PERMANENTLY WIPED) - Type this: fastboot oem unlock-go
8 - type fastboot reboot
YOU MAY PROCEED TO THE ROOTING PROCESS PART 2.
If you already unlocked OEM (ROOTING PROCESS PART 2):
1 - Go on your device and download Magisk Manager (Version is 23.0)
2 - install the APK file
3 - open magisk manager and check the ramdisk
We will look at 2 situations:
Yay! Ramdisk is checked as Yes! The process will be hassle free and you wont have to use LMSA to get the firmware!:
Spoiler
Code:
1 - On your computer put the modified boot.img file into the platform-tools folder (Dont worry, it doesnt bite)
2 - Move on to the CMD prompt and enter: adb reboot bootloader
3 - then type in: fastboot flash boot (THE FILE)
4 - after that reboot your device by typing in: fastboot reboot
5 - HURRAH! Now you have installed root using the boot method AND without TWRP! Its best to check it with root checker for best measure though.
OH HELL NAH! IN THIS RARE CIRCUMSTANCE YOUR RAMDISK IS LITERALLY NONEXISTANT AS CONFIRMED BY THE CHECKED NO! HERE'S THE HARD WAY:
Spoiler
Code:
1 - If not already, download LMSA (or just search on the internet lul)
2 - Install LMSA and make sure you have connected your device to the computer
3 - Go to the Rescue tab and download the Firmware
4 - the path should be C:\ProgramData\LMSA\Download\RomFiles\TB-X605L_S210224_200910_ROW, you should see recovery.img
5 - snatch it and then place it into the download folder of your device
6 - use magisk manager to install magisk on the recovery image (MAKE SURE TO CHECK RECOVERY MODE IN MAGISK MANAGER OPTIONS, IT MUST BE CHECKED!!!!)
7 - snatch it by typing the command into the command prompt: adb pull /sdcard/Download/magisk_patched_[random_strings].img
8 - boot your device into bootloader with this: adb reboot bootloader
9 - now flash it into recovery: fastboot flash recovery magisk_patched_[random strings].img
10 - reboot with fastboot reboot
11 - Congrats, you got root! Unfortunately for you and your nonexistant ramdisk you have to boot into recovery to run the system with magisk
12 - use the recovery key combo until you see the splash screen, then release the keys. You will boot into magisk as it hijacks the recovery
13 - and thats how you root without ramdisk! you have gone through the entire pain of having to now use the recovery combo and releasing keys in order to boot into the system with root, but hey, you got root!
if you brick your device and/or meet the device reaper under the name of QUALCOMM USB DIAGNOSTIC, you're pretty much dead and i do not take any responsibility. that was your choice to go with this method.
if you blame me for anything ranging from alarm clock app failing and cant wake you up because it couldnt access the vibration and/or sound to a god forsaken thermonuclear war because the error code of the qualcomm usb diagnostic somehow gave you nuclear access codes, here's the response: COPE AND SEETHE
Click to expand...
Click to collapse

Root method for Oxygen OS 11.0.5.BE83BA with Magisk

Notice this will VOID YOUR WARRANTY.
I am not to blame for BRICKED DEVICE.
Do this at YOUR OWN RISK.
Things you need :
1: OnePlus Nord N100 - Oxygen OS 11.0.5.BE83BA
2: Computer with Adb and Fastboot Installed - check google for adb and fastboot
3: Unlocked Bootloader - https://source.android.com/devices/bootloader/locking_unlocking
4: Adb Enabled in developer options aka USB debugging
5: The Boot.img - below
6: Magisk.apk - https://magiskmanager.com/
Guide :
Step 1: Patch Boot.img with Magisk
Open the magisk app and select Install>Select And Patch a File>Boot.img>Let's go
And then wait for :
Output file is written to
/storage/emulated/0/Download/magisk...img
- All done!
Press the arrow at the top and close Magisk for now
Step 2: Connect to the Computer with adb and fastboot installed
On Phone :
Allow the computer to browse files
On Computer :
Go in the file explorer to your phones downloads( This Computer\BE2013\Internal shared storage\Download ) folder and find the magisk...img
Copy the magisk...img to your desktop or any other folder if you can find it in Command Prompt(Windows)
Then Open Command Prompt(Windows)/Terminal(Linux)
Cd to your work folder(Desktop) or the "any other folder"
cd Desktop(Windows)
Step 3: Boot the device into bootloader
Do a check if the device is connected with:
adb devices
On phone :
Allow USB debugging
If nothing shows up on the phone or it says the phone is unauthorized reconnect the phone and try again.
On Computer :
Next we reboot the phone to bootloader with :
adb reboot bootloader
The phone will restart and you shall see a big START
Step 4: The Final Step Test & Install Root
Testing if everything works as expected eg Wifi, Bluetooth, Hotspot, Other stuff because these things broke for me once because I used the wrong version of boot.img.
Id still test them.
On Computer :
fastboot devices
If there is the same device as in Step 3 adb devices command all should be working expected.
Optional :
fastboot boot magisk...img Tip Use TAB to autocomplete in Command Prompt(Windows)
Next up test if all of the wireless stuff is working eg Wifi, Bluetooth, Hotspot, Other stuff
You can also open magisk to see if the device is Rooted.
Going back to bootloader is important for the next sub step("Flashing").
adb reboot bootloader
Flashing :
Did you boot the magisk...img?
If yes did everything work?
If not do not do this part!
fastboot flash boot magisk...img
fastboot reboot
Done!
Sorry for any typing mistakes if there is any.
If you have any questions ill be slow to respond if I even respond.
Sincerely Maxi
Where did you get this boot image?
I am getting the same behavior I get when trying to patch the global boot image - will not boot this TM model phone.
bouyakasha said:
Where did you get this boot image?
I am getting the same behavior I get when trying to patch the global boot image - will not boot this TM model phone.
Click to expand...
Click to collapse
I extracted the boot image from OTA update.
What do you mean with TM model phone? This is for the BE83BA.
hello someone does not have a rom 11.0.1be83ba I formatted the whole system unfortunately
Grilmama said:
hello someone does not have a rom 11.0.1be83ba I formatted the whole system unfortunately
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/t/...ota-oxygenos-repo-of-oxygenos-builds.4253501/
https://otafsg-cost-az.coloros.com/OnePlusN100_EEA/OnePlusN100Oxygen_14.E.25_GLO_0250_2203311235/patch/amazone2/GLO/OnePlusN100Oxygen/OnePlusN100Oxygen_14.E.25_GLO_0250_2203311235/OnePlusN100Oxygen_14.E.25_OTA_0250_all_2203311235_0a17ce328283d7.zip
Hi. Anyone can you extract Oxygen OS 11.0.5. BE83BA boot.img for me? Thank you! Can't access PC.
VPH20 said:
https://otafsg-cost-az.coloros.com/OnePlusN100_EEA/OnePlusN100Oxygen_14.E.25_GLO_0250_2203311235/patch/amazone2/GLO/OnePlusN100Oxygen/OnePlusN100Oxygen_14.E.25_GLO_0250_2203311235/OnePlusN100Oxygen_14.E.25_OTA_0250_all_2203311235_0a17ce328283d7.zip
Hi. Anyone can you extract Oxygen OS 11.0.5. BE83BA boot.img for me? Thank you! Can't access PC.
Click to expand...
Click to collapse
The post has been updated. It includes the updated boot.img.
Ma_x11 said:
The post has been updated. It includes the updated boot.img.
Click to expand...
Click to collapse
Thank you very much!

How To Guide [UPDATED] [REALME 8i/NARZO 50] How to get fastboot access and root your device easily.

Hello everyone! In this guide, I Sidharth will tell you how to flash recovery, root and access bootloader on the Realme 8i and Narzo 50, you probably have seen another guide by Pritish, it's not wrong but it became kind of outdated .
So lets begin,
Requirements:
PC (with windows or linux installed)
Platform tools installed
First unlock the bootloader by following this guide: http://telegra.ph/HOW-TO-UNLOCK-BOOTLOADER-REALME-8INARZO-50-05-08
Or this guide: https://forum.xda-developers.com/t/...-flash-twrp-and-root-rmx3151-rmx3286.4369399/ (dont worry about the boot imgs, just unlock the bootloader normally and boot the phone, don't go on the second step)
So after doing that, you should have platform tools and adb drivers installed, I am not going to tell you how to do that exactly but you should find tons of tutorials on the internet for both linux and windows. (I am going to be using Linux in this case but everything is the same for both windows and linux in this case)
Download this file: https://drive.google.com/file/d/13J2zlrUz84ZDSPERdosgNO6xdhwah4hl/view?usp=sharing
and paste it in your mtkclient folder (you should have that by now if you already unlocked the bootloader.)
{
"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"
}
Open the terminal and then type: python mtk w lk lk.bin
Now, power off your phone, hold both volume buttons and until it is done
Check if the phone boots into fastboot by holding volume down and power.
If it shows something like this then congrats, you have fastboot access now.
Flashing recovery is very easy now.
Download TWRP image from the TWRP website: https://twrp.me/realme/realme8i.html
Just keep it in the platform tools folder for now.
Boot into your phone, and download the magisk apk from here: https://github.com/topjohnwu/Magisk/releases
After downloading it, download ZArchiver from the Play Store and replace .apk with .zip and save it.
Now power off the phone and boot into fastboot/bootloader.
Open the terminal inside platform tools and:
fastboot flash recovery recovery.img
fastboot reboot recovery
You will be in your custom recovery now .
Now goto install, and select your magisk zip, and flash it normally.
After that is done, reboot to system and rename the magisk zip to apk again and install the apk.
Boom you have also rooted your device .
Thanks to Pritish for bootloader unlock guide and patched lk
also guys please let me know if you have any problems
here is how you can setup mtkclient on linux:
git clone https://github.com/bkerler/mtkclient
cd mtkclient
pip3 install -r requirements.txt
then you should have a mtkclient folder where u can execute the commands
bootloop on logo no way to fix hard to find how i can unbrick
the only thimg im able to do is on adb reflash the recovery and acces the Recovery TWRP but no way to acces the system
suauvia said:
bootloop on logo no way to fix hard to find how i can unbrick
the only thimg im able to do is on adb reflash the recovery and acces the Recovery TWRP but no way to acces the system
Click to expand...
Click to collapse
Just like bootloader unlock method, in MTK Tools, give this command:
#
python mtk e metadata,userdata,md_udc
#
(Without #)
Then connect your phone in BROM mode, then restart. it will be fine
suauvia said:
bootloop on logo no way to fix hard to find how i can unbrick
the only thimg im able to do is on adb reflash the recovery and acces the Recovery TWRP but no way to acces the system
Click to expand...
Click to collapse
be specific, did the lk file cause this or are you tryintg to unbrick through fastboot
if the lk caused this then tell me if you are on realme ui 3.0 or you are a narzo 50 user.
Sidharth09 said:
be specific, did the lk file cause this or are you tryintg to unbrick through fastboot
if the lk caused this then tell me if you are on realme ui 3.0 or you are a narzo 50 user.
Click to expand...
Click to collapse
thanks for your help but after doing so
python mtk e metadata,userdata,md_udc
nothing ha changed stil on realme logo and orange state and 5 seconds message and reloop reboot again
i was on UI 2,0 and updated firmware RMX3151 11.A_46
no idea if Lk make this
i have reflashed the stock recovery and format data also with TWRP recovery format data and cache but always on any move its a reloop reboot on Realme logo
-------
if i relock the bootloader ist possible to recover this phone and then how i can do this
im 67 old and not very used to this kind of operations
heroksiddiqi said:
Just like bootloader unlock method, in MTK Tools, give this command:
#
python mtk e metadata,userdata,md_udc
#
(Without #)
Then connect your phone in BROM mode, then restart. it will be fine
Click to expand...
Click to collapse
python mtk e metadata,userdata,md_udc
doneand nothing has changed
Is there a way to do this on a Mac? I have Realme 8i RMX3151 but do not have access to a Windows computer. Thank you.
I tried the Deep Testing App and it gives the following error "Failed to submit application. This phone model does not support deep testing."
suauvia said:
thanks for your help but after doing so
python mtk e metadata,userdata,md_udc
nothing ha changed stil on realme logo and orange state and 5 seconds message and reloop reboot again
i was on UI 2,0 and updated firmware RMX3151 11.A_46
no idea if Lk make this
i have reflashed the stock recovery and format data also with TWRP recovery format data and cache but always on any move its a reloop reboot on Realme logo
-------
if i relock the bootloader ist possible to recover this phone and then how i can do this
im 67 old and not very used to this kind of operations
Click to expand...
Click to collapse
u can always flash your stock LK again if it somehow made a problem so here
paste it in mtkclient and then
python mtk w lk lk.img
check if it fixes it!
jack1192 said:
Is there a way to do this on a Mac? I have Realme 8i RMX3151 but do not have access to a Windows computer. Thank you.
I tried the Deep Testing App and it gives the following error "Failed to submit application. This phone model does not support deep testing."
Click to expand...
Click to collapse
with mac it is not possible since mtkclient does not work on a mac
Sidharth09 said:
u can always flash your stock LK again if it somehow made a problem so here
paste it in mtkclient and then
python mtk w lk lk.img
check if it fixes it!
Click to expand...
Click to collapse
not working even worst even on fastboot it blocks about nserie decrypt or something like not remember well now i remake the process and get back to locked reboot on logo --- i would ask if i am on TWRP recovery and i want to flash a 7z firmware on .ofp files or a decrypted zip file do you think it will work ??
anyway trying to copy the 6 giigas firmware zip to an SD card the pc say that is too big to copy so maybe thru fastboot i can copt to the phone but i dont know about the command if you know about please let me know about the procedure if is positive way
or ist it any other way to recover the phone ??
finally i would like to install a Lineage customrom
suauvia said:
not working even worst even on fastboot it blocks about nserie decrypt or something like not remember well now i remake the process and get back to locked reboot on logo --- i would ask if i am on TWRP recovery and i want to flash a 7z firmware on .ofp files or a decrypted zip file do you think it will work ??
anyway trying to copy the 6 giigas firmware zip to an SD card the pc say that is too big to copy so maybe thru fastboot i can copt to the phone but i dont know about the command if you know about please let me know about the procedure if is positive way
or ist it any other way to recover the phone ??
finally i would like to install a Lineage customrom
Click to expand...
Click to collapse
finally i follow instructions on this link
[GUIDE][UNBRICK] Realme 8i/Narzo 50 Unbrick Free without Auth [RMX3151][RMX3286]
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX3151 (Realme 8i) and RMX3286...
forum.xda-developers.com
[GUIDE][UNBRICK] Realme 8i/Narzo 50 Unbrick Free without Auth [RMX3151][RMX3286]​all well now
thanks your guide to unlock the bootloader works a charm no success with other ones
Sidharth09 said:
Hello everyone! In this guide, I Sidharth will tell you how to flash recovery, root and access bootloader on the Realme 8i and Narzo 50, you probably have seen another guide by Pritish, it's not wrong but it became kind of outdated .
So lets begin,
Requirements:
PC (with windows or linux installed)
Platform tools installed
First unlock the bootloader by following this guide: http://telegra.ph/HOW-TO-UNLOCK-BOOTLOADER-REALME-8INARZO-50-05-08
Or this guide: https://forum.xda-developers.com/t/...-flash-twrp-and-root-rmx3151-rmx3286.4369399/ (dont worry about the boot imgs, just unlock the bootloader normally and boot the phone, don't go on the second step)
So after doing that, you should have platform tools and adb drivers installed, I am not going to tell you how to do that exactly but you should find tons of tutorials on the internet for both linux and windows. (I am going to be using Linux in this case but everything is the same for both windows and linux in this case)
Download this file: https://drive.google.com/file/d/13J2zlrUz84ZDSPERdosgNO6xdhwah4hl/view?usp=sharing
and paste it in your mtkclient folder (you should have that by now if you already unlocked the bootloader.)View attachment 5682939
Open the terminal and then type: python mtk w lk lk.bin
View attachment 5682941
Now, power off your phone, hold both volume buttons and until it is done
View attachment 5682943
Check if the phone boots into fastboot by holding volume down and power.
If it shows something like this then congrats, you have fastboot access now.View attachment 5682945
Flashing recovery is very easy now.
Download TWRP image from the TWRP website: https://twrp.me/realme/realme8i.html
Just keep it in the platform tools folder for now.
Boot into your phone, and download the magisk apk from here: https://github.com/topjohnwu/Magisk/releases
After downloading it, download ZArchiver from the Play Store and replace .apk with .zip and save it.
Now power off the phone and boot into fastboot/bootloader.
Open the terminal inside platform tools and:
fastboot flash recovery recovery.img
fastboot reboot recovery
You will be in your custom recovery now .
Now goto install, and select your magisk zip, and flash it normally.
After that is done, reboot to system and rename the magisk zip to apk again and install the apk.
Boom you have also rooted your device .
Thanks to Pritish for bootloader unlock guide and patched lk
Click to expand...
Click to collapse
now I cannot turn on my phone after try to access recovery :/
hoangnguyen320 said:
now I cannot turn on my phone after try to access recovery :/
Click to expand...
Click to collapse
i holded power button for 5 minutes...
hoangnguyen320 said:
i holded power button for 5 minutes..
Click to expand...
Click to collapse
volume up and power?
Sidharth09 said:
Hello everyone! In this guide, I Sidharth will tell you how to flash recovery, root and access bootloader on the Realme 8i and Narzo 50, you probably have seen another guide by Pritish, it's not wrong but it became kind of outdated .
So lets begin,
Requirements:
PC (with windows or linux installed)
Platform tools installed
First unlock the bootloader by following this guide: http://telegra.ph/HOW-TO-UNLOCK-BOOTLOADER-REALME-8INARZO-50-05-08
Or this guide: https://forum.xda-developers.com/t/...-flash-twrp-and-root-rmx3151-rmx3286.4369399/ (dont worry about the boot imgs, just unlock the bootloader normally and boot the phone, don't go on the second step)
So after doing that, you should have platform tools and adb drivers installed, I am not going to tell you how to do that exactly but you should find tons of tutorials on the internet for both linux and windows. (I am going to be using Linux in this case but everything is the same for both windows and linux in this case)
Download this file: https://drive.google.com/file/d/13J2zlrUz84ZDSPERdosgNO6xdhwah4hl/view?usp=sharing
and paste it in your mtkclient folder (you should have that by now if you already unlocked the bootloader.)View attachment 5682939
Open the terminal and then type: python mtk w lk lk.bin
View attachment 5682941
Now, power off your phone, hold both volume buttons and until it is done
View attachment 5682943
Check if the phone boots into fastboot by holding volume down and power.
If it shows something like this then congrats, you have fastboot access now.View attachment 5682945
Flashing recovery is very easy now.
Download TWRP image from the TWRP website: https://twrp.me/realme/realme8i.html
Just keep it in the platform tools folder for now.
Boot into your phone, and download the magisk apk from here: https://github.com/topjohnwu/Magisk/releases
After downloading it, download ZArchiver from the Play Store and replace .apk with .zip and save it.
Now power off the phone and boot into fastboot/bootloader.
Open the terminal inside platform tools and:
fastboot flash recovery recovery.img
fastboot reboot recovery
You will be in your custom recovery now .
Now goto install, and select your magisk zip, and flash it normally.
After that is done, reboot to system and rename the magisk zip to apk again and install the apk.
Boom you have also rooted your device .
Thanks to Pritish for bootloader unlock guide and patched lk
Click to expand...
Click to collapse
you can already do this using fastbootd
How to install usbdk in linux? I am using archlinux.
Sidharth09 said:
volume up and power?
Click to expand...
Click to collapse
just power , i tried all vl and pwer
and the battery was 90%
kawsarahmed369 said:
How to install usbdk in linux? I am using archlinux.
Click to expand...
Click to collapse
u dont need those for linux

Categories

Resources