Database Info

[Tutorial]Gigabyte G1305 / Orange Boston unlock and upgrade to 2.1 with CMLMod 1.5.1

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

[HELP!] Velocity Cruz T301 Full Brick Recovery

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

[Q] Unbrickable Mod Help - Won't complete?

Problem solved -- lessons learned posted on page 2 - in short, use Linux to do this and do the soldering right the first time. Still this experience may be helpful to some who try and come across similar hurdles. Thanks to all who helped.
So I was successful last year rooting and putting a new firmware on this phone. I cam back to try something new but made the bonehead move of grabbing a GB loader for the Vibrant and hard bricked the phone. Nothing worked of course so I got brave and tried the Unbrickable mod. I've worked under a microscope before and after some trial and error modified my tools to manage the task (I think!?).
Up front I want to thank Adam and everyone else who put effort into the Unbrickable mod - that's simply amazing work and I wAs so fascinated I had to try it too.
So I now nothing about linux so all around this has been a huge learning experience and I'm hoping my problem is software but I fear not. I'm running Ubuntu over VirtualBox and used the links provided in Adam's Development thread for the the T959V - of course I'm new here so couldn't comment there. There was no Detector download so I just downloaded the Resurrector. Upon hooking up the phone I got a huge smile because the phone was recognnized by the computer and finally by the resurrector when I figured out how to get Ubuntu to see the USB. I ran the device and everything went apparently well HOWEVER I could not follow on with Heimdall One-click as it would not recognize the phone.
Here's the Output from the ReSurrrector
**********************************************************
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 004
=> loaded 24576 bytes from /tmp/TempHeimdallOneClick99719EDC/UnBrickPack/HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum d8dc
=> usb_bulk_write() returned 0
failed to write 24586 bytes
Interceptor Injection Complete. Injecting modified SBL
*****************************************************************
I assumed all was good and went forward. I got no display from the phone but the navigation lights did come on. However as said, Heimdall said phone disconnected. The phone is recognized in Windows as well however Odin does not recognize it. I tried Resurrector again and again. In looking at the Resurrector output I noticed there is a fail to write so I'm not sure where to go from here.... is there something wrong wtih my solder job? is one of the adjacent resistors disturbed?
I feel so close and yet so far... any direction is appreciated

sounds like a driver issue. here's a link for heimdall suite 1.3.2 for windows. unzip and make sure your phone is connected to a usb port in back of your pc first. front side usb ports can cause some problems. when phone is plugged into pc via usb, run the zadig.exe in the drivers folder. when open, options>list all devices. then from the drop down menu, select the one for samsung (mine now says galaxy s 4g) and then click install drivers. should be good to go with heimdall after that is done.
http://cdgfx.me/hEiMdaLL

Yep. Driver issue. Its better to use a Heimdall one-click if you can find one for your device. Linux also requires no drivers.

