[Moto G6 Plus] 2: Returning to Stock - Moto G6 Plus Guides, News, & Discussion

THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
2: Returning to Stock
If for any reason your phone is no longer functioning properly such as a bootloop (the phone is restarting itself over and over), "Can't Load Android System," "Startup Failed", or any such error you can fix this by flashing the stock firmware using fastboot.
I have taken stock firmware version OPW27.113-89 and packaged it with a few extras. XDA Member luiz_neto has provided a modified logo.bin that removes the unlocked bootloader warning during boot. A special thanks to XDA Member lohanbarth for providing the stock firmware. I have included the fastboot file for Windows, Linux and Mac users. Windows users can run the .bat file to execute all the necessary commands. For Linux and Mac users, I have included a bash script. You will need access to a PC and connect your phone via a USB cable.
*Downloads:
Modified Stock Firmware OPW27.113-89: (Download)
MD5: 3a1d984a8a3d0c57fb21931a8004eb27
Instructions:
*On your phone:
2A. With the phone powered off(even if for just a moment between the phone rebooting) hold the Power button and the Volume Down(Vol -) at the same time. You should boot into what is called the bootloader. It should display information on the screen and state "AP Fastboot Flash Mode" in orange lettering.
*On your PC:
2B: Extract the firmware which is in tar.xz container/file extension. Windows user probably need to use Winrar, 7Zip or PeaZip to extract the file.
2C: Using Windows Explorer, navigate to the folder EVERT_OPW27.113-89_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml and click on it to open it.
2D: Hold the Shift Key on your Keyboard. While holding Shift, Right Click in the window(not on the file). Depending on your windows version you should see either "Open PowerShell Window here" or "Open Command Window here." Select which ever one applies.
2E: You will see a black and white screen or a blue and white screen. The steps are the same no matter which screen you see. Simply type(or copy and paste) the following command:
Windows:
Code:
flash_rom.bat
For Linux and Mac you need to make the script file executable. It will make the fastboot binary executable for you. From a terminal run these 2 commands one at a time:
Linux:
Code:
chmod a+x flash_rom.sh
./flash_rom.sh
Mac:
Code:
chmod a+x flash_rom_mac.sh
./flash_rom_mac.sh
Your phone should reboot on it's own. If for some reason it doesn't try tapping the enter key on your keyboard or use the volume keys to make sure “Start” is selected on the right side of the phone and pres the power key on the phone. It should successfully boot the stock firmware.

Xplorer4x4 Hello good afternoon is on is corrupted When it unzips it says that header is corrupted! @Xplorer4x4

carlosgeraldo said:
Xplorer4x4 Hello good afternoon is on is corrupted When it unzips it says that header is corrupted! @Xplorer4x4
Click to expand...
Click to collapse
Did you try to download the package again?

Does anyone know whether It's possible to remove the "Your device has loaded a different operating system." after flashing stock rom through fastboot and relocking bootloader? I was looking to sell the phone...

Mara-X said:
Does anyone know whether It's possible to remove the "Your device has loaded a different operating system." after flashing stock rom through fastboot and relocking bootloader? I was looking to sell the phone...
Click to expand...
Click to collapse
Flash the stock firmware in my op.
Sent from my Moto G6 Plus using XDA Labs

Xplorer4x4 said:
Flash the stock firmware in my op.
Sent from my Moto G6 Plus using XDA Labs
Click to expand...
Click to collapse
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"

Mara-X said:
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Click to expand...
Click to collapse
I have never relocked my bootloader so I can't say for sure but this sounds out of the ordinary. Did it boot fine with an unlocked bootloader?
Sent from my Phh-Treble vanilla using Tapatalk

weazie said:
Did you try to download the package again?
Click to expand...
Click to collapse
I found the error: it was in my PC I started a program to fix the registry and after that unzipped the file normally!

Mara-X said:
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Click to expand...
Click to collapse
Hi! have you succeed with your issue flashing this stock firmware ?
Does this stock firmware helps to remove warnings "This device has loaded a different operating system", and "Verity mode disabled" during boot?
And the worst thing is the message "System integrity compromized" and hens - GooglePay disabled and no software updates., when bootloader is re-locked?

MrMatnenko said:
Hi! have you succeed with your issue flashing this stock firmware ?
Does this stock firmware helps to remove warnings "This device has loaded a different operating system", and "Verity mode disabled" during boot?
And the worst thing is the message "System integrity compromized" and hens - GooglePay disabled and no software updates., when bootloader is re-locked?
Click to expand...
Click to collapse
Same problem here. I hate this messages

<bootloader> flash permission denied
friends, any command I give appeared this, someone knows how to solve?

Failed anything I've tried... Can you help @Xplorer4x4 ?

andreym_costa said:
Failed anything I've tried... Can you help @Xplorer4x4 ?
Click to expand...
Click to collapse
Shows the message "Failed Remote ' ' and "Flash permission denied"

andreym_costa said:
Shows the message "Failed Remote ' ' and "Flash permission denied"
Click to expand...
Click to collapse
You MUST provide MORE information! Screenshots, a detailed error description and not only a piece of your error.

WoKoschekk said:
You MUST provide MORE information! Screenshots, a detailed error description and not only a piece of your error.
Click to expand...
Click to collapse
I'm trying again... And now seeing this, can you help?
{
"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"
}

