Database Info

The Ultimate Guide to put Hero Builds and other Builds to your G1/Magic Android

The Ultimate Guide to put Hero Builds and other Builds to your G1/Magic Android Phones by hellogadgetman from Greece
or download from here for best structure and more
http://rapidshare.com/files/2522727..._Builds_and_other_Builds_to_your_G1_best.docx
for ROOTED Phones
I have no responsibility for mistakes and problems through this guide
1) Find your SPL and Radio Versions
• Radio
o Next you will want to confirm your Radio Baseband.
To Confirm this Press Menu - Settings - About Phone - Scroll down till you see Baseband version.
Compare the Baseband value to the value below to see if you are using the correct radio for your build or if you need to update.
o You will need 2.22.19.26I
• Currently there are three SPLs available. The G1 variant is the SPL that is installed in stock T-Mobile G1 phones. The Engineering variant is found in the Android Dev Phone 1. Finally, the HardSPL is a modification of the Engineering variant by cmonex, with additional hacker-friendly functionality.
• HardSPL
• VER: HSPL10.95.3000
• HardSPL is a modification of the Engineering SPL by cmonex. In addition to the functionality of the Engineering SPL, HardSPL also allows NBH files to be used without matching the CID (carrier ID) check.
• Engineering SPL
• VER: HBOOT-0.95.3000
• The Engineering SPL is a custom SPL installed in devices intended for Android development. It has existed since before the launch of the G1 and is now available to the general public as preinstalled on the Android Dev Phone 1.
• G1 Original SPL
• VER: HBOOT-0.95.0000
• This is the original SPL which is installed in a stock G1. It is easily distinguished by the "trademark" red-green-blue bootloader screen which appears in many HTC phones. This SPL does not support the fastboot protocol and thus will not allow the user to flash nand backup images.
2) Update the Radio to the Latest
• Download the Radio zip.
• http://android-roms.googlecode.com/files/ota-radio-2_22_19_26I.zip
• Rename it to "update.zip".
• Copy it to the root of your phone's SD card.
• Turn your phone off.
• Start up in recovery mode by holding Home and pressing Power.
• Press ALT+S to apply the update.
• Once the update is applied press Home+Back to reboot the phone. The Phone will start to boot up and then continue applying the update. Once this is completed the Recovery menu will ask you for the second time to reboot the phone via Home + Back
3) Update the SPL to the Latest
IF YOU HAVE ONE SD CARD:
• Upload new SPL on your microSD and rename to "update.zip"
• Reboot your phone into recovery mode. I ASSUME YOU MEAN HOLDING POWER AND HOME BUTTONS>>>RIGHT?
• THIS IS IMPORTANT (perform a nandroid backup, of course) APPLY THE UPDATE USING ALT-S..., and once complete DON'T DO ANYTHING.. read step 4.
• WITHOUT PRESSING ANY BUTTONS remove your microSD card from your phone, and plug it into your microSD card adapter/SD card reader
• Remove/rename the SPL update (to something other than "update.zip") and upload the update file of the build you are currently using onto your microSD card. Put your microSD card back in your phone AGAIN WITHOUT PUSHING ANY BUTTONS I KNOW THIS IS STUPID, BUT WE RENAME THE BUILD TO UPDATE.ZIP AS WELL
• Press Alt + x to go to the console. If your phone does not reboot automatically, press enter, type "reboot recovery", then press enter again.
• If you boot up in recovery, you have done everything correctly. Now APPLY THE UPDATE USING ALT-S, reboot, and you're done
4) Performing a NANDROID Backup
At this point you should backup your phone via NANDROID
1 Turn your phone off.
2 Hold Home, press Power button to boot into Recovery Mode
3 Press ALT+B to start the backup.
4 Once the backup has completed press Home + Back
Next your phone will reboot and load the OS, at this point you should copy the files your just backed up to your PC incase you need to recover your phone
1 Mount your SDCard to your PC
2 On your SDCard change to the nandroid/HT840GZ30985
3 Inside this folder you will see another folder the first 8 digits of this folder name is the date it was created in the YYYYMMDD format and the last four are the time.
4 Copy this entire folder to your PC and save it. As you make more backups to your phone repeat this process.
5) Format your sd card to Fat32 and Ext2/Ext3 Partitions
• Install the sdsplit executable to your phone. To so this, open the 'terminal' application / ADB Shell and type the following commands at the prompts:$ su
# cd /data
# wget http://64.105.21.209/bin/lib/droid/sdsplit
# chmod 555 sdsplit
# exit
• Decide the size of your FAT partition:
You should use one of two approaches to decide the size of your FAT partition. The first one involves simply directly deciding this size (i.e. I want a 5G FAT partition). In this case, the EXT2 partition will be the remainder of the card.
size_of_fat_partition = size
The second method is based upon the fact that you want to decide the size of the EXT2 partition and would like the FAT partition to be the remainder of the card. In this case, the size of the FAT partition will be based on the size of your sdcard and the size of the EXT2 partition that you want. Use this formula to calculate it:
size_of_sdcard - size_of_ext2_partition = size
So, if you have an 8GB sdcard and want 1GB of space for apps on your EXT2 partition, use 7000M for the FAT size.
No matter which method you use, you will need to specify either bytes (no parameter), kilobytes (K) or megabytes (M) . So, for a 5G partition would use a 5000M size parameter.
Note: The size parameter is currently case sensitive, use 7500M, not 7500m!
• Backup your SDCard onto your PC
Note: To figure out how much data (in K) you have on you FAT partition, you can type the following in your terminal / ADB Shell (the sdcard can not be mounted for this cmd to work):
$ du -s /sdcard
Note: to find out how much free space is left on your /data partition type (see available)
$ df /data
• Run sdsplit. Use the size from step 3 below (do not forget the "M" in size if you are specifying megabytes): (Note: you will need an internet connection on your phone for this step)
Note: If you are using the JF1.5 update, you should put a -nc at the end of the commands below since system configuration is not needed!
Non JF1.5 Build:
$ su
# /data/sdsplit -nd -fs size
# exit
JF1.5 Build:
$ su
# /data/sdsplit -nd -fs size -nc
# exit
Please, remember to record the output of this stage if you run into a problem. There will be a permanent record of it in, /data/sdsplit.log.
• Reboot your phone, via terminal:
reboot
• Restore your data from your PC to your Fat partition of your SDCard.
• You're done! You should have two partitions now on your sdcard. The FAT one mounted at /sdcard and the EXT2 one mounted at /system/sd.
6) Put the Cyanogen Recovery image 1.2
http://n0rp.chemlab.org/android/cm-recovery-1.2.img
To install raw image: copy it to your sdcard and run from a terminal:
flash_image recovery /sdcard/cm-recovery-1.2.img
It is suggested to fully shutdown the device and power it back up.
Check Recovery IMG by rebooting phone and pressing Home + Power to see the new Recovery IMG
If you have problems with a "no space on device" error, try using fastboot and erasing first:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.3.1.img
7) Upload JACHero 2.2.3 or any other to sd card and rename them as update.zip
8)Last steps to finalize
• wipe
• run apps2sd from recovery image menu
• then run fix filesystems
• then run update.zip
• then run apps2sd from recovery image menu again
• then reboot
• when phone reboots, give it about a minute after the screen comes on and chose deny on swapper in SU permissions pop up.
• then go thru the setup for gmail and android..
• after you get logged in to everything, do your settings for backlight and whatever else,
• then go to programs and do the swapper settings -
• SWAPPER SETTING:
/system/sd/swapfile.swp
Change swapper size
i did 20mb / 32mb ( i think thats right )
• then reboot ( after Gmail has finished syncing your contacts )
• when it comes back up choose always allow on swapper ( in su permission popup )
• then do you market and flickr( disable wifi for a sec ) to accept the terms..
• then give it a few seconds, and in about 1 min the phone will be running faster like cupcake
Many thanks to JACHero,Cyanogen,Robpet2,Jesus Freke,Jon Pezz, xmoo, Haykuro, Stericson, dapro, The Dude, Darkrift, and many others!

very nice guide thank you...also very nice guide structure
gonna try this and see if i can really get this to run as fast as cupcake

Just a side note;
Http://twistedumbrella.googlepages.com/index.htm
The guide there has all the resources loaded to the site already and no longer requires you to have to use fastboot because the recovery there has restore built in.

pretty good guide...but this has nothing to do with porting builds -- only installing builds that have already been "ported"
porting (in the context you used it) means to change a build to work on another system / device:
http://en.wikipedia.org/wiki/Porting
also...Recovery 1.3.1 is the latest and greatest
cheers