Again - please let me thank all in advance for looking at this problem.
So I've cleared all instances of USB installation before and the result is that I can now see "SCE S5PC110 Test B/D" show up in Zadig however - The drop down box shows only "USB Input Device (Interface 0) and another for (Interface 1)" and of course the S5PC110. I have "list all devices selected" however this devices only shows as the S5PC110 and thus Samsung is not selectable in the drop down box.
Driver reads as (NONE)
WInUSB (v6.1.7600.16385)
USB ID 04E8 1234
WCID shows a red "X"
There is no option to select Samung s4sg I suspect because the bootloaders are still not corrected and the Unbrickable mod is present?
Anyway, I pressed the install drivers button and indeed a usb driver installed with the following output.
******************************************
ini file 'zadig.ini' not found - default parameters will be used
default driver set to 'WinUSB'
0 devices found.
libwdi:info [detect_version] Windows 7
1 device found.
1 device found.
3 devices found.
Using inf name: SEC_S5PC110_Test_BD.inf
Succesfully extracted driver files.
Installing driver. Please wait...
libwdi:info [extract_binaries] successfully extracted driver files to C:\usb_driver
libwdi:info [wdi_prepare_driver] succesfully created 'C:\usb_driver\SEC_S5PC110_Test_BD.inf'
libwdi:info [wdi_prepare_driver] Vista or later detected - creating and self-signing a .cat file...
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\amd64\wdfcoinstaller01009.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\amd64\winusbcoinstaller2.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\sec_s5pc110_test_bd.inf'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\x86\wdfcoinstaller01009.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\x86\winusbcoinstaller2.dll'
libwdi:info [CreateCat] successfully created file 'C:\usb_driver\SEC_S5PC110_Test_BD.cat'
libwdi:info [CreateSelfSignedCert] created new self-signed certificate 'CN=USB\VID_04E8&PID_1234 (libwdi autogenerated)'
libwdi:info [SelfSignFile] added certificate 'CN=USB\VID_04E8&PID_1234 (libwdi autogenerated)' to 'Root' and 'TrustedPublisher' stores
libwdi:info [SelfSignFile] successfully signed file 'C:\usb_driver\SEC_S5PC110_Test_BD.cat'
libwdi:info [SelfSignFile] successfully deleted private key
Driver Installation: SUCCESS
3 devices found.
*********************************************
I have the Heimdall One Click for this device but as seen previously in both linux and windows - Heimdall does not detect this device as a Samsung and shows Disconnected... Similarly Odin does not detect this device.
So I switched back over to VM Virtual Box running Ubuntu 12.04 and no difference there either. I further made the USB permanent and took off automount from windows so that I could ensure the device interfaced directly into linux in the short period of time I assume is the download period - that is to be able to enter password for Resurrector, then plug in phone, and then press OK in a short period of time. The result is the same.
Summary - in Linux, Resurrector recognizes the device but Fails to write 24586 bytes as before. I can now also be in Windows and have the S5PC110 device recognized however nothing can write to it in Windows as far as I know.
*********************
One last try with a different method - held Vol +&- & power before connecting to computer. The following output from Resurrector in Linux appears the same as previous except for the questionable write. After the usb_bulk_write however I heard the device disconnect and again the progress stopped here
----------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 002
=> loaded 24576 bytes from /tmp/TempHeimdallOneClick14WD41A3/UnBrickPack/HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum d8dc
=> usb_bulk_write() returned 24586
Interceptor Injection Complete. Injecting modified SBL
************************************************** **************
there is no display on the phone and nothing progresses. The usb bulk write happens only on occassion and is immediately followed by the usb disconnect sound.

Lumin30 has a file called usbdeview in his fresh out of the box thread. Use that to remove all samsung drivers. It sounds like a residual driver is causing a problem.

eollie said:
Lumin30 has a file called usbdeview in his fresh out of the box thread. Use that to remove all samsung drivers. It sounds like a residual driver is causing a problem.
Click to expand...
Click to collapse
Thanks eollie but I did that already. I had to delete all previous Samsung and S5PC installations as I've tried so many things to date which involved using almost every usb port. It did make a difference in that now the device is recognized but as the test board and not as Samsung. I have gone through the route of installing the samsung drivers previously from the various Samsung Driver files that are around however none resulted in this phone being recognized as a Samsung again.

On the windows pc go to device manager and delete all USB drivers not just the ones related to phone then reboot and then try a heimdall one-click and only use zadig to install drivers??

OK - so I wanted to remove Windows from the equation as the experts suggested it's a driver issue and despite all my efforts I was having no success. I installed Ubuntu (dual boot) and voila Resurrector now completes and for the first time I actually get into download mode with a graphic on the screen. Using bhundven's One click The T959V Heimdall One-Click Collection I finally saw "connected" and was able to follow the steps twice to flash bootloaders. All operations completed successfully before disconnecting the phone however the phone did not reboot. SO I repeated the whole process again without any change.
current state - I cannot get the phone into download mode without using Resurrector. While I know a ton of progress has been made here thanks to the tools provided by Adam, bhundven, and others my phone still behaves as it did before - no display except for button lights on some methods to get to download mode. My jig does nothing either. Battery is fully charged and I remain stumped.

