Database Info

Help, MTTY task 2a

Hi! You are my last hope guys. I have some problems whith my Htc Cruise. I use MTTY and the task 2a command and now its dead. But I have a last hope. Please can anyone help me or tell me wich command should i use in the MTTY to try revive my phone. I have tell you, my htc cruise do not power on and cant put it in boot loader mode. His screen is complete blank.
Im from Argentina, sorry for my bad english.

Unfortunately you have to send the phone in service, the task 2A delete some drivers that can not be reinstalled

what are mtty and task 2a? never heard of?

The mtty is a program for format the ppc, but the task 2a is a command that in polaris delete some important driver. This is not reparable.

cruiserrr said:
what are mtty and task 2a? never heard of?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=425922

Spanish:
No te preocupes, yo utilicé el comando Task2a y la he recuperado. Tienes que seguir los pasos y los tutoriales que tienes abajo. Otra cosa cuando la tengas que poner en "dmode", que ya aprenderás lo que es, ponla siempre de la primera manera que aparece en el tutorial. Saludos!
English:
Ok I had the same problem. Now i can enter in 3 colors. Make this:
Step 1. Download and read this:
http://forum.xda-developers.com/showthread.php?t=393337
You need motorola Q drivers and a Windows XP 32bit to work.
Step 2. Read the post of jpg001 of this link:
http://forum.xda-developers.com/showpost.php?p=5369709&postcount=438
You need use the files of jpg001 to work
Step 3. You need a mtty called "mtty_0513_Test.exe" because other version freezes, at least for me.
If you need more information I will be here.
My Polaris it's working fine now!

I was meaning to post about this, over in the leo forum there is a RUU update which does a task 29. Formats the phone memory and then you can flash on top. This would solve all of the issues for flashing stock rom then reset, flash custom, reset.
So anyone know if this will work for the polaris?
Also sorry for the high jacking...

luzbel_es said:
Spanish:
No te preocupes, yo utilicé el comando Task2a y la he recuperado. Tienes que seguir los pasos y los tutoriales que tienes abajo. Otra cosa cuando la tengas que poner en "dmode", que ya aprenderás lo que es, ponla siempre de la primera manera que aparece en el tutorial. Saludos!
English:
Ok I had the same problem. Now i can enter in 3 colors. Make this:
Step 1. Download and read this:
http://forum.xda-developers.com/showthread.php?t=393337
You need motorola Q drivers and a Windows XP 32bit to work.
Step 2. Read the post of jpg001 of this link:
http://forum.xda-developers.com/showpost.php?p=5369709&postcount=438
You need use the files of jpg001 to work
Step 3. You need a mtty called "mtty_0513_Test.exe" because other version freezes, at least for me.
If you need more information I will be here.
My Polaris it's working fine now!
Click to expand...
Click to collapse
Don't you had problems running FrankenKaiser-V19004.exe? i have one stupid cygwin1.dll don't let me run FrankenKaiser...
You know something about that?

what os you using i've had problems with cygwin on win7 try download the latest cygwin http://www.cygwin.com/

I am using Win XP don't tried on Win 7... I have download cygwin, but i think it was from other page...i will remove a download from that page you point...
Thank's.
_____________Edit:
what package did you install? all? Can you remember?

Just copy the cygwin1.dll into the same folder as FrankenKaiser i think with xp any cygwin1.dll should be ok.