andreym_costa said:
I'm trying again... And now seeing this, can you help?
Click to expand...
Click to collapse
Please follow my guide below. That would be much easier I think, because it seems you are doing several things wrong.
1. download ADB/Fastboot tools from here and extract the downloaded zip to 'C:\' to create the path 'C:\platform-tools'
2. download your current firmware build here.
You use 116-16-22 but the latest build is 11-16-29 for RETBR.
3. extract the firmware.zip to 'C:\platform-tools'
Watch out to extract only single files and images to that path and do not create a subfolder => see screenshot attached
4. extract attached flashfile.zip to 'C:\platform-tools'
5. open 'C:\platform-tools' in Explorer and type 'cmd' in the address bar and hit 'Enter'
=> opens a new cmd window
6. boot your Moto into fastboot mode, connect it to your PC and run 'fastboot devices'
=> output: <SERIAL-NO> fastboot
7. execute 'flashfile.bat' and start flashing

WoKoschekk said:
Please follow my guide below. That would be much easier I think, because it seems you are doing several things wrong.
1. download ADB/Fastboot tools from here and extract the downloaded zip to 'C:\' to create the path 'C:\platform-tools'
2. download your current firmware build here.
You use 116-16-22 but the latest build is 11-16-29 for RETBR.
3. extract the firmware.zip to 'C:\platform-tools'
Watch out to extract only single files and images to that path and do not create a subfolder => see screenshot attached
4. extract attached flashfile.zip to 'C:\platform-tools'
5. open 'C:\platform-tools' in Explorer and type 'cmd' in the address bar and hit 'Enter'
=> opens a new cmd window
View attachment 5654883
6. boot your Moto into fastboot mode, connect it to your PC and run 'fastboot devices'
=> output: <SERIAL-NO> fastboot
7. execute 'flashfile.bat' and start flashing
Click to expand...
Click to collapse
I tried again and now these errors occur. I thought it might be a locked bootloader, but apparently everything is ok, at startup it has an unlocked bootloader warning. And really thank you to helping me.

andreym_costa said:
I tried again and now these errors occur. I thought it might be a locked bootloader, but apparently everything is ok, at startup it has an unlocked bootloader warning. And really thank you to helping me.
Click to expand...
Click to collapse
No, your bootloader isn't unlocked. The OEM-Unlock toggle would be inactive (greyed out) in case of an unlocked bootloader.

Related

Remove Unlocked Bootloader Message Moto G5S Plus, G5S