Did you make sure you flashed with bootloaders cus Ive had tthat happen with an older phone
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol

erikmm said:
Did you make sure you flashed with bootloaders cus Ive had tthat happen with an older phone
Click to expand...
Click to collapse
Yes twice with UVKJ6 package and subsequently tried AntonX-Basic_with_a_twist-v1.1.0-OC_UV.jar with double cycle to get the bootloaders flashed...
each time the process now gets to the point where it tries to reboot the phone and disconnects. The bottom status screen still maintains a rolling circle with statement of it's last step but the phone is powered down and nothing else will happen. No combination of buttons or jig or usb to computer will get the phone to boot or enter download mode.
On going back to windows (and Zadig) the device is still only seen as S5PC110 -- so I guess there is an improvement in but the phone is still not recognized as Samsung, Heimdall or Odin won't see it, and I have no idea what to try next.

You do have a SGH-T959V and not a 959W right? Have you tried to use heimdall frontend and flash everything except the modem? The 959W people that have been stuck in a bootloop got out of is by flashing everything except the modem. Then once sucessful they reboot to recovery and flash the modem of choice for the rom you are using.
I would pm getochkn and get the exact steps he uses and try it.

eollie said:
You do have a SGH-T959V and not a 959W right? Have you tried to use heimdall frontend and flash everything except the modem? The 959W people that have been stuck in a bootloop got out of is by flashing everything except the modem. Then once sucessful they reboot to recovery and flash the modem of choice for the rom you are using.
I would pm getochkn and get the exact steps he uses and try it.
Click to expand...
Click to collapse
This. Are you in Canada? A quick google search of "drsilicone" shows people with that same name on Canadian forums like redhotdeals, etc, so if that's you and you have a "W" phone, I may be able to help. 99% of the phone is the same as the "V" but small differences make a big deal sometimes and I have a pretty much complete dump now of a "W" phone with great help from bhundven and other team acid members. PM if you do have the "W" phone and we'll see what we can do. I've helped fix 2 other "W" peoples phones in the past 2 days. If you don't have a "W", then I can't help much. lol.
EVen if you see nothing on the screen, try the download button combo anyways. I did that to my phone yesterday, looked dead, but holding the buttons and putting the cable in, it still went into DL mode and Heimdall saw it, flashed back my dumps and was going again.

100% T959V -- it's a T-mobile phone that yes I previously rooted and unlocked. Worked fine for a year until my idiocy with the boot loader a few days ago.
and thanks for the advice but as I've noted above I've tried every key, button, jig, usb combination with no luck. The Unbrickable mod, resurrector, and Heimdall one-click with boot loader flash sequence appears to have worked except for the very last event expected - that is for the phone to reboot -- it does not reboot however.
The ONLY thing that produces any recognition or response in the phone is Adam's Resurrector. True the phone is now recognized in the window's environment as S5PC110 Test BD but it has never again been recognized as a Samsung so Heimdall simply won't find, connect, or otherwise allow command line flashing of this device. Similarly, Odin does not show any ID:Com open so that doesn't work either.
I can only hypothesize that the boot loaders were NOT actually written to the device as it would then show up as a Samsung no?? The only other thing to note is that after resurrector puts the device into Download mode (and I now see the yellow triangle graphic) I cannot disconnect the device and move to another port - the phone shuts right down and it's not responsive to ANYTHING I've tried..... and I think I've tried all sorts of combinations with battery in and out.
Edit:
Reading the Unbrickable Captivate thread again FredWorrell wrote on2nd September 2011, 04:31 AM #24
... a tip the size of a human hair. Although, if you screw up and you remove both resistors instead of just one, the phone can now be put into download mode and will accept a download. Unfortunately, it still won't boot normally.
Click to expand...
Click to collapse
This is the situation I guess I face but as I'm not certain what resistors he was referring to nor what those comparable resistors are on the T959V I'm still stumped -- unless Adam or someone knowledgeable can offer input...
I've borrowed this picture from Tablador for the magnification and clarity (Thank you Tablador) to highlight one resistor I have my questions about. I'm not sure how I can test it's function right now and my magnification is at 6X so I can't truly see the solder joints. I did disturb it but fixed it - could that explain this symptom?
{
"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"
}

