Database Users

[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

[Q] [HELP!] softbricked, can't load files, what to do?

So I was attempting to load Lollipop onto my Nexus 4, and stupidly was multi-tasking at the time. I wiped the cache, data, the system, dalvik, etc in preparation for loading the new ROM, GAapps, etc. Then when I tried to install them from a zip, I realized the really stupid error I made - I had also wiped the sd card. So now I have no installed ROM, and a completely blank sd card and phone, and of course it is in a bootloop. I've looked all over, and all of the answers seem to be the same - either push the files on, use sideload, or if all else fails, use the Wugfresh toolkit to restore it to factory. Sounds great. Except now windows can't see my phone and I can't copy files to it, push files to it, reach it through adb, etc.
- The phone turns on, and I can reach the bootloader and recovery.
- Windows recognizes that a device is attached, but then tells me there is a problem with the drivers. I have run the full driver install from Wugfresh with the Google drivers, and it says it is fine, but any time I connect the phone, it has an error.
- Through device manager, I've updated drivers to various types (standard MTP, android ADB, etc) and it usually works successfully, but the phone still doesn't show in explorer and adb lists no attached devices.
Any ideas? Thanks for your help.

ahs646 said:
So I was attempting to load Lollipop onto my Nexus 4, and stupidly was multi-tasking at the time. I wiped the cache, data, the system, dalvik, etc in preparation for loading the new ROM, GAapps, etc. Then when I tried to install them from a zip, I realized the really stupid error I made - I had also wiped the sd card. So now I have no installed ROM, and a completely blank sd card and phone, and of course it is in a bootloop. I've looked all over, and all of the answers seem to be the same - either push the files on, use sideload, or if all else fails, use the Wugfresh toolkit to restore it to factory. Sounds great. Except now windows can't see my phone and I can't copy files to it, push files to it, reach it through adb, etc.
- The phone turns on, and I can't reach the bootloader and recovery.
- Windows recognizes that a device is attached, but then tells me there is a problem with the drivers. I have run the full driver install from Wugfresh with the Google drivers, and it says it is fine, but any time I connect the phone, it has an error.
- Through device manager, I've updated drivers to various types (standard MTP, android ADB, etc) and it usually works successfully, but the phone still doesn't show in explorer and adb lists no attached devices.
Any ideas? Thanks for your help.
Click to expand...
Click to collapse
Press and hold Volume + and Volume - with Power toghether.
Stay press until it don't self-reboot itself.
When the logo about bootloader will load up, you can choose what to do :
1 ) Reinstall the stock roms 4.4.4 (https://dl.google.com/dl/android/aosp/occam-ktu84p-factory-b6ac3ad6.tgz)
2) If you still have a modify recovery (CWM or TRWP) you can run it and install zip from sideload. Put the rom zipped you wanna install where did you have adb tools and run "adb sideload <file.zip>" and wait it should be install.
If that dosen't work, you need to use download mode from LG ( for the moment i can't found a guide to do it, check on XDA / Google).

Thanks LainX, but as I said in my original post, my pc can't see the phone, so ADB can't connect and I can't get the new files over to it.