Although Motorola has made it facile to unlock the bootloader on its recent or upcoming devices, the manufacturer still warns about these activities. The unlock bootloader method is listed on Motorola’s official site, and has made the process easy and convenient for users and developers. However, once you unlock the bootloader, a message will be displayed warning about the risks associated with it. Although its won’t affect the functioning of your device, users find it annoying at times as it is displayed every time you reboot.
{
"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"
}
This logo can be used to replace the warning message on any new generation Motorola device. Here, as you may have already setup the adb and fastboot while unlocking the bootloader, you can use the same setup to remove the warning. You can also flash the zip file through a custom recovery, if you have TWRP or CWM on your Motorola device.
Prerequisites
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from download section (unzip it).
Install Motorola USB Drivers on your computer.
Open Settings> Developer options and enable USB Debugging on your device.
Go to Developer options and enable oem unlock.
Remove Unlocked Bootloader Warning
Make sure you have setup ADB and fastboot on your PC.
Download the logo file and transfer the logo.bin file to some place you can track it easily. Its better if you use the folder where you setup the fastboot.
Power off your device and keep it unplugged from your PC.
Boot into bootloader. To do so, press and hold volume down and the power button for 5-6 seconds.
You will see the bootloader screen. Now plug in your device to the PC.
Navigate to the location of the logo.bin file. While the folder with the logo file is open, hold shift on keyboard and right-click on an empty space and select “Open command window here” option to launch a cmd window.
Now type the following in the command prompt to get a code
fastboot flash logo logo.bin​
Now type the following in command prompt to reboot.
fastboot reboot​
Once you reboot, you will no longer see the bootloader warning as it has been replaced with the Motorola logo. You can choose a custom image you like but be sure it is in .bin extension.
Download Section
Minimal ADB size: 628.5KB
Logo.bin size: 1.26MB
Original Logo: Logo.bin size: 1.3MB
Note: Original Logo has blue background. So it shows a small white N/A text.
Extra Guides:
[ROOT][TWRP][BOOTLOADER UNLOCK] Moto G5s Plus [sanders]
Relock Bootloader Moto G5s Plus
Flash official firmware Moto G5s Plus [sanders]
Appreciate my work?
It is a very hard task to work over mobile data. Please consider making a donation If this guide helped you.
Bank Transfer: Name- Shubham Mishra, A/C no. 8756149523, IFSC code. AIRP0000001
Paypal https://paypal.me/shubhmishra
Awesome mate!!!worked like a charm! got rid of the stupid message! Cheers
Nice
diegomartinezlovey said:
Nice
Click to expand...
Click to collapse
its not the same logo came with Moto G5s Plus
may someone create a logo like it
thanks in advance
yograjfire18 said:
its not the same logo came with Moto G5s Plus
may someone create a logo like it
View attachment 4282762
thanks in advance
Click to expand...
Click to collapse
Yes I can create. I need logo.bin file from official firmware. I dont want to download 1.6 GB just for logo. I have only jio
shu006 said:
Yes I can create. I need logo.bin file from official firmware. I dont want to download 1.6 GB just for logo. I have only jio
Click to expand...
Click to collapse
may u send the original firmware download link, i will send download that and then attach the logo.bin
yograjfire18 said:
may u send the original firmware download link, i will send download that and then attach the logo.bin
Click to expand...
Click to collapse
drive google com/open?id=0B9VEaFoqTCkLX2JUd0lVdzZLUUk
shu006 said:
drive google com/open?id=0B9VEaFoqTCkLX2JUd0lVdzZLUUk
Click to expand...
Click to collapse
Hello Bro, I have attached the logo.bin(zipped) and the logo image
Thanx in advance again
View attachment Logo.zip
yograjfire18 said:
Hello Bro, I have attached the logo.bin(zipped) and the logo image
Thanx in advance again
View attachment 4283607
View attachment 4283608
Click to expand...
Click to collapse
http://hostracon.com/index.php?a=download&q=108
Done. But it is showing a small N/A over red circle. That's why it was white before.
Wow, that was fast.
shu006 said:
Yes I can create. I need logo.bin file from official firmware. I dont want to download 1.6 GB just for logo. I have only jio
Click to expand...
Click to collapse
hi, what program did u use? it seems that logobuilder was not for this...
---------- Post added at 01:56 AM ---------- Previous post was at 01:50 AM ----------
shu006 said:
Yes I can create. I need logo.bin file from official firmware. I dont want to download 1.6 GB just for logo. I have only jio
Click to expand...
Click to collapse
hi... what program did u use for this? logo builder is not i think...
Can someone create with darker color like black or grey? The white and blue are extremely bright when booting up. Thanks
THERAJ12 said:
Can someone create with darker color like black or grey? The white and blue are extremely bright when booting up. Thanks
Click to expand...
Click to collapse
More logo's and somewhat of a how to make your own.
https://forum.xda-developers.com/showthread.php?p=74240673
Sent by way of magic
Hey from where i can find Motorola usb drivers
It says in the instructions you can flash a zip from custom recovery? Can't find a zip file to download in the original post though. Is it as simple as zipping the logo.bin file and then flashing from TWRP?
shu006 said:
Although Motorola has made it facile to unlock the bootloader on its recent or upcoming devices, the manufacturer still warns about these activities. The unlock bootloader method is listed on Motorola’s official site, and has made the process easy and convenient for users and developers. However, once you unlock the bootloader, a message will be displayed warning about the risks associated with it. Although its won’t affect the functioning of your device, users find it annoying at times as it is displayed every time you reboot.
This logo can be used to replace the warning message on any new generation Motorola device. Here, as you may have already setup the adb and fastboot while unlocking the bootloader, you can use the same setup to remove the warning. You can also flash the zip file through a custom recovery, if you have TWRP or CWM on your Motorola device.
Prerequisites
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from download section (unzip it).
Open Settings> Developer options and enable USB Debugging on your device.
Make sure you have setup ADB and fastboot on your PC.
Power off your device and keep it unplugged from your PC.
You will see the bootloader screen. Now plug in your device to the PC.
Now type the following in the command prompt to get a code
fastboot flash logo logo.bin
Now type the following in command prompt to reboot.
fastboot reboot
Once you reboot, you will no longer see the bootloader warning as it has been replaced with the Motorola logo. You can choose a custom image you like but be sure it is in .bin extension.
Download Section
Minimal ADB size: 628.5KB
Original Logo: Logo.bin size: 1.3MB
Note: Original Logo has blue background. So it shows a small white N/A text.
Extra Guides:
[ROOT][TWRP][BOOTLOADER UNLOCK] Moto G5s Plus [sanders]
Relock Bootloader Moto G5s Plus
Flash official firmware Moto G5s Plus [sanders]
Appreciate my work?
It is a very hard task to work over mobile data. Please consider making a donation If this guide helped you.
Bank Transfer: Name- Shubham Mishra, A/C no. 8756149523, IFSC code. AIRP0000001
Paypalhttps://paypal.me/shubhmishra
Click to expand...
Click to collapse
Please help me. My phone is not connect on PC. "Waiting Device" on mode fastboot. I need tutorial to connect my phone on my PC, i want to flash logo.bin. moto g5s+ XT1805
Iaanbandol66 said:
Please help me. My phone is not connect on PC. "Waiting Device" on mode fastboot. I need tutorial to connect my phone on my PC, i want to flash logo.bin. moto g5s+ XT1805
Click to expand...
Click to collapse
Seems like PC is not detecting device.... Download motorola device manager.... Install it on pc and then try to connect (hope usb debugging is already enabled)....
aadi50 said:
Seems like PC is not detecting device.... Download motorola device manager.... Install it on pc and then try to connect (hope usb debugging is already enabled)....
Click to expand...
Click to collapse
I have installed motorola device manager and I have repeated it many times and always failed to connect. I have actived usb debungging
Please help me!
Iaanbandol66 said:
I have installed motorola device manager and I have repeated it many times and always failed to connect. I have actived usb debungging
Please help me!
Click to expand...
Click to collapse
Uninstall any and all drivers for any and all phones/devices, reboot pc, install again
Phazmos said:
Uninstall any and all drivers for any and all phones/devices, reboot pc, install again
Click to expand...
Click to collapse
OK, thanks for tutorial

TecLast P10 root?

