Database Users

[A70B/IT2 HC][3.2.81 update] Enabling SDE and rooted firmware package

First:
Warning! This is only for A70B/A70IT2 Honeycomb model, It won't work on Froyo model!
Here is a package that enables unofficially SDE menu in recovery and install a rooted stock firmware with busybox and SuperUser.Apk
Pre-Requisite:
- Adb must be enabled on tablet and PC driver+adb command must be working. You can test on pc with "adb shell", it should give you a '$' prompt. If you don't have this, first make it work. There are multiple links around to help if needed.
Instructions:
- Unzip files on your pc in adb.exe directory.
- Launch enable_sde.bat on your pc. It's better to do it in a cmd.exe window, you'll be able to copy-paste log here if anything goes wrong.
- Follow instructions in the cmd window. Basically, script reboots tablet multiple times, you have to press enter when tablet is completely booted each time.
- Congratulation, your device is sde enabled and has a rooted sde firmware. Please read below for more information.
Upgrades:
If you already installed a first version and enabled sde already, here is how to install new rooted firmware:
- Optional: flash updated stock firmware. I always recommend to match stock firmware, it avoids dalvik-cache rebuilds and bootloaders may have been updated in new firmwares.
- Boot rooted firmware. You should be running rooted firmware if you want upgrade script to work. To be sure of that, you should see SuperUser app in your apps menu.
- Unzip files on your pc in adb.exe directory
- Launch upgrade.bat (or upgrade.sh for linux)
- Tablet reboots at the end to rooted firmware and should be upgraded to new version.
SDE information:
1) What is SDE?
SDE (Special Developer Edition) is basically a dual boot mechanism. It allows us to dual boot Archos stock firmware and our custom ones.
2) How does it work ?
I won't give much details on how to use it, I should do a separate topic about this one someday. Until then, here is some basic information:
- At the end of this script, you are booted with sde firmware, superuser should be in your start menu and you should be root with adb or any root app.
- If you reboot or boot, press volume up while booting, it will display the dual boot menu. Select "Developer Edition", it will start the rooted build (check here point 9 to see how it looks).
- If you missed volume key or don't do anything during reboot, you will go back to unrooted stock firmware. You have to press the volume up key during boot to get the boot menu.
- Warning: booting stock firmware is harmless except that you will loose your SuperUser.apk preferences. As it's not part of stock firmware, Android clears it.
- You can boot straight to rooted firmware by deleting the stock firmware kernel in recovery. Check here, do point 4,5, and on screen 6, select "Remove Android Kernel". Make sure that you have properly working SDE firmware before doing that. If you want to re-enable back stock firmware, just flash it from recovery again.
Downloads:
3.2.80 can be downloaded here: Mirror 1 (Mediafire), Mirror 2 (Sendspace).
3.2.81 can be downloaded here: Mirror 1 (SendSpace) (bat fixed)
Sorry, Mediafire no longer let me upload without signup, if you know one good upload location without registration and allowing more than 200 MB, let me know.

*reserved*

Registered just to say thank you!
Worked like a charm, and no problems using the shell script (I run Arch Linux)
Keep up the good work!

Thanks
I mean real thanks
Sent from my ARCHOS 70it2 using xda premium
EDIT:
Beautiful man, beautiful. Works splendidly
Thanks again

LeTama
Have a beer or two on me, 84G89322WT2139701.
Thanks again for your Rom.

Hi mrew42,
Thanks a lot! Much appreciated!

Tomorrow, my 70b return at home
I testing that !
but my 70bit2 is with 3.2.81

Letama, can you may be make the same for 3.2.81?

Yes, it will come soon...

3.2.81 is up and instructions on first post updated if you upgrade.

Great
http://www.jbmm.fr/?p=27601
{
"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"
}

cajl said:
Great
Click to expand...
Click to collapse
Nice job! Thanks for the article on jbmm!

Thanks, will try it out soon.

Thanks letama, this is just what I wanted. Awsome work!
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Keep up the good work and thanks again.

ColinTaylor said:
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Click to expand...
Click to collapse
Ah! Right! Thanks for pointing it, I'll fix that and re-upload when I find time to do it.
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
Yes, this is normal, this one is only needed when enabling sde first time. local.prop is coming from temp root and won't be there anymore.