alapapa said:
pretty good guide...but this has nothing to do with porting builds -- only installing builds that have already been "ported"
porting (in the context you used it) means to change a build to work on another system / device:
http://en.wikipedia.org/wiki/Porting
also...Recovery 1.3.1 is the latest and greatest
cheers
Click to expand...
Click to collapse
I know but 1.2 Cyanogen has Apps to sd and fix filesystems

alapapa said:
pretty good guide...but this has nothing to do with porting builds -- only installing builds that have already been "ported"
porting (in the context you used it) means to change a build to work on another system / device:
http://en.wikipedia.org/wiki/Porting
Click to expand...
Click to collapse
Yes, the title of this post is rather misleading. I was expecting a guide to porting. This is a well organized collection of instructions to prepare your phone for most modern builds, and will surely be useful to some, but the title should really be changed to better reflect the content of the post.

hellogadgetman said:
I know but 1.2 Cyanogen has Apps to sd and fix filesystems
Click to expand...
Click to collapse
1.3.1 does too, but much like fix_permissions its executed through concole instead of menu

If someone made the guide please post his thoughts
Thanks

Anyone or better None

thanx for your instructions!
and, is the Cyanogen Recovery Image the necessary part for flashing Hero roms on G1?
thanx again.

thanx for your instructions!
and, is the Cyanogen Recovery Image the necessary part for flashing Hero roms on G1?
thanx again.

