Database Develop

[RECOVERY]Unofficial ClockworkMod Recovery v4.0.0.2(WIP)

Hi
Clockwork Recovery v 4.0.0.2 for Galaxy Ace
v2:
- working nandroid backup/restore!
For now i've disabled backup/restore of boot and recovery partitions. Restore of DATA, CACHE and SYSTEM is working fine.
If you have JTAG and want to test restore of boot/recovery please PM me!.
- it's based on KPH firmware + root in adb (both in normal and recovery mode)
v1:
Tested:
- wipe Data/Factory reset
- wipe cache partition
- some options under advanced menu (to wipe)
- install zip from SDCard (tested on some file from UOT kitchen)
- reboot recovery
- mount USB storage (and other mount options) Better not try to format partitions from recovery yet - it could format them to ext4 for which we probably not have yet support in kernel.
Know bugs:
- poweroff sems to reboot phone
- problem with graphics (probably framebuffer is set to 24 or 32 bpp mode. There is also missing double buffer support in framebuffer - thats why we have 2 recovery screens). It'll be fixed - thanks to tj_style!!
Remember, I am not reponsible if you brick your phone. You're flashing this on your own risk.Not all options are tested!!!.
How to flash (v2):
1. Download file from here .
2. flash it as PDA with odin
Mirrors:
Multiupload (thanks to peeter123)
I've removed recovery.zip - it was recovery.img packed with zip, not update for apply using stock recovery.
To move in recovery:
- Volume up/down to move.
- Home (center key) to select item.
- Back to move back.

Where did you get this?

Lovetz said:
Where did you get this?
Click to expand...
Click to collapse
I've build it from source using this tutorial Porting clockwork recovery to new device, with some changes. Then i've mixed recovery.img with those from samsung firmware.

PabloPL said:
I've build it from source using this tutorial Porting clockwork recovery to new device, with some changes. Then i've mixed recovery.img with those from samsung firmware.
Click to expand...
Click to collapse
You are elite, dude!;-) (Hackers)

This opens so many oppertunites to our Ace CyanogenMod being one of them. Have you got any further with these bugs? This is great. Thank you
Sent from my GT-S5830 using XDA App

awesome work!!!....it would be legendary if NANDROID backup works!!!!NO more bricking worries!!!

I've successfully to porting the Clockworkmod Recovery too for Galaxy mini.
The problem with framebuffer it's been fixed too.
I just have the problem with backup & restore, also with flashing full rom from zip.
Are you get success with backup and restore?
since galaxy ace / mini is using different tool for read / write the bml partition. not like SGS that can using redbend_ua

PabloPL said:
Hi
Today i managed to run the newest Clockwork Recovery on my Galaxy Ace. It has some problem with graphics (as you can see on screenshots).
I've tested following options (and for me they are working):
- wipe Data/Factory reset
- wipe cache partition
- some options under advanced menu (to wipe)
- install zip from SDCard (tested on some file from UOT kitchen)
- reboot recovery
- mount USB storage (and other mount options) Better not try to format partitions from recovery yet - it could format them to ext4 for which we probably not have yet support in kernel.
Know bugs:
- poweroff sems to reboot phone
- problem with graphics (probably framebuffer is set to 24 or 32 bpp mode. There is also missing double buffer support in framebuffer - thats why we have 2 recovery screens)
I've also managed to create nandroid backup of all partitions (boot,recovery,data and system) but not tried yet to restore them.
Phone info
In recovery mode (sorry for terrible image quality)
I've attached packed recovery.img. it's based on KPH firmware + root in adb (in both boot and recovery mode) + su binary.
Remember, I am not reponsible if you brick your phone. You're flashing this on your own risk.Not all options are tested.
How to flash:
1. take KPH firmware
2. extract CODE_S5830XXKPH_CL260130_REV03_user_low_true.tar.md5
- tar xvf CODE_S5830XXKPH_CL260130_REV03_user_low_true.tar.md5
3. replace recovery.img with attached file
4. pack it back
- tar -H ustar -c boot.img recovery.img data.rfs system.rfs >ODIN_FILE.tar
- md5sum -t ODIN_FILE.tar >>ODIN_FILE.tar
- mv ODIN_FILE.tar ODIN_FILE.tar.md5
5. flash it with odin
To move in recovery:
- Volume up/down to move.
- Home (center key) to select item.
- Back to move back.
Click to expand...
Click to collapse
GREAT JOB MAN!
Go ahead, you are on it!!!
CHEERS!

The main thing is to get the install update zip feature as that really is the reason we use ClockworkMod and what we wanted it for.
Sent from my GT-S5830 using XDA App

kills999 said:
awesome work!!!....it would be legendary if NANDROID backup works!!!!NO more bricking worries!!!
Click to expand...
Click to collapse
For now i've tested it only with creating backup of boot/recovery/data/system partitions and it generated without errors.
Jekle_Ace said:
The main thing is to get the install update zip feature as that really is the reason we use ClockworkMod and what we wanted it for.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I've tested installing update from zip on some theme from OUT Kitchen and it worked fine