I finally had time to try it out tonight, all seemed to be installed fine, but I don't see the Superuser in the apps list... I can boot into developers fw menu though. Did I miss something or should I just try to reinstall the SDE again by running that bat file again?

No, as ColinTaylor said, there is a typo in script, you just need to push the ext4.update at root of storage.
Just type this command in the directory you unzipped the files:
Code:
adb push android_32.ext4.update /data/media/
then boot sde.

Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!

hello, first of all thanks for your work.
I am having some problems with the upgrade file.
it says that it cannot stat 'zImage':no such file or directory
and secondly it cannot open the kernel file (no such file or directory) mkf lashimage failed.
could you please provide some help with this?
thanks!

lozano.markp said:
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
Click to expand...
Click to collapse
adb is a developer tool from android sdk that let you execute commands on your tablet from your PC. You have to install android sdk to get it, you need to enable it on the tablet and have a proper driver.

[TUT.easy] Back to stock. (Including working TrackID.apk)

Right, so you’ve got your bootloader unlocked and/or custom ROM flashed and now want to get everything back to stock. The stock TrackID and the Like app don’t work (ERROR 5) however due to the DRM stuff.
So here’s your workaround. All you do is to get the trackID.apk off market and push/ replace it to system so it works. You wouldn’t get DRM back though, but this is as close as you’ll get to the stock thing. There may be alternate ways to do this but this tutorial lists the exact way I did it (trying to avoid root and custom kernels).
The result was that I finally did get TrackID working on stock firmware after relocking the bootloader. Furthermore, it did work after an OTA update as well. I did use an Xperia Pro MK16i but since everything is rather general, it should work on any phone.
What you'll need:
Yaffey
Flashtool
A .zip extractor (would recommend 7-zip)
The attached TrackID.apk
Unlocked bootloader
Fastboot drivers (You may have installed it while unlocking your bootloader. If you haven’t, go here and start at step 8 and end at 15)
Step 1: Flashing stock firmware.
1. Find the required .ftf firmware file.
2. Download and install Flashtool/
3. Use this guide understand how Flashtool works and flash the downloaded firmware.
Now you should have stock firmware running on the phone. It doesn’t have root and neither do we need it as long as we still have the unlocked bootloader.
Step 2: Creating an edited .IMG file (which has the working TrackID.apk)
Note: You don’t need your phone for this step so keep it aside for now.
4. Using 7-zip (or whatever) extract the contents of the .ftf file that you just flashed onto the phone to a folder- you’ll find several .sin files.
5. Open Flashtool. Got to Advanced> SIN Editor and browse to the system.sin file you just extracted. Hit ‘Dump data’. You’ll find that it just created a system.yaffs2 file in the same folder which had the .sin file. Close Flashtool.
{
"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"
}
6. Now, download and open up Yaffey. Click the open tab and browse to the system.yaffs2 file and open it. Close the summary tab.
7. Expand the ‘app’ tab, find trackid.apk and delete it.
8. Highlight the ‘app’ tab again and click import. Import the trackid.apk file which is attached below.
9. Find the apk you just imported and edit the properties to what’s shown in the pic (-rw-r--r--). Hit OK.
10. Now click ‘Save As’ option and type in the ‘.img’ extension before you save it anywhere you like. Close Yaffey. You’ve created the .IMG file.
Step 3. Flashing the .IMG file via fastboot.
11. Switch off your phone and connect it via fastboot mode. Was holding menu while inserting the cable on the MKI6i but might be different based on your phone model. You should get the blue light once it’s connected.
12. Open command prompt wherever you have fastboot drivers installed. Enter this command - fastboot.exe -i 0x0fce getvar version (just to verify that you’re properly connected, you should get some response back)
13. Now hit fastboot.exe flash system C:\system.img (OR WHEREVER YOU HAD SAVED THE .IMG FILE, I saved it in C:\)
14. Let it do its work and you’re done. Hit fastboot.exe reboot , remove the cable and wait till your phone boots.
TrackID should work fine now and all that’s left to do is to relock your bootloader. Follow Bagus’s thread by flashing the file via Flashtool and you’re done. Completely stock, Track ID works and the bootloader is locked.

