Database Info

[AOSP] 4.1.1 JellyBean for Herotab C8

DISCLAIMER I (or any contributor) cannot be held responible in any way for any sort of damage caused for using this ROM or its derivatives.
This is the AOSP-based Android 4.1.1 Jellybean ROM using custom kernel 3.0 for Herotab C8/Dropad A8/Haipad M7/iBall Slide and compatible tablets.
The Herotab C8 and its siblings are one hackable device; It supports Android 2.2, 2.3, 3.0, 3.2, 4.0, and 4.1. It runs on a single-core Samsung S5PV210 1Ghz Processor and 512mb RAM. Pretty low spec, however with the right tinkering it can be one powerful device.
What works:
Display
Hardware acceleration
Touchscreen (thanks violet's ft506 driver and przemo27 for figuring the alternate data format)
Audio\Microphone (thanks to Asure's CM7 build for audio HAL; and mg3100's details on kernel)
Wi-Fi (thanks to violet's ar6000 driver and jolocotroco for locating source for a wpa_supplicant8 dependency)
Bluetooth
Accelerometer (thanks to Asure's port of mango210 kernel)
Battery Indicator
USB Host
USB OTG
Camera
Market, GoogleApps
Root
What does not work:
HDMI
3G dongle
(NOTE This list is not exhaustive; this build is still a Beta and not intended to be a daily driver)
Steps for flashing (using script; this will make 512MB system, 256MB cache and 1GB data partition and erase your existing settings and apps):
Extract the archive. You will get two files, one will be a GZipped tar (.tgz) and other the kernel (zImage). Copy these to the root of an external SD.
Download the attachment posted here and extract them to the root of the external SD. You should now see 6 files in the root of the external SD. (utscript, utscript_sd, utscript.sh, zImage.debug, zImage, rootfs.tgz).
Insert the SD card and boot your tablet using Menu+Power. This will flash your tablet.
Steps for flashing (using custom recovery):
Extract the archive. You will get two files, one will be a GZipped tar (.tgz) and other the kernel (zImage). Copy these into a folder (path muwst have no spaces) in your external SD card.
Boot into custom recovery.
Go to "Advanced", then "Partition SD card". Select partition sizes (make sure system partition > 320MB) and wait for it to format the partitions. Existing settings and apps will be lost.
[You can skip this step if your tab's system partition is > 320 MB]
Now return to the main menu, and select "Flash ROM". Give it the path where you stored the ROM in step 1. Wait for it to flash the ROM.
Return to main menu and select "Shutdown".
Turn on your tablet normally, and enjoy!
Links:
http://www.embedupload.com/?d=85OERSGVNV (Embedupload)
NOTE: I didn't make this ROM. The guys over at slatedroid did it, so credits all go to them. But you can thank me for sharing

Custom recovery for herotab c8
DISCLAIMER. Use this at your own risk. I will not be responsible for any damage\brick caused by using this recovery.
Currently this is a Beta and all functionality has not been thoroughly tested.
This is a custom recovery modeled on CWM recovery (built on the custom kernel based on Urbetter's source) for Herotab C8/Dropad A8/Haipad M7/iBall Slide i7011/Coby 7024 and equivalent tablets. It should also work on Coby 8024/1024 tablets.
The recovery is built to be compatible (as much as possible) with existing firmwares (stock as well as custom) and patches (again stock as well as those found in custom ROMs). The reason you might want to use this recovery to flash is that:
Its safer (bootloader, etc. are not touched so greatly reduced probability of bricking)
It does not erase your data partition (so Apps and Settings are carried over)
It maintains your existing partition layout (you can change if wanted)
In order to try this recovery,
Download BootExtRecovery.zip attached to this post.
Download the recovery zip from the GitHub link below
Extract both zip files to the root of an external SD card.
Boot your tablet using Menu+Power
This will boot the recovery externally (i.e. unless you actually do something using the recovery, your tablet will be completely unmodified). After the recovery boots and menus work, you may flash the recovery into your tablet (using "Partitions and Storage" menu). Flashed this way, the recovery can be booted into whenever both your SD cards don't have a "utscript" file (otherwise the script is executed instead of starting recovery).
Download: https://github.com/namko/midRecovery/downloads
Source: https://github.com/namko/midRecovery
Key assignments:
Herotab C8/Dropad A8/Haipad M7/iBall Slide -- HOME to select, MENU/BACK to scroll
Coby 7024 -- HOME to select, POWER to scroll
Function list:
Flash ROM - Flashes the ROM on SD card (external or internal) located in a specific folder.
This does not erase 'data' partition. If you downgrade Android, make sure to erase the 'data' partition (or at least erase dalvik-cache from advanced menu) for maximum compatibility.
This does not repartition the internal SD, so if you want a different layout, make sure to change before flashing.
This flashes only the kernel (no other partition e.g. logo, recovery, boot arguments, boot loader)
Apply patch/update - Prompts you to select a patch/update to apply.
Wipe data/factory reset - Erases the 'data' partition. This is equivalent to doing a factory reset.
Wipe cache - Erases the 'cache' partition.
Backup/Restore - Create a new backup (system = firmware, data = your settings/apps) or restore a previously created backup. Essentially this is a NANDROID backup.
Partitions/Storage - To backup or flash individual partitions (e.g. logo, kernel, recovery, boot arguments, bootloader, etc.)
Advanced - To repartition the internal SD card, erase Dalvik-cache, view log, etc.
You can flash ROM (or apply updates) from .ZIP files as well; but it doesn't support the "standard" format because they sometimes contain executables that must be executed to properly apply the patch.

Fixes and patches
Kernel fix (just update it via recovery -> apply patch/update -> update kernel):
http://www.4shared.com/zip/M_ZcGiSF/zImage.html
Wifi Patch:
http://www.4shared.com/zip/3T9hUxnt/wifipatch.html
Here's a patch implementing changes suggested by jolocotroco. To apply this patch:
Extract the zip into your external SD card (anywhere)
Boot into recovery
Select "Apply patch/update"
Select the extracted file ("wifi.patch.tgz")
Reboot after applying patch
It is also possible to apply the patch using adb. Remember to stop WiFi first. This will apply the patch and reboot your device.
adb push wifi.patch.tgz /mnt/sdcard
adb shell
su
mount -o rw,remount /
mount -o rw,remount /system
stop wpa_supplicant
stop hostapd
tar xvf /mnt/sdcard/wifi.patch.tgz -C /
reboot
Click to expand...
Click to collapse

bump

don't work
no one of this patch is recognized by the recovery...
also the kernel update is not a tgz file...
maybe i did a mistake?

j.valeron said:
no one of this patch is recognized by the recovery...
also the kernel update is not a tgz file...
maybe i did a mistake?
Click to expand...
Click to collapse
It should work, what steps did you took to install the kernel?

Custom Recovery for C8/A8/M7
I nearly forgot this. Sorry.
DISCLAIMER. Use this at your own risk. I will not be responsible for any damage\brick caused by using this recovery.
Currently this is a Beta and all functionality has not been thoroughly tested.
This is a custom recovery modeled on CWM recovery (built on the custom kernel based on Urbetter's source) for Herotab C8/Dropad A8/Haipad M7/iBall Slide i7011/Coby 7024 and equivalent tablets. It should also work on Coby 8024/1024 tablets.
The recovery is built to be compatible (as much as possible) with existing firmwares (stock as well as custom) and patches (again stock as well as those found in custom ROMs). The reason you might want to use this recovery to flash is that:
Its safer (bootloader, etc. are not touched so greatly reduced probability of bricking)
It does not erase your data partition (so Apps and Settings are carried over)
It maintains your existing partition layout (you can change if wanted)
In order to try this recovery,
Download BootExtRecovery.zip attached to this post.
Download the recovery zip from the GitHub link below
Extract both zip files to the root of an external SD card.
Boot your tablet using Menu+Power
This will boot the recovery externally (i.e. unless you actually do something using the recovery, your tablet will be completely unmodified). After the recovery boots and menus work, you may flash the recovery into your tablet (using "Partitions and Storage" menu). Flashed this way, the recovery can be booted into whenever both your SD cards don't have a "utscript" file (otherwise the script is executed instead of starting recovery).
Click to expand...
Click to collapse
Github:
https://github.com/namko/midRecovery/downloads
BootExtRecovery:
http://www.4shared.com/zip/HxPitG3B/BootExtRecovery.html

mid recovery is not working on 8024
the recovery is not working on 8024, i have just a black screen...
please help
Sorry it is working...

Now we have Jelly Bean 4.2 form SlateDroid
Please refer for the following hyperlink
http://www.slatedroid.com/topic/42771-romcm101android-421-build-1/
[WORKING]
- Audio
- Video
- Wifi
- Touchscreen
- Most regular things
[NOT WORKING]
- Bluetooth
- 3G

awesome will try it on my dropad A8 its a shame hdmi is not working

[Q] Painted myself into a corner...

I made a mistake by trying to get through the rooting/rom-ing process in a hurry. The result is that i'm stuck on cm boot logo.
1. I installed cwm 5.5.0.4 custom recovery through this guide.
2. Made a nandroid and copied it to pc, sd card, external sd card.
3. Flashed cm-10.1-noname>gapps>tablet ui>wipe cache>wipe dalvik>reboot. (source, version:cm-10.1-20130827-UNOFFICIAL-tf101.zip )
4. Stuck on boot screen.
I'm guessing I should have used twrp rather than cwm.
The trouble is that cwm 5.5.0.4 seemingly doesnt have external sd card support, and having tried to flash cm, it means that the stock nandroid i made probably got moved elsewhere as no backups are found when i try to recover.
Is there a way out of this mess?

Ah, you are not totally painted into a corner. Just climb up the wall and across the ceiling!
There are 2 ways out: ADB or APX.
To use ADB, whilst booted to CWM, connect your USB cord to your computer. Update using the Naked Drivers 0.72 for the unknown device, or ADB device. It will probably show an MTP device as well, leave that alone.
Once you think you have the driver working, you will need ADB. I have a copy of the files in my dropbox so you don't need the whole android SDK.
https://dl.dropboxusercontent.com/u/34321735/adb.zip
Unzip them to the c:\adb folder.
Command prompt and run the following:
Code:
c:
cd c:\adb
adb devices
You should see a device followed by RECOVERY.
Once this is working, find the file you want to move to the tablet to flash (I would recommend TWRP 2.6.3.9 unless you plan on flashing Android Revolution HD) and move this file to c:\adb. I will call it flash.zip for the purposes of this.
Next, go back to your command prompt and type the following:
Code:
adb push flash.zip /sdcard/
Once this is completed you should see the flash.zip on the tablet in CWM so you can install it.
If you do install TWRP, be sure to do a NORMAL reboot (even if it is to a bootlooped OS) so the installation completes. Once you get to the ROM boot screen (pas the Eee Pad logo screens) you can boot back to recovery.
Method 2 - APX
I have a guide for using APX and EasyFlasher here: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
You can either use one of my repacked versions (linked in that thread) to install TWRP (has not been updated for the latest TWRP yet, but it is only a few versions old). If you want the latest, put it on a microSD and flash it after updating to the Easyflasher version.
Or you can download the stock ROM from the Asus Support site, place the .zip file as is in the asusupdate folder within EasyFlasher folder structure and then click the unbrick option.

Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)

jbonetwo said:
Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)
Click to expand...
Click to collapse
If you are going to venture into the JellyBean 4.2/4.3 ROMs, I would HIGHLY recommend using TWRP. It is by far superior to CWM, and no one is supporting CWM for the TF101 as far as I know. 4.2 introduced a new file structure for multi-users and updates do not flash properly if using an older recovery. You end up with your /sdcard/ folder in the /sdcard/0/ (and an additional 0 for each new ROM update flashed).
TWRP is far more intuitive IMO (all wipes are in one simple menu), and @sidneyk has added (in addition to internal and microSD support) dock USB and SD card support. TWRP has a terminal emulator and lots of other nice features over CWM.

Well thats got me puzzled.
Installed TWRP 2.6.3.0 using APX.method
Reflashed cm-10.1-20130721-UNOFFICIAL-tf101.zip >
gapps_4.2.2_CM10.1_TF101_20130324_stock_camera >
cm-10.1-20130721-UNOFFICIAL-tf101-tabletUIpatch >
wipe cache/dalvik >
reboot
And I'm still stuck on cm loading screen. Unless it takes more than 10 minutes for first boot I'm stumped...
P.S. Any way of reusing the CWM made stock nandroid with TWRP?
P.P.S. You're right TWRP is MUCH better. Gonna convert all of my devices for sure.

solved!
flashed cm then rebooted - worked!
flashed cm and gapps then rebooted - still works!
flashed cm>gapps>tablet ui - still working!
all with wiped cache/dalvik
apparently it doesnt like all of them being flashed at the same time for first installs :S

[Guide][Devs] Dual Boot Android Roms

- Dual booting is the process through which you can switch between any two or more roms without the need of wiping data or making backups before flashing, all you need to do is switch between the roms, meanwhile all the apps you've installed remain intact in their specific rom.
Click to expand...
Click to collapse
Strictly put forth by Developers for Developers! If you are inexperienced with Android Development then proceed forward with extreme caution! As for the experienced, this will be easy for you.
***DISCLAMER***
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. YOU are choosing to make these modifications!
Click to expand...
Click to collapse
As always, do anything at your own risk. The above warning/disclaimer is only there because unfortuantely there will be someone who messes this up. The following guide will be conducted straight from the phone so if you are more comfortable using a computer then you will need to adapt this guide to your prefered surroundings. Please insure you have multiple ways to go about restoring your device in case you failed to follow the instructions or misunderstood something within the instructions - A Nandroid Backup, and/or RUU, and/or a ROM fitted for your specific device which you can apply via adb sideload.
Credit goes to @dreccon for bringing this to my attention with a more clear understanding over at his thread,
[GUIDELINES]Dual-Boot on (theoretically) any Android device. He was very helpful to opening my mind and thus putting up this thread. This thread is initially based around working with K2 Variant devices, but I am also aware that this will work on many other devices too.
The following numbers I will be using for partitioning the SD Card is based on maximum used space from a Stock Rom of my own K2_CL device using 4.1.2 Jelly Bean! These numbers are not to be taken literally, so USE COMMON SENSE, and insure you know the sizes for your System, Data, and Cache Partitions!
To determine the proper sizes of your partitions you can use the apk called, Partition Table, mentioned for requirements below. That APK is literally self explanatory so I will not be going over it. You will use this APK to determine the size of each partition and its current format. Do this and take note of them.
The Secondary Rom should be equal to or greater than the Primary Rom OS.
Requirements:
Device SPECIFIC boot.img and custom recovery.img
A text editor of the sorts - I use Quoda Code Editor
A Class 6 or better SDCard (I am talking about the external)
Partition Table from the Play Store
Working roms for your device
A compression tool (I use ZArchiver from the Play Store)
AParted (SD Card Partition) from the Play Store
Steps:
A. PARTITIONING YOUR SD CARD:
Plug your memory card (SD Card) in to your computer using either a card reader or by plugging your device in via usb, and copy everything from it over to your PC as we are going to partition your SD Card (which means it WILL be wiped out). Be sure to unmount your device from your pc if plugged in via usb or any other known method.
Unmount your SD Card on your device by going to, settings > storage > unmount sdcard,on your phone and then proceed to open up the apk, AParted.
Grant root access when prompted. Decline the "Agreement" because it will just try to install junk. Tap configuration, then tap the drop box under Detected devices. You should see mmcblk0, mmcblk1, and usbdisk. If you don't have both "mmcblk0", & "mmcblk1", then stop here, because either something is wrong on your end or this guide isnt for you. If you do, then select mmcblk1 from the list, tap Save, then OK. Tap TOOLS, you should now see parts 1 through 4. "Part: 1" should say fat32, and say the size in MB of your external SD card. If it does, then tap the checkbox next to "Part: 1", next tap the drop box that says Create, select Delete and tap apply. Once done, all parts should say empty. We're going to create 4 partitions. The first partition is going to be the standard external sd partition that will show up in both roms. Tap Create on the top, tap "+", tap the box with "0MB" in it, set it to the size you want the card to be, keeping in mind, that we need space for the second ROMs' partitions. Repeat these steps for System, Data, and Cache as seen below and once completed you will tap the menu button, and tap Apply changes, when done we are finished with the partition setup.
Partition it as followed:
First Partition-FAT32 (total memory card size - I recommend at least 20mb or more depending upon the actual size of your SD Card as a whole) <----- SD CARD
This is the space you will see as your memory card (external sd) in both of your roms (Primary and Secondary).
Second Partition-EXT4 (1339mb) <------ SYSTEM
This will be the System Partition of your Secondary Rom
Third Partition-EXT4 (1165mb) <----- DATA
This is Data Partition of your Secondary Rom, apps will go here
Fourth Partition-EXT4 (220mb) <----- CACHE
You can reduce it a bit more if you want to.
B. PREPARING SECONDARY ROM'S ZIP:
Get the updater-script of the rom you want to dual boot and open it up using Quoda as mentioned in the requirements or with anything else similar to a text editor which won't disrupt the unix coding of that file when you save it later.
SEARCH FOR-mmcblk0p35 (may vary for different devices, look for "mount("ext4", "EMMC", "/dev/block/mmcblk0p35");" in the updater script in order to know what yours is)
Replace with-mmcblk1p2
Save it and move it back to its location in the rom zip (META-INF\com\google\android).
Note: if there is a data folder in the rom's zip then you also have to replace the data partition block with mmcblk1p3, like: mmcblk0p37-->mmcblk1p3
C. PREPARING SECONDARY ROM'S BOOT.IMG:
Unpack the boot.img of the rom you want to dual boot using the proper unpacking and packing binaries. This can be done using your PC and/or phone. There is also the dsixda Kitchen via Windows using Cygwin and/or Linux. However, my guide will be based on doing this directly from my phone so for those who qualify may use this thread - Unpack, Edit, Repack Boot.img/Recovery.img. Otherwise, you will need to approach this differently.
You will need to go through all files which are feasible to view and read within the ramdisk of your boot.img.
Then find and replace:
Find-[email protected]
Replace with-/dev/block/mmcblk1p2
Find-[email protected]
Replace with-/dev/block/mmcblk1p3
Find-[email protected]
Replace with-/dev/block/mmcblk1p4
Save all the files that have had these changes made to them and then repack the ramdisk with the kernel to your new dualboot.img.
D. PREPARING SECONDARY ROM'S RECOVERY (OPTIONAL IF YOU DON'T WANT TO CHANGE THE SECONDARY ROM AGAIN):
Unpack the recovery.img like you unpacked your boot.img and open '/etc/recovery.fstab'.
Edit from this (May vary with other devices):
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p20
/cache ext4 [COLOR="darkred"]/dev/block/mmcblk0p36[/COLOR]
/data ext4 [COLOR="darkred"]/dev/block/mmcblk0p37[/COLOR]
/devlog ext4 /dev/block/mmcblk0p25
/misc emmc /dev/block/mmcblk0p22
/int_sd vfat /dev/block/mmcblk0p38
/recovery emmc /dev/block/mmcblk0p21
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 [COLOR="darkred"]/dev/block/mmcblk0p35[/COLOR]
to this
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p20
/cache ext4 [COLOR="red"]/dev/block/mmcblk1p4[/COLOR]
/data ext4 [COLOR="red"]/dev/block/mmcblk1p3[/COLOR]
/devlog ext4 /dev/block/mmcblk0p25
/misc emmc /dev/block/mmcblk0p22
/int_sd vfat /dev/block/mmcblk0p38
/recovery emmc /dev/block/mmcblk0p21
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 [COLOR="red"]/dev/block/mmcblk1p2[/COLOR]
Save the file and repack the modified ramdisk with the kernel as dualrecovery.img.
E. MAKING THE UPDATE.ZIP FOR YOUR BOOT.IMG:
By now, you should have your edited boot.img (dualboot.img) and your edited updater-script. Just place both of them within the Secondary rom zip and you are now good to go to flash and/or share to others (but you better test it prior to sharing it!).
F. FLASHING/SWITCHING ROMS:
Just reboot to your recovery and flash the Secondary rom and after that flash your dualboot.img, unless you have already added it to the rom zip then you wont be required to flash the dualboot.img unless you are S-On.
To Switch between Roms just reboot to your recovery and flash your Boot for primary rom and DualBoot for secondary rom.
NOTE: you can literally flash just your stock boot.img and your primary stock rom will appear as if nothing ever happened.
Sent from my C525c using Tapatalk

Quick question. While I appreciate the tutorial greatly... wouldnt it be safer to use a recovery like SafeStrap?
What would the benefits be of using thia method over SS?
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF

This is currently built with the K2 variant devices kept in mind. I will not guarantee anyone else who does not own a K2 variant that this will work. If you do not own a K2 variant and this does work, please, comment on this thread to let myself and other viewers know. Please specify your device and Rom. However, if you read my first post and everything you saw is fitting to your device and roms, then it is VERY LIKELY that this WILL work for you - Thanks.
To automatically generate your boot.img and/or rom zip to be 'dual bootable' you must download the DualBoot_v1.0 zip at the end of this post and extract it to the root of your internal sdcard. This will save you the hassle of manually unpacking, editing, and repacking the boot.img and as well as extracting, editing, and pushing back the updater-script originally from your rom zip. This process is really fast at accomplishing its goals while doing all the work for you .
The ZipEditor.sh will use my three binaries to edit your boot.img and while doing so, it will create a temporary repack.sh file to allow it to be properly rebuilt again. It will also create a backup of your original boot.img which will be named boot1.img. The dual boot.img will be named boot2.img.
This script is literally built around my three executable binaries - unmkbootimg, mkbootfs, and mkbootimg.
Of course, in order to use the scripts, you need to have had partitioned your SD card the way I described in the first post.
Initial Setup
First of all download the zip at the end of this post, unzip it and copy the DualBoot folder to the root of your SD card.
Install Script Manager from Play Store
How to use
A. ZipEditor.sh
Download the ROM you want to install and copy the zip into /sdcard/DualBoot/OriginalZIPs
Also download a suitable GAPPS.zip and copy it to the same directory (if this applies to you)
If you need to convert additional zips, the tool is designed to process as many as it finds in this directory
Open Script Manager, browse to /sdcard/DualBoot and tap on ZipEditor.sh
In the next screen, select the first two icons on top (Favorite and SU) and then select, Run.
The tool will give you some info about your device. Check them and if they are not right, then kill the script. If they are correct, press Enter to continue. The Editor will process the zips one by one. Everytime a zip is completed, it will prompt you to press Enter.
When all zips are processed you may reboot to recovery, make a backup of your current ROM and flash them.
When you reboot, your secondary ROM will load.
B. SwitchROM.sh
The name is self-explanatory. This tool can only function if it finds the files boot1.img and boot2.img inside the /sdcard/DualBoot/img folder.
These files will be automatically generated when you convert a ROM zip in the ZipEditor. Alternatively, if you know what you are doing, you can create and put them there yourself.
Tap it in Script Manager and again select the first two icons (Favorite and SU) and Run. It will automatically detect the current ROM, flash the boot.img of the other one and prompt you to reboot. Use your Power-Menu and reboot your device. Your device will now boot to the other ROM.
So, for now, you can automatically convert zips for installation to the external partitions with ZipEditor and you can switch between your two ROMs using SwitchROM. You will notice that your normal recovery cannot backup, restore, factory-reset or wipe your secondary ROM. Therefore, @dreccon is currently working on his next project to upload another script that will function as a full fledged Recovery for the secondary ROM, so stay tuned... Meanwhile, you will be required to edit your custom recovery image manually as described in the first post. This will allow you to flash to your secondary rom. For example, the ability to flash and root your secondary rom if it happens to not be rooted.
Click to expand...
Click to collapse
Credits for the ZipEditor.sh and SwitchROM.sh goes to @dreccon
Credits for the executable binaries goes to @Modding.MyMind - That's me

kevp75 said:
Quick question. While I appreciate the tutorial greatly... wouldnt it be safer to use a recovery like SafeStrap?
What would the benefits be of using thia method over SS?
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Click to expand...
Click to collapse
Simple, using your sd card prevents hard bricks and or changes to your actual partitions. This prevents the user from screwing up their device, while also, this prevents malicious roms that have been improperly built to be prevented from destroying the users devices which is really helpful for those who are flashaholics and messing around with nightlies. In addition, when all is said and done, all they need to do is put back their primary Rom boot.img and they will have back their primary (or stock) Rom again as if nothing ever happened.
Buying an sd card are a dime a dozen (cell phones are not)
Sent from my C525c using Tapatalk

Oh... I dont think its a bad idea... but the could be done by creating multipe rom slots with SafeStrap.
I'm really just wondering what the benefit would be chooaing this route over another.
I for one think its a great tutorial and is definately a handy way to do it... not so keen on the sd card usage tho... just due to varying speed issues and googles words on write issues to it...
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF

kevp75 said:
Oh... I dont think its a bad idea... but the could be done by creating multipe rom slots with SafeStrap.
I'm really just wondering what the benefit would be chooaing this route over another.
I for one think its a great tutorial and is definately a handy way to do it... not so keen on the sd card usage tho... just due to varying speed issues and googles words on write issues to it...
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Click to expand...
Click to collapse
Aren't any issues. You are formating the sdcard to the same format as your system, data, and cache partitions. That would be ext4. With that said, I have done this on a 2gig sdcard using a deodex Rom and it ran faster and smoother than from the actual device itself. Even the first boot time of the deodex Rom was cut down dramatically.
Sent from my C525c using Tapatalk

NICE. Gotta be a class 10 card and the ext4 filesystem.
I would imagine with a slower card it would slow down... tho.
Very cool and great info.... thanks bud!
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF

kevp75 said:
NICE. Gotta be a class 10 card and the ext4 filesystem.
I would imagine with a slower card it would slow down... tho.
Very cool and great info.... thanks bud!
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Click to expand...
Click to collapse
Over time it may slow down some, but that would only be due to its available memory filling up which you can only imagine with a 2gig to have but only so much available space when you format it. Now, if you have like a 16 or 32 gig or something close to it, then you would be set . You could even go as far as using any extra space as a swap for more ram .
Sent from my C525c using Tapatalk

kevp75 said:
Oh... I dont think its a bad idea... but the could be done by creating multipe rom slots with SafeStrap.
Click to expand...
Click to collapse
I also failed to mention, that if you use some general common sense you can use the guidelines provided in this thread, and create additional space on the sdcard for more roms
So, instead of dual booting, you could technically have three, four, or even 5 depending on the sdcard and what your device can handle. Not to mention, it doesn't take up space on your device. It is just a matter of swapping out your sdcard which can be handy.
Sent from my C525c using Tapatalk

awesome... i'm going to bookmark this so when i can get a spare device I can give it a whirl =)
hopefully my daughter gets sick of her cracked glass s3 soon and i'll be able to do this on that HA!
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF

kevp75 said:
awesome... i'm going to bookmark this so when i can get a spare device I can give it a whirl =)
hopefully my daughter gets sick of her cracked glass s3 soon and i'll be able to do this on that HA!
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Click to expand...
Click to collapse
Sounds good, and remember to not flash anything to your secondary Rom with your custom recovery. It must be done with your dualrecovery. This is only optional for those who plan to keep their secondary Rom.
Sent from my C525c using Tapatalk

gotcha. Thanks for this.
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF

Nicely written guide. Well done!
One alternative to constantly flashing the boot.img is to flash the secondary one into the recovery partition and then install bootstrap recoveries to both systems. This way, each ROM would have its own recovery and you would switch ROMs by key combination at bootup.

dreccon said:
Nicely written guide. Well done!
One alternative to constantly flashing the boot.img is to flash the secondary one into the recovery partition and then install bootstrap recoveries to both systems. This way, each ROM would have its own recovery and you would switch ROMs by key combination at bootup.
Click to expand...
Click to collapse
Would do this, but as my knowledge goes, we (meaning our K2 variants) currently do not have bootstrap support at this time, but if you know how to help in that matter, please pm me
Sent from my C525c using Tapatalk

Modding.MyMind said:
Would do this, but as my knowledge goes, we (meaning our K2 variants) currently do not have bootstrap support at this time, but if you know how to help in that matter, please pm me
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I haven't tried it. It's just an idea but I'm sure it works. As for building a bootstrap recovery, no I don't know how it's done. I was hoping you already had one.
Sent from the 3rd dimension!

dreccon said:
I haven't tried it. It's just an idea but I'm sure it works. As for building a bootstrap recovery, no I don't know how it's done. I was hoping you already had one.
Sent from the 3rd dimension!
Click to expand...
Click to collapse
I'm confident it would work. I may need to work on bringing it over to us. Will see if I can find time for that though.

Hey guys, a script is in the mix for automating all of what I described within the OP. It will save you the trouble of editing the boot.img, updater-script, and so forth. Some changes need to be made, but I cannot take credit for this. It all goes to dreccon. He is the one writing it out, and I am testing it to insure its integrity. When it is ready, I will be posting it in the third post giving full detailed instructions on how to set it up and use it.
Edit: However, you will still be responsible for formatting the sdcard yourself.
Sent from my C525c using Tapatalk

Third post has been updated. You can now use the available attachment in the third post to automatically generate your dual Rom/dual boot.img. So for those who read my guide in the first post that are scratching their heads... You don't need to anymore lol. All that is required from you is to format your sdcard.
Sent from my C525c using Tapatalk

Hey guys, I will be reconstructing the instructions for post three. Nothing to be concerned about for any of you reading this. Just to keep in accordance with a simple request out of respect and to hold true with the XDA rules.
-- Happy Hunting!!
Sent from my C525c using Tapatalk

Modding.MyMind said:
This is currently built with the K2 variant devices kept in mind. I will not guarantee anyone else who does not own a K2 variant that this will work. If you do not own a K2 variant and this does work, please, comment on this thread to let myself and other viewers know. Please specify your device and Rom. However, if you read my first post and everything you saw is fitting to your device and roms, then it is VERY LIKELY that this WILL work for you - Thanks.
To automatically generate your boot.img and/or rom zip to be 'dual bootable' you must download the DualBoot_v1.0 zip at the end of this post and extract it to the root of your internal sdcard. This will save you the hassle of manually unpacking, editing, and repacking the boot.img and as well as extracting, editing, and pushing back the updater-script originally from your rom zip. This process is really fast at accomplishing its goals while doing all the work for you .
The ZipEditor.sh will use my three binaries to edit your boot.img and while doing so, it will create a temporary repack.sh file to allow it to be properly rebuilt again. It will also create a backup of your original boot.img which will be named boot1.img. The dual boot.img will be named boot2.img.
This script is literally built around my three executable binaries - unmkbootimg, mkbootfs, and mkbootimg.
Of course, in order to use the scripts, you need to have had partitioned your SD card the way I described in the first post.
Initial Setup
First of all download the zip at the end of this post, unzip it and copy the DualBoot folder to the root of your SD card.
Install Script Manager from Play Store
How to use
A. ZipEditor.sh
Download the ROM you want to install and copy the zip into /sdcard/DualBoot/OriginalZIPs
Also download a suitable GAPPS.zip and copy it to the same directory (if this applies to you)
If you need to convert additional zips, the tool is designed to process as many as it finds in this directory
Open Script Manager, browse to /sdcard/DualBoot and tap on ZipEditor.sh
In the next screen, select the first two icons on top (Favorite and SU) and then select, Run.
The tool will give you some info about your device. Check them and if they are not right, then kill the script. If they are correct, press Enter to continue. The Editor will process the zips one by one. Everytime a zip is completed, it will prompt you to press Enter.
When all zips are processed you may reboot to recovery, make a backup of your current ROM and flash them.
When you reboot, your secondary ROM will load.
B. SwitchROM.sh
The name is self-explanatory. This tool can only function if it finds the files boot1.img and boot2.img inside the /sdcard/DualBoot/img folder.
These files will be automatically generated when you convert a ROM zip in the ZipEditor. Alternatively, if you know what you are doing, you can create and put them there yourself.
Tap it in Script Manager and again select the first two icons (Favorite and SU) and Run. It will automatically detect the current ROM, flash the boot.img of the other one and prompt you to reboot. Use your Power-Menu and reboot your device. Your device will now boot to the other ROM.
Credits for the ZipEditor.sh and SwitchROM.sh goes to @dreccon
Credits for the executable binaries goes to @Modding.MyMind - That's me
Click to expand...
Click to collapse
dang it... now i gotta get me a 64G card
Rockin it from my Rockin Smartly Deadly Venom NE5 S4 (much thanks to: @Venom0642 @ted77usa @rebel1699 @iB4STiD ~ 20GB free cloud https://copy.com?r=vtiraF

Newb Warning - I softbricked my P3110

I started experimenting with my old P3113 last night and ran into a bit of a problem. I successfully rooted using Odin 3.09, verified with root checker. I also successfully flashed TWRP 2.8.7.0 via Odin. All root and TWRP install/flashes were successful via Odin.
Following these instructions: http://forum.xda-developers.com/gal...m-dhollmen-lollipop-5-0-2-2015-02-02-t3020849
I downloaded the Dhollmen-P31xx-Kernel_20150215.zip and saved to the Download folder on the tab. From TWRP I ran a wipe and installed the .zip. I reboot the device and I am returned to TWRP recovery. TWRP tells me that the installation was successful however the log says "no MD5 file found". Does this have anything to do with why my device isn't booting properly? I've rooted other devices and flashed ROM's before but I don't understand what I missed on this one. Do I just need to try a different ROM? For reference I am still able to access download menu.
Any help would be appreciated!

Well, the "no MD5 file found" just means TWRP cannot verify the MD5 hash of the ZIP file - that's actually a security meassure to ensure the ZIP file didn't get damaged during download or transfer onto the tab.
Now ... once you flashed TWRP (which you obviously already successfully did) and flashed the Kernel (which you obviously also already successfully did) it would be about time to flash the actual Dhollmen ROM that goes along with the Kernel ... I doubt the Kernel will boot up your vanilla Samsung stock ROM.
In short (haven't read the ROM thread nor did I ever use Dhollmen, so check back to make sure it's about right): Download the ROM, download the GApps package for the ROM and download the Superuser package (if not already included in the ROM) of your choice. Put the files onto either a FAT32 formatted SD card (if you can't put them into the NAND "SD card" partition at the moment) or onto a FAT32 formatted USB stick (given you have a USB-OTG cable), plug it in (if you use a USB stick make sure your tablet is CHARGED!), boot into recovery and flash the files in one go ... ROM, Gapps, SU.
Run a wipe (Data and Cache) when everything is flashed to nuke any left-overs from the Stock ROM and reboot to system.
Keep in mind the first boot can take quite some time ... don't panic if the boot animation "just sits there" for 5<->15 minutes.
Easiest way would be to actually use a ROM that doesn't require a extra Kernel ... like Android-Andi's CyanogenMod 12.1 or Omni ROM 5.1 (use the 3110 versions for your 3113).

[ROM] Debloated Asus Zenpad S 8.0 (Z580C/Z580CA) WW Firmware Rom

This is a modded and signed ZIP of the latest Asus rom with all bloatware/junkware removed, dropping the ZIP size from 1.4 GB to only 920MB! It has no added applications/bloatware and has NOT been rooted (can root with SuperSu though). This rom will more than likely not work with OTA updates, but newer versions of the rom will be posted should Asus provide updates, and those should will be dirty flash-able. Picture of the app drawer with clean install: https://i.imgur.com/8xsZj8F.jpg
This modded ROM works fine with both the Z580C and Z5680CA (ROMs are the same ZIP). Currently only the WW firmware is supported, and will ONLY work on devices that already have a WW firmware. Flashing an incorrect firmware that does not match what your device originally had (WW, JP, TW, or CN) will NOT work, and may brick your device. Use caution. Only WW is available at this time.
Note: The ROM is currently stuck at 5.0. It will be unless Asus provides a 6 ROM or and an unlocked bootloader. Don't ask for Marshmallow, I can't do anything about it yet.
Requirements:
Asus Zenpad S 8.0 - Z580CA or Z580C with WW (World Wide) Firmware ONLY.
Micro SDCard - FAT32 Formatted, <= 32GB Size (Larger cards have issues with ClockWorkMod)
Intel Android Devices Root / Temp Recovery Session (Windows or Linux Version)
Latest ZIP file from thread
(Optionally) Latest SuperSU ZIP
(Optionally) Latest XposedFramework ZIP
Full Backups of your data, unless you want to lose it all.
Screenshots: https://i.imgur.com/8xsZj8F.jpg
https://i.imgur.com/4MTCqwo.jpg
https://i.imgur.com/eek03Te.jpg
Links:
Modded Stock Rom: https://drive.google.com/file/d/0B0af6CkRQIYWV3pCbHZnY09zamM/view?usp=sharing (sha1sum: 3cbdd3bc52bc486c24d1c2573ac924eb33f9f891)
Intel Android Root Tools:
Windows: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Linux: http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Latest SuperSU Stable: http://forum.xda-developers.com/showthread.php?t=1538053
Latest XposedFramework (sdk22, x86 Version): http://forum.xda-developers.com/showthread.php?t=3034811
Instructions:
Steps:
1.) Place all flashable ZIP files on the FAT32 formatted SDCard (Rom ZIP, SuperSU, and Xposed). Leave the card on your desk/table for now, do not install into tablet yet.
Note: If you have the tablet encrypted, you should factory reset it using stock recovery before moving on to step two. CWM doesn't do a good job of erasing encrypted /data and claimed it was still encrypted after the clean install, and required another reset.
2.) Use the Intel Boot/Recovery tools to boot CWM. Follow the instructions at their pages to do this. You must use Method #2.
3.) Completely format /cache /system, and /data. /cache make take some time, it took nearly 15 minutes, /system took about 2 minutes, and /data about 1 minute. DO NOT CLOSE CWM OR REBOOT.
4.) Pug in Micro SDCard, and install your flashable ZIPs from your external SDCard.
5.) WIPE CACHE AGAIN. Just /cache. It shouldn't take as long as the first time, but this MUST be done, or else you will get issues and/or bootloops.
6.) Done. Reboot to system.
I have only modded the stock rom. Credit for the tools and links goes to their respective creators and/or maintainers. I'm just sharing this with others.

