Database Users

[UTILITY][RUU IMITATE]Easy Installer - Install your rom's like an RUU[HTC only]

Easy Installer​
{
"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"
}
What is Easy Installer?
Easy installer is a windows RUU imitate that helps you as user to install your Rom's with only 2 clicks. Fully automated!
For devs Easy installer helps to provide Rom's alternate to the recovery zip archive.
Click to expand...
Click to collapse
How does Easy installer work?
Thats easy. The developer create a system img file of his rom and configure Easy installer easily with one config file. The package can provide like a normal rom.
The user run a little exe-file and the RUU installs the rom fully automated! If something runs false, the RUU gives the user an error and a explanation what he can to do now.
Click to expand...
Click to collapse
What i need for Easy installer
For now, Easy Installer works only with image files, so you need your Rom as a image file. You can create a image file of your rom easily with mkyaffs.arm (find in attachements).
The config file is easy to understand. An example here (found in package too):
Code:
;The config file is neccessary for the RUU. Here you define all file namens.
[functions]
;imgfile specify, if you want to flash a image or a zip file (0=zip-file, 1=img-file). For now, only img files working, sry :(
imgfile=1
;waitbl set the time the RUU wait for the bootloader (fastboot). Some devices take a while to reboot to bootloader. Set the time here, in generally the time 10 is enough
waitbl=10
;the img-name specify the name of the image file without the file extension!
img-name=system
;zip-name is for one of the next versions, when it is possible to flash zip files. If you want, you can delete this
zip-name=HC_MIUI3.2
;boot-name specify the name of the boot.img without extension.
boot-name=boot
;set the name of the clockworkmod recovery file for your device here.
cwm-name=cwm
;rec-name is the original recovery of HTC that must be inserted for img-files. Put the name here without extension
rec-name=recovery
[labels]
;specify the shown rom-name in the RUU
rom-name=.sense
;the device name is the full name of the device the rom is for
device-name=Wildfire S
;some devices has more versions (marvel, marvelc, marvelct e.g.). Specify for what device your rom is.
device-code=marvel
The picture in the RUU is namend "PHONE.bmp" in package, you can replace with your own.
Click to expand...
Click to collapse
How to create the system.img?
Well, thats is easy
1. Install your Rom you want to use in Easy Installer at your phone via the Recovery (don't start the Rom!!!)
2. Go to recovery, connect your phone via USB-Cable to computer
3. Download the mkfs.arm.zip (see attachements)
4. Create a new directory in your SD-Card (example: "build")
5. Copy the extracted file "mkfs" of the downloaded archive into the folder "build"
6. Insert the SD-Card into the phone
7. In recovery go to: "mounts&storage->mound /sdcard" or run following adb-command: adb mound /sdcard
8. run the following commands in adb one after one:
adb shell
cd /sdcard/build
./mkfs /system /sdcard/build/system.img
9. Wait for the "Build OK."-message
10. Exit the adb shell via exit command and turn off the phone
11. Take the SD-Card of the phone and insert it into your PC
12. in the SD-Card's folder /build you will find a "system.img". Use this file for the easy installer
Click to expand...
Click to collapse
Changelog
v0.0.1
- first version, basic install function
Click to expand...
Click to collapse
Download
See the attachements (WSWizard.zip)
Click to expand...
Click to collapse

Will this work for all devices?
Any chances of bricking? Because many of users of Micromax A70 bricked their phone by a chinese flashing tool.
Burned from my laser torch using pencil cells

Sorry, i see now, that i posted this in false section. In genarally it works only for HTC devices which are unlocked or S-OFF, not for others!

How can I use the mkfs.arm?

it works only on ARM-based devices, like the HTC phones.
You must copy the file onto your sd-card e.g.:
adb push mkfs.arm /sdcard/build
After this you install your Rom on the device or copy the /system-files to the sd-card. Now you run following command:
adb shell
cd /sdcard/build
./mkfs.arm /system /sdcard/system.img
ODER
./mkfs.arm /sdcard/build/system /sdcard/system.img
Then the file will build a system.img and copy it onto the sdcard for next use

Would like to know if this would work to ONelll123
Wipe everything
Flash Rom
Make Nandroid
Use Nandroid as ROM's Images
It seems much easier to me than having to go to shell and all Not meant to be an insult, just a recommendation/question

Hmm, it ia qn idea, but idk in what filesystem the backups are saved. If it is yaffs2 it can be that this works.
But you must do shell commands too. Its for secruity reasons and that this method used works.
Sent from my HTC Wildfire S A510e using XDA

ONeill123 said:
it works only on ARM-based devices, like the HTC phones.
You must copy the file onto your sd-card e.g.:
adb push mkfs.arm /sdcard/build
After this you install your Rom on the device or copy the /system-files to the sd-card. Now you run following command:
adb shell
cd /sdcard/build
./mkfs.arm /system /sdcard/system.img
ODER
./mkfs.arm /sdcard/build/system /sdcard/system.img
Then the file will build a system.img and copy it onto the sdcard for next use
Click to expand...
Click to collapse
Thanks I will be try this when htc one x gets adb working recovery

[Q] i have problem for hd mini

i have problem i follow method rom photonic CM 7.2 nand boot but ihave screen stuck on
nand id:0x5500bcec maker=0xec device=0xbc
press VOLUME UP for RECOVERY
press VOLUME DOWN for FASTBOOT
ERROR: cannot read boot image header
ERROR: could not do normal boot. Reverting to fastboot mode.
ENTERING FASTBOOT MODE
udc_start()
then i follow this
1 Preparation
1a. Extract the LK_16.Jul.2012.rar or ("CWM LK Boot Recovery (16-July-2012).zip" for the iPlasm’s Photonic ROM) to anywhere on your computer. Note this file is updated from time to time too just like the roms.
1b. Open that folder and unzip (extract) the subfolder "LK-Photonic-SD.rar" ("LK Boot SDCard.zip" for iPlasm’s Photonic ROM). Copy each of those three files (without folder) directly to the Root of SDCard ie. Lk.bin, startup.txt and HARET_Photon7227.exe.
1c. Also copy gapps-ics-20120317-signed.zip and the CM9 rom file(s).zip to SDCard (plus all updates if any are specified for the ROM) directly to the Root of SDCard too. Do not unzip (extract) these .zip files. If you don’t copy these zip files now, you can still do later after the NAND has been installed except you have to mount the USB drive with the cable via CWM Recovery LK Boot.
1d. Make sure your GPS is working in WM6.5 (to prevent the GPS issue).
1e. Make sure you have your official Stock ROM for your device (country specific) in case you need to restore to WM6.5. Refer to Schlund's instructions headed under How to go back to WinMobile NAND-BOOT
2 Install Munjeni's CWM Recovery LK Boot (16 July 2012)
2a. Disconnect the cable then in the Phone, Open File Explorer and navigate to SDCard and touch at HaRET. File Explorer at this step means the HD Mini file explorer for Windows Mobile 6.5 (the original WM6.5 operating system already on your phone). HARET.exe must be run from the phone. If you don't follow instruction 1b and 1c properly (to put the necessary files on the SDcard), then this step won't work.
2b. The screen will reboot and show the following (or something similar) in dark blue text. Don't panic as it is a normal part of the procedure!:
nand id:0x5500bcec maker=0xec device=0xbc
press VOLUME UP for RECOVERY
press VOLUME DOWN for FASTBOOT
ERROR: cannot read boot image header
ERROR: could not do normal boot. Reverting to fastboot mode.
ENTERING FASTBOOT MODE
udc_start()
2c. Since you are now in fastboot mode, you need to install the Android Debug Bridge (ADB) driver files. To do this, just reconnect the USB cable between the phone and the PC. You may be asked on the PC for the drivers needed to connect the phone. If so, they are in the Google Windows USB driver folder (in the LK_16.Jul.2012.rar (Munjeni)/ "CWM LK Boot Recovery (16-July-2012).zip" (iPlasm).
2d. Wait very patiently for a few minutes whilst the drivers are installed (it might seem it is not doing anything in this time but you need to wait). You can check if they are installed by opening the Windows device manager and looking for a fastboot device listed under the USB hardware. If not, then do a manual install in Windows.
2e. Once the Windows notification pops up to say the device drivers have been installed (assuming the PC needs to install the drivers), then click on the PC file “Update.bat” (this file is in the LK_16.July.2012.rar/CWM LK Boot Recovery (16-July-2012).zip). In the menu that comes up, install options (ie. First do (1) then select (2)). What this does is it automatically erases boot recovery, userdata, system, cache, misc, and recovery.
my mobile screen stuck this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and my pc cannot connect to mobile
i need your help thank you sir
sorry my english no good

Everything you did is perfect!
now, in the last (2e.), What windows you're using and 32bit or 64bit?
after that, It seems you haven't entered (FastBoot) or it haven't been probably entered Fastboot in the picture, It should be written under line 5 or 6.
When written similar (entering fastbootmode) then you can install by clinking Update.bat, and do the instructions...
And remember... every time when you want to install new cwm recovery you should be in Fastboot mode.
Have a nice try...

What windows you're using and 32bit or 64bit?
my windows 7 32 bit but no noting all popup
now i follow click update.bat and choose 1 that right
how long for waiting device
thank you for your coment

This image shows that your phone hasn't been connected to PC or the ADB drivers aren't installed correctly.
And this installation take about 3 minutes. But this < Waiting for device > means your phone either not connected or adb hasn't been ready...
I was used Windows XP 32Bit, your windows732bit should work also

hello my friend thank you your comment i still problem
i have new question i pull my sdcard from mobile
and put in card reader my file is
is it correct? i follow step
3.Copy 3.Copy cm-7-20120618-UNOFFICIAL-photonic-r10.zip, the GAPPS file and the content of lk-photonic-sd.rar archive to the root of your sdcard and run HaRET from your device, the GAPPS file and the content of lk-photonic-sd.rar archive to the root of your sdcard and run HaRET from your device
on 3.Copy cm-7-20120618-UNOFFICIAL-photonic-r10.zip must extract yes or no
thank you very must:good:

Yes, all is perfect!, only you should not extract GAPPS.
How it's going on?

if i want go back to first step or windows phone
how can i do? pls
thank you sir

see at the bottom of page: http://forum.xda-developers.com/showpost.php?p=21617447&postcount=2

[GUIDE] How to root Elephone P7000

Preparation:
1. Make sure that your computer installed a driver
(Download link here )
2. Flash tool (SP flash tool recommended, download link here )
Please be careful and make sure that you have enough knowledge or we suggest that don't root your phone casualy.
1. Download the file from below link. you're going to save to somewhere you can remember it, for this tutorial, I'm going to use my desktop.
Dnowload link here
2. Unzip the file that you have downloaded just now.
3. Cope zipe file named "superSU_PRO_V2.49.zip" to your SD card and then turn off the phone.
4. Open flash tool, Click "scatter-loading" and choose the file named "p7000-recovery" which you have just saved in your computer.
{
"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"
}
5.Click download and then connect your phone with computer.
6. When you see a picture as below that means you have installed the third party recovery successfully.
7. Move out the battery and then put it back, press "power" + "VOL +" to enter recovery mode. ("VOL -" to choose, "power" to confirm)
http://bbs.elephone.hk/data/attachment/forum/201506/11/164351v74mw4840lullmwr.png
8. Choose "install zip" by pressing "VOL -" ,
9.Go to "choosezip from /sdcard"
10. Choose "superSU_PRO_V2.49.zip" , press "power" key to confirm.
11. Choose "yes-install superSU_PRO_V2.49.zip", press "power" key to confirm.
12. Congratulations!!! You have finished the whole process, now enjoy.

You can also root without flashing recovery.
1) Download and install SuperSU from Play Store, don't run it yet.
2) Enable USB Debugging and install ADB drivers.
3) Download this ZIP http://www37.zippyshare.com/v/SaH4NxFw/file.html , unzip to a folder and open command prompt in it.
4) Issue the following commands:
Code:
adb kill-server
adb root
adb connect localhost:5037
adb shell setenforce 0
adb shell mkdir -p /data/local/tmp/supersu/arm64
adb push su /data/local/tmp/supersu/arm64/
adb push supolicy /data/local/tmp/supersu/arm64/
adb push libsupol.so /data/local/tmp/supersu/arm64/
adb push update-binary-adb-arm64-v8a-21 /data/local/tmp/supersu/
adb shell chmod 0755 /data/local/tmp/supersu/update-binary-adb-arm64-v8a-21
adb shell /data/local/tmp/supersu/update-binary-adb-arm64-v8a-21
5) Don't reboot, run SuperSU, choose normal install, done.

