Post Reply

[ROM]Adoli v1 | Monster M7 Tablet | Pre-Rooted | 4.1.1

OP kaiserII101

25th January 2014, 01:09 AM   |  #1  
kaiserII101's Avatar
OP Senior Member
Flag Groningen
Thanks Meter: 20
 
534 posts
Join Date:Joined: Jun 2008
More
Many thanks to all of the following. This small project would not be possible without their work/research.
Sergio Poverony
BSDgeek_Jake
raishiro
Koush
Garner
Basian Mile
rovo89
Prevailious
arctablet.com


This is a customized version of the most recent stock firmware (v4) for the Monster M7 tablet designed to make your tablet bloat free and easily rooted. Otherwise known as a custom ROM. The android version is 4.1.1.

In order to fully enjoy all the features of this ROM it needs to be flashed via some type of flashing tool through your computer, such as the Rk Batch Tool. Please see the instructions in the second post for setting up this tool properly.

Note that you can simply rename the .img file to update.img and flash it through your phone's recovery, but you'll be missing 3GB of storage in addition to having the manufacturer default allocation for app storage. Everything else should work correctly should you decide to use such a method.

Features:
  • Pre-Rooted (Koush SuperUser)
  • Very slim
  • xPosed framework
  • Modified Hosts file. Blocks large amount of advertising.
  • App storage increased to 3GB
  • All Monster bloatware removed.
  • DPI set at 160. (you can change this with an app.)
  • 4.4 E-mail and News&Weather Apps.
  • 4.2 Clock App.
  • Stock Browser with Adobe Flash 11
  • Added ArcTools for easy CWM installation.
  • ro.secure=0
  • ADB debug enabled by default.






Let me know if there are things you would like to see added. Higher android version at this point is beyond me, and I'm not even sure if it's possible as there is no source code yet available for this particular device. (Let me know if you somehow acquire source code for this device though )
Last edited by kaiserII101; 17th October 2014 at 04:59 AM.
The Following 9 Users Say Thank You to kaiserII101 For This Useful Post: [ View ]
25th January 2014, 01:09 AM   |  #2  
kaiserII101's Avatar
OP Senior Member
Flag Groningen
Thanks Meter: 20
 
534 posts
Join Date:Joined: Jun 2008
More
Instructions for setting up the RK Batch Tool and drivers. Thanks to sab99
  1. Shutdown the M7 tablet
  2. Run the RK Batch Tool, Open Device Manager
  3. Connect the USB cable to the PC, while pressing the volume down button on the side of the M7. You will see nothing on the screen, but at this point, Windows should be alerting you to a USB device insertion. At this point my Win 8.1 x64 box kept detecting the device and popping up a failed device message - the Win 7 x64 detected the device and left it as unknown (which is expected).
  4. Go into the device manager, find the unknown device, and update its driver with the Rk Batch Tool driver for your bitness and os.
  5. Now the RK Batch Tool should show green for your tablet.
  6. Load the ROM and press the Recover button.
  7. Have a beer while it flashes.
Last edited by kaiserII101; 28th January 2014 at 03:56 AM.
The Following User Says Thank You to kaiserII101 For This Useful Post: [ View ]
25th January 2014, 01:10 AM   |  #3  
kaiserII101's Avatar
OP Senior Member
Flag Groningen
Thanks Meter: 20
 
534 posts
Join Date:Joined: Jun 2008
More
reserved
The Following User Says Thank You to kaiserII101 For This Useful Post: [ View ]
25th January 2014, 01:10 AM   |  #4  
kaiserII101's Avatar
OP Senior Member
Flag Groningen
Thanks Meter: 20
 
534 posts
Join Date:Joined: Jun 2008
More
reserved
Last edited by kaiserII101; 25th January 2014 at 06:31 AM.
The Following User Says Thank You to kaiserII101 For This Useful Post: [ View ]
25th January 2014, 01:11 AM   |  #5  
kaiserII101's Avatar
OP Senior Member
Flag Groningen
Thanks Meter: 20
 
534 posts
Join Date:Joined: Jun 2008
More
reserved
Last edited by kaiserII101; 25th January 2014 at 06:32 AM.
The Following User Says Thank You to kaiserII101 For This Useful Post: [ View ]
25th January 2014, 07:27 AM   |  #6  
kaiserII101's Avatar
OP Senior Member
Flag Groningen
Thanks Meter: 20
 
534 posts
Join Date:Joined: Jun 2008
More
Open.
25th January 2014, 10:50 PM   |  #7  
Recognized Developer
Flag Boston, MA
Thanks Meter: 426
 
1,493 posts
Join Date:Joined: Nov 2009
Donate to Me
More
Could you please provide a correct drivers for Monster M7? Drivers from Rk Batch Tool you've provided are not working. I've tried on Win8/Win7, 32/64, driver can't start and always shows error 10. I also tried to install on the "Android-free" PC (Win7, 32), no android usb drivers are previously installed - no luck.

P.S. And of course I've tried different USB ports and cables (what is really stupid 'cause my Nexus 7 2013 and all WinPhones are using these cables without problems)
Last edited by sensboston; 25th January 2014 at 10:52 PM.
26th January 2014, 03:13 PM   |  #8  
Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Jun 2008
Quote:
Originally Posted by sensboston

Could you please provide a correct drivers for Monster M7? Drivers from Rk Batch Tool you've provided are not working. I've tried on Win8/Win7, 32/64, driver can't start and always shows error 10. I also tried to install on the "Android-free" PC (Win7, 32), no android usb drivers are previously installed - no luck.