Very good, indeed.
EDIT:
What happens if you miss a step, but still able to flash the latest 2.3.5 hero rom? (Following these steps reduces the lag?)
That's what exactly what I did:
1. I already had the latest radio update (so I didn't bother downloading again)
2. I installed latest SPL, renamed it to "update" in my sd card, turn off phone, turn-on phone (HOME+END button), hit ALT+S.
(I don't have a SD card reader yet.....but I have another phone (T-Mobile Wing), I removed SD card from G1, put it in T-Mobile Wing, opened folder where SD card is, and deleted "update" (SPL file), rename the 2.3.5 HERO rom to "update", took SD card out of T-Mobile Wing, put it in my G1)
3. Turn on G1 (HOME + END), wipe (ALT+W), then flash (ALT+S)
(Waited until it installed new hero ROM, it was installed, then I went to swapper application and changed settings to " /system/sd/swap.swp "
That's it.
I already had partition my SD card before doing this update. I dont know if it's necessary to do it again.
My G1 is working, and I have 72MB free space in internal phone storage (so far).
My question is:
Do I need to follow these steps to make the rom work better? To allow my apps go to my SD card (like it was before).?
By the way, I installed the OVERCLOCKWIDGET app from market and it won't open. (Launch Error, "Overclockwidget (need root) could not be launched")
Any inputs would be greatly appreciated.
Then I wipe, flash new ROM.

ss1271 said:
thanx for your instructions!
and, is the Cyanogen Recovery Image the necessary part for flashing Hero roms on G1?
thanx again.
Click to expand...
Click to collapse
Yes if you want to be a fast Hero ROM

jay22are said:
very nice guide thank you...also very nice guide structure
gonna try this and see if i can really get this to run as fast as cupcake
Click to expand...
Click to collapse
if it is let me lnow to make the change to hero

FAILURE to install
I followed your guide exactly but when I was flashing the hero update an error came back
"E: Cant't chown/mod /system/xbin
(no such file or directory)
E:Failure at line 14:
set_perm_recursive 0 2000 0755 06755 SYSTEM.xbin
Installation aborted."
Any suggestions???
NVM. Problem fixed. had to download the following spl
https://www.digital-bit.ch/g1devel/6.0-spl-signed.zip

Alt+M (apps2sd option) isn't showing up in v1.3.1
Anyone have any idea why Alt+M (apps2sd option) isn't showing up in Cyanogen's Recovery Image when all the other options that were updated in 1.3.1 are?
twistedumbrella said:
1.3.1 does too, but much like fix_permissions its executed through concole instead of menu
Click to expand...
Click to collapse

Thats the reason I put in my guide the 1.2 Cyanogen recovery

DirectMatrix said:
Anyone have any idea why Alt+M (apps2sd option) isn't showing up in Cyanogen's Recovery Image when all the other options that were updated in 1.3.1 are?
Click to expand...
Click to collapse
app2sd is automatic in version 1.3.1, but that's for new apps installation.

All the hero roms (at least that i know) require not the recommended "HardSPL" but Haykuro's updated SPL
This guide is very misleading esp since you bascially c/p from the other posts.
Dont take it personally, but it really needs to be cleaned up

B-man007 said:
All the hero roms (at least that i know) require not the recommended "HardSPL" but Haykuro's updated SPL
This guide is very misleading esp since you bascially c/p from the other posts.
Dont take it personally, but it really needs to be cleaned up
Click to expand...
Click to collapse
But this is the point of somebody who has to read over 500 posts to understand to have all the things straight away.
I have used it and it is fine and some others also ...(over 100 downloads of the document)
Thanks

[Official] HSG (X5A/X6) & Pandawill G11 rooting/dev thread (SetCPU & Root working!)

[Official] HSG (X5A/X6) & Pandawill G11 rooting/dev thread (SetCPU & Root working!)
Chinese-manufactured devices, with Korean cpu.. The midX5a / midx6 are both Telechips-based tablets. They're very similar to the Augen device, except they have the actual HDMI port, 300M /data, correct /cache size and a 3.5" headphone jack
The Pandawill G11 seems to be a rebranded version of this hardware using the same firmware(s).
Note: There are older versions of this hardware with no HOME/MENU/BACK buttons, running WinCE. These cannot be upgraded to Android as far as we know right now.
TODO / What's not working: (Updated 24/8/2010)
- Add more languages (like Dutch!)
- Cleanup included languages (Georg77cz is working on cz/cs translation.)
- Find out how to increase /data to the full 3.3GB that's available on internal NAND (hexedit LK.ROM?)
- SetCPU (fc's after moving slider) Working! See attachment![/strike]
- Can't seem to enter recovery by hardware buttons Working, connect USB and use Rom Manager to reboot into recovery!
- Unpack tcc_8900mtd files Naobsd figured it out, thanks!
- Unpack system.img Naobsd figured out to patch unyaffs!
- Repack system.img Naobsd released tools for this.
- Unpack boot IMG, figure out base & pagesizes (4096 page size, base 0x40000000)
- Custom recovery - We have Clockworkmod working as of 20-8!
- Can't boot into recovery from ADB - (From firmware #348 this is fixed..)
- Factory defaults (Works in #348 and wipes properly using the recovery reboot.)
What's working: (As of firmware release #348)
- Custom recovery (Clockworkmod)
- Calibration (You must hold the stylus at the spot for some time.)
- Rooted!
- Telechips FWDN firmware recovery (via WinXP/2K)
- Telechips USB host booting method with empty(!) nand
- Rotation with 'RotateD' from market
- YouTube HD (Just push the Evo4G Youtube.apk)
Note there are similar models. Visit the HSG website and note the right side button spacing/placement.
Link: HSG Website
The model this topic is about, has the buttons spaced across the right side.
The other model that is not from HSG appears to be non-available from China sellers right now, or not in production yet for unknown reason. (sensor rumours)
Another third model has popped up, it's basically the same hardware in APAD casing with metal back plate.
I moved this thread over here from Slatedroid since it got filled with non-dev talk, and thier hosting keeps going offline. I hate it when i can't backtrack to my own findings
{
"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"
}
Specs/Facts:
- MIDX6 has on-board rotation sensor, but it's apparently not working in the firmware yet.
- MIDX6 has optional 3G / GPS inside
- MIDX5A is the basic model with no sensor/3G/GPS. (The rest is the same.)
- CPU Runs at 720Mhz stock
- Has HDMI port
- Has a normal 3.5" jack for headphones
- One speaker, and one microphone inside.
- Runs Android 2.1 eclair-update1
- No GPS/3G/Orientation sensor inside
- Linpack score around 4.9 with no mods / clean os.
- Metal top body, plastic bottom
- Mine came with 2x 1300mA battery inside!
- Battery lasts really long, i can run for ~6-7 hours at work with wifi on.
Quick review
I've used the device for about 3 days now with firmware #297, and it's very fast to use & works like a charm. It has a very solid build quality with a metal top on a thick plastic bottom, making it feel like a quality product. Market worked out-of-the-box with no fuss or hacks. Touchscreen is responsive, but resistive. If you want to slide, push down your finger first, then slide (don't hit-and-run or do a driveby with you finger on the screen).
Battery life is pretty damn good. I've been using it for at least 6-7 hours in one go, with wifi while debugging and ADB and such. The screen is nice & bright, and even if it's a resistive screen it works OK. The main reason for an initial slow reaction from the screen, is that the CPU is downclocked to 36Mhz when you are not doing anything. Edit: This is sorted with SetCPU 2.01! After the first wipe/slide it goes up to 720Mhz.(Yes, that's 120 Mhz more than the Augen!)
Note to posters: Please keep this thread clean. If it's not about rooting or dev, do not post it here please. Thank you!

Post reserved for updates:
Root updated (20-11-2010)
Updated One-click root for #348 and lower.
Download here
This also works with the newer revisions of this tablet with g-sensor
Recovery now working! (20-8-2010, requires #348)
See This Topic for working recovery files.
Steps for flashing with FWDN in USB mode (16-08-2010) (Thanks @fun_ & GeorgCZ for testing!)
(more details will follow)
- Figure out your device serial number and /data/softmac. Store it. (easiest to do, is flash same firmware, FWDN shows it)
- Option #1: You are on V7 (@205, #270, #297, #320) ? Use FWDN mode, and just flash it, format entire nand between different versions!
- Option #2: You are on V6 (WINCE) firmware ? Use use the internal switch to set USB host mode. Place tcBoot.rom in fwdnv7 folder
- When going from V6 to V7 firmware, you will need to erase the entire flash with the dropdown box.
- Plug in when asked, the device will boot with the USB boot mode. Then flash your firmware.
- It's almost impossible to kill the device. The CPU will boot in USB host boot mode if you erase the nand completely!
(In)Compatible USB devices (13-08-2010)
- Keyboards
- Mice
- Wifi USB/Keyboard (as long as they are USB HID devices with no drivers)
- CSR Bluetooth: Not working (no driver in kernel)
- UVC webcams: Not working (no driver in kernel)
SAFE MODE boot (12-08-2010)
This is a special mode if you screwed up something and can't get in the OS because of force-closes in an bad-behaving app that you installed..
- Ensure no power is plugged in
- Press the centre of the touchscreen, & keep it pressed.
- Power on the device as normal. Don't let go of the touchscreen..
- You're now in Safe mode! (a message should be in the bottom left corner stating so.)
Exact steps for flashing with FWDN (12-08-2010) (Thanks @fun_!)
- Power off the unit
- Unplug USB
- Plug in the AC adapter
- Firmly touch the touchscreen
- Power on the unit
After a while you'll notice it stays at the boot splash screen, then you can plug in the USB cable and fire up FWDN.
Google maps update failure fix (11-08-2010)
Connect using ADB and issue the following commands:
Code:
adb remount
busybox rm /system/app/Maps.apk
cd /system/bin
sh pm uninstall com.google.android.apps.maps
sync
Now you can install the new Google Maps version from the Market.
(If not, just reboot the device & try again.)
Extract kernel from boot.img (11-08-2010) (Thanks @geoRG77!)
You can extract the contents using split_bootimg.pl (needs linux+perl installation.)
http://android-dls.com/files/linux/split_bootimg.zip
This also works on tcc8900_mtd.img, since boot.img is near the start of this file. Need to DD of some bytes
(Note that system.img and others are also inside this MTD dump, it's for flashing the whole nand area in one go in the FWDN software.)
Modified INF file for ADB driver:
]usb_inf_X5A.zip
How to:
- Enable USB debugging
- Install the driver from my usb_inf_X5A.zip (2k/xp/32 bits)
- Unzip root_setcpu_X5A.zip into C:\rootfiles
- Start a command prompt and do cd /rootfiles, then root.bat
- You should get no errors, and after the reboot, your X5A should be rooted.
- Note, SetCPU does not seem to work properly.
Firmware layout #297 7-10-2010
Here's /proc/mtd output from #297 rom:
Code:
dev: size erasesize name
mtd0: 80000000 00080000 "bootloader"
mtd1: 00a00000 00080000 "boot"
mtd2: 09600000 00080000 "system"
mtd3: 00400000 00080000 "splash"
mtd4: 01400000 00080000 "cache"
mtd5: 13b00000 00080000 "userdata"
mtd6: 00100000 00080000 "persist"
mtd7: 00a00000 00080000 "recovery"
mtd8: 00100000 00080000 "misc"
mtd9: 00100000 00080000 "tcc"
Firmware layout #348 7-10-2010
Code:
mtd0: 00a00000 00080000 "boot"
mtd1: 00500000 00080000 "kpanic"
mtd2: 09600000 00080000 "system"
mtd3: 00400000 00080000 "splash"
mtd4: 02800000 00080000 "cache"
mtd5: 12300000 00080000 "userdata"
mtd6: 00a00000 00080000 "recovery"
mtd7: 00100000 00080000 "misc"
mtd8: 00100000 00080000 "tcc"
Firmware layout #205 18-10-2010
Code:
mtd0: 80000000 00080000 "bootloader"
mtd1: 00500000 00080000 "boot"
mtd2: 09600000 00080000 "system"
mtd3: 00400000 00080000 "splash"
mtd4: 03200000 00080000 "cache"
mtd5: 12800000 00080000 "userdata"
mtd6: 00100000 00080000 "persist"
mtd7: 00500000 00080000 "recovery"
mtd8: 00100000 00080000 "misc"

Warning: Each device has a unique serial. Do not select to overwrite it in the 'Tools - Options' menu!!
It is strongly advised to write down your serial after doing a basic FWDN flash, in case of emergency!
Firmwares
Below you'll find a fast mirror for the current firmwares:
(Do a Right-click, save as.. these are 7zip compressed, get it at www.7zip.com)
Firmware #205 (0730) - No market, pretty bland rom.
Firmware #297 (0803) - Works stable, has market.
Firmware #348 (0816) - First rom with recovery booting, but no keys work to select options
We don't know how to repack or unpack them yet. LK.rom seems to hold the MTD layout inside. If anyone figures out how to unpack/repack these files, please let us know.
19-8-2010: User fun_ figured out, we need to flash lk.rom as a single file, and then reboot to have new partitions used
Firmware Updating
There are two modes in which you can update the firmware.
The first mode is basic FWDN mode. The second mode with a blank nand is a factory USB host mode boot, that works even if the nand was completely erased by accident, or empty at the production line.
Warning: Each device has a unique serial. Do not select to overwrite it in the 'Tools - Options' menu!!
It is strongly advised to write down your serial after doing a basic FWDN flash, in case of emergency!
Basic FWDN is also outlined in the Chinese document:
http://www.zonko.nl/files/tcc/CBS7001 Android Instructions v1.01.pdf
Use it a basis for upgrading in this mode.
Basic FWDN mode
This is triggered by the following procedure, and the standard way to upgrade these devices:
Tablet side:
- Unplug tablet from the PC!
- Power off the tablet. Insert the power plug (required!)
- Press & hold finger on the touch screen, and then press & hold the powerbutton.
- The tablet powers up, and remains on the splash screen.
PC Side:
- Install the VTC drivers on your PC (tested OK on Win7 & WinXP 32 bit)
- Set up FWDN before plugging in the tablet
- Optional: Browse & add LK.ROM as a single file when coming from another partition layout, flash and reboot the tablet afterwards, then do the steps below. (You can skip this step, if you are staying on the same MTD layout i.e. flashing the same firmware revision you are on.)
- Browse & add the LK.ROM file.
- Browse & add the tcc8900_mtd.img file.
- Ensure no options are selected in the Tools - Options menu or you loose the mac/serial!
- Plug the tablet into USB
- Click the Nand area map and create a FAT partition for the remaining space.
- Yes, thats 'click on the square below the text' where it shows the block See this picture.
- If you're going to a different MTD layout, choose 'low format' in the dropdown.
- Click Start, and patiently wait.
USB Host boot mode
19-8-2010: No longer needed!
Fun_ figured out the LK.ROM holds the partition info. So if you're coming from another layout, simply flash LK.ROM first. The below procedure remains as a service for those that accidently bricked the device.
This mode is triggered when you erase the entire flash by accident, or when you put the switch on the mainboard inside your tablet to the other position.
You will need to add a bootrom to the FWDN folder where the .exe for FWDN resides. You can get that bootrom from here.
In this mode, the tablet will boot when connected by USB to the PC and init the cpu. After that, it can be flashed the same way as above. In this case you'll need to fiddle with the settings under 'Tools - Options' to set back the serial to what it was before the 'accident'.
If you desire, WinCE can be flashed in this way, if you kill the nand using flash_eraseall under Android..

Uninstall Chinese apps (18-08-2010) (thanks to Asure)
Code:
adb pull /system/app/ ./app
adb shell rm /system/app/91pandaspace_v2.3.apk
adb shell rm /system/app/himarket.apk
adb shell rm -r /data/dalvik*
adb shell sync
adb shell reboot

Official Firmware Download Link:
http://www.huashiguang.com/service.html
* * *
naobsd teardown:
http://twitpic.com/2do3a6
* **
I can open up a forum for you at:
Androidtablets.net
For now, it's a thread here
If a couple of you are up for it, that is. XDA is alright for dev talk though.
* * *
I repacked recovery.img earlier before:
http://www.multiupload.com/3N9VPWXS53
I unpacked Asure's boot.img using instructions from here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Then took the Augen Gentouch recovery, unpacked that as well to replace the ramdisk
The stock 297 recovery image is really large (10mb? Augen is 3mb with clockwork) and has a bunch of useless stuff in it.
So Asure, your recovery image didn't boot? I got all excited...
Edit: repacking doesn't work apparently.
I need to get myself one

I tried to repack the recovery.img using all the methods outlined here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
They all produce an image that looks fine in a hex editor at first glance, but fails to boot on a real device (After flashing it with flash_image recovery /sdcard/recovery.img for example)
I'm pretty sure there's a TTL serial port in the device, but i'll need some time to sort that out. I asked Koush for help, perhaps he can see what is wrong with the image.

Root Holding...
I have the model similar to the Apad with the hardware buttons. The Augen root method worked fine and looks to be holding so far, no stability issues or lockups using SetCPU with 120/720 scaling . I can provide some assistance from the "third" model with direction as needed.
My device is actually showing #320. My partition layout is similar to #297.

Latest Firmware update failure
I tried to flash the new firmware from HSG (16-8-2010)
but everytime it failed with this error
[ERROR] The old version(=0x07000002) device can't support 'MTD' fwdn area image.
i followed the same steps when i did the 13-8 update.
Anybody tried to flash it with succes ?
What am i doing wrong this time?

Please read & follow the steps in the second post. Low-format to get the new MTD layout.
Also, please keep this a dev topic. This is not HSG customer support

First, credits to Koush for his amazing recovery, the Android scene would be completely different if it wasn't for you!
Second, i wonder who @google thought it would be a great idea to force a huge download of 4.5GB + apps needed to compile a 13kb mkbootimg.
Anyway, with some files from someone else's kitchen (only 15mb download) i managed to compile mkbootimg with the new --pagesize parameter from Koush.
(This recovery's kernel --base 40000000 and requires --pagesize 1000 to work properly.)
I've updated the second post with the working recovery.
Also the one-click root.bat is back.
Enjoy your weekend!

Recovery is now working thanks to Georg77cz who provided unmissable help with testing this!
Check http://twitter.com/Asure007 for some pics. I'll upload the recovery tomorrow. For now, only confirmed to work on #348 roms! (older roms don't honour adb shell reboot)

So, now that we can do custom roms/updates/zips, does anyone have Dutch strings.xml for Settings.apk and SettingsProvider.apk from a Android 2.1 release ? HSG did not include this language as an option in any of the stuff on the tablet..
Edit: Never mind, i've pulled them off the emulator and added the sections that were missing (HDMI Output selection and such.)

Accessing Flash Mode MID701
I am not sure if you want to track here or in another thread, but I was able to find the right combo to access safe-mode/flashing mode on the 3rd device, MID701 with the #320 firmware.
To access the flashing mode for a MID701 device. After you have prepped your Telechips VTC driver and have FWDN running, do the following in order:
1) Flip the ON/OFF switch to the OFF Position
2) Connect the AC Adapter
3) Connect the USB Cable
4) Press and Hold the Home+Back buttons on the top of the device (both sides of the "rocker" must be depressed)
5) Flip the ON/OFF switch to the ON Position
In a matter of seconds you should get driver/telechips prompts and FWDN will light up. The screen WILL NOT come on in this mode.
After making a few backups and records, I may attempt to install the #348 firmware tomorrow.

I would suggest to ensure you have a working flash to go back to. From tests we did with #320 on HSG x5a the video is not working (white screen). ADB still works and we could flash_image back a #297 kernel(boot.img) into it to get video back & working.
If you really want to try something, try Clockwork Recovery for #320 tablets: http://bit.ly/aA06cY and let me know if it works

I can flash it but it doesn't escape the fact that I can't get to recovery from #320 lol. I will probably wait until the supplier releases the firmware Monday, so I have an absolute recovery path. Will post back with any success.

You can use ADB to get into recovery: adb shell reboot recovery
Or, if you're a windows user, install Droid Explorer, and use the option in the menu.
Or, if you want, install Rom manager from market, or reboot control widget. Plenty of options
Edit: Also, no need to wait for your supplier, i've put #320 here:
http://www.zonko.nl/files/tcc/Haina.android.320.7z

Few new things to report.
- I located a firmware that is #330 from Pandawill that works on my device. The market works, and it appears to have native support for playing xvid files in the gallery which my #320 build could not do, and I am unsure if the #348 builds have the ability.
-It feels a bit snappier than my #320 build.
-The #330 build also responds to the reboot recovery, which results in the Triangle Android update screen we have all seen before.
-Clockwork recovery also works on my device. I can scroll the recovery menu with the "Home" side of the rocker button. Clockwork reports that the back button is enabled, so it should work as well. The problem is the device is programed with the front button as a Sleep button, so it turns the screen on and off at the recovery menu. If I could remap the buttons, I should be in business.
I may dump the MTD image into one of my linux boxes and try to modify the partitioning a bit. Is there an easy way to modify the size of the data partition. The default images only give 256MB for apps, which seems a bit small considering all of the devices have 2/4GB internal memory.

LCD Density
For those who want a bit more screen real estate, you can modify the lcd density in the build.prop. I switched to 161 and it really scales well in some applications like the browser. Other places like the the status bar menus, and some applications, so no honor the new density and will not render scaled. From some translated notes 161, 162, and 180 seem to be the best values for higher density over the default of 240
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 161
adb pull /system/build.prop /directory/to/store/build.prop
edit your build.prop
adb push /directory/to/new/build.prop /system/build.prop
adb reboot

No sleep?
I've got the X5A yesterday and it came loaded with firmware #348. Rooted it last night and it's quite a brilliant little device!
I surfed the net for a bit and left it idle for the entire night last night, and it promptly ate around 40% of the battery. Spare Parts shows that it hasn't been sleeping properly (just like my old Samsung Galaxy) and that Wifi was running the entire time.
I looked on logcat and this line keeps popping up, not sure if it's causing the issue?
V/BatteryService( 937): lwgmUsbOnline
Googled it but nothing seemed to come up...

helfrez said:
Is there an easy way to modify the size of the data partition. The default images only give 256MB for apps, which seems a bit small considering all of the devices have 2/4GB internal memory.
Click to expand...
Click to collapse
As far as i know, the MTD partitioning is done inside LK.ROM.
You can try to change it in a hex editor, and see if that works. I'm not sure if the CRC changes, and it we can even raw hex edit it.. (200+mb for /data is already pretty good..)
Suggested steps:
- Using a hexeditor on lk.rom you can do a search for 'BMPG'
- Around 0x4d350 you should find the mtd table.
- You can see the partition names, and sizes.
- For example, in '#297' LK.ROM, this is at 350Mbytes (00 00 00 D1 00 00 00)
- Try to change to 00 00 00 FF 00 00 00, see what happens
(If this works it's for all TCC related devices, and we can get an even huger /data partition hehehe.)

[Q] BeBook 7" Live Tablet

Does anyone have this tablet? I can't find this tablet on the website.
I want to know if this tablet can be upgraded to v3.0 or higher when ics comes on CyanogenMod?
Technical Specifications
Weight: 426 gr
Dimensions: 202 x 140 x 11 mm
CPU Samsung Cortex A8 1.0 GHZ
OS: Android 2.2
WiFi 802.11 b/g/n
Bluetooth
Capacitive Multi Touch Screen
7" TFT-LCD Display
SDRAM 512 MB
4 GB Internal Memory
Micro SD/SDHC slot (Up to 32 GB)
G-Sensor
Mini-HDMI port out
Mini-USB port
Microphone
Adobe Flash Compatible
Camera: 2 MP
2 Stereo Speakers

I've the exact same question about the Cyanogen Mod.
Also, I would like to know if it's possible to perform a COMPLETE back up (root or nand backup) without this mod. (without nandroid backup)
The device is also released as the BQ DaVinci. That company released a firmware update to Gingerbread a couple of days ago.
However, I'm a bit reluctant to install it, because it'll change the splash screen and who knows what else.
The update procedure seems to be different from other devices: you have to put a folder called SDFUSE on the root of the SD-card and reboot. The folder contains these files:
SDFUSE
--> ramdisk-uboot.img
--> sdfuse.txt
--> system.img
--> u-boot.bin
--> zImage
Does anyone have any idea on how to reverse-assemble these files (i.e. extract or replace boot splash screen,...)

Mahalaleel said:
I've the exact same question about the Cyanogen Mod.
Also, I would like to know if it's possible to perform a COMPLETE back up (root or nand backup) without this mod. (without nandroid backup)
The device is also released as the BQ DaVinci. That company released a firmware update to Gingerbread a couple of days ago.
However, I'm a bit reluctant to install it, because it'll change the splash screen and who knows what else.
The update procedure seems to be different from other devices: you have to put a folder called SDFUSE on the root of the SD-card and reboot. The folder contains these files:
SDFUSE
--> ramdisk-uboot.img
--> sdfuse.txt
--> system.img
--> u-boot.bin
--> zImage
Does anyone have any idea on how to reverse-assemble these files (i.e. extract or replace boot splash screen,...)
Click to expand...
Click to collapse
There is not much help here..
I think we can forget an answer to our question

From experience I can say 2.3.4 DaVinci upgrade works fine on BeBook Live, even Angry Birds Space is now playable!

Indeed so, I discovered that as well.
But... still no possibility to upgrade to a custom ROM apparently?

AGSO Somx 7 GS20 has same format for their ROMs. In my understanding:
zImage - linux kernel compressed
u-boot-config - ???
ramdisk-uboot.img - ram disk image for loading
system.img - image of /system disk
To convert other ROMs into this format you have to get kernel and ramdisk images from boot.img, then make system partition image (create virtual disk with same size, make filesystem on it, move all /system files to the disk).

After some researching:
zImage - linux kernel gzip-compressed (just kernel, with empty initramfs inside) with built-in unpacker code at start
u-boot-config.bin - u-boot loader and/or its config (perhaps, stage 2 loader as S5PC110 has two-stage loader)
ramdisk-uboot.img - initramfs image (initramfs archive by cpio, then gz [output name "ramdisk"], then mkimage from u-boot distribution)
system.img - image of /system disk (ext4, not compressed)

BQ put ICS (Android 4.0) online for the BQ DaVinci, works fine also (booting takes a bit). Definitely a good idea if you still are using the device, Skype and so on works smooth!

[Q] Help unbrick AMLogic aml8726-mx tablet

Hi, i want some help with unbricking an aml8726-mx tablet. It's Prestigio Multipad Prime Duo, 7" 1024x600 tablet with 16gb internal storage and micro-sd card slot. It has only Power and + - volume buttons.
I've bricked it by flashing official firmware with default recovery. Entered recovery, made wipe, than installed update.zip from sd card. Progress bar started to move, indicating what process is on the way. And than in about 20%(no real percentage was in that recovery) tablet first freezed and than turned off. From this point there was no reaction on buttons, no display(even no backlight) - nothing. Connecting it to PC made the power on light flashing every 1 second(i guess). No device found by PC. I've tried turning on with - and + pressed, with both, without pressing anything - no luck.
So it was deep brick. Later i have found some info about 5th and 6th pins on NAND chip inside tablet, if those pins are connected to each other, after turning on tablet will be discovered by PC as M6 device. That worked! After hours dancing around AML usb flashing tool i was able to boot some uboot on tablet, started some recovery(not on the screen, it's still black as night), connect to recovery with ADB and trying to flash BOOT, BOOTLOADER and RECOVERY.
What i've tried:
1)adb push boot.img, boot loader.img and recovery.img i get from official firmware for this tablet
2)to make sure what my files now exists on tablet. I've pushed them to /cache/ so
Code:
#cd /cache/
#ls
and ls told me what my .img files are there
3)tried to flash
Code:
#flash_image boot /cache/boot.img
#flash_image bootloader /cache/bootloader.img
#flash_image recovery /cache/recovery.img
And here is a problem - each of those command gave me that:
error scanning partitions exit with code -1
I can't flash bootloaders and recovery. I've googled for days and still dont get it - why that "partition scaning" errors and what should i try.
If anyone can help me with that, or is there some different method of flashing it - i will be highly appreciated. I've used this tablet for less than a week and now it's totally bricked what i can't bring it back to life.

Same issue
I have the exact same problem! Could anyone help please?
Futaba0rus said:
Hi, i want some help with unbricking an aml8726-mx tablet. It's Prestigio Multipad Prime Duo, 7" 1024x600 tablet with 16gb internal storage and micro-sd card slot. It has only Power and + - volume buttons.
I've bricked it by flashing official firmware with default recovery. Entered recovery, made wipe, than installed update.zip from sd card. Progress bar started to move, indicating what process is on the way. And than in about 20%(no real percentage was in that recovery) tablet first freezed and than turned off. From this point there was no reaction on buttons, no display(even no backlight) - nothing. Connecting it to PC made the power on light flashing every 1 second(i guess). No device found by PC. I've tried turning on with - and + pressed, with both, without pressing anything - no luck.
So it was deep brick. Later i have found some info about 5th and 6th pins on NAND chip inside tablet, if those pins are connected to each other, after turning on tablet will be discovered by PC as M6 device. That worked! After hours dancing around AML usb flashing tool i was able to boot some uboot on tablet, started some recovery(not on the screen, it's still black as night), connect to recovery with ADB and trying to flash BOOT, BOOTLOADER and RECOVERY.
What i've tried:
1)adb push boot.img, boot loader.img and recovery.img i get from official firmware for this tablet
2)to make sure what my files now exists on tablet. I've pushed them to /cache/ so
Code:
#cd /cache/
#ls
and ls told me what my .img files are there
3)tried to flash
Code:
#flash_image boot /cache/boot.img
#flash_image bootloader /cache/bootloader.img
#flash_image recovery /cache/recovery.img
And here is a problem - each of those command gave me that:
error scanning partitions exit with code -1
I can't flash bootloaders and recovery. I've googled for days and still dont get it - why that "partition scaning" errors and what should i try.
If anyone can help me with that, or is there some different method of flashing it - i will be highly appreciated. I've used this tablet for less than a week and now it's totally bricked what i can't bring it back to life.
Click to expand...
Click to collapse

bal2nis said:
I have the exact same problem! Could anyone help please?
Click to expand...
Click to collapse
Bump, anyone?

Futaba0rus said:
Bump, anyone?
Click to expand...
Click to collapse

Hi I have a sirius Nvsbl equals this model and also takes AML8726. Turns out my tablet is dead and the clearing to see if you can revive and has a pin GND, TX, RX and vcc and this gives me the idea that it is a port to relive problem is not with that program .. I guess with riff box can but I have this box I have several cables Nokia I'm sure it is compatible (DKU5) the problem is with software that can burn the boot?
Enviado desde mi GT-I9300 usando Tapatalk 2

I have exactly the same problem. I managed to flash it with Crystal batch 3 SW. Can acess shell thru adb, but the screen is black too.
I also have boot.img, recovery.img, factory.img, system, but I don't have the bootloader.
Once I flash it with the files mensioned above the tablet doesn't even boot and I have to shunt the TF boot contacts that exist on the board.
It is a DINO 7.17.
AML8726-MX - dual core 1.5GHz
1GB RAM
8GB internal ROM
According to build.prop (original) the board is:
ro.product.model=DINO7.17
ro.product.brand=MID
ro.product.name=DINO7.17
ro.product.device=g08ref - can't seem to find any firmware with this reference
ro.product.board=g08ref
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
the original mtd table:
mtd0: 00400000 00100000 "bootloader"
mtd1: 00800000 00400000 "logo"
mtd2: 00800000 00400000 "aml_logo"
mtd3: 00800000 00400000 "recovery" - have it
mtd4: 00800000 00400000 "boot" - have it
mtd5: 30000000 00400000 "system" - have it
mtd6: 08000000 00400000 "factory" - have it
mtd7: 08000000 00400000 "cache"
mtd8: 90000000 00400000 "userdata"
mtd9: 12d000000 00400000 "NFTL_Part"
Did you fix your tablet?
Could someone help us out here?
:crying:
Futaba0rus said:
Hi, i want some help with unbricking an aml8726-mx tablet. It's Prestigio Multipad Prime Duo, 7" 1024x600 tablet with 16gb internal storage and micro-sd card slot. It has only Power and + - volume buttons.
I've bricked it by flashing official firmware with default recovery. Entered recovery, made wipe, than installed update.zip from sd card. Progress bar started to move, indicating what process is on the way. And than in about 20%(no real percentage was in that recovery) tablet first freezed and than turned off. From this point there was no reaction on buttons, no display(even no backlight) - nothing. Connecting it to PC made the power on light flashing every 1 second(i guess). No device found by PC. I've tried turning on with - and + pressed, with both, without pressing anything - no luck.
So it was deep brick. Later i have found some info about 5th and 6th pins on NAND chip inside tablet, if those pins are connected to each other, after turning on tablet will be discovered by PC as M6 device. That worked! After hours dancing around AML usb flashing tool i was able to boot some uboot on tablet, started some recovery(not on the screen, it's still black as night), connect to recovery with ADB and trying to flash BOOT, BOOTLOADER and RECOVERY.
What i've tried:
1)adb push boot.img, boot loader.img and recovery.img i get from official firmware for this tablet
2)to make sure what my files now exists on tablet. I've pushed them to /cache/ so
Code:
#cd /cache/
#ls
and ls told me what my .img files are there
3)tried to flash
Code:
#flash_image boot /cache/boot.img
#flash_image bootloader /cache/bootloader.img
#flash_image recovery /cache/recovery.img
And here is a problem - each of those command gave me that:
error scanning partitions exit with code -1
I can't flash bootloaders and recovery. I've googled for days and still dont get it - why that "partition scaning" errors and what should i try.
If anyone can help me with that, or is there some different method of flashing it - i will be highly appreciated. I've used this tablet for less than a week and now it's totally bricked what i can't bring it back to life.
Click to expand...
Click to collapse

