Related
Hi XDA,
so basically i bought a Velocity Cruz T301 recently and followed the known procedures for rooting, flashing ClockworkMod Recovery and custom rom (SJHill Rom v0.3).
before the full brick my device was at ClockworkMod 5 and rooted with SJHill Rom v0.3.
i installed CWM by flashing the zip in stock recovery, then succesfully rooted the device, finally wiped and flashed my custom rom
after major dissapointment in this tablets performance i decided i wanted to get rid of it.
So i downloaded the stock rom, wipe and flashed it onto the tablet...
the tablet turned off when it was finished (i think it was attempting to reboot) and never turned back on again...EVER! :good:
i cant even get to recovery
i tried flashing with adb and fastboot but the device is never even presents itselft to the computer.
i found out that you can boot the device into USB boot mode where you hold the "VOL -" (Volume Down) button and press the reset button and while connected to the computer (windows only) a "JZ4760 USB Boot Device" appears.
i did some googling and also found out that the T301 is based on similar tech to a bunch of tablets and they can all be modified by some software released by Ingenic called USBBootTool.exe
the tool is written in chinese and i cant decypher it all, though i found out how to use it based on its usage for other Ingenic based tablets
1.) you will need to disable driver signature verification (press F8 on boot of windows and toggle the setting, i hate rebooting too but it has to be done)
2.) boot your tablet into USB Boot Mode (hold down Vol - and press Reset button)
3.) install the driver for your device (included in the files below)
4.) with the tablet disconnected you would open the USBBootTool.exe
5.) select your tablet in the options and fill each box with the files needed to flash (files included below)
6.) reconnect the tablet while still in USB Boot Mode and the software will flash your device on detection
everything goes fine for me except when i get to the flashing part in the end.
when USBBootTool detects my tablet, it attempts to flash and gives me a stream of errors and never flashes my device.
i dont know what to do at this point. i have provided direct links to all the software im using and also links to where i got them.
any help would be appreciated, thank you to the XDA community in advance
>------------------- DOWNLOADS ------------------------<
USBBootTool.exe / Tablet Drivers (4725 / 4725B / 4740 / 4750 / 4755 / 4760 / 4770)
http://dl.dropbox.com/u/79196608/burn_tools_3.0.16.rar
obtained from - http://forum.xda-developers.com/showthread.php?t=1720621
Velocity Cruz T301 Update.zip (contains the system.img / data.img / mbr-xboot.bin files)
http://www.cruztablet.com/T301update.zip
obtained from - http://www.cruztablet.com/Article_861.php
SJHill Rom v0.3
http://www.androidfilehost.com/?fid=9390362690511176486
obtained from - http://www.slatedroid.com/topic/27583-rom-t301-sjhill-rom-17-feb-2012-download-link-updated/
ClockworkMod 5
http://files.androtab.info/ingenic/cwm/20120514/T301-recovery-signed.zip
obtained from - http://androtab.info/mips/ingenic/clockworkmod/
I have the same situation. I have gone through every menu in the USB Boot tool and to no avail am I able to recover my T100.
gmick is redoing the software because the coding is set up wrong. Once he gets that figured out there should be a fool proof unbricking method that we can follow. He is posting information over on Slate Droid if you want to take a look.
feyerbrand said:
gmick is redoing the software because the coding is set up wrong. Once he gets that figured out there should be a fool proof unbricking method that we can follow. He is posting information over on Slate Droid if you want to take a look.
Click to expand...
Click to collapse
ok post the link to the thread, and ill add it to the first post as a solution if its found to be a working one
JustSayTech said:
ok post the link to the thread, and ill add it to the first post as a solution if its found to be a working one
Click to expand...
Click to collapse
*Cross Post from SlateDroid* (but I can't post the link because XDA won't allow it)
I found out why the USB boot isn't working. Well, more appropriately I know where it fails but not exactly "why".
The USB Boot tool works like this:
1) Send x00 command (Get CPU Info)
2) Device responds with "JZ4760V1"
3) Host sends two binaries, stage1 and stage2. Stage 1 sets up memory stuff, and Stage 2 sets up USB flashing functions.
4) Host checks that the binaries executed by issuing another x00 command (Which serves as an "Are you still there?" function)
5) If the response is good, the host will flash the images, if the response is bad, it will abort.
Our devices are failing at step 4. The linux usb boot tools (xburst-tools) fail in an identical fashion.
I know that the first stage binary transfers and executes fine because if it didn't the device would be limited to 16k. The second stage is 120K and is transferred successfully. Once the second stage "execute" command is sent, the device crashes.
The second stage is also unique to the CPU type. I've used all of the binaries for JZ4760 I could find on the net and when that failed I cross compiled my own binary from source and it still crashed.
At this point I highly doubt I'll ever be able to fix it, and this completely explains why no one could get any usb recovery tool to work while others using similar devices could. I guess our board is modified just enough for ingenic's stock binaries to fail. Without knowing what's changed (getting Velocity Micro's source) we're SOL.
I can open it up again and solder on the serial header but I'm betting it's going to give me some generic "couldn't execute" message that isn't going to help me. I'll probably do this anyway though because I've come this far so what's the loss.
wow, i learned alot from that post, seems like writing a usbboottool-like application that can send the commands but also log and possibly bypass security checks etc but that def would take sometime. thank you for your insight, seems youve come the closest to cracking the case, actually you found the fault, hopefully your methods can eventually bring about a fix
JZ 4770
gmick said:
*Cross Post from SlateDroid* (but I can't post the link because XDA won't allow it)
I found out why the USB boot isn't working. Well, more appropriately I know where it fails but not exactly "why".
The USB Boot tool works like this:
1) Send x00 command (Get CPU Info)
2) Device responds with "JZ4760V1"
3) Host sends two binaries, stage1 and stage2. Stage 1 sets up memory stuff, and Stage 2 sets up USB flashing functions.
4) Host checks that the binaries executed by issuing another x00 command (Which serves as an "Are you still there?" function)
5) If the response is good, the host will flash the images, if the response is bad, it will abort.
Our devices are failing at step 4. The linux usb boot tools (xburst-tools) fail in an identical fashion.
I know that the first stage binary transfers and executes fine because if it didn't the device would be limited to 16k. The second stage is 120K and is transferred successfully. Once the second stage "execute" command is sent, the device crashes.
The second stage is also unique to the CPU type. I've used all of the binaries for JZ4760 I could find on the net and when that failed I cross compiled my own binary from source and it still crashed.
At this point I highly doubt I'll ever be able to fix it, and this completely explains why no one could get any usb recovery tool to work while others using similar devices could. I guess our board is modified just enough for ingenic's stock binaries to fail. Without knowing what's changed (getting Velocity Micro's source) we're SOL.
I can open it up again and solder on the serial header but I'm betting it's going to give me some generic "couldn't execute" message that isn't going to help me. I'll probably do this anyway though because I've come this far so what's the loss.
Click to expand...
Click to collapse
for my JZ4770 Earlier USB tool was flashing .img without any problem but for now it is saying "load cfg failed". "API downlaod failed' like dialogues and doesnt flash anything. Any idea? Thanks in advance!!
First restart your computer (actually restart it) then redownload the USB boot tool and save it in a completely new directory and use a different USB port
Sent from my Pokeball
Yes, I did
JustSayTech said:
First restart your computer (actually restart it) then redownload the USB boot tool and save it in a completely new directory and use a different USB port
Sent from my Pokeball
Click to expand...
Click to collapse
Yes, I tried with this suggestion. Rather I reinstalled xp and the tried again. But the dialogues are same. The history is like this. Was having ICS on JZ 4770. Formatted with usb tool and put JB updates. It was not sensing touch so reflashed another JB updates. Now the tab boots, it reaches to boot logo for around 12 seconds and restarts in stock recovery. While it is in booting stage it get detected by windows and adb also. In stock recovery mode it get detected by windows and in turn by adb also. If I tried to install updates through SD card it shows it had installed and reboots after completion. But again the same way it goes to boot logo and then back to stock JB recovery. It also boots in ingenic boot device mode and gets detected by USB burn tools. But when try to flash any of the ROM it gives the same dialogues "check cfg failed" "api download failed" "boot. fw failed" and cant flash anything.
Is there any tool which can be flashed or a script which can be used from SD card for completely formatting flash memory so that USB burn tool can flash required ROM?
can you flash the stock rom in recovery?
Managed using USB BOOT TOOL for ingenic JZ 4770 board in English
JustSayTech said:
can you flash the stock rom in recovery?
Click to expand...
Click to collapse
thanks man but I managed to boot the device. I used following USB BOOT TOOL for ingenic 4770 boards. The goodness with this tool, this is completely in English. You will know what you are doing. Even after opening the main window of the tool you can right click and then get another options(yes again in English). My problem with this device was bad blocks at 1024. In the options there is chance to force erase whole the nand partitions which I used and erased all the partitions thereby made all the partions available for flashing and readable by the tool. Then from File option selected stock rom files and flashed them. While flashing selected JZ4770 iNanad.ini file in manual configuration. This tool has really helped me to come out of the issue and will be useful for guys using JZ 4770 board.
http://www.4shared.com/rar/m1BUV5r2/USBBurnTool_20120401_for_relea.html
Got USBBootTool.exe kind of working.
1. Download the following file from Ingenic.
ftp * ingenic * cn/3sw/01linux/tmp/jz4770-20110610.rar
2. Download Applocale from Microsoft.
www * microsoft * com/en-us/download/details.aspx?id=13209
3. Extract the jz4770-20110610.rar and find the folder. (Using 7zip should keep the UTF encoding in Chinese)
20110610\04burn\20110524_4770_Programmer
4. Copy the folder 20110524_4770_Programmer to location you want to use it in.
5. Install Microsoft Applocale (Just in case, I don't think it is required)
Now Start Applocale and create a shortcut to USBbootTool.exe inside 20110524_4770_Programmer
中文(简体) is simplified Chinese option and should let you view the GUI correctly.
6. Now with the Applocale Shortcut created for USBbootTool.exe you can start the application with correct fonts.
Now this is where is breaks down.
TABLET-8 NAND FINAL BSP(S3 TEST) will allow you to read from it and write to it, but the CFG is off.
\tool_cfg\tablet-8-nand-final.ini is the configuration for it.
DO NOT CONNECT THE DEVICE WITH ANY OPTIONS CHECKED OR LOAD ANY FILES.
See Attached Images.
Next to the Read button is some Boot Option menu. I am not fulling aware of what this does.
What I need is a someone to help me fix/correct the ini/cfg files in
\20110524_4770_Programmer\tool_cfg\.ini
\20110524_4770_Programmer\4760\
to correctly match the files of the NAND.
Also if anyone has a copy (dd to img) or (cat to img) of the block devices.
That would help a ton.
# cat /proc/partitions
# cat /proc/mtd
I would also love another T10x Tablet for cheap.
I want to start building things like new bootloader, kernel, system image,
performance libraries to take full use of the Ingenic JZ4760 (www * ingenic * cn/product.aspx?CID=11)
I also bring Christmas gifts
2 APKS. You can place them in /system/app or /data/app.
Google Play will crash now and again, but it will load and work. (Vending.apk)
Secondly I bring the gift of performance increase, just by a slight bit.
edit the line of the heapsize in /system/build.prop dalvik.vm.heapsize=96m
Remember to make sure the permissions are set back to 666 or 644.
Original Vending.Apk before updates came from here: (Incase you are paranoid)
code * google * com/p/ics-nexus-s-4g/source/browse/trunk/system/app/Vending.apk?spec=svn20&r=18
ics-nexus-s-4g * googlecode * com/svn-history/r18/trunk/system/app/Vending.apk
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for
Click to expand...
Click to collapse
Stupid. how do you expect real people to help post Tech Docs? That is bad Moderating and Administrating.
Make sure to replace the Asterisk's with spaces to normal dots.
Requesting Block Images.
Does anyone have a copy of it they can send me for a T10x?
block images......
IceGryphon said:
Does anyone have a copy of it they can send me for a T10x?
Click to expand...
Click to collapse
Which block images do you want?
...also is there a way to rip the stock images off the jz4760 in the t301.
Such as:
Can i usethe ingenic uboot tool?
Anybody find the jtag pins?
Is the 4 pin conn next 2 the batt for serial?
.......i guess ill try to take a look this weekend
Ics would be really nice, but probably slower than stock..... especially with the limited ram
I unpacked the stock rom. I also unpacked an ics rom for a jz4770, and repo sync'd the aosp and mips 3.0.8 android kernel.
I'm still trying to figure out specs for the processor though. I know that its mips32 - el- fp- r1, but i cannot figur out the dsp version ... if it has one?
Error in erasing nand
nanachitang420 said:
thanks man but I managed to boot the device. I used following USB BOOT TOOL for ingenic 4770 boards. The goodness with this tool, this is completely in English. You will know what you are doing. Even after opening the main window of the tool you can right click and then get another options(yes again in English). My problem with this device was bad blocks at 1024. In the options there is chance to force erase whole the nand partitions which I used and erased all the partitions thereby made all the partions available for flashing and readable by the tool. Then from File option selected stock rom files and flashed them. While flashing selected JZ4770 iNanad.ini file in manual configuration. This tool has really helped me to come out of the issue and will be useful for guys using JZ 4770 board.
http://www.4shared.com/rar/m1BUV5r2/USBBurnTool_20120401_for_relea.html
Click to expand...
Click to collapse
I used english ingenic tool to erase bad blocks but m nt able erase bad blocks live suit is giving eror id=0x4848
[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY NOTE 2 - Drivers, Root, Recovery + MORE
GSM (GT-N7100) and LTE (GT-N7105) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1923956
AUSTRALIAN GSM (GT-N7100T) and LTE (GT-N7105T) SUPPORTED. USE GSM THREAD
SPRINT (SPH-L900) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957155
TMOBILE (SGH-T889) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957720
MOBILICITY, VIDEOTRON, WIND [SGH-T889V] SUPPORTED. NO THREAD YET. USE TMOBILE THREAD
AT&T (SGH-L317) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052779
BELL, ROGERS, SASKTEL, TELUS [SGH-I317M] SUPPORTED. NO THREAD YET. USE AT&T THREAD
VERIZON ([SCH-I605]) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052788
US CELLULAR (SCH-R950) SUPPORTED. NO THREAD YET. USE ANY
KOREAN SK TELECOM [SHV-E250S] SUPPORTED. NO THREAD YET. USE ANY
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
{
"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"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**FAQ**
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on Android that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from the Market). Delete the file recovery-from-boot.p from /system. Now when you flash CWM Recovery it will NOT be overwritten after a reboot. You can also use the Toolkit to rename the files if you wish.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When would i perform a nandroid vs a titanium backup?
You would perform a nandroid backup to back up your entire system including boot image and data and system partitions so you can restore your entire system back to that particular point in the future.
You would use Titanium Backup mainly to back up your installed apps and settings so they could be reinstalled easily and quickly on any future roms. You can also choose individual apps to backup or restore on Titanium Backup whereas if you restore your boot partition via CWM Recovery you are stuck with the whole lot.
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) will pick it up as potentially harmful when it is not. They pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. I donated but where do I get my activation code from?
Donation Codes are sent out manually to your PayPal email address [unless otherwise stated] after a confirmation email from PayPal has been receive. The Code can then be entered in the ToolKit Settings, Activate Donators Features Screen. This will enable The Auto Updates, Quick Picks and Extras Features in the ToolKit. Please be patient when waiting for the Code to be sent as it depends very much on what I am doing and whether I am at my PC when the donation is made. Please do not post in the ToolKit's thread or pm me asking for the activation code as it clogs up the thread and my messages. If you haven't received your code after 24 hours then feel free to email me via the skipsoft.net contact page.
Don't worry that you have been forgotten about, I check all emails personally and will deal with it as soon as I can.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I flashed the Stock Firmware Image. Odin flashes the file successfully and the phone reboots but it stays stuck on the samsung logo
If the firmware tar file does not include a userdata image (which most Samsung firmware do not) then your userdata partition will be left from your previous setup. If this is incompatible with the new firmware because of build or something else then your system will freeze on boot up.
This is easily fixable by holding the Volume UP, Home and Power buttons all at the same time for about 10 seconds until the device reboots to the Stock Recovery screen. Use the Volume Down button to scroll down to 'wipe data/factory reset' and press the Home button to select it. Go down to yes to confirm and your userdata partition will be wiped. Your device should now boot fine.
*reserved if needed*
How To Videos on the Samsung Galaxy Note II ToolKit
This post belongs to wwjoshdew I am just mirroring his posts from the other Note2 threads.
Reserved for how to videos on this incredible toolkit!
http://www.youtube.com/playlist?list=PLwCVKEYxr_z7FBQYT32dbYw_kdSJmSDH2
How To Root
How To Manually Boot to Custom (or Stock) Recovery
mskips magic
Another one in the series of TOOLKITS from Mskip ( here since the early xdays ) and im v-happy to see this here.
im already rooted but this will make root a safer process for so many Note-2 owners.
here we go
Appreciate your big work Mskip !!!
This is a wonderful and complete tool
Mskip, the legend! !!!!!
Sent from my GT-N7100 using Tapatalk 2
Great news. Thank you so much for this. I'm sure it will come in very handy :good:
Released!!
Download link in first post.
Please let me know of any errors or bugs so I can get them fixed ASAP.
Mark.
hi mskip
Thanks for this great tool, i was using it on my GS3 to and was very useful.
I have a little issue I'm not able to flash the "boot-insecure-xxalj1-n7100.tar" after i hit start it doesn't goes on, i waited more than 15 min and nothing, see attached picture:
Any advise?
Can this be used for Note 2 LTE?
Sent from my GT-N7000 using Tapatalk 2
M3xital said:
hi mskip
Thanks for this great tool, i was using it on my GS3 to and was very useful.
I have a little issue I'm not able to flash the "boot-insecure-xxalj1-n7100.tar" after i hit start it doesn't goes on, i waited more than 15 min and nothing, see attached picture:
Any advise?
Click to expand...
Click to collapse
Its a driver problem with Odin.
Try rebooting your phone and pc and use a different usb port. I had that problem in the past and it usually fixed it. Also make sure you dont have samsung kies on your pc as Odin doesnt play nicely with it at all.
Mark.
zard said:
Can this be used for Note 2 LTE?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
As far as I know the gsm and lte lodels are exactly the same hardware so in theory it should work fine. The only difference would be radios. This is what im hoping so I can keep everything under a single Toolkit. Do you have a link to a Note 2 LTE forum so I can check it?
Mark.
I've used these mskip all in one tools for various Android devices and can thoroughly recommend them. Whilst I have already rooted and modded my 7100 I will be downloading this tool and buying him yet another beer!
Sent from my GT-N7100 using Tapatalk 2
mskip said:
Its a driver problem with Odin.
Try rebooting your phone and pc and use a different usb port. I had that problem in the past and it usually fixed it. Also make sure you dont have samsung kies on your pc as Odin doesnt play nicely with it at all.
Mark.
Click to expand...
Click to collapse
Gonna try to reboot phone and PC and try another USB port. Don't have Kies installed. Will let you know.
hey
Is it a chance for mac version ?
Cheers
P
mskip said:
As far as I know the gsm and lte lodels are exactly the same hardware so in theory it should work fine. The only difference would be radios. This is what im hoping so I can keep everything under a single Toolkit. Do you have a link to a Note 2 LTE forum so I can check it?
Mark.
Click to expand...
Click to collapse
Thanks Mark! That did the trick.
Just another question, after making a Nandroid backup I end up (on my PC) with a 16 mb folder like on a incremental backup but without the blobs folder.
Don't know why not able to download from MediaFire.
Try to get it later again. Thanks anyway.
Ive used it, works like a charm!!!! Thanks so much mate, i wil be making a donation tomorrow.
Sent from my GT-N7100 using Tapatalk 2
mskip said:
As far as I know the gsm and lte lodels are exactly the same hardware so in theory it should work fine. The only difference would be radios. This is what im hoping so I can keep everything under a single Toolkit. Do you have a link to a Note 2 LTE forum so I can check it?
Mark.
Click to expand...
Click to collapse
Sorry, no links as yet. I'm waiting for the Note 2 LTE to launch here (that's the only model to be launched here) this month, thus I had started to read Note 2 threads to get myself ready. I'll pm you if I find any link useful. So far, from the threads in Xda Note 2, there's no good information on LTE.
Sent from my GT-N7000 using Tapatalk 2
{
"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"
}
It has LINUX/UNIX and MAC support!
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
Download links: Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
Known bugs/limitations: - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
Changelog:
Check the changelog for each release here.
Tutorials/FAQ:
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
Sources: The official and original repository can be found here.
Bug reports/Feature requests: If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.
Licensing: Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff: Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.
Donations: Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
Disclaimer:I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Getting an error
FAILED(remote: oem unlock is not allowed)
Skies/SANKE said:
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Click to expand...
Click to collapse
Well, I've looked at your edit and I don't understand what looks better than mine... It might be subjective though...
Pikezer1337 said:
Getting an error
FAILED(remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Will investigate this problem and I hope I will get a solution fast
Edit: The information from this link might help with your problem.
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
paOol said:
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
Click to expand...
Click to collapse
The problem should be fixed in the V0.2, the Linux and MAC versions are not tested before posting, so bugs could still be around there...
added to index
Hi all, imusing linux and just tried to unlock my 5X. it worked but my question is, it is normal that it formated automatically?
after reboot, i have to start all over again with my account and setup.
Yes it's normal
Thanks mate, I'm new with nexus devices. One last thing, do I have to locked again or its OK leave it like that since on every reboot its showing me that I'm unlock. Sorry and thanks
Sent from my Nexus 5X using Tapatalk
You can leave it like that as long as you can deal with that message on every boot. If you lock it, you would have to unlock (and wipe) again if you ever want to flash anything again. Personally, unless you want to stick with the stock ROM OTAs, I'd leave it unlocked.
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Born<ICs said:
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Click to expand...
Click to collapse
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Lexmazter said:
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Click to expand...
Click to collapse
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Born<ICs said:
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Click to expand...
Click to collapse
To be honest I never locked my bootloader, didn't found a reason to, so I didn't tested.
But technically speaking, the only thing that happens is that you cannot flash other custom recoveries (fastboot stuff basically) without unlocking again and wiping all the stuff on your device.
OK, thank you. ReLocking to flash factory image was what I was thinking. I read doing so can lead to bootloop. Just trying to make note of things to avoid doing.
Cheers
You can lock and unlock your bootloader as much as your heart desires without consequence
skulldreamz said:
You can lock and unlock your bootloader as much as your heart desires without consequence
Click to expand...
Click to collapse
Well, wiping your data partition can be a pretty big consequence...
-edit-
You used to be able to use BootUnlocker for Nexus Devices to lock and unlock the bootloader from within the OS, but it looks like that's a no-go on the 5X...
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
owenrg said:
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
Click to expand...
Click to collapse
You will definitely lose root. I don't know about the bootloader since I've never taken an OTA, but I would guess that, unless there are bootloader changes in the update, your bootloader would stay unlocked. And to my knowledge the bootloaders are pretty much never updated for incremental OTAs.
{
"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 method will, when completed, will provide you with root and an unlocked bootloader, with fastboot available. It is a somewhat involved process, but the majority of the process has been simplified as much as possible.
WARNING!!!!This replaces your current bootloader with a debug bootloader. If you attempt to lock this bootloader you may brick your device.
Currently AT&T(H910) and Sprint(LS997) cannot return to stock because no KDZ files are available.
Disclaimer:
Once your phone is unlocked, it will no longer be covered by LG warranty @me2151.
As we cannot guarantee the proper operation of our hardware with custom software, we are not able to maintain the full scope of warranty for your device after you have unlocked the bootloader.
Because of that we have a responsibility to let you know that defects which may result from, or were caused by custom device-software may not be covered by LG warranty @me2151.
LG @me2151 can no longer guarantee the full functionality of your device after you unlock the bootloader. Unlocking your device may cause unexpected side effects that may include but are not limited to the following:
***Your device may stop working.
***Certain features and functionalities may be disabled.*
***Your device may become unsafe to the point of causing you harm.
***Your device becomes physically damaged due to overheating.
***The behavior of your device may be altered.
***Some content on your device may no longer be accessible or playable due to invalid DRM keys.*
***All your user data, settings, and accounts may disappear. (Therefore, we recommend that*you*backup all your data).
** -*Software updates delivered via LG FOTA (Firmware Over the Air) or Web Download services may not work on your device anymore.
LG @me2151 will not be responsible for the damages caused by any*custom software being flashed to your phone.
Known Issues:
AM&FM Radio no longer works
Boot time higher
No way to revert to stock(LS997/H910)
Possible overdose of root awesomeness!
Maybe more. Let us know!
Links:
- v20-root.zip
- TWRP
- Terminal Emulator
- Newest SuperSU(SuperSU v2.78 SR5 or greater is needed)
-Stock LS997 rom. for Sprint users only. (Fix's numerous problems)
Pre-requisites:
- ADB and fastboot setup and Installed
- Terminal Emulator installed onto the phone.
- The above links downloaded and SuperSU placed on the SD Card.
Working Devices:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
Note: International Variants (E.g.H990DS) May get supported in the future, but are currently being worked on at the moment. If you attempt to use this method on Unsupported Devices(any V20 not listed in working devices) then you are in uncharted territory. It will almost definitely brick your device. YOU HAVE BEEN WARNED!!!!
This will tutorial will be broken up into 2 sections, during the second section the instructions will differ depending on the variant of the phone you are using.
- Unlocking the Bootloader:
1) Copy all the files from inside the "Required Files" (Inside the unzipped "v20-root" folder) and paste it into your active ADB directory. Then copy and paste twrp-3.0.2-1-us996.img to your active ADB directory.
2) If you currently don't have Terminal Emulator then go and download and install now.
3) Plug your device into the computer and verify ADB is working. Then;
On Windows, double-click "RUNMEFIRST.bat, DO NOT CLOSE THE LOG WINDOW THAT OPENS, then double-click "Step1.bat"
On Linux/MacOS ("#" Signifies a comment below)
Code:
./RUNMEFIRST.sh
# OR
bash ./RUNMEFIRST.sh
Open a Separate Terminal next to the RUNMEFIRST terminal, then type:
Code:
./Step1.sh
# OR
bash ./Step1.sh
When you run The sh or Bat files there will be a Permission denied error on 2 files: Flatland and Flatland64. This is normal and nothing to worry about.
3.5) Wait for a shell prompt, then type (or copy):
Code:
run-as con
chmod 0777 /storage/emulated/0/*
4) Open Up Terminal Emulator
Type:
Code:
id
Check if context is "Untrusted_app"
If "Untrusted_app" is displayed, Continue:
Type into Terminal Emulator:
Code:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
If it doesn't show up as "Untrusted_app", repeat the above steps from Number 1
5) Watch the RUNMEFIRST dialog for when it tells you to run Step2. Then;
On Windows, double-click "Step2.bat"
On Linux/MacOS, type:
Code:
./Step2.sh
# OR
Bash ./Step2.sh
Once step 2 is completed, you'll be in bootloader, procced to "Flashing TWRP" section to continue.
Note/Warning: Verizon Users Vibrator will be constantly going off, until the whole process is complete (Past Android Setup Wizard).
- Flashing TWRP and Fixing Varient Issues:
1) Run Step3, so TWRP can be flashed and a working boot.img flashed (Fix's screen problem) by;
On Windows, double-click "Step3.bat"
On Linux/MacOS, type:
Code:
./Step3.sh
# OR
Bash ./Step3.sh
******Sidenote******
If you get message saying <waiting for device> on Step3.bat then you do not have the fastboot drivers installed(you may have the program but not the drivers).
To fix: Go to your device manager while the device is connected in fasboot and right click the item that says Android and select update drivers. Then select from internet. and let it install the drivers then try step3.bat again.
*************
2) After you're rebooted, and back at the main lockscreen, type;
Code:
adb reboot recovery
Your device will reboot to an LG screen. Keep checking adb devices for your device.
Then type:
Code:
adb reboot recovery
***********
Device should display a red triangle and say corrupt, then it will boot into TWRP.
3)Once in TWRP, Press Cancel on the password prompt and then swipe to allow system modifications.
Note:If you wish to make a back up now, you MUST save it to your SD card, and you cannot backup the data partition.
After the backup is complete, return to the main menu and hit wipe then select ?Format Data?, and follow the instructions there.
4) Steps below will differ, depending on what model you have, choose the correct model and follow its method.
- Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
- Sprint(LS997):
4.1) Go to Wipe > Advanced > Check Dalvik, System, Data and Cache > Slide to wipe
4.2) Go back to Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Main menu > Install > LS997 Stock Rom then Flash SuperSU.zip
4.4) Go back to Main-menu > Reboot > System(you will get static on boot. this is normal)
4.5) Sprint users are Done at this point. You do not need anything else. Everything will work except static on boot.Note:Any following Instructions are for all devices again.
5) During reboot you will get a Red Triangle with a "!" inside, this is normal (First boot after flashing SuperSu will show the Red triangle twice.Wait for system to boot (this will take awhile). It may appear like the system has frozen but it has not. JUST WAIT!
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot bootbackup.img
fastboot reboot
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
**************
Once you are booted and have proceeded through the setup wizard, re-enable Android Debugging (ADB) if not already enabled.
Type:
Code:
adb reboot bootloader
6) Once inside bootloader, Type:
Code:
fastboot flash boot bootbackup.img
When it says finished, Type:
Code:
fastboot reboot
The device will boot back into system.
WARNING:This is a required step for non sprint users, it prevents background crashes and fix's battery drain. If you do NOT follow this then the device will have bad battery life, be laggy and crashes will occur regularly.
7) Once full booted back into android, Type;
Code:
adb reboot recovery
8) Once TWRP loads, Then;
- Flash SuperSU.zip
- Go back to Wipe > Advanced > Check Dalvik and Cache > Slide to wipe
- Go back to Main-menu > Reboot > System
You now should have a rooted LG v20, download your favorite root checker app and verify root.
Note:For a root app to work, it will have to support Systemless root.
Contributers/Developers:
@me2151(General)
@glitschi667(General)
@EMSpilot(Debug device) #3
@elliwigy(Ideas and testing) #5
@Matt07211(Formatting this awesome guide and helping out with general stuffs)#4
@1619415(Awesome Santa Pic at the top!)#8
Alright guys. Its time for some fixes!!!
For our known issues:
Comfort view, youtube, boot time and possibly radio.
All fixed by flashing the AT&T H918 Konverged Kernel.
Keep in mind this is a temporary fix until I get a full custom kernel made for our devices(or at least a way to make the screen work out of box that we can use on other kernel sources).
To use this kernel on our phones you need to download the zip, Place on sd card, reboot to twrp, install the zip, wipe dalvik/cache then reboot.
You WILL GET STATIC ON EVERY REBOOT!
After the phone is booted put the screen to sleep by pressing the power button and cover your proximity sensor(so your 2nd screen turns off) then turn your screen back on. Your screen will work until reboot. If you reboot you will have the static again. Just follow the steps I just listed above to get the screen working again.
--------
Other Updates.
I believe I have finally found a way to revert sprint devices sprint devices to unrooted stock. I will be testing the method on my phone in the next couple days.
WooHoo!!!! I bricked attempting to revert!
So heres an update for you guys. Reverting has been confirmed possible using KDZ files for your specific models. Confirmed working for KDZs are H915, VS995 and some others. I do Have a new v20. I am going to pull the stock sprint files tomorrow and see what I can do about making that work.
Nicely done Guys.
@me2151(General)
@glitschi667(General)
@elliwigy(Ideas and testing)
@Matt07211(Formatting this awesome guide and helping out with general stuffs)
@1619415(Awesome Santa Pic at the top!)
I am extremely happy that the V20 User Debug I invested in worked out!
Enjoy everyone!!
Cheers
Reserved
Reserved lol
Awesome work guys!
Sent from my LG-LS997 using Tapatalk
reserved
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
pdaddy said:
Awesome work guys!
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
****
Good job @me2151 !!!:good::good::good:
Awesome! Now all the fun can begin!
Thanks for all your hard wprk on getting us root!
Thanks,
Chaz187
Sent from my LG-LS997 using Tapatalk
So awesome to hear, you guys are amazing. Its possible the dev with the h915 is waiting for the firmware update (we're told in time for the holidays?!) that would enable LTE on wind to see if this still applies. Nevertheless, thanks, i dont remember the last time i read so much. Lol
Sent from my LG-H915 using Tapatalk
Ooo Santa you so dirty.. Can't wait to do this
Sent from my VS995 using Tapatalk
SHABBA JOTS said:
So awesome to hear, you guys are amazing. Its possible the dev with the h915 is waiting for the firmware update (we're told in time for the holidays?!) that would enable LTE on wind to see if this still applies. Nevertheless, thanks, i dont remember the last time i read so much. Lol
Sent from my LG-H915 using Tapatalk
Click to expand...
Click to collapse
From the last I hear from him. The bootloader unlocks and twrp installs BUT he has no service(he is Rogers) So he is looking into all that.
AWESOME job, everyone! Thanks so much for this-- I admit I may wait a little while for feedback before trying my own unit, but given that I jumped on the V20 early in hopes that if any version is hacked it'll be the earliest firmwares, I can't imagine it'll be too long before I'm back to enjoying my phone the way I like it!
Definitely will be sending some coffee money along, even though I wasn't in any of the bounties...
Damn I've been waiting for this soooo much but there's only thing. I don't now crap about LG phones I've been a Sammy fanboy for 7 years lol. Guess I'll have to wait till my boy can do it.
Sent from my LG-LS997 using Tapatalk
---------- Post added at 08:13 PM ---------- Previous post was at 08:06 PM ----------
EMSpilot said:
Nicely done Guys.
@me2151(General)
@glitschi667(General)
@elliwigy(Ideas and testing)
I am extremely happy that the V20 User Debug I invested in worked out!
Enjoy everyone!!
Cheers
Click to expand...
Click to collapse
And thank you for purchasing that expensive out of pocket device.
Sent from my LG-LS997 using Tapatalk
Subutek said:
Damn I've been waiting for this soooo much but there's only thing. I don't now crap about LG phones I've been a Sammy fanboy for 7 years lol. Guess I'll have to wait till my boy can do it.
Sent from my LG-LS997 using Tapatalk
---------- Post added at 08:13 PM ---------- Previous post was at 08:06 PM ----------
And thank you for purchasing that expensive out of pocket device.
Click to expand...
Click to collapse
to be honest theres nothing really lg specific besides the files themselves lol.. of course you never use Odin outside of Samsung lol..
majority of it is pc bat or adb commands and then you got your typical twrp stuff but hey, best to have your buddy do it if youre not comfortable
Hey guys I need a little help, last step I was able to complete was running "Step3.sh, after reboot I'm unable to get into recovery mode. does anyone know the manual steps to get to recovery mode?
I also continue to get the popup "com.android.phone" has stopped.
No mobile service
hoopsdavis said:
Hey guys I need a little help, last step I was able to complete was running "Step3.sh, after reboot I'm unable to get into recovery mode. does anyone know the manual steps to get to recovery mode?
Click to expand...
Click to collapse
I'm assuming you're on Mac/Linux. If so, in terminal verify connection with "adb devices". If you're connected fine, enter "adb reboot recovery"
I started but wouldn't get any feedback when I would double RUNMEFIRST or Step 1.... I don't know if windows 10 matters.
I'll try again a little later tonight.
My device was connected and found; adb devices
oh yeah, im also running minimal adb and fastboot.
http://forum.xda-developers.com/showthread.php?t=2317790
Thank you guys for the hard work. So happy to have hotspot working.
dc.wash95 said:
I'm assuming you're on Mac/Linux. If so, in terminal verify connection with "adb devices". If you're connected fine, enter "adb reboot recovery"
Click to expand...
Click to collapse
I'm actually on windows
hoopsdavis said:
I'm actually on windows
Click to expand...
Click to collapse
Well in that case, you probably should have executed the ".bat" not the ".sh"
I'm running Windows 10, and successfully followed the guide. My device is past boot currently, and is installing apps from a Google backup.
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?