FAQs
Why the long process? Can’t I just flash the file via CWM recovery?
Like I said, I wanted to stick to as much ‘stock’ as possible. Hence didn’t feel like rooting it or flashing a custom kernel etc. Stock firmware, edited stock system.img was as close to stock I could get. But if you do feel that an alternate method may suit you better, feel free to do so.
I get a ‘Failed’ error in step 13?
Make sure your bootloader is unlocked. If you did relock it earlier, then unlock it again using the instructions on the SE page, complete this tutorial and relock it. Doesn’t really matter how many times you unlock/relock.
Why use the TrackID.apk you provided?
The attached apk is the latest version and I edited the icon image to make it look like that of the stock TrackID. (There is a difference in the icon image of the one present stock on the phone and the app you get off market). If the icon image doesn’t matter to you, you can use any TrackID.apk file. But make sure it isn’t the stock app which requires the DRM bit as it’ll be nothing but a huge waste of time then.
PS. As the attached .apk is edited, you may get an error message if you try installing it as a user app. Follow the tutorial and you should be fine. It may be fine for flashing via CWM as well but I haven’t tested that.
Such a long process, and just to get TrackID working? Are ya freakin’ crazy mate?
Umm, yes I am.
Will FB music like app work as well?
It should as it’s linked to TrackID. Would appreciate if someone reports back on whether it does or not.
Would this bring back warranty?
Well, that is the main reason I decided to do it in the first place. After doing this, mine was covered under warranty, and they sent me a new device as something was wrong with the memory card reader of the old one. But again, I may have been lucky as they may have other ways to check the DRM status.
PS. This is my first tutorial on XDA. It’s just me sharing what I’d done to make sure my phone gets covered under warranty. I will not be responsible if your phone doesn’t get covered under warranty or if you managed to mess up the steps mentioned. This tutorial, and any tutorial for that matter, should be carried out at your own risk.

Why don't you just install TrackID from Play Store?
And FB Music Like button requires DRM keys if I am not mistaken.

Someguyfromhell said:
Why don't you just install TrackID from Play Store?
And FB Music Like button requires DRM keys if I am not mistaken.
Click to expand...
Click to collapse
Well, the idea was to replace the TrackID system app with the one that works instead of having two of them in the app drawer. To me, it was more of a pre-warranty situation and I just felt the need to get everything as much 'back to stock' as possible.
As for the FB Like, I'm really not sure and did mention as well that it's not tested. I remember coming across somewhere that the both are interlinked or something, so just thought that might work as well, not sure though.

Can someone just replace the market trackid widget back to the stock one?
Sent From My Sony Xperia Arc S