Thanks

Thanks for all your work !

I followed all the directions and disabled the driver signature verification on my Windows 8.1 computer. I have a problem that when I plug in the phone to the computer (with the phone off) the computer recognizes it for a few seconds and then it does not anymore. I get the boopoopoop sound to incidate it is connected and the boopbum noise five seconds later indicating that it is off. Can anyone help?

GCbard said:
I followed all the directions and disabled the driver signature verification on my Windows 8.1 computer. I have a problem that when I plug in the phone to the computer (with the phone off) the computer recognizes it for a few seconds and then it does not anymore. I get the boopoopoop sound to incidate it is connected and the boopbum noise five seconds later indicating that it is off. Can anyone help?
Click to expand...
Click to collapse
If you can access adb (turn on debug mode in developer settings), then try my method above. No need to use preloader driver.

eLeKtriK EyE said:
If you can access adb (turn on debug mode in developer settings), then try my method above. No need to use preloader driver.
Click to expand...
Click to collapse
Thank you. I tried but the phone is not recognized as ADB. I have usb debugging checked and it still does not work. I even have all the drivers installed. Any suggestions?

Try with another computer, it must be windows 8 fault.

GCbard said:
Thank you. I tried but the phone is not recognized as ADB. I have usb debugging checked and it still does not work. I even have all the drivers installed. Any suggestions?
Click to expand...
Click to collapse
Download latest mtk droid tool's, i upload this some time's ago, this is Link.
https://mega.co.nz/#!2V9SRCRZ!xYn52zbVEfGze4zCyaUkfwStCUe0tt408IBpR-Tq-Fo
And here i add android commander. Try. For me working, but MTK DT no fully work