lolihunter said:
This is a modded and signed ZIP of the latest Asus rom with all bloatware/junkware removed, dropping the ZIP size from 1.4 GB to only 920MB! It has no added applications/bloatware and has NOT been rooted (can root with SuperSu though). This rom will more than likely not work with OTA updates, but newer versions of the rom will be posted should Asus provide updates, and those should will be dirty flash-able.
It is not compatible with the Z580C at this time. That requires a separate ROM, and I don't have a device to test with. If someone feels like being a little adventurous, I can make a test build for you to play with, and once its good I can upload that as well.
Note: The ROM is currently stuck at 5.0.1. It will be unless Asus provides a 6 ROM or and an unlocked bootloader. Don't ask for Marshmallow, I can't do anything about it yet.
Requirements:
Asus Zenpad S 8.0 64GB/4GB Edition - Z580CA (Not for the Z580C)
Micro SDCard - FAT32 Formatted, <= 32GB Size
Intel Android Devices Root / Temp Recovery Session (Windows or Linux Version)
Latest ZIP file from thread
(Optionally) Latest SuperSU ZIP
(Optionally) Latest XposedFramework ZIP
Full Backups of your data, unless you want to lose it all.
Screenshots: https://i.imgur.com/8xsZj8F.jpg
https://i.imgur.com/4MTCqwo.jpg
https://i.imgur.com/eek03Te.jpg
Links:
Modded Stock Rom: https://drive.google.com/file/d/0B0af6CkRQIYWV3pCbHZnY09zamM/view?usp=sharing (sha1sum: 3cbdd3bc52bc486c24d1c2573ac924eb33f9f891)
Intel Android Root Tools:
Windows: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Linux: http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Latest SuperSU Stable: http://forum.xda-developers.com/showthread.php?t=1538053
Latest XposedFramework (sdk22, x86 Version): http://forum.xda-developers.com/showthread.php?t=3034811
Instructions:
Steps:
1.) Place all flashable ZIP files on the FAT32 formatted SDCard (Rom ZIP, SuperSU, and Xposed). Leave the card on your desk/table for now, do not install into tablet yet.
Note: If you have the tablet encrypted, you should factory reset it using stock recovery before moving on to step two. CWM doesn't do a good job of erasing encrypted /data and claimed it was still encrypted after the clean install, and required another reset.
2.) Use the Intel Boot/Recovery tools to boot CWM. Follow the instructions at their pages to do this. You must use Method #2.
3.) Completely format /cache /system, and /data. /cache make take some time, it took nearly 15 minutes, /system took about 2 minutes, and /data about 1 minute. DO NOT CLOSE CWM OR REBOOT.
4.) Pug in Micro SDCard, and install your flashable ZIPs from your external SDCard.
5.) WIPE CACHE AGAIN. Just /cache. It shouldn't take as long as the first time, but this MUST be done, or else you will get issues and/or bootloops.
6.) Done. Reboot to system.
I have only modded the stock rom. Credit for the tools and links goes to their respective creators and/or maintainers. I'm just sharing this with others.
Click to expand...
Click to collapse
I can test I have the 32gb variant

