Just picked one of these up from Walmart. So far, not a bad tablet for the price. Their website is reporting it will have a KitKat update on July 15, 2014.
Rooting instructions for Nextbook 8 Quad Core (NX785QC8G).
1. Connect to PC via USB, enable USB debugging on tablet, then use Cydia Impactor to create ADB device Driver. (USB>Driver Scan>Create Driver).
2. While connected USB, use Kingo after device driver is installed to complete rooting.
Please post any Rom/Mod information on this thread. There's really no other resource available currently for this tab on XDA.
mjj777 said:
Just picked one of these up from Walmart. So far, not a bad tablet for the price. Their website is reporting it will have a KitKat update on July 15, 2014.
Rooting instructions for Nextbook 8 Quad Core (NX785QC8G).
1. Connect to PC via USB, enable USB debugging on tablet, then use Cydia Impactor to create ADB device Driver. (USB>Driver Scan>Create Driver).
2. While connected USB, use Kingo after device driver is installed to complete rooting.
Please post any Rom/Mod information on this thread. There's really no other resource available currently for this tab on XDA.
Click to expand...
Click to collapse
Thanks for this! I just picked up this tablet today.
mjj777 said:
Please post any Rom/Mod information on this thread. There's really no other resource available currently for this tab on XDA.
Click to expand...
Click to collapse
Ok, let us have a deeper look into the firmware.
Download a Terminal Emulator from Play Store. Boot the tab fresh and type:
Code:
su
dmesg >/mnt/sdcard/dmesg.txt
cat proc/cmdline >/mnt/sdcard/cmdline.txt
cat proc/mtd > /mnt/sdcard/mtd.txt
dd if=/dev/mtd/mtd1 of=/sdcard/kernel.img bs=4096
dd if=/dev/mtd/mtd2 of=/sdcard/boot.img bs=4096
dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtd8 of=/sdcard/system.img bs=4096
Zip the files, upload them to a file-hoster und post the link here.
- Oma -
Oma7144 said:
Ok, let us have a deeper look into the firmware.
Download a Terminal Emulator from Play Store. Boot the tab fresh and type:
Code:
su
dmesg >/mnt/sdcard/dmesg.txt
cat proc/cmdline >/mnt/sdcard/cmdline.txt
cat proc/mtd > /mnt/sdcard/mtd.txt
dd if=/dev/mtd/mtd1 of=/sdcard/kernel.img bs=4096
dd if=/dev/mtd/mtd2 of=/sdcard/boot.img bs=4096
dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtd8 of=/sdcard/system.img bs=4096
Zip the files, upload them to a file-hoster und post the link here.
- Oma -
Click to expand...
Click to collapse
https://www.dropbox.com/s/2ealpbnxribauqr/nextbook files.zip
Ok, this seems to be a generation 2 loader build. System is on /mtd9.
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 00c00000 00004000 "kernel"
mtd2: 00c00000 00004000 "boot"
mtd3: 02000000 00004000 "recovery"
mtd4: 04000000 00004000 "backup"
mtd5: 08000000 00004000 "cache"
mtd6: 3fc00000 00004000 "userdata"
mtd7: 00400000 00004000 "metadata"
mtd8: 00400000 00004000 "kpanic"
mtd9: 60000000 00004000 "system"
mtd10: 130c00000 00004000 "user"
Click to expand...
Click to collapse
So, pls dump system.img again:
dd if=/dev/mtd/mtd9 of=/sdcard/system.img bs=4096
Click to expand...
Click to collapse
- Oma -
Oma7144 said:
Ok, let us have a deeper look into the firmware.
Download a Terminal Emulator from Play Store. Boot the tab fresh and type:
Code:
su
dmesg >/mnt/sdcard/dmesg.txt
cat proc/cmdline >/mnt/sdcard/cmdline.txt
cat proc/mtd > /mnt/sdcard/mtd.txt
dd if=/dev/mtd/mtd1 of=/sdcard/kernel.img bs=4096
dd if=/dev/mtd/mtd2 of=/sdcard/boot.img bs=4096
dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtd8 of=/sdcard/system.img bs=4096
Zip the files, upload them to a file-hoster und post the link here.
- Oma -
Click to expand...
Click to collapse
Oma7144 said:
Ok, this seems to be a generation 2 loader build. System is on /mtd9.
So, pls dump system.img again:
- Oma -
Click to expand...
Click to collapse
It tells me permission denied...even after a fresh reboot.
Type su first.
- Oma -
Oma7144 said:
Type su first.
- Oma -
Click to expand...
Click to collapse
It's working to upload this huge file to dropbox. It'll be available shortly.
---------- Post added at 10:17 PM ---------- Previous post was at 10:10 PM ----------
Oma7144 said:
Type su first.
- Oma -
Click to expand...
Click to collapse
https://www.dropbox.com/sh/9xqb49glypcwy7x/AADOiH0tnPZqrIgFLhIgH6BJa
Can you pls check to dropbox link?
- Oma -
Oma7144 said:
Can you pls check to dropbox link?
- Oma -
Click to expand...
Click to collapse
Sorry about that! here ya go: https://www.dropbox.com/s/uppez7giz0szlc8/system.zip
Ok, well done
Build:
ro.build.display.id=V3.0.8.JDQ39.eng.root.20140401.231924
ro.product.model=NX785QC8G
ro.product.brand=Nextbook
ro.product.name=M865FD
ro.product.device=NXM865FD
ro.rksdk.version=RK31_ANDROID4.2.2-SDK-v1.04.00
ro.rk.bt_enable=false
ro.vendor.name=YFMID
Kernel: 3.0.36+ ([email protected]) (gcc version 4.4.3 (GCC) ) #570 SMP PREEMPT Tue Apr 1 23:48:15 CST 2014
Wifi: Realtek 8188EU USB WiFi driver (Powered by Rockchip,Ver 3.50.WFD) init.
No BT, right?
Are the nextbook apps in the system needed for some reason?
- Oma -
Oma7144 said:
Ok, well done
Build:
ro.build.display.id=V3.0.8.JDQ39.eng.root.20140401.231924
ro.product.model=NX785QC8G
ro.product.brand=Nextbook
ro.product.name=M865FD
ro.product.device=NXM865FD
ro.rksdk.version=RK31_ANDROID4.2.2-SDK-v1.04.00
ro.rk.bt_enable=false
ro.vendor.name=YFMID
Kernel: 3.0.36+ (br[email protected]) (gcc version 4.4.3 (GCC) ) #570 SMP PREEMPT Tue Apr 1 23:48:15 CST 2014
Wifi: Realtek 8188EU USB WiFi driver (Powered by Rockchip,Ver 3.50.WFD) init.
No BT, right?
Are the nextbook apps in the system needed for some reason?
- Oma -
Click to expand...
Click to collapse
Correct, no BT. I've frozen or removed (with Titanium) most of the Nextbook apps.
Nextbook 8 QC by Oma JB 4.2.2 build v1.0
– stock 4.4.0 recovery, CWM 6.0.3.1 recovery
– system ext4
– kernel bryan #570
– internal storage 2 GB
– Multi-User
– ethernet support
– init.d support
– gameloft compatible
– USB-Hub enabled
– gamepad compatible (PS2, XBox, …)
– kernel modules (cifs, tun, lan, serial, audio)
– latest hosts, su, su-binary, busybox
– Reboot Menue, sEFix, FX Sound
– Dateimanager HD (Root)
– Nova Launcher
Instructions are included in the download pack.
Please report any problem with this firmware, I can't verify this custom firmware
works as I don't have the tablet to fully test the custom firmware.
Be aware: it is your own risk!
- Oma -
Oma7144 said:
Nextbook 8 QC by Oma JB 4.2.2 build v1.0
– stock 4.4.0 recovery, CWM 6.0.3.1 recovery
– system ext4
– kernel bryan #570
– internal storage 2 GB
– Multi-User
– ethernet support
– init.d support
– gameloft compatible
– USB-Hub enabled
– gamepad compatible (PS2, XBox, …)
– kernel modules (cifs, tun, lan, serial, audio)
– latest hosts, su, su-binary, busybox
– Reboot Menue, sEFix, FX Sound
– Dateimanager HD (Root)
– Nova Launcher
Instructions are included in the download pack.
Please report any problem with this firmware, I can't verify this custom firmware
works as I don't have the tablet to fully test the custom firmware.
Be aware: it is your own risk!
- Oma -
Click to expand...
Click to collapse
Thanks so much! I"m downloading it now. I'll report back.
I can't get it into flash mode. I killed the battery trying repeatedly. It's now charging. WIll try again after it charges back up.
Oma7144 said:
Nextbook 8 QC by Oma JB 4.2.2 build v1.0
– stock 4.4.0 recovery, CWM 6.0.3.1 recovery
– system ext4
– kernel bryan #570
– internal storage 2 GB
– Multi-User
– ethernet support
– init.d support
– gameloft compatible
– USB-Hub enabled
– gamepad compatible (PS2, XBox, …)
– kernel modules (cifs, tun, lan, serial, audio)
– latest hosts, su, su-binary, busybox
– Reboot Menue, sEFix, FX Sound
– Dateimanager HD (Root)
– Nova Launcher
Instructions are included in the download pack.
Please report any problem with this firmware, I can't verify this custom firmware
works as I don't have the tablet to fully test the custom firmware.
Be aware: it is your own risk!
- Oma -
Click to expand...
Click to collapse
I got it! Now, I'm going to play around with it! Thank you so much!
There is a column with 3 dots (Address, Name, Path, ...), click the empty box.
- Oma -
Oma7144 said:
There is a column with 3 dots (Address, Name, Path, ...), click the empty box.
- Oma -
Click to expand...
Click to collapse
Thank you! Yes, I finally tried that and it worked! I'm so happy!
Can we start a forum on here for this tablet to encourage further development?
This ROM works fantastic! It has worked out the kinks in the Nextbook firmware completely (not saving personalization settings). I'm digg'n it, Oma!
---------- Post added at 05:20 PM ---------- Previous post was at 05:15 PM ----------
http://imgur.com/tbcfWzf
Sent from my Nextbook 8 using XDA Free mobile app
zombiegirl2010 said:
Can we start a forum on here for this tablet to encourage further development?
Click to expand...
Click to collapse
Sure.
- Oma -
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
Hello,
i found a description for enable the native USB-OTG access on this Website. You don't need any app, e.g. StickMount, for the USB access. This is a flashable patch for your Nexus 7 (grouper) device.
Requirements:
- customize recovery
- root access
- USB-OTG cable
Note:
Use Kernel 3.1.10-g830e42f from CM10-Stable (Only changed entries in boot.img-ramdisk.gz).
Tested with:
JB 4.1.2: CM10-ROM, SmoothROM v4.1 and Stock-ROM
JB 4.2.1: CleanROM v3.0 and StockROM.
Thanks:
- CyanogenMod-Team
- Google for Android
MD5:
for JB 4.1.2: f6adbf30518e7d7985430ef277ac5519
for JB 4.2.1: 7a16565c9034ad32920b3466fb81834f
Don't work on my nexus7
@nikdevil
Wich ROM and android version use you?
Cleanrom 2.5, JB 4.2
michaelm_007 said:
Hello,
i found a description for enable the native USB-OTG access on the AOSP-Developer-Website. You don't need any app, e.g. StickMount, for the USB access. This is a flashable patch for your Nexus 7 device.
Requirements:
- customize recovery
- root access
- USB-OTG cable
Tested on Nexus 7 (grouper) with JB 4.1.2 CM10- and Stock-ROM.
MD5: c10d57a8d00072ba29bcb7b33daf6061
Click to expand...
Click to collapse
Can you provide link to where you found this? What versions will it work with 4.2.1, 4.2 or 4.1.2, all versions?
michaelm_007 said:
Hello,
i found a description for enable the native USB-OTG access on the AOSP-Developer-Website. You don't need any app, e.g. StickMount, for the USB access. This is a flashable patch for your Nexus 7 device.
Requirements:
- customize recovery
- root access
- USB-OTG cable
Tested on Nexus 7 (grouper) with JB 4.1.2 CM10- and Stock-ROM.
MD5: c10d57a8d00072ba29bcb7b33daf6061
Click to expand...
Click to collapse
I have to try the patch. It is an elegant solution!
The MODE = 600, I might be wrong but, why not using 666 instead, so that every users can access the data ... might help for >= 4.2.
Interestingly, I have almost the same file in my Ubuntu (with only one line and MODE=666).
alfeuss said:
Can you provide link to where you found this? What versions will it work with 4.2.1, 4.2 or 4.1.2, all versions?
Click to expand...
Click to collapse
link here: http://source.android.com/source/initializing.html under "Configuring USB Access" (i don't know if this is true, because i think it is for the pc, not the nexus. This is the same reason why i think it will not work on the nexus. The zip includes the same code)
@all
Updated ZIP-file
is this work for 4.2.1 ?
michaelm_007 said:
@all
Updated ZIP-file
Click to expand...
Click to collapse
Does not seem to work on my 4.2.1 stock rooted (stickmount is uninstalled).
I have rebooted, patched the v3 in CWM. When back in android, nothing appends when I plug a usb memory stick: it should be mounted automatically in /storage/usbdisk when the usb stick is pluged ? does /storage/usbdisk have to be manally created ?
Doesnt work on AOKP ROM Milestone 1 JB 4.2.
@all
Sorry, i have it tested on JB 4.2.1 and it will not work at the moment. The kernel is the problem and at the moment i can it only offer for JB 4.1.2 :crying:
michaelm_007 said:
@all
Sorry, i have it tested on JB 4.2.1 and it will not work at the moment. The kernel is the problem and at the moment i can it only offer for JB 4.1.2 :crying:
Click to expand...
Click to collapse
Ah too bad! Too nice and simple to be true!
How to remove the patch: just deleting /system/etc/vold.fstab and /system/etc/udev ?
i got to looking into making this work for 4.2 now im no dev or anything and this is just fumbling around with files in a texteditor and or looking at the system files but could it be as easy a fix for 4.2 as this
Code:
## Vold 2.0 fstab for cardhu
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount usbdisk /storage/usbdisk auto /devices/platform/tegra-otg
NicoGa said:
Ah too bad! Too nice and simple to be true!
How to remove the patch: just deleting /system/etc/vold.fstab and /system/etc/udev ?
Click to expand...
Click to collapse
Yes, it should be that. I was bored, so i edited the zip so it will remove the files for you: http://ubuntuone.com/40OkIet0BHFnUhbkMx4Dwf
mid-kid said:
Yes, it should be that. I was bored, so i edited the zip so it will remove the files for you: http://ubuntuone.com/40OkIet0BHFnUhbkMx4Dwf
Click to expand...
Click to collapse
Thanks!
but in fact there may be a typo in your files:
In the zip used to flash the patch the file is named : vold.fstab
While in the zip to remove the patch it is named: void.fstab
Shouldn't it be void.fstab everywhere ?
Also I wonder why you have included a patch with the boot ? (curiosity of a newby)
Finally, where could it be possible to find more information on the mounting process in JB >=4.2 ?
@all
Updated files, now it is compatible with JB 4.1.2 and JB 4.3.1 :laugh:
Will it work on paranoid 2.54 (jb 4.1.2) and M- Kernel a11 ?
@doublin
I think: yes, but my patch use the kernel of CM10 and not the M-Kernel.
Well,I'll do a nandroid and try it myself.
I'll be back in few minutes with feedback.
EDIT:
OK,I just flashed it and plugged in flash drive with some the walking dead episodes.
I can see what's on the flash drive using ES Explorer and Nexus Media Importer.
Problem is i can't open the files. I tried playing the movies using stock movie player and MX Player with no success. Something opens and right after closed back without seeing anything.
Any idea?
EDIT 2:
After a few tests with 2 flash drives ( one NTFS and one FAT16 ) and an external HDD NTFS I noticed that:
The HDD works just fine
The NTFS flash plays only two out of nine episodes.
The FAT16 flash plays two out of four episodes.
Streaming this videos was possible only trough MX Player. Stock video player and ES Explorer's integrated video player didn't work.
I'll keep trying to see what's going on, but anyway this is better than nothing. I was with no USB OTG support with my from and kernel.
NO MORE LINUX OR CYGWIN NEEDED!!!
...now it`s easy as 123...
Boot.img structure should be the same as shown here http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
1. For MTK (chineese) phones - use MTK_unpack.bat (MTK_pack.bat)
2. For android standart phones - use STD_unpack.bat (STD_pack.bat)
To unpack: - drag boot.img (recovery.img) to unpack.bat ("unpack.bat boot.img" in command line)
- will be created "boot" ("recovery") folder with unpacked ramdisk inside - you can make changes and:
To pack back: - drag output folder ("boot" or "recovery") to pack.bat
- will be created new_image.img
I did this successfully on Lenovo A789 MTK6577 - it 100% works fine.
I`ve repack boot and recovery for phones listed below - but have no possibility to check out on the phone - so any volunteers appreciated...
- Samsung Galaxy S i9001, Galaxy III, Note II
- HTC Desire V sense 4
Not work with:
- Samsung Galaxy Note I, Tab I
But be careful - make backup and be ready to flash bricked phone with your flash utility.
UPD. v4 - win8 x64 support
Yeoh michfood, good job man...
i've been hunting up & down for something similar so that fellow xda member will be able to port compatible MT65xx cwmr to their device in Windows without the need of cygwin... :laugh:
Would you like to KANG my Android Kitchen plugins script here... :fingers-crossed:
yuweng said:
Yeoh michfood, good job man...
i've been hunting up & down for something similar so that fellow xda member will be able to port compatible MT65xx cwmr to their device in Windows without the need of cygwin... :laugh:
Would you like to KANG my Android Kitchen plugins script here... :fingers-crossed:
Click to expand...
Click to collapse
glad to hear smth like that :victory:
hope it`ll helps to make some things easily
but TWRP is much better for me for a while
and I`ve my own kitchen to work around with apks and jars and all firmware at all - odex and deodex them, but I didn`t translate it to english yet http://forum.china-iphone.ru/viewtopic.php?f=31&t=19708
Wow, i didn't know you are a
Master Shifu...
Hope you do get it translated to english so that the world will benefit from your hard work too...
yuweng said:
Wow, i didn't know you are a
Master Shifu...
Hope you do get it translated to english so that the world will benefit from your hard work too...
Click to expand...
Click to collapse
i`m just modest user of chineese phone - and while I`ve making it better - I`ve made some scripts - a lot of things i`ve got from this forum
wow... I`m really sorry - yesterday I forgot to attach STD bat files in archive - so please - reload files!
Thanks for the tool, it's compact and fast to work with.
Now at my first attempt to decompile it doesn't find some file and the ramdisk folder inside boot remains empty:
Code:
[total hits/matching patterns/non-matching patterns]
[298/1/0] bin\off2.txt
1 files checked, 1 changed.
- pagesize - 2048
- size of image - 7232000 byte
- ram_disk offset - 3272704
- split kernel...
3268608 bytes copied.
- extract ram_disk.gz...
3959296 bytes copied.
- unpack ram_disk.gz...
- unpack ram_disk.cpio...
[B]The system cannot find the file specified.[/B]
- copy source F:\Porting\ALL_phones_Boot_Recovery_repack_util_for_WINDOWS\boot.img to unpacked folder (to keep source image)...
Press any key to continue . . .
Smth. went wrong... can You give me your boot?
I have to say one thing - not ALL boot can be unpacked - some phones have they own boot structure - it is not correspond to this: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images - so my utility cannot process them.
For example it is Samsung Note (1) Samsung Galaxy Tab (1)... maybe other.
ps _polimorph_ - by the way... I have an interesting idea.
after unpacking gz archive - You should receive a file without extension in /boot folder - usually it is named "ram_disk" - and after that, my script uses it as source cpio archive to extract.
BUT! if in your boot this file was named "rmdisk" for example - script will stop after gz extraction - because were is no right-named cpio file to decompress.
this is easy to check
Works on I9001, but not on I9003.
Alex93917
the structure of stock ROM for i9003 is:
and (!) my utility works fine with normalboot.img - but not (!) with boot.bin - it`s different part of ROM
Now Allowed to Post
michfood said:
NO MORE LINUX OR CYGWIN NEEDED!!!
...now it`s easy as 123...
Boot.img structure should be the same as shown here http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
1. For MTK (chineese) phones - use MTK_unpack.bat (MTK_pack.bat)
2. For android standart phones - use STD_unpack.bat (STD_pack.bat)
To unpack: - drag boot.img (recovery.img) to unpack.bat ("unpack.bat boot.img" in command line)
- will be created "boot" ("recovery") folder with unpacked ramdisk inside - you can make changes and:
To pack back: - drag output folder ("boot" or "recovery") to pack.bat
- will be created new_image.img
I did this successfully on Lenovo A789 MTK6577 - it 100% works fine.
I`ve repack boot and recovery for phones listed below - but have no possibility to check out on the phone - so any volunteers appreciated...
- Samsung Galaxy S i9001, Galaxy III, Note II
- HTC Desire V sense 4
Not work with:
- Samsung Galaxy Note I, Tab I
But be careful - make backup and be ready to flash bricked phone with your flash utility.
UPD. v2 - fixed some bags with STD unpack/pack
Click to expand...
Click to collapse
Hi michfood!
A massive thanks for this fantastic recovery and for all your help getting it to work on my MTK6575 GB v2.3.6 device :angel:
I was not allowed to post here earlier because I was a noob but i am sure you have helped many people without knowing it. Please Please keep up the great work us noob's would be toltally lost without you. :good:
Regards bigrammy.
uboot & nvram backup mtd is it possible?
Hi michfood,
Could I call upon you for help once again
TWRP is without any doubt the best most user friendly recovery :good:
It works flawlessly on my Zopo zp300+ MT6577 Android 4.0.4 (ICS) :good:
With the help you provided me already TWRP also works great on my HDC A9300 MT6575 Android v2.3.6 (GB)
I was wondering if I we could get TWRP to backup uboot & nvram on the mtd version like it does on emmc version
I am unsure of the difficulty in doing this or is it a matter of simply editing a few lines of text.
Could you please advice once again which file's script's I need to edit etc
Here are the mtd partitions again from my device for your info.
adb shell
$ cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "preloader"
mtd1: 000c0000 00020000 "dsp_bl"
mtd2: 00300000 00020000 "nvram"
mtd3: 00020000 00020000 "seccnfg"
mtd4: 00060000 00020000 "uboot"
mtd5: 00500000 00020000 "boot"
mtd6: 00500000 00020000 "recovery"
mtd7: 00120000 00020000 "secstatic"
mtd8: 00060000 00020000 "misc"
mtd9: 00300000 00020000 "logo"
mtd10: 000a0000 00020000 "expdb"
mtd11: 12700000 00020000 "system"
mtd12: 03c00000 00020000 "cache"
mtd13: 07f20000 00020000 "userdata"
Hope you can help :fingers-crossed:
Thanks. bigrammy
I suppose it`s better to ask such question in TWRP thread.
Possibly You can achieve that with changing smth. like vold.fstab.
But possibly not - because it may need to change source codes and recompile again whole recovery binary
michfood said:
I suppose it`s better to ask such question in TWRP thread.
Possibly You can achieve that with changing smth. like vold.fstab.
But possibly not - because it may need to change source codes and recompile again whole recovery binary
Click to expand...
Click to collapse
Thanks for your reply :good:
So not quite so easy then I thought it maybe a bit more complicated but I had to ask :laugh:
I will post the question over on the TWRP thread as you suggest to see if anyone there can help :fingers-crossed:
Thanks again michfood for your help & hard work on this tool :angel:
Regards. bigrammy
bigrammy said:
but I had to ask
Click to expand...
Click to collapse
- no question, no answer
U understand that I mean... in Russia there`s a good saying - "follow to Kiev by tongue" - means do not shy to ask - it`s much better to be "know-hothing"
Experts,
Can you give any idea on Xperia boot structures!
Pls!
And would this work on Xperia 2011 series!
If not,why?
Sent from my MT11i using xda premium
I have problems to repack recovery.img for my Tegra3 device.
The script always say : access denied, pack rmdisk to cpio..., after this file not found , error unsupported page size0,....
Last try was simply repack the successfully unpacked folder. but fails
Any Idea ?
Best regards
cm
cmoegele said:
I have problems to repack recovery.img for my Tegra3 device.
The script always say : access denied, pack rmdisk to cpio..., after this file not found , error unsupported page size0,....
Last try was simply repack the successfully unpacked folder. but fails
Any Idea ?
Best regards
cm
Click to expand...
Click to collapse
which OS You use to? I hope it`s not win8? There are known problems with admin`s permissions
Ghostfreak NB said:
Experts,
Can you give any idea on Xperia boot structures!
Pls!
And would this work on Xperia 2011 series!
If not,why?
Click to expand...
Click to collapse
I haven`t, have You?
I`ve no answer because I never repacked Xperia boots. To do so, at first I need a Xperia boot.img
michfood said:
which OS You use to? I hope it`s not win8? There are known problems with admin`s permissions
Click to expand...
Click to collapse
Windows 7 locks the rmdisk folder so the script will fail.
Exec: %~dp0bin\chmod og=xr rmdisk
Then Cd rmdisk will give:
Access is denied.
- pack rmdisk to cpio...
/usr/bin/find: `./rmdisk': Permission denied
28482 blocks
The system cannot find the file specified.
- pack rmdisk.cpio to gzip...
- make new image...
The system cannot find the file ../pagesize.txt
- pagesize
error: unsupported page size 0
The system cannot find the file specified.
- done.
Press any key to continue . . .
ROM build is now up links are at the bottom,
This is for the HS_Q6_MB_V1.0 revision board,
ZMA_12_MB_V1.0 revision boards see the last post on thread for a working incomplete modded firmware.
Personally rebuilt stock OS installed on the R11 max china phone firmware with all mods done by myself apart from the optional modified boot.img
------------------------DISCLAIMER------------------------
Flash this Firmware at your own risk i am in no way responsible for any damage that can occurr flashing your MTK device with flash tools, such as
•Hardbricked devices
•Soft Bricked devices
•Lost imei or baseband issues
or anything else for that matter, you are solely responsible for the actions you make when flashing this firmware, however following instructions below you shouldnt have a problem with the device and you can enjoy your new updated R11 max Firmware.
______________________________________
R11 MAX DEVICE INFO
______________________________________
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
ROM ispre-rooted with SU & Busy Box binaries which will remain after factory reset.
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
INT RAM: 128KB SDRAM
EXT RAM: 512MB DRAM
NAND: (4GB + 4096MB) [HYNIX] - H9DA4GH4JJAMCR_4EM
Boot Style: NAND BOOT
Size: 0×20000000 [0.500GB]
BlockSize: 2048 SpareSize: 64 BMT blocks: 80
_____________________________________
REMOVED
_____________________________________
• Cooee launcher ( spyware )
• Marshmallow game ( adware )
• Browser
• calander
• gallery
• camera
• music fx
• exchange2
• email
• Volume control
• framework.jar
• calculator
• music player
• File manager
• system/vendor apps/FBlite/Whatsapp
• Stock boot animation
• Stock shutdown animation
• Stock start tone
• Stock Shutdown tone
• Stock UI sounds
• Stock Notifications sounds
• Stock Ringtone Sounds
• Stock Boot Logo
• Libs from removed apps
• framework from removed apps
• -res from removed apps
• Build.prop (Edited)
• Test Keys (they should be release)
• Wallpapers
• Live wallpapers
• Network Restriction lock (network Lock )
• Modem (connectivity & imei issues )
Plus alot more crap removed that i cant remember right now....
___________________________________________
ADDED OR REPLACED
___________________________________________
• SU Binary pre installed to system, will remain even after factory reset.
• BUSY BOX 1.28 binary pre installed to system, will remain even after factory reset.
• Nova Launcher as new stock launcher
• Opera mini browser (fast with inbuilt DL manager
• Google Calander
• Gmail
• Google wallpaper picker
• FOTO gallery 3.3
• Open Camera
• MTK Video Wallpapers
• Vivo Wallpapers
• Bubbles Live Wallpaper
• JRD Music Player
• JRD File Manager
• JRD Calculator
• updated exchange2
• JRD Secure container
• JRD FOTA & services
• JRD plugger
• Gmail
• MTK Sim Engineering mode
• Updated music FX
• CDS info.apk
• AVG mobile antivirus PRO* 365 day subscription free free from me
• JRD video player
• JRD video favourites
• JRD media container
• JRD Facelock
• Mobile Log
• Modem log
• Alcatel one touch manager agaent (wifi data sync)
• VIVO Boot Animation
• VIVO Shutdown Animation
• VIVO Boot Tone
• VIVO Shutdown Tone
• Updated Boot Logo
• Samsung G930F oreo Ringtone Sounds
• Samsung G930F oreo Notification Sounds
• Samsung G930F oreo UI sounds (where available)
• Build prop edited to display as VIVO R11 max
• Other .prop edits
• Updated to Release Keys (was test keys)
• updated libs for Jrd app support
• updated framework for Jrd app support
• updates -res for Jrd app support
• a few JRD -res and libs interswapped from alactel 4027A 4.4.2 EMMC with 3.4.67 Kernel also for use of some JRD features
• root set to function without the need for Su manager app binaries can run themselves.
• changed format of FAT from yaffs_img to normal_rom in scatter for use of the 37.8mb usb partition to be also used for for system storage aswell,
• UPDATED 3G modem to fix connectivity issues (pulled from HTC desire 310)
• added mount points to system for better SD card support and to mount as internal device storage when SD card is inserted.
•Replaced some system apps and some other apps from and alcatel OT 5050 MT6575 for faster UI and system stability.
•integrated framework2 into /system/framework/ as was completely absent, NOTE you cannot remove framework2 or any of its components you will break the system
Everything added or replaced came from the followimg devices.
•ZTE luna MT6572 EmmC
•Alcatel 4027 MT6572 EmmC
•Alcatel 5050 MT6575 EmmC
•HTC 310 MT6572 EmmC
•Samsung S7 Exynos8890
------------STORAGE CAPACITY--------------
storage free space is as follows without an SD card inserted before and after flash of new firmware
BEFORE
/data 20mb
/system 9.0kb
/usb storage 37.8mb (not usable)
AFTER
/DATA 62.9mb
/SYSTEM 25.2mb
/USB STORAGE 37.8mb (usable)
---------☆☆☆MODIFIED BOOT IMG☆☆☆---------
as these R11 max only come with a 512mb NAND chip with OS installed there is only 62.9mb Data storage after flash of my firmware,using the modified boot.img this allows you to use the devices SD card as the devices ROM & internal storage, info on my device with 15GB SD card,
/DATA 12.9GB
/SYSTEM 25.2MB
/USB storage 37.8MB
/internal storage 1.02GB
This has not been implemented into the build due to firmware size when pulling,
If you wish to use the modifed Boot.img and SD card you MUST partition the SD card BEFORE flashing the firmware if you wish to use the boot.img which is OPTIONAL rom will work fine without it,
partition your SD card as follows with 2 partitions
•PRIMARY partition - FAT32
•PRIMARY partition - EXT4
You should name your EXT4 partition that you made as "mmcblk0p2".
To flash with modified boot.img follow steps above for SD card, and steps below for flashing.
NOTE
if you use the boot.img you will need to reconfigure NOVA launchers looks in the Nova settings once flashed everything else is fine
WORKING
• everything is working unless stateded below
NOT WORKING
• VIVO wallpapers (not showing need to rubuild framework-res to set default as vivo)
• FaceLock (due to root installed secure container wont run, unroot and it should)
__________________________________________
FLASHING THE FIRMWARE
__________________________________________
********This is a "UBIFS" filesystem*********
EMMC storage devices are NOT compatible
Unless you change the scatter to support your file system and even then it may require porting still.
Open SP flash tool, and open the scatter.file and change flash method to download only and click download, plug the device in while switched off and the device will flash,
DO NOT USE "format all + download" unless you have a backup of your firmware and security partition or you WILL lose your imei.
________________________________________
LINKS
________________________________________
SP FLASH TOOL :
https://spflashtool.com/download/SP_Flash_Tool_v5.1824_Win.zip
FIRMWARE DOWNLOAD:
https://drive.google.com/file/d/1mK3lnvqSzvtMajyWm1S1YplfQvPlgcgY/view?usp=drivesdk
MODIFIED BOOT IMG :
https://drive.google.com/file/d/1IRwW4SY-mcRfRrFLYw45CpKacmoRRRW3/view?usp=drivesdk
all credits go to Luca Roggero for building this boot .img to allow SD card to be used as system & rom storage.
_______________________________________
☆☆EDIT☆☆
You must change the storage to SD card and "let the system decide" in preferences on initial fieat boot or you will get a soft reboot when installing any app for the first time it can be changed back after if wanted
Also all other MT6572 nand devices that are not an R11 max chinaphone flash only the android file in firmware first with download only to see if will boot (give it 5 or so minutes) and dont forget to take a partition information table backup to change to your addessses in the scatter of this firmware if no boot do a full flash with download only option again allow 5 minutes to boot dont forget to change addresses and lengths also to match your partition info.
Take a firmware backup also, NCK_MTK dongle can obtain the PIT info, backup your firmware and userdata also and has a variety of other usefull finctions such as formatting & network unlocking & imei and baseband backups aswell
Attention all users of R11 max,
New build will be up in a week maximum, Google play is functional, and has been completely rebuilt, i have also built a custom recovery for this model R11_Max however wont be released until the new rom is released.
Thread will be updated here with new links when its ready.
New rom is not far away now for the R11 MAX im just finishing up some minor touchups in the meantime i have built a number of custom recoveries for the phones due to 1 there not being any available at all for it & 2 all recovery porting tools do not work with this phone so manually built a number of different styles,versions etc theres TWRP, CTR, CWM, etc even an OPPO touch recovery even that i also managed to build enjoy,
https://forum.xda-developers.com/android/development/recovery-t3892041
Ti ringrazio
Sei un genio!!!! non ne potevo più di vedere memoria piena e questo launcher pietoso
---------- Post added at 10:30 ---------- Previous post was at 09:44 ----------
Problema: ho flashato la rom, flash andato ok nessun errore, però ora non si accende. Poco dopo che premo il pulsante di accensione fa solo una vibrazione e basta :/
metrovinz said:
Sei un genio!!!! non ne potevo più di vedere memoria piena e questo launcher pietoso
---------- Post added at 10:30 ---------- Previous post was at 09:44 ----------
Problema: ho flashato la rom, flash andato ok nessun errore, però ora non si accende. Poco dopo che premo il pulsante di accensione fa solo una vibrazione e basta :/
Click to expand...
Click to collapse
?? English please
Note all R11 max users,
A new rom will be released for this device by me in the near future when released it is advised to update to the latest build, modded with CM but stock 4.4.4 unfortunately that is all i am able to upgrade it to, 6.0 build i am scrapping for now i can get 6.0 apps to install but they just will not run most not at all,
Another note though ive managed to modify the boot.img some more to swap not only the data from
"ubifs" "UBI" "userdata" "/data" to
"Ext4 "EMMC" "/dev/block/platform/mtk-msdc.1/by-num/p2 (EXTERNAL SD)
but also system from
"ubifs" "UBI" "system" "/system" to
"ext4" EMMC" "/dev/block/mmcblk0p3" "/system" (SDCARD)
Not sure if i can get a rom functional to boot from it but TWRP recognises it aswell as mounts & formats it correctly, some useful info incase anyone else wants to give it a go also
I'm seeking ROM for my R11-1 device which is similar to R11 max.
I'm seeking ROM for my R11-1 device which is similar to R11 max.
The big difference between my R11-1 device and R11 max is the partition size for system.img.
R11-1 is 360MiB and R11 max is 310MiB.
I got some info of R11-1, but now it's bricked. I flashed wrong ROM..
Thank you for reading and I'm happy if you could help me.
______________________________________
R11-1 DEVICE INFO
______________________________________
[email protected]_ctx_jr151_p113m_r10_nd44_2k_2g_fl:/ $ df
Filesystem Size Used Free Blksize
/dev 238.2M 128.0K 238.1M 4096
/sys/fs/cgroup 238.2M 12.0K 238.2M 4096
/mnt/secure 238.2M 0.0K 238.2M 4096
/mnt/asec 238.2M 0.0K 238.2M 4096
/mnt/obb 238.2M 0.0K 238.2M 4096
/system 320.0M 235.7M 84.3M 4096
/data 80.5M 68.4M 12.1M 4096
/.cache 7.0M 772.0K 6.2M 4096
/fat 20.0M 2.6M 17.4M 4096
/protect_f 1.5M 784.0K 752.0K 4096
/protect_s 1.5M 780.0K 756.0K 4096
/mnt/cd-rom 1.2M 1.2M 0.0K 2048
/mnt/media_rw/sdcard0: Permission denied
/mnt/secure/asec: Permission denied
/storage/sdcard0 17.8M 352.0K 17.5M 4096
[email protected]_ctx_jr151_p113m_r10_nd44_2k_2g_fl:/ $ cat /proc/partitions
major minor #blocks name
7 0 1254 loop0
7 1 18304 loop1
253 0 393216 zram0
31 0 512 mtdblock0
31 1 1024 mtdblock1
31 2 1536 mtdblock2
31 3 1536 mtdblock3
31 4 1536 mtdblock4
31 5 128 mtdblock5
31 6 384 mtdblock6
31 7 6144 mtdblock7
31 8 6144 mtdblock8
31 9 256 mtdblock9
31 10 384 mtdblock10
31 11 1024 mtdblock11
31 12 2048 mtdblock12
31 13 20480 mtdblock13
31 14 368640 mtdblock14
31 15 7168 mtdblock15
31 16 94848 mtdblock16
[email protected]_ctx_jr151_p113m_r10_nd44_2k_2g_fl:/dev/block $ cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "preloader"
mtd1: 00100000 00020000 "pro_info"
mtd2: 00180000 00020000 "nvram"
mtd3: 00180000 00020000 "protect_f"
mtd4: 00180000 00020000 "protect_s"
mtd5: 00020000 00020000 "seccnfg"
mtd6: 00060000 00020000 "uboot"
mtd7: 00600000 00020000 "boot"
mtd8: 00600000 00020000 "recovery"
mtd9: 00040000 00020000 "secstatic"
mtd10: 00060000 00020000 "misc"
mtd11: 00100000 00020000 "logo"
mtd12: 00200000 00020000 "expdb"
mtd13: 01400000 00020000 "fat"
mtd14: 16800000 00020000 "system"
mtd15: 00700000 00020000 "cache"
mtd16: 05ca0000 00020000 "userdata"
[email protected]_ctx_jr151_p113m_r10_nd44_2k_2g_fl:/system $ cat build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=ALPS.KK1.MP7.Band1.2.5.V1.3-2018-10-09_12-33
ro.build.version.incremental=eng.daiweiping.1539059404
ro.custom.build.version=DW_MT6580_ZM9_FWVGAJ_CXT_RJ151_P113_R10_hhx_ZHX_FL_V1.0_20181009
ro.build.version.sdk=19
ro.defwidth2=480
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=2018年 10月 09日 星期二 12:33:14 CST
ro.build.date.utc=1539059594
ro.build.type=user
ro.build.user=daiweiping
ro.flash=yes
ro.build.host=user
ro.build.tags=test-keys
ro.product.model=R10
ro.product.name=R10
ro.product.device=zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl
ro.product.board=zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl
ro.product.brand=alps
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl-user 4.4.2 KOT49H eng.daiweiping.1539059404 test-keys
ro.build.fingerprint=alps/zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl/zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl:4.4.2/KOT49H/1539059404:user/test-keys
ro.build.flavor=
ro.build.characteristics=default
persist.sys.launcher=com.shly.theme.s6
dw.control.2d=true
ro.sversion=8200
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK1.MP7.Band1.2.5.V1.3
ro.mediatek.platform=MT6572
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=MAIN2.1
ro.mediatek.version.sdk=2
# end mediatek build properties
#
# from out/target/product/zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=128m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
ro.operator.optr=CUST
ro.kernel.zio=38,108,105,16
persist.sys.timezone = Asia/Dubai
ro.camera.front.sizeindex=0
ro.camera.back.sizeindex=0
persist.sys.sign_3g_4g=3
persist.sys.frontcamera=800W
persist.sys.backcamera=1600W
ro.defwidth=960
ro.defwidth2=960
isWallpaperSlide=true
bluetooth.HostName = X21
persist.sys.resolution=1920x1080
persist.sys.fingerprint2=true
persist.sys.hidenavigation=true
persist.sys.isshowrealrom=1
persist.sys.isshowrealram=1
factory_code=*#66*#
engineering_code=*#*#3646633#*#*
imei_code=*#0623#
hideSwitch_code=*#0011#
isshowUSB=false
ishotseatAllAppsRank=true
ro.product.name=R10
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=1
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=mediatek.wlan.module.postfix=_
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ro.fota.oem=MTK_KK
ro.fota.platform=MTK_KK
ro.fota.type=phone
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4_r5
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Hey mate,
Youve got the R10
In which i dont have one of those unfortunately, when you flashed the wrong firmware did you flash PRELOADER, UBOOT & BOOT ?
if so youve deffo messed it up,
Im assuming you didnt take a firmware backup first either ? If you did flash it back with SP flash tool if you didnt then i wont be able to help you i dont think unless by some miracle they both use the exact same kernel, either way i have 3 R11 firmwares
2 are ubifs NAND firmwares for the R11 max & the 3rd is an ext4 eMMC for R11 im happy to upload the UBOOT, PRELOADER & BOOT files from all 3 to see if you can get some life back into the device as they are all made from the same chinese manufacturer.
If you can get the device to at least turn on to the boot screen then after flash then the files are good you can then flash the ANDROID, CACHE & USRDATA from my firmwares here on xda and it should come back to life as i have tested this on the R11 EMMC i flashed my UBIFS system.img to the device & worked no problem,
system size also does not matter as long as the ANDROID file is not bigger than your system partition so that should also be fine,
You should never ever flash another devices preloader, uboot or boot.img as the kernels are compiled differently on each device in most cases,
If you cant get any power to the device to flash then take the backing off and take all the screws out take the backing off and look for a series of 4 -6 gold circular points.
These are called test points plug the device in and start the flash on pc then touch all the points with your finger you should now hear the VCOM connect to the device and flash the files youve loaded into SP
#edit ive just looked at your partition info you have the exact same layout as the R11 MAX ubifs models i have so ill upload the boot.img, preloader & uboot from my 2 variations for nand as both have different kernels so hopefully one will work for you & get power back.
Hello Matty1993,
Thank you very much for your reply!
It was good to find out my device name, R10!
>did you flash PRELOADER, UBOOT & BOOT ?
Yes,sir. I formatted all without taking any backup! I'm foolish..
>ill upload the boot.img, preloader & uboot from my 2 variations for nand as both have different kernels so hopefully one will work for you & get power back.
Thank you for your kindness,I wanna try it!
[email protected] said:
Hello Matty1993,
Thank you very much for your reply!
It was good to find out my device name, R10!
>did you flash PRELOADER, UBOOT & BOOT ?
Yes,sir. I formatted all without taking any backup! I'm foolish..
>ill upload the boot.img, preloader & uboot from my 2 variations for nand as both have different kernels so hopefully one will work for you & get power back.
Thank you for your kindness,I wanna try it!
Click to expand...
Click to collapse
Hey mate,
No worries at all,
For future references on your mtk devices it is always advisable to take a firmware backup using SP Flash tool you can do this by entering the readback menu or by using MTK nck dongle there is a free version in which works quite well which outputs the pulled files directly into there segregated partitions eg preloader, uboot, boot, secro,usrdata,system,cache files aswell as generating a scatter ready to be loaded into SP flash tool great program i use it all the time,
Anyhow give me 5-10mins & ill upload both of my variations of the R11 boot preloaders & uboot as youll need to flash them all to get rid of the other ones both have diff kernels as i mentioned so give them both a try and see how you go,
Let me know if they dont work also as i can ask a few people to see if maybe they have one they can pull a backup from.
#edit my google drive isnt working ill upload as soon as it is
Hey mate google drives back up now heres the links for preloader, uboot, & boot
R11 max ubifs ZMA_12_MB
https://drive.google.com/file/d/1kW34rLGyWGcUT04i3ThXGMM703frVHPr/view?usp=drivesdk
R11 max ubifs HS_Q6_MB
https://drive.google.com/file/d/1tTZjnGN5jQQ2lIl_4FmqPtyuoXsH1dJm/view?usp=drivesdk
See how they go
Hello Matty1993,
Thank you for your time and ROMs.
I flashed them and my device got power back with ZMA_12_MB.
I'm very happy to see NOT black screen!!
I took pictures.
I don't know the boot screen is working or freezing.
The title logo is 'boost mobile' and there are vertical stripes and flickling a little.
Anyway,I got advance a little! Thank you,again.
[email protected] said:
Hello Matty1993,
Thank you for your time and ROMs.
I flashed them and my device got power back with ZMA_12_MB.
I'm very happy to see NOT black screen!!
I took pictures.
I don't know the boot screen is working or freezing.
The title logo is 'boost mobile' and there are vertical stripes and flickling a little.
Anyway,I got advance a little! Thank you,again.
Click to expand...
Click to collapse
Hey mate,
Your device isnt R10 yours is R11 ZMA Variant ive confirmed this by looking at the pics youve provided,
The logo will look like that due to either 2 things the firmware or logo is still on the device,
1 either the logo is to small or to big for the device causing the lines, or 2 the firmware you flashed is using a diff LCD driver,
Give me a bit when i get home from work ill upload a full firmware for the ZMA_12_MB variant for you, its not the best but once ive finished on the R11_HS_Q6_MB firmware ill be doing the ZMA_12_MB after, the firmware ill be uplaoding is somewhat modified however,
Also did you know that there a storage fix available for these R11, all it requires is a modified boot.img which im happy to do now i know the zma12 kernel is your model for sure, & a decent class 10 sd card with an ext4 partition on it, ive already got a modified boot.img for the hsq6 variant i made a 14GB ext4 partition now data is 14GB instead of 20MB lol no lag at all or anything due to the sd being class10
Hello Matty1993,
Thank you for your informative insight.
I'm happy to hear that my device may revive and also transform to a practical device!:good:
I'm look forward to flashing your firmware!!
[email protected] said:
Hello Matty1993,
Thank you for your informative insight.
I'm happy to hear that my device may revive and also transform to a practical device!:good:
I'm look forward to flashing your firmware!!
Click to expand...
Click to collapse
Hey mate sorry i couldnt get the firmware up for you last night having troubles with PC being slow reinstalling windows on it now and ill get the FW up for you as soon as its booted up as its all stored on my 2TB external HD
Hey mate wow didnt realise it been 3 days will have the firmware up for you today some time 100% been doing some modifications to it as i didnt realise how crap the OS was still, ive also modified a stock boot.img aswell as a modifed storage boot.img with CM sources and im just about finished making the OS look a bit better, still gonna look bad as it was a quick job but it will be alot better than what it was before until i get around to properly building the firmware for the zma variant,
Ill update this post with the link soon as its uploaded sorry again for the wait mate
Hello Matty1993,
Pls don't worry about making me wait.
This is not a job,we do because we like it,isn't it?
Let's do it slowly.
[email protected] said:
Hello Matty1993,
Pls don't worry about making me wait.
This is not a job,we do because we like it,isn't it?
Let's do it slowly.
Click to expand...
Click to collapse
Hey mate,
Link will be up soon for you firmwares uplaoding to google drive still needs work but ive redone quite a bit considering what it used to look like youll see anyhow, some of the stuff ive done is modded the camera app & gallery app to run on 4.4, modded system to run cyanogenmod trebuchet launcher, redone the settings & dropdown and also built a setupwiz for it aswell which you will see,
I will finish it up after im done with the HS_Q6 variant, if theres anything majorly wrong with calls or anything etc let me know and ill get it sorted,
I cant test the ril as these are 2G network handsets, Australia dosent have 2G network anymore but it should be all good i know what im doing
## EDIT ##
Link for firmware is here,
https://drive.google.com/file/d/1Ix-k9Myjt1Mc9Rs36wQgRHXuQtU58Pwg/view?usp=drivesdk
Theres a readme id strongly suggest to read it before flashing as theyre are some extra files i have added, also the flash layout is very diff from normal MTK firmwares for 6572 as ive modifed most partitions already just never got around to the theming side of things on the zma variants
Anyhow let me know how you go
Hello Matty1993,
Thank you for your great works.
I flashed R11_Max_ZMA_12_MB_1.0_GT18_MT6572_NAND+UBIFS_20190322.
Then when I power on,the boot screen is shown with google logo 'G'.
But after that,it seems like to be freezing.
When I connect my device to my linux pc,my device is recognized as USB device.
[201999.116029] usb 1-4: new high-speed USB device number 7 using ehci-pci
[201999.248871] usb 1-4: New USB device found, idVendor=0bb4, idProduct=0001
[201999.248878] usb 1-4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[201999.248883] usb 1-4: Product: MT65xx Android Phone
[201999.248887] usb 1-4: Manufacturer: MediaTek
[201999.248891] usb 1-4: SerialNumber: 0123456789ABCDEF
[201999.249986] usb-storage 1-4:1.0: USB Mass Storage device detected
[201999.254160] scsi host6: usb-storage 1-4:1.0
[202000.252799] scsi 6:0:0:0: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2
[202000.253292] scsi 6:0:0:1: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2
[202000.258682] sd 6:0:0:0: Attached scsi generic sg2 type 0
[202000.261076] sd 6:0:0:1: Attached scsi generic sg3 type 0
[202000.262946] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[202000.265932] sd 6:0:0:1: [sdc] Attached SCSI removable disk
OPPO RECOVERY Ver 1.0 seems to be working good!
However there are vertical stripes and flickling a little,I can select menu like wipe data etc.
I took pictures below.
I'm very very happy if your custom_boot_storage_modified_zma_12_mb_1.0.img could work on my device!