Hi all,
yesterday I succeeded in rooting the new ASUS MeMo Pad HD 7.
Model-Number: ME173X
Android version: 4.2.1
Kernel version: 3.4.5
HD 7 Build: ME173X_WW_User_4.2.1.75146_20130523 release keys
PC operating system: Win.. XP
USB-Driver I used (but there's WdfCoInstaller.dll missing, which I already had on my PC):
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME172V/ASUS_Android_USB_drivers_for_Windows_20130415.zip
Maybe this more complete package would work, too (I didn't try that):
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/ASUS_Android_USB_drivers_for_Windows.zip
Method to root is by using motochopper.
You can follow the next steps in general as described in
http://forum.xda-developers.com/showpost.php?p=40129120&postcount=1
One important thing:
motochopper didn't recognize my HD7 at once, so I did the following
(while being connected with PC via USB and motochopper waiting for device):
While USB debugging activated, go to USB settings an connect it as
integrated CD drive. motochopper will automatically recognize it
and continue with rooting process.
And last but not least:
As always, all you do is your own risk and I'm not responsible for any damage.
Good luck
-----------------------------
EDIT 2013-07-06:
Above procedure for rooting works with the new HD7 update, too (but you have to re-root after the update).
Build version after the update: ME173X_WW_user_4.2.2.51129_20130619 release-keys
-----------------------------
Description for Linux users:
- use motochopper package from link above
- login as root
- extract package
- open console and change to directory where you extracted the package
- chmod +x adb.linux
- chmod +x run.sh
- Check your HD7 will be recognized:
-> ./adb.linux status-window
-> shows "State: unknown"
-> connect HD7 (with usb debugging enabled, connecting as MTP device)
-> above started adb command should show now "State: device"
-> HD7 recognized - greatful, you're ready
-> press Strg-C to abort
- (optional) for more information about your HD7 you can enter: ./adb.linux devices -l
-> this should show something like: D6OKCXXXXXXX device usb:1-3 product:WW_memo model:ME173X device:ME173X
- ./run.sh
-> follow instructions on screen
- you're done
-----------------------------
EDIT 2013-07-16:
Above procedure for rooting works with new HD7 update (but you have to re-root after the update).
Build version after the update: ME173X_WW_user_4.2.2.91525_20130711 release-keys
Thank you very much! I had it attached as a camera, worked fine as well. ^^
ASUS memopad HD 7
quaddler said:
Hi all,
yesterday I succeeded in rooting the new ASUS MeMo Pad HD 7.
Click to expand...
Click to collapse
Thats awesome, but how did you already purchase this when it hasnt hit the stores yet? I cant wait to replace my MSI Winpad with this bad boy
RELLC said:
Thats awesome, but how did you already purchase this when it hasnt hit the stores yet? I cant wait to replace my MSI Winpad with this bad boy
Click to expand...
Click to collapse
Amazon.de apparently received an early batch and sent them out immediately. I was surprised as well, target date was 10 July to 1 August and it arrived 25 June^^
SoWhy said:
Amazon.de apparently received an early batch and sent them out immediately. I was surprised as well, target date was 10 July to 1 August and it arrived 25 June^^
Click to expand...
Click to collapse
sooo jealous. :highfive:
SoWhy is right.
I bought mine last Thursday at amazon.de.
There were also some dealers on Amazon‘s marketplace who had some.
hi
it is possible to enable usb host with the root on the memo pad hd 7?
Memo Pad HD7
Thanks...
Have been looking for Root ever since I got one Device on Friday.
Root seems to be working fine.
By the way - Saturn Germany got stock now as well (blue and white back) - bought 3 more today.
The MircoSD is taking 32GB straight from my Galaxy Note 10.1 - the resolution is really cool and no errors or problems.
I personally can do no more than highly recommend the Tablet.
Change - just made a firmware update to 4.2.2 - root is gone...
Sky0ne said:
Change - just made a firmware update to 4.2.2 - root is gone...
Click to expand...
Click to collapse
Thanks for reporting that.
Do you mean that rooting is no more possible with 4.2.2 firmware?
Current version 4.2.1 is somewhat buggy. Launcher FC quite often. It would make sense to download 4.2.2 but it would be unusable for me without root
LaizyJumper said:
Thanks for reporting that.
Do you mean that rooting is no more possible with 4.2.2 firmware?
Current version 4.2.1 is somewhat buggy. Launcher FC quite often. It would make sense to download 4.2.2 but it would be unusable for me without root
Click to expand...
Click to collapse
Well, I wouldn't say not possible. It's just that I couldn't manage to get it done de same way so far.
The 4.2.2 update is pretty neat. The tablet works more stable now. The home screen rotates and the display is much brighter.
Just some update features I discovered.
As of root I was hoping that someone would discover some different, more stable way - like CF-Autoroot on the Nexus 7.
I‘m a little busy at the moment.
Hope to have a look on 4.2.2 on weekend.
Sky0ne said:
Well, I wouldn't say not possible. It's just that I couldn't manage to get it done de same way so far.
The 4.2.2 update is pretty neat. The tablet works more stable now. The home screen rotates and the display is much brighter.
Just some update features I discovered.
As of root I was hoping that someone would discover some different, more stable way - like CF-Autoroot on the Nexus 7.
Click to expand...
Click to collapse
Does it show the Android version 4.2.2 in System information? Or is it still 4.2.1 (and it says ME173X_WW_user_4.2.2.51129_20130619 in build number)?
I have Android version 4.2.1 and build number mentioned above. And I got it rooted without any problems on Linux (the way it is described in OP).
LaizyJumper said:
Does it show the Android version 4.2.2 in System information? Or is it still 4.2.1 (and it says ME173X_WW_user_4.2.2.51129_20130619 in build number)?
I have Android version 4.2.1 and build number mentioned above. And I got it rooted without any problems on Linux (the way it is described in OP).
Click to expand...
Click to collapse
Funny - you're right... :laugh: Didn't see that one.
Got exactly the same build no (ME173X_WW_user_4.2.2.51129_20130619 release-keys) and above Android Version 4.2.1...
I am running Linux too - couldn't make root so far - did you use some different settings?
Sky0ne said:
Funny - you're right... :laugh: Didn't see that one.
Got exactly the same build no (ME173X_WW_user_4.2.2.51129_20130619 release-keys) and above Android Version 4.2.1...
I am running Linux too - couldn't make root so far - did you use some different settings?
Click to expand...
Click to collapse
Nothing special... The only trouble I had in the beginning was to get ADB responding properly. I have different versions of adb utilities on my PC. Other ones did not work, the one in motochopper package worked fine. I was using the original motochopper files. I had to use root rights (running script with sudo) to get it working. Might be that this is the showstopper for you
Full sequence should be something like this:
* Switch on developer mode (multiple clicks in about box on build number).
* Find developer options in the setup menu. Switch on USB debuging.
* Plug in the USB cable, try different USB modes (I think I made it using cd-rom mode, modes can be changed in storage settings under advanced "USB computer connection" menu from the top-right corner menu icon).
* Run the motochopper script with sudo.
LaizyJumper said:
Nothing special... The only trouble I had in the beginning was to get ADB responding properly. I have different versions of adb utilities on my PC. Other ones did not work, the one in motochopper package worked fine. I was using the original motochopper files. I had to use root rights (running script with sudo) to get it working. Might be that this is the showstopper for you
Full sequence should be something like this:
* Switch on developer mode (multiple clicks in about box on build number).
* Find developer options in the setup menu. Switch on USB debuging.
* Plug in the USB cable, try different USB modes (I think I made it using cd-rom mode, modes can be changed in storage settings under advanced "USB computer connection" menu from the top-right corner menu icon).
* Run the motochopper script with sudo.
Click to expand...
Click to collapse
Thanks a lot - have been trying that already - not working with mine...
Sky0ne said:
Thanks a lot - have been trying that already - not working with mine...
Click to expand...
Click to collapse
Have you tried running adb.linux separately? Does it connect?
Run it first with "kill-server" argument and then "shell", for example.
If you get shell access then you should be able to root it. If not then there is something wrong in your pc setup or tab settings.
I assume it worked before you updated your HD7.
Hello everybody,
as promised I got some time to deal with the update.
In short, rooting with this update works, too (but you have to re-root after the update).
Build version after the update shows: ME173X_WW_user_4.2.2.51129_20130619 release-keys
I updated post #1 and put some additional information for linux users.
Regards
quaddler
My Memo HD7 arrived yesterday an it is great ! (amazon.de / germany)
Rooting procedure worked on Win 7 without installing new drivers very easy.
To turn on Developer Mode to switch USB debugging Mode on:
Build Number:
ME173X_WW_user_4.2.1.75146_20130532
Open “Settings”.
Scroll to the bottom and tap “About phone” or “About tablet”.
At the “About” screen, scroll to the bottom and tap on “Build number” seven times.
You will see a “You are now a developer!” message pop up, then you know you have done it correctly.
Done!
You can now enable/disable it under “Settings” -> “Developer Options” -> “Debugging” ->” USB debugging”.
Then just run "run.bat" from motochopper (http://forum.xda-developers.com/showpost.php?p=40129120&postcount=1) and
follow the instructions.
Sorry for offtopic but any info what's new in this update 4.2.2? I'm from Bulgaria and don't have update yet. l'm still with first version ME173X_WW_User_4.2.1.75146_20130523.
Sent from my ME173X using Tapatalk 2
update
Hello,
I have a question:
After the root any new Update can be install over the air?
Hi guys, I'm modified the resources in framework-res.apk on my Fire HD 8 2018 for enabling the features. All features has been disabled by the manufacturer Amazon so just modifying the resources such as bools.xml and integers.xml to enable all features.
The framework-res.apk in /system/framework/, the package name is android, the app name is System that renamed by Amazon, the original app name from stock AOSP is Android System
Features of modified framesork-res.apk:
-> Replaced the value of config_lowBatteryWarningLevel to 15 in res/values/integers.xml - to detect the low battery level to 15%
-> Replaced the value of config_longPressOnHomeBehavior to 2 in res/vales/integers.xml - to access the assist intent such as Google Assistant
-> Replaced false with true in res/values/bools.xml:
----> config_supportsMultiWindow - to make your Fire tablet to access the multi-window such as split-screen, freeform (resizable activity) and PiP for prevent kill the activities when in the background. Can be enable the resizable activity in developer options.
----> config_sustainedPerformanceModeSupported - to make your Fire tablet to access the sustained performance mode for make long-running apps and fast performance.
----> config_useRoundIcon - to make a circular app icon on your Fire tablet like a Google Pixel.
Requirements:
-> Rooted Fire HD 8 2018 running Fire OS 6.3.0.1, want to root from @xyz` or another link for new rooting method from @k4y0z
-> ADB for Windows, MacOS or Linux from Android SDK Manager
-> ADBD Insecure from @Chainfire: https://forum.xda-developers.com/showthread.php?t=1687590&page=27
-> Transferrable micro USB cable
-> Modded framework-res.apk under the post
WARNING
This is an experimental operations, can be got a boot-loop (brick) your Fire tablet after you accessing the invalid operations
Let's Get Started
1. Go to Settings -> Device Options -> About Fire tablet -> Serial Number and tap the several number until the Developer Options appears under About Fire tablet menu.
2. Go to Developer Option -> USB Debugging and enable it.
3. Connect your Fire tablet to your PC, Open Command Prompt or Microsoft PowerShell for Windows in your PC and approve the USB device
4. Verify the attached devices
Code:
adb devices
5. Remount the partition
Code:
adb remount
NOTE: If you got a result, Success or not, Do not run.
6. Push the modded framework-res.apk to /system/framwork/
Code:
adb push path/to/framework-res.apk /system/framwork/
7. Reboot your Fire tablet
Code:
adb reboot
8. Reset your launcher by clearing the app data in settings
Done! You have a modded framwork-res.apk on your Fire HD 8 2018. After booting your Fire tablet is completed, give a thanks and post the screenshot.
The Fire tablet is getting to boot-loop or brick, get the solution from @xyz`, this link or post the solution.
MOD EDIT: Link removed because in this cases of bricking or boot-looping. Link will be back after maintenance.
Updated in March 26, 2020
Being on nougat you are very lucky. You get to play with some other things like multi-window. I really wish the HD 10 would get a nougat update.
AmznUser444 Dev said:
. 5. Remount the partition
Click to expand...
Click to collapse
Doh, was hoping it was gonna be possible with the temp root solution! Now I gotta break out my Linux rig. Super excited for multi window!
AmznUser444 Dev said:
Hi guys, I'm modified the resources in framework-res.apk on my Fire HD 8 2018 for enabling the features. All features has been disabled by the manufacturer Amazon so just modifying the resources such as bools.xml and integers.xml to enable all features.
The framework-res.apk in /system/framework/, the package name is android, the app name is System that renamed by Amazon, the original app name from stock AOSP is Android System
Features of modified framesork-res.apk:
-> Replaced the value of config_lowBatteryWarningLevel to 15 in res/values/integers.xml - to detect the low battery level to 15%
-> Replaced the value of config_longPressOnHomeBehavior to 2 in res/vales/integers.xml - to access the assist intent such as Google Assistant
-> Replaced false with true in res/values/bools.xml:
----> config_supportsMultiWindow - to make your Fire tablet to access the multi-window such as split-screen, freeform (resizable activity) and PiP for prevent kill the activities when in the background. Can be enable the resizable activity in developer options.
----> config_sustainedPerformanceModeSupported - to make your Fire tablet to access the sustained performance mode for make long-running apps and fast performance.
----> config_useRoundIcon - to make a circular app icon on your Fire tablet like a Google Pixel.
Requirements:
-> Rooted Fire HD 8 2018 running Fire OS 6.3.0.1, want to root from @xyz`
-> ADB for Windows, MacOS and Linux from Android SDK Manager
-> Transferrable micro USB cable
-> Modded framework-res.apk under the post
WARNING
This is an experimental operations, can be got a boot-loop (brick) your Fire tablet after you accessing the invalid operations
Let's Get Started
1. Go to Settings -> Device Options -> About Fire tablet -> Serial Number and tap the several number until the Developer Options appears under About Fire tablet menu.
2. Go to Developer Option -> USB Debugging and enable it.
3. Connect your Fire tablet to your PC, Open Command Prompt or Microsoft PowerShell for Windows in your PC and approve the USB device
4. Verify the attached devices
Code:
adb devices
5. Remount the partition
Code:
adb remount
NOTE: If you got a result, Success or not, Do not run.
6. Push the modded framework-res.apk to /system/framwork/
Code:
adb push path/to/framework-res.apk /system/framwork/
7. Reboot your Fire tablet
Code:
adb reboot
8. Reset your launcher by clearing the app data in settings
Done! You have a modded framwork-res.apk on your Fire HD 8 2018. After booting your Fire tablet is completed, give a thanks and post the screenshot.
The Fire tablet is getting to boot-loop or brick, get the solution from @xyz`, this link or post the solution.
Download modded framework-res.apk from Google Drive link
Click to expand...
Click to collapse
Thanks. I tried this with my rooted Fire HD8 2018, but when I connect the tablet to Windows PC, it doesn't show up as a device on the PC. Instead, the Fire says it's connected to a low power charger.
CheapFire said:
Hi guys, I'm modified the resources in framework-res.apk on my Fire HD 8 2018 for enabling the features. All features has been disabled by the manufacturer Amazon so just modifying the resources such as bools.xml and integers.xml to enable all features.
The framework-res.apk in /system/framework/, the package name is android, the app name is System that renamed by Amazon, the original app name from stock AOSP is Android System
Features of modified framesork-res.apk:
-> Replaced the value of config_lowBatteryWarningLevel to 15 in res/values/integers.xml - to detect the low battery level to 15%
-> Replaced the value of config_longPressOnHomeBehavior to 2 in res/vales/integers.xml - to access the assist intent such as Google Assistant
-> Replaced false with true in res/values/bools.xml:
----> config_supportsMultiWindow - to make your Fire tablet to access the multi-window such as split-screen, freeform (resizable activity) and PiP for prevent kill the activities when in the background. Can be enable the resizable activity in developer options.
----> config_sustainedPerformanceModeSupported - to make your Fire tablet to access the sustained performance mode for make long-running apps and fast performance.
----> config_useRoundIcon - to make a circular app icon on your Fire tablet like a Google Pixel.
Requirements:
-> Rooted Fire HD 8 2018 running Fire OS 6.3.0.1, want to root from @xyz`
-> ADB for Windows, MacOS and Linux from Android SDK Manager
-> Transferrable micro USB cable
-> Modded framework-res.apk under the post
WARNING
This is an experimental operations, can be got a boot-loop (brick) your Fire tablet after you accessing the invalid operations
Let's Get Started
1. Go to Settings -> Device Options -> About Fire tablet -> Serial Number and tap the several number until the Developer Options appears under About Fire tablet menu.
2. Go to Developer Option -> USB Debugging and enable it.
3. Connect your Fire tablet to your PC, Open Command Prompt or Microsoft PowerShell for Windows in your PC and approve the USB device
4. Verify the attached devices
5. Remount the partition
NOTE: If you got a result, Success or not, Do not run.
6. Push the modded framework-res.apk to /system/framwork/
7. Reboot your Fire tablet
Thanks. I tried this with my rooted Fire HD8 2018, but when I connect the tablet to Windows PC, it doesn't show up as a device on the PC. Instead, the Fire says it's connected to a low power charger.
Click to expand...
Click to collapse
Use the transferrable USB cable, Enable USB Debugging in developer options and verify the attached devices
Code:
adb devices
So I tried to put this on my Fire HD 8 2018, but now my tablet is stuck booting up the OS.
Malonepwn said:
So I tried to put this on my Fire HD 8 2018, but now my tablet is stuck booting up the OS.
Click to expand...
Click to collapse
You going to have to extract your firmware from the zip and take the framework out of the system and manually put it back on your tablet through TWRP. Or you're going to have to reflash back to stock firmware and start all over again.
Sent from my Amazon KFSUWI using XDA Labs
I just flashed Lineage to it. I just thought I'd post in here to let people know there are potential issues with this modification.
Malonepwn said:
So I tried to put this on my Fire HD 8 2018, but now my tablet is stuck booting up the OS.
Click to expand...
Click to collapse
That happened to me, too. It took me a couple of tries - OK, maybe four LOL - going through steps 0-9 before I got it right. Once you can boot to TWRP with the volume down button you are most of the way there. From there you can reflash 6300 and Magisk. Good luck.
I can confirm that there are issues with this modification. I attempted to install this by replacing the file with a custom magisk module. This only resulted in the infinite booting OS problem that others above have described. After disabling the module, every single non-system app on my device lost permissions and had to be reinstalled.
Has anyone confirmed this working with LineageOS 14.1 on the HD8? I have tried a modded framework-res.apk and infinite loop for me too.
sd_dracula said:
Has anyone confirmed this working with LineageOS 14.1 on the HD8? I have tried a modded framework-res.apk and infinite loop for me too.
Click to expand...
Click to collapse
This would only apply to FireOS.
If you're running Lineage, why would you even bother with this?
If you're using the LineageOS custom ROM. Do not overwrite copy the modded framework-res.apk
The modded framework-res.apk for the Fire OS 6.3.0.1. We don't use 6300.zip from @xyz`
Coming Soon: Modded framework-res.apk for Fire OS 6.3.0.0 and 6.3.1.2
AmznUser444 Dev said:
If you're using the LineageOS custom ROM. Do not overwrite copy the modded framework-res.apk
The modded framework-res.apk for the Fire OS 6.3.0.1. We don't use 6300.zip from @xyz`
Coming Soon: Modded framework-res.apk for Fire OS 6.3.0.0
Click to expand...
Click to collapse
Kctucka said:
This would only apply to FireOS.
If you're running Lineage, why would you even bother with this?
Click to expand...
Click to collapse
Just wanted to enable tap to wake on the Fire HD8
AmznUser444 Dev said:
If you're using the LineageOS custom ROM. Do not overwrite copy the modded framework-res.apk
Click to expand...
Click to collapse
Then how to update the framework-res.apk for lineageOS with my edited one?
sd_dracula said:
Then how to update the framework-res.apk for lineageOS with my edited one?
Click to expand...
Click to collapse
I don't have a modded framework-res.apk for LineageOS. I'm in FireOS, I don't have a LineageOS ported.
Did this actually work for anyone? I'm on 6.3.0.1 stock rooted and replaced framework with this, now bootloop like others have reported. Any successful attempts?
I hope my TWRP backup is ok
Edit: TWRP backup restored but kept freezing on a blank screen a few seconds after boot. I don't know why though might have been something else, maybe Viper. Anyway had to reflash 6.3.0.0 and root and set the whole thing up again
wanting multi window and home google now for 6.3.1.4 please confirm it working with rooted 6.3.1.4
Hello, as there has been no answer, I pulled the apk from my device, decompiled with apktool and modified the values listed myself and recompiled with apktool.
I am not sure how to sign with the amazon key before pushing it to my device, can you help?
ameeno said:
Hello, as there has been no answer, I pulled the apk from my device, decompiled with apktool and modified the values listed myself and recompiled with apktool.
I am not sure how to sign with the amazon key before pushing it to my device, can you help?
Click to expand...
Click to collapse
Re-signing the APK will result in failure even on a rooted device especially when you're talking about the framework or any specific application signed by Amazon.
You have to open the original APK and the one you just recompiled in an archive manager like 7-Zip. Open them up as an archive side by side. Then take from the new APK the res folder and the resource file and drag them over to the original APK one by one. Then close both file managers. You can then use a root explorer to manually push the original APK back to the device. But you have to be quick and set the permissions quick. If you have custom recovery installed then you can do it manually through TWRP. If you use the app adbd-insecure, you can use 'adb remount' and then use ADB to push the APK.
QLink Scepter 8 TabletBy Hot Pepper Mobile
{
"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"
}
Bootloader Unlocking
& Rooting Guide
For Gen 1 & Gen 2 Models
TABLET MODELS & VARIANTS:
For those members familiar with the firmware restoration thread, there are a total of four model variants of the QLink Scepter 8 tablet: two variants of the Gen 1 model, and two variants of the latest Gen 2 model. Determining which Scepter 8 you have is a very simple two-part check. First, if you don't already know your Android OS version, go to device Settings> About tablet, and locate your Android version. If you are running Android 11 (Go Edition), you have the original Gen 1 model. If you are running Android 12 (Go Edition), your tablet is the latest Gen 2 model. Secondly, you will need to locate the device S/N in order to determine your tablet variant. Your S/N is printed on the manufacturer's label affixed to the exterior of the tablet's rear housing. From the Android OS, you can also locate your S/N by opening device Settings>About tablet>Model. Regardless of whether you have the Gen 1 or the Gen 2, the first two letters of your S/N will be either CF or MD. This is the codification of your tablet variant. To alleviate some of the legwork of rooting, and to keep this thread simple to follow, I have provided boot images pre-patched for Magisk v25.2 systemless root support. I have categorized the download links for each of the boot images in accordance with the respective model and S/N variant. To avoid potential bugs, instabilities, boot loops and the like, it is crucial that you download the boot image that corresponds with your model & variant. OVERVIEW:
This guide outlines step-by-step instructions for unlocking the bootloader and rooting all variants of the Gen 1 & Gen 2 QLink Scepter 8 tablet. This guide also includes a detailed section on properly installing the ADB, fastboot, & USB device drivers on your Windows PC or laptop, as well as steps to troubleshoot & manually update these drivers in the event the tablet is not being recognized while in fastboot mode.
DISCLAIMER:
Unlocking your bootloader and rooting your device are both procedures that carry inherent risks. Because these procedures involve modifying the device from it's stock factory configuration, it is possible to corrupt, damage, or even render your tablet completely inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your device, therefore absolving me of any liability in the event something goes south. I have, however, tested these guides and feel confident that things will go smoothly as long as you follow the instructions carefully. Moreover, I encourage all members to read the instructions fully before starting the steps, in order to first gain a fundamental understanding of the concepts and methods involved.
PLEASE PLAY NICE & FOLLOW XDA RULES:
This thread was created with the intent of being a noob-friendly forum. This simply means that new and inexperienced members are fully welcome here, and will be provided with extra guidance and assistance if needed. Please keep in mind that XDA is a global community of developers, enthusiasts and device users. As such, and although English is the only permitted language in the forums & threads, not all members speak English as their first language, and often rely on text translation tools when asking questions & posting. Accordingly, it is very common for words to be misconstrued, meanings to be misinterpreted, and the context as a whole lost in translation. I ask members to be patient, compassionate and respectful to others on this thread. Those members with the knowledge to do so are urged and asked to help newer members, and recall back when you were new here and others helped you.
Please help me with keeping this thread on point by ensuring that all subject matter herein be kept relevant to the topics of rooting and OEM unlocking the QLink Scepter 8. Any posts about other devices or subject matter run afoul of XDA rules and are subject to removal by moderators -- and potential sanctions imposed upon the offending member. Moreover, an on-topic thread keeps things organized and easier to follow. Thank you for your consideration.
PREREQUISITES:
To unlock the bootloader and root the QLink Scepter 8 tablet, you will need a laptop or PC running on Windows 7/8.1/10/11. (A Mac or Linux machine can also be used. For purposes of this guide, however, I am focusing on a Windows setup.) You will also need the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable. Last but not least, you will need to install compatible USB device drivers for ADB & Fastboot on your PC/laptop. I have included the 15-Second ADB Driver Installer below, under the DOWNLOADS section. This Installer will configure ADB & Fastboot system-wide, and installs the universal Google USB device drivers. I would encourage members to first read the instructions in their entirety prior to actually starting the guide.
•INSTALLING USB DEVICE DRIVERS•
This section is included to install and configure ADB, Fastboot and the proper USB device drivers on your Windows computer. This section can also be used to troubleshoot and fix issues involving your tablet not being recognized by Windows while connected in fastboot mode. If you have already installed the ADB & Fastboot tools (& the proper USB device drivers), and you are not experiencing fastboot recognition issues, you may skip this section and proceed to the bootloader unlocking section.
Many members have reported issues with device recognition while in fastboot mode. I have also noticed a persistence problem with Windows drivers on this tablet. I can manually update the driver using Windows Device Manager, enabling fastboot recognition; yet, once the tablet is disconnected from my PC the updated driver does not always persist, requiring a manual driver update each time fastboot mode is needed. Follow these steps to enable fastboot recognition of your device.
• 1. If you have not yet done so, install the 15-Second ADB Installer from the link below on your Windows PC or laptop. Open the utility and follow the prompts to install the ADB & Fastboot drivers. Next, opt to install ADB system-wide. Lastly, you will be prompted to install the Google USB device drivers. Select Y and install them. You should see an interface informing you that the drivers were successfully installed. NOTE: If you get a warning notification that the drivers are unsigned, select the option to install anyway;
• 2. With your tablet powered off, hold the Power and Volume Down buttons simultaneously until the QLink logo appears, at which time you release the Power button but continue holding Volume Down. When a green Android graphic appears on your display, you are in fastboot mode;
• 3. Connect your tablet to your Windows machine using the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable;
• 4. Open a command window in the path of your ADB/Fastboot directory. Execute this command:
Code:
fastboot devices
If properly connected, the command window will return an alphanumeric string which is synonymous with your tablet serial number. If this occurs, you are finished with this section and may proceed to the instructions for unlocking the bootloader/rooting. If the command window displays Waiting on Any Device, or if your serial number is not displayed, continue with the following steps;
• 5. Keeping your device connected to your Windows PC/laptop, right click your Windows Start icon and select Device Manager. Locate your tablet in the menu. It will likely be located under either the Portable Devices or Android Device heading;
• 6. Right click your device and select Update Driver. Next, select Browse My Computer for Drivers. On the next screen choose the option for Let Me Pick From a List... Now you will see a list of drivers to select from. Depending on the manner in which Windows recognized your tablet in the Device Manager menu, the driver selection menu can vary. If you see an option for Android Device, select that option and then select Android Composite ADB Interface. Or, you may be directly presented with options for Android Bootloader Interface, Android ADB Interface and Android Composite ADB Interface. In any event, choose Android Composite ADB Interface and then click Next. Click Yes in the Update Driver Warning dialogue screen, at which time the drivers will be installed.
• 7. Return to your command window and again execute the fastboot devices command. If your serial number is displayed, your drivers are now properly installed. If you are still experiencing fastboot recognition issues, try using another data sync cable, change USB ports on your computer, and/or reinstall the drivers using the 15-Second ADB Installer.
I. UNLOCKING THE BOOTLOADER:
If you plan on rooting your tablet, this step is mandatory. If your bootloader is already unlocked and you only wish to root your device, skip down to the rooting instructions in the next section below.
WARNING: Unlocking your bootloader forces the device into a factory data reset, which will effectively wipe all saved user data from the device. Make a backup at this point if there are files and media on your tablet that you wish to keep.
INSTRUCTIONS:
1. Enable Developer Options on your tablet by going to device Settings>About tablet and tap Build number approximately seven times. Android will notify you that Developer Options are enabled; this menu will appear under device Settings>System>Advanced.
2. Enable USB Debugging and OEM Unlocking in the Developer Options menu. NOTE: Users have reported the OEM Unlocking option being greyed-out unless you are signed in to your Google account.
3. Now to boot into fastboot mode, and this particular step is extremely important. Android 10 introduced a new fastboot mode for dynamic partitions, known as FASTBOOTD, which is relocated from the bootloader to userspace. This particular fastboot mode supports resizeable partitions within the dynamic scheme, and enables the user to create, resize and delete various logical partitions. However, FASTBOOTD mode cannot be utilized to unlock the bootloader, and will not recognize the unlock command. As such, the user must rely upon legacy fastboot mode in order to unlock the bootloader. From stock recovery mode, you may simply choose the option to reboot to bootloader. DO NOT CHOOSE THE OPTION TO ENTER FASTBOOT, as this option will boot to FASTBOOTD. From the Android OS, you can boot into legacy fastboot mode by executing:
Code:
adb reboot bootloader
Once you see a green Android graphic appear in the center of your display, you are in the correct fastboot mode.
4. Connect your tablet to your PC/laptop using the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable. Next, open a command window in the path of your ADB/Fastboot directory. Check your connection by executing this command:
Code:
fastboot devices
If you are properly connected, the command window will return an alphanumeric string synonymous with your device's serial number. If you do not see this, there is a problem with communications between your tablet and PC/laptop. To troubleshoot the issue, switch to another USB port, try another data sync cable, and/or reinstall the ADB/Fastboot drivers on your PC or laptop. Also, see my instructions above on installing USB device drivers on your Windows computer;
5. Once a proper connection has been verified, execute this command:
Code:
fastboot oem unlock
Once you see the Okay notification in the command window, your bootloader is now unlocked. Execute this command:
Code:
fastboot reboot
Your tablet will now initiate a factory data reset and then reboot into the initial setup for the Android OS.
II. ROOTING THE QLINK SCEPTER 8
Now that the bootloader has been unlocked, rooting this tablet is very straightforward. Again, I have provided pre-rooted boot image files in the DOWNLOADS section for all four models & variants.
INSTRUCTIONS:
A. Gen 1 QLink Scepter 8Android 11 (Go Edition)
NOTE: If your tablet is running Android 12 Go Edition, you're in the wrong place. Skip down to the next section.
1. Download the Gen 1 patched boot image that matches your S/N variant using the links below, and save the file on your PC/laptop in the ADB/Fastboot directory. Note that the file is named patched_boot.img. The flashing command below assumes that you leave this file name unchanged;
2. Go to device Settings>About tablet and tap Build number 7 times or until Developer Options are enabled. (This step is necessary if you unlocked your bootloader using the previous section, due to the factory data reset.) Enable USB Debugging in the Developer Options menu;
3. Power your tablet off. Hold the Power and Volume Down keys simultaneously until the QLink logo appears, at which time you release Power but continue holding Volume Down. The green Android will appear on the display to indicate fastboot mode;
4. Connect your tablet to your PC or laptop using a quality data sync cable. Verify your connection using the instructions in Step 4 of the bootloader unlocking section above;;
5. Once a solid connection is verified, execute these commands:
Code:
fastboot flash boot patched_boot.img
fastboot reboot
NOTE: Your active boot slot should be boot_a. Regardless, the above command flashes your active slot by default, without having to specify slot _a or _b.
Upon reboot, your tablet will be rooted with the latest Magisk systemless root strategy. If you do not see the Magisk app or the placeholder stub in your app drawer, go ahead and download the latest version from the link below and install the APK on your tablet. Open the Magisk app, grant the prompted permissions, and follow any prompts to complete setting up the root environment.
B. Gen 2 QLink Scepter 8Android 12 (Go Edition)
NOTE: If your tablet is running Android 11 Go Edition, you're in the wrong place. Go back to the previous section. .
1.Download the Gen 2 patched boot image that matches your S/N variant and the empty vbmeta.img using the links below, and save the files on your PC/laptop in the ADB/Fastboot directory. Note that the boot image file is named patched_boot.img, and the vbmeta image is named vbmeta.img. The flashing commands below assume that you leave these file names unchanged;
2. Go to device Settings>About tablet and tap Build number 7 times or until Developer Options are enabled. (This step is necessary if you unlocked your bootloader using the previous section, due to the factory data reset.) Enable USB Debugging in the Developer Options menu;
3. Power your tablet off. Hold the Power and Volume Down keys simultaneously until the QLink logo appears, at which time you release Power but continue holding Volume Down. The green Android will appear on the display to indicate fastboot mode;
4. Connect your tablet to your PC or laptop using a quality data sync cable. Verify your connection using the instructions in Step 4 of the bootloader unlocking section above;;
5. Once a solid connection is verified, execute this command:
Code:
fastboot flash boot patched_boot.img
Now, continuing in fastboot mode, you will need to disable dm-verity/Android Verified Boot (AVB) by flashing an empty vbmeta.img via executing the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Next, execute this command to reboot your device:
Code:
fastboot reboot
Upon reboot, your tablet should now be rooted with the Magisk systemless root strategy. If you do not see the Magisk app or the stub placeholder in your app drawer, go ahead and download the latest version from the link below and install it on your tablet. Open the Magisk app, grant the prompted permissions, and follow any prompts to update Magisk and/or complete setting up the root environment.
IMPORTANT NOTE:
In the unfortunate event you have a mishap with rooting your tablet and get stuck in a boot loop, or if your tablet will not otherwise boot into the Android OS, have no worries. My tutorial on firmware restoration for the QLink Scepter 8 will revert your device back to its original stock factory state. You can then return here and give it another try.
QLink Scepter 8 Firmware Restoration Guide
DOWNLOADS:
• 15-Second ADB Installer
• Gen 1 (CF) Patched Boot Image
• Gen 1 (MD) Patched Boot Image
• Gen 2 (CF) Patched Boot Image
• Gen 2 (MD) Patched Boot Image
• Empty vbmeta.img
• Official Magisk Releases / GitHub Repo
THANKS & MENTIONS:
Thanks goes out to Hot Pepper Mobile CEO Shawn Sun and Support Specialist Joshua G for providing stock firmware images for this device.
Also, I wish to recognize and thank @13lack13ox for being a huge help to thread members at times when I was not able.
For some reason, I'm stuck on the part where you have to use the fastboot option. So basically, I got my tablet in fastboot mode (the secondary one with the green android graphic), but when I tried to use the adb function, it doesn't detect my tablet. And also, the command, "fastboot devices" doesn't do anything, and when I try to use "fastboot device" it just says waiting for any device and just... stays there, not detecting my tablet. I tried multiple computers, tried both PowerShell and the command prompt with admin privileges, to no avail. For information, it worked when my tablet was on my tablet is the V9 firmware, but it slightly newer since I just updated to V9_20220224... so maybe that might have something to do with it...
64Star said:
For some reason, I'm stuck on the part where you have to use the fastboot option. So basically, I got my tablet in fastboot mode (the secondary one with the green android graphic), but when I tried to use the adb function, it doesn't detect my tablet. And also, the command, "fastboot devices" doesn't do anything, and when I try to use "fastboot device" it just says waiting for any device and just... stays there, not detecting my tablet. I tried multiple computers, tried both PowerShell and the command prompt with admin privileges, to no avail. For information, it worked when my tablet was on my tablet is the V9 firmware, but it slightly newer since I just updated to V9_20220224... so maybe that might have something to do with it...
Click to expand...
Click to collapse
Sounds like you have a common driver issue. Do this: with your device connected to your PC in fastboot mode, right click your Windows start button and open Device Manager. What is your tablet showing up as? We will need to update your driver. I can walk you through it. Did you install the Google driver from the 15-Second ADB Installer? I am nearly finished writing a guide on properly installing the device drivers. I will link it here when posted. It will give you a detailed step-by,-step outline. I don't think it's an issue with the firmware builds. Fastboot detection issues are common with this tablet due to some type of instability with driver persistence. For example, I often need to update my driver every time I use fastboot mode because, for some odd reason, the updated driver doesn't persist once the tablet is disconnected from the PC and then reconnected.
i dont have this tablet but another hot pepper device called the poblano. with that i was able to boot into ffbm from the bootloader and have root adb access. then i ran dd on my boot partition and patched it with magisk and flashed it back
wondering if hot pepper still makes their devices like that or they patched it. either way props to you for getting the fw straight from the oem
luridphantom said:
i dont have this tablet but another hot pepper device called the poblano. with that i was able to boot into ffbm from the bootloader and have root adb access. then i ran dd on my boot partition and patched it with magisk and flashed it back
wondering if hot pepper still makes their devices like that or they patched it. either way props to you for getting the fw straight from the oem
Click to expand...
Click to collapse
The Scepter 8 does not ship with adb root shell (adbd) enabled. In fact, the bootloader was not even intended to be unlocked. The unlock command is disabled in standard fastboot mode. Luckily, the Scepter 8 is integrated with a second fallback fastboot mode, which we were able to use to to the oem unlock.
Many AllWinner tablets and other Chinese devices do, as you pointed out on your Hot Pepper device. When the Scepter 8 was first released I was able to pull a boot image using a Phoenix Suite tool that had been reverse engineered and modded. As luck would have it, I got rid of the tablet and lost my files along with access to the Phoenix Suite tool. So I've been weeks quarreling with Hot Pepper Mobile to provide firmware and the kernel source code. To their credit, the Hot Pepper CEO and support team were very helpful once they understood what I needed. Hot Pepper's software developers are in China, so a language translation issue hindered my request for some time.
Anyway thank you for your kind words and it is a pleasure making your acquaintance.
@64Star I have updated the thread above with some detailed instructions on updating your device drivers. Hope this helps.
Viva La Android said:
@64Star I have updated the thread above with some detailed instructions on updating your device drivers. Hope this helps.
Click to expand...
Click to collapse
It does, I've unlocked the bootloader and now i'm gonna go root it. Thanks for your help!
I have an unfortunate update: When I went to turn on my tablet, I've noticed there was a noticeable crack on the top left corner of the screen... and then when I tried to use it... the touchscreen no longer functions. I have no clue where that crack came from, cause that wasn't there yesterday, and I've kept it safe in a drawer until now, so I have no clue how it's possible. Guess the software isn't the only thing that's cheap, cause my 2020 Moto G Power survived way worse without even a single crack.
TL,DR: Touch screen somehow broke overnight, meaning I can't get past the setup screen, so GG no re, this $10 qlink tablet ****ing sucks.
64Star said:
I have an unfortunate update: When I went to turn on my tablet, I've noticed there was a noticeable crack on the top left corner of the screen... and then when I tried to use it... the touchscreen no longer functions. I have no clue where that crack came from, cause that wasn't there yesterday, and I've kept it safe in a drawer until now, so I have no clue how it's possible. Guess the software isn't the only thing that's cheap, cause my 2020 Moto G Power survived way worse without even a single crack.
TL,DR: Touch screen somehow broke overnight, meaning I can't get past the setup screen, so GG no re, this $10 qlink tablet ****ing sucks.
Click to expand...
Click to collapse
@64Star I hate to hear that but I know exactly how it goes. I've cracked many a screen in my day. But, on a positive note, if you have the extra funds, there are a ton of these tablets available on eBay within the $35 to $40 price range.
Viva La Android said:
@64Star I hate to hear that but I know exactly how it goes. I've cracked many a screen in my day. But, on a positive note, if you have the extra funds, there are a ton of these tablets available on eBay within the $35 to $40 price range.
Click to expand...
Click to collapse
LOL really turning a profit!
13lack13ox said:
LOL really turning a profit!
Click to expand...
Click to collapse
Haha. No doubt
Sorry about the delay on TWRP guys. My mounting issues are actually encryption issues. TWRP isn't decrypting the /userdata or /vendor partitions with the default key. I'm going to chat with one of my friends over at TeamWin and see if I can get a little guidance.
Viva La Android said:
@64Star I hate to hear that but I know exactly how it goes. I've cracked many a screen in my day. But, on a positive note, if you have the extra funds, there are a ton of these tablets available on eBay within the $35 to $40 price range.
Click to expand...
Click to collapse
You really expect me to shell out around 35$ to 40$ on a slow, laggy 10$ tablet just to experiment on? Hahahahahaha....
Spoiler
Perhaps
64Star said:
You really expect me to shell out around 35$ to 40$ on a slow, laggy 10$ tablet just to experiment on? Hahahahahaha....
Spoiler
Perhaps
Click to expand...
Click to collapse
Not really. I was only providing you info as to where they were available. I found one for $19 which is more than I really wanted to give.
As it stands now,.all the lag is gone in mine. I debloated everything that wasn't essential for normal operations. Then I edited the system/build.prop to increase responsiveness and I limited background apps & processes. Finally, I installed a kernel tuner and set the LMK to very aggressive, tweaked the I/o scheduler parameters, and increased entropy from the available pool. And set SELinux to permissive mode. I'm using Nova Launcher Premium with the launcher locked into memory. Believe it or not, the tablet is now very responsive considering the specs. I'm looking into overclocking the CPU a bit, but 1.46 GHz seems to suffice once RAM is optimized. It's a difference in night and day. It's good for a project tablet but that's about it.
There's another government tablet floating around called the Maxwest Nitro 7Q. 4G/LTE supported with a lot better specs. I think I have one located to buy for cheap.
Lots of tweaks it doesnt run too bad just removing bloatware. Would be cool to get your params on your tweaks etc. If you ever got time could you post it up? Maybe the rom you were talking about in another post has all that included? Anyways if not no biggie, this thing is just for playing around on.
13lack13ox said:
Lots of tweaks it doesnt run too bad just removing bloatware. Would be cool to get your params on your tweaks etc. If you ever got time could you post it up? Maybe the rom you were talking about in another post has all that included? Anyways if not no biggie, this thing is just for playing around on.
Click to expand...
Click to collapse
Absolutely. I'll list those for you here in just a little bit. I have a pure stock ROM built with a TWRP installer, but my TWRP has run into a snag. I've reached out to TeamWin for guidance on that.
All in good time, man. Just glad someone with knowledge is doing all this. Wish I could help more. My ability to program and compile is equivalent to stick poking. I've done it once with aosp 6 that was awhile ago.
13lack13ox said:
All in good time, man. Just glad someone with knowledge is doing all this. Wish I could help more. My ability to program and compile is equivalent to stick poking. I've done it once with aosp 6 that was awhile ago.
Click to expand...
Click to collapse
You seem to know your way around the Android OS pretty well. I'm a developer in training myself. Learning every day. Yeah AOSP 6, I still love working with the Marshmallow builds.
Ok first things first. I notice a huge performance boost from some kernel level mods. Here is a link to Kernel Toolkit. Install both APKs. https://mega.nz/folder/QYwA0QTA#O_Zg3h_iVkHOdeyU_yOmLw
First go to the CPU heading and change the scaling governor to Ondemand. Under CPU Governor Params, tap on Performance Profile and select Maximum Performance (you may personally want to scale back to Aggressive or Balanced, depending on your need for battery life). Now, close Kernel Toolkit and restart the app. Next go to the I/O heading. Choose kyber as the I/o scheduler and set the read ahead buffer to 512 KB. Go down to ZRAM and increase to the maximum of 1000 MB. Set Swappiness to 100. Go over to the Profiles heading, create a profile will all settings and give it a name recommended from the list. When complete, tap on the profile, select save settings and then apply settings.
Now go to the menu button in the upper left of the app. Go down and enable Apply Settings on Boot. Select All and set a 5 second delay.
Next, download a build.prop editor from Play Store. There are tons of free ones and any will suffice. Make a backup of your system/build.prop before you tweak anything. Open the editor and grant root permission.
For build.prop edits, locking your launcher into memory helps a lot with responsiveness. Add this line to system/build.prop
ro.HOME_APP_ADJ=1
This basically prevents the launcher from being killed by Android's native LMK.
To increase touch responsiveness, add these lines as well.
debug.performance.tuning=1
video.accelerate.hw=1
Disable the boot animation for faster boot time.
debug.sf.nobootanimation=1
Reboot to enable the tweaks.
Give these a try and let me know your feedback. I'm working on a few more mods to optimize this tablet and I'll keep you posted on those as well.
Thx great changes so far. Yeah more "snappyness" for sure. I'll have to play around and open up as much as i can swap around.
I can't change I/O scheduler though, I get a contact developer message.
13lack13ox said:
Thx great changes so far.
Click to expand...
Click to collapse
Yw. Do you notice a decent improvement?