ahs646 said:
Thanks LainX, but as I said in my original post, my pc can't see the phone, so ADB can't connect and I can't get the new files over to it.
Click to expand...
Click to collapse
Did you try download mode ?
{
"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 don't think I've seen this "download mode." Where is this - on the phone (in recovery?) or through adb or sideload. The problem seems to be (and I see there are a few others right now with the same problem) that windows sees that the phone is connected, but then there seems to be a driver error such that the device doesn't show up in explorer, and abd and fastboot can't see the phone either.
I've tried different drivers, but haven't systematically gone through every single option so far, which is my next stop. Is any one driver option more failsafe than the others? Also, perhaps related - in the past, any time I've installed the drivers and connected to my phone from my pc, it never seems to "stick." Invariably, I can't access the phone through MTP after a short while (maybe after a reboot?). Recently I found updating the driver to just a Portable Device/Standard MTP USB device driver (i.e. not Google, Samsung, Android, etc) made it work. So now I feel the driver troubleshooting part is even longer and more complicated - go through all of the uninstall/reboot/install with the four Android options, then all of the generic Windows options. So I was just hoping that someone out there might have already cracked this and could point me in the right direction.
Also, in digging through some posts on reddit on related problems, someone said that Windows Media Player is somehow critical for MTP functionality. Is this the case? I had never heard this before. I don't have WMP installed, and in trying to install it, have come up with a Windows error. I'm not clear on the relationship between MTP and ADB/fastboot. Is MTP necessary for the file transfer, or is that not relevant here?
And one final question - to use adb/fastboot, do I need to be in bootloader or in recovery? To install the drivers, do I need to be in either bootloader or recovery?
Thanks so much.

[Tutorial] Easy way to ROOT Vivo Air

Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war
* or the current economic crisis caused by you following these directions.
* So don't be an *** ****
*/
DO NOT TAKE AN OTA WHILE ROOTED!!! YOU WILL HAVE A BRICK IN YOUR HANDS!!!
Hi, For while i try Root my Vivo Air and don't get much success with it... so i try a new ADB Driver* and that works :highfive:
Using vRoot you can easy root your phone BUT the problem is the Chinese SuperSU... so i get on Google a Script who Replace the Chinese SU to XDA's @Chainfire SuperSU :highfive:
So follow the Steps ;D
1 - Download vRoot , ADB installer (Just to have sure about the drivers) , Google ADB Driver Modificated to Vivo Air (Driver without Signature =/ ) and WolfDroid Script
2 - Install vRoot and ADB Installer on computer ;D
3 - Turn ON the USB Debugging ... (if you put the cable but don't appear the option to turn it on, go on settings -> about Device and click over "Build Number" 5 times to get developer Mode, than you go back and enter on Developer Options and turn on USB Debugging)
4 - than put the cable and wait the computer says about missing driver... than unzip the "Blu Vivo Air.rar"(Google Generic ADB Driver modificated to BLU Vivo Air) and go on device manager and follow the photo steps on FAQ above
5 - now turn off the Antivirus Firewall to ADB Daemon Server can Work without any restrictions
6 - execute vRoot and follow the steps on screen (Any doubts search on Youtube how to follow that) and at final step on rooting the phone will restart and maybe the computer recognized a MT65xx Driver installation but that isn't need to root... than he will show Rooted status on vRoot program
7- after all that you allow file copy to get acess to internal storage from phone to put the Folder MRW from WolfDroid Script.zip on phone and follow this steps from this official video from WolfDroid (Just to remember, is need to install a Terminal emulator app from google market to do this step)
8 - after replace the chinese SU to SuperSU you go to google market and update the SuperSU to lasted update and execute SuperSU to update the binaries and reboot
9 - Finish the process ;D

- FAQ:
1 - Question: Modificated Blu Vivo Air ADB Driver installation
Answer: you can try follow this steps from original Driver developer on Brazilian Forum (Just to remember.. the driver download already have all customizations about he describe on photos... LINK) or just follow this photos/steps on above
Go to Device Manager and right Click to select Update driver selected
{
"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"
}
Click on Browse My Computer for driver software
Click Let me pick...
Click Show ALL...
Have Disk...
Search...
Go to located Unzip Folder and select Android_WinUSB.inf ... than click Open(or two click on .inf) and than OK
Select the Android Composite ADB Interface and click NEXT and Accept if he ask if you want install this driver anyway
Now you Installed your ADB Driver working :highfive:
Have any question, Commit above... i will try answer you and maybe i can put here on FAQ to everyone :highfive:

Google ADB Driver Modificated to Vivo Air download link is broken. Can you fix it please.

broken link
there is a broken link in your post. can you please fix it. I'm trying to flash my vivo air.
thanks
DvDwx. said:
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war
* or the current economic crisis caused by you following these directions.
* So don't be an *** ****
*/
DO NOT TAKE AN OTA WHILE ROOTED!!! YOU WILL HAVE A BRICK IN YOUR HANDS!!!
Hi, For while i try Root my Vivo Air and don't get much success with it... so i try a new ADB Driver* and that works :highfive:
Using vRoot you can easy root your phone BUT the problem is the Chinese SuperSU... so i get on Google a Script who Replace the Chinese SU to XDA's @Chainfire SuperSU :highfive:
So follow the Steps ;D
1 - Download vRoot , ADB installer (Just to have sure about the drivers) , Google ADB Driver Modificated to Vivo Air (Driver without Signature =/ ) and WolfDroid Script
2 - Install vRoot and ADB Installer on computer ;D
3 - Turn ON the USB Debugging ... (if you put the cable but don't appear the option to turn it on, go on settings -> about Device and click over "Build Number" 5 times to get developer Mode, than you go back and enter on Developer Options and turn on USB Debugging)
4 - than put the cable and wait the computer says about missing driver... than unzip the "Blu Vivo Air.rar"(Google Generic ADB Driver modificated to BLU Vivo Air) and go on device manager and follow the photo steps on FAQ above
5 - now turn off the Antivirus Firewall to ADB Daemon Server can Work without any restrictions
6 - execute vRoot and follow the steps on screen (Any doubts search on Youtube how to follow that) and at final step on rooting the phone will restart and maybe the computer recognized a MT65xx Driver installation but that isn't need to root... than he will show Rooted status on vRoot program
7- after all that you allow file copy to get acess to internal storage from phone to put the Folder MRW from WolfDroid Script.zip on phone and follow this steps from this official video from WolfDroid (Just to remember, is need to install a Terminal emulator app from google market to do this step)
8 - after replace the chinese SU to SuperSU you go to google market and update the SuperSU to lasted update and execute SuperSU to update the binaries and reboot
9 - Finish the process ;D
Click to expand...
Click to collapse

DvDwx. said:
- FAQ:
1 - Question: Modificated Blu Vivo Air ADB Driver installation
Answer: you can try follow this steps from original Driver developer on Brazilian Forum (Just to remember.. the driver download already have all customizations about he describe on photos... LINK) or just follow this photos/steps on above
Go to Device Manager and right Click to select Update driver selected
Click on Browse My Computer for driver software
Click Let me pick...
Click Show ALL...
Have Disk...
Search...
Go to located Unzip Folder and select Android_WinUSB.inf ... than click Open(or two click on .inf) and than OK
Select the Android Composite ADB Interface and click NEXT and Accept if he ask if you want install this driver anyway
Now you Installed your ADB Driver working :highfive:
Have any question, Commit above... i will try answer you and maybe i can put here on FAQ to everyone :highfive:
Click to expand...
Click to collapse
I am having issues getting a custom recovery installed on this phone . I tried an app that allowed to choosed twrp or cwm and it installs succesfully but when i reboot recovery it still bots to stock. Being there is no option in dev options to unlock oem bootloader I belive this is causing the issue. Any ideas or links . Thanks in advanced

Links are invalid. Can some please post new links?

Yes

does anybody have the "ADB Driver Modificated to Vivo Air"?
link is dead. thanks!

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.