Problems SOLVED
Thanks for everyone's help - it turns out that it was the resistor pictured above. The picture above shows solder shoulders on these resistors - without equal magnification I would swear there was none and with the landing pads located underneath it looks like an impossible task but with the right technique I was able to correct my previous mistake.
Funny story goes along with this - I bought a Vibrant last year from a kid who said it was bricked by Kies and he didn't know what to do. I'm up for an adventure and bought it from him. I ended up getting the T959V right after with a broken screen so didn't really try too hard to fix the vibrant. Anyway, with this challenge I set out tonight to do the unbrickable mod on the Vibrant as the T959V wasn't working. On opening up I found quite the mess -- this kid obviously tried the unbrickable mod and the whole bank of high and low resistors was gone with 4 chips spread off to the sides -- A complete disaster indeed and made me realized I had been taken in buying it... Oh well, I was able to harvest a resistor (I guessed one near the cpu that looked similar to the one I wrecked on the T959V) and my only choice now was to go back to the T959V and try again.\
I added some magnification and was able to install the new resistor in place of the questionable one pictured. Happy simply with the new soldering skills I've gained over the past week I resigned myself to the result of this final attempt. Imagine my surprise when I pressed the power button and it booted into CWM -- I couldn't complete the boot sequence so I had to run Resurrector again followed by Heimdall One CLick and I'm overjoyed - This time it all worked as expected.
Thanks to Adam, bhundven, and all others who've contributed to these magnificent technical lessons.
If this thread will serve anyone else in trying the Unbrickable mod I would summarize my lessons --
#This is very difficult and technical work trying to solder these things - don't try it without the right tools, knowledge (which can be gained by reading and watching videos), and a steady hand. Seriously, if you shake under a microscope don't bother - pay someone.
#Don't bother trying to do this in Windows - not worth the headache -- Ubuntu provides a very easy way to install dual boot to your computer and it was so intuitive that I regret not doing it sooner.
# and I guess I'll just testify as one more person that this mod really does work exactly as described -- if it's not working as described you may have USB driver issues or soldering issues as I had. If it's not working - do the mod again and make sure all the connections are as they should be.

Unbrick Honor 9 STF-L09 (NOT FREE, HCU and DC-Phoenix required)

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.

Trying to unlock the bootloader with PotatoNV on Mediapad T5 not working (video explanation)

Hi there,
So After seen many tutorials I wanted to proceed to unlock the bootloader of my Huawei Mediapad T5 , here are the specs
```
Model: AGS2-W09
Build No: AGS2-W09 8.0.0.360(OCEC431)
CPU : Hisilicon Kirin 659
Android Version: 8.0
```
I have downloaded the last build of `potatoNV` along with the SER Drivers ,
I have booted in untrusted driver mode (on Win10) and have installed `usbser.sys` as far as I recall
I proceed opening the Tablet from inside and shorting the "short point" and I get connection with the Computer , I installed the drivers , and tried on `potatoNV` with `Kirin 65x (A)` .
I get to the end of the progress bar , and then I get the problem as there is no confirmation that the process has been performed correctly. The connection dissapears , and If I try to boot on rescue mode and I do `.\fastboot.exe devices` or `fastbook.exe oem device info` it doesnt show no device at all.
Also the `rescue mode` menu says `Phone locked , FRP Unlocked` So I guess I had no luck
Please see the video on the link (note that the 2 takes are not synchronized)
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
What I may be possibly doing wrong ? May it be the USB connection (cables or connectors) ? or the drivers I downloaded?
Please any assitance will be appreciated.
Thanks

