Database Users

Installing TWRP. Stuck at "waiting for device"

I'm getting this issue with Kindle Fire Utility when trying to install TWRP;
{
"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 have rebooted my kindle fire while waiting for it, but I haven't been able to find other solutions, please help! I'm fairly sure that I have ADB working... I'm really not sure what to do

georgeos said:
I'm getting this issue with Kindle Fire Utility when trying to install TWRP;
I have rebooted my kindle fire while waiting for it, but I haven't been able to find other solutions, please help! I'm fairly sure that I have ADB working... I'm really not sure what to do
Click to expand...
Click to collapse
If you would have followed my tutorial you wouldnt have this problem here is the fix:
• I have noticed that some people have problems getting stuck around 2:32 into the video where twrp is downloading and getting ready to install. If this happens to you and it is constantly “waiting for device” You may need to hit disconnect on your KF and run burrito root on your Kindle again, click “agree”,then click “You Rock”, Then click “root”. Once you do so you must re-open adb shell by opening a command prompt and typing the following:
cd c:\KindleADB this is to get into adb shell
adb devices this is to make sure your kindle is connected properly
adb root this is to get proper permissions
Just to be very clear on what you should type in your cmd prompt:
cd c:\KindleADB
adb devices
adb root
• Once you have done this re-open the run bat in KFU v0.9.1 and select option 5 again and it will install the twrp with proper root permissions.
here is a link to my tutorial for you to check if you have more problems afterwards:
http://forum.xda-developers.com/showthread.php?t=1417234

[-_-] said:
If you would have followed my tutorial you wouldnt have this problem here is the fix:
• I have noticed that some people have problems getting stuck around 2:32 into the video where twrp is downloading and getting ready to install. If this happens to you and it is constantly “waiting for device” You may need to hit disconnect on your KF and run burrito root on your Kindle again, click “agree”,then click “You Rock”, Then click “root”. Once you do so you must re-open adb shell by opening a command prompt and typing the following:
cd c:\KindleADB this is to get into adb shell
adb devices this is to make sure your kindle is connected properly
adb root this is to get proper permissions
Just to be very clear on what you should type in your cmd prompt:
cd c:\KindleADB
adb devices
adb root
• Once you have done this re-open the run bat in KFU v0.9.1 and select option 5 again and it will install the twrp with proper root permissions.
here is a link to my tutorial for you to check if you have more problems afterwards:
http://forum.xda-developers.com/showthread.php?t=1417234
Click to expand...
Click to collapse
I tried what you said, and have made some progress, the Kindle Fire is rebooting when it comes to say "waiting for device" but then gets stuck at boot, so I have to put it back to normal boot rather than fast boot

georgeos said:
I tried what you said, and have made some progress, the Kindle Fire is rebooting when it comes to say "waiting for device" but then gets stuck at boot, so I have to put it back to normal boot rather than fast boot
Click to expand...
Click to collapse
Once again all of the answers to your problems and the questions you have are in this tutorial. From what it looks like to me from your screen shot you do not have "root Permissions" if this is in fact the problem then what you are probably trying to do is to start at step five from the Kindle Fire Utility and download to install twrp2.0 If this is what you are trying to do then you must see on the command prompt of KFU that you are downloading and then waiting on device. If this is still your situation then the fix is what I stated above and in my link. If you have gotten passed that problem and still have issues with you either being stuck at the yellow triangle( firefirefire ) or a Kindle Fire boot screen that will not go away then the fix is also in my link... If you do not wish to follow the link and see the videos or read through the trouble shooting guide then I am afraid I have no way of helping you...
If I helped please do not forget to hit the thanks button and post back in my guide thread that it worked okay for you as well so that new members can see that this is one of the easiest guides to follow here is a link to take you to that guide a little quicker good luck....
http://forum.xda-developers.com/show....php?t=1417234
If you need further help reply in that thread and I will be more than happy to help you there so others can find the fix to the problem that you come across a little easier

I got stuck in several places when I did it, the issues I had where an old version of adb, and drivers, had to uninstall and reinstall the drivers
Sent from my Kindle Fire using xda premium

KFU Tweak to restore Full Functionality w/6.2.2 and BurritoRoot

Not wanting to steal any of Vashypooh's thunder, but I kluged together the following tweak/hack to restore full functionality to KFU with 6.2.2 ROM and the new version of BurritoRoot.
Basically I've taken JCase's directions for using BurritoRoot2 and incorporated them into Vashypooh's script. I know there are better ways to do this, but everything seems to be working OK.
1. Download the new BurritoRoot2. Links can be found at the following post:
http://forum.xda-developers.com/showthread.php?t=1410223
2. Move BurritoRoot2.bin to the '\files' subdirectory in your Kindle Fire Utility directory.
3. Find 'run.bat' in the KFU directory, open in your favorite text editor, and find the following section:
Code:
:burrito
if "%adb%" == "Online" (
if /i not "%rooted%" == "Yes" (
echo. Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
echo.
tools\adb install -r files\\%kindleroot%
echo. Activating BurritoRoot...
tools\adb shell am start -a android.intent.action.MAIN -n net.andirc.kindleroot/net.andirc.kindleroot.DirectCall
echo. Elevating the Shell...
tools\adb kill-server
echo.
tools\adb root
echo.
tools\sleep 5
set rooted="yes"
4. Edit the section so it looks like the following (the highlighted lines are the changes):
Code:
:burrito
if "%adb%" == "Online" (
if /i not "%rooted%" == "Yes" (
echo. Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
echo.
[COLOR="Red"][B]tools\adb push files\BurritoRoot2.bin /data/local/
tools\adb shell chmod 777 /data/local/BurritoRoot2.bin[/B][/COLOR]
echo. Activating BurritoRoot...
[COLOR="red"][B]tools\adb shell /data/local/BurritoRoot2.bin[/B][/COLOR]
echo. Elevating the Shell...
tools\adb kill-server
echo.
tools\adb root
echo.
tools\sleep 5
set rooted="yes"
5. Save the file and run. Full Functionality should be restored to KFU
I'll have to admit I haven't tried every option, but I have been able to install the permanent root, install Twrp, and install the Google apps.
Hopefully this works OK for you. If not... I can try to help, but I'm really pretty new at all of this. You might be better waiting for the next version of KFU.

I just used your method and replaced the Burrito2 code and added in the file. Then I went to 0.92 KFU and run it. Now my Kindle is bricked, stuck on kindle fire logo and the unbrick utility won't work for it.

thanks alot, your method works, i can install TWRP now
centerofprizes said:
I just used your method and replaced the Burrito2 code and added in the file. Then I went to 0.92 KFU and run it. Now my Kindle is bricked, stuck on kindle fire logo and the unbrick utility won't work for it.
Click to expand...
Click to collapse
thanks alot, your method works, i can install TWRP now on 6.2.2

centerofprizes said:
I just used your method and replaced the Burrito2 code and added in the file. Then I went to 0.92 KFU and run it. Now my Kindle is bricked, stuck on kindle fire logo and the unbrick utility won't work for it.
Click to expand...
Click to collapse
since it is still kfu the op of kfu is still valid:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506

Follow the instructions carefully and don't mess up your run.bat. This method DID work for me. I regained root and reinstalled recovery without issue.
Thank you very much, rich_stwrt!

Have you PMed vashy with the updated code so he could add it to the KFU on the main thread?

thrasherht said:
Have you PMed vashy with the updated code so he could add it to the KFU on the main thread?
Click to expand...
Click to collapse
I like this idea too.
Thanx for the info, changes worked fine for me. Just got my kindle 2 days ago and got recovery going now...time for some flashing!

yeah... if you use this to try and get into fastboot mode.... it'll brick you
i'm now bricked...

the_kwa said:
yeah... if you use this to try and get into fastboot mode.... it'll brick you
i'm now bricked...
Click to expand...
Click to collapse
Most likely not...
I used this this morning without any issue on a friends KF using his computer... There was a hitch where trying to get fastboot working but as usual it was the common problem of device drivers needing to be redone (again). Every thing needed to get his KF settled after the update is included.
Note that if you are seeing <waiting for device> your drivers are not loaded correctly... Even if they were before... you need to reinstall them again.

well, my kindle won't boot past the "kindle fire" screen, i've rebooted numerous times...
the lack of solid drivers for this thing is ridiculous

I edited the .bat file as you showed us how to do here and it worked great using the KFU, thanks a ton!!
---------- Post added at 11:47 PM ---------- Previous post was at 11:44 PM ----------
the_kwa said:
well, my kindle won't boot past the "kindle fire" screen, i've rebooted numerous times...
the lack of solid drivers for this thing is ridiculous
Click to expand...
Click to collapse
what do you mean lack of solid drivers?
They include the only drivers you need with the KFU. If you get stuck look up the KFU thread (http://forum.xda-developers.com/showthread.php?t=1399889) and there are plenty of people that got stuck, read how to get unstuck in that thread.
If you follow the directions carefully it should work as I have done it all on 3 kindle fires and all 3 worked flawlessly. The 1st one required me to install drivers again and after that everything very smooth.

like alot of people i'm reading about, i've downloaded the "install_drivers.bat" 1k times.
i even deleted android sdk and re-installed it, still same thing. adb works, fastboot does not.
Devices and printers in normal power on: (adb working)
{
"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"
}
Devices and printers in fastboot mode: (fastboot not working)
[Update] even though KFU showed no device attached, i ran option 1 again and it booted back up. i still can't use fastboot

root Kindle 6.2.2
Ready to paste Burrito2 from Kindleupdates folder, but can't find "files" directory, even with search. Do I edit run.bat on the Kindle? Is there any way to see all the kindle folders on the computer? TIA

I tried this method but i'm getting this error when the kfu tries to write the recovery image after rebooting into fastboot mode.
"downloading 'boot.img'... FAILED (data transfer failure (Too many links)"
Anyone had a similar issue?
I'm posting here cause i can't post in the official kfu thread.

Thanks for this! It worked great to quickly re-root my Kindle. I had absolutely no problems, but that may be because I don't use Fastboot. (To be honest, I never understood what I needed it for.)

Repacked KFU
You can find the repackaged Kindle Fire Utility for Firmware 6.6.2 in this thread:
http://forum.xda-developers.com/showthread.php?t=1458841

Thanks for this tweak. It worked perfectly! Before this, I'd rooted manually following jcase's instructions but wasn't able to get the recovery software loaded. This fixed the issues
Sent from my KF CM7 using Tapatalk

Euclid100 said:
You can find the repackaged Kindle Fire Utility for Firmware 6.6.2 in this thread:
http://forum.xda-developers.com/showthread.php?t=1458841
Click to expand...
Click to collapse
Comes up as invalid thread .
Anyone have a working link?
Thanks

damnlimey said:
Comes up as invalid thread .
Anyone have a working link?
Thanks
Click to expand...
Click to collapse
no - thread seems to be deleted - have to it by yourself like stated in the op

Thanks XDA ,modified the batch file and it works like a charm on 6.2.2

[Solved By the Genius (b63)] my Kindle Stuck At logo

Hi
I have Kindle Fire 6.2.2
and I tried to do what wrote here
http://forum.xda-developers.com/showthread.php?t=1369040
install the Root and everything goes well
then started to do what wrote Up
I came to replacy "libandroid_runtime.so", then the scren just frozen
waited around 5 min then turn it off
when I turn it on again, stuck at the logo and never cross it
I'm very amatur about fire, so please anyone help me solve this problem?

would try to follow this thread:
http://forum.xda-developers.com/showthread.php?t=1455501
basically install fff/twrp and flash one of the prerooted stock roms:
http://forum.xda-developers.com/showthread.php?t=1451747

ok, thanks of course
but let me tell you I'm a very stubid person
you know? the root couldnt do it without the video on Youtube
so can you please give me the steps one by one, like how can i install twrp??
i relly don't know that much, but i would be pleased if you help me, thank you anyway

1. download kfu http://random.kennocha.com/kindle/utility/Kindle_Fire_Utility_v0.9.2.zip
2. extract to c:\ and rename "kindle fire utility" to "kfu" that it is "c:\fku"
3. download http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img
4. move it to c:\kfu\tools"
5. open a (elevated command prompt) and enter "cd c:\kfu\tools"
6. enter "fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img" - leave command prompt open - need it later
7. tap reboot on the kf - it should reboot to twrp
8. download http://www.multiupload.com/VUAPS24569
9. rename downloaded file to "update.zip"
10. copy update.zip to sdcard
11. in twrp on the kf tap install - select update.zip and install
12. if it finished tap clear dalvik/cache on the same site
13. in your command prompt type: adb shell "idme bootmode 4000"
14. and then type: adb reboot
that's it - if you have got no errors to this point it should reboot - it takes some time for the first boot
good luck !

Thank You Again I Know I'm like Pain in the Ass, but you are amazing.
So, Now I'm at TWR, I did All the 10 steps successfully but still My PC couldn't find My Kindle Fire So I can copy update.zip to sdcard
Is there A Soultion you have for this problem?
becuase I think my problem will be kind of easy after this step, right?
Of Course many thanks to you, relly man you are a lifesaver
I Love You

PS : when i adapt the kf with my pc and go to Devises and printers
it goes under "unspecified" and the name "Unknown Device"
not like the others the name is "kindle fire".
I'don't know relly what the mistake that I made but I'm sure I did one because
before the name was Kindle fire not unknown
and thanks again anda again and again

it's a driver issue right now
- right click the unknown device and select update driver
- select don't search and have disk
- direct it to c:\kfu\drivers\kindle
if your on win7 this might be helpful too:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41

Sorry for being late, but i had a problem with the internet conection
So...
My PC OS is Windows 7 64-bit
i did what wrote on this: http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
but it dosen't really helpful, in fact it was somehow, let me tell you what i got now
Now, My Pc Recognized my Kindle, and when I go to devices and printers I had this "http://i.imgur.com/q8SCu.png"
but when I go to My Computer, I found nothing !!
there is no Driver for the device.
So... is there any solution to this problem?

when you are in twrp you should tap on mount and mount the sdcard
then it should show up on your computer
you should use device manager to look at the devices and see what's going on
what i see on your picture is not the device manager

Ok, this is photo from my device manger
{
"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"
}
about the twrp i don't have any option
just the the yellow triangle and wrote down "Press power button for recovery"
of course i try to hold on the power button to recovery and nothing happen
also try to press the power button repeatedly but nothing happen

try to issue:
fastboot -i 0x1949 oem idme bootmode 5001
if the command says <waiting for device> then power it down by holding pwr ~20sec - unplug and replug - but don't power it on - does it by itself
the kf should pickup the command at some point and the command finishes

No Way!!
Now I'm really like this
really I don't think that my kindle will be back after what I did
but you man?? Unbelievable, you are amazing, you are Genius
Thank you so much, so much.
Now People I have My Kindle Back, wow!
That's really Unbelievable.
and you sir, you are fantastic!
thank you again, and good night "it's night where I live"

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

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