I just finished installing it and everything seems to be running smoothly. Great job!

I am mighty sure that this is just plain 'ole 5.0 and not 5.0.1 as mentioned. Just to be clear, Cheers and good job!
Edit: Another thought, there are different versions or SKU's of this tablet (WW, JP, TW, CN etc.) that according to ASUS, you cannot install a rom from one SKU to another...... @lolihunter, what SKU version rom did you use? and IMHO, a warning should be added to the OP.

mad4some said:
I am mighty sure that this is just plain 'ole 5.0 and not 5.0.1 as mentioned. Just to be clear, Cheers and good job!
Edit: Another thought, there are different versions or SKU's of this tablet (WW, JP, TW, CN etc.) that according to ASUS, you cannot install a rom from one SKU to another...... @lolihunter, what SKU version rom did you use? and IMHO, a warning should be added to the OP.
Click to expand...
Click to collapse
You are indeed correct. I have edited the post to reflect the correct data. I shouldn't make such an important post when low on sleep.
Also, I am working on a version for Z580C. I actually noticed the file sizes, ZIP names, and descriptions of the stock ROMs for both devices are the same on the Asus website, but have slightly different links. If luck is in favor, the one I am downloading will match the original stock ROM for the Z580CA, meaning they are one and the same. Will update later today with either an edited post or a new separate modded ROM.
If there ends up being enough demand for the other firmwares, I may edit and add those as well.