PabloPL said:
I've tested installing update from zip on some theme from OUT Kitchen and it worked fine
Click to expand...
Click to collapse
Can you upload ready-to-flash KPH file with CWM integrated?

Wiping partitions /system /data etc is very important without wiping it can cause many problems as I've done that many times with my ZTE Blade. But still I appriciate this greatly
Sent from my GT-S5830 using XDA App

tj_style said:
I've successfully to porting the Clockworkmod Recovery too for Galaxy mini.
The problem with framebuffer it's been fixed too.
View attachment 623281
I just have the problem with backup & restore, also with flashing full rom from zip.
Are you get success with backup and restore?
since galaxy ace / mini is using different tool for read / write the bml partition. not like SGS that can using redbend_ua
Click to expand...
Click to collapse
Could You share what changed did you made to fix framebuffer problems ?? For now i've made some change found here to get 2 screens in recovery (was getting 4 before).
About backup, like i wrote, tested only creating. I have to set up correct size of all partitions in BoardConfig etc, Ace is my primary phone, so i don't want to brick it.
I've made some changes to recovery source (look into bmlutils/bmlutils.c - there are hardcoded paths to boot and recovery partitions, which on Ace are differend than those in code).
I've also used custom recovery_ui.c with custom key mapping.

Lovetz said:
Can you upload ready-to-flash KPH file with CWM integrated?
Click to expand...
Click to collapse
I have PDA file for odin with it, but i've messed something with Superuser.apk and you must install it by hand (only Superuser.apk, su binnaries are fine). Maybe when i'll have some free time - i'm working and studying (now have exams) - i'll upload it, if someone won't do this before .
Jekle_Ace said:
Wiping partitions /system /data etc is very important without wiping it can cause many problems as I've done that many times with my ZTE Blade. But still I appriciate this greatly
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
For now i've tested wipe only on following options (and it worked fine):
- battery stats
- cache
- data (factory reset)
Sorry for double-postings

PabloPL said:
Could You share what changed did you made to fix framebuffer problems ?? For now i've made some change found here to get 2 screens in recovery (was getting 4 before).
About backup, like i wrote, tested only creating. I have to set up correct size of all partitions in BoardConfig etc, Ace is my primary phone, so i don't want to brick it.
I've made some changes to recovery source (look into bmlutils/bmlutils.c - there are hardcoded paths to boot and recovery partitions, which on Ace are differend than those in code).
I've also used custom recovery_ui.c with custom key mapping.
Click to expand...
Click to collapse
Sure, You can see on my github soon. I'm not yet pushing to my github now.
because the project of Cyanogenmod port and Clockworkmod port for Galaxy Mini is pending now until i have the Galaxy mini back, you can see the progress in this thread.
I've add the double buffering to clockworkmod source, since Galaxy mini kernel doesn't suppot that.
I hope we can colaborate to make clockworkmod is fully working, because the Galaxy Mini, Ace, Gio and Fit is using similiar environtment.

thx dude, i really need this.

tj_style said:
I hope we can colaborate to make clockworkmod is fully working, because the Galaxy Mini, Ace, Gio and Fit is using similiar environtment.
Click to expand...
Click to collapse
It would be nice. As i see You have far more progress.
In my opinion it would be better to make it with only minimal changes (or even without) to android source (recovery etc), to keep it in synch with "mainline". Closer we keep(and less changes), longer we could have support.
Also getting rid of BML and use MTD (when we have sources for 2.3.4) would be great.

PabloPL said:
It would be nice. As i see You have far more progress.
In my opinion it would be better to make it with only minimal changes (or even without) to android source (recovery etc), to keep it in synch with "mainline". Closer we keep(and less changes), longer we could have support.
Also getting rid of BML and use MTD (when we have sources for 2.3.4) would be great.
Click to expand...
Click to collapse
Yup, i'm waiting to someone borrowing the galaxy mini to me and also waiting samsung to get released the 2.6.35.7 kernel source.

The source will come after 2.3 is offically released but we may be waiting a few weeks for it
Sent from my GT-S5830 using XDA App

Great work mate. Maybe you can work together with nprussel who is also trying to run cwm on g ace
@formatting partitions, there is indeed no support for ext4 in kernel
Sent from my GT-S5830 using XDA App

Samsung Galaxy Exhibit 4G