Maybe I can help you with this. Recently rooted this tab myself. Please give me a reminder tomorrow

Hey there I just saw the message . Please if you can guide me a bit of what I may be doing wrong? Also If there is a way to share the Drivers files that you used that would be great (I'm not sure if it was a matter of drivers or general clumsiness , please If you have a minute to check the video tell me what may be wrong on my "Technique") Thank you!!

freddieventura said:
Hey there I just saw the message . Please if you can guide me a bit of what I may be doing wrong? Also If there is a way to share the Drivers files that you used that would be great (I'm not sure if it was a matter of drivers or general clumsiness , please If you have a minute to check the video tell me what may be wrong on my "Technique") Thank you!!
Click to expand...
Click to collapse
Just saw your responce now (please use reply next time, I will get an notification then ).
The "Kirin 65x (A)" you've used is the correct bootloader. So guess it would have been something going on with the drivers or the procedure.
I recently (about 1 month ago) rooted this tab myself so I think I will have quite recent files for doing so. Maybe I can send them to you if you like. But I should have save the websites where I got them from too. But need to check it up for you then.
{
"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"
}
Did you have used the settings above?
You did had recieved the "New unlock code" message?
I have to go to work now, but I could help you further later this evening if you need further assistance

Rockel said:
Just saw your responce now (please use reply next time, I will get an notification then ).
The "Kirin 65x (A)" you've used is the correct bootloader. So guess it would have been something going on with the drivers or the procedure.
I recently (about 1 month ago) rooted this tab myself so I think I will have quite recent files for doing so. Maybe I can send them to you if you like. But I should have save the websites where I got them from too. But need to check it up for you then.
View attachment 5391207
Did you have used the settings above?
You did had recieved the "New unlock code" message?
I have to go to work now, but I could help you further later this evening if you need further assistance
Click to expand...
Click to collapse
Hi, thanks for assisting me. Yeah well, the version I used of PotatoNV(the last build) just had the option of Disable FBlock so I did that.
Also I tried wth a previous build that was showing both versions as you are showing and it happened the same thing.
My guess are more focused on 2 probable mistakes by my side either:
- When shorting the short point Im not doing it correctly. (not sure if this, as the device gets detected by PotatoNV and initiates the process)
- (Most likely thisone). Wrong drivers, I have downloaded them through a link found in a youtube video, and the video was not specific about this Tablet. Also there were a bunch of drivers within the same file so I installed one that looked like the correct one (but not 100% sure)
Anyways thanks for taking your time really and appreciate a reply but always whenever you find free time obviously. Take it easy today at work

freddieventura said:
Hi, thanks for assisting me. Yeah well, the version I used of PotatoNV(the last build) just had the option of Disable FBlock so I did that.
Also I tried wth a previous build that was showing both versions as you are showing and it happened the same thing.
My guess are more focused on 2 probable mistakes by my side either:
- When shorting the short point Im not doing it correctly. (not sure if this, as the device gets detected by PotatoNV and initiates the process)
- (Most likely thisone). Wrong drivers, I have downloaded them through a link found in a youtube video, and the video was not specific about this Tablet. Also there were a bunch of drivers within the same file so I installed one that looked like the correct one (but not 100% sure)
Anyways thanks for taking your time really and appreciate a reply but always whenever you find free time obviously. Take it easy today at work
Click to expand...
Click to collapse
Not sure, I should get into it again, but I'm not sure of potato is able to start the procesure or finding the divice if not shorted correctly.
Do you have a screenshot of your potato output/ results?
How are you performing the shorting procedure?
I can see if I can look for you for the right drivers tonight.

Rockel said:
Not sure, I should get into it again, but I'm not sure of potato is able to start the procesure or finding the divice if not shorted correctly.
Do you have a screenshot of your potato output/ results?
How are you performing the shorting procedure?
I can see if I can look for you for the right drivers tonight.
Click to expand...
Click to collapse
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks

freddieventura said:
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
Click to expand...
Click to collapse
Oh yes, forgot about the video in the OP...
Seems you're folowing the wrong procedure with the shorting proces.
And seems your potato version is a bit outdated. But don't think this will be much of an issue.
- Your tablet needs to be turned off.
- cable removed from the tab.
- start potato
- then short the circuit (tab turned off).
- keep it shorted and insert the usb cabel (the other end should be in the computer already)
- the tablet starts (i believe in somekind of flash mode. And i believe you should not be able to see the Huawei logo in this procedure).
- after 2 or 3 seconds after booting, release the shorted circuit.
- i believe it should display you now some info about the tab itself in potato when you press start.
P.s. Don't forget to make a screenshot of the results or write down the newly given unlock code. So you can use it afterwards to lock or unlock your bootloader at a later moment, without opening the tab again.
P.s. 2 I just read in your comment that the recordings are not synchronised. So it's possible you were following the correct steps above. Correct me if I'm wrong please

freddieventura said:
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
Click to expand...
Click to collapse
I'm home (finally)...
If the steps mentioned above didn't worked out, I would like to ask you to do axactly as I did. Just unlocked my Mediapad T5 just 1 month ago or so, so everything I've used should be recent enough I guess.
First:
- Un-install your potato version.
- Un-install your Mediapad T5 USB drivers.
So we can begin from scratch
Also:
- turn on OEM-unlock and USB-debugmode in developer settings.
I asume you have a decent and working ADB version installed on your PC?
If not, or when you're not sure, uninstall it too.
I was using the Minimal ADB and Fastboot from here:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Then:
1) Install the Huawei USB drivers from here:
Support area | files.dc-unlocker.com
(this) or (this) are the "official" sites I got this from.
2) Install the latest version of PotatoNV from here:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
Open potatoNV and use these settings marked in red:
3) Plug the USB-cable into your PC already, but don't connect the other side to the tablet. And make sure your tablet is turned off.
4) Now short the testingpoint with a shielded part. I just used a thick copper wire and used it between testingpoint and metalshield just next to it. Metal pliers as used in your video should work too ofcourse.
P.S. I see that you also disconnected your screen in the video? It seems that it's verry important not to see a charging icon in the next step, so maybe it's better to connect it again for this step.
5) While still shorting the testingpoint with the shield, connect the USB cable to your tablet and be sure no charging icon pops up (This can be a bit difficult doing on your own. Easiest way is to have someone around te help in this step). After a few secconds when connected (without seeing an charging icon) remove the shorting between testingpoint and shield.
6) Make sure that the Huawei USB COM is selected in PotatoNV (and that the other settings are the same as the screenshot)
7) And pres "Start!"
8) You should get similar results now:
PotatoNV v2.2.1
User manual: https://kutt.it/pnv-en
Verifying images...
Uploading hisi65x_a...
- xloader
- fastboot
Waiting for any device...
Connecting...
Serial number: FQB***************
Board ID: FQB*************
Model: AGS2-W09
Build number: AGS2-W09 8.0.0.360(OCEC431)
FBLOCK state: unlocked
Saved key: 6BN**************
Writing FBLOCK...
Writing WVLOCK...
Writing USRKEY...
Rebooting...
New unlock code: 3BS*************
p.s. In your video it seemed your device got disconnected somehow while uploading. You should not see that "timeout" message here now annymore.
9) Make a screenshot of your results, copy them to a text file or write down at least your "new unlock code"
So you won't have to open your tablet annymore in the future. You can use this newly obtained unlock code now to lock and unlock your tablet without opening again.
10) You should now see a warning screen everytime you reboot the tab. It warns you about that the device can't be trusted annymore because of the unlocked bootloader.
You can also enter Fastboot to check it
Fastboot/ Bootloader mode:
1. Turn off the device by holding the Power key for a few seconds.
2. Connect tablet to PC/laptop using the USB-cable.
3. Hold down Volume-Down.
4. Hold down the Power button until device starts (while still holding Volume-Down and USB connected).
4. Tablet boots now into Fastboot-mode.
You should see the following screen then (pay attention on the 2 red lines at the bottom):
You can close your tablet now!