Same problem here
I have the same problem with my prime duo, but I have a problem with aml flash tool too. Can you link the files (bootorig... config_progress.xml etc) what are worked for you?

I unbricked my android tv box, AML8726-MX g18ref box with a special sd card. I had similar problem....
Sent from my ST18i using xda app-developers app

BenniBenassi said:
I unbricked my android tv box, AML8726-MX g18ref box with a special sd card. I had similar problem....
Sent from my ST18i using xda app-developers app
Click to expand...
Click to collapse
Hello, can you tell us what kind off special SD card?
Thanks

ruyzalim said:
Hello, can you tell us what kind off special SD card?
Thanks
Click to expand...
Click to collapse
Yes I can.
It is a Generic MX Droid-TV (AML8726-MX G18REF) box, now with AndroidGadget ROM.
I used this program below to create a special SD card (with a new image), which booted and fixed my box, with AndroidGadget ROM.
FILE: DD
FILE: IMAGE
FILE: ROM (pw: androidgadget.co.uk)
The DD program used to create the special bootable SD only works under Win XP (Under VMware is also OK)
I hope it will be of help.
If anyone makes a kernel for this that supports CWM, CPU speed mod and CyanogenMod, I'd be grateful

BenniBenassi said:
Yes I can.
It is a Generic MX Droid-TV (AML8726-MX G18REF) box, now with AndroidGadget ROM.
I used this program below to create a special SD card (with a new image), which booted and fixed my box, with AndroidGadget ROM.
FILE: DD
FILE: IMAGE
FILE: ROM (pw: androidgadget.co.uk)
The DD program used to create the special bootable SD only works under Win XP (Under VMware is also OK)
I hope it will be of help.
If anyone makes a kernel for this that supports CWM, CPU speed mod and CyanogenMod, I'd be grateful
Click to expand...
Click to collapse
Thank you very much