meknb said:
Just copy the cygwin1.dll into the same folder as FrankenKaiser i think with xp any cygwin1.dll should be ok.
Click to expand...
Click to collapse
Thank you men
Dont now why but before i go to sleep this didn't work, and now it's working... Thank you for your messages
For someone who needs, the cygwin1.dll is at:
C:/cygwin/bin
Only copy the file from there to folder FrankenKaiser-V19004, i remember now that earlier i did download cygwin1.dll file from internet and didnt work (that's the mistake)

[Alcatel OT-991] Unbrick. + CWM Recovery.

Since those files are important for those who looking for CWM recovery or to unbrick / revive their phones. i decided to start a new thread to keep
them all together into one section... so it will be easy for the rest of the world to find them.
I managed to gather pro_info + preloader from models: 991X-2IRGES3 (Espaniol) (N F83 ), 991D-2AALDE1 (German) (N G3G) , 991D-2AALGR1 (Greek) (N G3G), 991D-2AALIT1 (Italian) (G3G), 991X-2ATBMK1 (N F47) 991X-2ARGRO1 (Romanian) (N F3B), if you want to unbrick your OT-991 but its model is not listed there, then you can try all adove one by one, until you find the right one.. when you find the right one the screen lights up. that means you can go with OT-UPGRADE and let it flash again the firmware all over.
If you can't find your language:
Edit pro_info with hex editor and change the 2 letters of the language u want for example 991X-2IRGXX3 change the xx part to EN for english or RU for Russian.
LOOK at the sticker behind the battery it looks like this:
CE 1588 (!)
ONE TOUCH 991
TCT MOBILE LIMITED
Bluetooth QD ID xxxxxxxxxx
N xxx xxxx xx xxx
Made in China
991X-xxxxxx-xx
PRO_INFO's from directories with 991D stands for dual sim and 991X stands for signle sim.
^ check the N part on the sticker, or the 991-xxxx part and choose preloader+pro_info
Flash tool version to be used is V3.1216.05 <------ Important
PS. If still the phone is dead (Even after OT-Upgrade) you can try reflash ONLY preloader.img and not the rest of the files..
when you find the correct preloader the phone will turn on.. since OT-UPGRADE Already has flashed the rest of the firmware.
PS2. i uploaded recovery.img (CWM) and boot.img (root) if u want to restore a CWM recovery or root it after.
--------------------------------------------------------------------------------------------------------------
Updates:
[ 2/2/2013 ] 991D-2AALIT1 (G3G) added to 7zip.
[ 2/3/2013 ] 991X-2ARGRO1 (F3B) added to 7zip.
[ 2/21/2013] 991D-2AALIT1 [2] (G4G) Added
[ 2/21/2013] 991X-2ARGRO1 [2] (F3B) Added
[ 2/24/2013] 991D-2EALDE1 Added
[ 2/25/2013] 991X-2BYGES1 Added
Good News Member @mentolatux (Thanks to @Gradu2012 memeber) has managed to unbrick his phone with 991X-2ARGRO1 [2] as it is the same model.. finally we come into conclusion that there is no any serial/imei checks or something like that, you just need to find the right preloader for your phone.. this 7z already contains enough preloaders but may not be able to cover all the models.
The second attachment contains boot.img for rooting the phone, and also a CWM Recovery for Alcatel, that backups and restores also custpack partition. due to many request from our friend @catdoggy (custpack will be shown as /datadata, but its custpack) custpack name will be datadata
If you wipe data through Recovery you also loose custpack So.. you have those options.
1. Wipe using some other tool.
2. Take a clean backup, rename the dir to "Wipe" instead of wiping use restore, and then the wipe backup.
3. Open adb shell and type: wipe data
4. Still not happy? no s... is given use stock rom and drink milk
Click to expand...
Click to collapse
If you run into a problems with Recovery, Boot or anything by me, there is always a solution to use your stock rom/anything else and guess, don't care at all. Also you do everything you do at your very own risk, I am NOT responsible of any damages.
Unbrick / Debrick is ONLY if phone don't turn at all (eg. full format) NOT If android have problems Don't TRY to use images to unbrick phone if phone can turn on. then use ONE TOUCH UPGRADE or install a ROM (eg. gradu etc). You will damage your preloader if your phone power button works up to android logo or recovery.
the steps to unbrick phone goes like that
1. Load the scatter.
2. Full format everything.
3. load all the files that this small fixed scatter wants (DSP_BL to LOGO.IMG)
4. Download all the files
5. You can use OTU, then use the same scatter and try ONLY just 1 preloader each time, they flash correctly always. once you found the correct preloader phone turns on and boots up to android.
OR alternate, you don't use OTU, instead you keep flashing preloaders until the screen lights up.
To make this more clear to you,
step 1.
FULL FORMAT.
step 2.
PRELOADER -checked- (a random one doesn't mater)
DSP_BL -checked-
PRO_INFO -checked-
NVRAM-checked-
UBOOT -checked-
BOOTIMG -checked-
RECOVERY -checked-
LOGO -checked-
step 3 and now :
PRELOADER -checked- (a random one doesn't mater, can be flashed all over and over again until the screen lights)
DSP_BL -empty-
PRO_INFO -empty-
NVRAM-empty-
UBOOT -empty-
BOOTIMG -empty-
RECOVERY -empty-
LOGO -empty-
Click to expand...
Click to collapse
Use this zip to do your job Download unbrick zip with the preloader collection

PROINFO
@IvanX9 try this for Espaniol
*attachment removed*

frapedas said:
@IvanX9 try this for Espaniol
Click to expand...
Click to collapse
Thanks a lot. It will force Alcatel Upgrade to flash and download a Spanish Dual Sim Stock ROM ?? ( not a single rom ! )

IvanX9 said:
Thanks a lot. It will force Alcatel Upgrade to flash and download a Spanish Dual Sim Stock ROM ?? ( not a single rom ! )
Click to expand...
Click to collapse
This is the deal. try it and tell me if it works for you.

frapedas said:
This is the deal. try it and tell me if it works for you.
Click to expand...
Click to collapse
I tried, and it doesn´t work......:crying:
I got the same lenguages, but not the spanish ! What can I do ??

You got to be kidding, are you sure you flashed it right, and OTU completed?

If u are sure it got flashed and everything ok, then u are in the sad case to look for an 991D-xxxESx we have already an ES but is from a single sim phone... so.. you also must look if you have a backup from before you brick your phone.. or at Espaniol forum ask them to type in adb shell
cat /dev/mtd/mtd0 >> /sdcard/preloader.img
cat /dev/mtd/mtd2 >> /sdcard/pro_info.img
You only need pro_info.img i need both to included in the 7z here.
Any one with a spanish 991 dual sim??? please type those commants and upload pro_info/preloader here. thanks in advance

frapedas said:
If u are sure it got flashed and everything ok, then u are in the sad case to look for an 991D-xxxESx we have already an ES but is from a single sim phone... so.. you also must look if you have a backup from before you brick your phone.. or at Espaniol forum ask them to type in adb shell
cat /dev/mtd/mtd0 >> /sdcard/preloader.img
cat /dev/mtd/mtd2 >> /sdcard/pro_info.img
You only need pro_info.img i need both to included in the 7z here.
Any one with a spanish 991 dual sim??? please type those commants and upload pro_info/preloader here. thanks in advance
Click to expand...
Click to collapse
I'm asking in spanish forums in order to get that 2 files.... but I think that it will be difficult because not everybody knows how to manage with de ADB SHELL :crying:

Ivan.. please ask at the "how to root" thread so more people will be able to see your message. Ask for an italian pro_info rom there ok?

The region information is included in Preloader image not pro_info, methods are not valid if they pass by OTU returned to factory settings, not valid when loading images with FlashTool, I've tried everything, I have reached maximum SetupWizard get it installed and running half the root menu translated into English as recognizable by me (and most do not understand). In fact pro_info image is not included in the firmware is loaded with basic information that sends the preloader to OTU is a loop if the images are loaded with OTU, what we need to edit is the preloader not pro_info me not worth any of which there are published, not even mine, do not load the preloader FlashTool neither nor dsp_bl
What you need are the original files that include dsp_bl Preloader and Spanish and can be loaded without errors FlashTool.
Thank you.

tzadkiel2 said:
The region information is included in Preloader image not pro_info, methods are not valid if they pass by OTU returned to factory settings, not valid when loading images with FlashTool, I've tried everything, I have reached maximum SetupWizard get it installed and running half the root menu translated into English as recognizable by me (and most do not understand). In fact pro_info image is not included in the firmware is loaded with basic information that sends the preloader to OTU is a loop if the images are loaded with OTU, what we need to edit is the preloader not pro_info me not worth any of which there are published, not even mine, do not load the preloader FlashTool neither nor dsp_bl
What you need are the original files that include dsp_bl Preloader and Spanish and can be loaded without errors FlashTool.
Thank you.
Click to expand...
Click to collapse
@tzadkiel allow me to dissagree with you please.. OTU doesn't use at all preloader (doesn't even flash it back) and it uses pro_info to determine which firmware it will provide (thats why when you have corrupted pro_info it can't detect the version and gives you a 'you have the latest version' also another person in this forum already tryied changing the language part only and succeed. (i mean recieved from OTU a native firmware) preloader as far as i know its a basic driver of the hardware-set of the phone.
The person who changed his language like this, he used backedup preloader of his rom, edited only pro_info. If your statement is right then he is going to face another problem, preloaders are not going to work on all phones.. so it will be like 90% if he flash another preloader that will brick his phone... The second thing of your thery that doesn't match is that preloader is a completely binary file that contains only hex. while pro_info contains readable information and strings that match the model, the version, and the hardware of the phone. in Fact ..we can't edit preloader. this will cause phone to be bricked even a small bit if you change there.
@tzadkiel Lets leave the technical part, you can tell if you are looking also a Spanish rom or another language is that you looking for? for 991D or for 991X ask here.. and u can try both preloader,+pro_info when we got them.
I Wish you all, luck into returning it to your language. (and someone to give you the files u need) cheers

frapedas said:
@tzadkiel allow me to dissagree with you please.. OTU doesn't use at all preloader (doesn't even flash it back) and it uses pro_info to determine which firmware it will provide (thats why when you have corrupted pro_info it can't detect the version and gives you a 'you have the latest version' also another person in this forum already tryied changing the language part only and succeed. (i mean recieved from OTU a native firmware) preloader as far as i know its a basic driver of the hardware-set of the phone.
The person who changed his language like this, he used backedup preloader of his rom, edited only pro_info. If your statement is right then he is going to face another problem, preloaders are not going to work on all phones.. so it will be like 90% if he flash another preloader that will brick his phone... The second thing of your thery that doesn't match is that preloader is a completely binary file that contains only hex. while pro_info contains readable information and strings that match the model, the version, and the hardware of the phone. in Fact ..we can't edit preloader. this will cause phone to be bricked even a small bit if you change there.
@tzadkiel Lets leave the technical part, you can tell if you are looking also a Spanish rom or another language is that you looking for? for 991D or for 991X ask here.. and u can try both preloader,+pro_info when we got them.
I Wish you all, luck into returning it to your language. (and someone to give you the files u need) cheers
Click to expand...
Click to collapse
My english is very basic, google translation spanish to english in previous post.
I tryed whith diferents options images, the preloader included region (see in hex editor)
I can previous images brick download what download image returned factory settings, original firmware not included pro_info is generated for OTU download.
Mine is 991X even if tihink what its 991D, only image not changed been preloader and dsp_bl the other images been replaces whith differents options, not valid, is the loop return factory setting whith information preloader greek what download in the phone
Sorry for my bad english.

Its ok my friend, you installed greek because the first version of this zip had my own pro_info (im Greek) Now do that
In this thread, in the first post, there is a file Unbrick-991.7z, go to 1st and download that, inside that you will find for "Single Sim" 991X a directory 991X-2IRGES3 <-- flash from that directory ONLY pro_info.img (not preloader, will brick the phone again) then run OTU again to get single sim italian Rom.
Come back to tell us if everything is ok.

A ver si alguien me traduce al inglés
frapedas said:
Its ok my friend, you installed greek because the first version of this zip had my own pro_info (im Greek) Now do that
In this thread, in the first post, there is a file Unbrick-991.7z, go to 1st and download that, inside that you will find for "Single Sim" 991X a directory 991X-2IRGES3 <-- flash from that directory ONLY pro_info.img (not preloader, will brick the phone again) then run OTU again to get single sim italian Rom.
Come back to tell us if everything is ok.
Click to expand...
Click to collapse
No, no está utilizado tu método porque no me sirvió, encontré un firmware original para descargar, 991 ALEUO. Es de dualsim y el build.prop indica como idioma el griego.
Me tiré horas y horas con Flashtool hasta conseguir desbrickear el teléfono, el único preloader y dsp_bl que me aceptan los Flashtool son lo de este firmware, ni siquiera mis imágenes anteriores al brickeo, las tenía todas extraídas y las únicas imágenes que no me acepta son estas cada vez que intento cargarlas FAIL, descargo cualquier otra FAIL a excepción de las del 991 ALEUO.
Después se me corrompió la NAND Flash tuve que pasarlo directamente por el upgrade para repararla y volver a cargar las imágenes, he probado con más de 100 imágenes no vale el cargar el pro_info, si es que le tengo y lo carga pero no hace nada, y si lo paso por el upgrade vuelvo a comenzar con el teléfono a origen pero a origen griego.
Puedo devolverle el idioma con la ROM 3!min pero me daba tal cantidad de errores que prefiero tener el menú raíz en inglés y que se crea que es un dualsim aunque no lo sea, ya que el resto lo puedo tener en español.
Gracias.

This is the files for your phone. you need to flash this preloader + pro_info then use OTU. (Sticker behind battery: 991X-2BYGES1)
Este archivo es de ladrillo antes de la misma. i fijo para usarlo de nuevo (Model: 991X-2BYGES1 )

@IvanX9 Your Spanish friend he says he debricked his phone with a Greek preloader and worked but without Spanish language, I don't believe him. He just confused the pro_info file, because i checked his preloader with the Greek one and they totally different.. (different hardware though) so.. his phone should remain dead.. (phone can't turn on with a different preloader)
If you believe him..you can try his preloader from 991X-2BYGES1 and tell me if phone still works.. then use OTU (if phone doesnt get bricked...again) and if you get spanish like that come back tell me that. (don't flash his pro_info as it is single sim rom)
One note guys:
Recently i flashed by mistake romanian pro_info (preloader untouched) and got Romanian firmware... and no Greek. so... PRELOADER i dont believe does matter, its pro_info that do the trick with OTU. thats how i restored to Greek.. by flashing another pro_info.
However.. i fixed the preloader he send to me and i uploaded as a set with his pro_info (991X-2BYGES1) i hope this will work for him.
So @tzadkiel2 since your pro_info (before brick phone) is and was ok (no need for fixing) then why you STILL haven't got Spanish?

frapedas said:
This is the files for your phone. you need to flash this preloader + pro_info then use OTU. (Sticker behind battery: 991X-2BYGES1)
Este archivo es de ladrillo antes de la misma. i fijo para usarlo de nuevo (Model: 991X-2BYGES1 )
Click to expand...
Click to collapse
Otra vez con problemas de NAND Flash, hasta que no me acepte el formateo correcto de la misma no puedo hacer nada otra vez brickeado, y la última vez que me sucedió esto me tiré horas y horas para que lo aceptara, si no se formatea la NAND Flash no hay manera de hacer que el OTU actualice ya que detecta la última versión disponible.
Gracias, ya contaré en que acaba.
________________________________________
Again with NAND Flash problems, until I accept the correct formatting of it I can do nothing bricked again, and the last time this happened to me I jumped for hours for him to accept, if not formatted NAND Flash is no way to make the update OTU by detecting the latest version available.
Thanks, I just tell it.
(Google translation)

1. Use SP Flash Tool V3.1216.05
2. Select 991X-2BYGES1 Preloader. + dsp_bl (from unbrick.7z) + UBOOT.img
3. Full Format NAND.
4. Click Download On Flash Tools
5. Run OTU

1.Tienes que descargar cualquier custom rom (gradu custom rom o otro,cualquier quieres,pero uno que functiona,sin errores) y guardarlo en tu sd card
2.Si tienes un backup original hecho con CWM,guardalo en tu sd card
3.Usa Flash Tool V3.1216.05 y descarga: preloader,dsp_bl,pro_info,boot,recovery(uno cada uno y cada vez que acabas de descargar cada archivo,desconectar el usb,sacar la bateria,volver a ponerla,conectar el usb y descargar siguente archivo)
4.Despues de acabar la descarga de los archivos,entrar en CWM,wipe data/factory,instalar Custom rom(el que lo has descargado y lo has guardado en tu sd card)
5.Sin reiniciar el telefono,instalar el backup original que lo has guardado en tu sd card (hacer la recuperacion/recovery).
Listo.
*El 4. lo haces para guardar custpack,porque tu backup no contiene el archivo custpack.img
**Si no tienes algun backup,seguir los pasos 1,2 y 3 y usar OTU.

frapedas said:
1. Use SP Flash Tool V3.1216.05
2. Select 991X-2BYGES1 Preloader. + dsp_bl (from unbrick.7z) + UBOOT.img
3. Full Format NAND.
4. Click Download On Flash Tools
5. Run OTU
Click to expand...
Click to collapse
Thank you, the method not valid for me, the SP Flash Tool V3 not functionally in me laptop (errors COM, etc, etc, etc...)
I have unbricked whit ROM 3!min right now
Not formating correct NAND Flash 42% ERROR, differents SP Flash tool versions and scatter's an images I have installed 3!min ROM unbricked whitout OTU
Thank you very much
Sorry for the inconveniences and thank you very much for the images corrected are fully functional, but have problems whith NAND Flash format

[ROM] LG K4 K120E PreRooted stock rom 5.1.1 Lollipop with SuperSU!

The newer builds above 2016-01-01 cant be rooted with KingoRoot or KingRoot any more but if you want to downgrade and be rooted you can use this good luck
>>LG K4 K120E<< is rooted with SuperSU!
Android Version: 5.1.1
Patch Level: 2016-01-01
Kernel Version: 3.10.65
Buildnumber: LMY47V
Baseband Number: MOLY.LR9.W1530.MD.LWTG.TC01.SP.E1LTE.V1.P2
Software Version: V10I-EUR-XX
Download Link:
https://mega.nz/#F!rshTgL7a!MPQ_qnVjfHnMgSuwHbtE9g
You can flash it with Smart Phone flash Tool.
The scatter file for LG K4 K120E is below.
WARNING!!!!! FLASH AT YOUR OWN RISK!
Download Smart Phone Flash Tool Windows:
https://androidmtk.com/smart-phone-flash-tool

It works for me so it will work for you guys to!

First, thanks for this.
I own a K130E, which has the same hardware specs but sold outside EU, is it safe to try this?
I'm worried that the mobile op. won't recognize it anymore (it's my first time flashing a rom so I don't know if that makes sense or not).

thomasgf22 said:
First, thanks for this.
I own a K130E, which has the same hardware specs but sold outside EU, is it safe to try this?
I'm worried that the mobile op. won't recognize it anymore (it's my first time flashing a rom so I don't know if that makes sense or not).
Click to expand...
Click to collapse
i wish i could tell you but i cant tell you if its working or not because i dont have a K130E and cant test it out sorry man i have to leave to you

Please, give us instructions how to install the ROM
Thanks

So, I'm yet another one who's asking for help. Not because I can't flash a ROM, but because I have never used this program before and I really don't have the time to explore and explain to myself what this and that setting does. So, by replying to this thread, you would do yourself a favor (not getting any more notifications from people in this thread trying to figure out how it works) and me and much more guys like me (by telling us how it's done, since there are no other places on the Internet regarding the root of this phone).
EDIT: I figured it out, after 2 hours.
So, here we go:
Before you start this, make sure you have the LG drivers installed! If not, connect the phone to your PC and in the notification center, select the notifiaction that says "Device connected as ___". It will open up another window. Press on the three dots in the up right side of the screen and select "Install drivers", if the phone doesn't ask for this as soon as the window is opened. The driver installer should pop in your computer. I guess you know what to do with what popped up.
1st: Create a Mega account, if you don't already have one, you'll understand later why. Download and extract the ROM that the OP is giving link to. If you're using Firefox, get Chrome and download it from there as the file is hosted on Mega, which won't store almost anything if on Firefox. So, open the ROM link in Chrome and log into your Mega account. Now, open the link again, right click on that folder and select "Download as .zip" file. Chrome should ask for permission to let Mega store things on your PC, allow it.
2nd: After the download is ready, extract it somewhere you won't forget it's there.
3rd: Download Smart Phone Flash tool. Select last version compatible with Windows PC and, after it's downloaded, extract it. Right click on flash_tool.exe, go to compatibility tab and select "Run program as Administrator".
4th: Download Scatter file - right click on the attached file to this thread and select "Save as…" and click OK. The file should be saved in your Downloads folder.
5th: Open flash_tool.exe and go to download tab. Select "Scatter-Loading" and point to the file downloaded at step 4. VERY IMPORTANT!! DON'T MODIFY ANYTHING!! LET EVERYTHING AS THE PROGRAM SEES AND CONFIGURES IT!!
6th: You will see that only "system" is checked, but it isn't pointed to any file. Under the directory tab, you'll have to click on the empty space and point to where you extracted the ROM, at the file system.img.
7th: If your phone is on, turn it off and remove its battery.
8th: In flash_tool, press download. Now, connect your device to the computer and do a short "Volume Up" button press. The program will detect the phone and it will start the flashing process, which will take ~5 minutes.
9th: After the flash is done, you can close the program and disconnect your phone. Plug the battery back in and power the phone back up. After it boots up, you may get com.android.phone errors or something similar. You will have to get to Settings-Backup&Reset and reset the phone. After it's been reset, you will be able to enjoy your rooted LG K4. Good luck!
Thank you, OP for this thing. Also, some extra information, this is ranked as "Hard" to root phone by Root Checker and it is ~4600th hardest to root out of 5600 phone model numbers registered in Root Checker. Didn't expect that.

antoniu200 said:
So, I'm yet another one who's asking for help. Not because I can't flash a ROM, but because I have never used this program before and I really don't have the time to explore and explain to myself what this and that setting does. So, by replying to this thread, you would do yourself a favor (not getting any more notifications from people in this thread trying to figure out how it works) and me and much more guys like me (by telling us how it's done, since there are no other places on the Internet regarding the root of this phone).
EDIT: I figured it out, after 2 hours.
So, here we go:
Before you start this, make sure you have the LG drivers installed! If not, connect the phone to your PC and in the notification center, select the notifiaction that says "Device connected as ___". It will open up another window. Press on the three dots in the up right side of the screen and select "Install drivers", if the phone doesn't ask for this as soon as the window is opened. The driver installer should pop in your computer. I guess you know what to do with what popped up.
1st: Create a Mega account, if you don't already have one, you'll understand later why. Download and extract the ROM that the OP is giving link to. If you're using Firefox, get Chrome and download it from there as the file is hosted on Mega, which won't store almost anything if on Firefox. So, open the ROM link in Chrome and log into your Mega account. Now, open the link again, right click on that folder and select "Download as .zip" file. Chrome should ask for permission to let Mega store things on your PC, allow it.
2nd: After the download is ready, extract it somewhere you won't forget it's there.
3rd: Download Smart Phone Flash tool. Select last version compatible with Windows PC and, after it's downloaded, extract it. Right click on flash_tool.exe, go to compatibility tab and select "Run program as Administrator".
4th: Download Scatter file - right click on the attached file to this thread and select "Save as…" and click OK. The file should be saved in your Downloads folder.
5th: Open flash_tool.exe and go to download tab. Select "Scatter-Loading" and point to the file downloaded at step 4. VERY IMPORTANT!! DON'T MODIFY ANYTHING!! LET EVERYTHING AS THE PROGRAM SEES AND CONFIGURES IT!!
6th: You will see that only "system" is checked, but it isn't pointed to any file. Under the directory tab, you'll have to click on the empty space and point to where you extracted the ROM, at the file system.img.
7th: If your phone is on, turn it off and remove its battery.
8th: In flash_tool, press download. Now, connect your device to the computer and do a short "Volume Up" button press. The program will detect the phone and it will start the flashing process, which will take ~5 minutes.
9th: After the flash is done, you can close the program and disconnect your phone. Plug the battery back in and power the phone back up. After it boots up, you may get com.android.phone errors or something similar. You will have to get to Settings-Backup&Reset and reset the phone. After it's been reset, you will be able to enjoy your rooted LG K4. Good luck!
Thank you, OP for this thing. Also, some extra information, this is ranked as "Hard" to root phone by Root Checker and it is ~4600th hardest to root out of 5600 phone model numbers registered in Root Checker. Didn't expect that.
Click to expand...
Click to collapse
your welcome man!!!

I ****ed up... :S
Hey guys, damn i was so happy to see this sh!t because I bricked my phone hard when i was playing with some settings in the root directory and I was playing around with the write and read functions because I was trying to be able to write and format my sd card on my PC and anyways it ****ed up my settings so i had this "Bluetooth stopped working" or whatever pop up every 1 sec and no connection could load because of it so it was basically bricked i tried hard reset, didn't work so i was going to flash so i first tried the LG flash thingie, didn't detect the phone and when the LG mobile support tool was starting then it didn't detect the file and everything was just not going right, so in the end i found the software smart phone flash tool and researched a bit and found this thread here with the scatter file and img, so anyways i ****ed up when i was going to flash the phone with this software because i thought download meant literally downloading the software online so i checked in format all + download and left it all blank
then i held the volume button for a long time but did not see any recovery panel or anything but i saw the software load every once a while but still phone screen black so i thought that the reason the software was showing loading every once n a while was because it was maybe trying to detect the phone but not being able to so i took the cable out and then i got some error, so i thought damn maybe it was really extracting some files or something, so i think that i basically formatted the phone and download does mean extract?!?! or what?? does it download files or you have to input them manually ?
if that is the case then can you guys help me locate the missing files from a full format?
that is tee1, tee2, preloader, user data
---- EDIT ----
ok now I tried without using the above I requested and I get this error
hxxp://imgur.com/a/G0g69
--- EDIT 2 -----
Seems most information says that my preloader is corrupt and i am trying to have mtk droid root detect my phone which is identical in model and going to dump the data from there through a backup and cross my fingers hoping that the preloader is also in there and (which is going very badly since my authorization does never pop up after i enabled debugging and it never pops up in mtk and I tried reinstalling and installing and uninstalling about every single driver out there and about 10 restarts so trying to figure that out, if someone can dump the preloader it would be good
---- EDIT 3 ------
I was able to get my phone out of hard brick mode and here is a full download to what i used https://mega.nz/#!jwdSwT7T!Tn3rPS0LeZoP74ShK_7_jsqJr8ZJQ7Lg8l1OZ6Bri1Y <<< it is stock firmware 2016 with ALL software included to fix if you get in a hard brick situation or brick your device somehow then you can do a full restore from this I did a full restore with preloader and now I am only installing this pre-rooted version and it works fine, anyways all ended well and if you have any trouble with LG K 4 bricking then use this what I posted and sometimes it's good to only upload the preloader first with no battery in phone and then taking the cable from the phone and putting the battery in and then flashing all the rest with the battery and then taking cable out and starting the phone
-----THE FIX-----

Rooted lg K120AR
Hello friends of the forum I tried this rom on my LG K120AR (from Argentina) and it works correctly !!!
Thank you very much for the help!!
:laugh:

Hola , que dejaste seleccionado para flashear el 120
Hola , que dejaste seleccionado para flashear el 120ar soy de argentina tambien lo hice como decia ahi y no me pasa del logo de LG y el driver de mtp me salta error no me deja instalarlo de niguna forma para flshear lo de stock

Facufox87 said:
Hola , que dejaste seleccionado para flashear el 120ar soy de argentina tambien lo hice como decia ahi y no me pasa del logo de LG y el driver de mtp me salta error no me deja instalarlo de niguna forma para flshear lo de stock
Click to expand...
Click to collapse
justo estaba por flashearlo y vi tu comentario , es imposible rootear este aparato parece

alelovecraft said:
justo estaba por flashearlo y vi tu comentario , es imposible rootear este aparato parece
Click to expand...
Click to collapse
Entonces no es viable flashearlo?
Es una mierda todos los smarts que tuve antes los podía cocinar de cualquier forma, este nose deja porque los de LG los hicieron así, no voy a volver a comprar un LG.

RagnarLodbrokARG said:
Entonces no es viable flashearlo?
Es una mierda todos los smarts que tuve antes los podía cocinar de cualquier forma, este nose deja porque los de LG los hicieron así, no voy a volver a comprar un LG.
Click to expand...
Click to collapse
Si funcióna nada mas que el flaco que explica nada que ver todo para el culo te dice, tenes que ponel el scatter en la carpeta donde descomprimiste la rom rooteada y y en el flash tool elegí el scatter y no toques nada dale a download y listo capo , luego hace un reseteo de fábrica y ya esta rooteada esta mierda

Compa que mas hay que hacer no me reconoce el CEL, es con bateria, y en modo actulizar firmware, si le quito la bateria no lo hace nada el programa

gariasaya said:
Compa que mas hay que hacer no me reconoce el CEL, es con bateria, y en modo actulizar firmware, si le quito la bateria no lo hace nada el programa
Click to expand...
Click to collapse
Tenes que tener los driver univerales lg y presionar la tecla volumen + cuando conectas el cel a la pc en modo download

alelovecraft said:
Tenes que tener los driver univerales lg y presionar la tecla volumen + cuando conectas el cel a la pc en modo download
Click to expand...
Click to collapse
Ok vamos a probarlo así [emoji106]
Enviado desde mi LG-D850 mediante Tapatalk

gariasaya said:
Ok vamos a probarlo así [emoji106]
Enviado desde mi LG-D850 mediante Tapatalk
Click to expand...
Click to collapse
Y con la batería puesta

eniak1 said:
Hello friends of the forum I tried this rom on my LG K120AR (from Argentina) and it works correctly !!!
Thank you very much for the help!!
:laugh:
Click to expand...
Click to collapse
Como hiciste ? podrias ayudarme tambien soy de argentina mi problema es que el mio esta en banda negativa y quiero hacerlo root para sacarlo de banda

my phone in a hard brick dead...
my phone in a hard brick dead...
I tried the solutions here without success
Getting random errors 4032, 5054. 0x0FC0..
there is a solution?

I know this is random but. mine is lg k4 with marshmallow version but since I messed with it now it is lollipop. and some features are not working properly. like the cellular data for example. I tried searching for my official firmware years passed but no luck. can anyone help me. or any suggestion.

Stuck at CSC FastBoot Mode

Hello everyone,
i yesterday i bought secondhand Asus Zenphone 7 PRO stucked at CSC Fastboot MODE
When i turn on the phone it pops android icon for 1 sec then it goes automatically to CSC FastBoot Mode, then you can choose between START, Restart bootloader, Recovery mode, and Power OFF.
When you choose one of them they restart phone and again 1 sec android icon (sometimes charging icon also ) and then CSC fastboot mode .,
On PC the device can be recognise like ASUS BOATLOADER , after installing drivers it shows like Android ADB device.
Tried with platform-tools_r30.0.4-windows , on adb devices it now shows up , but when i type fasboot device it shows the serial number of my phone, and i can restart it with /fastboot reboot.
Thats all i tried stuck at this point.
Greetings

The only way to fix this is flash a full stock image.
This happened to me while trying to root. After unlocking, installing twrp, and following the rest of the directions kept booting back into twrp. After messing around with it a few more times it gave me an error that the system was corrupt and would not allow booting into anything other than crc fastboot. I was crapping my pants at the thought that I just bricked my new phone. But after a little more research I found the asus flashing tool and full image.
This is the specific link I got the flashing tool from. I see there are other versions if I do a google search. But I used this one and know it worked fine.
AFT_ASUS
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Then I grabbed this zip file, and the latest firmware from asus website. I saw the firmware from Asus was almost half the size so I was unsure what it may have been missing. Which is why I flashed the larger file from Mega first.
Also, the flashing tool gives an error about missing a frp account, you don't have to worry about that. The flashing tool likes to be started before the phone is connected as well. So if you start it and it doesn't see the phone, disconnect and reconnect and it should pop up.
Then just pick the first zip file in the tool and hit start. It took almost 10 minutes to fully write everything for me. plugged into a usb 3 port. When it is done restart it and it should be like a factory phone again. After setting it up, I copied the smaller zip i grabbed from asus to update it onto the sdcard. As soon as it was done copying the system automatically saw the zip as an update and asked if I wanted to install it.

Joeb2000 said:
The only way to fix this is flash a full stock image.
This happened to me while trying to root. After unlocking, installing twrp, and following the rest of the directions kept booting back into twrp. After messing around with it a few more times it gave me an error that the system was corrupt and would not allow booting into anything other than crc fastboot. I was crapping my pants at the thought that I just bricked my new phone. But after a little more research I found the asus flashing tool and full image.
This is the specific link I got the flashing tool from. I see there are other versions if I do a google search. But I used this one and know it worked fine.
AFT_ASUS
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Then I grabbed this zip file, and the latest firmware from asus website. I saw the firmware from Asus was almost half the size so I was unsure what it may have been missing. Which is why I flashed the larger file from Mega first.
Also, the flashing tool gives an error about missing a frp account, you don't have to worry about that. The flashing tool likes to be started before the phone is connected as well. So if you start it and it doesn't see the phone, disconnect and reconnect and it should pop up.
Then just pick the first zip file in the tool and hit start. It took almost 10 minutes to fully write everything for me. plugged into a usb 3 port. When it is done restart it and it should be like a factory phone again. After setting it up, I copied the smaller zip i grabbed from asus to update it onto the sdcard. As soon as it was done copying the system automatically saw the zip as an update and asked if I wanted to install it.
Click to expand...
Click to collapse
hello friend
you seemt to be knowledgable, do you know how i can root my zenfone 7, have you managed to root yours or get twrp installed?

articoceanic said:
hello friend
you seemt to be knowledgable, do you know how i can root my zenfone 7, have you managed to root yours or get twrp installed?
Click to expand...
Click to collapse
I was able to root mine, but the method with TWRP kept giving me a bootloop so I had to use a different way.
I used the "Method 2" listed here.
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Just make sure you pay attention to the pre-req's both the main and the method 2 specific ones.
Then it will basically go like this (assuming you already unlocked your bootloader and have adb and usb drivers already installed).
Grab latest firmware from Asus.
Copy the firmware zip to your phone storage and let it update. usually after you copy the zip and unplug your phone the system sees the update and asks if you want to apply it.
Download and install Python.
Grab payload dumper I attached to this post and extract the contents to your Python install directory.
Open the firmware zip and pull out the "payload.bin" file and put it in your python directory.
Open a command window in the python directory and run these 2 commands.
python -m pip install protobuf
python payload_dumper.py payload.bin
While that is extracting, download the latest Magisk apk, then copy it to your phone and install it.
In your python directory there should be a new folder called "output" look and see if the "boot.img" is done extracting. its the only thing you really need from it. Copy that boot.img file your phone storage (SD card preferrable if you have one).
Open Magisk manager on your phone, click "install" next to Magisk. It will ask for the method, choose to patch a file. Then select the boot.img file you copied.
After it is done look in your phones download folder for a "Magisk_Patched.img", copy that file to your adb folder.
Reboot your phone into fastboot mode.
Open command window in your adb folder. and run these commands
fastboot devices
fastboot flash boot magisk_patched.img
The first one should list your phone, if it does not, you don't have it in fastboot mode. I had that problem at first, I had it in recovery instead of fastboot.
After it is done flashing, reboot your phone with
fastboot reboot
Then you should be ready to go, although I had to go back in the manager and install Magisk a second time myself. Plus I had to use the manager to install the "Magisk hide" module and hide it from a few apps. Things like google pay don't like to work if it detects root. But hiding it from that app works great.

I am having the same problem. The AFT_Asus tool from above doesnt seem to work any more, saying too old on installation.
What I have found is Asus_Zenfonr_FlashTool_v2.0.1, which installs ok.
After starting the app and connecting the fone, I get disconnected and a warning that battery is at -1%, which is not true, its fully charged. There is nothing more I can do, Browse asks to connect the fone, hitting yes shows the same screen again.
Did somebody else run into this problem or has a working Asus flash tool?

Same issue please help

23598685 said:
I am having the same problem. The AFT_Asus tool from above doesnt seem to work any more, saying too old on installation.
What I have found is Asus_Zenfonr_FlashTool_v2.0.1, which installs ok.
After starting the app and connecting the fone, I get disconnected and a warning that battery is at -1%, which is not true, its fully charged. There is nothing more I can do, Browse asks to connect the fone, hitting yes shows the same screen again.
Did somebody else run into this problem or has a working Asus flash tool?
View attachment 5379741
Click to expand...
Click to collapse
IronSingh said:
Same issue please help
Click to expand...
Click to collapse
You did correct getting the new version, but you also need an updated driver.
I found one that works. The phone still says it is 0%, but it let me connect it this time and after selecting the image lit up the start button. I didn't want to completely wipe my phone at the time and try to redo everything so I did not hit start, but at least you can install the new drivers and give it a try yourself.
I got them from here.
Zenfone 8｜Phones｜ASUS USA
A new compact powerful choice: Flagship 5G processor · 120Hz AMOLED display · 4000mAh battery · Pro-grade dual rear and front camera · IP68 water resistant
www.asus.com
For some reason they don't even list the zenfone 7. it goes from 6 to 8.
But you can select the windows 8.1 64bit drivers (or x86 if you are running a 32bit system). Download and install those. It may have you reboot after, please do it.
Just in case you do not know how to install these kind of drivers. Simply extract the zip, then inside go into the "windows_xp_vista_7_8_8.1" folder, then into the "android" folder, and there will be a file called "android_winusb.inf" unless you have file extensions hidden, then it won't have the .inf on the end. But simply right click on it and it should say "install" as the second option on your right click menu. Just click on install and it should only take a couple seconds.

Thanks but I unpacked the latest zip from on official site and then just fastboot flashed everything. I have a custom script if someone wants.

Joeb2000 said:
The only way to fix this is flash a full stock image.
snip
Then I grabbed this zip file, and the latest firmware from asus website.
Click to expand...
Click to collapse
Man thank you very much for your help. I was able to recover the device using the zip file.
I was never able to get the flash tool working, the device did not connect. Even with the latest USB drivers.
How I got is working is download and unzipped the zip file from above, connected using fastboot , then ran dl_multiple_update_image.sh.
I am on Linux and had to buy a Windows 10 notebook just for this crappy flash tool, looks like this was not needed. If anybody is on Windows, there is a dl_multiple_update_image.bat file included in the Zip file.

23598685 said:
Man thank you very much for your help. I was able to recover the device using the zip file.
I was never able to get the flash tool working, the device did not connect. Even with the latest USB drivers.
How I got is working is download and unzipped the zip file from above, connected using fastboot , then ran dl_multiple_update_image.sh.
I am on Linux and had to buy a Windows 10 notebook just for this crappy flash tool, looks like this was not needed. If anybody is on Windows, there is a dl_multiple_update_image.bat file included in the Zip file.
Click to expand...
Click to collapse
Um virtual box?
and this is latest
you can also fastboot to recover

Try to flash with RAW
WW-ZS670KS-31.0210.0210.287-REL-2207-M3.35.19.26-SM8250_001522-ASUS_1.1.1-user-20220727.zip

digitalmaxMG said:
Olá pessoal,
ontem eu comprei o Asus Zenphone 7 PRO de segunda mão preso no CSC Fastboot MODE
Quando ligo ou telefone, aparece o ícone do Android por 1 segundo, depois vai automaticamente para o modo CSC FastBoot, então você pode escolher entre INICIAR, Reiniciar ou carregador de inicialização, Modo de recuperação e Desligar.
Quando você escolher um deles, eles reiniciam o telefone e novamente 1 segundo ícone do Android (às vezes também ícone de carregamento) e, em seguida, o modo CSC fastboot.,
No PC, o dispositivo pode ser reconhecido como ASUS BOATLOADER, depois de instalar os drivers, ele mostra como um Android ADB.
Tentei com platform-tools_r30.0.4-windows , em dispositivos adb agora aparece, mas quando digito fasboot device, ele mostra o número da série do meu telefone e posso reiniciá-lo com / fastboot reboot.
Isso é tudo que eu tentei neste momento.
Saudações
Click to expand...
Click to collapse
Joeb2000 said:
A única maneira de corrigir isso é fazer o flash de uma imagem completa.
Isso aconteceu comigo ao tentar fazer o root. Depois de desbloquear, instalar o twrp e seguir o restante das instruções, continuei inicializando novamente no twrp. Depois de brincar com ele mais algumas vezes, deu-me um erro de que o sistema estava corrompido e não permitiria a inicialização em nada além do crc fastboot. Eu estava cagando nas calças com o pensamento de que acabei de emparedar meu novo telefone. Mas depois de um pouco mais de pesquisa, encontrei a ferramenta de flash da asus e a imagem completa.
Este é o link específico de onde peguei a ferramenta piscando. Vejo que existem outras versões se eu fizer uma pesquisa no google. Mas eu usei este e sei que funcionou bem.
AFT_ASUS
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Então peguei este arquivo zip e o firmware mais recente do site da asus. Vi que o firmware da Asus tinha quase metade do tamanho, então não tinha certeza do que poderia estar faltando. É por isso que eu pisquei o arquivo maior do Mega primeiro.
Além disso, a ferramenta piscando dá um erro sobre a falta de uma conta frp, você não precisa se preocupar com isso. A ferramenta intermitente também gosta de ser iniciada antes que o telefone seja conectado. Portanto, se você iniciá-lo e ele não vir o telefone, desconecte e reconecte e ele deverá aparecer.
Em seguida, basta escolher o primeiro arquivo zip na ferramenta e clicar em iniciar. Demorou quase 10 minutos para escrever tudo para mim. conectado a uma porta usb 3. Quando terminar, reinicie-o e ele deverá estar como um telefone de fábrica novamente. Depois de configurá-lo, copiei o zip menor que peguei da asus para atualizá-lo no sdcard. Assim que terminou de copiar o sistema automaticamente viu o zip como uma atualização e perguntou se eu queria instalá-lo.
Click to expand...
Click to collapse
Eu tenho um rog 3 e tenho o mesmo problema. Não consigo encontrar o celular no pc para fazer os procedimentos. Instalei drivers e ainda não consigo encontrar o dispositivo, você pode me ajudar?

Widney2 said:
Eu tenho um rog 3 e tenho o mesmo problema. Não consigo encontrar o celular no pc para fazer os procedimentos. Instalei drivers e ainda não consigo encontrar o dispositivo, você pode me ajudar?
View attachment 5689357
View attachment 5689355
Click to expand...
Click to collapse
First of all english please. What Machine are you on Windows, Mac, Linux?
If your on windows please share screenshot of your Device Manager

IronSingh said:
First of all english please. What Machine are you on Windows, Mac, Linux?
If your on windows please share screenshot of your Device Manager
Click to expand...
Click to collapse
Worse, I wrote everything in English before sending.
Windows 10.

Widney2 said:
Worse, I wrote everything in English before sending.
Windows 10.
Click to expand...
Click to collapse
Update your windows and install the drivers
https://mega.nz/folder/OjpFmSQb#MLT96tXlhzmKbtGWtXrApQ drivers

IronSingh said:
Update your windows and install the drivers
https://mega.nz/folder/OjpFmSQb#MLT96tXlhzmKbtGWtXrApQ drivers
Click to expand...
Click to collapse
I did the procedure with this driver installed and it does not find the device rog phone 3 and I have already installed many drivers and finally this one that you sent me I could not find in adb and asus flash tool, thank you very much for your help.

Widney2 said:
I did the procedure with this driver installed and it does not find the device rog phone 3 and I have already installed many drivers and finally this one that you sent me I could not find in adb and asus flash tool, thank you very much for your help.
Click to expand...
Click to collapse
Your device manager stays the same?

IronSingh said:
Your device manager stays the same?
Click to expand...
Click to collapse
Yes

Widney2 said:
Yes
Click to expand...
Click to collapse
download this install it and then Update windows.

Question Oneplus 9 CN version first steps

Hi all,
I've been reading a lot before creating this post and still have doubts.
I have a Oneplus 9 CN version that came with Global ROM, I want to root it and be able to update it with OTA, as I've been doing with My OP6T.
Do I have to unlock bootloader first? How?
ROMs of EU/Global version are valid for CN Version?
Thanks

yeah super simple bro, same phone i Got

First, go to about phone, click on Build Number 7 Times.
Then back to System > Developer Options, click the OEM Unlocking Tab, also scroll down and click the USB Debugging tab.
then to your computer, make sure you have ADB and Fastboot program installed.
- SDK Platforms.
Then go to the folder or if you have ADB installed. Click the "path" bar and tyif pe CMD and hit enter
your command prompt will no open. Connect the phone to the computer.
Type
- adb devices
if it shows your device, were good and connected. It will show a prompt, "Allow Devices" click allow always.
now you need to Download "twrp.img" from the twrp website. also download the latest Magisk and put both files into the Platforms folder or wherever you download ADB and Fastboot.
once you have that done.
go back to your command window.
type
- adb reboot bootloader
now we are in fastboot mode
type
- fastboot boot twrp.img
it will boot into TWRP recovery.
go to Advanced tab, click Flash current TWRP
now go back to advanced and click ADB Sideload
now back to command window
type
- adb sideload Magisk2022.zip "or whatever you have it named.
it will flash Magisk, once that is done, you are Bootloader Unlocked and Now Rooted.
open the app on the phone and follow the prompts. click updates if it says update on both
always do "direct install" on the first one. Unless you do an update of some sort. Then you do "inactive slot"
any other questions brother, feel free to holler at me. Hope this helps. Hope you got the 12GB/256GB phone.
Many blessings

illusiveairforce said:
Primeiro, vá para sobre o telefone, clique em Build Number 7 Times.
Em seguida, volte para Sistema> Opções do desenvolvedor, clique na guia Desbloqueio OEM, role para baixo e clique na guia Depuração USB.
em seguida, para o seu computador, certifique-se de ter o programa ADB e Fastboot instalado.
- Plataformas SDK.
Em seguida, vá para a pasta ou se você tiver o ADB instalado. Clique na barra "path" e tyif pe CMD e pressione enter
seu prompt de comando não será aberto. Conecte o telefone ao computador.
Tipo
- dispositivos adb
se mostra seu aparelho, estava bom e conectado. Ele mostrará um prompt, "Permitir dispositivos" clique em permitir sempre.
agora você precisa baixar "twrp.img" do site twrp. também baixe o Magisk mais recente e coloque os dois arquivos na pasta Plataformas ou onde quer que você baixe o ADB e o Fastboot.
uma vez que você tenha feito isso.
volte para sua janela de comando.
tipo
- bootloader de reinicialização do adb
agora estamos no modo fastboot
tipo
- inicialização rápida twrp.img
ele inicializará na recuperação do TWRP.
vá para o guia avançado, clique em Flash atual TWRP
agora volte para avançar e clique em ADB Sideload
agora de volta à janela de comando
tipo
-b sideload Magisk2022.zip "ou o que você configurou anúncio.
ele irá piscar o Magisk, uma vez feito isso, você está com o Bootloader desbloqueado e agora enraizado.
abra o aplicativo no telefone e siga as instruções. clique em atualizações se disser atualização em ambos
sempre fachada "instalação direta" no primeiro. A menos que você faça uma atualização de algum tipo. Então você faz "slot inativo"
qualquer outra pergunta irmão, sinta-se à vontade para gritar comigo. Espero que isto ajude. Espero que você tenha o telefone de 12 GB/256 GB.
Muitas benções
Click to expand...
Click to collapse
You could make a video , teach this in video , it would help the Oneplus 9 community a lot , because there is no video or someone to show this

illusiveairforce said:
First, go to about phone, click on Build Number 7 Times.
Then back to System > Developer Options, click the OEM Unlocking Tab, also scroll down and click the USB Debugging tab.
then to your computer, make sure you have ADB and Fastboot program installed.
- SDK Platforms.
Then go to the folder or if you have ADB installed. Click the "path" bar and tyif pe CMD and hit enter
your command prompt will no open. Connect the phone to the computer.
Type
- adb devices
if it shows your device, were good and connected. It will show a prompt, "Allow Devices" click allow always.
now you need to Download "twrp.img" from the twrp website. also download the latest Magisk and put both files into the Platforms folder or wherever you download ADB and Fastboot.
once you have that done.
go back to your command window.
type
- adb reboot bootloader
now we are in fastboot mode
type
- fastboot boot twrp.img
it will boot into TWRP recovery.
go to Advanced tab, click Flash current TWRP
now go back to advanced and click ADB Sideload
now back to command window
type
- adb sideload Magisk2022.zip "or whatever you have it named.
it will flash Magisk, once that is done, you are Bootloader Unlocked and Now Rooted.
open the app on the phone and follow the prompts. click updates if it says update on both
always do "direct install" on the first one. Unless you do an update of some sort. Then you do "inactive slot"
any other questions brother, feel free to holler at me. Hope this helps. Hope you got the 12GB/256GB phone.
Many blessings
Click to expand...
Click to collapse
Thanks a lot! It comes with Global ROM, but I'm not sure this is a chinese version with ads...
I guess I prefer flashing EU/Global oficial versión.
When should I do it? After unlocking bootloader?
Thanks again

I have the same model and upgraded to android v12 do I do same steps or I have to downgrade to v11 first ?
Also, from security point of view what is the possipility of collecting my phone data after unlocking my boot loader ! is that true ?
Thanks in advance