Rockel said:
I'm home (finally)...
If the steps mentioned above didn't worked out, I would like to ask you to do axactly as I did. Just unlocked my Mediapad T5 just 1 month ago or so, so everything I've used should be recent enough I guess.
First:
- Un-install your potato version.
- Un-install your Mediapad T5 USB drivers.
So we can begin from scratch
Also:
- turn on OEM-unlock and USB-debugmode in developer settings.
I asume you have a decent and working ADB version installed on your PC?
If not, or when you're not sure, uninstall it too.
I was using the Minimal ADB and Fastboot from here:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Then:
1) Install the Huawei USB drivers from here:
Support area | files.dc-unlocker.com
(this) or (this) are the "official" sites I got this from.
2) Install the latest version of PotatoNV from here:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
Open potatoNV and use these settings marked in red:
View attachment 5391609
3) Plug the USB-cable into your PC already, but don't connect the other side to the tablet. And make sure your tablet is turned off.
4) Now short the testingpoint with a shielded part. I just used a thick copper wire and used it between testingpoint and metalshield just next to it. Metal pliers as used in your video should work too ofcourse.
View attachment 5391623
P.S. I see that you also disconnected your screen in the video? It seems that it's verry important not to see a charging icon in the next step, so maybe it's better to connect it again for this step.
5) While still shorting the testingpoint with the shield, connect the USB cable to your tablet and be sure no charging icon pops up (This can be a bit difficult doing on your own. Easiest way is to have someone around te help in this step). After a few secconds when connected (without seeing an charging icon) remove the shorting between testingpoint and shield.
6) Make sure that the Huawei USB COM is selected in PotatoNV (and that the other settings are the same as the screenshot)
7) And pres "Start!"
8) You should get similar results now:
PotatoNV v2.2.1
User manual: https://kutt.it/pnv-en
Verifying images...
Uploading hisi65x_a...
- xloader
- fastboot
Waiting for any device...
Connecting...
Serial number: FQB***************
Board ID: FQB*************
Model: AGS2-W09
Build number: AGS2-W09 8.0.0.360(OCEC431)
FBLOCK state: unlocked
Saved key: 6BN**************
Writing FBLOCK...
Writing WVLOCK...
Writing USRKEY...
Rebooting...
New unlock code: 3BS*************
p.s. In your video it seemed your device got disconnected somehow while uploading. You should not see that "timeout" message here now annymore.
9) Make a screenshot of your results, copy them to a text file or write down at least your "new unlock code"
So you won't have to open your tablet annymore in the future. You can use this newly obtained unlock code now to lock and unlock your tablet without opening again.
10) You should now see a warning screen everytime you reboot the tab. It warns you about that the device can't be trusted annymore because of the unlocked bootloader.
You can also enter Fastboot to check it
Fastboot/ Bootloader mode:
1. Turn off the device by holding the Power key for a few seconds.
2. Connect tablet to PC/laptop using the USB-cable.
3. Hold down Volume-Down.
4. Hold down the Power button until device starts (while still holding Volume-Down and USB connected).
4. Tablet boots now into Fastboot-mode.
You should see the following screen then (pay attention on the 2 red lines at the bottom):
View attachment 5391639
You can close your tablet now!
Click to expand...
Click to collapse
Thanks very much for your explanation , I will do this when I am back at home and let you know .
Cheers!!