Cannot connect via ADB and cannot pull files from ExtSD
(Issue Resolved, see below)
Hello,
While attempting to flash my tablet, my CWM session did not seem to recognize my SD card with the files needed to flash.
So, right now, my tablet is:
-In a CWM session (somewhat afraid to restart)
-Unable to read SD cards for some reason (tried two separate SD cards, 4GB and 16GB, both formatted FAT32)
-Without an operating system (/System, /Data, /Cache wiped)
-Is unauthorized by ADB.
Is there anything I can do to fix my tablet? Restart into stock bootloader maybe? Authorize ADB to sideload files (somehow)?
Any help is appreciated,
-Pjb0521
(Forgot to mention, I have the Z580C)

pjb0521 said:
Hello,
While attempting to flash my tablet, my CWM session did not seem to recognize my SD card with the files needed to flash.
So, right now, my tablet is:
-In a CWM session (somewhat afraid to restart)
-Unable to read SD cards for some reason (tried two separate SD cards, 4GB and 16GB, both formatted FAT32)
-Without an operating system (/System, /Data, /Cache wiped)
-Is unauthorized by ADB.
Is there anything I can do to fix my tablet? Restart into stock bootloader maybe? Authorize ADB to sideload files (somehow)?
Any help is appreciated,
-Pjb0521
(Forgot to mention, I have the Z580C)
Click to expand...
Click to collapse
If CWM is failing to detect an SDCard, I would suspect the card itself as being the problem. What OS are you using to format the SDCard? If your are using Windows, try to use disk management to make sure the card is using the GPT partition table instead of MBR. If it is already, use it to initialize it to MBR then back to GPT, and use it to create a single nameless fat32 partition across the whole SDCard.
CWM should automatically mount the card. I didn't need to mount it with mounts and storage, I just plugged it in and tried to install from it, and it automatically showed the files I had copied to it.
This tablet does not allow for pushing or pulling of files with adb, it is always unauthorized. I would imagine this has to do with the locked bootloader, as even in Linux I cannot push the files to it, which is why the guide uses the SDCard.

