THIS IS FOR 1.2 & 1.3 (Please Check Below for Instructions) - Please don't quote the first post.
Read this before you post:
http://forum.xda-developers.com/showpost.php?p=13953240&postcount=774
What it does:
Permanently Enables ADB via uRamdisk
Installs adbWireless
Installs su and Superuser.apk
Installs Busybox
Installs Softkeys 3.0.6
Installs zeam Launcher
Installs B&N HomeLauncher
Installs NookColor Tools (To Enable Non-Market Installs)
Installs Gapps (Gmail, Market, Youtube, Others)
Enable Multi-touch for Android Apps
App Auto Install (Open up update.zip from sdcard drop in /data/app)
System Files that get Modified:
uRamdisk - Enables permanent ADB Access
/system/build.prop - Fingerprint change
packages.xml - Attempt to fix signature issue (unnecessary?)
downloads.db - Fixes Market "Download Unsuccessful" issues
Changes:
September 3, 2011 - 1.3 Instructions Added
June 16, 2011 - 4.6.16
Fixed: Restored missing permission files that were in 4.5.18 but not 4.5.25
May 25, 2011 - 4.5.25 - Thanks to GMPOWER for this update.
Fixed: Calendar Sync
Fixed: New Market FCs
Fixed: Unknown Reason -18 - This will replace your current Kernel!
May 18, 2011 - 4.5.18
Fixed: Touchscreen issues with Kids Books
Added: B&N HomeLauncher
May 6, 2011 - 4.5.6 - Special Thanks: lewellyn for all the work he put into this version.
Fixed: /cache/downloadnull issue.
Fixed: "Download Unsuccessful"
Fixed: Market Force Closed (No guarantee it'll hold if Market is updated)
Added: adbWireless
Before you begin:
To update to 1.2 you must do a complete wipe.
You must update to 1.2 to use ManualNooter Instructions Here.
You must already have a registered NOOKcolor
You must have a Google Account, for Gmail, Market, Etc. IF you used a Gmail account for B&N Registration you should use that one for this process.
CWM Bootable from SD Card: http://forum.xda-developers.com/showthread.php?t=987735 - You should always use the Latest CWM Version
OR emmc CWM Recovery Installed
You must have enough intelligence to follow instructions.
1.3 Must do these instructions first with 4.5.18 then with 4.6.16.
Let's get started:
If you're running a previous MN you do not need to do a complete wipe.
Download ManualNooter from here:
ManualNooter-4-5-18.zip - 1.3 Only
ManualNooter-4-6-16.zip
Copy onto your flashable CWM SD card using Windows Explorer, OS X Finder, etc.
See step 3 above for how to make a flashable CWM card.
DO NOT extract the zip file. It MUST be left as-is.
DO NOT copy the zip file into a folder. Leave it at the top directory of your card
Unplug your NOOKcolor from computer. (If Plugged in.)
Turn off your NookColor (If turned on.)
Insert Flashable CWM SDcard with ManulNooter into your NOOKcolor.
Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)
If using Flashable CWM SDCard this should boot you into recovery.
If using eMMC CWM Recovery instead of SD CWM Recovery, boot to recovery.
When CWM boots select the update using your Volume Keys and n button:
- install zip from sdcard (Volume up 4 times, then n)
- choose zip from sdcard (Volume down 1 time, then n)
- manualnooter-4-x-x.zip (Hit volume up until you get to it, then n)
1.3 needs to run 4.5.18 before 4.6.16
- Confirm that you really want to run the update.
Selecting this indicates that you take responsibility for your own actions.
Wait patiently and follow onscreen directions.
If you get "Install Failed" after rebooting out of CWM this can be normal. Just reboot again.
After reboot and unlocking your device select Zeam Launcher.
Run Fix Permissions from Rom Manager - 1.3 Only after running 4.6.16
Open up Market and Accept Terms and Service/Sign In.
If you get a full application list, you're done!
You may not have to Accept Terms and Service or Sign In if you're updating from a previous MN version.
If you made it this far your nook should be successfully Rooted.
Enable Non-Market Installs by running the NookColor Tools App.
If you want to revert your card to a "usable" state.
Go to Settings > Device Info > SdCard > UnMount > Format
This will wipe your SDCard of all MN/CWM Flashable abilities. If you use this you will have to reflash the SDCard for future MN releases.
Known Issues without solutions:
IMEI Force Close -
There is no randomly Generated IMEI in this version. - Apps that close due to lack of IMEI need to be fixed by Developers not users.
Network Location isn't enabled -
Signature Issue again - Work is being done to locate the fix.
Known Issues and Solutions:
"Download Unsuccessful" -
Fixed Fixed as of 4.5.6
Market Force Close -
Fixed Fixed as of 4.5.6
Market tries to download to /cache/downloadnull instead of /cache/download -
Fixed Fixed as of 4.5.6
Installation Error - Unknown Reason -18
Fixed Fixed as of 4.5.25
Calendar does not sync -
Fixed Fixed as of 4.5.25
Market has limited visibility - This is a known tablet issue, not just a NOOKcolor one.
Start Nook Color Tools.
Select the "All Settings" button.
Unplug your NOOKcolor from computer. (If Plugged in.)
Choose "Manage Applications" from the list.
Select the "All" tab.
Scroll down to "Market" and select it.
Tap "Force stop".
Tap "Clear cache".
Tap the Back button if you have SoftKeys running, else swipe right to left on the status bar at the bottom of the screen (from the clock to the book icon).
Scroll up to "Google Services Framework" and select it.
Tap "Clear data".
Tap "OK".
Tap "Force stop".
Press the n button to return to your launcher.
Start Market.
At the "An error has occurred" message, tap "OK".
Hold your power button to turn off your NOOK Color from the menu.
Turn your NOOK Color back on and give it a moment to find your WiFi connection.
Start Market again, and the problem is resolved.
Complete Wipe:
8 Failed Boots > Wipes /system
Factory Reset > Wipes /data
This will not work if you're using emmc Clockwork Mod Recovery
You must do both of these to completely wipe clean your NOOKcolor.
Thanks To:
Donate to these people! They did all the work I just put it into a single package!
bpk - Soft Keys
MrSiir - adbWireless
mastapsi - Coding help
gojimi - Tablet Calendar
Suteru - Boot Animation
Ben74 - NookColor Tools
thecubed - Edifying Nooter
HamNCheese - B&N HomeLauncher
nemith - CWM on NOOKcolor, ADB fixes for 1.2.
Pentagram - Figuring out how to get Market to list properly.
Michael Bentz - Zeam Minimalist Launcher which allows us to access apps.
hari - Discovering the Fix for "Download Unsuccessful" and /cache/downloadnull
lewellyn - Coding help, research, and helping make instructions clear for this post.
pokey9000 - Original Nooter that started the AutoNooter and ManualNooter Projects.
Freenode's #nookcolor chat - dealing with my crap, checking my code, keeping me motivated.
GMPOWER - Kernel to fix Unknown Reason -18 and GAPPs that fix Calendar Sync and gives us newer market.
Donators - Even though I don't think I deserve it a few of you have donated for my work piecing things like this together. It's appreciated.
Please Note: If I'm using your app within ManualNooter or AutoNooter and you'd like it removed please send me a PM stating so and I will do so for future versions.
For those of us on 1.2 with su busybox install ith most of this already in place including most of the gapps etc must we start over from scratch or can we just flash this over our current install with CWM?
From 1.2 Nook Color with root
This will replace su and it adds busybox to /system/xbin, everything else will just copy over something if it has the same name.
On the second step 4, what does "Insert Flashable CWM SDcard with ManulNooter into your NOOKcolor." mean? Please provide step by step instrucitons to make a flashable CWM SDcard.
buellwinkle said:
On the second step 4, what does "Insert Flashable CWM SDcard with ManulNooter into your NOOKcolor." mean? Please provide step by step instrucitons to make a flashable CWM SDcard.
Click to expand...
Click to collapse
There is a link in the preceding paragraph of the instructions on how to make the CWM card.
What version of CWM works?
Will 3.0.05 work or should I go to 3.0.1.0 or even 3.0.2.8?
Thanks for the great work.
Awesome so i can just flash it over
I'm assuming it's safe to use this with eMMC clockwork recovery?
If not no big deal, just one less thing i have to do if i can use my currently installed recovery
Manual Nooter isn't as step by step as AN because this expects you to already have some things before hand. Sorry. Working on the issues that stops me from being able to AutoNooter via CWM.
davidukfl said:
I'm assuming it's safe to use this with eMMC clockwork recovery?
If not no big deal, just one less thing i have to do if i can use my currently installed recovery
Click to expand...
Click to collapse
No clue, find out? If it works you'll be rooted, if not it shouldn't do anything.
GabrialDestruir said:
No clue, find out? If it works you'll be rooted, if not it shouldn't do anything.
Click to expand...
Click to collapse
lol ok sounds good. I'll give it a shot and let you know how it goes
thank you thank you thank you.... will report if needed....
Can anyone confirm a deprecated market issue? Or is it just me?
Congrats, looks like you've made a lot of progress on this.
Before 10,000 others ask, what happens if you flash your Nooter over my apk-enabler? Perhaps we should compare Edify scripts to see if anything is being stepped on.
Uhm... there'd be double app issues, Nook Color Tools Data and System Busybox in xbin and w/e you put it, Superuser in Data and System, anything else it should just overwrite.
A couple of suggestions:
* Some apps may expect su to reside in /system/xbiin - it would be a good idea to set a symlink here
* Busybox is rather useless without having all of its symlnks created. /system/xbin is an appropriate place for these. Something like this should suffice:
symlink("/system/bin/busybox", "/system/xbin/[", "/system/xbin/[[", "/system/xbin/arp", "/system/xbin/ash", "/system/xbin/awk", "/system/xbin/basename", "/system/xbin/bbconfig", "/system/xbin/brctl", "/system/xbin/bunzip2", "/system/xbin/bzcat", "/system/xbin/bzip2", "/system/xbin/cal", "/system/xbin/cat", "/system/xbin/catv", "/system/xbin/chgrp", "/system/xbin/chmod", "/system/xbin/chown", "/system/xbin/chroot", "/system/xbin/cksum", "/system/xbin/clear", "/system/xbin/cmp", "/system/xbin/cp", "/system/xbin/cpio", "/system/xbin/cut", "/system/xbin/date", "/system/xbin/dc", "/system/xbin/dd", "/system/xbin/depmod", "/system/xbin/devmem", "/system/xbin/df", "/system/xbin/diff", "/system/xbin/dirname", "/system/xbin/dmesg", "/system/xbin/dnsd", "/system/xbin/dos2unix", "/system/xbin/du", "/system/xbin/echo", "/system/xbin/ed", "/system/xbin/egrep", "/system/xbin/env", "/system/xbin/expr", "/system/xbin/false", "/system/xbin/fdisk", "/system/xbin/fgrep", "/system/xbin/find", "/system/xbin/fold", "/system/xbin/free", "/system/xbin/freeramdisk", "/system/xbin/fuser", "/system/xbin/getopt", "/system/xbin/grep", "/system/xbin/gunzip", "/system/xbin/gzip", "/system/xbin/head", "/system/xbin/hexdump", "/system/xbin/id", "/system/xbin/ifconfig", "/system/xbin/insmod", "/system/xbin/install", "/system/xbin/ip", "/system/xbin/kill", "/system/xbin/killall", "/system/xbin/killall5", "/system/xbin/length", "/system/xbin/less", "/system/xbin/ln", "/system/xbin/losetup", "/system/xbin/ls", "/system/xbin/lsmod", "/system/xbin/lspci", "/system/xbin/lsusb", "/system/xbin/lzop", "/system/xbin/lzopcat", "/system/xbin/md5sum", "/system/xbin/mkdir", "/system/xbin/mke2fs", "/system/xbin/mkfifo", "/system/xbin/mkfs.ext2", "/system/xbin/mknod", "/system/xbin/mkswap", "/system/xbin/mktemp", "/system/xbin/modprobe", "/system/xbin/more", "/system/xbin/mount", "/system/xbin/mountpoint", "/system/xbin/mv", "/system/xbin/netstat", "/system/xbin/nice", "/system/xbin/nohup", "/system/xbin/nslookup", "/system/xbin/ntpd", "/system/xbin/od", "/system/xbin/patch", "/system/xbin/pgrep", "/system/xbin/pidof", "/system/xbin/ping", "/system/xbin/pkill", "/system/xbin/printenv", "/system/xbin/printf", "/system/xbin/ps", "/system/xbin/pwd", "/system/xbin/rdev", "/system/xbin/readlink", "/system/xbin/realpath", "/system/xbin/renice", "/system/xbin/reset", "/system/xbin/rm", "/system/xbin/rmdir", "/system/xbin/rmmod", "/system/xbin/route", "/system/xbin/run-parts", "/system/xbin/sed", "/system/xbin/seq", "/system/xbin/setsid", "/system/xbin/sh", "/system/xbin/sha1sum", "/system/xbin/sha256sum", "/system/xbin/sha512sum", "/system/xbin/sleep", "/system/xbin/sort", "/system/xbin/split", "/system/xbin/stat", "/system/xbin/strings", "/system/xbin/stty", "/system/xbin/swapoff", "/system/xbin/swapon", "/system/xbin/sync", "/system/xbin/sysctl", "/system/xbin/tac", "/system/xbin/tail", "/system/xbin/tar", "/system/xbin/tee", "/system/xbin/telnet", "/system/xbin/test", "/system/xbin/tftp", "/system/xbin/time", "/system/xbin/top", "/system/xbin/touch", "/system/xbin/tr", "/system/xbin/traceroute", "/system/xbin/true", "/system/xbin/tty", "/system/xbin/tune2fs", "/system/xbin/umount", "/system/xbin/uname", "/system/xbin/uniq", "/system/xbin/unix2dos", "/system/xbin/unlzop", "/system/xbin/unzip", "/system/xbin/uptime", "/system/xbin/usleep", "/system/xbin/uudecode", "/system/xbin/uuencode", "/system/xbin/vi", "/system/xbin/watch", "/system/xbin/wc", "/system/xbin/wget", "/system/xbin/which", "/system/xbin/whoami", "/system/xbin/xargs", "/system/xbin/yes", "/system/xbin/zcat");
GabrialDestruir said:
Uhm... there'd be double app issues, Nook Color Tools Data and System Busybox in xbin and w/e you put it, Superuser in Data and System, anything else it should just overwrite.
Click to expand...
Click to collapse
In that case, can you put a few lines in to remove other versions?
Also, it may be a good idea to install non-AOSP APKs to /data/app for several reasons:
* users can uninstall unwanted apps
* updates to things like Superuser.apk will complain about over-writing "system applications"
* Ideally, vendor-supplied files *should* reside in /system, "user" stuff should go in /data (much like how file paths work in unix - /bin and /sbin vs /usr/sbin /usr/bin /usr/local/sbin /usr/local/bin etc...)
The lines are blurred here because we are also replacing missing vendor functionality, but the principal is the same - you will never see an update for framework.jar via the market so it's a non-issue there.
Just wanted to clear this up - I would prefer not to step on one-another if possible
Thanks, sorry I missed that. All worked as advertised. When I run Market, it doesn't have many apps, much less than before, not even Angry Birds.
buellwinkle said:
Thanks, sorry I missed that. All worked as advertised. When I run Market, it doesn't have many apps, much less than before, not even Angry Birds.
Click to expand...
Click to collapse
Thank you for that, seems there's an issue with the fingerprint or something else, will be looking into it.
HamNCheese said:
In that case, can you put a few lines in to remove other versions?
Also, it may be a good idea to install non-AOSP APKs to /data/app for several reasons:
* users can uninstall unwanted apps
* updates to things like Superuser.apk will complain about over-writing "system applications"
* Ideally, vendor-supplied files *should* reside in /system, "user" stuff should go in /data (much like how file paths work in unix - /bin and /sbin vs /usr/sbin /usr/bin /usr/local/sbin /usr/local/bin etc...)
The lines are blurred here because we are also replacing missing vendor functionality, but the principal is the same - you will never see an update for framework.jar via the market so it's a non-issue there.
Just wanted to clear this up - I would prefer not to step on one-another if possible
Click to expand...
Click to collapse
This his been the same setup for several versions of AutoNooter.
Gapps goes into system the same way it does on CM.
Superuser has gone in system/app because that's where the superuser zip would of put it.
Nook Color Tools goes into System so that it can switch keyboards (when you have more than one available and LatineIME.apk isn't there.).
There's no issue with framework.jar being updated anymore because this uses an ALTERNATIVE method for what framework was fixing.
Related
This is a custom recovery based on Cyanogen's recovery source with a lot of things added by me. The purpose of this recovery is to avoid using adb by accessing all features directly from the menu.
This recovery is for the HTC Nexus One only, if you have a :
- HTC Dream/G1 you should go here.
- HTC Magic/MT3G you should go here.
- HTC Hero you should go here.
- HTC Sprint Hero you should go here.
- HTC Eris you should go here.
- HTC Tattoo you should go here.
Important notes
Always check recovery.log before posting your issues!
You can do this by doing :
"cat /tmp/recovery.log" OR "cat /cache/recovery/log" right after you had the issue.
Use the "move log to sd" option in the "others" menu right after you had the issue. This will move the log to /sdcard/recovery.log so you can easily open it with a text editor.
Features
Use the trackball (up+down) to navigate through the menu, press the trackball to select items. Use the Volume-down key to go back to a previous menu.
Features
full ADB access in recovery mode
Alternative CM and JF version
Busybox v1.15.3
Kernel (2.6.35.7) with ext3 + ext4 support
SLCD and AMOLED support
HW-Key navigation (Trackball + Volume-key) option
Extended menu :
Reboot system now :: reboot your phone
USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
Backup/Restore
Nand backup :: Make a selective Nandroid backup
Nand restore :: Restore a Nandroid backup
Backup Google proprietary system files :: Makes a backup of the Google proprietary system files in /cache/google
Restore Google proprietary system files :: Restores the Google proprietary system files from /cache/google
Flash zip from sdcard.
Choose zip from sdcard :: Flash a zip update file from any (sub)-directory on your sdcard
Toggle signature verification :: Toggles the signature verification for zip files.
Wipe
Wipe ALL data/factory reset :: wipes /data + /cache + entire ext partition + all apps installed on your sdcard (froyo a2sd).
Wipe /data :: wipes /data.
Wipe /cache :: wipes /cache.
Wipe /sdcard/.android_secure :: wipes all apps installed on your sdcard (froyo a2sd).
Wipe /sd-ext :: wipes the entire ext partition on your sd (if present).
Wipe Dalvik-cache :: wipes the dalvik-cache located in /cache + /data + /sd-ext is present.
Wipe battery stats :: reset the battery calibration.
Wipe rotate settings :: reset the sensor calibration.
Partition sdcard
Partition SD :: Interactive SD partitioning
Repair SD:ext :: Repair the ext partition
SD:ext2 to ext3 :: Convert ext2 to ext3
SD:ext3 to ext4 :: Convert ext3 to ext4
Mounts
(Un)Mount /system
(Un)Mount /cache
(Un)Mount /data
(Un)Mount /sd-ext
(Un)Mount /sdcard
Other
Fix apk uid mismatches :: Does extacly that
Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
Power off :: Powers off your phone
Scripts available via adb :
Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start.
sdparted v0.6 : enter "sdparted" to start.
Install
Pre-Requirements :
Root
Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android). More info on this here.
via Rom Manager
Download "Rom Manager" from the Android market
Start "Rom Manager"
Select "Flash ClockworkMod Recovery" and wait for it to finish
Select "Flash Alternate Recovery" and wait for it to finish -> this will install the latest version of RA recovery.
via fastboot
Code:
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-passion-v2.2.1.img
via terminal app
Code:
Copy recovery-RA-passion-v2.2.1.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img(press enter)
reboot recovery(press enter)
How to boot in Recovery Mode
Boot the phone while holding down the VOLUMEDOWN-key.
Navigate to RECOVERY with the the VOLUMEDOWN-key.
Press the POWER-key to select.
Download
ALWAYS check the md5sum to make sure the zip isn't corrupted.
Latest version :
recovery-RA-passion-v2.2.1.img - MD5Sum: 3def709ab1c9e051a92a1c8b1504a36a
CyanogenMOD themed version :recovery-RA-passion-v2.2.1-CM.img - MD5Sum: e8262ae23943ce50fd346001812fae79
JesusFreke themed version : recovery-RA-passion-v2.2.1-JF.img - MD5Sum: e94484905a8f39d0985f14e2a5aea403
Previous versions :
recovery-RA-nexus-v2.1.1.img - MD5Sum: 2efdfa4c4adf386d5182c7b290d78c37
CyanogenMOD themed version :recovery-RA-nexus-v2.1.1-CM.img - MD5Sum: 413802bfab420b81946984da988a5be2
JesusFreke themed version : recovery-RA-nexus-v2.1.1-JF.img - MD5Sum: f5238022493deb434e594b36bf43ef02
Change-log :
v2.2.1
Nandroid backup is now selective, boot/system/cache/data are selected by default.
Nandroid checks if there's at least 500MB free on SDcard before starting a backup.
Added/updated error/warning messages.
v2.1.1
Fixed ext4 support in kernel! Update from v2.x if you are using sd-ext!
v2.1.0
Reduced recovery size by 800kb so it fits any hboot version to date :
Set Kernel compression mode to LZMA (33% smaller kernel)
Switched kernel debugging off
Removed : Networking support - Bluetooth subsystem support
Removed : Device Drivers - Misc device - AKM8973 Compass Driver
Removed : Device Drivers - Misc device - A1026 Voice Processor Driver
Removed : Device Drivers - Multimedia support
Removed : Device Drivers - MSM 3D Graphics driver for Adreno class GPU's
Nandroid now backups the entire content of /sd-ext , not just the apps. This fixes bootloops of certain restored roms.
Moved the "Toggle signature verification"-option from the Other- to the main flash-submenu.
Re-ordered the wipe menu.
v2.0.0
Some things in v2.0.0 were kanged with a twist from the Clockworkmod recovery.
Updated kernel to 2.6.35 (SLCD and AMOLED are now both supported).
Added SDEXT support for update scripts.
Added "filebrowser" support when you select a zip to flash.
Added "/.." support to the filebrowser so you can navigate up.
Added a mount menu so you can manually (u)mount stuff.
Added a toggle verification switch so you can flash those awesome unsigned winrar rom releases...
Fully re-wrote the wipe menu (it's not using a script anymore), added a few new wipe options.
Added "/sdcard/.android_secure" support , nandroid now backups/restores .android_secure (Froyo a2sd apps) by default.
Added a few new Google apps to the Google app backup script.
Special thanks to :
packetlss for all the hours of support and awesome coding skills, THANKS man ^^, donate to Haiti
Koushik Dutta for all his recovery work ^^
Cyanogen for his dedicated work! , buy him a beer!
Chris Soyars for the new Apps2SD method ^^
JesusFreke for his awesome JFv1.43's recovery , donate
pensive for adding awesome features to Nandroid
Bkmo for his utility script!
Devsk for his switchrom script!
51dusty for his sdparted script!
k4str0 for his fix_permissions v2.03 update.
Devsk, Dumfuq, Overground for creating BART
rikupw for the ideas and toggle_ums script.
http://www.androidspin.com for hosting ^^
[Recovery] [27-Dec-2010] RA-nexus-v2.1.1
Reserved for future use
Wow, great! hopefully the nexus one will get more love from the devs than the hero
please make this sticky @ mods
qvert said:
Wow, great! hopefully the nexus one will get more love from the devs than the hero
Click to expand...
Click to collapse
Who doesn't want a 1Ghz processor to play with?
how is this possible if the nexus one didnt even come out yet?? lol
damn you are fast amon...i hope to have the phone asap
Amon_RA: I love this dude in a manly way. This guy is quick!
Keep up the good work amon, looking forward to flashing this asap.
i'm so psyched that the devs are jumping on the N1 so quick. I foresee lots of good dev work ahead for this apparently awesome phone. can't wait to see what comes of it.
j.books said:
i'm so psyched that the devs are jumping on the N1 so quick. I foresee lots of good dev work ahead for this apparently awesome phone. can't wait to see what comes of it.
Click to expand...
Click to collapse
Exactly, already rooted AND now a niice recovery . Nice work man, cant wait for the phone to come in !!!
THANK YOU!
LOL Amon_RA, you are faster than sound!...
Greetz
Andfreek!
Thanks to the devs!!!
Thanks guys for all your work!!!!!! Can't wait to get my Nexus One!!
Amon_Ra Please help us with our HTC Droid Eris, We have not been able to get root.
Nice image thanks!
Awesome, lookin forward to getting my N1 to try this on
Good lord man I just ordered mine and you already got a recovery made?? Great job man!
Bigup!
Nice work Amon..
Awesome job!
NICE, amazing work as always and you seemed to have mastered time travel this time around
Are the touch sensitive buttons hard to code for or did I just overlook that, it seems as if they are not available from reading the feature list
I would love it if you could add HOME = Accept / BACK = Cancel
Can't wait to get my Nexus tomorrow, the future looks bright, blinding even
now time to kill some time, going to see Laker game live
OMG FLASHING NOW!
I got some goodies coming up too!
IRC on freenode: #sk8erwitskil
NEW: I have created a script to easily update to the latest version of my recovery.
- Download this file ----> updater.sh
- Put it on your sdcard
- open adb and type:
Code:
su
sh /mnt/sdcard/updater.sh
- it will reboot you into recovery and automatically install recovery and reboot
- only ATT version is supported right now
- must be on at least v14.4.7 for script to work
Click to expand...
Click to collapse
Here is a video of how it works: --------> YOUTUBE LINK
Flashable zip:
cwm6027touch_v14.4.7_geeb.zip: ---------> DOWNLOAD
Click to expand...
Click to collapse
Thanks to :
gweedo767 (for creating the original touch recovery)
koush (for creating CWM)
PhilZ (for his amazing improvements and help with applying universal touch code) BIG THANKS!
PREVIOUS VERSIONS:
Code:
v1:
[CODE]initial release
v2:
Code:
- updated to latest version of clockworkmod
- add reboot download option
- add reboot recovery option
- add power off option
- change font size
- add various internal/external sdcard options from cwm 5.5.0.4 touch recovery
- change order of internal/external sdcard so internal comes first on backup/restore/install
v3:
Code:
- add support for phones that sdcard mounts as external_sd
- fix the line below the menu to actually be below the menu
- clean up the "andy the android" picture. (if you make a backup you will see that the picture in the background has been poorly edited. there are bits of black spots around him)
- JellyBean Background
v4:
Code:
- fixed missing slash that was not allowing installs from external sdcard
v5:
Code:
- update to latest version of CWM 6.0.0.8
v6:
Code:
- updated to latest version of CWM 6.0.0.9
- added ability to delete nandroids from recovery (in backup and restore menu)
- changed order of internal/external so external comes first
- fix timestamp creation on backups
v7:
Code:
- updated to latest version of CWM 6.0.1.0
- fixed bug that would not allow backup of /system
v8:
Code:
- update to latest version of CWM 6.0.1.1
- allow customization of backup format (dedupe/tar)
- use minizip tool instead of e2fsck, etc.
- more....
v9:
Code:
- update to latest version CWM 6.0.1.2
- fixed bug where backing up to external wouldnt backup /emmc/.android_secure
- ADDED DUAL LUNFILE SUPPORT! (thanks to topprospect for this!)
-- what this does is when you mount USB storage you
will see both of your sdcards mount at the same time
- various /emmc fixes (recovery now looks for all clockworkmod "." files in /emmc instead of /sdcard)
- this is useful for people who dont use an external sdcard at all
v10:
Code:
- grabbed latest commits to official CWM 6
- added new extras menu (look in 2nd post for info)
- some other stuff i dont remember
v11:
Code:
- fixed hide nandroid progress bug (it now works)
- added sk8's fix permissions option (logging is disabled so it runs faster and it also clears stale data directories)
- fixed bug where normal fix permissions wouldnt create a log to correct location
- cleaned up some syntax
v12:
Code:
- added darkside wipe/super wipe built in
- added aroma file manager built in
- added ability to backup/restore the /efs partition
- cleaned up oneconfirm/hidenandroidprogess features to be one menu item
- more......
v12.5:
Code:
- fixed bug where darkside cache scripts wouldnt work
- added option to create a custom zip (read 2nd post)
v13:
Code:
- report log gets copied to /emmc instead of /sdcard
- add support for roms without busybox (stock roms) to create a custom rom zip
- add support for openrecoveryscript (read [URL="http://forum.xda-developers.com/showpost.php?p=31093552&postcount=344"]THIS[/URL])
- add support to choose a custom created openrecoveryscript
- use goo-manager to flash roms and create openrecoveryscripts
- now detects where android_secure is automatically
- fix ors-mount.sh to work even if 'sdcard' is in the path
- misc code cleanups.....
v13.1
Code:
- bug fixes
- android_secure fixes
v13.2
Code:
- that pesky android_secure - bugfixes for restoring android_secure
v13.3
Code:
- updated to latest 6.0.1.4
- some bugfixes
- added option to select where android_secure lives (hopefully this is the last time. i promise)
v13.4:
Code:
- updated aroma file manager to latest version
v13.5:
Code:
- add initial support for whole-device encryption (thanks topprospect)
v14:
Code:
- updated to latest CWM 6.0.1.5
- fixed some mtdutils issues
- added a bootanimation changer
v14.1:
Code:
- not released
v14.2:
Code:
- added bootanimation change selection from external sdcard
- added newest aroma filemanager w/ console support (you can use terminal in recovery)
- updated to latest changes of official CWM
- added support for Android 4.2
- zip file now installs updater.sh to your internal sdcard
- updated updater.sh to fix typo
v14.2.1:
Code:
- openrecoveryscript automatically runs if script is found in /cache/recovery/
- this is good for using my updater.sh or goomanager
v14.3
Code:
- skipping this number to keep in line with my other devices
v14.3.1
Code:
- lots and lots of under the hood improvements
- re-wrote OpenRecoveryScript and efs backup/restore code
- these work alot better now (thanks so much to PhilZ for his amazing help)
- add option to backup/restore boot.img from sdcard
- now using latest stable kernel
- completely re-wrote the touch code for some improvements
- now to select you tap anywhere on the screen
- fixed some typos
- made my source code universally compatible with all phones using ICS or greater
- compiling in jellybean base recovery code now
Code:
v14.4
- fixed soft keys (virtual keys on bottom) (credit to PhilZ for this)
- reverted back to swipe to select
- tweaked some features in the extras menu
Code:
v14.4.1
- messed up on the mount points so i fixed them now
- added some buffer to fix ability to accidentally select wrong item
Code:
v14.4.5
- skipped some versions because they were made for other phones
- re-wrote the create custom backup feature to be universal now with all phones/roms (thanks to PhilZ for the help)
- added new settings menu
- add ability to change timezone
- added /preload support [B](must go and enable it in misc nandroid settings)[/B]
- add rom name to nandroid names
- more i just cant remember now....
Code:
v14.4.6
- added exFAT support
- some under the hood optimizations
[/CODE]
Current Version:
v14.4.7
- added extras>>misc nandroid settings>>disable assert check
- removed black space in error icons
- some under the hood optimizations
- added updater.sh script
Click to expand...
Click to collapse
Major update to how touch works now:
UP - swipe finger up on screen
DOWN - swipe finger down on screen
SELECT - swipe finger from left to right
BACK - swipe from right to left
SOURCE: https://github.com/sk8erwitskil/touch_recovery_cm10.1
This is what the new dedupe format does. This is a direct quote from the original creator of clockworkmod:
Code:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard(or emmc)/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Whats in the extras menu?
- change bootanimation (this lets you select a bootanimation form your internal sdcard. it backs up your current bootanimation to /{internal sdcard}/clockworkmod/ba_backup/. it only backs up the original bootanimation so if you keep changing your bootanimation you will still only have your original one in ba_backup.)
- enable/disable one confirm (this makes it so you only have to scroll through one confirm selection when installing something instead of having to go through 10 of them to click yes)
- hide/show backup & restore progress (this makes it so the progress bar when you backup/restore doesnt show up and makes backups/restores a bit faster since it doesnt have to show you the progress and files its backing up)
- select android_secure on internal/external (use this to select where you have .android_secure. default is internal, so if you have it on external make sure to choose this once to set it up)
- aroma file manager (file explorer)
- create custom zip (this will create a custom rom from the currently installed files you have on your phone. it takes your /system partition and /boot partition and makes them into a zip file ready to be flashed. the end product will be in clockworkmod/custom_rom/. this has recently been fixed to work on all phones/roms
- choose custom openrecoveryscript (read THIS)
- recovery info (shows the version of recovery and the build date)
- Special Backup & Restore (backup and restore your kernel/boot and /misc partitions)
- Misc Nandroid Settings (change time zone, turn preload support on/off (default is off), enable md5 checking, disable assert check)
i dont actually have my LGOG yet. it comes on monday. once i get it tho i should be able to have a completely stable build in less than a week
it doesn't work although it flashes successfully all I get is a kernel crash, tried manually booting into recovery and adb reboot recovery no dice. btw I am rooted with an unlocked bootloader.
sk8erwitskil said:
i dont actually have my LGOG yet. it comes on monday. once i get it tho i should be able to have a completely stable build in less than a week
Click to expand...
Click to collapse
are u gonna work on roms for this phone
Sent from my LG-E970 using xda premium
sk8erwitskil said:
i dont actually have my LGOG yet. it comes on monday. once i get it tho i should be able to have a completely stable build in less than a week
Click to expand...
Click to collapse
Glad to see you here in the OG forums! Thanks for working on this!
Ok got it to work. I can create a fakeflash that you flash in your current cwm. All touch code is working great which is the hardest part
I'm gona have to make some ramdisk edits to make an installable recovery.img. hopefully iomonster gets back to me on how he fixed the ramdisk to get it booting
Sent from my LG-E970 using xda app-developers app
sk8erwitskil said:
Ok got it to work. I can create a fakeflash that you flash in your current cwm. All touch code is working great which is the hardest part
I'm gona have to make some ramdisk edits to make an installable recovery.img. hopefully iomonster gets back to me on how he fixed the ramdisk to get it booting
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
You can probably just add etc and default.prop from IO's image to the mako cwm touch.
Sent from my SPH-D700 using Tapatalk 2
got it working great. just uploaded now.
Just installed on e973, works well, looks nice. Thanks for your work.
Installed on my E973 and work nice too. Thanks for the work. If you could add a bit more space between menu item, it would be perfect. I have big finger
Gr8 stuff sk8. Only problem i found is the md5 mismatch bug (it doesn't create an md5sum while creating backups). No biggie, but if it's easily fixed it'd be nice to not have to make an md5 manually every time.
Also curious if it's possible to change the font. Thanks!
chadouming said:
Installed on my E973 and work nice too. Thanks for the work. If you could add a bit more space between menu item, it would be perfect. I have big finger
Click to expand...
Click to collapse
Yah this isn't a final product at all. I will be making more updates soon. And this is one of them
carrett said:
Gr8 stuff sk8. Only problem i found is the md5 mismatch bug (it doesn't create an md5sum while creating backups). No biggie, but if it's easily fixed it'd be nice to not have to make an md5 manually every time.
Also curious if it's possible to change the font. Thanks!
Click to expand...
Click to collapse
Hmm I've never encountered this bug and ive been using this exact recovery on my other devices for a long time. Can you create a backup and pull /tmp/recovery.log when you do?
Sent from my LG-E970 using xda app-developers app
I'll have an update tomorrow that fixes the background and font sizes and a few other features.
Sent from my LG-E970 using xda app-developers app
sk8erwitskil said:
I'll have an update tomorrow that fixes the background and font sizes and a few other features.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
nice, I always favor the touch recoveries it make navigating thru the menus so much easier without having to mash the volume/power keys all the time :laugh:
Any chance you could make this a flashable zip?
davideholland said:
Any chance you could make this a flashable zip?
Click to expand...
Click to collapse
Yes I will do that.
Sent from my LG-E970 using xda app-developers app
I second the flashable zip. Tried the other methods and have failed for some reason
Sent from my LG-E970 using xda app-developers app
Will this work on the sprint version too?
Sent from my LG-LS970 using xda app-developers app
Has the MD5 issue been fixed in the release yet? I saw it mentioned but I didn't see any posts that stated it was fixed in the current release. Thanks for the clarification.
Guys I know that many of you have been having trouble with installing exposed on your One x+. This is what I did to get it working:
Before we begin I must note that you MUST start clean. No Data, No ROM and Wipe Dalvik.
1. In the recovery find the cm rom on your sd card and install it.
2. Then find the Paranoid Android Gapps and install the as well.
3. Then Wipe cache and reboot into boot loader.
4. Flash the kernel and reboot into your ROM.
5. After the setup process get the Xposed.apk file and install.
6. Go into the app, Install the Framework, BUT DON'T REBOOT!!
7. Exit the app.
8. Change SELinux to Permissive. ( I used SELinuxModeChanger from the play store to change it)
9. After you changed it go into Terminal Emulator and type in these commands
a. su
b. mount -o remount,rw /
c. mount -o remount,rw /system
d. restorecon /system/bin/app_process
10. Now you can reboot!
11. Done and have fun modding your device!
Dalvik still alive: cm-11-20160612-NIGHTLY-enrc2b.zip
Battery friendly
If some are interested, you can build latest nightly 20160612 cm11 +3originals:
- mar-V-in fake signature for nogapp (github .com/microg/android_packages_apps_GmsCore/blob/master/patches/android_frameworks_base-KK-LP.patch;
- inverted broken xposed & SELinuxModeChanger from d8130142.diff (cm 20151109 review.cyanogenmod .org/#/c/118800/);
- wakelockblocker cherry-picked from crdoid 4.4 (github .com/crdroidandroid/).
Your build will, keep same CVE as the official one and, stay untouched apart +3 above.
For xposed only correction; get 2 files from ORIGINAL cm-11-20151108-NIGHTLY-... or any unofficial CMbased,before 20151109, for your device; then xposed(+1reboot?) AND SELinuxModeChanger.apk will both work back:
system/bin/app_process
system/lib/libandroid_runtime.so.
Wakelock Blocker for Official 2016, Nightly CM11 (and many more...wip)
I will be glad, if some could report a checked OK with BetterBatteryStats_2.1.0.0 or Wakekock Detector /device, in my thread.
Thanks in advance, and re-joy your battery & privacy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YOU MUST BE ON THE HAIRYBEAN 2.31 JB 4.2.1 BOOTLOADER VERSION 10.6.1.27.1 AND TWRP 2.8.0.0.+ OR CWM 6.5.0.0+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE
You must do a full wipe in recovery if coming from another ROM. Do not do a full wipe from the bootloader. Don't forget to do a Nandroid Backup first and give the ROM 15 mins to stabilise! The first boot will take 15 minutes!
Features and Tweaks
This ROM is based from OMNI AOSP sources
Supports EXT4 and F2FS Data partitions
Based off omni-5.1.1-20150508-zombi_tf300t-KANG source by lj50036/hardslog
Full Aroma Installer for main rom including choice of 4 kernels and ROM2SD/DATA2SD/F2FS support
Remixed _thatv11 kernel with OMNI ramdisk - repacked by sbdags
Grimlock kernel with OMNI ramdisk and _that init - by hardslog
DPI Size: 160 (TF300 recommended small fonts), 240 (Stock fonts), 224 (Medium fonts) & 200 (Small fonts), 180 (Tiny fonts) & 160 (Specsavers fonts)
Launchers: Omni, Google Experience Launcher, Apex , Nova
Boot Animations: ZOMBi-POP, Android-L, Nexus Phase Beam
Gapps (updated by me to Google latest apks and libs)
Misc Apps: ESFile Explorer, Adobe Flash, AdAway, Titanium Backup, Keyboard Manager
Tweaks: File system and performance optimised, Init.d support, Zip Align, Force GPU Rendering, Browser2RAM
Continued Best Support of any ROM!
Warning - experimental tweaks
[*]Option to enable / disable data journaling on /data during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Option to enable / disable fsync during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Tip 1: Go to Settings - About Tablet, Click build number 7 times
Now you will see Developer Settings & Performance menus
Bug List
[*]No Floating windows yet
Change Log
20150728 ZOMBi-POP RC1 changes
- RELEASE CANDIDATE 1!
- Fixed the problem with ROM2SD and DATA2SD not working correctly on beta 4
- Added SuperUser and Secure Kernel as options to the installer (Turn these off for work wifi or watching sky go, etc)
- Added dock battery icon as an option to the installer under tweaks
- Fixed partitions not getting unmounted correctly for tuning during installation
- Fixed WiFi across the unified bases for TF700/TF300/TF201
- OmniSwitch now working - thanks hardslog
- Tidied up some installer messages
- Google play services updated to unified version for all devices
- Updated Google Maps to version 9.12.0
- Updated Google TTS to version 3.5.6
- Updated Google Calendar to version 5.2.2-98195638
- Updated YouTube to version 10.28.59
- Updated Apex Launcher to version 3.1.0
20150723 ZOMBi-POP Beta 4 changes
- Unified Aroma installer for TF700/TF300/TF201
- Rebased from omni-5.1.1-20150718-zombi_tf300t-KANG maintained by lj50036, hardslog, sbdags
- Merged source from omni-5.1.1-20150718-zombi_tf700t/tf201t-KANG maintained by lj50036, hardslog
- Updated all kernels and modules to the unified versions - thanks lj50036
- Added inverted kernel for TF201 users
- Aroma re-written to allow multi device selection and detection
- Additional tweaks added from TF701 Zombi-pop
- Amended SuperSU installer script to give correct permissions and install locations
- Reverted to latest Banks Gapps - means another wipe - sorry!
- Updated Google Calendar, Google Mail, Google Hangouts, YouTube, Google Search & Google Maps to latest versions
- Updated ESFile Explorer and Nova Launcher to latest versions
- Added flashable zip to enable dock battery - NOTE - this means you can't change the battery icon
20150119 ZOMBi-POP Beta 3 changes
- Rebased from omni-5.1.1-20150508-zombi_tf300t-KANG maintained by lj50036, hardslog
- Repacked Grimlock kernel for 5.1.1 (Grimlock lite is still using 5.0)
- Retweaked some File System and Virtual Memory parameters - focus on smoothness and battery
- Added Aroma code to remember previous selections as well as offer various installs
- sbdags best auto install, omni default auto install, previous options and previous auto install
- Viper4Android sound enhancer updated to lollipop version + updated the audio_effect.conf file
- Updated Google Play Store to version 5.5.8
- Updated Google Play Services to version 7.3.29
- Updated Google Search to version 4.5.13.19
- Updated Google Maps to version 9.8.1
- Updated Google Hangouts to version 3.2.91698097
- Updated Google Play Music to version 5.9.1854R
- Updated Google Calendar to version 5.2-91668080
- Updated ESFileExplorer to version 3.2.5.1
- Fixed swipe gestures on google keyboard
- Fix for Battery Drain on Google Play Services
- Removed Titanium Backup from the zip file
20150422 ZOMBi-POP 5.1 Beta 2 changes
- Rebased from omni-5.1.1-20150422-zombi_tf300t-KANG maintained by lj50036, hardslog
- New base is from OMNI 5.1.1 merged by lj50036
- Browser History is back again! Thanks lj50036 or Hardslog
- You can now choose to install, no GAPPS or minimal GAPPS (just playstore and syncs)
- Updated Google Maps to version 9.7.1
- Updated Google Search to version 4.4.11.16
- Updated Google Mail to verison 5.1.90765967
- Updated Google Calendar to version 5.2-90091543
- Updated Google Hangouts to version 3.1.89134953
- Updated Google Text-to-Speech to version 3.4.6.1819666
- Updated YouTube to version 10.14.56
- Updated ESFileExplorer to version 3.2.5
- Updated Android Terminal to version 1.0.70
- Updated Banks Gapps:
- Google Play Services 7.3.28 (1863718-438)
- Google Play Store 5.4.12
- fixed OC on Some TF201's running Grimlock-lite
20150119 ZOMBi-POP Beta 1 changes
- First public release
- Added Linrao Grimlocks kernel (needs more testing)
- Fixed auto-rotate (Thx hardslog)
- AOSP browser materialized (green)
20150119 ZOMBi-POP Alpah 4 changes
- New name - new logo! ZOMBi-POP
- Rethemed Aroma to new ZOMBi-POP theme
- Added 2 optional beta tweaks for testing (screen and kernel)
- Fixed _thatv11 kernel option
- Added Grimlock v5.0 (not tested)
20150118 Lollipop Alpha 3 changes
- Updated to latest OMNI Lollipop source omni-5.0.2-20150117-zombi_tf700t-KANG maintained by lj50036
- Fixed issue with AOSP Browser getting installed when not selected
- Fixed issue with Live Wallpapers getting installed when not selected
- Fixed issue with Launcher3 getting installed when not selected
- Fixed issue with Terminal not getting installed when selected
- Fixed issue with DSPManager still getting installed when Viper4fx is installed
- Removed stock calendar as google app one is far superior
- Fixed init.d scripts not running due to wrong permissions and wrong ramdisk init.rc call
20150117 Lollipop Alpha 2 changes
- Updated system and data apps to use new lollipop structures
- Updated all apps to latest versions
- Removed xposed as not compaitble with lollipop
- Tweaked the force gpu options
20150111 Lollipop Alpha 1 changes
- Updated to latest OMNI Lollipop source maintained by lj50036
- New PA GApps Lollipop version 2015
- Initial Beta test build to see what works and what doesn't
Click to expand...
Click to collapse
The Team
@sbdags - Creative Mastermind (From CROMi-X/CROMBi-kk/ZOMBi-X ROMS)
@lj50036 - Source Guy (From CROMBi-kk/ZOMBI-X ROMS)
@hardslog - The Canadian (From Grimlock ROMS)
Credits
Google
Omni Team - Thanks!
@_that For all the great advice, watching over us and fixing everything we break!!!!!
All the beta testers for your patience and feedback : fatboyinlycra, berndblb, drewski_1, duckredbeard, keshavmot2, corb06, jmaybush, JoJoDaClown, kansasboy001, TrofeoSC
To Do
Fix loads of stuff!
XDA:DevDB Information
ZOMBi-POP, ROM for the Asus Eee Pad Transformer Prime
Contributors
lj50036, hardslog, sbdags, _that
Source Code: https://github.com/zombi-x-lp
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
ROM Firmware Required: JB Ending with 27.1 or 27.5 bootloader
Based On: OMNI AOSP
Version Information
Status: Stable
Current Stable Version: 20150728 RC1
Stable Release Date: 2015-07-28
Current Beta Version: 20150723 Beta 4
Beta Release Date: 2015-07-23
Created 2015-01-30
Last Updated 2015-07-27
Reserved
UPGRADE INSTRUCTIONS
Steps
1. Refer to the bottom of post #3 UPGRADE FROM STOCK BOOTLODER
2. If you haven’t yet, unlock your TF201 by following these instructions.
3. Install the latest version of Team Win Recovery Project (TWRP) 2.7+ or ClockWorkMod Recovery 6.0.5.0+ Note this ROM will NOT install with older versions of recovery!
TWRP HOME
Download the recovery file from above, put it into the same folder where you have adb and fastboot files. Please rename it to twrp.blob or cwm.img and follow the instructions below:
Code:
adb reboot bootloader
To flash the recovery:
Code:
fastboot -i 0x0B05 flash recovery cwm.img
or
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
A blue bar will go accross the screen on the tab and the command prompt will indicate it was successful in about 10 seconds
Then reboot the tablet either back to the bootloader or to android to complete
Code:
fastboot -i 0x0B05 reboot-bootloader
fastboot -i 0x0B05 reboot
You can now access the recovery by pushing [volume up] on the RCK icon in the bootloader screen
Click to expand...
Click to collapse
FLASHING THE ROM FROM RECOVERY
Steps
1. Download the ROM below and save to your internal or external SD Card. Do not unzip the file.
ZOMBi-POP ROM DOWNLOAD
Note: The first boot after install will take 15 mins whilst everything is built. Some people might think it is looping but it is not. The ROM also takes about 15 mins to stabilise after the first boot
ZOMBi-POP RC1 LP 5.1 Full Mirror 1
ZOMBi-POP RC1 LP 5.1 Full Mirror 2
MD5 Sum: e3980e1bffa539e676ac1269268abcd1
Flash this patch please as there is a file missing that gives better performance
RC1 Performance Patch
MD5 Sum: 4fbf9d5f934fa40a6e33ac409f703fcd
FILES ARE SIGNED. IF YOU ENABLE SIGNATURE VERIFICATION IN RECOVERY IT WILL VALIDATE THE FILE BEFORE FLASHING.
ROM2SD/DATA2SD USERS PLEASE READ!
ROM2SD only works if you have ZOMBI-POP, ZOMBi-X, CROMBi-kk, CROMi-X or miniC flashed on internal with a THATv10+ kernel. Just choose ROM2SD in the installer of ZOMBi-POP to flash it to ROM2SD and the installer will do the rest.
- Install ZOMBi-POP and choose ROM2SD or DATA2SD install
The ROM2SD1.zip below is only needed if you need to switch your recovery to between normal and rom2sd mode. For Example you want to backup or restore a rom2sd installation. Flash once to go rom2sd and flash again to go back to normal. A reboot always puts you back to normal. Thanks to _that!
ROM2SD1.zip Download Mirror 1
ROM2SD1.zip Download Mirror 2
MD5 Sum: 7b699136d59ea3d5538570ccaf422acf
The DATA2SD1.zip below is only needed if you need to switch your recovery to between normal and data2sd mode. For Example you want to backup or restore a data2sd installation. Flash once to go data2sd and flash again to go back to normal. A reboot always puts you back to normal.
DATA2SD1.zip Download Mirror 1
DATA2SD1.zip Download Mirror 2
MD5 Sum: 9d5e9e2fd32593f981624499b37924b2
2. Boot to recovery – Either choose Boot to Recovery from the Power Menu if available on your current ROM or from the tablet power off hold the [volume down] button and press the [power] button. Once your see the flashing RCK icon, press [volume up] to select. If another icon is flashing use [volume down] to move between icons.
3. Using your recovery make a Nandroid Backup of your current setup
4. Select install and navigate to where you saved your ROM zip file.
5. Choose the ZOMBi-POP zip file and follow the on screen prompts to customize your installation.
6. Reboot and enjoy.
Using GParted to setup a micro SD for ROM2SD or DATA2SD!
First and foremost - DO NOT USE MINI TOOL!
Formatting a micro sd card for ROM2SD
Note for DATA2SD just do one partition in stead of 2
We will be using a GParted Live boot USB and a FAST good quality micro sd like a Sandisk or Samsung Class 10 - SDHC/SDXC UHS-1 card with read speed of at least 20MB/S. If you have a cheap chinese eBay card don't bother - they are not good enough.
You will also need a USB Stick with at least 1GB size. Note this process formats the USB disk so don't keep any important files on it. It will also wipe your micro sd so make sure you are prepared.
1. Go to the link below and download the GParted Live CD/USB/HD/PXE Bootable Image and save it somewhere you remember
http://gparted.sourceforge.net/download.php
2. Download Linux Live USB Creator and install it
http://www.linuxliveusb.com/
3. Fire up LiLi USB Creator:
a. Choose your USB key - I,e, the drive letter for your USB (not sd card)
b. Choose your GParted iso image for the source
c. Choose the check box to Format Key in FAT32 and hide files
d. Click the lightning bolt to create
4. Now you have a bootable disk you need to boot from it. You may need to alter you BIOS Settings on your PC to boot from a USB Stick but mine did it without messing.
5. Insert your micro SD card into an SD Card adapter and insert into PC
6. Boot into GParted
7. Choose Gparted Live <Enter>
8. Don’t touch keymap <Enter>
9. Languge <Enter>
10. Start Gparted Automatically
11. Change device to your micro sd )it will default to you hard disk - hda– mine is /dev/sdc
12. Delete all existing partitions
For a 64GB card: (resize as needed but /system doesn't need to be bigger than 1GB)
13. Create new, always select primary: do this 3 times.
14. FAT 32 : Size 16GB – this will be /dev/sdc1 in gparted and will be your sdcard for storage in Android
15. EXT4 : Size 42GB – this will be /dev/sdc2 in gparted and will be your /data partition in Android
16. EXT4 : Size 1GB – this will be /dev/sdc3 in gparted and will be your /system partition in Android (not needed for data2sd)
Apply, wait until it finishes and then reboot. Remember to remove the usb stick
*Images stolen from elsewhere as I couldn’t get it to save mine
Now you are ready to install ROM2SD. Note if you want to use DATA2SD then only do 2 partitions 1x FAT32 and 1x larger EXT4
Then reinstall ZOMBi-POP but this time choose the ROM2SD / DATA2SD option
Reserved
All,
The ROM is still in BETA and by flashing it you are helping the BETA Testing process
It may still have some bugs, spontaneously reboot, drain the battery faster or heat up a bit. The aim is to make it better and fix them.
If you find a bug and want to report it here please post a logcat (after it occurred) with a description of what you were doing at the time and the rough timing in the logcat to look at (these things get huge!).
You can also post a dmesg which is the kernel boot logs and can indicate issues with data corruption or hardware.
If you get a reboot then please post a last_kmsg from the /proc folder.
How to get a logcat
How to get useful logs
Thank you!!
Join us on IRC for a chat or if you have questions:
https://webchat.freenode.net/
Channel: #zombi-x
There is no Q&A section for this rom as it is still in dev so you are ok to post your questions here!
UPGRADE FROM STOCK BOOTLODER
This may help
Starting from a stock bootloader V 10.4.2.18
What you will need
Woking fastboot & adb / SDcard optional
TWRP for a 201 = twrp_tf201t.blob
TWRP for the 300 = twrp_tf300t.blob
HairyBean BL & TWRP: This is effectively turn your 201 into a 300 <---- which is a flashable zip inside the zip that you downloasd
All 3 of the above file are in a zip in the Download section @ the top of every page of the thread ...... THIS ZIP IS NOT FLASHABLE...Your must unzip it to get to the real files !!! The name of this zip is
upgrade_tf201_to_tf300t.zip
foo 201 ROM zip
A fully charged tablet
All the above files in the same directory as your fastboot.exe (if using windows) In your home folder on linux....
The process
Lets start with the TWRP recovery for the 201, let flash it with fastboot...
Power your tablet off and with the [ VOL DOWN & POWER ] buttons boot the tablet into the bootloader
Once there [ VOL DOWN ] untill the green box is on the USB ICON then [ VOL UP ] to select fastboot
Let make sure your PC can see your tablet with this command.
Code:
fastboot devices:
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
Then
Code:
fastboot -i 0x0b05 reboot-bootloader
[ VOL UP ] ON RCK to enter recovery
Once in TWRP check to see if adb is working...
Code:
adb devices
Ok now that we know that is working let go ahead and push the HairyBean BL onto the tablet
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now under the install tab in TWRP fine the folder and flash it....
reboot once it has fishined..If ask to install SuperUser say NO..........
LET THE BLUE BAR FILL !!!!!!!!! Once it has finished it will reboot into Hairybean TWRP....
Once booted into recovery, run this command to boot into fastboot
Code:
adb reboot-bootloader
You will see that the USB icon is missing now, this is good... If you still see the USB icon DON'T go to the next step
Now lets flash TWRP recovery
Code:
fastboot -i 0x0b05 flash recovery twrp.blob
Once that has finished let reboot into bootloader
Code:
fastboot -i 0x0b05 reboot-bootloader
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Now lets push foo.zip onto your tab
Code:
adb push foo.zip /sdcard
Find it under the install tab and flash it..
REBOOT into android, first boot can take up to 15 minutes
Downloads failing for me
terrigan said:
Downloads failing for me
Click to expand...
Click to collapse
Data is it really you....
Working here ....
No idea why it would be broken, mirror 2 will be up soon.....
Thx Josh
oh man! ... was waiting for L version for my old TF201
and very, very and I mean very happy to see You guys are working on this for our beloved TF201's
lj50036 said:
UPGRADE INSTRUCTIONS
Steps
1. If you haven’t yet, unlock your TF201 by following these instructions.
2. Install the latest version of Team Win Recovery Project (TWRP) 2.7+ or ClockWorkMod Recovery 6.0.5.0+ Note this ROM will NOT install with older versions of recovery!
CWM Touch XDA Thread
CWM XDA Thread
TWRP XDA Thread
Download the recovery file from above, put it into the same folder where you have adb and fastboot files. Please rename it to twrp.blob or cwm.img and follow the instructions below:
[/HIDE]
Click to expand...
Click to collapse
no links at all .... You forgot 'em or ?!?
specially interested in TWRP
terrigan said:
Downloads failing for me
Click to expand...
Click to collapse
Full Mirror 2 @AndroidFileHost downloaded in less than a minute
Could someone please post step by step tutorial how to install this rom?
I have a cm11 unofficial rom/ android cardhu-user bootloader 1.00e released by ww_epad- 10.4.2.15-20120917 A03
and cwm rck v6.0.5.0
when i install this rom it just boots up to screen with penguins and after a while reboots
Sneaky bugger
Thank you very much team!!!!!
I would very much like to test out your rom, but there seems to be a problem with the links for the twrp and cwm recoveries provided by you. Clicking them leads me nowhere. I seem not to be able to find the proper twrp recovery 2.8 for our device. Could you please repost the links? Thank you very much
I am running Lollipop with my beloved Prime....:victory:
Have been lurking this fora and have been running Omni 4.4.4 for a while.
Took the step to this beauty....
- The default Omni kernel is broken with wifi
-Flashed with the Grimlock option but it messes up partition??? Low internal space.
- Wiped a factory reset and it works.....
Playing around but no power left, must charge....
lj50036 said:
YOU MUST BE ON THE HAIRYBEAN 2.31 JB 4.2.1 BOOTLOADER VERSION 10.6.1.27.1 AND TWRP 2.8.0.0.+ OR CWM 6.5.0.0+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE
Click to expand...
Click to collapse
Sakeus said:
Could someone please post step by step tutorial how to install this rom?
I have a cm11 unofficial rom/ android cardhu-user bootloader 1.00e released by ww_epad- 10.4.2.15-20120917 A03
and cwm rck v6.0.5.0
when i install this rom it just boots up to screen with penguins and after a while reboots
Click to expand...
Click to collapse
if you look at the first few lines from the OP, you will see that you are apparently on the wrong bootloader. you need the Hairybean JB 4.2.1 bootloader. you can find that here: http://forum.xda-developers.com/showthread.php?t=2407248 you also need to upgrade/update your recovery. once you do those things, then you can flash this. (i'm surprised you haven't softbricked...)
Lj50036 you killing me lol just yesterday ive flashed the tf300 version of zombiepop you posted to check it out and now i come here and found a version for tf201 haha needless to say im formating my tablet and installing this righ now thank you!
pikul said:
Lj50036 you killing me lol just yesterday ive flashed the tf300 version of zombiepop you posted to check it out and now i come here and found a version for tf201 haha needless to say im formating my tablet and installing this righ now thank you!
Click to expand...
Click to collapse
unless i'm not reading something correctly, i think the dl links are for the same tf300t rom - it's just being posted here because it's compatible with the tf201??
huskerkate said:
unless i'm not reading something correctly, i think the dl links are for the same tf300t rom - it's just being posted here because it's compatible with the tf201??
Click to expand...
Click to collapse
Yes its true....
More to come if there are issue....
Thx Josh
lj50036 said:
Yes its true....
More to come if there are issue....
Thx Josh
Click to expand...
Click to collapse
...and i should have added that not only is it compatible with the tf201, it is running quite nicely! definitely more fluid and responsive than the other LP tf300 rom i had on this thing.
thanks!!! :good:
huskerkate said:
unless i'm not reading something correctly, i think the dl links are for the same tf300t rom - it's just being posted here because it's compatible with the tf201??
Click to expand...
Click to collapse
I wiped my tablet and realized that later lol anyways did a fresh install again xD
lj50036 said:
Yes its true....
More to come if there are issue....
Thx Josh
Click to expand...
Click to collapse
Hi, Josh don´t know, what I did (what went) wrong but I´ve installed the Zombi-pop about week ago, bud I had some issues with some apps stability and reboots, and needed tablet for daily use so I ve restored nandroid of 4.4.
This weekend I do have some mor time so I´ve did a clean install of Zombi-pop and got a message about low memory space. Don´t know why - installed Zombi pop twice before without hiccups - first with your+ _that´s overclocked kernel , second time with your + sbdags´es kernel - both ok. This time with hardslog´s 5.0 linaro kernel I got the low memory message... any clue???? THX 4 answer. Nandroid backup of 4.4 . is OK again... Maybe too much gapps installed - I knoow KatKiss 5.0 had that problem????
JuraP said:
Hi, Josh don´t know, what I did (what went) wrong but I´ve installed the Zombi-pop about week ago, bud I had some issues with some apps stability and reboots, and needed tablet for daily use so I ve restored nandroid of 4.4.
This weekend I do have some mor time so I´ve did a clean install of Zombi-pop and got a message about low memory space. Don´t know why - installed Zombi pop twice before without hiccups - first with your+ _that´s overclocked kernel , second time with your + sbdags´es kernel - both ok. This time with hardslog´s 5.0 linaro kernel I got the low memory message... any clue???? THX 4 answer. Nandroid backup of 4.4 . is OK again... Maybe too much gapps installed - I knoow KatKiss 5.0 had that problem????
Click to expand...
Click to collapse
You should go settings/storage and click clean cache memory then reboot your prime
Same thing happens when clean dalvik cache and cache from twrp on katkiss 5.0
Could somebody please tell me where I can find Twrp 2.8? When checking their website I can only find 2.6 for our device....
Substratum
- if you are here, that means you know that substratum is based on the system of layers of Sony, and it was added to works in custom ROMs that runs android 7.0 from LineageOS to any based ROMs on it.
- this thread aims to those having a s2 phone (gt-i9100...maybe other variants as well) with problems installing a layer in substratum or substratum itself.
**Installing Substratum
1- Download substratum from play store.
2- Go to settings>apps>substratum and enable all permissions.
3- go to settings>apps, and press the 3 dots menu(or the gear icon in top right corner).
4- scroll down and choose "special access"
5- add permission to substratum in every permission possible.
6- force stop substratum(DON'T CLEAR THE DATA) then start it.
****Installing Overlays
- there are two ways to install layers in substratum.
(1) first way
1- download in install your theme from play store or if you have an apk.
2- select the theme in substratum.
3- Mark your desired overlays.
4- press on the brush icon and select build & install.
wait a few minutes (restarts often the system ui) and ready! your theme is applied
-I use the other method and I've never failed.
(2)second way
1- install your theme as a normal apk or from play store.
2- open substratum and choose the theme.
3- Mark your desired overlays.
4- click on the brush icon and select build & update.
P.S: Once compiled go to OVERLAY LIST and mark the layers that you apply
Warning: if you use this method and want to apply layers make sure you have unapplied already applied layers, (this is done by checking which you will remove and then press on the icon brush and Press disable selected) ...
______________________________________
other data:
- If you want to apply a layer to the system only (i.e navigation bar, status bar and other system stuff), apply the layer "system UI" layer, and "Android system" layer only.
Credits goes to:
@MigoMujahid for helping in design and the substratum installation guide.
F.A.Q
Q: Some layers fail and doesn't install correctly?
A: open the section of the parts of the ROM that has overlays applied to, and select which gives you the error, then click the three points at the top, select "disable installed overlay", also select "clean installed overlay" and finally uninstall theme now reinstall the theme and try to apply it.
Q: I have fear, substratum didn't request access to root after open the app, and I don't want to fall in bootlop?
A: this OK to confirm that substratum recognizes well the root, go to substratum settings and where it says system verification sure that say rootless.
Q: i need to know more about Substratum?
A: If you are looking for info about Substratum, please go to the announcements thread.
Q: how do i make a logcat?
A: you can create a logcat using Catlog app from playstore, or by usung this guide.
All right reserved to "Nathan Chancellor" for this guide.
Q:
how to delete a culprid overlay that bootloop our device?
A: There are 3 ways provided thanks to @Troubadour666 ?
(1) From TWRP, delete the /data/app/"substratum.theme.name.folder"/*.* <---- where was installed the lastest overlay apk (generaly android or systemui overlay) that can give FCs of SystemUi app or bootllop device at next reboot.
-------------------------------------------------------------------------------------
(2) While you have your systemui FCs, if you have a wifi access to your device folders tree, without rebooting it, you can only delete the lastest overlay idmap file on your /data/resource-cache/ folder and instantly FIX the systemui FCs issue.
(maybe with some adb command shell you can do that without rebooting, i ignore the command at the moment, but i'm sure its possible)
Then, always without rebouting, you can safely/quietly open your substratum app on the overlays installed list and uninstall again the culprid overlay (finaly this step concern the APK on data/app) by ticking it and unsing the brush icon.
-------------------------------------------------------------------------------------
(3) You can use a zip that exist on G+ Substratum and flash it on TWRP to clean all the overlays in one pass. you will be safe at next boot.
More F.A.Qs coming....
MigoMujahid said:
F.A.Q
Q: Some layers fail and doesn't install correctly?
A: open the section of the parts of the ROM that has overlays applied to, and select which gives you the error, then click the three points at the top, select "disable installed overlay", also select "clean installed overlay" and finally uninstall theme now reinstall the theme and try to apply it.
Q: I have fear, substratum didn't request access to root after open the app, and I don't want to fall in bootlop?
A: this OK to confirm that substratum recognizes well the root, go to substratum settings and where it says system verification sure that say rootless.
Q: i need to know more about Substratum?
A: If you are looking for info about Substratum, please go to the announcements thread.
Q: how do i make a logcat?
A: you can create a logcat using Catlog app from playstore, or by usung this guide.
All right reserved to "Nathan Chancellor" for this guide.
More F.A.Qs coming....
Click to expand...
Click to collapse
I forgot forgot this :silly:
Excellent thread that start here !
thanks
Question :
- how to delete a culprid overlay that bootloop our device ?
* From TWRP, delete the /data/app/"substratum.theme.name.folder"/*.* <---- where was installed the lastest overlay apk (generaly android or systemui overlay) that can give FCs of SystemUi app or bootllop device at next reboot.
** While you have your systemui FCs, if you have a wifi access to your device folders tree, without rebooting it, you can only delete the lastest overlay idmap file on your /data/resource-cache/ folder and instantly FIX the systemui FCs issue.
(maybe with some adb command shell you can do that without rebooting, i ignore the command at the moment, but i'm sure its possible)
Then, always without rebouting, you can safely/quietly open your substratum app on the overlays installed list and uninstall again the culprid overlay (finaly this step concern the APK on data/app) by ticking it and unsing the brush icon.
*** you can use a zip that exist on G+ Substratum and flash it on TWRP to clean all the overlays in one pass. you will be safe at next boot.
hope i was clear, thanks.
Troubadour666 said:
Excellent thread that start here !
thanks
Question :
- how to delete a culprid overlay that bootloop our device ?
* From TWRP, delete the /data/app/"substratum.theme.name.folder"/*.* <---- where was installed the lastest overlay apk (generaly android or systemui overlay) that can give FCs of SystemUi app or bootllop device at next reboot.
** While you have your systemui FCs, if you have a wifi access to your device folders tree, without rebooting it, you can only delete the lastest overlay idmap file on your /data/resource-cache/ folder and instantly FIX the systemui FCs issue.
(maybe with some adb command shell you can do that without rebooting, i ignore the command at the moment, but i'm sure its possible)
Then, always without rebouting, you can safely/quietly open your substratum app on the overlays installed list and uninstall again the culprid overlay (finaly this step concern the APK on data/app) by ticking it and unsing the brush icon.
*** you can use a zip that exist on G+ Substratum and flash it on TWRP to clean all the overlays in one pass. you will be safe at next boot.
hope i was clear, thanks.
Click to expand...
Click to collapse
Excellent
Thanks bro, i will add it to the F.A.Q
Troubadour666 said:
Excellent thread that start here !
thanks
Question :
- how to delete a culprid overlay that bootloop our device ?
* From TWRP, delete the /data/app/"substratum.theme.name.folder"/*.* <---- where was installed the lastest overlay apk (generaly android or systemui overlay) that can give FCs of SystemUi app or bootllop device at next reboot.
** While you have your systemui FCs, if you have a wifi access to your device folders tree, without rebooting it, you can only delete the lastest overlay idmap file on your /data/resource-cache/ folder and instantly FIX the systemui FCs issue.
(maybe with some adb command shell you can do that without rebooting, i ignore the command at the moment, but i'm sure its possible)
Then, always without rebouting, you can safely/quietly open your substratum app on the overlays installed list and uninstall again the culprid overlay (finaly this step concern the APK on data/app) by ticking it and unsing the brush icon.
*** you can use a zip that exist on G+ Substratum and flash it on TWRP to clean all the overlays in one pass. you will be safe at next boot.
hope i was clear, thanks.
Click to expand...
Click to collapse
Excellent my bro
This is very important
Thank you very much