Database Info

ASUS ZenPad C 7.0 (Z170C - P01Z) - Working Root Method

Forenote: Root has finally been achieved for us on the Asus Zenpad C 7.0! Special shoutout to @InvisiBot (source) and @b0joker (source). Not only that, but also to the Russian 4pda forum where the root process was brought up and discovered (source). All credit lies where it is due.
This topic is not me claiming to have made the root process, but only instead simplifying the process (hopefully) for all you guys to get root up and running on your ZenPad C 7.0. Let's do this!
I am not responsible for any screwed tablets, rekt skrubs, or anything that happens as a result of you following this guide. It worked for me on my Z170C, so there's no reason as to why it probably shouldn't work for you. This guide has been reported to also work with the Z170CG and Z370C tablets, in which case owners of these tablets can attempt this method but with caution. Beware, this method has not been tested by myself and prepare yourself for the event of a brick.
ASUS ZenPad C 7.0 Root Prerequisites
ADB + Fastboot Drivers (can either use Google's, Intel's or ASUS')
Z170C Root img
Patience
Android SDK (and platform tools installed, can be installed through the SDK Manager)
Ensure that the ADB + Fastboot drivers are correctly installed by opening a new command prompt window, and typing the command "cd {this should be the directory to your Android-sdk/platform tools folder - the folder where adb.exe and fastboot.exe are located". Now, type "adb devices". If you see your device in the list with 'unauthorised', ensure that you check your tablet and allow ADB debugging to continue with your computer.
A full backup of everything that you would like to keep (because the device is unrooted, we cannot complete a Titanium Backup or likewise. Instead, ensure that all valuable photos, music, apps are backed up and are kept a note of to reinstall afterwards. We will have to be factory resetting the tablet in order to unlock the bootloader and boot from the root img.
(downloads are below in the attached files)
ASUS ZenPad C 7.0 Root Process
Ensure that ADB Debugging is enabled on your device, and that a full backup of everything that you want to keep has been made.
Connect your Z170C to your computer with ADB Debugging checked, and ensure that the ADB drivers are installed and working as intended.
Download the Z170C root img, and store it on your desktop.
Open a new command prompt window, cd to your Platform tools folder (with adb.exe and fastboot.exe) and run adb devices to ensure that your device is connected.
Once connected successfully...
Code:
adb reboot fastboot
to reboot into fastboot.
Now you are successfully in fastboot, here's the tricky part. Follow the code as exactly given below:
Code:
fastboot oem unlock
fastboot oem unlock confirm
fastboot boot "C:\Users\{your PC user name here}\Desktop\root-z170c_cg.img"
IMPORTANT: The window will request that you follow the code "adb format userdata" and "adb format cache". DO NOT DO THIS. You will risk bricking your tablet (this was the mistake I took when I tried rooting this tablet for the first time, so it's no biggie). If you accidentally follow this and end up bricking your tablet, follow the guidance below.
Allow the tablet to boot up. Give it a few minutes, and you should be at the ASUS tablet setup screen again. Proceed with setting the device up.
Once set up, proceed to the Play Store and install SuperSU (maybe even 'Root Checker' for further confirmation that root is successfully installed on your device). Once SuperSU is installed, be sure to update the root binary when it first prompts you to. At the prompt screen, select 'Normal' installation rather than 'TWRP/CWM'.
When the binary has installed, reboot your device one final time. Welcome to your rooted Z170C!
Endnote
I hope this brief tutorial helped you to gain root onto your ASUS ZenPad C 7.0. It is disappointing that you will have to go through all of this trouble in order to obtain root, but if you follow all of the steps exactly I can guarantee that it will work. And not forgetting, again, all credit stands to where it's due (check top of forum post).
In case of brick...
It happened to me, and it'll probably (not) happen to you. If by any chance you make a mistake and go wrong, fear not.
Firstly, leave fastboot by powering off the device.
Power back on the device, and when you reach the 'ASUS' boot up screen, hold the power + volume down buttons at the same time. Wait roughly 5 seconds.
At the 'recovery menu' screen, use the volume keys to select "Factory reset" and press the power button to select.
Wait a minute or two, and when the process has completed, use the volume keys to scroll back up to the top and reboot your device.
Once you are back inside the ASUS Setup, reboot your device and try again! This time, following the steps... Good luck.
Unbrick process not working for you? Download the stock firmware .zip here, and be sure to boot into recovery mode (power + volume down at boot) and flash the .zip. - I haven't tested this yet so I cannot confirm 100% that this method works, but it should. It could be either an update package or the full stock firmware, but one user has confirmed this method to be working.
UPDATE: A quick update for all you guys on what is currently happening.
v1.0.2 - Minor update, grammar corrections.
v.1.0.1 - Topic created. Will require cleaning up and simplifying sometime.

Success!

With latest updates on my device tried and it works thx for great job

great job AwesomeLewis24.
I complete all steps and the device Z170CG ( p01y) boot into normal mode without any root rights.
After repeating the method, device is hanging on asus boot screen and even factory reset not helped.
Fortunately i was able to flash stock rom and device turned on and now working normally again.
wish me luck, i'm going to try rooting again.

Asus p01z z170c tablet rooting access /custom recovery anyone?
AwesomeLewis24 said:
Forenote: Root has finally been achieved for us on the Asus Zenpad C 7.0! Special shoutout to @InvisiBot (source) and @b0joker (source). Not only that, but also to the Russian 4pda forum where the root process was brought up and discovered (source). All rightful credit can be paid to those.
This topic is not me claiming to have made the root process, but only instead simplifying the process (hopefully) for all y'all guys to get root up and running on your ZenPad C 7.0. Let's do this!
I am not responsible for any screwed tablets, rekt skrubs, or anything that happens as a result of you following this guide. It worked for me on my Z170C, so there's no reason as to why it probably shouldn't work for you.
ASUS ZenPad C 7.0 Root Prerequisites
ADB + Fastboot Drivers (can either use Google's, Intel's or ASUS')
Z170C Root img
Patience
Android SDK (and platform tools installed, can be installed through the SDK Manager)
Ensure that the ADB + Fastboot drivers are correctly installed by opening a new command prompt window, and typing the command "cd {this should be the directory to your Android-sdk/platform tools folder - the folder where adb.exe and fastboot.exe are located". Now, type "adb devices". If you see your device in the list with 'unauthorised', ensure that you check your tablet and allow ADB debugging to continue with your computer.
A full backup of everything that you would like to keep (because the device is unrooted, we cannot complete a Titanium Backup or likewise. Instead, ensure that all valuable photos, music, apps are backed up and are kept a note of to reinstall afterwards. We will have to be factory resetting the tablet in order to unlock the bootloader and boot from the root img.
(downloads are below in the attached files)
ASUS ZenPad C 7.0 Root Process
Ensure that ADB Debugging is enabled on your device, and that a full backup of everything that you want to keep has been made.
Connect your Z170C to your computer with ADB Debugging checked, and ensure that the ADB drivers are installed and working as intended.
Download the Z170C root img, and store it on your desktop.
Open a new command prompt window, cd to your Platform tools folder (with adb.exe and fastboot.exe) and run adb devices to ensure that your device is connected.
Once connected successfully...
Code:
adb reboot fastboot
to reboot into fastboot.
Now you are successfully in fastboot, here's the tricky part. Follow the code as exactly given below:
Code:
fastboot oem unlock
fastboot oem unlock confirm
fastboot boot "C:\Users\{your PC user name here}\Desktop\root-z170c_cg.img"
IMPORTANT: The window will request that you follow the code "adb format userdata" and "adb format cache". DO NOT DO THIS. You will risk bricking your tablet (this was the mistake I took when I tried rooting this tablet for the first time, so it's no biggie). If you accidentally follow this by accident and end up bricking your tablet, follow the guidance below.
Allow the tablet to boot up. Give it a few minutes, and you should be at the ASUS tablet setup screen again. Proceed with setting the device up.
Once set up, proceed to the Play Store and install SuperSU (maybe even 'Root Checker' for further confirmation that root is successfully installed on your device). Once SuperSU is installed, be sure to update the root binary when it first prompts you to. At the prompt screen, select 'Normal' installation rather than 'TWRP/CWM'.
When the binary has installed, reboot your device one final time. Welcome to your rooted Z170C!
Endnote
I hope this brief tutorial helped you to gain root onto your ASUS ZenPad C 7.0. It is disappointing that you will have to go through all of this trouble in order to obtain root, but if you follow all of the steps exactly I can guarantee that it will work. And not forgetting, again, all credit stands to where it's due (check top of forum post).
In case of brick...
It happened to me, and it'll probably (not) happen to you. If by any chance you make a mistake and go wrong, fear not.
Firstly, leave fastboot by powering off the device.
Power back on the device, and when you reach the 'ASUS' boot up screen, hold the power + volume down buttons at the same time. Wait roughly 5 seconds.
At the 'recovery menu' screen, use the volume keys to select "Factory reset" and press the power button to select.
Wait a minute or two, and when the process has completed, use the volume keys to scroll back up to the top and reboot your device.
Once you are back inside the ASUS Setup, reboot your device and try again! This time, following the steps... Good luck.
v.1.0.1 - Topic created. Will require cleaning up and simplifying sometime.
Click to expand...
Click to collapse
Thanks for all your work and research. I must wait till I'm home and try this method out! Has anyone been working on a custom recovery for this!? Thanks again!

hayabusa_gsxr said:
great job AwesomeLewis24.
I complete all steps and the device Z170CG ( p01y) boot into normal mode without any root rights.
After repeating the method, device is hanging on asus boot screen and even factory reset not helped.
Fortunately i was able to flash stock rom and device turned on and now working normally again.
wish me luck, i'm going to try rooting again.
Click to expand...
Click to collapse
Good luck buddy! If you could, do you mind sharing where you got the stock ROM from? This could come in handy sometime...
Also, @totalppl so far there's nothing in terms of custom recoveries or the such for this device. Maybe I'll see if there's any chance of an available TWRP port I can port over from a fellow x86 asus device. Until then, this is as far as we have gotten in terms of dev support.
Sent from my Moto G 2014 LTE using Tapatalk

AwesomeLewis24 said:
Good luck buddy! If you could, do you mind sharing where you got the stock ROM from? This could come in handy sometime...
Also, @totalppl so far there's nothing in terms of custom recoveries or the such for this device. Maybe I'll see if there's any chance of an available TWRP port I can port over from a fellow x86 asus device. Until then, this is as far as we have gotten in terms of dev support.
Sent from my Moto G 2014 LTE using Tapatalk
Click to expand...
Click to collapse
This (as it stands) is much appreciated.....
No need to hurry on the recovery front...
Root (for me at least) is the important bit....being able to use TiBu to get rid of the bloat.....that's my priority.....
http://i.imgur.com/rVnFwJM.jpg

@keithross39
Can confirm for me that the majority of the bloatware has been successfully removed and the tablet runs much cleaner now.
Thanks for the messages guys, but like I said credit is where it stands to the guys who found the root.
Sent from my Moto G 2014 LTE using Tapatalk

http://4pda.ru/forum/lofiversion/index.php?t679135-1600.html
Here is the stock rom.
rom flashed using the official rom(there are 2 roms 1GB and 2GB, i'm using 1GB version,don't know the difference) and boot from sdcard.

@hayabusa_gsxr
Thanks for the link, I've been searching on ends for stock ROMs for this tablet. It's been stressing me out! 4pda has been a good forum to us Zenpad users.
Other than that, maybe I'll link that in the top forum post, just in case worse comes to worse.
Sent from my Moto G 2014 LTE using Tapatalk

hayabusa_gsxr said:
http://4pda.ru/forum/lofiversion/index.php?t679135-1600.html
Here is the stock rom.
rom flashed using the official rom(there are 2 roms 1GB and 2GB, i'm using 1GB version,don't know the difference) and boot from sdcard.
Click to expand...
Click to collapse
Just to confirm.....what is the exact process for flashing these firmwares?
tia.....Keith
http://i.imgur.com/rVnFwJM.jpg

Thank you very much, working 100% in my P01Y.
Please share if you know about custom roms for this tablet.

Having root is amazing, I created a bootloader already:
https://youtu.be/H5eXCwYpRvs

chrisupi007 said:
Having root is amazing, I created a bootloader already:
https://youtu.be/H5eXCwYpRvs
Click to expand...
Click to collapse
Nice work! Awesome to see how we are slowly but steadily finding out and developing more and more for this nimble tablet.
Sent from my Moto G 2014 LTE using Tapatalk

Need a little help
AwesomeLewis24 said:
Forenote: Root has finally been achieved for us on the Asus Zenpad C 7.0! Special shoutout to @InvisiBot (source) and @b0joker (source). Not only that, but also to the Russian 4pda forum where the root process was brought up and discovered (source). All rightful credit can be paid to those.
This topic is not me claiming to have made the root process, but only instead simplifying the process (hopefully) for all y'all guys to get root up and running on your ZenPad C 7.0. Let's do this!
I am not responsible for any screwed tablets, rekt skrubs, or anything that happens as a result of you following this guide. It worked for me on my Z170C, so there's no reason as to why it probably shouldn't work for you.
ASUS ZenPad C 7.0 Root Prerequisites
ADB + Fastboot Drivers (can either use Google's, Intel's or ASUS')
Z170C Root img
Patience
Android SDK (and platform tools installed, can be installed through the SDK Manager)
Ensure that the ADB + Fastboot drivers are correctly installed by opening a new command prompt window, and typing the command "cd {this should be the directory to your Android-sdk/platform tools folder - the folder where adb.exe and fastboot.exe are located". Now, type "adb devices". If you see your device in the list with 'unauthorised', ensure that you check your tablet and allow ADB debugging to continue with your computer.
A full backup of everything that you would like to keep (because the device is unrooted, we cannot complete a Titanium Backup or likewise. Instead, ensure that all valuable photos, music, apps are backed up and are kept a note of to reinstall afterwards. We will have to be factory resetting the tablet in order to unlock the bootloader and boot from the root img.
(downloads are below in the attached files)
ASUS ZenPad C 7.0 Root Process
Ensure that ADB Debugging is enabled on your device, and that a full backup of everything that you want to keep has been made.
Connect your Z170C to your computer with ADB Debugging checked, and ensure that the ADB drivers are installed and working as intended.
Download the Z170C root img, and store it on your desktop.
Open a new command prompt window, cd to your Platform tools folder (with adb.exe and fastboot.exe) and run adb devices to ensure that your device is connected.
Once connected successfully...
Code:
adb reboot fastboot
to reboot into fastboot.
Now you are successfully in fastboot, here's the tricky part. Follow the code as exactly given below:
Code:
fastboot oem unlock
fastboot oem unlock confirm
fastboot boot "C:\Users\{your PC user name here}\Desktop\root-z170c_cg.img"
IMPORTANT: The window will request that you follow the code "adb format userdata" and "adb format cache". DO NOT DO THIS. You will risk bricking your tablet (this was the mistake I took when I tried rooting this tablet for the first time, so it's no biggie). If you accidentally follow this by accident and end up bricking your tablet, follow the guidance below.
Allow the tablet to boot up. Give it a few minutes, and you should be at the ASUS tablet setup screen again. Proceed with setting the device up.
Once set up, proceed to the Play Store and install SuperSU (maybe even 'Root Checker' for further confirmation that root is successfully installed on your device). Once SuperSU is installed, be sure to update the root binary when it first prompts you to. At the prompt screen, select 'Normal' installation rather than 'TWRP/CWM'.
When the binary has installed, reboot your device one final time. Welcome to your rooted Z170C!
Endnote
I hope this brief tutorial helped you to gain root onto your ASUS ZenPad C 7.0. It is disappointing that you will have to go through all of this trouble in order to obtain root, but if you follow all of the steps exactly I can guarantee that it will work. And not forgetting, again, all credit stands to where it's due (check top of forum post).
In case of brick...
It happened to me, and it'll probably (not) happen to you. If by any chance you make a mistake and go wrong, fear not.
Firstly, leave fastboot by powering off the device.
Power back on the device, and when you reach the 'ASUS' boot up screen, hold the power + volume down buttons at the same time. Wait roughly 5 seconds.
At the 'recovery menu' screen, use the volume keys to select "Factory reset" and press the power button to select.
Wait a minute or two, and when the process has completed, use the volume keys to scroll back up to the top and reboot your device.
Once you are back inside the ASUS Setup, reboot your device and try again! This time, following the steps... Good luck.
Unbrick process not working for you? Download the stock firmware .zip here, and be sure to boot into recovery mode (power + volume down at boot) and flash the .zip. - I haven't tested this yet so I cannot confirm 100% that this method works, but it should. It could be either an update package or the full stock firmware, but one user has confirmed this method to be working.
v.1.0.1 - Topic created. Will require cleaning up and simplifying sometime.
Click to expand...
Click to collapse
Okay, I am not sure what I am doing wrong, i can run the adb devices command and it shows that it is connected. After i run the adb reboot fastboot my p01z is at a green screen with the little android guy on it. Then I try to run the next command and it says waiting for device. What am I doing wrong? What info do I need to provide for some help? Any and all help is appreciated. Thanks

@corvusfan23
When you're in the green screen where it says "waiting for device", check your Device Manager (windows key + R, search for devmgmt.msc"). If you see your device with the yellow warning symbol next to it, it isn't correctly installed. Simply double click on it, and click browse to manually install the driver and click on either the Google / ASUS / Intel or any other compatible ADB driver and let it install. It should then be usable to and from your computer.
This happened with me and is quite frequent. For me however, the device kept connecting and disconnecting every 20 seconds so I had to be very quick at reinstalling the correct driver. After the driver was reinstalled for my tablet again in fastboot, I could continue on with the process.
Sent from my Moto G 2014 LTE using Tapatalk

AwesomeLewis24 said:
@corvusfan23
When you're in the green screen where it says "waiting for device", check your Device Manager (windows key + R, search for devmgmt.msc"). If you see your device with the yellow warning symbol next to it, it isn't correctly installed. Simply double click on it, and click browse to manually install the driver and click on either the Google / ASUS / Intel or any other compatible ADB driver and let it install. It should then be usable to and from your computer.
This happened with me and is quite frequent. For me however, the device kept connecting and disconnecting every 20 seconds so I had to be very quick at reinstalling the correct driver. After the driver was reinstalled for my tablet again in fastboot, I could continue on with the process.
Sent from my Moto G 2014 LTE using Tapatalk
Click to expand...
Click to collapse
Okay I did end up getting my device rooted, how would I go about making a backup of my device? I saw something about titanium backup, and the next thing I want to do is remove the bloatware. Any help is appreciated!

@corvusfan23
That's great to hear! To make a backup of your device, yes definitely I'd recommend Titanium Backup. It's a pretty powerful tool for root users to make full backups of the system, media, specific apps, etc. I haven't actually used it much myself as usually I don't keep much important stuff on my device (photos and music I usually keep in the cloud now) but on the odd occasion that I have used it, its been very good. I have it installed on my Moto G for "emergency situations".
Also, to uninstall the bloatware you can indeed use Titanium Backup but I'm quite a fan of Link2SD. I prefer the material design interface and the easy visuals, but that's just me. In terms of uninstalling bloatware, they work pretty much the same so its your choice. I've been loyal to Link2SD for a while now.
As far as bloatware comes, uninstall (or even better, freeze) as much crap as you want. I haven't experienced any problems with it so far - (on my old Acer tablet that I got at Christmas, the first thing after root I did was uninstall the Amazon app store. It bricked my tablet and there was nothing like stock firmwares around, or any dev support, so I returned it and got this asus). However, stay cautious and of course don't mess around with any apps that seem to be tied in with the system in some way.
Sent from my Moto G 2014 LTE using Tapatalk

AwesomeLewis24 said:
@corvusfan23
That's great to hear! To make a backup of your device, yes definitely I'd recommend Titanium Backup. It's a pretty powerful tool for root users to make full backups of the system, media, specific apps, etc. I haven't actually used it much myself as usually I don't keep much important stuff on my device (photos and music I usually keep in the cloud now) but on the odd occasion that I have used it, its been very good. I have it installed on my Moto G for "emergency situations".
Also, to uninstall the bloatware you can indeed use Titanium Backup but I'm quite a fan of Link2SD. I prefer the material design interface and the easy visuals, but that's just me. In terms of uninstalling bloatware, they work pretty much the same so its your choice. I've been loyal to Link2SD for a while now.
As far as bloatware comes, uninstall (or even better, freeze) as much crap as you want. I haven't experienced any problems with it so far - (on my old Acer tablet that I got at Christmas, the first thing after root I did was uninstall the Amazon app store. It bricked my tablet and there was nothing like stock firmwares around, or any dev support, so I returned it and got this asus). However, stay cautious and of course don't mess around with any apps that seem to be tied in with the system in some way.
Sent from my Moto G 2014 LTE using Tapatalk
Click to expand...
Click to collapse
Last question I have for now. What apps would you recommend uninstalling/freezing? I don't use a lot of the asus apps that came with it. Could I get rid of the "Asus Demo" app and "Asus Support" apps?

@corvusfan23
I've uninstalled most of the preinstalled apps (non asus) but also I've uninstalled some of the asus cloud and "do it later sort of apps. I've frozen the asus keyboard, the ZenUI launcher, and the built in browser as well because I use alternative Google apps.
Sent from my Moto G 2014 LTE using Tapatalk

[Resolved] How to successfully root PTCL Charji Wingle R660 and enable security and NAT features

Goal has been successfully achieved by a little bit of research and careful experimentation. Got to the middle of this post to find the complete solution.
I have a 4g Router Model: R660 also called 4g Wingle. The manufacturer is unknown as there is no branding on the device. But some say it is a GadgetIT product. I have scoured the internet and I cannot find the vendor named GadgetIT. But that is a separate discussion.
Main Goal: My main goal is to enable Virtual Server/Port forwarding in the device. The UI available when the device is connected is available at 192.168.1.1 with credentials admin/admin and Looks like 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"
}
This device is marketed by ISP PTCL as CHARJI EVO . The users of PTCL charji on this forum might say that port forwarding is not possible in this device but I disagree. and I have evidence to support otherwise but again that is a separate discussion.
What I have found so far?
I am able to telnet to this device at 192.168.1.1 via admin/admin credentials. Here is what I get.:
Version
LNX.LE.4.1-41009-9x35
But admin is not root. There is a separate user called root which obviously has a different password. I have tried all common router password (not sure what all will constitute...but i have tried many).
The goal here is to root this device so that I can perform the necessary changes such as the following:
As you might have guessed by now, that i cannot unless I am root which I am not.
So I need your help guys. Here are other interesting things to look at:
I could edit mobileap_cfg.xml but I cannot because the file is readonly and I was unable to chmod it to 777 with an error message "Operation not permitted" indicating that I am not root and I can not make that happen.
The second thing i would like to do is to enable SNMP monitoring which I cannot do from the main interface because the vendor hid the option.
Lastly, enable firewall.
Interestingly, all these options are available in a tab called "Security" which the vendor has hidden from the configuration interface available at 192.168.1.1
So I am inviting the expert comments of all hackers that can help me make get it sorted out. Ideally, it would be awesome to have these options enabled from the UI (I am willing to hack, root this device and modify firmware if needed) to get this done.
This can potentially help millions of PTCL Charji Users who cannot run any kind of server using this device (including game servers) and any kind of listening services (sockets or WEB or FTP) r those who would like use torrents but suffer from terrible low download speeds on torrents because of not being able to open ports for incoming connections that significantly raise download speeds for torrent.
More details:
mobileap_cfg.xml ownership and permissions:
Appreciate your help. Waiting to hear helpful responses soon. Successfully rooted without any busy box.
Solution Achieved successfully- See Steps & detail as follows:
I was able to switch device to bootloader mode and was able to change root password and now I am able to switch to root mode when logged in via admin using telnet. I have successfully change the DMZ but i have yet to observe its effects. If it works, I will work on changing other values as well.
Detail:
The device closely resembles D-Link DWR 901 But mind you, it is NOT DWR 901. Even thought the radio matches, if you flash the firmware from DWR 901 (which will be successful), the device will NOT work. Since there is no available source of the original firmware of the device, the device will be of no use anymore. So do not do it.
Similary D-Link's DWM 222 is also similar to this device (only that DWM 222) is a 3G modem. I downloaded both firmwares and found out upon extraction of these firmwares, that it contains the following files.
Files that you actually need are present in this archive -
WARNING
Use at your own RISK!!. Flashing this directly to your Charji will brick you Charji device. So just follow the procedure I described and do not try to flash it directly otherwise it will render your device unable to connect even though everything will look all right in the software. The device will never connect again...ever!
https://www.dropbox.com/s/hqa2m4499pyrj3z/R660A-Donot-Flash-it-On-Charji-It-Will-Brick-Your-device.7z?dl=0
There is a file called dl.exe which can turn the device into download mode assumung you have the PTCL Charji Wingle R660 plugged into the USB port.
After that running adb devices command will list all the devices.
After that you need to run the following commands
Code:
adb shell
passwd
The adb shell command will take you to the shell.
The passwd command executed from shell will tell you to enter a new password for root user
You will have to provide a secure password for it to be accepted.
After that, it will update the root password.
exit the shell using the exit or quit command or simply close the command prompt.
Now, you can telnet to the device using the command
Code:
telnet 192.168.1.1
Login with username admin and password admin (if these are your credentials to access the router page, Use your credentials. Mine were admin/admin)
The issue the following command to switch to root mode
Code:
su
It will ask for root password. Enter the password you set using the adb shell you had used before. and viola. You will turn to root mode.
You you have two ways to fix the NAT/DMZ problem.
Either you can directly use the vi editor (my OpenEmbedded Linux OS installed on the device has only vi support) to edit the file mobileap_cfg.xml and update DMZ value and port forwarding values.
or you can enable the security tab by editing the menu.js file which is located in /WEBSERVER/www/ directory. Now I had a PTCL Charji R660. If you have a different device, your files will be located elsewhere with different sets of issues.
You can do whatever you want!
Older Updates
Update# 02:
DMZ is now working !!
Update# 03
Successfuly unlocked the hidden security tab but still untested. Will test it shortly.
Update # 04
Successfully unlocked Wizard
Update# 05
NAT Rules persisting and working, tested by download torrents and using CanYouSeeMe.ORG
Torrents Downloads working on max available speeds

Reserved 1

Reserved for additional instructions etc
Reserved 2

Good find but instructions are really ambiguous and unclear. What are you supposed to do with dl.exe? run it, stare at it, run it and press enter????
You are just trapping people into bricking their devices with this instruction.

Yes I am bad at providing instructions.
dl.exe once run, turns the charji into bootloader mode and then it is possible to run adb shell and adb commands.
Hope this helps. I will update the article to be more descriptive in future sometime. Don't have time right now.
Regards.

timematcher said:
dl.exe once run, turns the charji into bootloader mode and then it is possible to run adb shell and adb commands.
Click to expand...
Click to collapse
Ok you are still not being clear. What do you mean by run once? currently dl.exe shows
Code:
Welcome to use OnekeyUpdate Tool.
The Software to be updated:Desktop
Press 'Enter' to update or 'Q' to quit.
on opening. Should I press Enter?
Sorry about being rude in first comment. I am really angry right now over this device right now, what kind of stupidity is not allowing user to port forward.

raza1080p said:
Ok you are still not being clear. What do you mean by run once? currently dl.exe shows
Code:
Welcome to use OnekeyUpdate Tool.
The Software to be updated:Desktop
Press 'Enter' to update or 'Q' to quit.
on opening. Should I press Enter?
Sorry about being rude in first comment. I am really angry right now over this device right now, what kind of stupidity is not allowing user to port forward.
Click to expand...
Click to collapse
When you click Enter, it will say "Waiting for device...." and then "found"
That is the point the device will appear in device manager (on windows) as well. and Now is the time to run adb shell and corresponding commands in my first article.
Important thing to note is that if you have never rooted any android (or linux) based device/phone/tablet, I suggest you read more about running adb.
The goal of my article was the following:
1. reset root password on the OpenEmbedded Linux variant on teh charji wingle device
2. Login via Telnet to 192.168.1.1 (Charji web console) using admin/admin (default credentials of Charji)
3. change to root mode using su command
4. Be able to change the xml files ( i mentioned in the first post) that allow the user to create the firewall rules and virtual server entries.
Now at this point I did not know that the person who whitelabelled Charji wingle for PTCL simply had disabled the relevant code in menu.js that enabled the Virtual server entries and firewall entries and DMZ fields (that allow pot forwarding, open firewall or simply set an ip address for DMZ that opens everything to a single IP on charji local network).
Once I found out, I was really happy and now I created the virtual server entries for torrent which was my main problem.
Thanks to Dr.hack who created a proper tutorial on his blog based on information in this article in a more streamlined manner.
Dr. Hack's Blog, Root-hack-ptcl-charji-evo-nat/

thank you for the tutorial.I am trying it on a charji cloud R500A. when dl.exe finds the device it goes to "6% Downloading hex image" .Am i suppose to wait at this point?
And will i be able to use other sim on the the device after the root?

Tarar said:
thank you for the tutorial.I am trying it on a charji cloud R500A. when dl.exe finds the device it goes to "6% Downloading hex image" .Am i suppose to wait at this point?
And will i be able to use other sim on the the device after the root?
Click to expand...
Click to collapse
First things first!, Are you trying to flash the image from the firmware link I gave? You should really not do that!
The link i gave is only provided for firmware modding experts. It is not the firmware of Charji. So if you flash it, it will brick your device and it will become useless.
What you really need to use is th dl.exe file , copy it into a separate folder with no other stuff in it.
If you run it from the same folder, it will brick your device by flashing a firmware which will not work for your Charji. CHarji will never connect after that!
dl.exe must be run to turn the device into booloader mode, After that you have to run adb shell commands and make the necessary changes to reset the root user password.
I don't know if it will allow you to use another SIM or not. PTCL devices are usually NOT network locked. But again, this is not a tutorial for allowing the users to use another sim. It merely allows the user unlock Virtual Server, Firewall, DMZ settings and similar features which are hidden by PTCL.
And there is no such thing as "Telenet". Telnet is a client application in windows which is not installed by default. You will have to install Telnet Client from "Add Remove programs" in Windows. It is needed to access the device using the telnet protocol. Do some research on Telnet.

timematcher said:
First things first!, Are you trying to flash the image from the firmware link I gave? You should really not do that!
The link i gave is only provided for firmware modding experts. It is not the firmware of Charji. So if you flash it, it will brick your device and it will become useless.
What you really need to use is th dl.exe file , copy it into a separate folder with no other stuff in it.
If you run it from the same folder, it will brick your device by flashing a firmware which will not work for your Charji. CHarji will never connect after that!
dl.exe must be run to turn the device into booloader mode, After that you have to run adb shell commands and make the necessary changes to reset the root user password.
I don't know if it will allow you to use another SIM or not. PTCL devices are usually NOT network locked. But again, this is not a tutorial for allowing the users to use another sim. It merely allows the user unlock Virtual Server, Firewall, DMZ settings and similar features which are hidden by PTCL.
And there is no such thing as "Telenet". Telnet is a client application in windows which is not installed by default. You will have to install Telnet Client from "Add Remove programs" in Windows. It is needed to access the device using the telnet protocol. Do some research on Telnet.
Click to expand...
Click to collapse
Thank you so very much for the details.
Yeah i found out about telnet commands.but i was using the dl.exe in the same folder.i guess that's why adb devices wasn't able to find my device.
Luckily it didn't install that firmware.

I have bricked my device by accidentally runing the gui.exe and i was dont know that it will flash new firmware. is there any way to get back ?:crying:

If you are able to switch to fastboot mode and you have the original software in the right format, then you should be able to flash the new firmaware using the utilities provided in the original post. The only way I think. I will try to see if I can create an image for my Charji R660 but I can not promise anything.
Note that I bricked first of mine and I took it to the people who upgrade firmware of the device and they were unable to fix it. and I got a new one by being sneaky (and playing dubm) about it.
Or if you want to learn, maybe start experimenting a little bit but I think you will need the original firmware.

timematcher said:
When you click Enter, it will say "Waiting for device...." and then "found"
That is the point the device will appear in device manager (on windows) as well. and Now is the time to run adb shell and corresponding commands in my first article.
Important thing to note is that if you have never rooted any android (or linux) based device/phone/tablet, I suggest you read more about running adb.
The goal of my article was the following:
1. reset root password on the OpenEmbedded Linux variant on teh charji wingle device
2. Login via Telnet to 192.168.1.1 (Charji web console) using admin/admin (default credentials of Charji)
3. change to root mode using su command
4. Be able to change the xml files ( i mentioned in the first post) that allow the user to create the firewall rules and virtual server entries.
Now at this point I did not know that the person who whitelabelled Charji wingle for PTCL simply had disabled the relevant code in menu.js that enabled the Virtual server entries and firewall entries and DMZ fields (that allow pot forwarding, open firewall or simply set an ip address for DMZ that opens everything to a single IP on charji local network).
Once I found out, I was really happy and now I created the virtual server entries for torrent which was my main problem.
Thanks to Dr.hack who created a proper tutorial on his blog based on information in this article in a more streamlined manner.
Dr. Hack's Blog, Root-hack-ptcl-charji-evo-nat/
Click to expand...
Click to collapse
Hi dear friend how are you? I need original webui of PTCL Charji device For Huawei Ec8372u-876 device please can you share the link or any guidance for this

saqi755 said:
Hi dear friend how are you? I need original webui of PTCL Charji device For Huawei Ec8372u-876 device please can you share the link or any guidance for this
Click to expand...
Click to collapse
Or any other links of non modified original Loced Huawei firmware and Webui

Huawei Ec8372u-876 is a very good device compared to sh!t devices offered by PTCL before.
Here is what I have found on the web.
Its probably an unlocking solution and not a locked file.
I am in no way responsible for the quality of the file or the steps as I dont have this device and I can not test it before posting.
Please use these are your own risk. I at least downloaded the file and executed on local PC.
but that is pretty much it. Please use at your own risk.
PTCL Evo Charji Cloud
E5377u-872
How to Unlock Evo Charji E5377u-872
1: Battery Should be 100% Charged
2: Data Cable
3: A Pin
4. Unlocked file
Click to expand...
Click to collapse
Code:
www.mediafire.com/file/6td2bh12b4l6g9o/PTCL_charji_E5377u-872-www.hispeedsolution.com.exe/file
Process>>
1. Remove the battery from the device
2. Press & Hold Power Button + Reset Button on the same time after 5 seconds device will boot into download mode.
3. Connect to PC
4. Wait for drivers
5. After the drivers installed go to device manager & note down the port # namely appplication UI interface.
6. Run the *.exe file & enter the port # (E.g 19 or 20 or etc etc)
7. Let it flash the device, it will take about 5 minutes, after the flashing let the device reboot. Your device will stuck on the Huawei screen, Don't worry wait for 3 minutes then remove the battery insert any Sim card & turn on the device.
8. Your device is successfully unlocked on all network Sim.
9. Connect the device to PC & set up accordingly.
Click to expand...
Click to collapse

timematcher said:
Huawei Ec8372u-876 is a very good device compared to sh!t devices offered by PTCL before.
Here is what I have found on the web.
Its probably an unlocking solution and not a locked file.
I am in no way responsible for the quality of the file or the steps as I dont have this device and I can not test it before posting.
Please use these are your own risk. I at least downloaded the file and executed on local PC.
View attachment 5369881
but that is pretty much it. Please use at your own risk.
Code:
www.mediafire.com/file/6td2bh12b4l6g9o/PTCL_charji_E5377u-872-www.hispeedsolution.com.exe/file
Click to expand...
Click to collapse

Thanks for your cooperation but I need file for Ec8372u-876 this file is not working on this please check this again this is not a device with battery

Let me look into it.

timematcher said:
timematcher said:
Can we use other networks 4G in this device?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Please reply if possible

sparking111 said:
Please reply if possible
Click to expand...
Click to collapse
Huawei 4G wingle should support other networks/SIMs once rooted.
I had a E8372h-608 4G wingle which was network locked to Telenor. After flashing it with network-neutral, universal firmware from huawei, it works for Ufone, Telenor, Warid/Jazz after appropriate AP configuration within the device UI.
Does that answer your query?

TiVo Stream 4K

Has anyone had much experience with the TiVo Stream 4K yet? I have 2 questions really. I would like to accomplish both without rooting the device.
1) Is there a way to skip the initial TiVo activation? I've tried powering off the device once it gets to that screen, but it starts right back up to the activation. I've tried hitting home, back, skip, everything I can think of, but it won't let me move on until the device is activated on a TiVo account. I want to help a buddy out by setting up his device for him, but I don't want the device to be locked to my TiVo account. I may be able to clear data on the TiVo app and remove it from my TiVo account manually (I haven't tried that yet), but I'd like to just skip the whole TiVo activation and let my friend do it all himself (set preferences, services to monitor, etc).
2) Has anyone been able to remove the TiVo Suggestions Channel from the Android TV home screen? When you go into the Channel Customization, you can deselect all channels but the TiVo Suggestions Channel. I can't even get it to move down the list (all other channels you can go left on the channel and move or remove, but that option isn't available for the TiVo suggestions Channel). I've tried clearing data on the TiVo apps. I've even tried disabling the TiVo and Sling apps, but the channel remains (and if you click it when the apps are disabled, it just errors out loading the app).
The important thing with both of those is it must be done without Root. I want Google Play to remain genuine so Netflix and other streaming apps work properly.

From what I can tell, No and No unfortunately. If you disable the Tivo app as well, the block in the launcher remains and won't go away. If you click it, its magically working again and not disabled. I'm fairly certain they modified the launcher and worked the Tivo stuff is permanent as for the price. The hardware is made by another company, same one that makes their AirTV2 tuner for sling. So I would just setup the tivo stuff under your tivo email. If your friend isn't going to use Tivo services in any way, it won't be an issue for you.

https://photos.app.goo.gl/pNcD361dJLsxTxMK9
I went through the original setup and configured it as it expected me to. Then I uninstalled most of the apps it comes bloated with. The ones I couldn't uninstall, I disabled at least visually. Then I installed Wolf Launcher and modified it to my liking. I then moddifed the remote to make the tivo button to open tivimate with a single click and vod apk with double click. I also made the Guide single click to open app history and double to open "Power off, Restart and Screenshot". Sometimes pressing tivo button would bring up the tivo guide and tivimate, so I disabled the tivo app, sling and most other crap entirely I didn't want running in the given app settings.
The only button I could not override was the Netflix button. You cannot uninstall Netflix either, but I believe you can disable it. My device runs incredibly smooth now and my display stays off when I use the power options above. Playback of vod does flicker sometimes, but I feel sure that will get resolved with a future update.

USAMac said:
https://photos.app.goo.gl/pNcD361dJLsxTxMK9
I went through the original setup and configured it as it expected me to. Then I uninstalled most of the apps it comes bloated with. The ones I couldn't uninstall, I disabled at least visually. Then I installed Wolf Launcher and modified it to my liking. I then moddifed the remote to make the tivo button to open tivimate with a single click and vod apk with double click. I also made the Guide single click to open app history and double to open "Power off, Restart and Screenshot". Sometimes pressing tivo button would bring up the tivo guide and tivimate, so I disabled the tivo app, sling and most other crap entirely I didn't want running in the given app settings.
The only button I could not override was the Netflix button. You cannot uninstall Netflix either, but I believe you can disable it. My device runs incredibly smooth now and my display stays off when I use the power options above. Playback of vod does flicker sometimes, but I feel sure that will get resolved with a future update.
Click to expand...
Click to collapse
Which button remapper app did you use? Might want to do something similar.
Also, not sure if it's just the hub I bought, but the Aukey USB type c 4 port hub doesn't work on the stream, but it does on my Huawei. Strangely a generic type c otg with a USB Ethernet adapter works fine.

siralsmooth said:
Which button remapper app did you use? Might want to do something similar.
Also, not sure if it's just the hub I bought, but the Aukey USB type c 4 port hub doesn't work on the stream, but it does on my Huawei. Strangely a generic type c otg with a USB Ethernet adapter works fine.
Click to expand...
Click to collapse
Yea I've had issues with ethernet connection as well. I believe there will be an update soon to resolve alot of the issues. My anker and amazon after ethernet adapters don't work, but I've read ugreen works but some say its unstable.
Anyhow, I used ButtonMapper

siralsmooth said:
Which button remapper app did you use? Might want to do something similar.
Also, not sure if it's just the hub I bought, but the Aukey USB type c 4 port hub doesn't work on the stream, but it does on my Huawei. Strangely a generic type c otg with a USB Ethernet adapter works fine.
Click to expand...
Click to collapse
Hey sorry for the delay! I used ButtonMapper.. and yea, there are alot of externals not working.. hopefully, the pending update will resolve these issues as well!

Is there a way to install the Tivo app on this thing? Kind of ironic it doesn't come with it.

there is a debug version of the firmware
TIVO - Google Drive
drive.google.com
adb shell reboot fastboot
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot reboot
adb disable-verity
adb reboot
adb root
adb remount
relook command is
fastboot flashing lock_critical
fastboot flashing lock
fastboot reboot

ben1226 said:
there is a debug version of the firmware
TIVO - Google Drive
drive.google.com
adb shell reboot fastboot
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot reboot
adb disable-verity
adb reboot
adb root
adb remount
relook command is
fastboot flashing lock_critical
fastboot flashing lock
fastboot reboot
Click to expand...
Click to collapse
what is the point of debug version of the firmware? sorry just asking to clarify

chinkster said:
what is the point of debug version of the firmware? sorry just asking to clarify
Click to expand...
Click to collapse
i'm curious about this too. the new ts4k software is absolute trash, would love to be able to go backwards and keep it from doing updates if possible...but i need more clarity on what exactly this does.

crackers8199 said:
i'm curious about this too. the new ts4k software is absolute trash, would love to be able to go backwards and keep it from doing updates if possible...but i need more clarity on what exactly this does.
Click to expand...
Click to collapse
I see the commands but do you know exactly how to implement them to flash the firmware? Just asking I've been watching this thread for a while

jmanley69 said:
Has anyone been able to remove the TiVo Suggestions Channel from the Android TV home screen?
Click to expand...
Click to collapse
Might be a year late and I'm sure everyone knows this already but.
If you go to apps system apps then disable the app I circled in this picture then restart your system it will let you freely customize everything on the homescreen. (Besides play next but that can be disabled)
{
"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"
}

ben1226 said:
there is a debug version of the firmware
TIVO - Google Drive
drive.google.com
adb shell reboot fastboot
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot reboot
adb disable-verity
adb reboot
adb root
adb remount
relook command is
fastboot flashing lock_critical
fastboot flashing lock
fastboot reboot
Click to expand...
Click to collapse
So, it is important not to have the erase button checked. I mistakenly had it checked and now the device is stuck in USB download mode showing GX-CHIP (instead of worldcup) that is password protected and the password.bin provided does not seem to unlock it. Any guidance would be helpful.
For others, I have successfully downloaded the ota and have flashable images for anyone interested. If you haven't updated you can flash from fastboot, if you haven't then follow what @ben1226 has in TiVo gdrive remember to uncheck erase and then you should be able to unlock flashing from fastboot. The Rom already has a su binary (in /xbin) which can be enabled (permissions are set off by default) for those interested if one wants root.
EDIT: Attached the unmodified OTA update.
ota-type=BLOCK
post-build=eSTREAM4K/SEI400TV/SEI400TV:9/PI/5614:user/release-keys
post-build-incremental=5614
post-sdk-level=28
post-security-patch-level=2021-04-05
post-timestamp=1622542764
pre-device=SEI400TV

jahrule said:
So, it is important not to have the erase button checked. I mistakenly had it checked and now the device is stuck in USB download mode showing GX-CHIP (instead of worldcup) that is password protected and the password.bin provided does not seem to unlock it. Any guidance would be helpful.
For others, I have successfully downloaded the ota and have flashable images for anyone interested. If you haven't updated you can flash from fastboot, if you haven't then follow what @ben1226 has in TiVo gdrive remember to uncheck erase and then you should be able to unlock flashing from fastboot. The Rom already has a su binary (in /xbin) which can be enabled (permissions are set off by default) for those interested if one wants root.
EDIT: Attached the unmodified OTA update.
ota-type=BLOCK
post-build=eSTREAM4K/SEI400TV/SEI400TV:9/PI/5614:user/release-keys
post-build-incremental=5614
post-sdk-level=28
post-security-patch-level=2021-04-05
post-timestamp=1622542764
pre-device=SEI400TV
Click to expand...
Click to collapse
Is there a guide to do this the links you gave me dont show anything . I'm about to buy one and attempt this but I need instructions I mainly want root .

@tokoam The tools etc are found here https://drive.google.com/drive/folders/18PWax4UPUBAdgAz1R9KnmCNFlt6a3fjA?usp=sharing where @ben1226 linked.
basically don't update it when you first get it. In a few days I will have more as m currently working on something for it.
If you are inpatient and have some know how then: flash the update I provided above, but NOT the bootloader from there (the updated bootloader enables oem lock and so far have not found a way to expose the option in dev options). Then chmod the `su` binary located in /xbin/ and you should have root and be good to go.

flash the update I provided above ... Then chmod the `su` binary located in /xbin/ and you should have root and be good to go
Click to expand...
Click to collapse
I installed the update that you attached above (in post #13) but there is not any su binary located in /xbin/, or anywhere else.
This seems to make sense, because you say in post #13:
EDIT: Attached the unmodified OTA update.
But I'm not sure why you suggested that the 'su' binary would be there, if the update attached to post #13 was installed.
flash the update I provided above, but NOT the bootloader from there (the updated bootloader enables oem lock and so far have not found a way to expose the option in dev options)
Click to expand...
Click to collapse
I didn't flash the bootloader from the update (in post #13), but still the bootloader was locked after I installed the rest of the update. Even if I didn't update bootloader.img or boot.img, the bootloader still gets locked when installing the rest of the update attached to post #13. So, the update is locking the bootloader by other means, probably via system.
I could unlock the bootloader again only by re-flashing the userdebug verson via usb burning mode. But then, of course, I no longer have 5614.

Right the bootloader lock happens only when you flash a system.IMG which is not a user debug version. The su binary is in the debug system img. I think if we can expose the allow OEM unlock option in Dev settings then we would be good to ho. My device bricked in gx-chip mode that apparently uses a different password then the one provided by Ben so im stuck there for now

goapy said:
I installed the update that you attached above (in post #13) but there is not any su binary located in /xbin/, or anywhere else.
This seems to make sense, because you say in post #13:
EDIT: Attached the unmodified OTA update.
But I'm not sure why you suggested that the 'su' binary would be there, if the update attached to post #13 was installed.
I didn't flash the bootloader from the update (in post #13), but still the bootloader was locked after I installed the rest of the update. Even if I didn't update bootloader.img or boot.img, the bootloader still gets locked when installing the rest of the update attached to post #13. So, the update is locking the bootloader by other means, probably via system.
I could unlock the bootloader again only by re-flashing the userdebug verson via usb burning mode. But then, of course, I no longer have 5614.
Click to expand...
Click to collapse
jahrule said:
Right the bootloader lock happens only when you flash a system.IMG which is not a user debug version. The su binary is in the debug system img. I think if we can expose the allow OEM unlock option in Dev settings then we would be good to ho. My device bricked in gx-chip mode that apparently uses a different password then the one provided by Ben so im stuck there for now
Click to expand...
Click to collapse
Here is something that can be done:
if (!showEnableOemUnlockPreference()) {
removePreference(this.mEnableOemUnlock);
this.mEnableOemUnlock = null;
That needs to he removed from tvsettings.apk
doing that is the easy part.. but installing the custom apk is the hard part.
need bootloader unlocked so we make changes to system.
the above is decompiled from the userdebug build.
also:
private static boolean showEnableOemUnlockPreference() {
return !SystemProperties.get("ro.frp.pst").equals("");
}
private boolean isOemUnlockAllowed() {
return !this.mUm.hasUserRestriction("no_oem_unlock");
}
pretty much: ro.frp.pst = 1 or true should turn on OEM unlock in developer options.
BTW: user restrictions only means, you must be logged into box with correct username and all..
bypassing settings and logging on as guest or whatever will not show any developer options..
that is what it means about user restrictions..

The circuit board used in the tivo stream 4k has a place for a micro sd card socket. I'm going to install a socket and check if it works.

I read on reddit this morning that the android 10 update started on 3/17. No sign of it on my hardware yet.

How To Root Any Android Device~! Part 1

=================================================
================================
HOW TO ROOT ANYTHING ANDROID
=============================
===========================​
Hello Friends~!
I am working out a Series of Threads that I want to string together to sort of go over the many nuances and intricacies of unlocking a device's bootloader and flashing Roms.
This is part 1, unlocking the bootloader, part 2 will be rom flashing oriented, and will be added to a separate thread whenever the heck I work it out~!
Part 3? Will be taking the adb tools and building our first piece of Open Source "Software" on Windows, with a GUI, to make using ADB easier and more fun~!
Please Note That There Is No "One Best Way" To Do Anything In Rooting and Computing in General. There are Many Ways~! As evidenced here:
Spoiler: THE MOST EPIC ROOT
[CLOSED]HaHaHack Dis: No Magisk REQUIRED!!!!
Magisk is no more... I present a new fool proof method of flashing su to Android 10_Q and above!! I ranted and ranted about variant=user/user-debug/eng builds that I got no-where... people thinkin am dissin john wu, nah, I respect what I've...
forum.xda-developers.com
This Guide Is Catered To Take Someone Down "The Path", Who Has Never Done A "Root" before, For An Android Device, On Windows~!
Spoiler: DISCLAIMER
Note that this Guide cannot Currently help if you have purchased an Android Device from a Proprietary Manufacturer, that Locks the Bootloader with Efuse Chip Technology..
eFuse - Wikipedia
en.wikipedia.org
Spoiler: GETTING STARTED
You will need some options enabled in File Explorer, if you don't have them already...
Press the Windows Key and type "folder"
That should pull up an option for "File Explorer Options" Select it, then..
Make sure "Display the Full Path" is ticked.
Select, "Show Hidden Files and Folders"
UNTICK hide extensions for known file types.
Spoiler: LIKE 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"
}
Spoiler: GETTING ADB AND THE USB DRIVERS
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
Spoiler: PROGRAMMING OUR DEVICE FOR ADB
Spoiler: A QUICK NOTE ABOUT MANUALLY ACCESSING THE BOOTLOADER
For Knowledge Purposes~!
You can usually use a combination of the power and volume keys, to access the bootloader.
This can also be done with devices like Google's Chromecast
Which uses a method involving the usb cable itself, and the back button... android boxes, etc.
Sometimes the bootloader can be accessed with controllers or keyboards, but this method is Not Universal for all Manufacturers and or Devices~!
Since we setup ADB Fully, we will make the method to access the Bootloader Partition of the Android Device, Universal, on Windows, by using the Command Line...
So we will use adb Instead of an Analouge Method..
Spoiler: EXAMPLES OF MANUALLY POWERING INTO THE BOOTLOADER
Since we will use ADB From the Start, we will Avoid Having to Figure out the Manual Method for our Devices.
For instance...
Spoiler: VISUAL EXAMPLES
This video Illustrates the Common Volume and Power button Method~!
The beginning of this video shows using a controller method, which would equate to holding a+b on a USB 3.0 keyboard, to post into the NVIDIA Shield's Bootloader. USB 3.0 Mattering in this, Device Specific, Case~!
Spoiler: ENABLE DEVELOPER OPTIONS
We will need to enable developer options for our device~!
This process Is Universal, But Only Universal to Your Android Firmware Version, IE Android 10,11,12 and if it is a TV, Phone, etc~!
Every Firmware will simply Require some form of you going into Settings, finding the "About" section on the device, Finding the build number,
Then select your Build 7 times. There's tons of videos on this step, Should you get hung up on your Particular device~!
Spoiler: ENABLE USB DEBUGGING AND OEM UNLOCKING
Once you have Developer Settings Unlocked, you need to go into the actual "Developer Settings" tab and enable these options..
Your browser is not able to display this video.
Spoiler: INSTALLING THE WINDOWS USB DRIVER FOR YOUR DEVICE
Now that we have USB ADB Debugging Enabled on Our Device, and OEM Unlocking, we can plug the device into our PC, and open Device Manager.
Your device will likely show up as either "fastboot", "other", or an "unknown" device.
Right Click that device, then install the driver as shown below..
Spoiler: INSTALLING THE WIN_USB DRIVER
Your browser is not able to display this video.
Spoiler: DOWNLOAD
Here is a link for a Mirror of Google's Universal USB DRIVER, if you need:
FASTBOOT DRIVER.zip
drive.google.com
Spoiler: DRIVER TROUBLESHOOTING
SAVE YOURSELF A HEADACHE AND KNOW FROM THE START, THAT THE GOOGLE USB DRIVERS AND FASTBOOT DO NOT WORK WITH SOME USB 3.0 DEVICES...
FOR INSTANCE, LATER MODEL LAPTOPS.... IF YOU FIND YOURSELF GETTING A CODE 1O ERROR, USE A USB 2.0 HUB TO ATTACH YOUR ANDROID DEVICE TO THE PC.
Spoiler: CODE10ERROR
Spoiler: USING ADB TO BOOT INTO THE BOOTLOADER
Now we should be able to open command prompt, type: adb devices, and see our device attached.
Spoiler: LIKE THIS
Spoiler: PASTE THIS COMMAND
adb reboot bootloader
Spoiler: BOOTLOADER PICS
You should have one of two results from this command..
Spoiler: BOOTLOAD IMAGE1
If your device shows this:
Spoiler: SHOW IMAGE
Then your device uses fastbootd and will require us to run a different command.
Remove the USB cable from your device, then hold the power key down for 10-20 seconds.
Your device will Power Off. Power it back on.
When it has fully rebooted, plug the usb cable back in, make sure USB debugging is Enabled and Run this Command:
Spoiler: PASTE THIS
adb reboot fastboot
Which will put us in fastbootd
Spoiler: WHAT IS FASTBOOT D
"Android 10 and higher supports resizable partitions by relocating the fastboot implementation from bootloader to userspace.
This relocation enables moving the flashing code into a maintainable and testable common location with only the vendor-specific
parts of fastboot implemented by a hardware abstraction layer (HAL)."
"In addition, Android 12 and higher supports flashing ramdisks through an added fastboot command."
--SOURCE.ANDROID.COM
Essentially, some devices may have this new fastboot scheme, meaning we will have a few new commands to work with when using fastboot..
Requiring a change in Semantics~!
In FastbootD, a noticeable difference in Semantics is the process of "Unlocking" the bootloader.
Traditionally, one would simply boot into the bootloader, and issue a command of "fastboot oem unlock" and that would get the job done.
However, with the integration of FastbootD, we too have to learn to speak it's new Language~!
So Instead, to get the same effect, we would use this command:
Spoiler: UNLOCK FLASHING IN FASTBOOTD
This part may or may not require OEM Specific Fastboot commands.
type:
fastboot flashing unlock
If successful, you're ready to Flash, which will be covered in part 2...
If not we need to look at figuring out our device's fastboot OEM commands, which can be vendor specific and will be covered on this guide, using the G20 as an example..
Mapping Out The G20's Internals
================================== ===================================== NOKIA G20 ALL ADB SHELL COMMANDS ========================================= Hello Friends, Welcome To.... My Book~! xD ===================== This Thread's mostly being put...
forum.xda-developers.com
Spoiler: BOOTLOAD IMAGE2
Else, if your device shows something like this:
Spoiler: SHOW IMAGE
You're ready to continue...
Spoiler: UNLOCK BOOTLOADER
You should now see an option to "Unlock" The Bootloader, Do So~!
THIS WILL DELETE THE DATA ON YOUR DEVICE~! YOU HAVE BEEN WARNED~!
Unlocking the bootloader will allow you to be able run this fastboot command:
fastboot oem unlock
to "Unlock" or allow your device's partitions to be modified, flashed, erased, etc~! I.E. Giving us "Root" Access~!
Spoiler: ADB TROUBLESHOOTING
If you do not see your device attached, remove the usb cable from the device, and remove the usb hub cable if using one, reset the Android device.
When the device is fully booted, reattach the usb cable and/or hub, and verify USB Debugging is showing on the device.
Spoiler: LIKE THIS
Your browser is not able to display this video.
This is the end of part 1, part 2+ will involve the intricacies of building and flashing of A Rom for our devices~!
<333333
Spoiler: REFS
How to enter Recovery mode on Nokia G10/G20?
Hello everyone. This is my post here on XDA. I'm using Nokia G20 TA-1365 Model (INDIA). Let's get to the tutorial. Prerequisites: 1. A Windows PC. 2. ADB and Fastboot Drivers. 3. Nokia G20 or G10. Switch off your Nokia G20 device. Press and...
forum.xda-developers.com
joegib's post on the thread above taught me about fastbootd
joegib
forum.xda-developers.com
This article goes into fastbootd, which I hadn't heard of before
What is fastbootd? How to Enable and Boot?
Google introduced the Android 10 operating system back in September 2019. Android 10 brought in new support for resizable partition which relocates the
www.getdroidtips.com
FastbootD Source Code
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
This video explains Super Partition Better
What are Ram Disks
RAM Disks Explained: What They Are and Why You Probably Shouldn’t Use One
Your computer’s RAM is still faster than even modern solid-state drives. RAM disks take advantage of this, using your computer’s RAM as a lightning-fast virtual drive. But you probably don’t want to use a RAM disk, anyway.
www.howtogeek.com
How to unlock bootloader on Nokia G20 - ROM-Provider
step by step guide to unlock bootloader on Nokia G20, after unlocking the bootloader you can root it by using the magisk
romprovider.com
Android Kitchens~! Or at least some tools to edit the bootimg for future reference
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
GitHub - szym/unbootimg: The complement to Android's mkbootimg
The complement to Android's mkbootimg. Contribute to szym/unbootimg development by creating an account on GitHub.
github.com
Please feel free to share any details below related to bootloader unlocking, adb, fastboot, etc~! I learn A Lot from You Guys~!
LEARN HOW TO MAP OUT YOUR DEVICE'S INTERNALS
Mapping Out The G20's Internals
================================== ===================================== NOKIA G20 ALL ADB SHELL COMMANDS ========================================= Hello Friends, Welcome To.... My Book~! xD ===================== This Thread's mostly being put...
forum.xda-developers.com
Hello from Jen in August 2022. A TLDR, I spent 5 months learning that android literally is linux i.e. all the bin files are ambidextrous and therefore a lot of the articles I link for knowledge to the systems on this device are linux specific.
The exercise and effort of mapping out the device taught me a lot. Highly recommend doing it once if you are brand new. I learned so much about Linux in a way I could personally digest.

An Addendum,
Some devices have a "preloader", a layer before the bootloader. I am working through learning how to bypass and explain that whole mess. Idk how long it will take.
With that out of the way, I have an idea how one Could Actually Root any Android device, just not conventionally.
What I mean is, and this is all in theory and being developed now https://forum.xda-developers.com/t/...r-android-devices-windows-10-nox-lab.4481613/
What if you could just use a simple app like limbo to boot up a pre-installed with root and magisk android image?
Breaking it down further, what if it was possible to run a virtual machine image of android that was pre-rooted with pre-installed apps (i.e. a custom rom)
That would in theory allow one to keep the integrity of the main system, while working or playing on the virtual machine.
This is a project being started from the grassroots by a crazy cat lady. Feel free to help develop our new Machine, "Root" if you can. I will begin running isos tomorrow
Oh, and There's This News Today~!

(Help Needed) Teclast P25T - Unofficial - [MOD] [ROOT] [ROM] [KERNEL]

TLDR:
I bought a cheap Teclast P25T tablet with slim-to-no support for customization/modding/rooting/etc. I really would appreciate any help I could get and will be very responsive, listen intently, and be very descriptive in my feedback. I consider myself very tech-savvy, but I am no expert in coding/software modding/android modding/hacking in general. In fact, I would say I'm rather new to this realm, and that is why I have come to ask for help from THE BEST, the XDA community.
(Short) Device Specs and Options:
Manufacturer: Teclast
Model: P25T
ID: P9A6
USB debugging: Enabled
OEM unlocking: Enabled
Why I bought the Device:
I recently bought a new Android tablet rather impulsively I will admit, my purpose for the device was to disable the bootloader and root the tablet for fun, exploration, and ultimately boot a custom Linux operating system that has root privileges for providing defensive network security to prevent and identify threats on free local wifis. This is proving to be a significant challenge for a few reasons.
My Personal Objectives:
Unlock the bootloader
Gain superuser/root privileges
Install Kali and remove the current OS/ROM (not sure what it's called)
Spoiler: Current Project Status:
Current Project Status:
Found the manufacturer's official software/firmware download page: https://en.teclast.com/pages/firmwaredownload
The RevDev_Tool has a "config.ini" file with an option under [Language] for changing the software language.
Change "Selected=1" to "Selected=2"
*Note i have no idea how to use this tool and the tool was not able to identify my device was plugged in
Found the official youtube channel and a 5-year-old video where they show how to "flash" the device
Official page: https://www.youtube.com/@TeclastOfficial
Title: "Teclast Root Process for Android Tablet"
Multiple comments state that this video does not in fact show any actual rooting of the device shown, but rather a way to "flash"
The video shows software that does not appear to be in the manufacturer's firmware folder when I downloaded the files from the official firmware page. (I made sure to use my device "ID": P9A6)
The software in the video (SCP_Flash_Tool) I was able to track down: https://spflashtool.com/
I downloaded platform tools & SamFW_Tool
I can see the device under ./adb devices, but not ./fastboot devices
research indicates it's likely a driver issue.
I have attempted to solve the issue but am yet to do so, and now I likely need to uninstall drivers to get a clean install since I have several drivers installed.
./adb reboot bootloader
The device turns off, turns on to the booting screen, *stops* (I have waited up to 10 minutes)
I then need to turn the device on/off 3 times to get to boot up
Using SamFW Tool I rebooted into [FASTBOOT] Recovery and was greeted with the "No Command" text and the android on its back with the caution logo image that is common
Loading into custom boot settings via external buttons & factory reboot
nothing has worked that I have tried:
Turn device off, then hold volume down + Power, *device boots normally*
Turn the device off, hold both volume keys + plug it into the computer, *Device boots normally*
In settings, I was able to locate the Factory Reboot option and was able to reboot
The device loaded a custom reboot screen before loading into the user setup process
the device performed a factory reset successfully
Spoiler: (Long) Device Specs:
(Long) Device Specs: (SamFW Tool 4.6)
I (REDACTED) some of the info I believed to be private. let me know if any of this is relevant to assisting me.
Device information
Model : P25T_ROW
Brand : Teclast
Device name : P25T_Y_ROW
Product name : P25T_Y_ROW
CPU : rk30sdk
Platform : rk356x
CPU Arch : arm64-v8a
Serial number : (REDACTED)
Software information
Build : V1.00_20221212
Version : 20220914
Build date : Mon Dec 12 11:53:52 CST 2022
Fingerprint : Teclast/P25T_Y_ROW/P25T_Y_ROW:12/SQ1D.211205.016.A5/20220914:user/release-keys
Security patch : 2022-09-05
Android version : 12
Android SDK : 32
Device status
USB : mtp,adb
Timezone : Asia/Shanghai
Language : en-US
Device state : locked
Network type : Unknown
Android ID : (REDACTED)
Wifi Address : (REDACTED)
Root status
Shell SU : NO
Binary Magisk : NO
Binary SU : NO
App Magisk : NO
App SuperSU : NO
Spoiler: Developer Menu Screenshots:
Developer menu screenshots:
{
"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"
}
Comments:
Hello, XDA community, I am new to the forums and did my best to try to properly label my question thread, post in the correct forum, and provide relevant info in this description. If I should repost, or modify the thread to comply or better communicate my needs and question I would be more than happy to do so. I apologize if my terminology and knowledge make it difficult to understand what my needs are, but I will be carefully reviewing all replies and will make sure to take notes and incorporate all feedback into my understanding.

I'm not familiar with that device, sounds like a cheap Chinese knockoff.
Have you tried the standard ADB commands to unlock the bootloader?
If you haven't already, download SDK Platform Tools 33.0.3, you can find it here at the top of the thread. Do not use 34.x+ as there's some rather fatal issues.
Extract the Platform Tools folder, launch a command window in the folder (where you see adb.exe and fastboot.exe), connect your tablet via USB and run adb devices
If it has to start the daemon, simply run the command again, and ensure you've authorized ADB on your device (you should get a popup about authorizing the PC). You should see the serial number of your device appear under adb devices
Next, reboot to bootloader: adb reboot bootloader. If you can, post a photo of the screen with the serial number redacted. Try to command bootloader unlock: fastboot flashing unlock
You may also need to use fastboot flashing unlock-critical
You should get a message on the screen confirming you want to unlock the bootloader. Proceeding will wipe data.
Once the bootloader is unlocked, you would be able to flash custom images. The best way to root is to use Magisk; see these instructions. The easiest way will be to extract the factory firmware and look for boot.img; patch this in Magisk on the device, then reboot to bootloader again and flash the patched image to /boot.

V0latyle said:
I'm not familiar with that device, sounds like a cheap Chinese knockoff.
Have you tried the standard ADB commands to unlock the bootloader?
If you haven't already, download SDK Platform Tools 33.0.3, you can find it here at the top of the thread. Do not use 34.x+ as there's some rather fatal issues.
Extract the Platform Tools folder, launch a command window in the folder (where you see adb.exe and fastboot.exe), connect your tablet via USB and run adb devices
If it has to start the daemon, simply run the command again, and ensure you've authorized ADB on your device (you should get a popup about authorizing the PC). You should see the serial number of your device appear under adb devices
Next, reboot to bootloader: adb reboot bootloader. If you can, post a photo of the screen with the serial number redacted. Try to command bootloader unlock: fastboot flashing unlock
You may also need to use fastboot flashing unlock-critical
You should get a message on the screen confirming you want to unlock the bootloader. Proceeding will wipe data.
Once the bootloader is unlocked, you would be able to flash custom images. The best way to root is to use Magisk; see these instructions. The easiest way will be to extract the factory firmware and look for boot.img; patch this in Magisk on the device, then reboot to bootloader again and flash the patched image to /boot.
Click to expand...
Click to collapse
It is truly the CHEAPEST of the Chinese knockoffs . Regardless, I still spent $130 on the thing including the accessories and shipping. Also, I think there needs to be more documentation on how to mod these things even though its highly unadvised to purchase one lol. Also I'm just a stubborn SOB, so I want to try my best to crack this nut.
So yes, I had tried the standard adb commands. But I had not tried the specific version of Platform Tools you recommended until now. Here is some feedback on your reply.
Spoiler: Feedback and More info:
So I went and grabbed those Platform Tools to begin with then I launched Powershell from the Platform Tools directory. I first ran the "devices commands to see if I was able to fetch a device using "fastboot devices". Unfortunately I am still facing an issue with this device being assigned the wrong drivers. More on that below this image:
Then I ran the other suggested commands you provided:
Research indicates that the "< waiting for any device >" pause (even when device is connected) is a symptom of incorrect driver installations for the device in question. Specifically the "Android Bootloader Interface" model within the "android_winusb.inf" driver options.
Something odd about the device is that it is very determined to remain a "Portable Device"classification and even when I begin appending permissions from TrustedInstaller and deleting the non-windows drivers it remains in this classification. I have also tried uninstalling it from device manager, and from the printers and devices menu with no success of reassigning it as of yet.
Here are the specific drivers that are assigned to it currently:
As you will be reading this I am working to resolve this issue first. Until advised otherwise.
Updates on this process:
Driver Signature Enforcement has been disabled, pc rebooted with no effect for assigning "android_winusb.inf" adb drivers
Thank you for your time and consideration!

TheFuzzyFuzz said:
It is truly the CHEAPEST of the Chinese knockoffs . Regardless, I still spent $130 on the thing including the accessories and shipping. Also, I think there needs to be more documentation on how to mod these things even though its highly unadvised to purchase one lol. Also I'm just a stubborn SOB, so I want to try my best to crack this nut.
So yes, I had tried the standard adb commands. But I had not tried the specific version of Platform Tools you recommended until now. Here is some feedback on your reply.
Spoiler: Feedback and More info:
So I went and grabbed those Platform Tools to begin with then I launched Powershell from the Platform Tools directory. I first ran the "devices commands to see if I was able to fetch a device using "fastboot devices". Unfortunately I am still facing an issue with this device being assigned the wrong drivers. More on that below this image:
View attachment 5894161
Then I ran the other suggested commands you provided:
View attachment 5894163
Research indicates that the "< waiting for any device >" pause (even when device is connected) is a symptom of incorrect driver installations for the device in question. Specifically the "Android Bootloader Interface" model within the "android_winusb.inf" driver options.
Something odd about the device is that it is very determined to remain a "Portable Device"classification and even when I begin appending permissions from TrustedInstaller and deleting the non-windows drivers it remains in this classification. I have also tried uninstalling it from device manager, and from the printers and devices menu with no success of reassigning it as of yet.
View attachment 5894175
Here are the specific drivers that are assigned to it currently:
View attachment 5894179
As you will be reading this I am working to resolve this issue first. Until advised otherwise.
Updates on this process:
Driver Signature Enforcement has been disabled, pc rebooted with no effect for assigning "android_winusb.inf" adb drivers
Thank you for your time and consideration!
Click to expand...
Click to collapse
Yeah looks like you'd have to install the correct driver. ADB drivers are usually generic, fastboot drivers are device specific.
When you commanded the device to reboot to bootloader, what was on the device screen?

V0latyle said:
Yeah looks like you'd have to install the correct driver. ADB drivers are usually generic, fastboot drivers are device specific.
When you commanded the device to reboot to bootloader, what was on the device screen?
Click to expand...
Click to collapse
I get the standard boot screen, It stops on this screen and then does nothing. Also something else kind of weird is that it will refuse to boot back up if it is NOT plugged in to my computer. And even WEIRDER is that i have only been able to charge/data transfer with the factory cord it came with. Which is, concerning to say the least, and kind of perplexing:
Also, I think I just found the solution to the driver issue. I just need to figure out how to use this tool I found:
Device manager for Windows 10 / 8 / 7 / Vista / XP
DevManView is an alternative to the standard Device Manager of Windows, which displays all devices and their properties in flat table, instead of tree viewer.
www.nirsoft.net
It was recommended by this reference article:
Device Manager Alternative: 3 Picks You Didn't Know About
Looking for a device manager alternative? If so, explore our top three choices so you can have more variety next time you experience issues.
windowsreport.com