Nevermind, issue is resolved. Just rebooted into fastboot, restarted the CWM session and installed the ROM. Thanks anyways for your help!

Do you think you can port marshmallow rom for zenfone 2 to zenpad s Z580CA? same hardware

lolihunter said:
This is a modded and signed ZIP of the latest Asus rom with all bloatware/junkware removed, dropping the ZIP size from 1.4 GB to only 920MB! It has no added applications/bloatware and has NOT been rooted (can root with SuperSu though). This rom will more than likely not work with OTA updates, but newer versions of the rom will be posted should Asus provide updates, and those should will be dirty flash-able. Picture of the app drawer with clean install: https://i.imgur.com/8xsZj8F.jpg
This modded ROM works fine with both the Z580C and Z5680CA (ROMs are the same ZIP). Currently only the WW firmware is supported, and will ONLY work on devices that already have a WW firmware. Flashing an incorrect firmware that does not match what your device originally had (WW, JP, TW, or CN) will NOT work, and may brick your device. Use caution. Only WW is available at this time. ....
.....I have only modded the stock rom. Credit for the tools and links goes to their respective creators and/or maintainers. I'm just sharing this with others.
Click to expand...
Click to collapse
Excellent work - much appreciated!
One question - after installing this ROM is it possible to return it back to stock at a later time?

