Related
I won't follow this thread anymore since i have sold my Boston. Anyway you can find more informations on htcmania.com (use google translate if you don't speak spanish)
EDIT: Upgrade to CMLMod 1.5 based on Muchtel ROM (below outdated CML 1.4)
With this tutorial you sould be able to unlock your Orange Boston (aka GigaByte G1305 Codfish, Apanda A60, WellcoM A88, Vibo A688, Cincinnati Bell Blaze f800, Commtiva Z71, Muchtel A1, Chinavision Excalibur, Motorola Greco, Nexian A890) and install CMLMod 1.5.1 (or 1.4) (by c.martinez.lozano) based on the ROM Muchtel 2.1 (eclair)
Main advantages/disadvantages of CMLMod 1.5.1:
+Unlocked device (can use any SIM)
+Android 2.1 (Eclair)
+Root access with Superuser permissions
+Preinstalled programms and other features
+Easy SD partitioning and more features thanks to the new recovery
+Optional App2SD
+Processor speed adjustable in a range between 122 and 600MHz (with the possibility to set variable processor speed to have performance and longer battery life at the same time)
+Other features: 3 different launchers, flash light, setcpu, app2SD in one click, other preinstalled apps and tweaks
=Camera autofocus not working (like on stock ROM)
=Different UserInterface (in my opinion better, but that's subjective)
-You may loose the warranty on your device
-IMEI may change, to restore your original IMEI use the tutorial in my second post
-Languages not fully implemented (english is working fully, other languages settable with LocaleSwitch but not fully integrated )
Important!!! There may be the risk of damaging your phone in an irreparable way! Be aware also by installing this ROM you will loose your warranty! I do not take any responsability for the status of your device!
I translated the tutorials on htcmania.com
All credits to c.martinez.lozano and pindemon from htcmania.com
Requirements
Hardware requirements:
-Phone model: Orange Boston (aka GigaByte G1305 Codfish, Apanda A60, WellcoM A88, Vibo A688, Cincinnati Bell Blaze f800, Commtiva Z71, Muchtel A1, Chinavision Excalibur, Motorola Greco, Nexian A890)
Edit: never seen a phone with so many different names!!!
-PC operating system: Windows XP 32 bit with SP3 and .NET Framework 2.0 and Winrar installed. Do not try with Windows XP working on a virtual machine!!!. Seems to work also on other Windows 32 bit operating. Does NOT work with Windows7 64 bit
-USB to micro USB cable (comes with the phone)
Software requirements For CMLMod 1.5.1:
Firmware Apanda A60 1.6.2
Firmware CMLMod 1.5.1 (this file already contains RUT 1.2.2 and the Phone drivers)
Additional for CMLMod 1.4 (Outdated):
RUT 1.2.2
Phone drivers
Firmware Apanda A60 2.1.9
Firmware CMLMod 1.4
Tools like adb, fastboot, etc
Ready to start! make sure you have enough battery left (at least 30%)
PART 1: Installing Apanda 1.6.2
Unpack the file Phone drivers on your desktop, or another place, but remember where
install RUT_V1_2_2. At the end you will have to reboot your pc. Reboot it
[*]Unpack the firmware 1.6.2 from the archive Hipi1_6_2.rar and you get a file ending with .nb0
[*]Execute RUT (the shortcut should be on your desktop). The program reminds us to prepare the USB cable and to have all the drivers installed. (For Vista or Seven 32 bit: right click on the RUT shortcut. on the menu select Properties-->Compatibility check Run this program in compatibility mode for: and select Windows XP (Service Pack 3) then press OK, then right click on the Rut shortcut and select Run as administrator)
[*]In the next window, look for the firmware just to unpacked (the .nb0 file) and select it.
[*]The instructions tell you what to do: disconnect the phone from your pc (if connected), remove and reinsert the battery to your phone
[*]Hold the camera button and the volume up button pressed and then press the power button to enter recovery menu.
[*]Once the recovery menu, connect your phone to your computer. If we never connected in recovery, it requires new drivers. They are in the inside the Folder we unpacked in step 1 inside the subfolder AndroidX32 for 32 bit operating systems (if it later asks for drivers again, select the same folder again).
[*]The installer will detect your phone. If not, enter the Device Manager and check that all devices are correctly installed.
[*]From now on, follow the on-screen instructions and wait, it takes a while.
[*]Once complete, we have the new firmware installed. Our phone will restart and (after a while) show us something in chinese. Touch the right on-screen button to select the english language.
[*]When your phone is on check your IMEI by dialing *#06# and then press the call button and write it down. Now check the IMEI written on the phone under the battery. If the IMEI is the same, go on with PART 2. if the IMEI changes, use the tutorial in my second post to restore the original IMEI.
Now your phone is unlocked but you have the chinese version of Android 1.6
PART 2: Installing CMLMod 1.5.1 (for CMLMod 1.4 skip this and go to PART 2 OLD)
Unpack the file CMLMod1.5.rar
Run the programm RUT once again, and select the newCMLMod1.5.nb0 file you got
Repeat the same steps described in PART 1: 6.-10.
Now on your phone open the main menu and then CMLMod1.5 to configure App2SD select Configurar Apps2sd, then partitionar SD the phone will restart into recovery mode.
Now select Partition sdcard, Partition SD and confirm with the Home key. set swap=0, Ext2=512 (is more then enough! you can also set less) and Confirm twice again.
Then press the back button and select APP2SD if you want your apps being installed on your sd in the Ext2 partition.
Attention!!! if after you want your apps being installed on your phone memory you have to make a Wipe, that means, your data will be lost.
Always in CMLMod1.5 you can select a launcher, install flash lite and install setcpu to set the speed of the phone's processor with the possibility of variable speed.
FINISH!!!
PART 2 OLD: Installing Apanda 2.1.9
Unpack the file Hipi_2_1_9GMS.rar and you get the file Hipi2_1_9_GMS版.nb0. Rename this file in Hipi2_1_9_GMS.nb0 (the chinese symbol can make problems)
Run the programm RUT once again, and select the new Hipi2_1_9_GMS.nb0 file you got
Repeat the same steps described in PART 1: 6.-10.
Now you have the chinese version of Android 2.1
PART 3 OLD: Installing CMLMod 1.4
Unzip the archive CMLMod1.4zip copy the 3 files inside and paste them into the folder A688
Remove and reinsert the battery of your phone
Press and hold the volume down and the end call buttons and then press the power button
Now your phone starts in fastboot mode. Connect it to your PC
Press on your keyboard Windows+R in the pop up window type "cmd" and press Enter
In the dos window type "cd.." (off course without ") and press Enter, until you are in C:\
Now type "cd A688" Enter, then "fastboot getvar version" Enter. If the answer is "0:5" procede, otherwise control if your drivers are correctly installed
Type "fasboot -w" Enter
Type "fastboot flash system system.img" Enter (wait 2-3 min. until it finishes)
Type "fastboot reboot"
Tutorial: Restore your original IMEI
Wrong IMEI seems to lead to a lot of different strange problems while using the phone. So if your IMEI changed after flashing an other ROM it might be better to restore the original one.
All Credits to c.martinez.lozano
Attention!!! this process is delicated!!! I have no responsability for any damages to your phone!
Dowload this File: and Unpack it to "C:\IMEI"
Go into C:\IMEI and execute setup. This will install PSAS
Execute MadEdit (answer NO), in MadEdit click File-->Open and choose NVList.nvr and we see a lot of numbers
Scroll down until on the left grey side you see "000020C0" and on the same line in the white part you see the numbers ".. .. .. .. 1A 23 45 67 89 AB CD EF...." this is the BAD IMEI
Now open notepad (on your pc) and write down your correct IMEI (found under your battery) putting in front "A" and separing every 2 characters (E.g. if your IMEI is "324867523906130" write "A3 24 86 75 23 90 61 30") and now invert every coupe of letters (in this case you would have "3A 42 68 57 32 09 16 03") *NOTE: thanks to jhonburton for better example
In MadEdit instead of the BAD IMEI "1A 23 45 67 89 AB CD EF" write (replace it) the number you got (in this case "3A 42 68 57 32 09 16 03")
Save the file and close MadEdit
Disconnect from your PC and turn off your phone and restart it into Recovery mode (Camera+Vol. up+Power). Reconnect it to your PC and if necessary install the drivers
Run PSAS (you installed it before) and choose Hardware Forensics-->Use Mobile Ports
Right to Serial Com Port select COM? - Smartphone 2009 Wireless USB Moden. The ? stands for a number. So very important!!! remember for Example if ?=3, remember COM3
Go to the tab Codes (QC) and click on Send SPC
Go to the tab Dialog Port (QC) and on the second drop down menu left to the button Lets go select Restore NVItems (Binary) and then press Lets go
Select the NVList.nrv (we have changed before) and click Open
IMPORTANT Once the process is complete, closed PSAS
Download and install QPST
Launch QPST Configuration
Click on the tab Ports and select Add New Port... and there you write the COM? port you had to remember before (in my example write "COM3") and click OK
In the tab Active Phones now you should see your phone. If not something went wrong.
Click on Start Clients-->SERVICE PROGRAMMING
A window with our phone will pop up. We select OK
Select Load from file and choose the 00000000_sp.qcn inside the folder c:\IMEI and click Open
Click Write to Phone and wait until your phone restarts, with your new IMEI.
Check your IMEI again by dialing *#06# now it should be correct
If your IMEI is still wrong, check accurately if you did everything right (correct number in NRV file etc etc...) if nothing helps procede with following steps:
Turn on the phone in download mode ( Hang up + Vol. Up + Power) and flash Apanda 1.6.2 again
Repeat all the steps of the Tutorial to restore your IMEI
If this didn't help install Apanda 1.6.1 always with the phone in download mode
Repeat all the steps of the Tutorial to restore your IMEI
If you still have problems, try to find another PC with WindowsXP SP3 32bit where you can try again.
Sooner or later you will be able to get you IMEI right (i think so)
thanx a ton suriya I've unlocked my blaze f800
You forget to explain how to use app2sd on CMLMod1.4
Thank's about your translate!!.
Sorry about my bad english
thanks alot. really good tutorial!
i didnt encounter any problems at all, not even those specified by you in the tutorial. as for the underclocked cpu, i see that as an advantage: this android version is faster with lower cpu frequency then the original one (at least for me), and thus, less battery is consumed.
if u dont care about ur phone's warranty (i dont), i really recommend this upgrade.
so far seems stable, but the bug when u place a call and u don't here ringing, persists.
Thanks alot, again!
Is it possible to flash the phone with this room using ROM Manager?
And if following your method do we have to do PART1 of the tutorial? i allready have my phone unlocked and have Android 1.6 for example.
thanks!
I have problem with Imei. After flash it is chaged. And i use this tutorial for restore imei but it didn´t work and my imei is still different thet under battery. And i have problem whit wifi. Maybe bad IMEI is reason for don´t working Wifi
Sorry for my poor english
c.martinez.lozano said:
You forget to explain how to use app2sd on CMLMod1.4
Click to expand...
Click to collapse
I will do as soon as i have my sd (i think it will arrive this week) and i will also translate how to bring it back to 600MHz. By the way, THANKS TO YOU!!!!
floroiu.andrew said:
but the bug when u place a call and u don't here ringing, persists.
Click to expand...
Click to collapse
Explain me better. Do you mean, when you call someone you don't hear this "tuuut-tuuut"? cause if it's that i don't have this bug
by the way if you didn't read it look here, about battery optimization.
nuno_mdj said:
Is it possible to flash the phone with this room using ROM Manager?
And if following your method do we have to do PART1 of the tutorial?
Click to expand...
Click to collapse
ROM Manager doesn't support our phone as far as i know.
I wouldn't skip that part! seems strange but i think i have red that people got trouble if skipping PART 1
gru15 said:
I have problem with Imei. Maybe bad IMEI is reason for don´t working Wifi
Click to expand...
Click to collapse
Try once again step by step. start with PART 1 again. be careful you don't forget anything. Use this version of QPST and a new .nrv file this time. if this does not help we will find a solution together looking step by step (in case c.martinez.lozano is an expert).
By the way wich kind of phone do you have, and from wich country? And wich operating system has your computer?
So i have Orange Boston from Slovakia and i am using WIN vista 32-bit. I read original post on htcmania but it is spanish so i dont understand everything, but some people write there that this tutorial must be use whe RUT is in download mode while i am installing 1.6.2 rom. I don´t know when is RUT in download mode...
And your qpst want serail !!!!
gru15 said:
So i have Orange Boston from Slovakia and i am using WIN vista 32-bit. I read original post on htcmania but it is spanish so i dont understand everything, but some people write there that this tutorial must be use whe RUT is in download mode while i am installing 1.6.2 rom. I don´t know when is RUT in download mode...
And your qpst want serail !!!!
Click to expand...
Click to collapse
Sorry i replaced the qpst links.
ok... not download mode but compatibility mode.
you right click on tha RUT shortcut. on the menu select Properties-->Compatibility check Run this program in compatibility mode for: and select Windows XP (Service Pack 3) then press OK
Now right click on the RUT shortcut again and select Run as administrator.
Try that way. then try that imei stuff again!
cheers
P.S. Anyway if you know where you can use an XP (32 bit) with SP3 i am confident everything will work if you do it step by step
ok IMEI is correct now. But i have a problem with wifi. On any 2.1 rom cant find any network but when i flash 1.6.2 it find. So i dont know where is a problem.
gru15 said:
ok IMEI is correct now. But i have a problem with wifi. On any 2.1 rom cant find any network but when i flash 1.6.2 it find. So i dont know where is a problem.
Click to expand...
Click to collapse
Ok good you restored your IMEI. About WIFI. Best thing is if you ask on htcmania because i don't know what to do.
When you have an answer and corrected your problem please post it here. So i add it to first post cuz other people may have the same issue.
CMLMod 1.5 with some nice new features is on the way!!!
there is in italian version too?
gru15 said:
So i have Orange Boston from Slovakia and i am using WIN vista 32-bit. I read original post on htcmania but it is spanish so i dont understand everything, but some people write there that this tutorial must be use whe RUT is in download mode while i am installing 1.6.2 rom. I don´t know when is RUT in download mode...
And your qpst want serail !!!!
Click to expand...
Click to collapse
dont remember exactly, but in some parts of the tutorial, you have to "Run as administrator" the given applications (RUT, etc). i used win7 32bit, and no problem.
ady_uaic said:
there is in italian version too?
Click to expand...
Click to collapse
No. But with LocaleSwitch you can select italian then most things are in italian. Settings (impostazioni) is still in English, and no italian dictionary on the stock keyboard. you can install another keyboard, to solve this. But wait for CML 1.5. Maybe some better.
floroiu.andrew said:
dont remember exactly, but in some parts of the tutorial, you have to "Run as administrator" the given applications (RUT, etc). i used win7 32bit, and no problem.
Click to expand...
Click to collapse
Yeah thanks for your confirmation. I wrote it on the first page.
cheers suriya
oki..thx for info. but, what does exactly that locale switch app? what are the changes?
Please add Nexian A890 (Indonesian version of this device) on the list too. Here, in Indonesia, we can bring it to the official service center to upgrade it.
ady_uaic said:
oki..thx for info. but, what does exactly that locale switch app? what are the changes?
Click to expand...
Click to collapse
with it you can select languages wich are present in the phone. Italian is also partially present. most things then are in italian. except the settings menu, the camera menu, the date on the lockscreen and maybe something else
minori_aoi said:
Please add Nexian A890 (Indonesian version of this device) on the list too.
Click to expand...
Click to collapse
thanks mate. added
It worked on my Cincinnati bell Blaze,but I can't get the IMEI to change. all works but
the Internet connection, WIFI does work.
Thanks for the 2.1 Upgrade
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
Introduction
THIS METHOD IS NOT FREE. I HAVE NO IDEA HOW TO DO THIS FOR FREE, EXCEPT MAYBE WITH THIS : https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/162196-free-hcu-license-offer
Oh my god. I just come out of 3 days of trying to get this to work, non-stop. I feel the need to write this guide so people in the exact same configuration as me won't have to go through what I did.
Yes there are many tutorials about unbricking your Honor 9, but few are very detailed, and I couldn't make them to work for my european STF-L09. Plus, very few of them have a solution for updating to the very latest version (9.1.0 as the time of writing). So here we go.
The device I did this with, and the situation I was in.
There are so many variants of the Honor 9, and I've tried tutorials that weren't the same model as me, they just wouldn't work.
Honor 9 STF-L09, Europe version, Kirin960.
Previous installed ROM before brick was Oreo (the Pie update I tried to make bricked the phone), but I think you can do that on any previous version.
After the brick, I had a completely dead Honor 9 : no reaction at all, whether I plugged it in or tried any buttons combination.
What you need
- The correct Drivers
- A HCU Client Timed License, which is 19 EUR for 72h, and is going to give you access to the main software we need, DC-Phoenix.
- The correct .dgtks Repair File
- The correct ROM file to flash
- HiSuite
- Tools to open the back of your phone
- A metal object to connect the testpoints (anything will do : tweezers, copper cable, paperclip, sim-tool...)
- Read these two tutorials from www.dc-unlocker.com :
https://www.dc-unlocker.com/dc-phoenix-flash-repair-tutorial
https://www.dc-unlocker.com/flash-bricked-huawei-phones-in-huawei-1-mode
Step 1 - Connect the testpoints
Then open the back of your phone to reveal the testpoints that you can see on the image below (thanks to the user 4r44444 for the picture).
Then, open the Device Manager on Windows, and reveal the COM and LPT Ports (so you can see if you failed at connecting the testpoints or not).
You don't need to connect the two testpoints shown in the picture : you only need to connect the bottom one with anything else that's metal inside the phone.
It will take you some trial and error but eventually, your Device Manager should refresh and show you an unknown device called "SER".
Step 2 - Install the drivers
First, install the latest version of HiSuite to get the basic drivers. Make sure to close it completely (taskbar) and disable the fact that it opens itself when you plug your phone, or it might screw things up.
Then, install the two drivers that are on both dc-unlocker.com tutorials I've linked above.
https://files.dc-unlocker.com/share.html?v=share/984CE114852148B5B9A9CDD918BEC235
https://files.dc-unlocker.com/share.html?v=share/18B15B9D02C945A79B1967234CECB423
The first one "Huawei_Android_phone_drivers.rar" was not useful for me, but the second one, "Huawei drivers testpoint.rar", is to make your COM port recognizable instead of this unknown "SER" in device manager.
In Device Manager, right click on "SER", "Update driver", and locate the extracted folder on your computer.
This is all you need I think, but I installed so many random drivers (which I would not recommend) that I'm not even sure anymore.
Step 3 - Repair the phone with DC-Phoenix
Following "Method 3" from this link, but with some differences : https://www.dc-unlocker.com/dc-phoenix-flash-repair-tutorial
As I said, this method is not free. You can buy credits to make DC-Phoenix work for 72 hours (you need 15 of them for that I think), but since we need HCU, you're better off buying a timed license which gives access to DC-Phoenix.
Open DC-Phoenix, and click on the "Download files" button on top. There, search for the file "STF-Full-Repair-NV-included-Board-A051-7.0.0_r1.dgtks" and download it, it's the Repair File.
https://get-file.org/search#q|STF-Full-Repair-NV-included-Board-A051-7.0.0_r1|1
With your phone connected via testpoints (it has to appear in the Device Manager in the COM Ports, and I recommend changing the COM Port to 1 (right click, Port settings, advanced,...)), go to the "Update OEMINFO" tab, and check "Use BOOTLOADER". There, choose "Kirin960_T2_A7.0_V4" (maybe it's a different one for you, but for me only this one worked).
Then check "Update OEMINFO and unlock Huawei ID", and choose "STF-L09". Click Update, and this should run without errors. If it doesn't recognize your device, that means that it's not turned off and connected via testpoints.
Once that is done, your device may show a sign of life by booting into fastboot mode (or sometimes not). Anyway, you can go directly to the "Update Firmware" tab, and in the "Update file" field, choose the file "STF-Full-Repair-NV-included-Board-A051-7.0.0_r1", check "Rescue Revovery" and "Old slow algo", and click "Update".
After completion, your phone should be able to boot (after a very long press) into a chinese test ROM.
Step 4 - Repair the phone infos with DCU
Follow this tutorial : http://hcu-client.com/huawei-phone-repair-as-empty-board/
Don't forget to change your phone to Manufactured mode (as explained) so you can read your phone info.
In the Step 4, they let you choose between Repair UMTS or CDMA tab, I chose CDMA because I think the phone has a MEID.
Then, when they tell you that you just have to click on "Repair as empty board" to make everything fill in automatically, for me this was complete bs : only my IMEIs were added.
So what you have to do is fill your original SN, WiFi and BT MAC adresses, and so on. But since your phone is bricked and you probably dumped the box that states the SN, you're outta luck like me. It seems like it's illegal to change a MAC or SN number, so I can't recommend it, but I personally just chose random numbers (that have the same number of digits).
For model I entered "STF-L09", for vendor "hw", and for country "eu". Don't check "Erase restricted ver.", since it's only for Qualcomm CPUs. Click on Repair.
Once this is done, your phone should be resetting, and able to boot in the same ROM as before, except in english.
Step 5 - Upgrade to the latest Android 9.1.0
Normally you'd have to do this step with DC-Phoenix : just flash one of their Full Stock Roms they have on their file database (click Download Files on DC-Phoenix, and search for "STF-L09").
You can try that (don't forget that you have to be in fastboot mode (Vol down + plug USB) to install), but it really didn't work for me, and even if it did, I don't know how you'd update after it, because your phone probably won't receive OTAs.
So the solution I found was this one : https://www.reddit.com/r/Huawei/comments/az4bl7/finally_managed_to_update_my_mate10_pro_to_pie/
First, uninstall your latest version of HiSuite to be able to follow this tutorial and install the old version.
Then, the file I chose in Firmware Finder was this one :
STF-L09 9.0.1.175(C432E2R1P5)
STF-L09C432E2R1P5B175 (9.0.1.175)
STF-L09C432E2R1P5T8B175 (9.0.1.175)
I chose the "full" version, which gave me this link :
http://update.dbankcdn.com/TDS/data/files/p3/s15/G3757/g1699/v260353/f1/full/update.zip
After following this tutorial, your phone should boot normally. You can then installs OTAs to update to 9.1.0. I'd recommend resetting the phone after this last step, to have a clean install.
If it doesn't work for you, you can also try this method : https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/
I'll try to answer as many questions as fast as possible (since the Timed License is quite stressful), so feel free to ask !
Does the HCU Client unblock the network after doing the full repair?
Hello , Is this solution still works for honor 9 ?
I can't find stock rom on official website also.
This thread will go over restoring the IMEI number if you cleared the NVRAM (or fully formatted your phone). The official tool to use is the SN Writer tool from Mediatek but as the P60 processor is not compatible with that, I had to search for alternative ways.
First the legal blerb:
IT IS ILLEGAL TO FLASH A DIFFERENT IMEI NUMBER THAN THE ONE IT CAME WITH (AS FOUND ON THE SIM TRAY OR BOX).
I AM NOT RESPONSIBLE FOR ANY DAMAGE OR LEGAL AFFAIRS CAUSED BY USING THIS GUIDE. IF YOU DO BLAME IT ON ME THEN I WILL LAUGH AT YOU!
Now the guide.
You will need:
- The phone
- A USB cable
- A Windows computer (I used Windows XP, I will get to that later.)
- The drivers linked below (no other drivers seem to work properly or at all.)
- MauiMETA (linked below.)
Part 1: driver installation
These are essential to get the phone to be recognized
- Remove the phone if it's plugged in.
- If using Windows Vista or newer, disable driver signature enforcing (look up online if you don't know how to). For Windows XP there is no such limitation, you can just click a "continue anyway" button.
- Download and extract the drivers (linked below).
- Run "Install Drivers.bat" and follow instructions.
- Reboot the computer to be sure.
Part 2: installing MauiMETA
You will need this tool to start the phone to META mode and write the IMEI numbers.
- Download the setup program.
- Install the software by following on-screen instructions.
Part 3: getting the phone to go into meta mode
- Turn off the phone completely.
- REMOVE THE SIM CARD JUST IN CASE!
- Open the MauiMETA program on your computer.
- Check if the device select is set to "Smartphone" and if the drop-down in the top left is set to "IMEI Download"
- Click "reconnect" and plug in the phone.
- Wait until the phone displays "=> Meta mode" and the application either says "connected" or displays an error box.
Don't be scared of the error box. Just close it. Another may pop up, close that too. If the MauiMETA program displays a few boxes that say something with 6771, it's been detected and the IMEI Download tool is about to open.
Part 4: downloading an IMEI number to the phone
I would again like to warn you that flashing the non-original IMEI is illegal!
If the tool asks if it should find the database itself, click yes. There is no database you can load yourself, so the built-in one will work fine.
- Find your IMEI number(s). They should start with "35".
- Put in the IMEI number to the tool. The middle box is where you start typing. The very last number will need to go in the small box to the right. If you have a dual SIM model, there will be a submenu called "SIM_2" which you can find at the top of the tool.
- Click the "Download to phone" button and it should flash the IMEI numbers.
- When everything is done, hold the power button of the phone for about 10 seconds until it boots into the OS.
If everything went right, you should have a working phone now. I still need to figure out how to restore WiFi and BlueTooth MAC addresses, but the random ones the OS give you should do fine. Also ignore the NVRAM Error 0x10 wifi network, it indicates both are gone. Also some UI bits and pieces might be wrong on the latest Android because for example the notch values were loaded into device-specific partitions.
My device is oneplus nord 2 . When i am using the maui meta software , my phone is always connected on COM6 port and in the maui meta software i can only see COM1 , USB COM and DIAG COM . When i connect the phone the COM6 is displayed and after that when i click on reconnect the maui meta software says please connect cable to target and power on when the phone is already in meta mode. Can you please help me with that ?
BennoMP said:
This thread will go over restoring the IMEI number if you cleared the NVRAM (or fully formatted your phone). The official tool to use is the SN Writer tool from Mediatek but as the P60 processor is not compatible with that, I had to search for alternative ways.
First the legal blerb:
IT IS ILLEGAL TO FLASH A DIFFERENT IMEI NUMBER THAN THE ONE IT CAME WITH (AS FOUND ON THE SIM TRAY OR BOX).
I AM NOT RESPONSIBLE FOR ANY DAMAGE OR LEGAL AFFAIRS CAUSED BY USING THIS GUIDE. IF YOU DO BLAME IT ON ME THEN I WILL LAUGH AT YOU!
Now the guide.
You will need:
- The phone
- A USB cable
- A Windows computer (I used Windows XP, I will get to that later.)
- The drivers linked below (no other drivers seem to work properly or at all.)
- MauiMETA (linked below.)
Part 1: driver installation
These are essential to get the phone to be recognized
- Remove the phone if it's plugged in.
- If using Windows Vista or newer, disable driver signature enforcing (look up online if you don't know how to). For Windows XP there is no such limitation, you can just click a "continue anyway" button.
- Download and extract the drivers (linked below).
- Run "Install Drivers.bat" and follow instructions.
- Reboot the computer to be sure.
Part 2: installing MauiMETA
You will need this tool to start the phone to META mode and write the IMEI numbers.
- Download the setup program.
- Install the software by following on-screen instructions.
Part 3: getting the phone to go into meta mode
- Turn off the phone completely.
- REMOVE THE SIM CARD JUST IN CASE!
- Open the MauiMETA program on your computer.
- Check if the device select is set to "Smartphone" and if the drop-down in the top left is set to "IMEI Download"
- Click "reconnect" and plug in the phone.
- Wait until the phone displays "=> Meta mode" and the application either says "connected" or displays an error box.
Don't be scared of the error box. Just close it. Another may pop up, close that too. If the MauiMETA program displays a few boxes that say something with 6771, it's been detected and the IMEI Download tool is about to open.
Part 4: downloading an IMEI number to the phone
I would again like to warn you that flashing the non-original IMEI is illegal!
If the tool asks if it should find the database itself, click yes. There is no database you can load yourself, so the built-in one will work fine.
- Find your IMEI number(s). They should start with "35".
- Put in the IMEI number to the tool. The middle box is where you start typing. The very last number will need to go in the small box to the right. If you have a dual SIM model, there will be a submenu called "SIM_2" which you can find at the top of the tool.
- Click the "Download to phone" button and it should flash the IMEI numbers.
- When everything is done, hold the power button of the phone for about 10 seconds until it boots into the OS.
If everything went right, you should have a working phone now. I still need to figure out how to restore WiFi and BlueTooth MAC addresses, but the random ones the OS give you should do fine. Also ignore the NVRAM Error 0x10 wifi network, it indicates both are gone. Also some UI bits and pieces might be wrong on the latest Android because for example the notch values were loaded into device-specific partitions.
Click to expand...
Click to collapse
My device is oneplus nord 2 . When i am using the maui meta software , my phone is always connected on COM6 port and in the maui meta software i can only see COM1 , USB COM and DIAG COM . When i connect the phone the COM6 is displayed and after that when i click on reconnect the maui meta software says please connect cable to target and power on when the phone is already in meta mode. Can you please help me with that ?
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?