freddieventura said:
Thanks very much for your explanation , I will do this when I am back at home and let you know .
Cheers!!
Click to expand...
Click to collapse
Are you btw sure that the pliers you used in in the video are making a circuit from one point to the other? Maybe worthwile to measure the resistance first?
I just used a thick copper wire and bended it to an easy to use U-shape.

Rockel said:
Are you btw sure that the pliers you used in in the video are making a circuit from one point to the other? Maybe worthwile to measure the resistance first?
I just used a thick copper wire and bended it to an easy to use U-shape.
Click to expand...
Click to collapse
Sorry Rockel I have been very busy this week , I'm gonna try and find a little bit of time to get this done this weekend . Thank you!!

freddieventura said:
Sorry Rockel I have been very busy this week , I'm gonna try and find a little bit of time to get this done this weekend . Thank you!!
Click to expand...
Click to collapse
No problem, take your time. Hope these steps wil solve your problem. Please keep me informed when you have time

Rockel said:
No problem, take your time. Hope these steps wil solve your problem. Please keep me informed when you have time
Click to expand...
Click to collapse
Do angels wear capes? because I haven't seen yours .
Much much much appreciate your help with this, I have just done it perfectly it didn't take me much time to do it.
Whatever I was doing wrong (probably the drivers , probably the shorting point thing not doing it properly) , whatever who cares!!.
I was also a bit not confident to do it that's why it took me time to get into doing it , but you definitely coached me with your messages .
Really thanks very much Rockel . For anything we keep in touch mate

