Rooting And Development For MID 1045

[unasoto]

after your do root and install CW recovery, I believe that you can just boot to recovery and install zip from sdcard and select the 20120429 to install the google apps package

 

[unasoto]

ssalavat posted this, and this is what I've been looking for

mountrootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandd /system ext4 ro,relatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journ al_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journ al_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandi /mnt/private vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022 ,codepage=cp437,iocharset=ascii,shortname=mix
ed,errors=remount-ro 0 0
/dev/block/vold/93:80 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime
=0020,codepage=cp437,iocharset=ascii,shortname=mix ed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:80 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_
utime=0020,codepage=cp437,iocharset=ascii,shortnam e=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

if someone can make a cache.img and post it. I think I could make a zip that I could flash to repair my cache
this should work I think

adb shell su -c "cat /dev/block/nandh> /sdcard/dump/cache.img" > NUL
adb pull /sdcard/cache.img

 

[unasoto]

OK I think I might have made some progress I went to do something on my Ubuntu dual boot and had a billion updates in my package manager so I said get and went to make dinner came back ate dinner while it finished up (yeah 6 months since I last used it and longer since I updated) So just for ****s and giggles I put android into the search box and found abootimg - AC100 Wiki so I got it and ran my boot.img, Kawboy, and kavenfradejas boot.img through it and this is what I got. Note the ramdisk size difference and when I did abootimg -x boot.img to extract the img I got a file initrd.img that is 170kb and their initrd.img files are 179kb I think I got a bad boot.img I'm going to make a update.zip and try to fix it

Myboot.img
unasoto@ubuntu:/host/Shared/Stuff/Android/Boot$ abootimg -i boot.img
Android Boot Image Info:
file name = boot.img
image size = 33554432 bytes (32.00 MB)
page size = 2048 bytes
Boot Name = ""
kernel size= 8122052 bytes (7.75 MB)
ramdisk size = 180271 bytes (0.17 MB)
load addresses:
kernel: 0x40008000
ramdisk: 0x41000000
tags: 0x40000100
cmdline = console=ttyS0,115200 rw init=/init loglevel=8
id = 0x2e0927e4 0xaa3d7fec 0x1bd51b4c 0x253badf2 0x9d011abd 0x00000000 0x00000000 0x00000000

Kawboy's boot.img
unasoto@ubuntu:/host/Shared/Stuff/Android/Boot$ abootimg -i boot.img
Android Boot Image Info:
file name = boot.img
image size = 33554432 bytes (32.00 MB)
page size = 2048 bytes
Boot Name = ""
kernel size = 8122052 bytes (7.75 MB)
ramdisk size = 183477 bytes (0.17 MB)
load addresses:
kernel: 0x40008000
ramdisk: 0x41000000
tags: 0x40000100
cmdline = console=ttyS0,115200 rw init=/init loglevel=8
id = 0xef02d917 0xdcf11b54 0xe6078491 0x016bf834 0xedbd5a8b 0x00000000 0x00000000 0x00000000

kavenfradejas boot.img
unasoto@ubuntu:/host/Shared/Stuff/Android/Boot$ abootimg -i boot.img
Android Boot Image Info:
file name = boot.img
image size = 33554432 bytes (32.00 MB)
page size = 2048 bytes
Boot Name = ""
kernel size = 8122052 bytes (7.75 MB)
ramdisk size = 183462 bytes (0.17 MB)
load addresses:
kernel: 0x40008000
ramdisk: 0x41000000
tags: 0x40000100
cmdline = console=ttyS0,115200 rw init=/init loglevel=8
id = 0x72008c6f 0x587c5c89 0x40db3904 0xe2bede68 0x0f64ab72 0x00000000 0x00000000 0x00000000

 

[vampirefo.]

These are all the same boot.img just packing is slightly different, nothing here.

 

[unasoto]

OK I have made some progress and I think figured out what is wrong with my tab, I have lost root. I booted into stock recovery to try a new boot.img update it verification failed and it aborted. then I used the temp CW recovery and tried to wipe dalvik cache and got the same errors I always got so I did a show log and got bunch more errors that I hadn't seen before. I then did a report errors and this is what I got in the recovery log full log here https://docs.google.com/file/d/0Bzj3t6CnUni0OVN5UVBaN2MtajA/edit?usp=sharing so I need to reroot from a zip file now I know what I need to do just not how to do it yet, and knowing is half the battle

this is the wipe dalvik cache note the read-only file system errors

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:Can't unlink /cache/recovery/command
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
E:unknown volume for path [/sd-ext]
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected][email protected]': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache/data@[email protected]@classes.dex': Read-only file system
rm: can't remove '/data/dalvik-cache': Read-only file system
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
W:failed to mount /dev/block/nande (Invalid argument)
W:failed to mount /dev/block/nande (Invalid argument)
W:failed to mount /dev/block/nande (Invalid argument)
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:Can't unlink /cache/recovery/command

and this is the wipe data

-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Discard failed


Formatting /cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
warning: wipe_block_device: Discard failed