GCbard said:
I followed all the directions and disabled the driver signature verification on my Windows 8.1 computer. I have a problem that when I plug in the phone to the computer (with the phone off) the computer recognizes it for a few seconds and then it does not anymore. I get the boopoopoop sound to incidate it is connected and the boopbum noise five seconds later indicating that it is off. Can anyone help?
Click to expand...
Click to collapse
i had the same issues when i first tried flashing the device, some moderator in the eleforum stated that's normal for the phone to act like that, because it will just detect to flash for 1.5 sec and then jump into charging mode
do this steps and should work fine
1 - DO not connect the phone to the computer
2 - open the flash tool
3 - look for the scatter.txt file that you want to flash "either rom or recovery"
4 - click download on the top
5 - once the processes above have been done, connect the device and it will start the flashing process.
you are done.

TopoX84 said:
i had the same issues when i first tried flashing the device, some moderator in the eleforum stated that's normal for the phone to act like that, because it will just detect to flash for 1.5 sec and then jump into charging mode
do this steps and should work fine
1 - DO not connect the phone to the computer
2 - open the flash tool
3 - look for the scatter.txt file that you want to flash "either rom or recovery"
4 - click download on the top
5 - once the processes above have been done, connect the device and it will start the flashing process.
you are done.
Click to expand...
Click to collapse
Thanks! It worked.