T-Mobile/Samsung have rebranded the Exhibit II 4G, giving us a new kernel, a bump to Android v2.3.6 and performance improvements (they claim) in the process. The phone we all love is now the Samsung Galaxy Exhibit 4G.
This stock ROM (UVLG3) is NOT vulnerable to USSD Dialer Attacks!
Rooting
Currently, zergrush will not root this phone's Android 2.3.6. Three known methods:
Root Stock 2.3.6 w/o a new kernel or ROM
root-stock.zip
Mirror
This zip will install Superuser, su and busybox, leaving you rooted, but otherwise no changes to your phone. ClockworkMod must be installed to flash this. So:
1. Flash ClockworkMod
2. Boot into ClockworkMod and flash root-stock.zip.
Rooted Community ROM (forkable)
t679.uvlg3.odex.01.zip
Mirror
(also see custom ROMs)
Linked above is Samsung's newest release for the Galaxy Exhibit, a stock rooted UVLG3 Gingerbread ROM. Busybox is also included. You must flash it via clockworkmod. Clockworkmod can be flashed with Samsung's stock recovery.
Custom rooted kernel
t679-root-v1.8.zip
Mirror
Kernel sources
The kernel is based on Samsung's kernel source. This kernel is rooted; if you flash it via stock recovery or cwm your ROM will be rooted with Superuser.apk, Busybox and the Galaxy Exhibit cwm-recovery installed. This kernel works with all Samsung Gingerbread releases.
Rooted ROM Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. The installation will format your data partition. I suggest Titanium Backup, available in the Market.
2. Download & copy the current t679.uv???.deodex.0x.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
3. Install Galaxy Exhibit Custom Recovery . If you're already rooted, you may install from the command line, otherwise you may install from Samsung's Recovery. Samsung's recovery only sees the internal SD, so copy the cwm zip there if you just have stock recovery. Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Select ROMwipe. This step is required!
6. Highlight install zip from sdcard, then press Home.
7. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
8. Highlight the rooted rom zip file, then press Home.
After you confirm your choice, installation should take less than three minutes.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied. Your first post-installation boot may be several minutes long.
Rooted Kernel Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. I suggest Titanium Backup, available in the Market.
2. Download & copy t679-root-v1.8.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
It's recommended to install Clockwork Mod, but you can also flash the kernel from Samsung's stock recovery. Samsung's recovery only sees the internal sd, so copy files there if you don't have cwm.
Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Highlight install zip from sdcard, then press Home.
6. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
7. Highlight the kernel zip file, then press Home.
After you confirm your choice, installation should take less than a minute.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied.
Please DO NOT PM me with support questions! They will be ignored! Post them in this thread!