WARNING, IF YOU DO NOT KNOW WHAT YOU ARE DOING, THEN DO NOT DO IT.
1) THE PROCESS IS ENTIRELY AUTOMATED.
2) NO NEED TO MANUALLY INSTALL ANYTHING ONCE THE PROCESS IS STARTED.
3) THE 2 ERRORS COMING AT THE END OF THE RECOVERY PROCESS ARE PART OF THE PROCESS.
AN IMPORTANT REMINDER:
If you can not follow the instructions correctly or you do not understand them, ASK BEFOREHAND on the FORUM and UNDER NO CIRCUMSTANCES PERFORM THE RECOVERY.
Under no circumstances should you do any manual installation of any of the files located on the recovery sd card.
The result may be a permanently bricked box with no way to recover.
Here is an almost-idiot proof ROM install and UNBRICK method instruction for AML8726-MX (M6) Android TV Box (1gb / 8gb dual core):
If you manage to brick your box, it is your fault entirely. I did the recovery image for myself and decided to share it with community. Use at your own reponsibility.
Also known as:
G18REF
DROIDBOX iMX6
DROIDTV MX
MX2REF
MATRICOM G-BOX MX2
or any generic Android MX Media Box with same hardware, AML8726MX 1G/8G set top box
HD18 V2.2
HD18 V2.21
HD18 V2.22
I created an easy-install SD Card image from this ROM: Matricom G-Box Midnight MX2 v1.1.5+ (ROM DATE = 9th of August 2013)
The ROM was used for creating the special install SD card.
It is very simple to install, just insert a 4gb or larger SD CARD into Windows PC and use this program to set up the card:
DOWNLOAD THIS:
http://hddguru.com/software/HDD-Raw-Copy-Tool/HDDRawCopy1.02Portable.exe
Then use the extracted sd card image file as a source and set a target to your sd card (4 gb), it writes the image, close the HDD RAW COPY program and eject the card (SAFELY - choose eject from PC, right click menu + eject).
DOWNLOAD THIS:
FILE: Matricom Midnight G-BOX MX2 v1.1.5+ image (August 9th, 2013)
WARNING: THIS METHOD WILL ERASE EVERYTHING FROM YOUR MX BOX AND INSTALL A NEW ROM. USE AT YOUR OWN DISCRETION.
As an added BONUS this will UNBRICK your device in case it is bricked.
Matricom image (Android 4.2.2): OTA works for XBMC etc
- Make sure MX device is powered off and power cable removed.
- Insert SD card you just created.
- Insert a match or a toothpick to reset hole - you will feel a click. (it is the AV hole in the back)
- Power on the MX box by inserting power cable, while holding the match in the reset hole.
- It will boot to recovery and start installing ROM.
- After finishing it will give 2 errors - these do not matter.
- Remove power cable and insert it again, the device will boot as MATRICOM MIDNIGHT G-BOX MX2
This is how the board looks from inside: (NO NEED TO OPEN FOR INSTALLING)
{
"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"
}

