Related
[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.)
this is a work-in-progress development project for porting CyanogenMod 7 (gingerbread/2.3.7) and ClockworkMod Recovery 5 to Telechips TCC8902 and TCC8803 tablets.
this is not perfect at all. and I'm very busy. progress will be very very slow. I may not be able to answer your question/request. if you have some idea for improvement, please do it freely.
there is no support from any makers/vendors. you must agree all risks by installing non-supported files, it may brick your tablet, and you may lose official support/warranty.
* YOU MUST READ CAREFULLY POST#1, #2, AND #3!
* DO NOT USE IF YOUR TABLET IS NOT LISTED BELOW. IT WILL BRICK YOUR TABLET!
* DO NOT USE FwTool APP. IT WILL BRICK TOUCHSCREEN!
* project page
http://androtab.info/telechips/cyanogenmod/
* supported tablets (TCC8902 with atheros wifi)
a-rival PAD NAV-PA80/83 capacitive (a.k.a. ViewQuest Slate 8")
a-rival PAD NAV-PA81 resistive
Cherrypal CherryPad America (a.k.a. NanoPad)
COBY Kyros MID7015(4K)/7016(8K) GB ROM (a.k.a. Emdoor EM71 singletouch, Optimist Gpad701)
ConCorde tab 7.1 GB ROM (a.k.a. DWCO UM700)
Dropad D10 (a.k.a. GOCLEVER TAB T73)
Emdoor EM51
Emdoor EM71 multitouch (a.k.a. Herotab G701, Lonpad D7)
Haipad M1001 GB ROM 4K(non-HY) and 8K(HY) (a.k.a. Musican U10, Telepad 10.1)
Haipad M701 GB ROM 4K(non-HY) and 8K(HY) (a.k.a. Musican U70, Pandawill G10 1st/3rd model)
HSG X5A (a.k.a. Herotab RK7, Pandawill G11 1st model)
HSG X5A-G (a.k.a. COBY Kyros MID7005, Herotab X5A, Pandawill G11 2nd model)
HSG X6D
HSG X6 GB ROM
inet S1008
Optimist Gpad802 GB ROM
Phecda P7 4K(non-HY) and 8K(HY) (a.k.a. TMARSS P7)
Phecda P7S GB ROM
Storage Options miScroll GB ROM
Storage Options Scroll 7" capacitive GB ROM
Storage Options Scroll 7" resistive 4K(non-S) and 8K(S)
Storage Options Scroll 8"
* supported tablets (TCC8902 with realtek wifi)
Haipad M701 512MB
RoverPad 3W T71
Yarvik TAB211 (a.k.a. EKEN MT705)
* supported tablets (TCC8803 with atheros wifi)
COBY Kyros MID7022 (a.k.a. ConCorde tab 7020, Emdoor EM73 capacitive HY30, Joyplus M778 capacitive HY30, Optimist Gpad702 HY30)
Emdoor EM73 capacitive GC2M 4K and 8K (a.k.a. mivvy MIDroid H23, Joyplus M778 capacitive GC2M, Kogan Agora, Optimist Gpad702 GC2M, Telepad 7C)
Emdoor EM73 resistive AK GC2M, HY30 and SX HY2M (a.k.a. DFP7002A8, Joyplus M778 resistive)
inet 11A3 resistive and 11A4 capacitive
LY-F521 with 1024x600 LCD (a.k.a. Diel Flick 7", Sense V7, Suli MY-7)
LY-F521 with 800x480 LCD
* supported tablets (TCC8803 with realtek wifi)
inet 11A5 capacitive
* current status (2011/10/29)
not work:
3G, bluetooth, camera, hardware accelerated video, GPS, HDMI, and many things which you expect to work
work:
accelerometer, audio, gapps, internal NAND flash, SD card, touchscreen with calibration app, USB host/device, wlan
* changelog
refer git log
* resources
http://www.cyanogenmod.com/ (What is CyanogenMod?)
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps (Google Apps)
http://wiki.cyanogenmod.com/index.php?title=Building_from_source
http://source.android.com/source/
http://review.cyanogenmod.com/#q,status:merged,n,z (CyanogenMod merged changes)
https://github.com/naobsd/cm_device_telechips_common
https://github.com/naobsd/cm_device_telechips_tcc8803
https://github.com/naobsd/cm_device_telechips_tcc8803rt (for realtek wifi models)
https://github.com/naobsd/cm_device_telechips_tcc8902gb (for TCC8902 with GB ROM)
https://github.com/naobsd/cm_device_telechips_tcc8902rt (for TCC8902 with realtek wifi models)
https://github.com/naobsd/cm_device_telechips_tcc8902 (for TCC8902 with Eclair ROM)
https://github.com/naobsd/cm_external_yaffs2/compare/gingerbread-naobsd (placeholder for patches to cherry-pick)
https://github.com/naobsd/cm_frameworks_base/compare/gingerbread-naobsd (placeholder for patches to cherry-pick)
https://github.com/naobsd/cm_packages_apps_TSCalibration
https://github.com/naobsd/cm_system_core/compare/gingerbread-naobsd (placeholder for patches to cherry-pick)
http://www.bernhard-ehlers.de/projects/unyaffs.html
* users' forum
http://scrolltabletforum.co.uk/site/viewtopic.php?f=15&t=1390 (Scroll)
* How to make backup of stock recovery
1. download dump-recovery-signed.zip and put it as update.zip on root of SD card (e.g. /sdcard/update.zip) *1 *2
2. install update.zip from stock recovery *3
stock recovery will be dumped as dumped_recovery.img and /proc/mtd will be copied as dumped_proc_mtd.txt on root of SD card. keep them in safe place.
* How to install ClockworkMod Recovery 5
1. make backup of stock recovery
2. download recovery.zip and put it as update.zip on root of SD card (e.g. /sdcard/update.zip) *1 *2
3. install update.zip from stock recovery *3
clockworkmod will be booted on next reboot recovery.
how to operate: MENU/VOL- = next(down), SEARCH/VOL+ prev(up), HOME/POWER = select, BACK = back
*1 if recovery is 3e, you can put it with any name on any directory in SD card
*2 some tablets/roms mount internal storage as /sdcard. confirm update.zip exists on root of SD card.
*3 some tablets/roms have system update function in Settings to install update.zip
* How to install ClockworkMod Recovery 5 (alternative)
a. flash recovery.img in recovery.zip by fastboot (if your tablet has fastboot mode)
b. flash recovery.img in recovery.zip by flash_image command on root shell
c. flash tcc_mtd.img with clockworkmod recovery.img by FWDN
you may need to delete /system/etc/install-recovery.sh before install (if it exists on your tablet)
* How to install CyanogenMod 7
1. install ClockworkMod Recovery 5
2. reboot recovery
3. make backup of stock ROM
4. wipe data/factory reset *4
5. install cyanogen.zip
6. reboot
7. touchscreen calibration *4 *5
*4 only if you are upgrading from non-CM7 ROM (CM7 1st install)
*5 only if you are using resistive touchscreen or misaligned capacitive touchscreen. if calibration is not needed, press BACK to cancel calibration.
* How to flash FWDN image (Windows PC is required)
i) prepare
1. download FWDN_V7_v2.13.exe
2. download & install VTC Driver v5.xx for your Windows PC
3. download lk.rom and tcc_mtd.img for your tablet (DO NOT USE FILES FOR OTHER TABLETS!)
4. connect power cable (do not use USB power for safety)
ii) flash bootloader(lk.rom) you can skip this step if you already flashed proper lk.rom or you don't have proper lk.rom for your tablet
1. start FWDN on PC
2. drag & drop lk.rom into FWDN window
3. (re)boot tablet into FWDN mode
4. connect PC and tablet (window popped and size of "NAND Data" is displayed in Area Map in FWDN window)
5. confirm checkbox of lk.rom is checked
6. click "Start" & wait complete
7. disconnect & reboot tablet into FWDN mode to use new(just flashed) bootloader
8. uncheck checkbox of lk.rom (it's ok if checked but no reason to flash again in next step)
iii) flash Android image and initialize internal NAND(FAT) partition
1. drag & drop tcc_mtd.img into FWDN window
2. (re)boot tablet into FWDN mode (if you forgot it in 7. in previous step)
3. connect PC and tablet
4. click "NAND Data" in Area Map in FWDN window *6 *7
5. fill "Image File Path" (use [...] button) *8
6. click "Create Image" (NAND Data.fai will be added in main FWDN window)
7. confirm checkbox of tcc_mtd.img and NAND Data.fai are checked
8. click "Start" & wait complete (take several minutes)
9. disconnect & reboot tablet
*6 creating new NAND Data.fai is required when size of NAND Data(FAT partition) is changed by flashing new lk.rom in previous step. you can use same NAND Data.fai if you are using same lk.rom. don't use NAND Data.fai from other people.
*7 if size of NAND Data is not changed, you can skip flashing NAND Data.fai to keep your files in NAND(FAT) partition.
*8 you can make non-empty NAND Data.fai in this window
* issues
no mic input with stock apps
USB host on Scroll 7" resistive and 8"
USB mass storage mode (mount from PC) under some condition
some USB mouse
suspend/resume on Emdoor's tablet with Eclair ROM (a-rival PADs, EM51, and EM71 multitouch)
* tips
- what is lk_androtab.rom? / how to increase size of /data?
use lk_androtab.rom in FWDN.zip. in lk_androtab.rom, size of partitions are modified to get more /data. in addition to this, lk.rom/lk_androtab.rom for COBY Kyros MID7015/7016/7022 and EM73 capacitives have +512MB for MTD(assigned to /data) and -512MB for NAND.
- how to use internal NAND flash as SD card?
Settings -> CyanogenMod settings -> Application -> Use internal storage -> On -> reboot
if enabled, internal NAND flash is mounted on /mnt/sdcard and SD card is mounted on /mnt/nand.
in clockworkmod, internal NAND flash is mounted on /emmc. it will be used by "install zip from sdcard -> choose zip from internal sdcard".
- I like portrait / my favorite portrait apps are upside down / accelerometer axes are wrong on some apps
make /data/local.prop with following 3 lines, then reboot.
Code:
accelerometer.hwrotation=270
input.hwrotation=270
ro.sf.hwrotation=270
* FAQ
- what is GB ROM?
old TCC8902 tablets were shipped with Eclair ROM, but there is GingerBread ROM for some tablets. bootloader(lk.rom) and kernel in GingerBread ROM are not compatible with bootloader/kernel in Eclair ROM. CM7 for GB ROMs only work with bootloader in GB ROM, so you need to install GB ROM before installing CM7. (you can use CM7 FWDN image as alternative)
- what is 4K/8K?
there is 2(or more) variants for some tablets. they have different NAND, pagesize are 8192 or 4096, and it may need specific kernel for each.
HY means Hynix, and S means Samsung.
- touchscreen doesn't work (EM71/73)
there is many variants for EM71 and EM73. check your tablet carefully and use proper file.
- touchscreen calibration doesn't run on 1st boot
try run manually
Code:
am start -a android.intent.action.MAIN -n org.zeroxlab.util.tscal/.TSCalibration
- I want to do calibration again
delete following files if exist, reboot, run calibration app, then reboot again
Code:
/data/misc/pointercal
/data/misc/idc/*
- I can't push any file under /system/
Code:
adb remount
- install failed on some apps (e.g. Angry Birds)
remove SD card before install
- no HQ video on youtube app/web
yes, certainly
- no HDMI output
yes, certainly
here is clockworkmod recovery for Kyros7015/Gpad701 users who installed GB ROM(lk.rom)
http://androtab.info/files/tcc8902/cwm/KYROS7015-GB/
ALL FILES UNDER KYROS7015-GB DIRECTORY ARE JUST FOR TEST. DO NOT USE THEM FOR DAILY USE UNTILL TEST IS DONE.
I can't test it at all. if it can be booted, please check /proc/mtd at first
Code:
dev: size erasesize name
mtd0: 00a00000 00100000 "boot"
mtd1: 00500000 00100000 "kpanic"
mtd2: 0b400000 00100000 "system"
mtd3: 00400000 00100000 "splash"
mtd4: 02800000 00100000 "cache"
mtd5: 10500000 00100000 "userdata"
mtd6: 00a00000 00100000 "recovery"
mtd7: 00100000 00100000 "misc"
mtd8: 00100000 00100000 "tcc"
then try to make backup.
Just flashed Clockworkmod on my GB 7015A. Will try it tomorrow. Thanks for the work
by the way, is fastboot mode(not FWDN mode) exist on GB ROM for Gpad701/Kyros7015?
if yes, flashing recovery.img is easy on GB ROM, right?
if no, should I make tcc8900_mtd.img with clockworkmod recovery for easy install?
(no need talk about rooting here. it's meaningless for us because we can modify any files in .img directly)
Fast boot is present
Hey Fun,
Yes fast boot is present in the OEM version.
Cheers
jschill31 said:
Yes fast boot is present in the OEM version.
Click to expand...
Click to collapse
thank you. then, you can flash recovery.img with fastboot easily, right?
20110529 for Kyros 7015(non-GB ROM)/EM71/EM51 are uploaded.
I'm thinking better way to make zips/imgs to support many tablets...
You r da man!
Fun,
I am excited to say that your Clockwork recovery has made a nandroid of the new OEM 2.3.1 for the Coby 7015. I can't wait to see how your CM version progresses. Is it ok with you to direct some other users to your thread?
Cheers
jschill31 said:
I am excited to say that your Clockwork recovery has made a nandroid of the new OEM 2.3.1 for the Coby 7015. I can't wait to see how your CM version progresses. Is it ok with you to direct some other users to your thread?
Click to expand...
Click to collapse
here is dev thread, and I don't have that tablet, so if you tried clockworkmod recovery on Kyros 7015 with GB ROM, I want to hear detail what works and what not.
reboot recovery ok? /proc/mtd ok? backup ok? restore ok?
EDIT: oops I read wrongly. "has made a nandroid" == "backup ok", right?
CM7 for it is already uploaded on my site, but I don't know it boot or not. even if everything works as I except, touch screen will not work because there is no calibration yet.
please don't think "I uploaded" is "it boots". please don't consider "it boots" is "it works without problem". test is required but I can't do it on real device.
EDIT:
here is open forum. anyone can join/leave here.
(I'm not owner/admin. I just started this thread)
jschill31 said:
Fun,
I am excited to say that your Clockwork recovery has made a nandroid of the new OEM 2.3.1 for the Coby 7015. I can't wait to see how your CM version progresses. Is it ok with you to direct some other users to your thread?
Cheers
Click to expand...
Click to collapse
me to iam excited. I will wait. Good work
fabricioemmerick said:
me to iam excited. I will wait. Good work
Click to expand...
Click to collapse
I don't have Kyros 7015. someone need to go further away.
fun_ said:
thank you. then, you can flash recovery.img with fastboot easily, right?
Click to expand...
Click to collapse
yep, just did it in fastboot. Really the easiest method to flash recovery. ClockwordMod 3.2.0.0 also made a successfully backup of my GB 7015A tablet. Did it try to restore though but I guess if the mtd is correct for the backup it will be with the restore.
Thanks a lot for that fun
thank you for your cooperation.
here is next test file for Kyros 7015 GB ROM users.
http://androtab.info/files/tcc8902/cm7/20110529/KYROS7015-GB/cyanogen_kyros7015-ota-eng.fun.zip
it's CM7 for Kyros 7015 GB ROM.
there is no support for touch screen calibration (I think no calc_table on GB ROM, but please confirm), so it will be only for test purpose. please try if you have enough free time
I want to know it boots or not. if not boot, what happen e.g. "a n d r o i d" yes/no, boot anim yes/no, adb yes/no, etc... if adb works, I want to see logcat.
--
I noticed EM71 is usable for this work... touchscreen doesn't work on kernel for Kyros 7015, but it can be usable for initial porting work.
anyway, to get Kyros 7015/EM71 in Japan, cost performance isn't good
I installed the rom for GB and installed your CM7 it gets to chinese 1st boot screen
Then my screen goes black and doesn't do anything ADb doesnt recognize it.
hankm24 said:
I installed the rom for GB and installed your CM7 it gets to chinese 1st boot screen
Then my screen goes black and doesn't do anything ADb doesnt recognize it.
Click to expand...
Click to collapse
oops. thanks. probably insmod lines in init.rc is wrong (I forgot some args)
I'll make next test image, but if you can, please remove all insmod lines from init.rc. I think at least adb will work... (but will not boot without mali.ko. just for testing)
--
try this boot.img
http://androtab.info/files/tcc8902/cm7/20110529/KYROS7015-GB/boot.img
20110529 cyanogen.zip is also replaced just now.
Trying
Okay will try your boot.img in a while my tablet is completely dead ATM. When it's charged i'll flash it and report back
hankm24 said:
Okay will try your boot.img in a while my tablet is completely dead ATM. When it's charged i'll flash it and report back
Click to expand...
Click to collapse
Any luck?
And also, how are you guys able to make cm7 now? For a while everyone said there was almost no way, then it randomly showed up =o
fun_ said:
thank you for your cooperation.
here is next test file for Kyros 7015 GB ROM users.
http://androtab.info/files/tcc8902/cm7/20110529/KYROS7015-GB/cyanogen_kyros7015-ota-eng.fun.zip
it's CM7 for Kyros 7015 GB ROM.
there is no support for touch screen calibration (I think no calc_table on GB ROM, but please confirm), so it will be only for test purpose. please try if you have enough free time
I want to know it boots or not. if not boot, what happen e.g. "a n d r o i d" yes/no, boot anim yes/no, adb yes/no, etc... if adb works, I want to see logcat.
--
I noticed EM71 is usable for this work... touchscreen doesn't work on kernel for Kyros 7015, but it can be usable for initial porting work.
anyway, to get Kyros 7015/EM71 in Japan, cost performance isn't good
Click to expand...
Click to collapse
Here's the logcat with the black screen after flashing...
ps: I'm now about to flash the boot.img you created. Will post my feedfack once done
---------------------------------
Overview
---------------------------------
*RZrecovery*:
-=overclock settings=-
-=Arbitrary update.zip selection (with folders) (don't have to rename files to update.zip).=-
-=rom.tgz support (of course)=-
-=Unsigned update.zip support=-
-=ability to wipe system, data, boot, dalvik-cache, battery stats, cache-
-=No automatic backup when installing a rom.tgz=-
-=update.zip from folder support=-
-=Ability to install APK's, IMG's, ZIP's, TAR's, TGZ's from the same menu=-
-=Wipe battery statistics=-
-=Battery charging!=-
-=clockwork nandroid restore=-
-=Ability to root any ROM=-
-=12 predefined colors + random color selection=-
-=Rave mode: random color every time screen is redrawn=-
-=preinstall update.zip menu=-
-=battery status (charging status, temperature and charge level) display=-
-=android_secure nandroid / wipe support=-
-=Hold volume keys to scroll=-
-=Touch screen scrolling on some devices=-
-=Davlik bytecode verification disable/enable=-
---------------------------------
Background
---------------------------------
Last year I made RZRecovery for the original droid. It was a huge success, since then I have been asked to port to other devices. So here, about 1 year later, I have done just that. This will bring all the features of the old RZR plus a few new ones including the epic rom.tgz install format from the days of yore to any device. I have built this recovery specifically to handle all devices without the need for a recompile (except for Tegra2-based devices, they have to be recompiled because of some libc bugs). I have made img files for a few devices to start with:
---------------------------------
CONFIRMED
---------------------------------
HTC Thunderbolt
Samsung Nexus S
Samsung Nexus S 4G
Motorola Droid
HTC Incredible/Incredible S/ Incredible 2
HTC EVO 4G
---------------------------------
EXPERIMENTAL
---------------------------------
HTC MyTouch 4G/Slide
HTC Leo
HTC Dream/Sapphire/Magic
HTC Click/Tattoo
HTC Aria
HTC Wildfire
HTC Legend
HTC Desire/Desire CDMA/Desire S/ Desire HD
HTC Hero/Hero CDMA
Samsung Fascinate (need to find out where recovery is stored for mtd)
LG Optimus S
LG Optimus 1
LG Optimus V
LG Optimus 2X
Huawei Ideos
Huawei u8220/u8150
Motorola Cliq/ Cliq XT
Motorola Backflip
Motorola Atrix
PLEASE: IF ANY OF THSE EXPERIMENTAL BUILDS WORK, PLEASE POST AND LET ME KNOW SO THAT I MAY MOVE THEM TO THE CONFIRMED SECTION
In order to port RZR to anything, I need to know the base kernel address, the boot command line, the page size and the partition layout.
---------------------------------
SCREENSHOTS
---------------------------------
{
"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"
}
View all (in case forums limit the amount of images shown): http://rzdroid.com/ftp/recovery/screenshots/2.1.0/view.html
---------------------------------
CREDITS
---------------------------------
(without any of these individuals/organizations none of this could be possible)
CyanogenMod - for being completely open and having a huge database of device information
koush - for clockworkmod, where I got support for other partition types and filesystems
rbox - for repeat scroll and touch screen scrolling
cvpcs - for helping with anything I have ever asked
slayher - for showing me how to enable capacitive buttons on HTC devices
bekit - for showing me the bionic commits to get recovery built for tegra2's
trevorj - for the original battery charge knowledge
my wife - for giving me all the time I needed to get this done
all the testers for testing and encouragement!
---------------------------------
DOWNLOADS
---------------------------------
I will link img files for use with fastboot or flash_image and any applicable zips.
DISCLAIMER: Not that this needs to be said, but by downloading any of the files below, you take full responsibility for what happens with them. Make sure you have a way out if something goes wrong. The devices above are in the experimental section for a reason
EVO 4G: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-supersonic-update.zip
SAMSUNG FASCINATE: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-fascinate-update.zip
MYTOUCH 4G: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-glacier-update.zip
HTC THUNDERBOLT: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-mecha-update.zip
SAMSUNG NEXUS S: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-nexusS-update.zip
SAMSUNG NEXUS S 4G: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-ns4g-update.zip
HTC INCREDIBLE 2: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-vivow-update.zip
HTC INCREDIBLE S: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-vivo-update.zip
LG OPTIMUS S: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-thunderc-update.zip
LG OPTIMUS 1: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-thunderg-update.zip
LG OPTIMUS 2X: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-p990-update.zip
MOTOROLA DROID: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-sholes-update.zip
HTC LEO: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-leo-update.zip
HTC MAGIC: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-magic-update.zip
HTC DREAM: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream_sapphire-update.zip
HTC MARVEL: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream_sapphire-update.zip
HTC ACE: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-ace-update.zip
HTC DESIRE http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-bravo-update.zip
HTC DESIRE (CDMA): http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-bravoc-update.zip
HTC WILDFIRE: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-buzz-update.zip
HTC CLICK: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-click-update.zip
MyTouch Slide: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-espresso-update.zip
HTC HERO: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-hero-update.zip
HTC HERO (CDMA): http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-heroc-update.zip
HTC LEGEND: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-legend-update.zip
HTC ARIA: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-liberty-update.zip
MOTO CLIQ: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-morrison-update.zip
MOTO BACKFLIP: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-motus-update.zip
MOTO ATRIX: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-olympus-update.zip
HTC SAGA: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-saga-update.zip
HUAWEI U8150: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-u8150-update.zip
HUAWEI U8220: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-u8220-update.zip
HTC VISION: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-vision-update.zip
MOTO CLIQ XT: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-zeppelin-update.zip
HTC ZERO: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-zero-update.zip
---------------------------------
SOURCE
---------------------------------
https://github.com/raidzero/RZrecovery/tree/gingerbread
---------------------------------
WALKTHROUGH
---------------------------------
Volume up/down - scroll (can hold down to repeat scroll)
HTC - touch screen - scroll
Home - select
Back/Power - back
Code:
Main screen
Reboot android
Reboot recovery
Reboot bootloader
Power off
Wipe menu
Wipe all - wipe everything on the device except recovery
Wipe system (the ROM)
Wipe data (your applications and settings)
Wipe .android-secure (other applications and settings on sdcard)
Wipe boot (the main android kernel)
Wipe cache
Wipe battery stats
Wipe dalvik cache (cache of optimized dalvik executables)
Mount menu
Mount/unmount system (the ROM)
Mount/unmount data (apps and settings)
Mount/unmount sdcard
Enable/Disable USB Mass storage
Nandroid menu
Nandroid Backup
Perform backup
choose boot,data,android-secure,system to back up
Nandroid restore
Choose backup
choose boot,data,android-secure,system to restore
Clockwork nandroid restore
choose backup and immediately restore the whole thing
Install from sdcard
choose item to install:
APK, ZIP, IMG, (must end in rec.img or boot.img) .TAR, .TGZ
Preinstall Menu
Abort Install
Backup before install (make a quick backup of the device naming it preinstall-date-time)
Wipe data
Perform install
if(APK)
Abort APK install
Install to system
Install to data
Extras menu
Custom Colors
Random - randomly generated color, will save to sdcard
Any other color - will save to sdcard
Rave mode - a totally random color each time the screen is redrawn (every key press)
Show battery status - will show charge status, level, temperature if available
Recovery overclocking
Kernel will report the available CPU slots, pick one and it will set the max to your selection. Saves to sdcard
ROM tweaks
Disable OTA update downloads in ROM - will prevent android from downloading updates OTA
Activate Root access in ROM
Yes - roots the current ROM (still requires the superuser.apk from chainsdd)
No - does nothing
Dalvik bytecode tweaks
Disable bytecode verification
Enable bytecode verificaion
this deserves some explaining. saved the best for last :) In android, when executables are loaded, the dalvik VM will go
through each line of instructions and make sure it is valid, if it isn't (poorly written application) it will fix it to the best of its ability. This verification process takes time. Disabling this will speed up all the operations on the phone and might even save some RAM. If it doesn't work for you or causes apps to crash, re-enable the verifier here.
So please, if you want this for your device just post here and I will try to get it done for you
POSSIBLE CAVEATS
Update.zip status 2: this means the update.zip you re trying to flash has an outdated update-binary (META-INF/com/google/android/update-binary). Please replace this file in your zip with my version (from gingerbread) here: http://rzdroid.com/ftp/recovery/gingerbread/APIlevel3-update-binary
Update.zip status 7: This means the script is not compatible with the update-binary. This will most likely happen after you replace the update-binary in an outdated update.zip. The most common errors are that the mount and format commands now take extra arguments. you must pass the filesystem type like so:
OLD:
Code:
format("MTD", "system");
mount("MTD", "system", "/system");
NEW:
Code:
format("MTD", "yaffs2", "system");
mount ("MTD", "yaffs2", "system", "/system");
I have changed the API level to 2, to help alleviate some of these issues. It is still evel 3 but all level 2 update.zips should work fine.
Not the addition of the filesystem type. No idea why they changed this, seems like since it now uses recovery.fstab that this info could simply be figured out. or maybe I will implement a method of checking for status 7 and possibly telling it the filesystem information myself. Either way, this info will get you rolling now.
Can you make one for the lg optimus gt540 dont no it this helps
Partitions
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 04000000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00060000 00020000 "splash"
mtd4: 0f500000 00020000 "system"
mtd5: 002c0000 00020000 "lgdrm"
mtd6: 08a80000 00020000 "userdata"
mtd7: 00100000 00020000 "misc"
mtd8: 00080000 00020000 "usd"
mtd9: 005a0000 00020000 "pkg"
mtd10: 1cfc0000 00020000 ""
Cmdline
mem=214M console=ttyMSM2,115200n8 androidboot.hardware=swift uart.mode=arm11_uart_disable crash=off
Sent from my LG GT540 Swift using xda premium
eoghan2t7 said:
Can you make one for the lg optimus gt540 dont no it this helps
Partitions
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 04000000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00060000 00020000 "splash"
mtd4: 0f500000 00020000 "system"
mtd5: 002c0000 00020000 "lgdrm"
mtd6: 08a80000 00020000 "userdata"
mtd7: 00100000 00020000 "misc"
mtd8: 00080000 00020000 "usd"
mtd9: 005a0000 00020000 "pkg"
mtd10: 1cfc0000 00020000 ""
Cmdline
mem=214M console=ttyMSM2,115200n8 androidboot.hardware=swift uart.mode=arm11_uart_disable crash=off
Sent from my LG GT540 Swift using xda premium
Click to expand...
Click to collapse
The only other thing I am missing is the pagesize and base address. Is there a Cyanogenmod for it? thats the quickest way to get all that info
raidzero said:
The only other thing I am missing is the pagesize and base address. Is there a Cyanogenmod for it? thats the quickest way to get all that info
Click to expand...
Click to collapse
There is kernel source would that help? Thanks
Edit: no cm repo but heres the kernel source:
https://github.com/wingrime/android_kernel_swift_lg/
Sent from my LG GT540 Swift using xda premium
About to try this
nobody calls my EVO a fizzle and gets away with it!!
Well mate any luck?
Sent from my LG GT540 Swift using xda premium
with some research I have found the base address for that device to be
0x00200000
I will make an img for it tonight. Do you have google talk? I will need to experiment to find the correct pagesize for the device.
raidzero said:
with some research I have found the base address for that device to be
0x00200000
I will make an img for it tonight. Do you have google talk? I will need to experiment to find the correct pagesize for the device.
Click to expand...
Click to collapse
Yeah i do ill pm you the address
Sent from my LG GT540 Swift using xda premium
For wildfire s??
Would you mind bringing this to the HTC Wildfire S?????
And as for the info you need.......there is an unofficial port of cm7
here
HD2
i like what u have here...if u can i hope i can use it on HD2
THX
Can it be made for Dell streak 5 PLease PLease..................
anyone try this on NS4G yet?
TheBurgh said:
anyone try this on NS4G yet?
Click to expand...
Click to collapse
ns4g is the phone I have. it works great
Would you mind making this available to HTC G1 please?
Thanks in advance.
ahmadns said:
Would you mind bringing this to the HTC Wildfire S?????
And as for the info you need.......there is an unofficial port of cm7
here
Click to expand...
Click to collapse
marvel? http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-marvel-update.zip
BeenAndroidized said:
Would you mind making this available to HTC G1 please?
Thanks in advance.
Click to expand...
Click to collapse
dream & magic:
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream-update.zip
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-magic-update.zip
(they are the exact same thing)
raidzero said:
dream & magic:
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream-update.zip
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-magic-update.zip
(they are the exact same thing)
Click to expand...
Click to collapse
Thank you. I will download it when I have a chance.
EDIT: OK, since there is no instruction on this. I am assuming that I flash it through my current recovery from SD card. Is that right?
BeenAndroidized said:
Thank you. I will download it when I have a chance.
EDIT: OK, since there is no instruction on this. I am assuming that I flash it through my current recovery from SD card. Is that right?
Click to expand...
Click to collapse
that is correct. flash it like any other update.zip please let me know if it boots and how it works!
eoghan2t7 said:
Yeah i do ill pm you the address
Sent from my LG GT540 Swift using xda premium
Click to expand...
Click to collapse
try this: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-swift-update.zip
let me know if it boots and how it runs
seaman2k said:
i like what u have here...if u can i hope i can use it on HD2
THX
Click to expand...
Click to collapse
htc leo, right? http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-leo-update.zip
same story as the rest...
Lenovo IdeaTab A2107A -F -H Tablet [FAQ]
We need a clearing house of concise information for the A2107A to address FAQ
(Much of this information can be useful to other MTK devices)
-----------------------------------------------------------------------------------------------------------
Please reply to this thread with any FAQ items you wish to see here.
-----------------------------------------------------------------------------------------------------------
Q: Why are you doing this? Creating a FAQ?
A: Because my brain hurts and I'm a slow reader. There are a few A2107A threads, but the main one has well over 1800 posts. We need to learn, not just follow recipes. We need to build our understanding with unhindered flow of information.
Q: What are the main threads for A2107A users?
A:
Lenovo IdeaTab a2107
Lenovo IdeaTab A2107A-F roms
Lenovo IdeaTab A2107A-F
A2107A-H Firmware update, Custom Rom and CWM Recovery (calling feature - unlocked)
[ROM] SE for Lenovo A2107A-F and A2107A-H
Q: Should I buy an A2107A?
A: At this point (Sept 2013), new ones are not a good value, but used/refurbs can be a good value. Lenovo themselves have better values: A1000 and A3000. I would like to know and post if these have 3G GSM SIMs? UPDATE: If you really want a 3G SIM tablet, this may be still king. The A1000 has no SIM. The A3000 has an LTE SIM.
Q: Are there custom ROMs? (NEW)
A: Depends on what "custom" means to you. I've stripped some stock ones down: http://forum.xda-developers.com/showthread.php?p=46201425 and makbro collected some... chinese, foxtrot, pemergency: http://forum.xda-developers.com/showpost.php?p=37409096&postcount=800 which I also mirrored here: https://drive.google.com/?authuser=0#folders/0B8PcIZoLeGNuWS1JUnA2UXdPYUE
Q: What is different about MTK devices from my phone (Motorola, Samsung, etc)?
A: MediaTek SoCs are cheap. They seem to be unique in that they allow for some low level fiddling where others don't. The low level fiddling is done with MediaTek software called SP Flash Tool (Smart Phone Flash Tool).
Q: It seems, this little beast is a lot more complicated to mess with, than other devices?
A: MediaTek devices are a pain in some respects... but once you use and understand MediaTek's SP Flash Tool -- you actually bypass a lot of complexity. You are able to write blocks anywhere in flash. And also, read blocks anywhere from flash. So you are in full control.
Q: Can I get an update.zip and put it on my sdcard?
A: Some folks (myself included) have grabbed OTAs, but they are not full flashes, they are just updates. Lenovo has not released official update.zip files for these devices. You may find something, I'd like to know. (You have other paths with CWM Recovery and also SP Flash Tools)
Q: What is the difference between a -H and a -F model?
A: There are 3 distinct hardware profiles: -H with 1 GSM SIM slot, -H with 2 GSM SIM, and -F with no SIM. Check the A2107A wiki here: http://forum.xda-developers.com/wiki/Lenovo_IdeaTab_A2107A
Q: Are there different Official ROMs?
A: Yes, there are at least different -H ROMs for US, Europe, and China. The Chinese ROMs enable a Phone App on the -H. To my knowledge there is just one -F ROM.
Q: What are the current stock ROMs?
A: If you have a US -H and OTA it as of Sept 2013 -- you will get Android 4.0.4 (ATT build A2107A_A404_000_033_121011_ATT)
A: If you have a US -F and OTA it as of Sept 2013 -- you will get Android 4.0.3 (build A2107A-F_S486_130221).
Q: Can I root after an OTA?
A: Yep, root4.03.zip etc should work fine. [Assuming there will never be 4.1 OTAs]
Q: Can I flash -H to a -F?
A: First, ask why do you want to do this? The phone software on a Tablet without phone (SIM) hardware won't get you anywhere. Yes, you can flash -H onto -F, and you will likely not like the results. It is jerky and sluggish and has some errors. For example audio breaks up horribly and swiping between homescreens is jittery. You'll want to go back to a -F ROM, and it's hard.
Q: Does the -F model have FM Radio hardware?
A: Yes! Tapping into it though is not easy. It's not as simple as grabbing the FM_Radio_1.0.apk from the -H ROM and installing it. Apparently the kernel driver on -F is missing, because the app wants to close and can't find any signals. On the SAME -F device, using the -H ROM, I'm able to hear FM Radio.
Q: Who do we owe thanks to?
A: Lots of folks, but makbro, FoxtrotKZ, and pemergency have to be at the top of the list.
Q: Are there custom ROMs for the -H?
A: Yes, check out makbro's post http://forum.xda-developers.com/showpost.php?p=37409096&postcount=800
Q: Are there recovery ROMs for the -H?
A: Yes, check makbro's post above and ClearSky or ANTIKIRPICH are within makbros posted SP_Flash_Tool_FULL_A2107.rar here:
https://docs.google.com/file/d/0By3a11Z9icECSXVLWUl4djc3WTg/edit?pli=1
(this is a very good rar/zip/tarball to grab, almost all you need... props go to FoxtrotKZ)
Q: Are there custom ROMs for the -F?
A: ShilohDaniel has stripped the stock ROM and I believe added some things -- calling it "A2107A-F Bare Bones ROM." thread: http://forum.xda-developers.com/showthread.php?t=2213225
Q: Are there recovery ROMs for the -F?
A: Not really. Once I broke my -F I pushed ClearSky (-H) on it. It was semi-operational, but then getting the right partitioning back to -F was horrible. In this respect, getting CWM on and going with Bare Bones ROM wouldn't get you fixed. I hope to change that.
Q: Will Lenovo release more OTAs? JB?
A: No, they already have a new line-up. They are "done" with these devices. The only thing that would change that is if a partner like AT&T needs a security fix.
Q: Is there a JellyBean ROM for either the A2107A-F or the A2107A-H?
A: No, are you volunteering?
Q: Does Lenovo respond to questions on their forums?
A: Probably not the questions that you would ask. Their answers are more "Well have you tried turning it off and then on again?" When I asked if there were model variants they had no idea. They didn't know if different features were enabled (with different ROMs) in different countries. Their online support chat was able to find a few product PDFs that show several long model numbers. (those PDFs are on the wiki)
Q: Can I use all these untrusted tools inside a VMware virtual machine instead of my daily rig?
A: Yes. I encourage it. Also, if you are using VMware snapshots or VirtualBox snapshots you can roll back and try different drivers. It seems trying to replace ADB USB drivers that don't work with MTDRT is very hard. Rolling back is much easier than trying to expunge the already installed driver so you can try another.
Q: What is MTK Droid Tools?
A: A Windows app that will convert a "firmware.info" to a scatter.txt file.
A: This tool is also able to root some devices and do a backup. I imagine if it gets that far it can restore too.
Q: What is MTK Rom Studio?
A: A Windows app that will convert a "firmware.info" to a scatter.txt file too I think. (I haven't used it)
Q: Why would I want a *_scatter.txt file?
A: It contains the partition information for your device. This is something you need to feed SP Flash Tool so it can flash the bits in the right places. You can make one from a working device by dumping a "firmware.info" file with a tool like the gscript backup method or presumably MTK Droid Tools will build you one right off, I'm sure doing the same thing to get the data which is dumped to firmware.info.
Q: Can I brick my -F or -H?
A: Probably not. There is a Meta Mode that you can get into even if your PRELOADER is broken/overwritten. I verified this today by writing zeroes to the first 16K of flash, broke my -F, then wrote over a known good firmware. makbro believes it's unbrickable and also yuweng has good info: http://forum.xda-developers.com/showpost.php?p=34914486&postcount=3
Q: How do I get into Meta Mode?
A1: While plugged into PC... Hold down Reset, hold VolUp, release Reset, release VolUp
A2: While off... hold VolUp, plug into PC, release VolUp
A3: While off... hold Reset, plug into PC, hold VolUp, release Reset, release VolUp
Q: Can someone help me unbrick my tablet?
A: I haven't seen a bricked A2107A-* that I could not fix. Please post to the original Lenovo IdeaTab a2107 thread.
Q: How do I use SP Flash Tool?
A: I'd like to write a FAQ on it too since there are many pitfalls, but I fear I don't have enough time to do everything. For now, here is a tutorial: http://forum.xda-developers.com/showthread.php?t=1982587
Q: What should I know about SP Flash Tool?
A: SP Flash Tool allows you to read or write any chunk of nvram/flash. It's normal operation though is to load a *scatter.txt file which describes different image chunks and allows you to "download" (write) them to MTK devices. You can think of the NVRAM as a disk (block device) and this scatter file describing the sizes of PARTITIONS. I think in one error I ran across even says your PMT (partition table?) doesn't match. So the download will write blocks of your NVRAM from image files on your WIndows computer.
Q: When I try to Download (write) a scatter and set of image files to my tablet with SP Flash Tool, I get a PMT does not match. What is causing this?
A: Well, for some reason you have to "Format". Not only do the Format, but you must select "Whole Flash". (assuming this next part) Then it write the PMT to your tablet to match the scatter file you have loaded. At this point you can Download (write) successfully. You will want to have a good backup of your NVRAM block or /data/nvram directory first!
Q: What is a PMT?
A: A partition table that holds the addresses to all the other partitions. I believe the PMT block is created by SP Flash Tool dynamically from scatter file. It's comparing the scatter file with what is sitting at the PMT address on the flash. If these two mismatch, you get the error you mentioned. If you want to force a new PMT that matches your scatter file's layout, you have to do a "Format" in SP Flash Tool. This will get you back to a PMT on flash that matches your scatter file, then SP Flash Tool will be happy and allow you to use Download (write to flash). SPFT is very picky about the scatter file matching the PMT on flash, even the __NODL_ in the scatter has to match the PMT.
Q: How do I get into Factory Mode?
A: Turn Off completely. (no power from USB, you might even hit the reset button)
A: Press and hold Power On and VolUp for 12 sec
A: Observe a menu similar to recovery but with tests etc
Q: How do I get into Recovery Mode?
A: Turn Off completely. (no power from USB, you might even hit the reset button)
A: Press and hold Power On for 4 sec, release, then hold VolUp and VolDown at the same time for up to 10 sec
A: Observe the stock Recovery or CWM if you've replaced the stock
Q: Why is SP Flash Tool giving me errors?
A: SP Flash Tool is not quality software, IMHO. I've had it give me BROM ERROR:S_DL_GET_DRAM_SETTING_FAIL(5054))... over and over, then I exited out and got back into the program and flashing worked fine. Also, make sure you have PRELOADER etc files associated with the blocks even though you don't have them selected to Download/write to flash. For some reason, SPFT checks these things even if they are irrelevant.
Q: I don't have a scatter file, or I have an incorrect scatter file... how do I create one if my device won't boot?
A: Interestingly enough, SPFT reads the PMT during a Download/write. It puts all the values of the PMT in it's log file. You can go look at the log file and fix your scatter file. This is cheating... knowing exactly what your scatter file needs to look like to match your device.
Q: I renamed the scatter file from MT6575_Android_scatter_emmc.txt to my_failed_attempt_scatter.txt is that ok?
A: Obviously you didn't know to ask this question and it's just contrived.... but yes you just screwed up, the file name of the scatter matters. I hate this, I lost like 2 weeks to this. Don't rename it. I've found some names that work, but just don't go there, leave the name and organize things with directories instead of file names.
(Some dumb Questions I had early on... that didn't seem to be answered clearly)
Q: How do a SBF or ODIN a A2107A
A: MediaTek's method is through software called SP Flash Tool. This is similar in function to Motorola SBF or Samsung ODIN.
Q: How do I get into Fastboot?
A: I don't think you do on MTK devices.
Q: How do I boot into the Bootloader?
A: Not sure if they have a bootloader menu. I think this is irrelevant. After an OTA, I was never able to. But with all the methods of gaining root and flashing, I guess I don't see why you need it.
Q: Does this device have a locked bootloader? Can I unlock it?
A: I'm not sure. If it does, you could probably overwrite the bootloader easy enough. Can the stock bootloader boot a homebrewed kernel? So far, I have seen no one produce a homebrew kernel for either the -F or -H. Hacks come from the stock kernels or the Lenovo A750 phone.
Q: Can the A2107A run Cyanogenmod (CM9, CM10)?
A: No. Cyanogenmod may run on MTK (MediaTek) chips soon, but even after that it will be a bunch of work.
Q: Why do I want to root my device?
Q: How do I root my device?
Q: Why do I want to install a custom recovery like CMW (Clockwork Mod) Recovery?
Q: How do I install CWM?
<-- Click Thanks If you found the information here useful, please!
Backup / root / recovery
Lenovo IdeaTab A2107A -F -H Tablet FAQ
CONTINUED DETAILS!
(but applicable for MT65xx devices)
Backup -- Post 3
Root -- Post 4
Recovery -- Post 5
Topic #1 - Backup
Before you start rooting, I highly recommend getting a full dump of your ROM. And why not? MediaTek makes it easy! At the very least, get a dump of the NVRAM partition. And if you really want to be risky, you'll just get a copy of /data/nvram.
Why Backup?
* First, so you can get back to a factory state.
* This is really good if you return your device or have it serviced.
* It's also good if you are going to sell it.
* Last, if you break it (semi-brick it) you can go back to this known working state.
Methods:
* SP Flash Tool - covered here
* rua1's MKDRT MediaTek Droid Root Tool - covered elsewhere
* Mobile Uncle backup of MEI - may cover here soon
SP Flash Tool BACKUP
If you are big on making images of hard drives, your going to like this tool. But, SP Flash Tool has some bugs and is designed a bit weird.
There are 4 main features to be concerned about: "Format", "Download" (write partition blocks), "Read back" memory, "Write memory".
To backup, you really want to be using the Read memory tab of the interface. But first, you need to make the tool happy.
replaces http://forum.xda-developers.com/showthread.php?p=46595925
Perfect Total Backup of your Firmware
Here is a cookbook for doing a total backup of your MTK device with MediaTek's SP Flash Tool. No rooting, you might even do this before you ever boot! I have basically done this with both of my devices before I fiddled too much. I recommend doing it before you do anything really.
1. Install VCOM Drivers. I'd use this: https://docs.google.com/file/d/0B8PcIZoLeGNuUTFIT1J2eXNFd28
2. Install SP Flash Tool. I'd use this: https://docs.google.com/file/d/0B8PcIZoLeGNuVDluTXk4QXdQaUU
3. Grab a -H scatter file with accompanying block images, just to make SP Flash happy. I'd use this: https://docs.google.com/file/d/0B8PcIZoLeGNuM3lxakdIU2hvWTA
4. Run SP Flash Tool, Open Scatter File
5. Don't play with anything, go into the "Read back" tab (This will read your flash to a file on your PC)
6. Click on any items in the list, then click the "Remove" button
7. Now click the "Add" button
8. Double click on the "N/A" under Read Flag
9. Type a file name to write to, like "WHOLE_ROM"
10. Now it will popup a window "Readback block start address"
11. Leave "Hex" selected, Start Address" 0x0000, Length: 0x323E4000, Click OK
12. Click the "Read back" button
13. SPFT now waits for you to connect your device and put it in Meta Mode
14. Without plugging your tablet in, tap the Reset Button on the back under the camera
15. Hold VolUp, plug in USB, Release VolUp (putting it in Meta Mode) <--- Important
16. You will see the progress bar moving. Total backup takes forever, because in this mode SPFT seems to not do USB HIGHSPEED
That's IT! Go to bed, check on it in the morning.
If you ever restore, just go into Recovery and Wipe Data and Cache. (as these are large and we didn't back them up above)
Note: "Length" in Step 11 is extra long. If you have a 4 or 8GB model it actually backs up part of your cache partition block too. But this is the right length for the 16GB model and it doesn't hurt to backup too much.
(If anyone would like to share there's with me, that would be great. I only want stock dumps though, for comparison purposes.)
Topic #2 - Root
Note: MediaTek is very different as you have low level access to their Flash. Ask
yourself if you really need root. MediaTek's tool SP Flash Tool is very powerful. You can dump your stock rom, replace your recovery image, or blow on another SPFT ROM. So, unless you want your STOCK ROM ROOTED, you can probably skip rooting your stock ROM in the first place.
Why Root?
You have very little ability to do backups or change your device without rooting it. You can use vendor tools to do backup/restore of your user data, whatever they determine is your user data. You can use Android "Factory Reset" which just wipes the data and cache partitions. If you want to do more, you need to root.
More access like:
* Complete backups of ROM (although a bit sketchy to backup a running system)
* Install busybox
* Install apps requiring root, Root Explorer and WiFi sharing
* Install drivers, like OpenVPN, alternative wireless drivers, OTG, FM Radio?
* Install sshd server etc
* Do custom theming?
* Performance tweaks
* Remove APKs from /system/apps (scary)
Different Methods - I think all rely on the same mechanism
1. 4.03root.zip (requires working ADB and Windows)
2. setools/seroot (syserr's port of 4.03root.zip to linux shell, instead of .bat)
3. SRS Root (requires working ADB and Windows)
4. rua1's MKDRT MediaTek Droid Root Tool (requires working ADB and Windows)
Topic #3 - CWM (Clock Work Mod) Recovery
Why?
CWM Recovery is awesome. It allows you to install custom ROMs as long as they are "CWM" compatible. CWM Recovery is a lot like a typical stock Recovery but better. For new people, a Recovery is basically a minimal Android system that allows you to do maintenance on the device and reload etc the main operating system. On MTK devices the Recovery image sits on the RECOVERY partition. You usually press certain buttons early in the boot process to "boot into Recovery."
Different Methods
* SP Flash Tool
* MobileUncle (requires root)
* rua1's MKDRT MediaTek Droid Root Tool (requires root)
* dd / flash_image (requires root)
SP Flash Tool Method
Disconnect Tablet from PC
Run SP Flash Tool (exe)
Select Scatter File
Uncheck all block partition checkboxes except for Recovery.
Click on the Recovery text/tag and then find the CWM Recovery image you desire.
Select Download, SPFT waits for device
Hit reset on Tablet
Press VolUp, connect USB, Release VolUp (to get to Meta Mode)
SPFT ALWAYS finds device this way.
You should see progress bars moving, and it complete
lenovo s6000-h
hi syserr,
your reading was really interesting and help me a lot to better understand the device i just bought.
i think it's quit similar. I m looking/searching information as much as i can at the moment.
thks
fragargon said:
hi syserr,
your reading was really interesting and help me a lot to better understand the device i just bought.
i think it's quit similar. I m looking/searching information as much as i can at the moment.
thks
Click to expand...
Click to collapse
I get paid with "Thanks." So, thanks! :good:
I've often wondered if forums are the right structure to capture this information. When I finally decided to dive in deep, I had to make notes of which posts had good information - it took 3 days of solid reading to make sense of it all. There are plenty of posts that have incorrect information or irrelevant information.
Good luck.
I need some help!
Thank you for helping
But I can not I download:
S6000-H (16GB model, WiFi and 3G)
S6000_A422_000_015_130503_WW_SMS.rar - 495.90 MB
I have problems installing the program and set the theme on the device
I'm not familiar with these settings. Explain the preliminary
My device: S6000-H_A422_101_022_131101_WW_SMS
Put a new link for download. Please
Who can help????
Scatter file
syserr said:
Topic #1 - Backup
Before you start rooting, I highly recommend getting a full dump of your ROM. And why not? MediaTek makes it easy! At the very least, get a dump of the NVRAM partition. And if you really want to be risky, you'll just get a copy of /data/nvram.
Why Backup?
* First, so you can get back to a factory state.
* This is really good if you return your device or have it serviced.
* It's also good if you are going to sell it.
* Last, if you break it (semi-brick it) you can go back to this known working state.
Methods:
* SP Flash Tool - covered here
* rua1's MKDRT MediaTek Droid Root Tool - covered elsewhere
* Mobile Uncle backup of MEI - may cover here soon
SP Flash Tool BACKUP
If you are big on making images of hard drives, your going to like this tool. But, SP Flash Tool has some bugs and is designed a bit weird.
There are 4 main features to be concerned about: "Format", "Download" (write partition blocks), "Read back" memory, "Write memory".
To backup, you really want to be using the Read memory tab of the interface. But first, you need to make the tool happy.
replaces http://forum.xda-developers.com/showthread.php?p=46595925
Perfect Total Backup of your Firmware
Here is a cookbook for doing a total backup of your MTK device with MediaTek's SP Flash Tool. No rooting, you might even do this before you ever boot! I have basically done this with both of my devices before I fiddled too much. I recommend doing it before you do anything really.
1. Install VCOM Drivers. I'd use this: https://docs.google.com/file/d/0B8PcIZoLeGNuUTFIT1J2eXNFd28
2. Install SP Flash Tool. I'd use this: https://docs.google.com/file/d/0B8PcIZoLeGNuVDluTXk4QXdQaUU
3. Grab a -H scatter file with accompanying block images, just to make SP Flash happy. I'd use this: https://docs.google.com/file/d/0B8PcIZoLeGNuM3lxakdIU2hvWTA
4. Run SP Flash Tool, Open Scatter File
5. Don't play with anything, go into the "Read back" tab (This will read your flash to a file on your PC)
6. Click on any items in the list, then click the "Remove" button
7. Now click the "Add" button
8. Double click on the "N/A" under Read Flag
9. Type a file name to write to, like "WHOLE_ROM"
10. Now it will popup a window "Readback block start address"
11. Leave "Hex" selected, Start Address" 0x0000, Length: 0x323E4000, Click OK
12. Click the "Read back" button
13. SPFT now waits for you to connect your device and put it in Meta Mode
14. Without plugging your tablet in, tap the Reset Button on the back under the camera
15. Hold VolUp, plug in USB, Release VolUp (putting it in Meta Mode) <--- Important
16. You will see the progress bar moving. Total backup takes forever, because in this mode SPFT seems to not do USB HIGHSPEED
That's IT! Go to bed, check on it in the morning.
If you ever restore, just go into Recovery and Wipe Data and Cache. (as these are large and we didn't back them up above)
Note: "Length" in Step 11 is extra long. If you have a 4 or 8GB model it actually backs up part of your cache partition block too. But this is the right length for the 16GB model and it doesn't hurt to backup too much.
(If anyone would like to share there's with me, that would be great. I only want stock dumps though, for comparison purposes.)
Click to expand...
Click to collapse
I do not understand. How Lenght you have used : 0x323E4000
11. Leave "Hex" selected, Start Address" 0x0000, Length: 0x323E4000, Click OK
The scatter file, there is no partition at this address
Yours scatter file :
EBR2 0x23e0000
{
}
ANDROID 0x23e4000
{
}
CACHE 0x224e4000
{
}
USRDATA 0x425e4000
{
}
FAT 0x626e4000
{
}
__NODL_BMTPOOL 0xffffffffffff0050
{
}
I used to read back:
0x3c3c00000 + from firmware.info
0x00600000 = preloader
0x3c9c00000 – CACHE scatter file with MTKDroid
I used to read back:
0x3c3c00000 + from firmware.info
0x00600000 = preloader
0x3c9c00000 – CACHE scatter file with MTKDroid
Click to expand...
Click to collapse
when doing this with a hex calculator i got : 3C4200000 - check this wit a hex calculator
Explain how it is with hex
fragargon said:
when doing this with a hex calculator i got : 3C4200000 - check this wit a hex calculator
Click to expand...
Click to collapse
OK , OK I understand.
But the address you left partition to get 3C4200000 - cache or else.explain how
This is scater file: posted by you:
MT6575_Android_scatter_emmc
PRELOADER 0x0
{
}
DSP_BL 0x40000
{
}
MBR 0x600000
{
}
EBR1 0x604000
{
}
__NODL_PMT 0x660000
{
}
__NODL_NVRAM 0xa60000
{
}
__NODL_SECCFG 0xd60000
{
}
UBOOT 0xd80000
{
}
BOOTIMG 0xde0000
{
}
RECOVERY 0x13e0000
{
}
SEC_RO 0x19e0000
{
}
__NODL_MISC 0x1fe0000
{
}
LOGO 0x2040000
{
}
__NODL_EXPDB 0x2340000
{
}
EBR2 0x23e0000
{
}
ANDROID 0x23e4000
{
}
CACHE 0x224e4000
{
}
USRDATA 0x425e4000
{
}
FAT 0x626e4000
{
}
__NODL_BMTPOOL 0xffffffffffff0050
{
}
Alex1948 said:
OK , OK I understand.
But the address you left partition to get 3C4200000 - cache or else.explain how
Click to expand...
Click to collapse
this value 0x3C4200000 is the sum of=> 0x3C4200000 = 0x3c3c00000 (from firmware.info) + 0x00600000 (preloader)
Code:
partname size start adress map to
android 0x0000000040000000 0x0000000010980000 2 /dev/block/mmcblk0p6
cache 0x0000000007e00000 0x0000000050980000 2 /dev/block/mmcblk0p7
usrdata 0x0000000349fa0000 0x0000000058780000 2 /dev/block/mmcblk0p8
whilst this is not really friendly I'll try answer.
when hex number i advice you to use an hex calculator because this is 16 base not 10base that's why you would be better using a hex calculator.
this all about readback the memory for backup purpose so according to my file:
I do not understand. How Lenght you have used
Click to expand...
Click to collapse
take my file as example and i would bump the partition cache, i would do:
readback: start adress:0x0000000050980000
: size : 0x0000000007e00000 = 126 Mb
: lenght: 0x0000000050980000+0x0000000007e00000 = 0x0000000058780000 (end adress)
this should result by a file.img of 126Mb with by spft on readback memory starting adress at 0x0000000050980000 and ending at 0x0000000058780000.
you can see that this overlapted the next partition 0x0000000058780000 (userdata) so i bet that spft does this to not overlapted start adress of next partition:
0x0000000050980000+0x0000000007e00000-0x00000000000001=0x000000005877ffff
i hope this explanation is readable and will answer your question.
What Scatter file ?
fragargon said:
this value 0x3C4200000 is the sum of=> 0x3C4200000 = 0x3c3c00000 (from firmware.info) + 0x00600000 0x3c3c00000 (from firmware.info) + 0x00600000 (preloader)
Code:
partname size start adress map to
android 0x0000000040000000 0x0000000010980000 2 /dev/block/mmcblk0p6
cache 0x0000000007e00000 0x0000000050980000 2 /dev/block/mmcblk0p7
usrdata 0x0000000349fa0000 0x0000000058780000 2 /dev/block/mmcblk0p8
whilst this is not really friendly I'll try answer.
when hex number i advice you to use an hex calculator because this is 16 base not 10base that's why you would be better using a hex calculator.
this all about readback the memory for backup purpose so according to my file:
take my file as example and i would bump the partition cache, i would do:
readback: start adress:0x0000000050980000
: size : 0x0000000007e00000 = 126 Mb
: lenght: 0x0000000050980000+0x0000000007e00000 = 0x0000000058780000 (end adress)
this should result by a file.img of 126Mb with by spft on readback memory starting adress at 0x0000000050980000 and ending at 0x0000000058780000.
you can see that this overlapted the next partition 0x0000000058780000 (userdata) so i bet that spft does this to not overlapted start adress of next partition:
0x0000000050980000+0x0000000007e00000-0x00000000000001=0x000000005877ffff
i hope this explanation is readable and will answer your question.
Click to expand...
Click to collapse
My bewilderment came from that and MTKDroid do the same, add preloader - in my case CACHE : 0x3c3c00000 (from firmware.info) + 0x00600000(preloader) = 0x3C9C0000(that we used from READ BACK with SPFT).
I understand that the scatter file created with MTKDroid Tool is not good ???
Alex1948 said:
My bewilderment came from that and MTKDroid do the same, add preloader - in my case CACHE : 0x3c3c00000 (from firmware.info) + 0x00600000(preloader) = 0x3C9C0000(that we used from READ BACK with SPFT).
I understand that the scatter file created with MTKDroid Tool is not good ???
Click to expand...
Click to collapse
lol :silly:
sometimes you should read back what you wrote, i really don't understand what you mean but i am sure you are not reading what i have wrote because this
================+++>
============++>
=========+>
in my case CACHE : 0x3c3c00000 (from firmware.info) + 0x00600000(preloader) = 0x3C9C0000(that we used from READ BACK with SPFT).
Click to expand...
Click to collapse
i wish you a good night! :cyclops:
????
fragargon said:
lol :silly:
sometimes you should read back what you wrote, i really don't understand what you mean but i am sure you are not reading what i have wrote because this
================+++>
============++>
=========+>
i wish you a good night! :cyclops:
Click to expand...
Click to collapse
Please forgive me greatly.
I asked a simple question : if scatter file made with MTKDroid TOOL is good or no , work or no.
So , good night !
fragargon said:
i hope this explanation is readable and will answer your question.
Click to expand...
Click to collapse
Thanks for trying to explain, it's appreciated!
Alex1948 said:
Please forgive me greatly.
I asked a simple question : if scatter file made with MTKDroid TOOL is good or no , work or no.
So , good night !
Click to expand...
Click to collapse
I believe "MTK Droid Root & Tools" does give you a good scatter file, but I've actually never used it.
Background: During the time I used it, I had major problems with ADB drivers on Windows. I ended up soft-bricking my device by playing with the "Test" tab in SP Flash Tools. So when I came back to working on things again, with a new device to donate the ROM, I wanted to be absolutely sure I knew what I was doing. First thing was "Read back" the ENTIRE ROM of the new device. This is an insurance policy. I had made backups with the GScript mtk*backup.sh scripts that run ON the unit, so I never went back to MTK DRT.Something I think everyone that wants to do HEX math should to is start playing with the python interpreter... it is AWESOME. :good:
Code:
$ more MT6575_Android_scatter_emmc.txt
....
ANDROID 0x123e4000
{
}
CACHE 0x324e4000
{
}
USRDATA 0x525e4000
{
}
FAT 0x726e4000
{
}
__NODL_BMTPOOL 0xffffffffffff0050
{
}
$ python
Python 2.7.3 (default, Sep 26 2013, 16:35:25)
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> hex(0x324e4000-0x123e4000)
'0x20100000'
Alex1948, if you are wondering why the length of my full/entire/whole dumps seems arbitrary... my answer is in some cases I was guessing at large enough numbers. My device (A2107A-*) has at least 5 different partitioning schemes from the factory. I want extra length, I didn't want to tell someone to read too short.
Why I am reading to the start address of CACHE is because that is the end of ANDROID. This is just looking at the physical real addresses in the scatter file. How those addresses are calculated from firmware.info/dumchar_info is a different story. I think you are aware of adding the 0x600000. This is only added to the lines in the file that are not preloader or dsp_bl:
Code:
$ more dumchar.txt
preloader 0x0000000000040000 0x0000000000000000 2 /dev/[B]misc[/B]-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/[B]block[/B]/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
fac 0x0000000010000000 0x0000000001de4000 2 /dev/block/mmcblk0p6
android 0x0000000020100000 0x0000000011de4000 2 /dev/block/mmcblk0p7
cache 0x0000000020100000 0x0000000031ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000020100000 0x0000000051fe4000 2 /dev/block/mmcblk0p3
fat 0x00000000762fc000 0x00000000720e4000 2 /dev/block/mmcblk0p4
bmtpool 0x0000000000a00000 0xffffffffff9f0050 2 /dev/block/mmcblk0
So my code here:
Code:
if block != 'misc':
start = start + 0x600000
Is only adding the offset to the partitions that don't have that "misc" in their block device name.
I'm explaining a lot. I'm hoping somewhere in this you have the answer you are looking for.
We should have discussed this here:
[GUIDE][UTIL][MT65xx] Create Scatter File and Dump Full ROM
http://forum.xda-developers.com/showthread.php?p=47809842
Tks
syserr said:
Thanks for trying to explain, it's appreciated!
I believe "MTK Droid Root & Tools" does give you a good scatter file, but I've actually never used it.
Background: During the time I used it, I had major problems with ADB drivers on Windows. I ended up soft-bricking my device by playing with the "Test" tab in SP Flash Tools. So when I came back to working on things again, with a new device to donate the ROM, I wanted to be absolutely sure I knew what I was doing. First thing was "Read back" the ENTIRE ROM of the new device. This is an insurance policy. I had made backups with the GScript mtk*backup.sh scripts that run ON the unit, so I never went back to MTK DRT.Something I think everyone that wants to do HEX math should to is start playing with the python interpreter... it is AWESOME. :good:
Code:
$ more MT6575_Android_scatter_emmc.txt
....
ANDROID 0x123e4000
{
}
CACHE 0x324e4000
{
}
USRDATA 0x525e4000
{
}
FAT 0x726e4000
{
}
__NODL_BMTPOOL 0xffffffffffff0050
{
}
$ python
Python 2.7.3 (default, Sep 26 2013, 16:35:25)
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> hex(0x324e4000-0x123e4000)
'0x201000000'
Alex1948, if you are wondering why the length of my full/entire/whole dumps seems arbitrary... my answer is in some cases I was guessing at large enough numbers. My device (A2107A-*) has at least 5 different partitioning schemes from the factory. I want extra length, I didn't want to tell someone to read too short.
Why I am reading to the start address of CACHE is because that is the end of ANDROID. This is just looking at the physical real addresses in the scatter file. How those addresses are calculated from firmware.info/dumchar_info is a different story. I think you are aware of adding the 0x600000. This is only added to the lines in the file that are not preloader or dsp_bl:
Code:
$ more dumchar.txt
preloader 0x0000000000040000 0x0000000000000000 2 /dev/[B]misc[/B]-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/[B]block[/B]/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
fac 0x0000000010000000 0x0000000001de4000 2 /dev/block/mmcblk0p6
android 0x0000000020100000 0x0000000011de4000 2 /dev/block/mmcblk0p7
cache 0x0000000020100000 0x0000000031ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000020100000 0x0000000051fe4000 2 /dev/block/mmcblk0p3
fat 0x00000000762fc000 0x00000000720e4000 2 /dev/block/mmcblk0p4
bmtpool 0x0000000000a00000 0xffffffffff9f0050 2 /dev/block/mmcblk0
So my code here:
Code:
if block != 'misc':
start = start + 0x600000
Is only adding the offset to the partitions that don't have that "misc" in their block device name.
I'm explaining a lot. I'm hoping somewhere in this you have the answer you are looking for.
We should have discussed this here:
[GUIDE][UTIL][MT65xx] Create Scatter File and Dump Full ROM
http://forum.xda-developers.com/showthread.php?p=47809842
Click to expand...
Click to collapse
Thank you very much.I understand something.and conversely :ANDROID 0x123e4000+0x20100000(lenght) = CACHE 0x324e4000
I wrote on the other thread
A3000 hardware
Just a note, in Europe and likely in Asian the A3000 SIM version is dual SIM, organised much the same as the A2107A. One SIM is expected to be used for data (HSDP+, this is the European high speed 3G, up to 42mbs, I get 18mbs off my local tower) and one for SMS and Voice. You can run SMS on the Data SIM if you are provisioned, I do. The European firmware does not support GSM voice (again) but Asian and Middle Eastern does. Why Lenovo does not include voice support in the European firmware is a mystery.
Many thanks for the A2107A FAQ, I'm selling one now, replaced by a A3000.
Not create worry... but I have a very cheap ($75 sale) Lenovo A1000 coming. This has JB, FM Radio, and dual-core. This is going to work out better for a in-dash car system.
Partitioning 16 GB A2107A-H
Does anyone please have an EBR1 and EBR2 (or other means) by which I can repartition my internal SD flash so that the system and other partitions are larger?
I have read about an apk to do this for the 4 GB model, and also the limitation to one of the partitions (32-bit addressing?) to 2 GB, but have not found anything available for the 16 GB model.
Could anyone please advise and/or upload the necessary files?
Also, does anyone have a view on the "best" ROM? It seems all have compromises in some way, including the stock ROM. Pemergency looks good unless someone tells me otherwise.
Hi guys,
I'm here to explain my new fresh app that I tested on my HTC Desire 310 and it's faboulous. His name is...
MTKTransfROM
*What does it do?
- This app will let you do all the process of porting an MTK ROM to your MTK phone without a PC! You can choose a lot of options and method, like signing ZIP, Fix BootLoop/Stuck at Boot Logo and even READ BOOT.IMG DIRECTLY FROM YOUR PHONE and AUTOMATICALLY ADAPT THE ROM FOR YOUR PARTITION (/dev/block/mmcblk0p*)
*What do I have to do?
-All you have to do is select the ZIP ROM, choose chipset and options and then click "Port ROM for your device!". The default chipsets installed are taken on online forums, like XDA and 4pda.ru (thanks a lot for those guides), but you can build your own chipset method with a simple text editor!
*How can I build my chipset method?
-The chipset structure is like: e.g.
Code:
[B]system/bin/vold [/B] (Copy this file from your device)
[B]system/etc[I]/[/I][/B] (Copy entire directory, replacing existing files)
[B][I]-[/I]system/etc/ [/B] (First delete ROM folder and then copy entire folder)
[B]system/lib/libaudio[I]*[/I][/B] (Copy all files that starts with libaudio...)
Then save it as "{THE NAME YOU WANT}.txt" in your SDCard under "MTKTransfROM" named folder (e.g. /storage/sdcard0/MTKTransfROM/mt6589.txt)
*Bugs?
Existing bugs TODO:
-During porting, the UI lags. Don't worry, the app is working. If appears Not Responding error, just wait.
-For now, it's only in English.
*Changelog
**1.2
- Discarded zip4j for problems during extraction, using java.util.zip now
- Fixed Exception on some ROM structures
- Added Exit menu voice if activity doesn't terminate
**1.0
- Initial Release
*Credit
-Kellinwood for his ZipSigner class. Thanks a lot.
Now I need help from you community...
As you can see from Play Store screenshots, it has the "Port boot.img" function. However I'm searching a method to unpack and repack MTK boot.img directly from phone. If someone can help me, I will be the most happy man in the world!
As for now, it's the only thing I need to let this app became perfect!
Google Play Store URL: Click here to be redirected (If it says 1.0, is because it's updating or uploading, I'm writing this post while this app is updating).
P.S. Sorry for my English, I'm Italian.
Can you add support for MT6752 devices?
You can add it yourself putting your custom files in the folder I explained in the tutorial
RacerOttavio97 said:
You can add it yourself putting your custom files in the folder I explained in the tutorial
Click to expand...
Click to collapse
Thanks, I will try it and see if it works :fingers-crossed:
I was thinking of doing something similar with MT6732/52 devices...
[I'd be doing it from recovery as I have almost zero app making abilities]
Have a look at the MTKsplit file in the MTK folder in my sig. for the boot.img (un)pack - it works fine with the 64bit SoC's boot/recovery images - so not sure about the older ones.
HypoTurtle said:
I was thinking of doing something similar with MT6732/52 devices...
[I'd be doing it from recovery as I have almost zero app making abilities]
Have a look at the MTKsplit file in the MTK folder in my sig. for the boot.img (un)pack - it works fine with the 64bit SoC's boot/recovery images - so not sure about the older ones.
Click to expand...
Click to collapse
Thank you HypoTurtle, but I'm searching a tool that run on android phone itself, like a sh script or a linux binary.
RacerOttavio97 said:
Thank you HypoTurtle, but I'm searching a tool that run on android phone itself, like a sh script or a linux binary.
Click to expand...
Click to collapse
MTKsplit can/does run on android itself - thats why I wrote it. It's a sh - primarily using dd to split the boot/recovery. I removed the #! at the top so the same script can be run fron recovery and system (making it default to the shell that calls it - /sbin/sh in recovery and /system/bin/sh in system).
Just tested the MTKsplit against a 6592 recovery.img and it works fine:
Code:
[email protected]_phone:/tmp # ls -la
ls -la
-rwx------ root root 5867520 2015-10-05 16:22 recovery-6592.img
[email protected]_phone:/tmp # MTKsplit recovery-6592 unpack
MTKsplit recovery-6592 unpack
Unpacking recovery-6592 - will only take 30 seconds
All Done...
Command line: f30"
Ramdisk unpacked to /tmp/work
[email protected]_phone:/tmp # ls -la
ls -la
-rw------- root root 4265472 2015-10-05 16:24 kernel
-rw------- root root 512 2015-10-05 16:23 kernel_header
-rw------- root root 2048 2015-10-05 16:23 mtk_header
-rw------- root root 1598976 2015-10-05 16:24 ramdisk.cpio.gz
-rw------- root root 512 2015-10-05 16:24 ramdisk_header
-rwx------ root root 5867520 2015-10-05 16:22 recovery-6592.img
drwx------ root root 2015-10-05 16:24 work
Android sdk
Is it necessary to be the port rom is the same android sdk level of my mobile stock rom ?!
RacerOttavio97 said:
Hi guys,
I'm here to explain my new fresh app that I tested on my HTC Desire 310 and it's faboulous. His name is...
MTKTransfROM
*What does it do?
- This app will let you do all the process of porting an MTK ROM to your MTK phone without a PC! You can choose a lot of options and method, like signing ZIP, Fix BootLoop/Stuck at Boot Logo and even READ BOOT.IMG DIRECTLY FROM YOUR PHONE and AUTOMATICALLY ADAPT THE ROM FOR YOUR PARTITION (/dev/block/mmcblk0p*)
*What do I have to do?
-All you have to do is select the ZIP ROM, choose chipset and options and then click "Port ROM for your device!". The default chipsets installed are taken on online forums, like XDA and 4pda.ru (thanks a lot for those guides), but you can build your own chipset method with a simple text editor!
*How can I build my chipset method?
-The chipset structure is like: e.g.
Then save it as "{THE NAME YOU WANT}.txt" in your SDCard under "MTKTransfROM" named folder (e.g. /storage/sdcard0/MTKTransfROM/mt6589.txt)
*Bugs?
Existing bugs TODO:
-During porting, the UI lags. Don't worry, the app is working. If appears Not Responding error, just wait.
-For now, it's only in English.
*Changelog
**1.2
- Discarded zip4j for problems during extraction, using java.util.zip now
- Fixed Exception on some ROM structures
- Added Exit menu voice if activity doesn't terminate
**1.0
- Initial Release
*Credit
-Kellinwood for his ZipSigner class. Thanks a lot.
Now I need help from you community...
As you can see from Play Store screenshots, it has the "Port boot.img" function. However I'm searching a method to unpack and repack MTK boot.img directly from phone. If someone can help me, I will be the most happy man in the world!
As for now, it's the only thing I need to let this app became perfect!
Google Play Store URL: Click here to be redirected (If it says 1.0, is because it's updating or uploading, I'm writing this post while this app is updating).
P.S. Sorry for my English, I'm Italian.
Click to expand...
Click to collapse
playstore-item not found
what ca i do..??
link not work