@glaudrem it might be possible to get a marshmallow build ported, but unless we actually get an unlocked bootloader for the device it's really gonna be too much work.
@Angus66 yes, you can just flash the latest stock rom zip from the Asus website in the same way you flashed the modded one. In fact, the only thing I have done to the modded rom is just removed the bloatware from /system/ and repacked it, making clean installs or reinstalls much easier. Just make sure to do a full wipe with CMW should you decide to go back.

Hi, Thanks for your work on this. I have the Z580C and can you tell me the version of superSU that you have verified to work with this rom? I have had problems with older devices and "the latest version of SuperSU" causing bootloops. I currently use version 2.65 which works.
jfoss

Where can I find what firmware version I currently have on my Zenpad S???

Official Marshmallow rom for Z580C/CA is UP!
It has just been discovered that the Portuguese Z580C/CA web page has version 5.4.3 available for download!
This Android version for these ROMs is 6.0, and is for the JP and WW SKUs.
http://www.asus.com/pt/Tablets/ASUS_ZenPad_S_80_Z580C/HelpDesk_Download/

hheeyyy it's the same on the US webpage
ASUS ZenPad S 8.0 (Z580C) Firmware: V5.4.3.0 (for WW SKU version only)
***This version is only for download manually, device wouldn't receive FOTA notification***
Notice：
Note1: Software update to Android 6.0 Marshmallow. Internal storage will decrease slightly after update, suggest backing up data and relocating media file (pictures & video clip) to SD card to reserve enough storage before starting the software update.
Note2: The battery life of device has to be more that 50%. It suggest plug ASUS adapter in order to avoid upgrading failed.
* OS upgrade from Lollipop to Marshmallow
http://www.asus.com/us/Tablets/ASUS_ZenPad_S_80_Z580C/HelpDesk_Download/
gimmie smores

