Related
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
Hi I am a new member on this forum, though I had been browsing this forum for long long time, I had not registered. Recently I had the courage to root and install omnirom on my phone (as my phone is getting old, i was ready to take the chances of bricking my device. I verified my device with eMMC brick bug tester and my device is frees from that bug, probably as my motherboard was changed under warranty). After toying with omnirom, I am back on stock rom. I went to Samsung Service Center and got my factory firmware installed for Rs 225/- (I had taken nandroid backup with epsilon 6.0... version of CWM, but it missed preload partition and restored the backup with philz recovery and my preload partition was erasaed and have to go for SSC).
I have few queries regarding the SGR, please help me with them:
1. Is there a temporary recovery for SGR (ie, can be flashed with stock recovery and returns back to stock on reboot. The zip file has to be maintained on SD card)
For SGS2: http://forum.xda-developers.com/galaxy-s2/general/guide-root-unroot-stock-ics-firmware-t1501719
2. In order to restore the partition on my own, I tried and searched net for recovery using testdisk and had taken a file image of the SGR internal flash disk. I opened it with testdisk, but testdisk was not able recognise the partitions I tried EFI GPT as suggested and Intel partiton table type and both did not work. Do you know the partition table type for this?
recovery link: http://www.df.lth.se/~jokke/androidfilerecovery/
3. I was just curious if becoming root (on adb shell) is just running su, thought I would copy su binary from superuser zip ro sdcard and run it with the path, but it just runs and nothing happens (I need this to remove few samsung apps esp, vlingo. I plan to do it from recovery -> adb shell -> su and delete apk & odex files).
This has been a great forum and helped me a lot. Thank you guys for all your effort.
Hi people, here is a short instruction if you have a P or L version of the I8160 and want to update this (great) old phone. credits to xdas-e
for a while i thought that roms didnt work on the P version, because when installing roms i got the error that the rom was only for I8160, not I8160P. so yeah it is possible, maybe this is common knowledge, but i couldnt find out how before i found this information.
I have not tested this exhaustively but i believe they all should work, because i believe the only difference from the P version is that it has an NFC module.
]------- modify the rom for P version:
1.- Get the custom ROM.
2.- Get the /system/lib/tee folder contents from your GT-I8160P JB installation (from stock rom). You may need root access, although in my case I could simply move trough the hidden directories and copy the folder to my sd card.
3.- Swap the /system/lib/tee folder, and put what you got from step 2, into the zip file of step 1, same place, same everything. You may very well dispose the original /system/lib/tee folder in the zip file.
4.- Change /system/build.prop and introduce a P in every GT-I8160 entry (from GT-I8160 to GT-I8160P).
5.- (tricky one) look for the updater script file within the custom ROM zip file, and delete (or add a P) the first complete entry of the assert command (you shall see some GT-I8160 there). in my case it was located under META-INF\com\google\android\.
------- from here you have successfully modified the rom for the P version, these steps just show the installation:
6.- If you dont already have CWM, get yourself one (I used this one [JB] CWM Recovery 6).
7.- Put both zip files into your sd card; get a copy also of gapps (google apps, play store etc) for the android version of the rom.
8.- Back up all your data.
9.- Swicht off your phone and restart in recovery mode (up volume, home and power buttons pressed simultaneously).
10.- Load from the external sd card the CWM zip file.
11.- Make a full ROM backup to restore if things go wrong. Wipe data/factory reset; wipe cache partition; wipe dalvik cache (under advance options), format /system if needed (see rom instructions).
12.- Install from external sd card: a) custom CM rom; and b) gapps if you're for it.
13.- Restart.
14.- You shall be done!!! (first boot takes a long time)
good luck! my phone was crap with stock and now it works great, so basically it saved me from buying a new phone.. a big thanks to all the rom developers for this device .
[GUIDE] f2fs for stock, developer and custom - roms
This is my first post in xda, im a silent reader since years.
Just registerd to post this because so many people always asks the thing with f2fs and if the rom have f2fs support.
Dont ask again, make it support on your own!
its not magic, its just format the partitions, editing two lines in fstab and flashing the right kernel.
Caution! You will lose all data from internal storage so please backup your files!
What you need:
1. unlocked android device, i´m on Redmi note 5 Global 4/64
2. pc or notebook with adb and fastboot
3. custom recovery solution, i use original latest twrp
4. off course a rom of your choice, in my case xiaomi.eu latest developer (MIUI 10.4 / 9.5.16)
5. a kernel that supports f2fs, i use KangarooX r4.4 with OC but ice cold etc. works also
6. a texteditor, i use the windows notepad
7. time
Ok, lets go:
All this things must be done in a row, without reboot!
1. remove fingerprint, face and pin unlock on your running device
2. boot into twrp by pressing vol up + power button
3. go to wipe > make a factory reset
4. go to wipe > advanced wipe > select Cache > repair or change file system > change file system > select f2fs
5. go to wipe > advanced wipe > select Data > repair or change file system > change file system > select f2fs
6. connect your device to pc
7. transfer your rom, kernel and all your files you need to internal storage or take your sd card (i prepared my sd card)
8. flash your rom
9. flash your kernel
10. flash your other stuff (i flashed magisk)
11. check your cache partition, it should be f2fs if not, change cache file system again (Point 4)
12. mount the vendor partition
13. on your pc, go to your adb folder and check in terminal if device is listed
14. type in terminal without quotes "adb pull /vendor/etc/fstab.qcom"
15. edit the fstab.qcom with your editor, search for the data and cache lines
16. edit the line for the cache partition that it looks like "/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait" without quotes
17. edit the line for the data partition that it looks like "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,background_gc=off,fsync_mode=nobarrier wait,resize,check,crashcheck,quota" again without quotes
18. save the file and push it to your device with terminal "adb push fstab.qcom /vendor/etc/" remember without quotes
19. set permisson of the file in terminal or twrp, i use terminal "adb shell" > "cd /vendor/etc" > "chmod 644 fstab.qcom"
20. now you´re ready to reboot the device and have a lag free gcam pixel3, etc.
After reboot, check your partitions with diskinfo or similar.
This guide should also work with other devices.
Happy flashing and i hope you enjoy
PS: my english is not so good as it can be
Remember: if you flash the vendor partition, you have to edit the fstab.qcom again!
its easier to convert to f2fs data and cache and flash datafix-fstabs cachefix-fstabs in twrp
JA
raptorddd said:
its easier to convert to f2fs data and cache and flash datafix-fstabs cachefix-fstabs in twrp
Click to expand...
Click to collapse
but not work for MIUI
RubenPCA said:
but not work for MIUI
Click to expand...
Click to collapse
yes it does. i am using in xiaomi .EU
Both methods work.
Let me explain why i posted this tiny Guide.
For people who are not familiar with operating systems in this case android, its allmost tricky to find the right solutions or files without any clue what they need.
If you do things from ground, you understand what you´ve done and are able to fix it or remove it by yourself.
I personally prefer the way to do things on my own and not spend many hours to search for the right files, to download and flash without any clue what they do or how they work.
When i decided to change the filesystem of my devices, i started to search and found fragmented solutions over the net.
Btw. doesn´t found the 2 zip files easy. Heard the first time as you commented this tiny Guide. So i started to search and found the hint in a different comment from you, it can be downloaded from a telegram group.
Anyway, i doesnt had this files but knowledge in linux, so i decided to change the lines quickly by myself. It isnt much work and its always the same so you can copy and paste the two lines.
To make the choice and search for the peoples easy, here ist the link to the thread where you can find the telegram group to download the files https://forum.xda-developers.com/redmi-note-5-pro/help/f2fs-miui-pie-roms-t3922370
raptorddd said:
yes it does. i am using in xiaomi .EU
Click to expand...
Click to collapse
Do you need to reflash cache and data fix after every rom update/dirty flash?
sushuguru said:
Do you need to reflash cache and data fix after every rom update/dirty flash?
Click to expand...
Click to collapse
it depends on the rom that you want to flash.
The file that needs to edit from hand or the two zip files is on the vendor partition.
In short, the file tells the System witch partition with attributs, names and filesystem is automatic mount during the startup process.
Gerr1 said:
it depends on the rom that you want to flash.
The file that needs to edit from hand or the two zip files is on the vendor partition.
In short, the file tells the System witch partition with attributs, names and filesystem is automatic mount during the startup process.
Click to expand...
Click to collapse
Xiaomi.eu in my case, wonder if the rom will replace the file has been fixed after flashing.
sushuguru said:
Xiaomi.eu in my case, wonder if the rom will replace the file has been fixed after flashing.
Click to expand...
Click to collapse
Dont know, try it out. If the phone doesnt boot, go to twrp and flash the zips again.
sushuguru said:
Do you need to reflash cache and data fix after every rom update/dirty flash?
Click to expand...
Click to collapse
yes. rom-kernel-datafix-cachefix.
Do I need to do steps 12 to 20 for HavocOS or AOSiP? (Both these ROMs support f2fs)
Also, do I need to do these steps again after I update the said roms?
devansh8 said:
Do I need to do steps 12 to 20 for HavocOS or AOSiP? (Both these ROMs support f2fs)
Also, do I need to do these steps again after I update the said roms?
Click to expand...
Click to collapse
Nope, just format data and cache partition to f2fs and you're good to go.
Gerr1 said:
[GUIDE] f2fs for stock, developer and custom - roms
This is my first post in xda, im a silent reader since years.
Just registerd to post this because so many people always asks the thing with f2fs and if the rom have f2fs support.
Dont ask again, make it support on your own!
its not magic, its just format the partitions, editing two lines in fstab and flashing the right kernel.
Caution! You will lose all data from internal storage so please backup your files!
What you need:
1. unlocked android device, i´m on Redmi note 5 Global 4/64
2. pc or notebook with adb and fastboot
3. custom recovery solution, i use original latest twrp
4. off course a rom of your choice, in my case xiaomi.eu latest developer (MIUI 10.4 / 9.5.16)
5. a kernel that supports f2fs, i use KangarooX r4.4 with OC but ice cold etc. works also
6. a texteditor, i use the windows notepad
7. time
Ok, lets go:
All this things must be done in a row, without reboot!
1. remove fingerprint, face and pin unlock on your running device
2. boot into twrp by pressing vol up + power button
3. go to wipe > make a factory reset
4. go to wipe > advanced wipe > select Cache > repair or change file system > change file system > select f2fs
5. go to wipe > advanced wipe > select Data > repair or change file system > change file system > select f2fs
6. connect your device to pc
7. transfer your rom, kernel and all your files you need to internal storage or take your sd card (i prepared my sd card)
8. flash your rom
9. flash your kernel
10. flash your other stuff (i flashed magisk)
11. check your cache partition, it should be f2fs if not, change cache file system again (Point 4)
12. mount the vendor partition
13. on your pc, go to your adb folder and check in terminal if device is listed
14. type in terminal without quotes "adb pull /vendor/etc/fstab.qcom"
15. edit the fstab.qcom with your editor, search for the data and cache lines
16. edit the line for the cache partition that it looks like "/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait" without quotes
17. edit the line for the data partition that it looks like "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,background_gc=off,fsync_mode=nobarrier wait,resize,check,crashcheck,quota" again without quotes
18. save the file and push it to your device with terminal "adb push fstab.qcom /vendor/etc/" remember without quotes
19. set permisson of the file in terminal or twrp, i use terminal "adb shell" > "cd /vendor/etc" > "chmod 644 fstab.qcom"
20. now you´re ready to reboot the device and have a lag free gcam pixel3, etc.
After reboot, check your partitions with diskinfo or similar.
This guide should also work with other devices.
Happy flashing and i hope you enjoy
PS: my english is not so good as it can be
Remember: if you flash the vendor partition, you have to edit the fstab.qcom again!
Click to expand...
Click to collapse
Can you pls make tutorial for exynos chipsets also? Pls pls pls
Is there a way to know if a custom rom Support f2fs or not ?
HI,
I have 2 Samsung devices with TWRP installed, and I can access the TWRP recovery menu. When I install the flash ROM and try to boot, devices are stuck in system boot forever.
Device 1: SM-T800, with LineageOS 14.1 previously. I opened an email and the device got hacked, so I did a factory reset (which failed), then re-flashed the latest TWRP and recovered rescue mode. Now when I flash the Lineage ROM (from TWRP) the device does not boot to system but keeps showing the splash screen. I think the hack might have placed immutable files under system. could I format this partition to zero it out via ADB? What other choices are there?
<EDITED>
Device 2: Galaxy S3 GT-I9300 - I solved this so i removed this section.
Thank you for any help.
Beeblebrox-BSD said:
HI,
I have 2 Samsung devices with TWRP installed, and I can access the TWRP recovery menu. When I install the flash ROM and try to boot, devices are stuck in system boot forever.
Device 1: SM-T800, with LineageOS 14.1 previously. I opened an email and the device got hacked, so I did a factory reset (which failed), then re-flashed the latest TWRP and recovered rescue mode. Now when I flash the Lineage ROM (from TWRP) the device does not boot to system but keeps showing the splash screen. I think the hack might have placed immutable files under system. could I format this partition to zero it out via ADB? What other choices are there?
Device 2: Galaxy S3 GT-I9300, with working TWRP. This device is giving a "Failed to mount /efs (Invalid argument)" error. The previous setup was shared storage with sdcard and encryption on both internal and sdcard. The sdcard got corrupted, hence the error. This post suggests running
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
but the device does not have identifiable boot device under /dev/block. I think this might work if I can identify the boot partition name?
Thank you for any help.
Click to expand...
Click to collapse
Flash a custom ROM for i9300 via TWRP. Download a custom ROM for i9300 and the appropriate Gapps to go with the ROM, store them on external sdcard. When you are in TWRP, before you flash your ROM, select the "Wipe" option, then select "advanced wipes", on the next menu, choose the system partition, data partition, cache partition and dalvik cache partition then swipe the slider to wipe. Then go back to home screen in TWRP and choose the "Install" option, then choose your ROM file and your Gapps file then swipe to flash. When the flash is finished, select the "Reboot system" option and see if it boots into system.
If that doesn't work, we will take some steps further back and try starting from the beginning.
Keep in mind that some of the custom ROMs for i9300 may have a different partition structure and partition sizes than the stock firmware for i9300 has and may require resizing certain partitions such as the system partition by flashing a custom PIT file like the Galaxy S2 had to do before it flashed certain custom ROMs.
Hi, thanks for the input.
* I had already solved the GT-I9300 issue before your post (I should have added to thread rather than edit the original post). I solved issue with that device by including system partition in the wipe.
* For the SM-T800, I used a LineageOS-14.1 that I had stored somewhere. That also did not work, until I only flashed Lineage and did not include any GApps. If I really need it, I can always flash later. I assume the latest GApps 7.1 build conflicts with older ROMs.
An unexpected problem was the lack of current ROMs for the 2 devices. SM-T800 has nothing other than last build Lineage-14-1-20190205. The I9300 has several unofficial ROMs floating around for newer Android versions, but they are all debug/dev builds with enabled options that drain the battery very quickly.
If anyone comes across a decent ROM for either of these devices please LMK. Thanks.