Formatting /sd-ext...
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.
W:failed to mount /dev/block/nandh (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/nandh (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/nandh (Invalid argument)
W:Can't unlink /cache/recovery/command
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc

 

[unasoto]

Ok I think I have it, I took the code from cobyadb Root and Dump Utility for Windows and I'm converting it to a zip file that can be used to root/reroot your tablet from the SDcard thankyou traveller1701

this is the base code for rooting that I pulled from traveller's batch file

@ping localhost -n 5 > NUL
adb.exe push data /data/local/tmp/ > NUL
@ping localhost -n 5 > NUL
adb.exe shell chmod 0777 /data/local/tmp/mempodroid > NUL
adb.exe shell /data/local/tmp/mempodroid 0xd7cc 0xad27 sh /data/local/tmp/root.sh > NUL
@ping localhost -n 5 > NUL
@ping localhost -n 5 > NUL
adb.exe reboot > NUL
@ping localhost -n 5 > NUL

This is what I turned it into could someone check this to make sure I got it right? I'm not sure if I got the run_program line correct, and should I use set_perm_recursive for the rest of the files in the folder?

format("ext4", "EMMC", "/dev/block/nandd","0");
format("ext4", "EMMC", "/dev/block/nande","0');
mount("ext4", "EMMC", "/dev/block/nandd", "/system");
mount("ext4", "EMMC", "/dev/block/nande", "/data");
package_extract_dir("data", "/data/local/tmp");
set_perm(0, 0, 0, 0777, "/data/local/tmp/mempodroid");
run_program("/data/local/mempodroid", "0xd7cc 0xad27", "sh", "/data/local/tmp/rootsh");

edit got an error, fixed
script aborted: format() expects 4 args, got 3

 

[unasoto]

ok tried again and in CW recovery log got

-- Installing: /sdcard/update.zip
E:Can't open /cache/recovery/last_install
E:failed to open last_install: I/O error
Finding update package...
I:Update location: /sdcard/update.zip
Opening update package...
Installing update...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
warning: wipe_block_device: Discard failed


Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Discard failed


minzip: Extracted file "/data/local/tmp/Superuser.apk"
minzip: Extracted file "/data/local/tmp/busybox"
minzip: Extracted file "/data/local/tmp/install-cwm-recovery.sh"
minzip: Extracted file "/data/local/tmp/install-stock-recovery.sh"
minzip: Extracted file "/data/local/tmp/mempodroid"
minzip: Extracted file "/data/local/tmp/reboot-recovery"
minzip: Extracted file "/data/local/tmp/root.sh"
minzip: Extracted file "/data/local/tmp/su"
about to run program [/data/local/mempodroid] with 4 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
script result was [256]


Install from sdcard complete.
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:Can't unlink /cache/recovery/command
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc

 

[Poekie]

Hi all, I've successfully rooted many android phones, but the MID1045 is the first tablet I've gotten. I'm looking to get some of the functionality of my rooted phones on my tablet (i.e. CWM, Google Apps, Superuser)

I've tried a few different methods to root the 1045 (SuperOneClick, DooM's, and the CobyADB utility) but the one that worked successfully for me was the Root With Recovery method by Bin4ry.

Since there isn't a dedicated thread for the MID1045, if anyone else knows of how to get Google Apps, CWM, the Play Store, and ROMs working on the MID1045, please share it here, as I'm a little lost. Thanks!

(p.s. Posted Stock sysdump in the Sticky thread)

Hello, I tried to root but I got the message cannot dectect the device. It is asking for ADB driver. Where can I find ADB driver for coby kyros MID1045

 

[unasoto]

ok poekie check this post out http://www.androidtablets.net/forum...rooting-development-mid1045-2.html#post261073 you need to download the coby gen 3 drivers and I would say use the cobyadb READ FIRST: Development Index and Root Utility after you do that then read my next post

 

[unasoto]

OK I've been talking to several people on the techknow.me forums and they believe that I could make the image I need if I had a factory image or an image from a working mid1045. If someone with a 1045 could use Uberizer and extract an image for me and post it then I could get my tablet working again this image is also the first step needed to start making ROM's like Cyanogenmod with the things I've learned from all of this and some help from some people (looks at vampirefo, and traveller1701, and several helpful people from techknow ) and guides from CyanogenMod | Android Community Rom based on Jelly Bean I might be able to port CM 9 and maybe even CM 10 well I can dream can't I also this image could be used to port Ubuntu and Debian to our tabs yeah now I'm really dreaming lol


Uberizer
Uberizer


Youtube Guide
[YOUTUBE] Uberoid Quick HowTo / Walkthrough by Twjordo


Suggested Procedure
twjordo's mk802II - a10 - Uberizer suggested procedure


PS
you need to be a registered user to get downloads from techknow.me

EDIT
sorry the image I need is run uberizer select i A1x Firmware Menu then 3 Dump A1x Firmware to \rom_dumps
after image is dumped you can just do o Open Uberizer directory

 

[asukaragnaboy]

How to get my mid 1045 to stock recovery? any help?

 

[asukaragnaboy]

Here is your system should install from any recovery.

1045_stock_rom_signed.zip

factory reset then install rom.

Sir, kindly help me with this zip files? how can I use this? what would be my procedure? thanks in advance

 

[asukaragnaboy]

Up for this thread

 

[asukaragnaboy]

Up for this thread, hope someone could help me revive my MID 1045 it's stucked on android logo

 

[thorius]

what is mid1045.ab? how did you make it.

Thanks for all your work on this device, Vampirefo. I have 2 new MID1045's and they're stuck at a blank screen after Coby logo. I started trying to install gapps following various sets of instructions. Forgive me... I'm a total no0b I have rooted many phones but these are my first two devices.

My current status is this: I've managed to flash your CW Recovery for the 1045. I then tried to flash the stock rom from kawboy76 but I'm still at the blank screen. I made sure to do factory reset on both before flashing. Both times, screen says update completed successfully, but nothing.

PLEASE help me. Is there a way out for me?? Promise I'll donate. Not a bribe.. just a token of thanks! Cheers.