BenniBenassi said:
Here is an almost-idiot proof ROM install and UNBRICK method instruction for AML8726-MX (M6) Android TV Box (1gb / 8gb dual core):
Also known as:
G18REF
MX2REF
GENERIC MX MEDIA BOX
HD18 V2.2
HD18 V2.21
I created an easy-install SD Card image from this ROM: Matricom G-Box Midnight MX2 v1.1.5+ (ROM DATE = 9th of August 2013)
The ROM was used for creating the special install SD card.
It is very simple to install, just insert a 4gb or larger SD CARD into Windows PC and use this program to set up the card:
DOWNLOAD THIS:
http://hddguru.com/software/HDD-Raw-Copy-Tool/HDDRawCopy1.02Portable.exe
Then use the extracted sd card image file as a source and set a target to your sd card (4 gb), it writes the image, close the HDD RAW COPY program and eject the card (SAFELY - choose eject from PC, right click menu + eject).
DOWNLOAD THIS:
FILE: Matricom Midnight G-BOX MX2 v1.1.5+ image (August 9th, 2013)
WARNING: THIS METHOD WILL ERASE EVERYTHING FROM YOUR MX BOX AND INSTALL A NEW ROM. USE AT YOUR OWN DISCRETION.
As an added BONUS this will UNBRICK your device in case it is bricked.
Matricom image (Android 4.2.2): OTA works for XBMC etc
- Make sure MX device is powered off and power cable removed.
- Insert SD card you just created.
- Insert a match or a toothpick to reset hole - you will feel a click. (it is the AV hole in the back)
- Power on the MX box by inserting power cable, while holding the match in the reset hole.
- It will boot to recovery and start installing ROM.
- After finishing it will give 2 errors - these do not matter.
- Remove power cable and insert it again, the device will boot as MATRICOM MIDNIGHT G-BOX MX2
This is how the board looks from inside: (NO NEED TO OPEN FOR INSTALLING)
Click to expand...
Click to collapse
Thanks for this
Question, I thought Matricom prevented loading their firmware on non Matricom boxes, will this definitely work on a DroidTV MX?
Thanks