Hey everyone,
I am looking for a root method for my Teclast P10 running Android 7.1.2
Can anyone help me?
Thank you
Im interested to root my teclast also!
Is it possible to use some other device custom recovery to root which have same RK3368 chipset?
This model nothing rom, twrp.
I hope.
techtechmoe said:
Hey everyone,
I am looking for a root method for my Teclast P10 running Android 7.1.2
Can anyone help me?
Thank you
Click to expand...
Click to collapse
Did you get to root your tablet?
I am looking for some help too.
could you root it ? I don't find any info to do it !!
root Teclast P10
Getting root access using Magisk:
1. Flash by AndroidTool patched boot.img from the attached archive (boot.img from firmvare 2.04).
2. Install MagiskManager-v5.6.2.apk from archive.
Pay attention, that boot.img patched by MagiskManager exactly version 5.6.2. and when update Manager procedure is required to produce again (I own this tablet and will try to do it in a timely manner).
It's advisable to rename/delete the binary "su" in the system/xbin folder.
ViAlexSt said:
Getting root access using Magisk:
1. Flash by AndroidTool patched boot.img from the attached archive (boot.img from firmvare 2.04).
2. Install MagiskManager-v5.6.2.apk from archive.
Pay attention, that boot.img patched by MagiskManager exactly version 5.6.2. and when update Manager procedure is required to produce again (I own this tablet and will try to do it in a timely manner).
Click to expand...
Click to collapse
Hurray! Thanks! :victory:
Could you please give instruction and settings how to flash boot.img with AndroidTool?
Makildo said:
Could you please give instruction and settings how to flash boot.img with AndroidTool?
Click to expand...
Click to collapse
1. Install the drivers.
2. Run AndroidTool, choose the boot.img (see the picture).
3. Turn off tablet. Hold down the volume key"+", connect tablet to PC; device should be determined and the message 'Found One LOADER Device' will appear in the program (see the picture).
4. Start the process by clicking "Run".
{
"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"
}
ViAlexSt said:
1. Install the drivers.
2. Run AndroidTool, choose the boot.img (see the picture).
3. Turn off tablet. Hold down the volume key"+", connect tablet to PC; device should be determined and the message 'Found One LOADER Device' will appear in the program (see the picture).
4. Start the process by clicking "Run".
Click to expand...
Click to collapse
Thanks again! :highfive:
Can't open full picture some reason
But in Android Tool is this default address 0x00000000 correct for 7#- boot image?
Makildo said:
But in Android Tool is this default address 0x00000000 correct for 7#- boot image?
Click to expand...
Click to collapse
No. Addresses of blocks of different - see the picture, I fixed it. I don't use the cable that comes with the tablet - take another, tested.
ViAlexSt said:
No. Addresses of blocks of different - see the picture, I fixed it. I don't use the cable that comes with the tablet - take another, tested.
Click to expand...
Click to collapse
This works perfectly! :good:
After boot flash move only app to sd-card/tab and install that.
Does not.work for me.i tried
ERROR
ViAlexSt said:
1. Install the drivers.
2. Run AndroidTool, choose the boot.img (see the picture).
3. Turn off tablet. Hold down the volume key"+", connect tablet to PC; device should be determined and the message 'Found One LOADER Device' will appear in the program (see the picture).
4. Start the process by clicking "Run".
I always get this message.
BOOT IS NOT EXISTED, STOP RUNNING!
Click to expand...
Click to collapse
marcelalabres said:
I always get this message.
BOOT IS NOT EXISTED, STOP RUNNING!
Click to expand...
Click to collapse
Try to run AndroidTool as " Administrator"
Same thing unfortunately
pls, uplod pic in another pic hust
bilausdaniel said:
Same thing unfortunately
Click to expand...
Click to collapse
pls, uplod pic in another pic hust
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
ViAlexSt said:
1. Install the drivers.
2. Run AndroidTool, choose the boot.img (see the picture).
3. Turn off tablet. Hold down the volume key"+", connect tablet to PC; device should be determined and the message 'Found One LOADER Device' will appear in the program (see the picture).
4. Start the process by clicking "Run".
Click to expand...
Click to collapse
pls, uplod pic in another pic hust
Please I need help guys.
I got stuck at stage 4. I saw the message "Found one loader device" yet when I click Run, instead of the running the program, I saw another message "boot is not existed, stop running!".
Pls what is the problem? Why do I keep getting this message?
By the way, I tried to rename/delete 'Su' file system/xbin but was unsuccessful. I saw the message "'task failed', 'su cannot be deleted'". I have tried to root the tablet before with kingroot app but was unsuccessful. Worse still the kingroot refused to be uninstalled, masquerading itself as a system app. Now my tablet WiFi is misbehaving, refuses to turn on.
So I really need to root the tablet to uninstall the malicious kingroot app.
Any help will be appreciated, thanks
ViAlexSt said:
Try to run AndroidTool as " Administrator"
Click to expand...
Click to collapse
Thank you! I found the problem! Tablet rooted perfectly!
---------- Post added at 11:31 AM ---------- Previous post was at 11:25 AM ----------
When you run Android Tools, you have to click on the last empty square in the boot line, and choose the boot.img that you downloaded. Then, click run.
---------- Post added at 11:31 AM ---------- Previous post was at 11:31 AM ----------
nwaogu said:
Please I need help guys.
I got stuck at stage 4. I saw the message "Found one loader device" yet when I click Run, instead of the running the program, I saw another message "boot is not existed, stop running!".
Pls what is the problem? Why do I keep getting this message?
By the way, I tried to rename/delete 'Su' file system/xbin but was unsuccessful. I saw the message "'task failed', 'su cannot be deleted'". I have tried to root the tablet before with kingroot app but was unsuccessful. Worse still the kingroot refused to be uninstalled, masquerading itself as a system app. Now my tablet WiFi is misbehaving, refuses to turn on.
So I really need to root the tablet to uninstall the malicious kingroot app.
Any help will be appreciated, thanks
Click to expand...
Click to collapse
When you run Android Tools, you have to click on the last empty square in the boot line, and choose the boot.img that you downloaded. Then, click run.
Can't get it to work. If i hold down the volume key "+" and connect tablet to PC (Win10), device is not recognised. (drivers are installed)
The tablet shows the Android Recovery:
Teclast/rk3368H_64/rk3368H_64
7.1.2/NHG47K/fb11231759
When i select 'reboot to bootloader' from the Android Recovery menu, AndroidTools shows 'Found One ADB Device'
But when i click on run, the message 'Match device type failed, stop running!' appears
Any hints?
I just tried it with a fresh Win7 installation in a VM, works now!

Route to ROOT an unkonw AndroidTV Devices Technicolor DWI259S/UIW4020ETI (Sapphire)