Links and useful info
Galaxy Exhibit XDA Wiki
Galaxy Exhibit IRC channel
Galaxy Exhibit Themes
Custom ROMs
All ROMs listed require cwm for installation.
Peach Sunrise
RebelROM
XquiziT
CyanogenMod 9 Beta
Galaxy ExHibition
CM10 Port
AOKP (WIP)
CM7 (WIP)
CM9 Pure Nexus
Stalled, partially working
AOKP
KEMIUI
Help! I keep getting FCs!
Custom kernel for Rebel Rom
This is custom kernel 1.8 packaged specifically for RebelRom, tested on
version 3.0.8. This package includes kernel & modules only.
rrkernel.zip
Mirror 2
Stock 2.3.6 via Odin
uvlg3.odin.zip
Mirror
Adb for Windows
winadb.zip unzip and copy to your c:\Windows directory
Mirror
Flash2Stock
Flash2Stock (flash via cwm) will install stock UVLG3 and Samsung's stock recovery, un-rooting
your phone, removing ClockworkMod and returning your phone to factory condition.
uvlg3.flash2stock.zip
Mirror
SwapSD
SwapSD This simple app allows you to swap internal "usb storage" (aka /sdcard) and your removable sdcard (aka external_sd) so your larger "external sd" is mounted as "/mnt/sdcard/" and the smaller sd internal memory is mounted as "/mnt/sdcard/external_sd". This is done by changing a file called vold.fstab in your phone's /etc folder. The original device vold.fstab file is backed up to /etc/vold.fstab.backup when this app first runs. Your data on /mnt/sdcard and /mnt/sdcard/external_sd is not touched in any way whatsoever.
Dropbear (flash via cwm)
is a software package that provides a Secure Shell-compatible (ssh) server and client. It is designed as a replacement for standard OpenSSH for environments with low memory and processor resources, such as embedded systems. This archive also includes the scp and rsync utilities.
dropbear.zip
Mirror
Bloatware
These apps are safe to delete. You may also freeze them using Titanium backup.
AnalogClock.apk
Browser.apk (Only if you use an alternative browser)
Dlna.apk
DownloadProviderUI.apk
DualClock.apk
DualClock.apk
IQ-tmobile-release-signed-zipaligned-v1.1....
JobManager.apk
KiesAir.apk
MobileBackup-unsigned_v3.3.02.apk
MyFiles.apk(Only if you have an alternative File Browser i.e. Astro File Manager)
SamsungWidget_Program...
Swype.apk
TetheringManager2.apk(Only if you don't use T-Mo's tethering service)
TouchWizCalendar.apk
TouchWizCalculator.apk
TwCalendarAppWidget.apk
VideoPlayer.apk(Only if you have an alternative video player)
VoiceRecorder.apk
WiFi-Calling.apk(If you don't use it)
ZinioSettingsProvider.v2.03.3331.TMobile....
sihome-signed-tmo-android-8.apk
talkback.apk
tmobile_m4m_3_0_15.signed...
vvm-signed.apk
Partition Table
/dev/block/mmcblk0p1 secboot2 partition map
/dev/block/mmcblk0p2 dbl.mbn (boot loader)
/dev/block/mmcblk0p3 osbl.mbn (boot loader)
/dev/block/mmcblk0p4 MBR extended partition table
/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
/dev/block/mmcblk0p6 amss.mbn
/dev/block/mmcblk0p7 emmcparam.bin
/dev/block/mmcblk0p8 boot.img (linux kernel)
/dev/block/mmcblk0p9 adsp.mbn (baseband)
/dev/block/mmcblk0p10 rmt
/dev/block/mmcblk0p11 rmt
/dev/block/mmcblk0p12 persist.ext4
/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
/dev/block/mmcblk0p14 param
/dev/block/mmcblk0p15 system.ext4
/dev/block/mmcblk0p16 cache.ext4
/dev/block/mmcblk0p17 data.ext4
/dev/block/mmcblk0p18 preload.ext4
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20 all 0's
/dev/block/mmcblk0p21 all 0's
/dev/block/mmcblk0p22 all 0's
/dev/block/mmcblk0p23 all 0's
/dev/block/mmcblk0p24 all 0's
/dev/block/mmcblk0p25 all 0's
/dev/block/mmcblk0p26 all 0's
/dev/block/mmcblk0p27 efs (encrypted fs)
/dev/block/mmcblk0p28 /mnt/sdcard
Credits:VanillaTbone,s0unds,KemikalElite, jocala, Wildchild, bpear96, camcory, Intercepter and others. If your name belongs here or you have info that needs to be added please speak up!

Zergrush
Rooting the original Exhibit II via zergrush: Please read DooMLoRD's Easy Rooting Thread
Please note that this method does not work with Android 2.3.6 on the Galaxy Exhibit.

ClockworkMod
Galaxy Exhibit cwm-based recovery v6.0.1.2
6.0.1.2 has new features, including better support for both external and internal SD cards, faster backups and restores with a new backup format that de-duplicates data in between backups. Exclusive features for Galaxy Exhibit include:
wipe menu with rom wipe
All system wipes under one menu: rom (system/cache/data),cache,dalvik,cache/dalvik,data.
Stack zip files for installation:
Flash cm9 & gapps, etc. Select as many zip files for installation as you choose. Flash them all with one command.
Install system images:
Drop any recognized system image into a folder on your phone and recovery can flash it. You can even drop the entire contents of an odin tar/md5 file in a folder and cwm recovery will flash it all automatically.
All images must conform to Odin naming standards:
adsp.mbn
amss.mbn
boot.img
cache.img.ext4
preload.img.ext4
recovery.img
system.img.ext4
Click to expand...
Click to collapse
This is regular interface, not touch.
cwm.6012.t679.zip
Mirror
To initially install Galaxy Exhibit Custom Recovery you need to:
1. Copy cwm.galaxy.exhibit.zip to your internal SD storage.
2. Boot into stock recovery:
Starting recovery: Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons.
Or a different method some find easier:
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Recovery should start after the Galaxy Exhibit/T-Mobile logo.
3. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm.galaxy.exhibit.zip file.
If you already have cwm installed, to update follow the steps above, booting into your current cwm instead of stock recovery.
Should you need to install ClockworkMod via Odin:
cwm.6012.tar
Mirror

We have needed a new thread for our phone, thanks for making this!

kingdavidd said:
We have needed a new thread for our phone, thanks for making this!
Click to expand...
Click to collapse
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links and information.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any general discussion of our Galaxy Exhibits (concerning development as well). I also hope folks will evangelize and point people here rather than carry on in the older abandoned OP threads.

Nice job jocala! Thanks.
Sent from my Calculator with Android.

So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct? Much rather flash that then go back to stock then update. Thank you for that.
Sent from my SGH-T679 using xda premium

jocala said:
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any discussion of our Galaxy Exhibits.
Click to expand...
Click to collapse
Yea all the old threads OP's abandoned them and the original post had all old info, I am glad you're dedicated to this phone!

SurgeRush said:
So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct?
Click to expand...
Click to collapse
Yep, that's it. Purely stock except for root, busybox & recovery.

Cant wait to see what roms come out of this
Sent from my SGH-T679 using XDA

The rebranding works out nicely, if for no other reason than providing a point of demarcation.
Many props to Jocala who is awesome, as we all know. It can't be said too often but we'll try not to overdo it. :thumbup:
Sent via frazzled carrier pigeon -->

Ditto here man. We'd all be screwed & tattooed without his know-how. BTW worth mentioning I had to refreeze all the bloatware again after the update. Noticed how the phone lagged and then checked Titanium Backup. Sure enough all the crap was back. Also re-check settings in programs like Juice Defender and Rom Toolbox. I had to re-enter some of them again as well.

Has anyone managed to update successfully while already being rooted? (Specifically by Zerg Rush method)
I've yet to received the OTA notification and still holding off If i should update using the software. Stock ROM but just rooted. Holding off on "flashing" anything as I've never done it before.

ArtfulDodger said:
Ditto here man. We'd all be screwed & tattooed without his know-how.
Click to expand...
Click to collapse
That's not true at all, but thanks for saying it. Anyone handy with *nix can do what I do, and 95% (or more) of the techniques I use were pioneered by others here on xda.

Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder(not in stock) T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though. It also looks like you might have taken a different approach to rooting the rom, maybe you could look at mine see if its just complete fail or not lol and or maybe pming me, to avoid clutter, on how you did urs.
ive made sooo many edits lol but just wanted to add too, thanx for all the work you have done for us.

cars1189 said:
Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though.
Click to expand...
Click to collapse
The phones I use have always come odexed. I know of no other root methods. I don't have time to beta your rom, but feel free to post a link. I'm sure you'll have volunteers

cool, and no problem, and basically all i did was use the dsixd kitchen and added root(from in the kitchen menu), does that not really root it? does that just change the file permissions? cause when i did that it added the su binary so i assumed it did, but doesn't look like thats what you did, urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.

cars1189 said:
urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.
Click to expand...
Click to collapse
You are correct

Flashed the ROM, all went smooth, but I can't install anything from the Market. Every time I try I get "ERROR "Blah" Could not be downloaded due to an error." Any ideas? Did a full romwipe and dalvik before flashing. The markets not even updating to Play store either.

Frederuco's Boot Animations - for Android

So, I was bored at work today. I love the TeamEOS 4 CRT style screen off animation as it is a bit retro, and I was thinking about the BIOS style boot animation from a Honeycomb ROM (PRIME! by Roach2010 if I recall) and I decided to cook up one of my own.
First, I did one for the TeamEOS 4 (Android 4.2) for the TF101. Here is a preview video:
The spot light continues to shine left and right in a loop until the boot completes.
There are 4 versions of the TeamEOS 4 available:
16 GB Regular (shows 16 GB internal memory): http://db.tt/GDCmRrsy - Approximately 33 seconds until loop starts
16 GB Short (shows 16 GB internal memory): http://db.tt/ipSH5v2P - Approximately 22 seconds until loop starts
32 GB Regular (shows 32 GB internal memory): http://db.tt/RJfIKkhG - Approximately 33 seconds until loop starts
32 GB Short (shows 32 GB internal memory): http://db.tt/Gvt20bqV - Approximately 22 seconds until loop starts​
Then, I decided to make one of these for those running CyanogenMod 10.1 on the TF101:
The light continues chasing inside the circle until boot finishes.
16 GB (shows 16 GB internal memory): CyanogenMod 10.1 Boot animation for TF101 with BIOS style boot.
CyanogenMod animation continues with the circular ring until boot completes.
There 2 versions available for the CM10.1:
16 GB (shows 16 GB internal memory): http://db.tt/E12GEFvc
32 GB (shows 32 GB internal memory): http://db.tt/6tjiR3E7​
I also made one that says Cyanogen[SUP](mod)[/SUP] as I like that version better:
There 4 versions available for the C(m)10.1:
16 GB Long (shows 16 GB internal memory): http://db.tt/FCL62d84 Approximately 28 seconds
16 GB Short (shows 16 GB internal memory): http://db.tt/6cNrSyUu Approximately 20 seconds
32 GB Long (shows 32 GB internal memory): http://db.tt/fSUQhbfI Approximately 28 Seconds
32 GB Short (shows 32 GB internal memory): http://db.tt/i0oA8zD2 Approximately 20 Seconds​
e154037 has requested the Dancing Android.
This will work on phones or tablets.
It is now square and has 2 size options:
400x400 size: http://db.tt/GGVRiQgb
800x800 size: http://db.tt/lUVFbcWz​
Installation Instructions:
Disclaimer - I am not responsible for bricking your device. These are to be used at your own risk. I have personally tested these and they are fully working. Be sure to do a nandroid backup BEFORE installing these just in case.
Method 1 (works for rooted and unrooted devices)
Rename the file to bootanimation.zip
Use adb and issue the following commands (If you don't know how to use adb, please google it):
Code:
adb push bootanimation.zip /data/local/
adb shell
reboot
Method 2
Rename the file to bootanimation.zip
Use your favorite Root Explorer and copy the bootanimation.zip to /system/media/ OR /data/local/
Note that ES File Explorer does not work well for this.​
I cannot take credit for most of the work on these - I only did some minor editing to the BIOS style files along with some assembly and testing.
Credit to frysee for the BIOS style boot animation from this thread: http://forum.xda-developers.com/showthread.php?t=648555 This boot animation was updated for the respective ROM names and SD card sizes.
Credit to JoinTheRealms for his work on the TeamEOS Boot Animation here that was incorporated into this animation.
Credit to CyanogenMod for the boot animation borrowed from the links of this video
As a side project, here is a copy of JoinTheRealms boot animation with it looping properly: http://db.tt/tm9J8lMB

i am getting a zip cannot be moved on es file explorer

catfishbilly said:
i am getting a zip cannot be moved on es file explorer
Click to expand...
Click to collapse
same here with ES and alot of other weird behavior when trying to move it. finally got it to delete. Re-downloaded it, and used Root Explorer to move it to /system/media with no issues. My guess is ES has issues with the zip. Always pays to have multiple file managers downloaded just for these occasions, if one doesn't work you can fall back to another file manager.

[Boot Animations] TF101 for Android 4.2 - BIOS style
I think you have to long press on the media folder with ES and change permissions to allow write access.
Root Explorer is a bit nicer I for this.
I boot looped myself trying to use ES.
I ended up using adb via WiFi and it was easier (didn't have my USB cord with me to use regular adb)

Nice Job
Nice job frederuco! Excellent work, my thanks to you, frysee and JoinTheRealms; works just fine.
On a side note when you get bored again do you think you can make one adding timduru's picture from the team roster giving him a little extra props for maintaining and developing for the tf101

thanks guys, it worked with root explorer. my tab boots kind of fast, so i just enjoy the bios part of the boot animation without the part from jointherealms.

catfishbilly said:
thanks guys, it worked with root explorer. my tab boots kind of fast, so i just enjoy the bios part of the boot animation without the part from jointherealms.
Click to expand...
Click to collapse
I added some shorter boot animations for the EOS ROM.
For the CM10 users, let me know if that is too long. I think it only takes about 25-28 seconds to get to the loop, so it should be OK. If y'all need a shorter one just let me know.

frederuco said:
I added some shorter boot animations for the EOS ROM.
For the CM10 users, let me know if that is too long. I think it only takes about 25-28 seconds to get to the loop, so it should be OK. If y'all need a shorter one just let me know.
Click to expand...
Click to collapse
I like the "Dancing Android Boot Animation" (http://androidbootanimation.com/page/3/), but it is for
phone. Any way to make it work for TF101 tab?

e154037 said:
I like the "Dancing Android Boot Animation" (http://androidbootanimation.com/page/3/), but it is for
phone. Any way to make it work for TF101 tab?
Click to expand...
Click to collapse
You want it, you got it!
From to the OP:
frederuco said:
e154037 has requested the Dancing Android.
This will work on phones or tablets.
It is now square and has 2 size options:
400x400 size: http://db.tt/GGVRiQgb
800x800 size: http://db.tt/lUVFbcWz​
Click to expand...
Click to collapse

Device Essential Material *** Firmware, Source Code, Root etc.***

This thread will list and link to all core device essential stuff.
PM me if there is new stuff or something doesn't work please​
STOCK ASUS FIRMWARE
WW_epaduser_11_4_1_17_UpdateLauncher.zip: HERE
US_epaduser_11_4_1_17_UpdateLauncher.zip: HERE
WW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
CN_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
CN_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
JP_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
US_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
WW_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
CN_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
How to flash:
Step 1: Download and unzip the zipfile of your choice.
Step 2: Copy the new Zipfile and paste it in root directory of your internal SdCard, then reboot the device and the update will automatically start.
ASUS SOURCE CODE
kernel_10_14_1_42.rar: HERE
kernel_10_14_1_45.rar: HERE
kernel_10_14_1_47.rar: HERE
kernel_10_26_1_7.rar: HERE
kernel_10_26_1_18.rar: HERE
kernel_11_4_1_17.rar: HERE
UNLOCK YOUR DEVICE
0820-0954_SIGNED_UnLock_for_TF701_repart.apk: HERE
How to unlock:
- Download the Asus unlock app
- Install and run the app. This will require a valid google account (if you use one time passwords, you'll need to generate one for this purpose) and internet access.
- When booting with [vol-] + [power] pressed, the transformer will show the message "The device is unlocked"
ROOT TOOLS
Read here: http://forum.xda-developers.com/showthread.php?t=2516215
CUSTOM RECOVERY
CWM Recovery V6.0.4.8. for 4.3*: HERE
ATTENTION: you must have an unlocked bootloader
How to flash this:
- reboot device into fastboot mode:
- adb reboot bootloader
- now flash the recovery using : fastboot flash recovery recovery.img [where recovery.img is the name of the file image you downloaded]
CUSTOM ROM'S
By Sbdags based on stock with quite some enhancements: HERE
CyanogenMod 11 Preview Proxy thread: HERE
THEMES
Non available yet
BOOTANIMATIONS
Non available yet
OTHER MOD'S
None available yet
PARTITION INFORMATION**
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)
RECOVERY.FSTAB**
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 vfat default voldmanaged=sdcard:auto
/devices/platform/tegra-ehci.0 /mnt/usbdrive vfat default voldmanaged=usbdrive:auto
BLOB**
Code:
name size description status
10.14.1.47: [ATTACH]2435244[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (original) [ATTACH]2435246[/ATTACH]
blob.BC1 8,192 Bytes ? (original) [ATTACH]2435245[/ATTACH]
blob.EBT 1,396,736 Bytes Bootloader (original) [ATTACH]2435247[/ATTACH]
blob.PT 2,202 Bytes Partition Table (original) [ATTACH]2435248[/ATTACH]
10.26.1.7: [ATTACH]2435238[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (unchanged) [ATTACH]2435241[/ATTACH]
blob.BC1 8,192 Bytes ? (changed) [ATTACH]2435240[/ATTACH]
blob.EBT 1,421,312 Bytes Bootloader (changed) [ATTACH]2435242[/ATTACH]
**= Thanks to Ipdunwell for sharing this info
HOW TO UNBRICK YOUR DEVICE
Read here: http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1
ATTENTION​
YOUR WARRANTY COULD BE VOID DUE TO ROOTING AND UNLOCKING YOUR DEVICE (depending of which country you reside)
I am NOT responsible for bricked devices, dead SD cards or dead docks.
Please do some research if you have any concerns about the files here BEFORE flashing anything!
When you have no clue what we are talking about here you better leave your hands off it!!
YOU are choosing yourself freely to use these file(s) all by yourself!!!​

Updated Recovery for 4.3 with working "external" SD card, found here
http://forum.xda-developers.com/show....php?t=2621051
Custom Rom's
Cromi-x
http://forum.xda-developers.com/show....php?t=2608129
CM11 -Preview (Unofficial)
http://forum.xda-developers.com/show....php?t=2621028

Delete

Root and firmware.
Hello all. I'm new to the site, and very sorry if this is a dumb question, but Id rather sound dumb than brick my transformer.. I'm planning to root my TF701 following lpdunwells guide. One of the prerequisites is to have 10.14.1.47 as the firmware version. My question is this.. When I unlock my bootloader and it wipes my tablet, will it reset me back to the original firmware version? Or will this matter?
My current firmware version is 10.26.1.18
Thank you very much in advance for your help, also, I will greatly appreciate any and all help and info regarding this matter.

tf701mega said:
Hello all. I'm new to the site, and very sorry if this is a dumb question, but Id rather sound dumb than brick my transformer.. I'm planning to root my TF701 following lpdunwells guide. One of the prerequisites is to have 10.14.1.47 as the firmware version. My question is this.. When I unlock my bootloader and it wipes my tablet, will it reset me back to the original firmware version? Or will this matter?
My current firmware version is 10.26.1.18
Thank you very much in advance for your help, also, I will greatly appreciate any and all help and info regarding this matter.
Click to expand...
Click to collapse
If you want to root then use my guide as it is for 10.26.1.18. Downgrading to .47 and back up again is really painful.

download problem
Hi OP,
Download links are down...
please fix theme?

henengel said:
Hi OP,
Download links are down...
please fix theme?
Click to expand...
Click to collapse
anyone know where I can get the files? links are broken

kuthedude said:
anyone know where I can get the files? links are broken
Click to expand...
Click to collapse
Which files are you looking for?
Most of the files are available from ASUS's website and the ROM and recovery links are old and newer ones are available in the Development section of this form.

Sorry for the inconvenience.
Asked in the OP to PM me if there is new stuff or if somethings doesn't work but received nothing.
Files will be back end of the day with latest firmware and kernel source.

Hi, I am getting my tablet soon, and I am assuming the tablet will be on 4.3 or earlier by the time I get it.
What firmware/kernal/boot loader is the best setup to get me onto the latest 4.3 OS. I only am wanting this because I want to avoid the 4.4.2 battery drain issues (since I am most likely going to flash an AOSP ROM after I get this tablet).
Also, how would I be able to properly update the tablet with the firmware/kernal/boot loader? Thanks for the help!
Sent from my SCH-I545 using Tapatalk 2

Hi, I tried pushing my firmware file to root, but it wouldn't work. I would use root explorer and it would just freeze and restart. anyone know why this would happen? Im trying to update to 4.3 without getting into 4.4.2. please help if you can

You have to unpack the file, inside this is another zip file. Put it then in sd root this should work as far as i know
Gesendet von meinem LG-D855 mit Tapatalk

Hi
There is a new firmware version 11.4.1.27.
Is it posible to add this version to the post?

Working Bootable recovery for the KFFOWI (Ford)

As you know, root has been achieved on this device. Now, let's move on to recovery. The recovery.img is a lot like the boot.img, in the way that you can boot from it. In theory, if we make a 3e recovery.bin for this device (TWRP/CWM), and we boot from it, we will be able to install any rom. Let's let the Recovery.bin development start!
THIS DEVICE DOES NOT SUPPORT FLASHING RECOVERIES. YOU HAVE TO BOOT FROM THEM IN FASTBOOT.​
This device now has 2 custom recoveries, those 2 being TWRP (Team Win Recovery Project) and CM (CyanogenMod) Recovery. CyanogenMod recovery is much like the stock recovery, with the only difference being that CM Recovery can install files that don't have the Amazon ZIP Signature. TWRP, on the other hand, has a touchscreen display, and is much more user friendly than CM Recovery. The links to both are here:
CM Recovery
TWRP
You can do many things in a Custom Recovery, such as:
Install custom ROMs (Found here)
Install modifications to your current OS (XPosed Framework, Root, etc.)
Install GAPPS (Google Applications, including Play Store and Play Services)
Wipe your current ROM
Backup your current ROM
Restore a backup of a previous ROM
If you have any questions, ask them here.
Now, press the thank button here and thank the developers that made these recoveries and ROMs possible, and you are good to go.
Good Luck!

Im dumping the recovery partition right now as well as the boot as well and the other two extra bootloader stuff that may help us

I have attached the images we can use. I dont know if we need the system image file but if we do just let me know hopefully ill be able to upload it or someone else might cause its 1 GB it may take some time.

Awesomeslayerg said:
I have attached the images we can use. I dont know if we need the system image file but if we do just let me know hopefully ill be able to upload it or someone else might cause its 1 GB it may take some time.
Click to expand...
Click to collapse
Well, we just need someone to build a recovery for this device. Once that is bootable, we can install roms. Also, since we will most likely not be able to unlock the bootloader, Safestrap might be our best bet.

True.. it's a mediatek soc so there's gotta be a way to unlock the bootloader because most of the mediatek devices have unlocked bootloader I think. And besides it gives us an unlock code so we need to see what that deal is

Just leaving here partitions structure:
Model: MMC 8GND3R (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 2097kB 1049kB KB
2 2097kB 3146kB 1049kB DKB
3 3146kB 21.4MB 18.2MB EXPDB
4 21.4MB 22.4MB 1049kB UBOOT
5 22.4MB 39.2MB 16.8MB boot
6 39.2MB 56.0MB 16.8MB recovery
7 56.0MB 56.5MB 524kB MISC
8 56.5MB 60.2MB 3670kB LOGO
9 60.2MB 65.4MB 5243kB TEE1
10 65.4MB 70.6MB 5243kB TEE2
11 70.6MB 1329MB 1258MB ext4 system
12 1329MB 1591MB 262MB ext4 cache
13 1591MB 7818MB 6227MB ext4 userdata

Hmm it looks like the MTK Droid Root and Tools V2.5.3 works now so we can flash images via that as well as recovery AND boot. But someone should get a 2nd fire and try it out because we have no scatter file.
We could possibly install a 2nd bootloader

Awesomeslayerg said:
Hmm it looks like the MTK Droid Root and Tools V2.5.3 works now so we can flash images via that as well as recovery AND boot. But someone should get a 2nd fire and try it out because we have no scatter file.
We could possibly install a 2nd bootloader
Click to expand...
Click to collapse
I have made this one and test ro readback partitions bug gets error 2004
Partition lists
storage, boot_channel & block_size maybe not good
Model: MMC 8GND3R (sd/mmc)
storage: SDMMC ????
Sometimes tablet wont boot and have to remove battery connector
Last SP Flash TOOL, linux version have much errors and force to remove battery
http://firmware.su/51343-sp-flash-tool.html
DO NO USE TO DOWNLOAD ANYTHING
UNDER CONSTRUCTION
scatter updated, UNTESTED

Lets go recovery!

idme print as su
unlock_code:
---------- Post added at 12:09 PM ---------- Previous post was at 11:52 AM ----------
There are 2 boads type and 2 preloaders......
Mine have preloader_prod.img board_id: 0025001040000015
Code:
# check if production device
if ("0025001000000015" == read_file_str("/proc/idme/board_id") ||
"0025001000010015" == read_file_str("/proc/idme/board_id") ||
"0025001010000015" == read_file_str("/proc/idme/board_id") ||
"0025001010010015" == read_file_str("/proc/idme/board_id") ||
"0025001020000015" == read_file_str("/proc/idme/board_id"))
then
ui_print("Copying preloader.img to boot partition 0 for unsecure device...");
package_extract_file("images/preloader.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
else
ui_print("Copying preloader_prod.img to boot partition 0 for secure device...");
package_extract_file("images/preloader_prod.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
endif;

my /proc/idme/board_id reads 0025001040000015

Can anyone try this: http://forum.xda-developers.com/showthread.php?t=2798257?
Sent from my KFFOWI using Tapatalk

I did yesterday didn't work

Awesomeslayerg said:
I did yesterday didn't work
Click to expand...
Click to collapse
Did you try Fastboot boot recovery.img with the one it gave?
Sent from my XT912 using Tapatalk

No I'll try today

Okay i used the MTK-TWRP thing right now and used it to unpack the recovery image and it looks like we can use this to our advantage to flash unverified files by editing some of the prop settings.

Can someone try this: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device? It might work.

How would we flash it?

Awesomeslayerg said:
How would we flash it?
Click to expand...
Click to collapse
Zips are flashable in flashfire...

Awesomeslayerg said:
How would we flash it?
Click to expand...
Click to collapse
Use the following commands to flash the recovery
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
- I have Cyanogenmod Recovery working except a few minor niggles
- Let you know once it's fully working
- It looks like we can't boot unsigned images that are flashed to the recovery partition
- If I boot the image from fastboot rather than flashing it then it works
- CVE-2014-0973 is patched in the bootloader