jackhill said:
Thanks for this
Question, I thought Matricom prevented loading their firmware on non Matricom boxes, will this definitely work on a DroidTV MX?
Thanks
Click to expand...
Click to collapse
IF IT IS one of these and the board looks like the one on the picture:
G18REF
MX2REF
GENERIC MX MEDIA BOX
HD18 V2.2
HD18 V2.21
Make sure you check it is the correct hardware.
Don't forget to back up anything you need from it, since this will format everything and install a new rom.
ANSWER IS: YES
This is a special AMLogic Boot SD card image and YES it works.
This is how the MX box looks like:
MX Android 4.2.2 TV Box XBMC Amgloic 8726-MX Dual Core Unboxing
.

can not to flash the firmware with usb metode
Hi to all!
I have a problem with my eboda e300 tablet!
Tablet is bricked and works strange!!
With tablet off when connect this to pc into amlogicburnning software is detected like "standard enhanced" without press the button power and home.
My problem : can not to flash this tablet with original firmware!
Log is:
W/ Import upgrade file E:\Android\AML8726MX\eboda E300_SW-pc-1113-RD_20121129.zip
W/ [P3][20:50:01]Loading spl ...
W/ [P3][20:50:02]Transfer Complete! total size is 18556 Bytes
W/ [P3][20:50:04]Transfer Complete! total size is 500204 Bytes
W/ [P3][20:50:16]After load uboot, disconnect, mBurnWaitCount: 9
W/ [P3][20:50:19]After load uboot, disconnect, mBurnWaitCount: 12
W/ [P3][20:50:21]wait uboot run ,scan system again!!!
W/ [P3][20:50:22]After load uboot, disconnect, mBurnWaitCount: 15
W/ [P3][20:50:25]After load uboot, disconnect, mBurnWaitCount: 18
W/ [P4][21:47:32]Identify get 0, maybe device is reset, back from 0 step and retry
When try to flash this command work :
<command sn="0" path="usb_spl.bin" address="0xd9000000" run="true">load spl</command>
<command sn="1" path="u-boot-orig.bin" address="0x8f800000" run="false">load uboot</command>
<command sn="2" >crc 0x8f800000 size value</command>
and stopped here :
<command sn="3" >run 0x8f800000</command>
In this moment the tablet is not detected into hardware device!!
Thanks to all to any sugestion!:crying:

Confirmed working on my DroidTV MX
Thanks so much

BenniBenassi said:
Here is an almost-idiot proof ROM install and UNBRICK method instruction for AML8726-MX (M6) Android TV Box (1gb / 8gb dual core):
Also known as:
G18REF
MX2REF
GENERIC MX MEDIA BOX
HD18 V2.2
HD18 V2.21m
I created an easy-install SD Card image from this ROM: Matricom G-Box Midnight MX2 v1.1.5+ (ROM DATE = 9th of August 2013)
The ROM was used for creating the special install SD card.
It is very simple to install, just insert a 4gb or larger SD CARD into Windows PC and use this program to set up the card:
DOWNLOAD THIS:
http://hddguru.com/software/HDD-Raw-Copy-Tool/HDDRawCopy1.02Portable.exe
Then use the extracted sd card image file as a source and set a target to your sd card (4 gb), it writes the image, close the HDD RAW COPY program and eject the card (SAFELY - choose eject from PC, right click menu + eject).
DOWNLOAD THIS:
FILE: Matricom Midnight G-BOX MX2 v1.1.5+ image (August 9th, 2013)
WARNING: THIS METHOD WILL ERASE EVERYTHING FROM YOUR MX BOX AND INSTALL A NEW ROM. USE AT YOUR OWN DISCRETION.
As an added BONUS this will UNBRICK your device in case it is bricked.
Matricom image (Android 4.2.2): OTA works for XBMC etc
- Make sure MX device is powered off and power cable removed.
- Insert SD card you just created.
- Insert a match or a toothpick to reset hole - you will feel a click. (it is the AV hole in the back)
- Power on the MX box by inserting power cable, while holding the match in the reset hole.
- It will boot to recovery and start installing ROM.
- After finishing it will give 2 errors - these do not matter.
- Remove power cable and insert it again, the device will boot as MATRICOM MIDNIGHT G-BOX MX2
This is how the board looks from inside: (NO NEED TO OPEN FOR INSTALLING)
Click to expand...
Click to collapse
Must be an idiot. I can't get the card to flash without an error writing after it says 100. If I try it the box boots into recovery but nothing flashes to the box.. I've tried 2 different sd cards

joeblow3 said:
Must be an idiot. I can't get the card to flash without an error writing after it says 100. If I try it the box boots into recovery but nothing flashes to the box.. I've tried 2 different sd cards
Click to expand...
Click to collapse
Your box is not the correct hardware for this ROM.
It is not for other hardware than mentioned in my OP.

It can work in the G02REF(1gb / 4gb dual core)?
---------- Post added at 07:42 AM ---------- Previous post was at 07:35 AM ----------
BenniBenassi said:
Here is an almost-idiot proof ROM install and UNBRICK method instruction for AML8726-MX (M6) Android TV Box (1gb / 8gb dual core):
Also known as:
G18REF
MX2REF
GENERIC MX MEDIA BOX
HD18 V2.2
HD18 V2.21
I created an easy-install SD Card image from this ROM: Matricom G-Box Midnight MX2 v1.1.5+ (ROM DATE = 9th of August 2013)
The ROM was used for creating the special install SD card.
It is very simple to install, just insert a 4gb or larger SD CARD into Windows PC and use this program to set up the card:
DOWNLOAD THIS:
Then use the extracted sd card image file as a source and set a target to your sd card (4 gb), it writes the image, close the HDD RAW COPY program and eject the card (SAFELY - choose eject from PC, right click menu + eject).
DOWNLOAD THIS:
WARNING: THIS METHOD WILL ERASE EVERYTHING FROM YOUR MX BOX AND INSTALL A NEW ROM. USE AT YOUR OWN DISCRETION.
As an added BONUS this will UNBRICK your device in case it is bricked.
Matricom image (Android 4.2.2): OTA works for XBMC etc
- Make sure MX device is powered off and power cable removed.
- Insert SD card you just created.
- Insert a match or a toothpick to reset hole - you will feel a click. (it is the AV hole in the back)
- Power on the MX box by inserting power cable, while holding the match in the reset hole.
- It will boot to recovery and start installing ROM.
- After finishing it will give 2 errors - these do not matter.
- Remove power cable and insert it again, the device will boot as MATRICOM MIDNIGHT G-BOX MX2
This is how the board looks from inside: (NO NEED TO OPEN FOR INSTALLING)
It can work in the G02REF(1gb / 4gb dual core)?
Click to expand...
Click to collapse

I have no idea but I think NOT.
Sent from my ST18i using xda app-developers app

[PX5][Android 10] Patched recovery

This is the Android 10 recovery image by HCT (version 10.3.1) patched to skip signature checking on .zip files
Tested on MTCE_LM (Eunavi). Use at your own risk
It can be flashed from a root shell (either adb or via terminal emulator) by performing the following steps
1. upload recovery via adb
Code:
adb push hct_recovery_patched.img /sdcard/
2. flash recovery
Code:
# backup current recovery
dd if=/dev/block/by-name/recovery of=/sdcard/recovery_backup.img
# write new recovery
dd if=/sdcard/hct_recovery_patched.img of=/dev/block/by-name/recovery
NOTE: If you do not disable the "flash_recovery" service in /init.rc, AND you have a stock kernel, recovery will be restored to the original version after rebooting.
There are 3 ways to avoid this:
- Flash magisk (or a modified kernel) while in recovery. The patch will then fail to apply and recovery won't be overwritten
- Disable "flash_recovery" by doing "adb remount" and editing /init.rc (comment out the following)
Code:
service flash_recovery /system/bin/install-recovery.sh
class main
oneshot
- Neuter the service by either:
- removing /system/bin/install-recovery.sh​- replacing /system/bin/install-recovery.sh with a dummy script​- removing /system/recovery-from-boot.p​

Woo-hoo, after hundreds of rubbish posts in the MTCD forums, we have a real development post!
Great work and thanks for sharing this, these forums need more like you.