I tried it , once I click download. I don't see it downloading anything. 0 b/s and -0 bytes.

TopoX84 said:
do this steps and should work fine (add : turn phone off)
1 - DO not connect the phone to the computer
2 - open the flash tool
3 - look for the scatter.txt file that you want to flash "either rom or recovery"
4 - click download on the top
5 - once the processes above have been done, connect the device trough usb cable (phone still off)
6- then turn it on and it will start the flashing process.
you are done.
Click to expand...
Click to collapse
Worked fine here (added some steps), did not install it from sd card as it is still in the old phone :
choosed install zip from last folder and then move to the folder where it is ( vol + /- to scroll down, power to validate). I put it on download folder (on the phone memory), but of course you can put it anywhere you want !
Very smooth install, thx for the great tutorial

Help me
Followed all your directions, when I click on download, nothing happens

yeah same here when I press "Download" nothing happens (Windows 8.1 x32)

If I use one of these methods to root my P7000, enable Link2SD and then unroot it, can I retain the Link2SD features?
I want to be able to install/move apps onto the SD card but I don't really want or need a rooted phone in the long term.

Re upload recovery:
adf . ly/1NoLAj
(without the spaces)

Hi, could you anybody please reupload files with CWM and Supersu.zip? The link doesn´t work
Edit: Sorry, the link is working, error in my browser