Hi guys, I'm here to learn something about Android Security System.
I have this Sapphire TV BOX
model: DWI259S / UIW4020ETI / UIW4020ETI2 (Sapphire)
SoC: Broadcom BCM7271
The goal of this post is to understand how I can gain root access on this device
I know how to turn it in recovery mode .
if you are interested you can read this Reddit post from ams_sharif
"You can boot to recovery by switching the unit off ( the black button in the back), then while holding the power button (the one on the side, next to the pair button) turn the set top box on until the recovery shows up."
This is what I see.
{
"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 tried to flash an update.zip in order to see if I can execute command through any script, but the verification of the signature fails.
I tried to click on "Apply update from USB" (that is adb sideload) , but connecting the tv box on the pc nothing happen, no device found neither with "adb devices"
I tried also to click on "Reboot to bootloader" but "fastboot devices" command return nod devices connected.
My idea was to read the recovery image from fastboot extract it and try to compile my own TWRP
Do you have any suggestions to guide me in the right way?
@element14
When you enter
Code:
adb devices
and don't see an entry listed under the “List of devices” section, then your device isn't connected to PC.
Same is case when you enter
Code:
fastboot devices
Recovery option "Apply update from USB" isn't equal to "adb sideload". This option assumes the Update.Zip you want to flash is located on USB-device connected with your TV box.
With regards to rooting your TV box you can try to flash Chainfire's SuperSu Pro.
BTW: TWRP isn't a recovery image you compile in order to flash, it's merely a touch-enabled replacement for device's Stock Recovery menu as shown by you
Example screenshot:
jwoegerbauer said:
@element14
When you enter
Code:
adb devices
and don't see an entry listed under the “List of devices” section, then your device isn't connected to PC.
Same is case when you enter
Code:
fastboot devices
Recovery option "Apply update from USB" isn't equal to "adb sideload". This option assumes the Update.Zip you want to flash is located on USB-device connected with your TV box.
Click to expand...
Click to collapse
I tried to flash a custom script that use the
Code:
u_print()
function , but the signature verification fails i get an
Code:
errorr:21
jwoegerbauer said:
With regards to rooting your TV box you can try to flash Chainfire's SuperSu Pro[/url].
Click to expand...
Click to collapse
Are you sure that I can flash an unsigned zip like superSu , with a stock recovery and locked bootloader ?
jwoegerbauer said:
BTW: TWRP isn't a recovery image you compile in order to flash, it's merely a touch-enabled replacement for device's Stock Recovery menu as shown by you
Click to expand...
Click to collapse
The TWRP is an open source project , all the source code is avaiable. But to have it works , you need the original kernel .
I tought , If I can unlock the bootloader I can read the image of the recvoery.img and from it extarct the kernel
Thanks for your answer.
@ element14
did you manage to make the device usebale?
Hello, i am also interested to reset\flash this device but I couldn't find any useful guide, did you manage to root it or flash it, I want to use it as android STB.
As long as you can establish an USB-connection ( read: ADB connection ) then you can root any device's Android OS, otherwise NOT.
Any updates on this topic? It would be great to know if someone was able to root it.
If this is the etisalat version of this box I have gotten APKs to work on it.
xilogofficial said:
If this is the etisalat version of this box I have gotten APKs to work on it.
Click to expand...
Click to collapse
What apk exactly?what you can do with this apk? And how you installed?
element14 said:
What apk exactly?what you can do with this apk? And how you installed?
Click to expand...
Click to collapse
I think it lets you install any APK on the device. Check https://emiratestel.github.io/website
There is only one port. Is there any other way? And how can i play videos from usb
xilogofficial said:
I think it lets you install any APK on the device. My method:
Going to apps list:
- insert usb
- click browse
- go up to internal storage, press ok, click Apps
part 1
- go to apps list, keep usb inserted
- scroll to Files, click it, click open
- if it opens skip to part 2
- else it will crash and show the first time boot
- go to apps list again while keeping usb inserted
- open files again
part 2
- connect a mouse to other USB port, navigate into the USB and into where you placed your APKs
- double click the apk to install it
- on first time install, it will show an error about unknown sources
- click settings on the prompt
- enable all sources shown
- continue installing the app
Click to expand...
Click to collapse
There is only one usb port. Is there any other way? And how can i play videos from usb
there's another on the bottom, or use a USB hub.
you can't play videos from USB without installing third party apps.
xilogofficial said:
If this is the etisalat version of this box I have gotten APKs to work on it.
Click to expand...
Click to collapse
Good Day! Appreciate your support . Dear Exactly Etisalat TV box model: DWI259S, but it is locked on Etisalat home page with their logo as I don't have Etisalat subscription any more, in that situation how possible to browse an APK file as you said in below steps? 2nd thing there is no standard Firmware available by Manufacturer (Technicolor), Please make a video or at least solve with help of photos and help us close this topic. Till date solution is not yet provided, Please help, Thanks and appreciate your support
.
element14 said:
Hi guys, I'm here to learn something about Android Security System.
I have this Sapphire TV BOX
model: DWI259S / UIW4020ETI / UIW4020ETI2 (Sapphire)
SoC: Broadcom BCM7271
The goal of this post is to understand how I can gain root access on this device
I know how to turn it in recovery mode .
if you are interested you can read this Reddit post from ams_sharif
"You can boot to recovery by switching the unit off ( the black button in the back), then while holding the power button (the one on the side, next to the pair button) turn the set top box on until the recovery shows up."
This is what I see.
I tried to flash an update.zip in order to see if I can execute command through any script, but the verification of the signature fails.
I tried to click on "Apply update from USB" (that is adb sideload) , but connecting the tv box on the pc nothing happen, no device found neither with "adb devices"
I tried also to click on "Reboot to bootloader" but "fastboot devices" command return nod devices connected.
My idea was to read the recovery image from fastboot extract it and try to compile my own TWRP
Do you have any suggestions to guide me in the right way?
Click to expand...
Click to collapse
Any Luck dear, Please advise as I want the same solution and receive same error 21.
engr.sys said:
Any Luck dear, Please advise as I want the same solution and receive same error 21.
Click to expand...
Click to collapse
Kindly Join our Discord Server Link :https://discord.gg/sbFnauNTWy
I can help u there
Hi
Can you please share the APK please ?
any update on this? did anyone managed to finally root this device or least sideload and apk?
b1acktiger said:
Hi
Can you please share the APK please ?
Click to expand...
Click to collapse
PM Me
Can you please share the APK please ?

YT-X705F - Rooting Guide (Android 10.0)

Solution below.
For those with the same device, I was able to successfully root + pass safetynet, without TWRP or custom recovery. Since this device isn't yet on the forums I thought I should share my findings.
At the time of rooting, I was currently updated to the newest version available (10) and did this through the regular OTA updates.
Preparations
1. Download Magisk Manager Beta from https://magiskmanager.com/magisk-beta/
2. Download the stock firmware for your tablet from https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
3. Download kdrag0n's SafetyNet Fix from: https://github.com/kdrag0n/safetynet-fix/releases
Edit: looks like I missed a step, thanks for the feedback! Point 4 has been corrected to include instructions on how to unlock the bootloader specifically.
4. Unlock your bootloader, instructions on how to enable USB debugging which is needed, can be found here: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html, from there you can open your command prompt, navigate to the directory where you have your fastboot and ADB stored, and type "adb devices" to confirm your device is found (a serial number will display on success) - next type "adb reboot bootloader" to force your tablet to restart into it, finally type "fastboot oem unlock-go" to unlock the bootloader. This voids your warranty.
-- end of edit.
5. Enable USB debugging through developer options (go to settings->about->find build # and tap a handful of times until it says you are a developer.
6. Plug the tablet into your PC, and set the default option to Charge only, or go to file transfer mode and enable USB debugging over file transfer.
Steps
1. Unzip the firmware, there should be a folder called Maincode, in it contains "boot.img" as well as adb/fastboot.
2. Copy the boot.img and Magisk apk to the tablet.
3. Install Magisk
4. Tap on "Install" or "Update" beside Magisk in the app and follow the prompts.
5. You will be asked to select a file, select the boot.img you copied earlier.
6. This will generate a file (it will tell you the path) of a patched boot image.
7. Reboot, and copy the patched boot image to the "Maincode" folder from the tablet.
8. In command prompt, type adb devices and make sure your serial number is shown. If not, review the preparations.
9. Type adb reboot bootloader and you'll see a cute little Tux (penguin)
10. Type fastboot devices and ensure your device is shown, if not then it could be bad drivers on your PC or a crappy USB cable. Check device manager on your computer and make sure you see Lenovo ADB. You may have to force it to install it, or you may see a yellow exclaimation mark - right click on the device and force it to install the Lenovo Bootloader option.
11. Next, in the "Maincode" folder where you put the patched image, rename the old "boot.img" to "stock_boot.img" and the patched version to "boot.img"
12. Back in the command prompt, type fastboot flash boot boot.img
13. Reboot by typing fastboot reboot.
Magisk should now be installed, and your tablet should be rooted. Next, you'll want to go into Magisk and do the following:
Steps:
1. Click on the modules button (bottom of the screen, far right option) and at the top you're given an option to install from storage.
2. Navigate to the SafetyNet Fix zip file and select it, then proceed.
3. You will be given the option to reboot - do this. The first time it may go into recovery, but rebooting brings you back to the home screen.
4. Go back to Magisk, click on the gear at the top right - there is an option to hide Magisk from the system, do this and name it whatever you'd like (just not Magisk) - wait a moment, as the app will restart after it installs.
You can check to make sure you pass SafetyNet in the Magisk (now renamed) app, and root status by downloading one of the countless root checking apps on Google Play Store.
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Bobmat34 said:
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Click to expand...
Click to collapse
Thanks for pointing that out! - I've updated my notes above, but if your familiar with fastboot the command is simply "fastboot oem unlock-go", no unlock code needed for these guys. It will wipe your device and void your warranty though, in case you're not already aware.
Cheers!
Thanks for this rooting guide! I was able to root my YT-X705F
Here some comments/hints:
- At first make sure your downloading the right stock firmware. I've tried a different one which results into a boot loop. One way to find out the right version is to start into the recovery mode. In the header you will find the right version. In my case it was YT-X705F_S001130_210508_ROW
- Make sure you have actually unlocked the boot loader. "fastboot flash x y.img" worked, so I didn't recognized that the boot loader was not unlocked. This was reason for "fastboot boot y.img" shows errors "FAILED (status read failed (Too many links))".
- The extracted stock firmware have no "Mainfolder". All files, including boot.img and recovery.img, contained in the root directory of the ZIP file.
- After installing Magisk app (v23.0) it shows me: Installed: N/A, Ramdisk: No, A/B: No, SAR: Yes. According to this Magisk installation guide you have to patch the recovery image instead of the boot.
{
"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"
}
- Patching the recovery image was fine with Magisk. No errors was shown. Please note I used the recovery.img
After this I was able to boot the patched image without flashing it:
After "fastboot boot patched_recovery.img" nothing happens. The tablet keeps showing me the Linux Tux image. I have to disconnect the USB cable and then I booted into system.
*Upd. never mind, I download the official rom file from lenovo\
Crap. I patched the boot image with Magisk, and by the time I flashed it - the system got updated from S001133 to S001135, and I'm getting a bootloop. Can someone maybe upload original boot img from S001135?
Or what else can I do? the update isn't on the mirror server yet https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
Rooting was successful! Thanks for the guide. Since I cannot find any section in the forum for the YT-x705 tablet, I thought I can have a follow up question in here. The reason I rooted was because alexa app keeps getting removed after each reboot. I rooted as I wanted to convert it into a system app.
So far, I've been unsuccessful . I have tried with the systemizer module and titanium backup. Anyone have any idea how we can retain alexa app after a reboot? Interestingly enough, titanium backup shows alexa as frozen after I install alexa from playstore, despite it appearing in my app launcher. I am unable to unfreeze it. Alexa is then removed after I reboot.
Quick question: What do i do if i don't have a "MainCode" folder, on the tablet or in the extracted folder.
or is that just the folder with the maincode, in it?
Thanks, looks like a good guide!
Jim
you're just going into the zip file from step 2 where the boot.img file is. I just followed all these instructions and got my yoga rooted.
ugh...I don't have a device that I can root for a couple of years... and it feels like I'm a complete noob, now!
when i try to flash the boot image I'm getting: FAILED (remote: Partition flashing is not allowed)
When i run fastboot oem device-info i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Finished. Total time: 0.010s
So i don't think i am unlocked. even after following the steps. I've got Developer options, Debugging is obviously working, OEM Unlocking is toggled on.
I feel like on my phones we had to run an adb or fastboot command, and then the device would reboot and reset it and it would then be unlocked.
Am i missing something?
Thanks again!!
Jim
p.s. and once i get it working, what roms can i flash? any of the "yoga" roms? or do i need to look at something specific like the 3 or 4?
answered my own question!
i had to run: fastboot oem unlock-go
the device rebooted and reset
now i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Now on to the next step!
So anyone know what ROMs i should use and how best to install them, i don't think we have a working TWRP, do we?
... after crash of my booting Android 10 system last stock rom my yt-x705F 210909 can't be rooted anymore!
i use some app and this app ask for busybox .... so crash !!!
i reset tablet by system recovery .
"wipe data/ factory reset"
after restart my tablet is working again.
Bootloader is still open
also develover mode is working USB Debugging etc.
but no rooting alowed by patching root img .. see next
now i try to install stock rom NEW but some error
"apply update from external storage " get error
same is from "Apply update from ADB" abd sideload file.img
are this zip files from this server corrupt? mirros lolinet ?
i use magisk 25.2 i try all option with hook on recovery also vbmeta
patch both boot.img and recovery.img
after patch one of these img device runs into the bootloader , tux start up.
if i patch stock boot.img device booting normal but NO ROOT
also twrp can't no flash only option "fastboot boot twrp.img"
"fastboot boot flash recovery twrp.img" not working
if i use twrp by "fastboot boot twrp.img" zip stockrom makes also error
someone knows about RESCUE and SMART ASSISTENT" LMSA Tool ?
any suggestion
how is this working ?
go on settings > about tablet > push a view times on Hardware-Version
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
looserintheend said:
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
Click to expand...
Click to collapse
Know where can I find this firmware?

How To Guide [EU model] Unlock bootloader of European model

As you may know, at the time of writing it's not possible to unlock the bootloader of the European model. Fortunately there's a workaround. To know how it works, scroll to the end of the post.
First of all, this is only for the European RMX3301, but you can try on any other global model that doesn't allow the unlocking of the bootloader. I'm not talking about temporary errors, but of the infamous This phone model does not support deep testing error message.
Before starting I would like to thank polygraphene for their implementation of the Dirty Pipe vulnerability on Android. Without that, this would not have been possible.
Requirements:​
The phone with a decent charge. Do not attempt this procedure with the phone at 10% and then cry if something goes wrong
A compatible build, read below
A Windows or Linux PC with adb and fastboot drivers installed
Check if your build is compatible:​
Go to Settings -> About device -> Version and check Build number:
If your build is between RMX3301_11_A.14 and RMX3301_11_A.21, go to the procedure below
If your build is lower than RMX3301_11_A.14, or higher than RMX3301_11_A.21, install this OTA package to downgrade (or upgrade) to RMX3301_11_A.14
Procedure:​
Make sure under Developer options you have OEM unlocking and USB debugging enabled
Download and extract the attached gt2pro_eu_unlock_dirtypipe_v0.2.zip file
Open a terminal in the folder of the extracted files
Connect the phone to the PC and select the File transfer option
Run the script:
On Windows, type run.bat and press enter
On Linux, type ./run.sh and press enter
Now the phone is temporarily rooted and the phone model is changed to RMX3301. Do not reboot or you will lose this status.
At this point you can follow the procedure on the official forum to unlock the bootloader of the global model. If you already have the Deeptesting app installed, clear its data to make sure it will update.
Changelog:​v0.2:
Show more info about device for better debug
Show the model at the end to check if it worked
For technical people: how does it work?​The script abuses a vulnerability of the Linux kernel called Dirty Pipe (or CVE-2022-0847). For further details, you can visit the official website. This allows us to gain temporary root and overwrite the ro.product.name property, the only one checked by the Deeptesting app. The vulnerability is present in Android and it has been fixed, at least for the Pixel 6, in the May 2022 security update. On the GT 2 Pro, the vulnerability has been fixed with the Android 13 update, while the latest Android 12 build (RMX3301_11_A.21) is still vulnerable. I have tested the procedure personally up to build RMX3301_11_A.16. If you're on a newer build and it doesn't work, please report it in the comments.
Will it work on device X?​If the following conditions are met:
it is a Realme device;
the kernel version is 5.10.66;
there's a global model with a different ro.product.name that can be unlocked;
then you can edit the startup-root file and replace RMX3301 (near the end) with the ro.product.name of the global model and try if it works. If it doesn't, it could be for a lot of reasons. Unfortunately, I can't help you without physically having the device in hand.
If you have further questions about the procedure, please post them below.
woowww... thanks for you aport
I wonder if we can use this temporary root to do some modifications on system.
criszz said:
I wonder if we can use this temporary root to do some modifications on system.
criszz said:
I wonder if we can use this temporary root to do some modifications on system.
Click to expand...
Click to collapse
Excellent question... for example try modific the build regist
Click to expand...
Click to collapse
Rapper_skull said:
As you may know, at the time of writing it's not possible to unlock the bootloader of the European model. Fortunately there's a workaround. To know how it works, scroll to the end of the post.
First of all, this is only for the European RMX3301, but you can try on any other global model that doesn't allow the unlocking of the bootloader. I'm not talking about temporary errors, but of the infamous This phone model does not support deep testing error message.
Before starting I would like to thankpolygraphene for their implementation of the Dirty Pipe vulnerability on Android. Without that, this would not have been possible.
Requirements:
The phone with a decent charge. Do not attempt this procedure with the phone at 10% and then cry if something goes wrong
A compatible build, read below
A Windows or Linux PC with adb and fastboot drivers installed
Check if your build is compatible:
Go to Settings -> About device -> Version and check Build number:
If your build is RMX3301_11_A.14, RMX3301_11_A.15 or RMX3301_11_A.16, go to the procedure below
If your build is lower than RMX3301_11_A.14, or higher than RMX3301_11_A.16, install this OTA package to downgrade (or upgrade) to RMX3301_11_A.14
Procedure:
Make sure under Developer options you have OEM unlocking and USB debugging enabled
Download and extract the attached gt2pro_eu_unlock_dirtypipe.zip file
Open a terminal in the folder of the extracted files
Connect the phone to the PC and select the File transfer option
Run the script:
On Windows, type run.bat and press enter
On Linux, type ./run.sh and press enter
Now the phone is temporarily rooted and the phone model is changed to RMX3301. Do not reboot or you will lose this status.
At this point you can follow the procedure on the official forum to unlock the bootloader of the global model. If you already have the Deeptesting app installed, clear its data to make sure it will update.
For technical people: how does it work?
The script abuses a vulnerability of the Linux kernel called Dirty Pipe (or CVE-2022-0847). For further details, you can visit the official website. This allows us to gain temporary root and overwrite the ro.product.name property, the only one checked by the Deeptesting app. The vulnerability is present in Android and it has been fixed, at least for the Pixel 6, in the may 2022 security update. At the time of writing, the latest build for the GT2 Pro is RMX3301_11_A.16, and it's still vulnerable.
If you have further questions about the procedure, please post them below.
Click to expand...
Click to collapse
When you try the procedure... delete al date of phone? whe finish---- type run.bat and press enter ---- erase all?
criszz said:
I wonder if we can use this temporary root to do some modifications on system.
Click to expand...
Click to collapse
Theoretically you can do everything you can do on a rooted phone (Magisk, but without modules and Zygisk). In practice I never got Magisk to work properly, so I just limited myself to change the property. My goal was to unlock the bootloader, so I did it and installed Magisk.
manu81cba said:
When you try the procedure... delete al date of phone? whe finish---- type run.bat and press enter ---- erase all?
Click to expand...
Click to collapse
My procedure will not delete any data, but after that you have to follow the official procedure to unlock the bootloader, and that will factory reset your phone.
{
"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 this error... why?
manu81cba said:
View attachment 5634133
I have this error... why?
Click to expand...
Click to collapse
Can you post the output of adb devices?
Rapper_skull said:
Can you post the output of adb devices?
Click to expand...
Click to collapse
You can explain? no understand.. what do you say?
manu81cba said:
You can explain? no understand.. what do you say?
Click to expand...
Click to collapse
In the terminal, where you are, type adb devices and press enter, then post the output.
Rapper_skull said:
In the terminal, where you are, type adb devices and press enter, then post the output.
Click to expand...
Click to collapse
manu81cba said:
View attachment 5634133
I have this error... why?
Click to expand...
Click to collapse
Yes i have same output on A.16 installed.
manu81cba said:
View attachment 5634153
Click to expand...
Click to collapse
I can see that you have two different versions of adb, one inside the platform-tools folder and one installed elsewhere. Please confirm that by running adb version inside platform-tools and then outside.
Rapper_skull said:
In the terminal, where you are, type adb devices and press enter, then post the output.
Click to expand...
Click to collapse
now put all file decripted to plataform adb... and this result... all ok?
manu81cba said:
now put all file decripted to plataform adb... and this result... all ok?
View attachment 5634159
Click to expand...
Click to collapse
Yes. To make sure, run adb getprop ro.product.name and confirm it's RMX3301.
manu81cba said:
now put all file decripted to plataform adb... and this result... all ok?
View attachment 5634159
Click to expand...
Click to collapse
Working now?
Is rooting temporary? i can modific build.pro? or this process is only for change the model propety?
manu81cba said:
Working now?
Is rooting temporary? i can modific build.pro? or this process is only for change the model propety?
Click to expand...
Click to collapse
No, you can't modify any files, since /system is read-only. Even if you manage to do it, you will brick your device since the bootloader is still locked. If you want to unlock your bootloader, follow the official guide I've linked.
Rapper_skull said:
Yes. To make sure, run adb getprop ro.product.name and confirm it's RMX3301.
Click to expand...
Click to collapse
manu81cba said:
View attachment 5634169
Click to expand...
Click to collapse
Sorry, adb shell getprop ro.product.name

Categories

Resources