freddieventura said:
Do angels wear capes? because I haven't seen yours .
Much much much appreciate your help with this, I have just done it perfectly it didn't take me much time to do it.
Whatever I was doing wrong (probably the drivers , probably the shorting point thing not doing it properly) , whatever who cares!!.
I was also a bit not confident to do it that's why it took me time to get into doing it , but you definitely coached me with your messages .
Really thanks very much Rockel . For anything we keep in touch mate
Click to expand...
Click to collapse
Hehehehe, thanks for your nice responce!
So I asume You've managed to root unlock the device now!
It was a pleasure assisting you in this.
If you need anny other information regarding this rooted device, please let me know. I'm not a pro with this. But had to solve a few problems myself. And came there with the help of others aswell.

What is the use of New unlock code?

do anyone have system, boot, cust, recovery, userdata.img with you i want to try with multi-tool to unbrick my tab

The unlock code can be used to unlock bootloader (using something like "adb oem unlock <code>" from PC)
I have saved the OTA folder form huawei system update app just before updating from 8.0.0.320(C432) to 8.0.0.371(C432), it can be found in /data/HwOUC folder after updater finished downloading. This version cannot be found on HuaweiFirmwareFinder site but I have temporary shared then here. Perhaps we could contact the authors to upload this version.
You can later use HuaweiFirmwareExtractor to extract different images from the zip files (no clue why there are 3 of them).
You need to disable "Verify Header checksums" in the "Settings" to open the extracted update.app files from the zips.
Good luck!

denzelcris said:
The unlock code can be used to unlock bootloader (using something like "adb oem unlock <code>" from PC)
I have saved the OTA folder form huawei system update app just before updating from 8.0.0.320(C432) to 8.0.0.371(C432), it can be found in /data/HwOUC folder after updater finished downloading. This version cannot be found on HuaweiFirmwareFinder site but I have temporary shared then here. Perhaps we could contact the authors to upload this version.
You can later use HuaweiFirmwareExtractor to extract different images from the zip files (no clue why there are 3 of them).
You need to disable "Verify Header checksums" in the "Settings" to open the extracted update.app files from the zips.
Good luck!
Click to expand...
Click to collapse
thank you .. but i extract app didnt uderstand which img file to install there no exact name for boot.img, recovery.img, cust.img, can you plz tell me which file equal to those file..

I don't think Huawei has boot.img or recovery.img, they may have a different layout and names (someone correct me if I'm wrong). I know the equivalent of boot.img is ramdisk.img or kernel.img (I flash both when restoring to be sure) and recovery should be recovery_ramdisk.img. The names from HuaweiExtractor should match with the images. Cust.img can be found in the other zip: update_full_AGS2-W09_hw_eu.
There is also this partition layout table which I don't know how it works for Huawei but I know that it may change for different firmwares so it is usefull to have remembered what version you had previously or use a safe tool to flash that also.