download link has broken. T_T

I've got " the load scatter file is invalid" is there any way to get through this problem? I've already tried different versions of SP flashtool still got the same. Files downloaded from Devblaze who reuploaded them! The first post's links don't work.

2022 - Xperia Z2 Root with Locked Bootloader, talk here

Most threads are really old, so I am starting a new one.
And one of better ones was just locked and deleted
I have Xperia Z2 D6503 with locked bootloader.
Sadly at this moment pretty much every single thread you find is 5+ years old and most links are dead.
You can find those files online but question is are those same files you need.
You might download the wrong file with same name.
So I will either update the links if I find the files or I will link the best root method if any at this present time.
And if you have any files or info to share, do so here.
So far,as of creation of this thread, nothing is available.

Ok so I will just update you with news.
I found everything I wanted from Russian folks at 4pda, simply put, once again Russians come trough when no one else could.
Spoiler: My rant
Funny thing, I always knew I should learn Russian and German, for doing things no one else can and fixing stuff, those two places/nations are simply THE best.
LIterally every time I needed something I found it on a Russian website, and every time I needed to fix something, some cool German helped out.
I am attaching the archive with all files needed to root the Xperia Z2 with locked bootloader, with instructions inside, do this at your own risk as usual.
Btw since I plan to host these files forever they should be available at all times as long as these hosts dont remove em.
Please dont contact me if they don't work, I only keep them there, I dont have them on my PC
Spoiler: DL here
Mega
Spoiler: DL here
Yandexdisk
https://disk.yandex.com/d/O-C06nagysIqQg