Thanks for the kind comment!
I have to admit that it was frustrating to see the lack of information sharing on this forum, and the pervasive pay-per-use model.
I spent a lot of time just getting Android 10 installed (starting from Android 9), and i had to bring the head unit to my desk as working in the car was rather hard and all i achieved was a brick.
I unfortunately had to bring it back in the car now (can't sit on my desk forever) but, now that i figured out how to make bootable recoveries, i was wondering how hard it could be to have TWRP or at least a hassle-free recovery to install Android 10 from Android 9.
As a first step, this recovery makes it possible to install Magisk or other zip files without doing it manually within adb.
Cheers!

Your work is really good!
Thanks a lot for it.
Now you can also modify ROM's without signatur errors when installing.
Wouldn't it be good if we had an app like the ModInstaller ?
So a one click installation of the recovery without shell or adb.

I have now built an app.
And now need help.
Namely, in the app is the recovery and the script.
Unfortunately, the flash process is not started.
It always comes only the first message from the script.
The app is open source and the script and the recovery are in res/raw.
In the attach you will find the finished app and pictures.
If someone has a solution, he can write me or make a pull request on Github.
Source code:
GitHub - jamal2362/RK33XX-Custom-Recovery-Installer: Application for flashing custom recovery on Rockchip Android Head-Units.
Application for flashing custom recovery on Rockchip Android Head-Units. - GitHub - jamal2362/RK33XX-Custom-Recovery-Installer: Application for flashing custom recovery on Rockchip Android Head-Units.
github.com
The script:
RK33XX-Custom-Recovery-Installer/script at master · jamal2362/RK33XX-Custom-Recovery-Installer
Application for flashing custom recovery on Rockchip Android Head-Units. - RK33XX-Custom-Recovery-Installer/script at master · jamal2362/RK33XX-Custom-Recovery-Installer
github.com

First of all, congrats for the work!
DISCLAIMER:
I don't own ModInstaller, i have never bought a copy of it and i don't intend to do so.
Analysis is purely done from Youtube videos, open source code analysis and existing and openly available binary images.
I was working to figure out how to make a FLOSS alternative to ModInstaller.
The issues i found in all my attempts are the following:
- A6 recovery is the only one that can boot from SD Card (which can then be used to flash A9 -> A10 with the 2SD trick)
- (it took me a long time to pull these information together and unbrick my unit)​- The A6 recovery is unable to directly flash A10 RKAF/RKFW images (sdupdate.img) due to the code being too old
- a failure will be observed while writing super.img. This happens because the device needs to be repartitioned, and the A6 recovery is not doing it correctly​- A9 recovery is buggy. Booting it with no system installed will result in a black screen.
- it will only boot succesfully after being written by the A6 flash tool, which writes the "misc" partition with the recovery commands to run (the "hint" i get from this is that the misc partition is important)​- A10 recovery can't be loaded by the A6 recovery. I always got a black screen after flash. Is it a flash issue? is it an issue with the recovery itself? hard to know
Theory: maybe the recovery could be written over the kernel partition? ("boot")
This way, the recovery will always run after being flashed instead of requiring an explicit "enter recovery" trigger (buttons, misc partition, etc.)
Besides these experiments, in parallel, i did some bug fixing to this repository: https://github.com/liftoff-sr/rockchip-tool/commits/master (i'm "smx-smx")
That allows me to unpack nad repack "sdupdate.img" , "reduced recovery images" and "full IMG files".
With those tools. i tried to swap "recovery.img" in the A6 image, but i always got the black screen upon booting from SD.
Either A9/A10 breaks sdboot or the bootloader crashes before it gets there.
Since this also happens when being flashed, this could either be a bug in the flashing program or a bug in the boot stack (which fails to run recovery perhaps due to a dirty state of the internal flash). It's hard to know for sure without having a UART connection with the board.
BUT, we have an alternative, in the form of the recovery built-in ISP flash tool.
This is the code that reads "sdupdate.img" from the SD Card and flashes it
After reading the recovery source code, i realised that this code can only be triggered correctly when booting from the SD card.
It detects this state by reading /proc/cmdline and probing for specific values (https://github.com/rockchip-android...6f72b7d3123dab27135ac41d55029/sdboot.cpp#L206)
This means the bootloader can (and will) pass those arguments under specific conditions (https://github.com/rockchip-linux/u...c873f178c/arch/arm/mach-rockchip/board.c#L358)
If you check here https://github.com/rockchip-linux/u...3f178c/arch/arm/mach-rockchip/boot_mode.c#L47 you can see the magic word that needs to be written to the "misc" partition in order to trigger that code.
Note that, besides the well known "sdboot", "usbboot" is also possible.
I'm not sure if the ROM can physically boot from USB, but the bootloader and recovery do support (according to code) passing the flag to enable flashing from USB.
So, recapping, there are these ways we can try:
a - try to overwrite "boot" with "recovery" (but it might not work due to the partitioning layout, e.g. jumping from A6 -> A10)
- note: uboot might also need to be written when doing this.
b - making a modified "sdupdate.img" that flashes recovery on top of boot, and all the other core partitions like "misc", "uboot", "trust", "vbmeta"
c - writing "misc" from android in order to triggers the "rkfwupdate" mode
d - taking a dump of the first portion of the flash in various states (A6, A8, A9, A10), and having a "dd" that writes it back to the beginning of the flash (i suspect this is how ModInstaller does it)
Considering cases "b" and "c" depend on a recovery that can write them correctly (and the A6 one is buggy), this leaves us with "a" and "d"
Considering that ModInstaller does it in one shot, and doesn't seem to matter about the partitioning layout, i believe "d" might be the most viable option...
Using the "rockchip-tool" repository i linked from github, the partition table can be dumped from any .img file
You can observe "Image/parameter.txt" from the extracted firmware
This is the partition table from A6's recovery:
[email protected](uboot)
[email protected](trust)
[email protected](misc)
[email protected](resource)
[email protected](kernel)
[email protected](dtb)
[email protected](dtbo)
[email protected](vbmeta)
[email protected](boot)
[email protected](recovery)
[email protected](backup)
[email protected](security)
[email protected](cache)
[email protected](system)
[email protected](metadata)
[email protected](vendor)
[email protected](oem)
[email protected](frp)
[email protected](userdata)
And this is the partition table from A9's recovery
[email protected](uboot)
[email protected](trust)
[email protected](misc)
[email protected](resource)
[email protected](kernel)
[email protected](dtb)
[email protected](dtbo)
[email protected](vbmeta)
[email protected](boot)
[email protected](recovery)
[email protected](backup)
[email protected](security)
[email protected](cache)
[email protected](system)
[email protected](metadata)
[email protected](vendor)
[email protected](oem)
[email protected](frp)
[email protected](userdata)
Notice how uboot, trust, misc, resource, kernel, dtb, and others live in the same space. (2000, 4000, 6000, 8000, 10000, ...)
What we could do is create a raw blob that spans that address range, and "dd" it directly to /dev/mmcblk0 at the right offset.
So i would focus on converting recovery images to raw blobs, with recovery-as-kernel so it boots straight away on the first try.

Bump a real thread.

Is it possible to convert it to a file installed by SDDiskTool?

marchnz said:
Bump a real thread.
Click to expand...
Click to collapse
I created a flashing tool to flash recovery within Android, using Rockchip's own code: https://forum.xda-developers.com/t/...chip-firmware-flash-tool-for-android.4458299/

blala said:
I created a flashing tool to flash recovery within Android, using Rockchip's own code: https://forum.xda-developers.com/t/...chip-firmware-flash-tool-for-android.4458299/
Click to expand...
Click to collapse
This file hct_recovery.patched.img does not appear to be installed via rkupdate

sadaghiani said:
Is it possible to convert it to a file installed by SDDiskTool?
Click to expand...
Click to collapse
It needs to be converted, yes
I'll take a look this afternoon

blala said:
It needs to be converted, yes
I'll take a look this afternoon
Click to expand...
Click to collapse
Is it possible to create a boot image that includes moded recovery & magisk and moded kernel ?

If by image you mean firmware image then yes, it can be done with https://github.com/liftoff-sr/rockchip-tool
But what i would recommend is the modded recovery only, with the magisk .zip to use in Recovery
Otherwise you risk flashing a kernel that doesn't match with kernel modules or is otherwise not fully compatible with the installed system

blala said:
If by image you mean firmware image then yes, it can be done with https://github.com/liftoff-sr/rockchip-tool
But what i would recommend is the modded recovery only, with the magisk .zip to use in Recovery
Otherwise you risk flashing a kernel that doesn't match with kernel modules or is otherwise not fully compatible with the installed system
Click to expand...
Click to collapse
boot.img file included recovery+magisk+kernel

Flashing a boot.img (Kernel, for example) in an Android mobile phone via adb shell
Flashing a boot.img (Kernel, for example) in an Android mobile phone via adb shell - script.sh
gist.github.com

MTCD has separate boot and recovery partitions.
Perhaps you can adapt both recovery/kernel to be in the same image but the bootloader won't know about that (and will always boot from "recovery" partition)