Hey guys,
everything went fine, except that I forgot to erase the cache before rebooting. Now I am stuck in droidboot and I can't get out of there. The only thing that detects the tablet is fastboot, but i can't execute any commands, as it says
Code:
FAILED (remote: command not allowed in this device state)
So I can't start a new temporary CWM session.
Wiping cache or anything else with fastboot does not work either, as it's the same error...
Any suggestions?

Hi!
I have a question:
During this week Asus updated to mm.
Can i do the upgrade if i have installed the debloated version of the firmware? If yes, how? If not, how Can i roll back and get mm?
Thank you very much in Advance.

4k7 said:
Hey guys,
everything went fine, except that I forgot to erase the cache before rebooting. Now I am stuck in droidboot and I can't get out of there. The only thing that detects the tablet is fastboot, but i can't execute any commands, as it says
Code:
FAILED (remote: command not allowed in this device state)
So I can't start a new temporary CWM session.
Wiping cache or anything else with fastboot does not work either, as it's the same error...
Any suggestions?
Click to expand...
Click to collapse
If you installed the MM update, from the tethered recovery, that is the cause of your problem and no one has found a solution, at this point. You can find more discussion on this issue, in the rooting your Zenpad S tablet discussion.
http://forum.xda-developers.com/showthread.php?t=3160422
Sent from my Nexus 6P using Tapatalk