So I managed to root my Xperia Z2 with locked 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"
}
I would like to document my little journey here for anyone who might need help.
So first flashed the stock firmware by downloading it via XperiFirm+5.6.2+(by+Igor+Eisberg)
But that tool only downloads "File" files, it downloaded 4 of them, but you need only one FTF file.
So I used FlashTool 0.9.34.0(also called Sony Mobile Flasher by Androxyde), it has a tool, Tools > Bundles > FILESET decrypt and by following the Youtube video I used that tool to create the FTF file I needed but for some reason the FlashTool put that FTF file in C:\Users\USERNAME\.flashTool\firmwares
I also needed to install the the drivers for my phone as well as fastboot drivers, this is covered in the original guide that I included in the archive above.
Steps 7,9 and 10.
Btw sorry if I skip something I did, you can fill in the gaps, I'm sure.
Anyways after FlashTool detected my device I flashed the stock firmware(23.5.A.1.291).
Then comes the moment of rooting.
So all the drivers are installed, files are there and nicely organizd, I am ready.
I opened both guides, the original one and Russian one translated to English.
Turned out both added up together to create the ultimate guide, I will explain why in a minute.
-Put the files on SD, check;
-Rename the 575 kernel files extension to .TFT , check;
-Turn off the phone, check;
-FlashTool is opened and waiting,check;
-At this moment I actually clicked on lightning bolt icon, then I clicked Flashmode and then under Source folder I located the folder where 575.tft kernel file is located.
Then I selected THE FOLDER
After that under Firmwares, the 575 kernel shows up and I go trough drop down arrows to click on it 23.5.A.0.575.
Then I click on kernel.sin in Content section.
Then under Device filter I double click and find Xperia Z2;
-At this point I slide the Firmware Selector window to the right and I don't close it, so I can see the console and what Flashtool is reporting, the console would be the part where Flashtool is writing something, all that text under those big icons(lightning bolt,BLU,lock,key..)
-After that I hold the volume down and connect the USB cable to the phone
And I notice Flashtool tells me phone is connected in flashmode
-I click Flash in the Firmware Selector window that was still open
-It does its thing and reports success.
-I disconnect the phone and close the Flashtool as Russian instructions also recommend it, dont skip this
-I turn on the phone, all boots fine and I do check the kernel by opening the service menu(dial *#*#7378423#*#* and find Service info, first line Phone software version at the end theres .575)
Actually at this point I had minor ****pants moment, Service menu wouldn't open instantly, took about 20 seconds
-Then I proceeded to flash the recovery
But here I ran into the problem, error adb server version (40) doesn't match this client (36)
That is because 3 files inside Recovery_for_MM575-291>files folder, named
adb.exe , AdbWinApi.dll , AdbWinUsbApi.dll
need to be replaced with version 40.
So I browsed online and downloaded platform-tools_r28.0.2-windows
Here is where you can find more versions
adb-win/SDK_Platform-Tools_for_Windows at master · awake558/adb-win
adb.exe fastboot.exe. Contribute to awake558/adb-win development by creating an account on GitHub.
github.com
Theres a readme that tells you what file is what version.
So I extracted the archive and inside the platform-tools folder I found the 3 files, copied them and replaced those files I mentioned earlier located in Recovery_for_MM575-291>files .
-After that I run the install.bat without admin right actually and it all goes smooth.
-Instantly phone rebooted into recovery which made me smile
Also I pressed any key to continue and that closed the install.bat window that opened earlier on the computer.
-Then I installed SuperSU, no problem there.
-I press the arrow to go back,
-And find and finally install 291 kernel.
-After that I click reboot button
-Phone reboots without any issues.
Boom, rooted.
Hope and wish you all the best with rooting yours.

According to my experience and reanalyzing current status, I could give this as a permanent order for moving from Locked Bootloader to having a Magisk rooted ROM.
(Any error might be corrected, if an explanation is given.)
1) Flashtool's Flashmode
Flash D6503_23.5.A.0.575_kernel.ftf (which includes loader.sin and kernel.sin)
2) Backup TA partition with backupTA_v2 by Jens Andersen (XDA: rayman, Twitter: @droidray, GitHub: EnJens)
3) Reset to factory defaults
4) Unlock Bootloader
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
5) Flashtool's Flashmode
Flash D6503_23.5.A.0.575_kernel.ftf (which includes loader.sin and kernel.sin) again
6) Change recovery with (NEW)_Recovery_for_MM575-291v5 by executing its install.bat
Stay on Stock ROM:
Booting into TWRP
7) Flash root (SuperSU only)
UPDATE-SuperSU-v2.76-20160630161323.zip
8) Flash Z2_23.5.A.1.291_Marshmallow_Kernel_Flasher.zip by moman2000
Change to LineageOS:
7) Wipe cache, dalvik cache, data and system
8) Format data (for encryption removal)
9) Reboot into Fastboot mode
TWRP - Reboot to Bootloader
Flashtool - Fastboot mode
ADB - adb reboot bootloader
Volume down + Power on
10) Flash new kernel extracted from LineageOS
fastboot flash boot boot.img (fastboot flash:raw boot boot.img)
11) Flash new TWRP (twrp-3.3.1-sirius-20200221.img)
fastboot flash recovery recovery.img
12) Reboot into recovery for verification (Failsafe)
fastboot boot recovery.img
13) TWRP
Flash ROM
Flash Magisk
14) TWRP or as Magisk module
Install GApps or microG

change to ftf not tft!!!!

also great guide and thanks for the links and files basically everything

kakashi7593 said:
..it has a tool, Tools > Bundles > FILESET decrypt and by following the Youtube video...
Click to expand...
Click to collapse
Hi, Pls kindly give that youtube video link if it is still alive. I wanna know how to convert those downloaded file in to ftf format.
Rgds

[Root Guide] INSTALL ROOT / WITHOUT RECOVERY / ADB-FASTBOOT / MAGISK