[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

Fixing script for boot looping on OOS 3 [Windows]

OK, I just did another rescue script, it's using the files from the final release but it will install them one at a time using your computer instead of trying to install the rom.
THIS GUIDE IS FOR WINDOWS ONLY!
If someone else wants to convert it for Linux/OSX feel free but please make a new thread with a similar format to the title as this one but with [Linux/OSX]
Bear in mind this script will also install the compatible TWRP version 3.0.2.0 which will work with the final OOS3 and also with the new codebase in CM13 unless you sideload the complete rom in which case that will install the default OnePlus recovery. You can always install TWRP using the files within after this anyway
Anyone who wants to give it a go can download it at the link below, remember IT'S NOT A FLASHABLE ZIP, it's the files packaged into a zip.
Download here from Android FileHost : https://www.androidfilehost.com/?fid=24580943222146240
Carry out the following instructions as I have entered them.
Unpack the zip file into a folder, possibly on your desktop so you can see all the files easily.
Reboot your phone into fastboot mode by holding down the VOLUME UP button while holding the POWER button until you see fastboot mode show, obviously make sure you have connected the phone to your computer via usb cable.
If you have not unlocked your phone then immediately go watch the video below to find out how to do so then come back and continue the instructions from step 4.
https://www.youtube.com/watch?v=KZaajUEybNM
Open an elevated prompt window in the folder you unpacked the zip into (elevated means it has administrator privileges), to do this, right click in the folder (not on a file) while holding the SHIFT key, then choose "Open command window here", see below:
{
"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"
}
You may be prompted to allow admin privileges, say yes.
In the command window you opened type the following:
fastboot devices
You should then see something similar to the screenshot below:
If you don't see a number followed by fastboot then you need to install or re-install your drivers. (I've uploaded the latest version to Android FileHost here : Download, remember to restart the computer before proceeding)
If you do see something similar to the above, then type the following into the command window:
fixoos
Then press enter, now adb will flash the different new versions of the partitions needed to either install the rom or reboot into the new version of TWRP.
It should look like this (I've shrunk the text to try to fit it all in) :
The last 2 steps in the script are going to flash the new compatible TWRP as your recovery partition and then it will also reboot into that version of TWRP.
All of this presumes that you were able to copy whichever rom you want to install onto your phone.
If you did not copy the rom onto your phone then download it the link below :
https://www.androidfilehost.com/?fid=24580917854994435
Copy the file into the same folder as the rest of the files and then run the following in the command window :
adb sideload OnePlus2Oxygen_14_OTA_019_all_1606041303.zip
(If you start typing the filename and press TAB it should autocomplete the name as long as the zip file is in the same folder as you opened the command window in)
Now press enter and ADB should install the full release rom itself, bear in mind, this will NOT include the new TWRP as TWRP is not a part of the default rom.
Please post any problems you have below, however, as long as you follow the instructions properly you should be ok.

djsubterrain said:
OK, I just did another rescue script, it's using the files from the final release but it will install them one at a time using your computer instead of trying to install the rom.
THIS GUIDE IS FOR WINDOWS ONLY!
If someone else wants to convert it for Linux/OSX feel free but please make a new thread with a similar format to the title as this one but with [Linux/OSX]
Bear in mind this script will also install the compatible TWRP version 3.0.2.0 which will work with the final OOS3 and also with the new codebase in CM13 unless you sideload the complete rom in which case that will install the default OnePlus recovery. You can always install TWRP using the files within after this anyway
Anyone who wants to give it a go can download it at the link below, remember IT'S NOT A FLASHABLE ZIP, it's the files packaged into a zip.
Download here from Android FileHost : https://www.androidfilehost.com/?fid=24580943222146240
Carry out the following instructions as I have entered them.
Unpack the zip file into a folder, possibly on your desktop so you can see all the files easily.
Reboot your phone into fastboot mode by holding down the VOLUME UP button while holding the POWER button until you see fastboot mode show, obviously make sure you have connected the phone to your computer via usb cable.
If you have not unlocked your phone then immediately go watch the video below to find out how to do so then come back and continue the instructions from step 4.
https://www.youtube.com/watch?v=KZaajUEybNM
Open an elevated prompt window in the folder you unpacked the zip into (elevated means it has administrator privileges), to do this, right click in the folder (not on a file) while holding the SHIFT key, then choose "Open command window here", see below:
You may be prompted to allow admin privileges, say yes.
In the command window you opened type the following:
fastboot devices
You should then see something similar to the screenshot below:
If you don't see a number followed by fastboot then you need to install or re-install your drivers. (I've uploaded the latest version to Android FileHost here : Download, remember to restart the computer before proceeding)
If you do see something similar to the above, then type the following into the command window:
fixoos
Then press enter, now adb will flash the different new versions of the partitions needed to either install the rom or reboot into the new version of TWRP.
It should look like this (I've shrunk the text to try to fit it all in) :
The last 2 steps in the script are going to flash the new compatible TWRP as your recovery partition and then it will also reboot into that version of TWRP.
All of this presumes that you were able to copy whichever rom you want to install onto your phone.
If you did not copy the rom onto your phone then download it the link below :
https://www.androidfilehost.com/?fid=24580917854994435
Copy the file into the same folder as the rest of the files and then run the following in the command window :
adb sideload OnePlus2Oxygen_14_OTA_019_all_1606041303.zip
(If you start typing the filename and press TAB it should autocomplete the name as long as the zip file is in the same folder as you opened the command window in)
Now press enter and ADB should install the full release rom itself, bear in mind, this will NOT include the new TWRP as TWRP is not a part of the default rom.
Please post any problems you have below, however, as long as you follow the instructions properly you should be ok.
Click to expand...
Click to collapse
Linux version -> http://forum.xda-developers.com/oneplus-2/help/linux-fixing-script-boot-looping-oos-3-t3395736

[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.