S. Prime said:
If you installed the MM update, from the tethered recovery, that is the cause of your problem and no one has found a solution, at this point. You can find more discussion on this issue, in the rooting your Zenpad S tablet discussion.
http://forum.xda-developers.com/showthread.php?t=3160422
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Ah okay, I've just seen the thread. Well, as I still have warranty I handed it back to the store today and they will send it to Asus, so it will either be repaired or I will get a new one.
Thanks anyways.

lolihunter said:
@glaudrem it might be possible to get a marshmallow build ported, but unless we actually get an unlocked bootloader for the device it's really gonna be too much work.
@Angus66 yes, you can just flash the latest stock rom zip from the Asus website in the same way you flashed the modded one. In fact, the only thing I have done to the modded rom is just removed the bloatware from /system/ and repacked it, making clean installs or reinstalls much easier. Just make sure to do a full wipe with CMW should you decide to go back.
Click to expand...
Click to collapse
There is now an official Marshmallow Update from ASUS I am currently running it but its full of bloat, if you could remove bloat again that would be awesome, I just want an AOSP version for this tablet but I don't think I will ever get that. Here is a link to the actual download from the ASUS website: http ://dlcdnetDOTasus.com/pub/ASUS/EeePAD/Zenpad/Z580C/UL-P01M-WW-5.5.0.0-user.zip?_ga=1.264638607.1670638117.1483822798 This is for the Z580C.
I just signed up so I can't post links :crying: but just replace the 'DOT' with a . and the space between the http and ://