Hello, first of all I apologize for my English if you don't understand me somewhere, I'm learning English. Greetings from Peru.
Files and programs you need to download​THIS PROCESS WORKS WITH ALMOST ALL DEVICES, ONLY IF THEY HAVE THE BOOTLOADER CORRECTLY UNLOCKED WITHOUT THE NEED OF A TWRP.
In the computer​1- Lenovo Rescue and Smart Assistant, will help you in 2 things: In case your device is frozen or in a loop, there you can recover it and right there you can find and download the ROM of your device for free.
As you can see in this image my device is already selected and the ROM is already downloaded (just follow the steps and your device will be fine again)
{
"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"
}
Here you will find the ROM
as you can see, location, folder and files of the ROM (it is necessary that you know where it is since you will need some files later)
2-You need to have ADB/FASTBOOT installed to be able to install the ROOT (remember that this is the safe way, there is no risk of your device freezing or in a loop, but everything is possible).
Link : https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
on device​1- First of all, you have to have the bootloader unlocked, here I leave the guide since it is somewhat long to read
Link : https://www.mobilewithdrivers.com/download/unlock-bootloader/lenovo-tab-m10-fhd-plus-tb-x606f
2- After unlocking the bootloader, you have to have Magisk.apk installed on your device
Link : https://github.com/topjohnwu/Magisk/releases
3- After installing Magisk, on the main screen you have to see if Ramdisk is "yes" or "no".
It says "si" because my native language is Spanish.
4- Go back to the computer and in the ROM folder you have to find the file "boot.img" and copy it to your device
5- within Magisk where it says "install", they give it to install and something similar to this will come out:
6- They only give the following next "siguiente " and select the option of Select file "seleccionar y parchar un archivo" (I repeat again ignore if it comes out in Spanish, you in English)
7- from there the explorer will open and they will look for where they copied the "boot.img" and select it.
Once the selector is given to start or let's start "comencemos"
the process has to be something similar to the image that I will post below, you can several certain lines but at the end it has to say "done!" without any error.
8- Now to finish the process on your device, copy the file that appears in your magisk "the patched file". Copy and paste it into the ADB/FASTBOOT folder
we return to the computer​
1- First of all, you have to enable "usb debugging" on your device
Link : https://www.embarcadero.com/starthe...bling_usb_debugging_on_an_android_device.html
2- Now go to your ADB/FASTBOOT folder and in a blank part open "powershell",
Now go to your ADB/FASTBOOT folder and in a blank part open "powershell" .
Holding SHIFT and right clicking open POWERSHELL
now they write "cmd" without quotes so that inside PowerShell you can use it as cmd
3- Here I will explain it in a long but correct way without errors, do not turn off the computer and leave it on since you will write an ADB command to order the device to enter Fastboot mode.
By typing "adb devices" you will find out if the drivers are correctly installed and your computer, cmd and adb/fastboot should recognize it.
now type "adb reboot-bootloader" , this will command your device to reboot into "bootloader" mode
Now this part is important that you pay attention as some people make mistakes.
Once your device has rebooted and you get to the "fastboot mode" screen, you will type the following in powershell :
fastboot devices
If the following appears, it is because your computer detects your device in fastboot mode.
Now comes almost the end of this guide, to install root do the following.
To root your device they usually tell you to type the following "fastboot flash boot boot.img", but sometimes there are errors.
what you will do is the following :
once you have written the following
you are going to drag the "magisk patches" file to the poweshell
and you will have to leave the path where the saved file is (this is a safe way so that you do not get errors)
now you just hit "enter" and it will be installed on your device
Now to finish, restart the device, install "root checker" and you will realize that you have it activated.
attached image of my device "Tab M10 FHD 2nd TB-x606x" with the latest ROM installed, having ROOT, MAGISK and modules installed
THIS PROCESS WORKS WITH ALMOST ALL DEVICES, ONLY IF THEY HAVE THE BOOTLOADER CORRECTLY UNLOCKED WITHOUT THE NEED OF A TWRP.
If the guide helped you, please comment, if it didn't work for you, please comment as I will try to help you solve the problem.
Currently I will not be contributing more to the community since I do not have my own computer, the computer I use will only be there for a few days, after that they will take it away.
when I have a new computer, I will be sharing RecoveryTWRP for some devices modified by me or some other help that I am able to carry out and finish as a project.
I thank XDA for creating this space to help, guide and for everyone to learn in the process.
I send you greetings from Peru.

Nice, thank you very much, sir.