I had an issue with my Windows 8.1 x64 machine, but it worked on a Win 7 x64 machine. The steps to use the RK Batch tool with the M7 are:
  1. Shutdown the M7 tablet
  2. Run the RK Batch Tool, Open Device Manager
  3. Connect the USB cable to the PC, while pressing the volume down button on the side of the M7. You will see nothing on the screen, but at this point, Windows should be alerting you to a USB device insertion. At this point my Win 8.1 x64 box kept detecting the device and popping up a failed device message - the Win 7 x64 detected the device and left it as unknown (which is expected).
  4. Go into the device manager, find the unknown device, and update its driver with the Rk Batch Tool driver for your bitness and os.
  5. Now the RK Batch Tool should show green for your tablet.
  6. Load the ROM and press the Recover button.
  7. Have a beer while it flashes.

Thanks for the cleanups on this ROM, kaiserII101. 3GB, no crapware, and all source code is the way everything should be shipped. At least you fixed 2 of the 3. When you start looking at these 'value' tablets they are all pretty much the same. If you REALLY wanted to sell a ton of your hardware, releasing the source would encourage the modding community here and be worth more advertising dollars than your razor thin margins could ever support.
26th January 2014, 03:48 PM   |  #9  
Recognized Developer
Flag Boston, MA
Thanks Meter: 426
 
1,493 posts
Join Date:Joined: Nov 2009
Donate to Me
More
sab99, thanks for the help but yesterday I figured out by myself (it costs me a few hours of sleep but fortunately it's a weekend )

But definitely TS should add your instructions to the first post! Also, #3 is very important - it's absolutely unclear from TS post and another discussion (someone referred to the bootloader mode as a "flashing mode" that is confusing).

Also, using topic starter's image and RK29xxImageTools, I've increased userdata (internal memory) up to 8GB. Here is parameters for partitioning (I also attached my parameter file):
Code:
CMDLINE: console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x00004000@0x00004000(kernel),0x00008000@0x00008000(boot),0x00008000@0x00010000(recovery),0x00020000@0x00018000(backup),0x00100000@0x00038000(cache),0x01000000@0x00138000(userdata),0x00002000@0x01138000(kpanic),0x00500000@0x0113A000(system),-@0x0163A000(user)
I'm curious: is it possible to completely get rid of "user" (aka "internal sdcard") partition? This "monster" works perfectly with 32GB microsd, so we don't need to waste important nand space...
Also, could we change mtdparts order, to simplify calculations? I mean something like this (showing just the end of CMDLINE string):
Code:
... 0x00100000@0x00038000(cache),0x00002000@0x00138000(kpanic),0x00500000@0x0013A000(system),-@0x0063A000(userdata)
I can't try now: my daughter (3.5 yo) just grabbed the tablet and started installing and reinstalling her favorite games (actually, I've bought this "monster" 'cause her old Gtab 7'' just broke - probably, LCD screen connection problem - but I can't fix it, need a special screwdriver to disassemble. BTW, this Galaxy Tab is a great product - very old but still working).

sab99, could you try "user"-less partitioning (i.e. without "internal sdcard")? Actually it will be great, and this option (if works of course) will significantly improve tablet value.

P.S. Seems like to be able to do this, we also need to comment that line in \system\etc\vold.fstab and repack system.img. Probably, TS can help us...
Code:
## Vold 2.0 Generic fstab
## - San Mehat (san@android.com)
## 

#######################
## 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
######################

## Example of a standard sdcard mount for the emulator / Dream
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
### dev_mount flash /mnt/sdcard auto /dev/block/mtd/by-name/user                                         <-- we need to comment this line (in case we don't want to have "internal sdcard"
dev_mount sdcard /mnt/external_sd auto /devices/platform/rk29_sdmmc.0/mmc_host/mmc0
dev_mount udisk /mnt/usb_storage auto /devices/platform/usb20_otg/usb1 
## Example of a dual card setup
# dev_mount left_sdcard  /sdcard1  auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# dev_mount right_sdcard /sdcard2  auto /devices/platform/goldfish_mmc.1 /devices/platform/msm_sdcc.3/mmc_host/mmc1

## Example of specifying a specific partition for mounts
# dev_mount sdcard /sdcard 2 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
Attached Files
File Type: txt parameter.txt - [Click for QR Code] (587 Bytes, 57 views)
Last edited by sensboston; 26th January 2014 at 11:08 PM.
The Following 2 Users Say Thank You to sensboston For This Useful Post: [ View ]
28th January 2014, 04:09 AM   |  #10  
kaiserII101's Avatar
OP Senior Member
Flag Groningen
Thanks Meter: 20
 
534 posts
Join Date:Joined: Jun 2008
More
Added the instructions for setting up the RK Batch Tool in the second post.

Possible bug with velvet.apk (search) force quitting.. May need to revert to an older version as soon as I can start building again.

As far as eliminating the user partition, I would say, yes it is probably possible. Personally though, I'm not sure I want to do that. Will certainly try experimenting with it though.

Also, please everyone feel free to take the ROM, modify it, and post a link to your modified version (preferably list the changes you made). In order to modify update.img contents easily and repack them into flashable form you can use Sergio Poverony's tools. http://forum.xda-developers.com/show....php?t=2445406


I will be travelling to Russia wednesday for 5 months, and so I probably will be out of action here for a week at least I imagine. I will have internet access there eventually, as I'll be getting a sim-card, but important thing is to get settled in there first.

The Following 2 Users Say Thank You to kaiserII101 For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Miscellaneous Android Development by ThreadRank