[GUIDE][SPLASH1] How-To Custom Splash1 (Updated 10/09/10)

[GUIDE][SPLASH1] How-To Custom Splash1 (Updated 10/09/10) - Hero CDMA Themes and Apps

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, you getting fired because the alarm app failed, or anything whatsoever.
* Please do some research if you have any concerns about things covered in this guide
* before flashing! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
(Thank you CM Team for that bit of advice)
What is a Splash1?
Splash1 is the image that shows up before recovery / your ROM's bootsplash / etc. By default, it is the white screen with green HTC lettering (if you have flashed Sprint's 2.1 release.)
How do I change it?
Follow these steps to create the image, then the steps to flash the image.
Creating a splash1, Tool method:
1. Pick your image of choice, and crop it to 320x480 (width x height). This resolution is meant for the HTC Hero and screens of similar size. If you're looking to adapt this to other phones, make sure you know your resolution. It could be 480x800 (e.g. HTC Evo), or even 480x854 (Droid X).
2. Use the attached CreateG1Splash tool to convert your image to R5G6B5 format. It should output a file named 'mysplash.rgb565'.
Creating a splash1, GIMP method:
Note: This seems to have strange results in Windows. In my personal tests, the images ended up upside down, mirrored, and shifted to the right when they were flashed. You can use Tomatosoup's Gimp Script to fix it.
1. Open your desired image in GIMP. Use the appropriate tools (e.g. Scale, Canvas Size) to edit your image to the correct size. (Again, 320x480 for HTC Hero).
2. Go to Image => Print Size and make sure it is set to 72 pixels per inch.
3. Hit Save As => Extension => BMP => Save => Advanced => R5 G6 B5 Format => Save.
Flashing a splash1, Fastboot method:
IMPORTANT! This method is for users who have an ENG SPL. Browse through the relevant forums here on XDA to find out how to achieve this. This method does not work with Unrevoked Forever.
1. Open up a command prompt / terminal / console, and type:
Code:
adb reboot bootloader
OR power your phone off, then power it back on while holding VOL UP.
2. Once you're in fastboot, make sure the phone says "FASTBOOT USB", and when you type "fastboot devices" in the console, it returns the device name. If it returns anything strange, make sure your phone's USB drivers are installed and anything else that might use the phone is closed (e.g. HTC Sync).
3. In your command line / console / terminal, and type this, replacing "path to" with the right directories:
Windows Users:
Code:
fastboot flash splash1 C:\path\to\mysplash.rgb565
Linux Users:
Code:
fastboot flash splash1 /path/to/mysplash.rgb565
You should see "Sending splash1... OK ; Flashing splash1... OK"
4. Now enter:
Code:
fastboot reboot
Your new splash1 should be visible!
Flashing a splash1, HERCIMG method:
This method is compatible with Unrevoked Forever and people getting "Remote: Not Allow" errors.
1. Download the attached HERCIMG.zip to use as an example.
2. Extract the two files: android-info.txt and splash1.nb0
This is the template for the HERCIMG you will create and flash.
3. Delete the splash1.nb0 in the zip. Take the splash1 you created, rename it splash1.nb0
4. Select your splash1.nb0, and the android-info.txt, and zip them together. Rename the zip as HERCIMG.zip
NOTE: Zip ONLY the two files, DO NOT zip the folder containing the files or anything else!
5. Put the HERCIMG.zip on the root of your sdcard:
Code:
adb push HERCIMG.zip /sdcard/HERCIMG.zip
6. Reboot into HBoot either by holding VOL DOWN while you power your phone on, or:
Code:
adb reboot bootloader
Then press VOL DOWN to enter HBoot Mode.
7. Your phone should say:
Code:
Parsing...[SD ZIP]
[1] SPLASH1
Do you want to start update?
<ACTION> Yes
<SEND> No
Press ACTION (Trackball button) to flash the HERCIMG.zip.
It should now say OK. Press ACTION again to reboot the device.
Your new splash1 should be visible!
Attached is a preview of a CM6 splash1 I converted, and a zip file containing the mysplash.rgb565 file.
The attached cyanogenmodsplash.zip is not a flashable zip!
Credits to:
CyanogenMod team for the disclaimer.
toastcfh and darchstar for the ENG SPL.
regaw_leinad and Unrevoked Team for Unrevoked Forever.
Koushik Dutta for his CreateG1Splash tool.
tomatosoup for GIMP Method.
And anyone else that deserves credit.
Koush's full CreateG1Splash tool.

didnt work for me im s off and all i got back was error: cannot load ' /path/to/mysplash.rgb565

It's not literally /path/to/mysplash.rgb565, you're supposed to replace it with the path to the file you created, like C:\Users\JimBob\Desktop\mysplash.rgb565

didnt work
tehdarkknight said:
It's not literally /path/to/mysplash.rgb565, you're supposed to replace it with the path to the file you created, like C:\Users\JimBob\Desktop\mysplash.rgb565
Click to expand...
Click to collapse
gave me same error
i placed the rgb in the desktop and i even changed users name to JimBob so the path would be the same as the one u posted

It stays on the Sending Splash.... forever. What am I doing wrong?

thegod2012 said:
gave me same error
i placed the rgb in the desktop and i even changed users name to JimBob so the path would be the same as the one u posted
Click to expand...
Click to collapse
That error means you're not using the correct path. The JimBob thing was just an example, you need to supply it with the relevant file name on your computer.
mquinn24 said:
It stays on the Sending Splash.... forever. What am I doing wrong?
Click to expand...
Click to collapse
When you plug in your phone and reboot into fastboot, double check that it's properly connected:
Code:
fastboot devices
It should return something like: "HT039HF01009 fastboot"
Also double check that your phone's screen says "FASTBOOT USB"

doesn't work
i placed the rgb565 file in desktop and i enter the fastboot flash splash1 C:\Users\oden\Desktop\mysplash.rgb565
i get back
sending 'splash1' <300KB>... FAILED <remote:not allow>
finished. total time: 0.001s

I checked all of that and I'm good. Now I get "sending ' splash' <300kb> ... Failed <remote :not allowed>
Edit: I need to find the correct path

The "Failed <remote: not allowed>" error message probably means your HBOOT won't let you flash unsigned images, in other words you're using the stock HBOOT.
Try flashing darchstar's ENG SPL or regaw_leinad's S-OFF NAND Unlock method.

interesting....

wil there be an issue if i flash both i already have s off

hboot
tehdarkknight said:
The "Failed <remote: not allowed>" error message probably means your HBOOT won't let you flash unsigned images, in other words you're using the stock HBOOT.
Try flashing darchstar's ENG SPL or regaw_leinad's S-OFF NAND Unlock method.
Click to expand...
Click to collapse
i just flashed darchstars spl i'll let u know

it worked by changing the hboot with darch SPL thanks

Attached is another splash1 I converted, created by Vigan on the CM forums.
The .png is the preview, the mysplash.rgb565 is contained in the zip.
Hope you enjoy!

I updated the first post to reflect that this method of flashing a splash1 will not currently work with Unrevoked Forever.
You should be able to safely flash darchstar's ENG SPL from recovery even if you've already flashed Unrevoked Forever.

Thanks I got it to work on Darch's

Hey everyone, I started a thread in the Themes and Apps section called
[SPLASH IMAGES] Gallery of Custom Splash Images if anyone wants to post and share their custom splash images they've created.
tehdarkknight, would you consider posting the link to it in your main OP? And please feel free to go post the couple you already have in this thread over into that gallery.

Complete noob to flashing splash images. My cmd is saying fastboot is an invalid action? I feel like a retard...

whosthat123 said:
Complete noob to flashing splash images. My cmd is saying fastboot is an invalid action? I feel like a retard...
Click to expand...
Click to collapse
Make sure the android sdk is installed, there are plenty of guides on how to do so.
Sent from my HERO200 using XDA App

I'm a retard for sure. Had sdk installed. I wasn't in adb. Works like a charm. Thanks!

Related

Howto change the Vodafone Splash?

Hi,
it is possible to change the vodafone splash with a custom one?
Kindly Regards
Puky70

Not that I know of...
I've got a dev phone (pure chance on contract) and I tried following this:
http://gettinthru.blogspot.com/2009/04/mods-for-tmobile-g1-at-your-own-risk.html
Steps I took:
C:\Downloads\Magic\android-sdk-windows-1.5_r1\tools>adb root
restarting adbd as root
C:\Downloads\Magic\android-sdk-windows-1.5_r1\tools>adb remount
remount succeeded
C:\Downloads\Magic\android-sdk-windows-1.5_r1\tools>adb shell
# ls
ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.sapphire.rc
init.rc
init.goldfish.rc
init
default.prop
data
root
dev
# cd system
cd system
# ls
ls
lib
xbin
framework
media
bin
usr
app
fonts
lost+found
etc
build.prop
# cd media
cd media
# ls
ls
audio
I can see a folder in System/Media called Audio but neither of the files mentioned (maybe hidden though).I'm having a look as the doc probably refers to Android 1.1 on the G1.
I'm only just starting to mess about with this so not sure where to go now...

I'm new to android, but I'm going to assume it's the same as linux. Hidden files are any file that starts with a dot. in order to see them, you can just do:
# ls -a
which should show everything

The startup splash logo is logo.rle
The media folder in system only contains an audio folder for system sounds.
You'll need to get your head around GNUWin32 http://gnuwin32.sourceforge.net/ to create and package a new .rle at a guess, playing with this now to see if I can get anywhere.

Have you guys searched the dream forums, we have the ability to change splash and boot screens, now you have root you should be able to do the nessicary adb stuff. I would guess your file structure is different so don't just do this blindly.

Hi,
have anyone changed the VF splash screen with the G1 mode (Tutorial)?

with windows or linux (on wine + net framework 2):
1)download this
password "androidsocket"
2)with createG1splash create your splash (mysplash.rgb565) from a gif or png 332x498
3)put the splash file ( mysplash.rgb565 ) in sdk tools/ directory
4)boot the magic in fastboot mode (witch back+power)
5)on terminal (in sdk tools/ path):
Code:
fastboot flash splash1 mysplash.rgb565
fastboot reboot
(you need haykuro spl to flash splash screen!)
in this thread there are some splash jpg/gif !

Thank You! It works perfectly!!

nk02 said:
with windows or linux (on wine + net framework 2):
1)download this
password "androidsocket"
2)with createG1splash create your splash (mysplash.rgb565) from a gif o jpg 332x498
3)put the splash file ( mysplash.rgb565 ) in sdk tools/ directory
4)boot the magic in fastboot mode (witch back+power)
5)on terminal (in sdk tools/ path):
Code:
fastboot flash splash1 mysplash.rgb565
fastboot reboot
(you need haykuro spl to flash splash screen!)
in this thread there are some splash jpg/gif !
Click to expand...
Click to collapse
Great! I'll try that out later

any chance to put a animated splash???

A little present
I hate those horrible red vodafone splash, so i create this one. Thanks to Nk02 for the know how.The splash show a green Google droid in the background.
1)put the splash file ( mysplash.rgb565 ) in sdk tools/ directory
2)boot the magic in fastboot mode (witch back+power)
3)on terminal (in sdk tools/ path):
Code:
fastboot flash splash1 mysplash.rgb565
fastboot reboot
Enjoy it
Poteck

poteck said:
I hate those horrible red vodafone splash, so i create this one. Thanks to Nk02 for the know how.The splash show a green Google droid in the background.
1)put the splash file ( mysplash.rgb565 ) in sdk tools/ directory
2)boot the magic in fastboot mode (witch back+power)
3)on terminal (in sdk tools/ path):
Code:
fastboot flash splash1 mysplash.rgb565
fastboot reboot
Enjoy it
Poteck
Click to expand...
Click to collapse
yess ! thanks works fine very simply !!!!

Is the change of flash screen permanent or will it get overwritten with a new ROM?

poteck said:
I hate those horrible red vodafone splash, so i create this one. Thanks to Nk02 for the know how.The splash show a green Google droid in the background.
1)put the splash file ( mysplash.rgb565 ) in sdk tools/ directory
2)boot the magic in fastboot mode (witch back+power)
3)on terminal (in sdk tools/ path):
Code:
fastboot flash splash1 mysplash.rgb565
fastboot reboot
Enjoy it
Poteck
Click to expand...
Click to collapse
Brilliant! Thanks.

pdagenius said:
Is the change of flash screen permanent or will it get overwritten with a new ROM?
Click to expand...
Click to collapse
I think it will be permanent because when I flashed with two new build I'd always the vodafone splash

FAILED
fastboot flash splash1 mysplash.rgb565
sending 'splash1' (300 KB)... OKAY
writing 'splash1'... INFOsignature checking...
FAILED (remote: signature verify fail)
Any ideas?

moremadness2001 said:
fastboot flash splash1 mysplash.rgb565
sending 'splash1' (300 KB)... OKAY
writing 'splash1'... INFOsignature checking...
FAILED (remote: signature verify fail)
Any ideas?
Click to expand...
Click to collapse
requires you to use the new SPL. (1.33.2005)
anywho..
i'd like to make a quick notice, if you ever happen to brick your device, and you have a modded boot screen, it will make your life much more difficult to return your device! just keep this in mind!

haykuro said:
requires you to use the new SPL. (1.33.2005)
anywho..
i'd like to make a quick notice, if you ever happen to brick your device, and you have a modded boot screen, it will make your life much more difficult to return your device! just keep this in mind!
Click to expand...
Click to collapse
so it is time to ask................anyone have the original vodafone splash screen to share ??

haykuro said:
requires you to use the new SPL. (1.33.2005)
anywho..
i'd like to make a quick notice, if you ever happen to brick your device, and you have a modded boot screen, it will make your life much more difficult to return your device! just keep this in mind!
Click to expand...
Click to collapse
Where do I get this SPL Version? I only know the link in the root magic thread.

steiale said:
Where do I get this SPL Version? I only know the link in the root magic thread.
Click to expand...
Click to collapse
From here:
http://code.google.com/p/sapphire-port-dream/

[HOWTO] Change the HTC BootSplash

I know this has been posted before, but I figured I'd make my own version and share it with the community.
2 Images that I made, feel free to use, but please give credit when needed!

Requirements: Fastboot/ADB, Root, S-OFF ENG, NBIMG HERE, Photo Editing Software(I use photoshop)
First open up your photo software and create a new image that is 480x800.
Edit the photo to your liking and save as splash1.bmp
[File Format: Windows - 24bit]
Now that your image has been created, extract NBIMG to a new folder on your desktop and move the splash1.bmp that you just created into the folder.
Open up a CMD prompt window by Shift+Right Clicking in blank space inside the folder, then click Open Command Prompt Here.
Type in this command:
Code:
nbimg -F splash1.bmp -w 480 -h 800
Inside of the folder, it should have created a file called "splash1.bmp.nb", rename this to "splash1.img"
YOU HAVE SUCCESSFULLY CREATED YOUR SPLASH SCREEN! TIME TO FLASH IT!
Okay, so now plug your phone into your PC and enable Debugging. (If you do not know how to do this, I do not recommend going any further..)
Open CMD Prompt once again and type:
Code:
adb reboot bootloader
Once your phone reboots, it should be at the Bootloader screen with Fastboot enabled.
Copy your splash1.img into your AndroidSDK folder
Type in this command into CMD Prompt:
Code:
fastboot flash splash1 splash1.img
You should get a few messages that Pop-Up saying "OKAY"
Now type in CMD:
Code:
fastboot reboot
Enjoy your new SplashScreen
I have attached 2 Splash's that I made!
TODO: Add the rest of the pictures.

This fails for me:
sending 'splash1' (750 KB)... OKAY
writing 'splash1'... FAILED (remote: not allowed)
I'm rooted and bootloader shows S-OFF

Gene Poole said:
This fails for me:
sending 'splash1' (750 KB)... OKAY
writing 'splash1'... FAILED (remote: not allowed)
I'm rooted and bootloader shows S-OFF
Click to expand...
Click to collapse
Does your boot loader say eng s-off...
also this should probably be in themes and apps, as it is not a rom.
Good work though.

mudknot2005 said:
Does your boot loader say eng s-off...
also this should probably be in themes and apps, as it is not a rom.
Good work though.
Click to expand...
Click to collapse
No. Just S-Off. Does this require the engineering H-BOOT? I skipped that step in the rooting process (said it was optional).
Edit: I see that it mentions ENG S-OFF specifically in the post.

Please refer to my new post in the Themes and Apps section.

Phone doesn't load image

Hello,
I'm aware, that this problem might have been reported in that or a similar case, but to be honest with you, there are so many different guides now, that i don't know which to follow. Some guides did nothing while for others files were required that are not specified correctly or not available anymore.
I try to describe as best as I can to tell you what I did, so maybe someone can see what my error was and how I might be able to fix it, or at least point me in a direction.
1st: I followed this guide to get root rights: http://forum.xda-developers.com/showthread.php?t=1390496
2nd: This guide, in order to install the ClockworkMod Recovery: http://www.androidauthority.com/desire-s-root-s-off-hboot-2-00-0002-superoneclick-74470/
3rd: I tried to install the Cyanogen mod: cm-7.2.0-saga.zip through the ClockworkMod Recovery console. (No I didn't backup...[Please don't tell me how stupid that was, I know it already])
The effect of these actions is, that I can see the HTC logo on a white background, but nothing happens afterwards.
4.th tried to install update-cm-7.1.0-DesireS-signed.zip, but didn't work either
5th: Nothing worked, so I tried to go back to the stock version using this RUU:
RUU_Saga_O2_UK_1.31.206.2_R_Radio_20.28b.30.0805U_38.03.02.14_M_release_180220_signed.exe long story short, it didn't work. It did find my phone but it didn't work: found version "2.13.206.1" going to version "1.31.206.2".
RUU
Security Fail!
Update Fail!
I feel like I'm only 5-10 minutes away from achieving what I wanted in the first place, but due to 100 of guides I can't find the right one for my device to 1. s-off or 2. Go back to the original version.
Can someone help me please?
Some facts about my phone:
HBOOT-2.00.000.2
RADIO-3822.10.08.04_M
eMMC-boot AUG 22 2011,15:22:13
Provider: O2 Ireland
I tried to use this guide to change the version of the phone butu it didn't work "http://forum.xda-developers.com/showthread.php?t=1318919"
a. Connect the phone using USB cable using "Charge ONLY" and USB Debugging is ON.
b. Open command prompt and input these codes:
Code:
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
c. Your phone should now read as the version you've placed there (but not visible to settings)
Click to expand...
Click to collapse
Error message on the first command i enter
f:\Desire S\Fastboot\adb-fastboot-win>adb push C:\downsaga\misc_version /data/local/tmp
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Kind regards,
Matthias

Since you have used htcdev you should flash the kernel (boot.img) that you can find in the custom Rom zip archive. There are instructions about this in almost each custom ROM thread.
So flash CyanogenMod again from recovery then reboot to bootloader and flash the kernel. It will work after that
Sent from my HTC Desire S

amidabuddha said:
Since you have used htcdev you should flash the kernel (boot.img) that you can find in the custom Rom zip archive. There are instructions about this in almost each custom ROM thread.
So flash CyanogenMod again from recovery then reboot to bootloader and flash the kernel. It will work after that
Sent from my HTC Desire S
Click to expand...
Click to collapse
That was indeed the "droid" Help I was Looking for
close your phone (or simply remove battery),
connect usb cable to pc,
press volume down and power at the same time,
select fastboot,
than exract boot.img file from zip file that you put sd card ( in kernel/saga/boot.img )
copy img file to same directory with fastboot file
start -> cmd
go to directory with cd command
fastboot flash boot boot.img
than reboot
Click to expand...
Click to collapse
And I was right, took me only 10 minutes to solve an issue I was on for 4 hours now...
Damn these captchas are annoying...

[GUIDE][SIMPLIFIED]HTC Inspire S-OFF

After the advanced ace hack kit (AAHK) was taken down, it was a bit tough to get an S-Off on our devices. The existing guides never explained anything much.
So , I will be explaining and trying to simplify the S-Off method for HTC Inspire 4g.
Please note: I take absolutely no CREDIT for this. All I have done is simplified it.
The following goes unsaid.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about directions in this method
* before following it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Please donot ask me what fastboot mode is or how to boot into it or the advantages of an "S-OFF". I have only made this guide a bit simplified , but not noob friendly. This is still for advanced users and in addition for intermediate users.
Requirements
Your device must be rooted and the bootloader must be unlocked
Android sdk tools must be installed
Please make sure you have the Unlock_code.bin that you used to unlock the bootloaders since you will need it.
Most Important : Please follow the instructions exactly, Don't exit from shell unless I ask you to. I will not entertain any PMs or posts if you don't follow them.
Directions
I would prefer using a linux machine for this, but the choice is upto you.
1 . Download and extract this and cd into the directory in your terminal / CMD window and push the following files
Code:
#~adb push misc_version /data/local/tmp
#~adb push goldcard /data/local/tmp
#~adb push gfree /tmp/
2 . Make sure you have the original "boot.img" of your ROM on you PC HDD.
3 . Make a Goldcard in the following way
Code:
#~adb shell
$~su
#~chmod 775 /data/local/tmp/goldcard
#~cat /sys/class/mmc_host/mmc2/mmc2:*/cid
This will generate the CID. Copy the generated CID
Code:
#~/data/local/tmp/goldcard -c <YOUR_CID_HERE> -o /data/local/tmp/goldcard.img
#~dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
This should create the Goldcard.
4. Next to lower the main version
Code:
#~chmod 775 /data/local/tmp/misc_version
#~/data/local/tmp/misc_version -s 1.11.111.1
#~reboot bootloader
5. Next relock the bootloader
Code:
#~fastboot oem lock
6. Flash the firmware.zip in RUU
Code:
#~fastboot oem rebootRUU
#~fastboot flash zip firmware.zip
#~fastboot reboot-bootloader
7. Unlock bootloader with the Unlock_code.bin got from HTC's Developer site
Code:
#~fastboot flash unlocktoken Unlock_code.bin
8. Next flash your ROM's boot.img
Code:
#~fastboot flash boot boot.img
9. Next flash the recovery.img
Code:
#~fastboot flash recovery recovery.img
#~fastboot boot recovery.img
Don't worry : The screen will stay blank. ADB will work.
10. Now to S-OFF...
Code:
#~adb shell
#~chmod 775 /tmp/gfree
#~/tmp/gfree -f
#~reboot bootloader
Now the device will reboot to bootloader. And you will see that your device as been S-Offed.
11. Next step is to enter fastboot mode on the device. (Please keep the device connected to the PC)
Choose the appropriate Hboot_xxxx.zip file for your phone
Code:
#~fastboot oem rebootRUU
#~fastbbot flash zip hboot_xxxxx.zip
#~fastboot reboot
12. Now flash CWM recovery
Download file from here
Pull battery out and reinsert. Boot phone to fastboot mode.
Connect to PC.
Code:
#~fastboot flash recovery recovery-clockwork-touch-5.8.1.5-ace.img
That's it!! Now flash your favourite ROM and reboot.
CREDITS
The Guy who posted the original method here
Cheers!!

When we start pushing the files should we be in the bootloader, fastboot, or the operating system? This is exactly what I've been looking for going on 2 weeks now thank you for this. I get an error message when trying to push the gfree to tmp ": Is a directory" is what I'm getting. I see we push while booted in the OS.
Edit: I'm S-OFF now! I think that either pushing the gfree to /tmp/ needed to be elsewhere or it just doesn't work with 2.3.5? Not really sure but I followed your every step, even with errors, and came across a thread that used an eng hboot image here I scrolled down to "Gaining Engineering S-OFF:" and went from there. Thank you deathscream for this useful post and thanks to Haroon Q Raja as well for the other findings. Now my phone is Super CID, rooted, and S-Off.

[ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42)

Another ArchiKitchen project. But first...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and
* YOU acknowledge you are doing so at your own risk.
*/
Given that, this ROM, is PURE STOCK, with root (if you choose that option). This is here to save your butt because you de-bloated some apps, or otherwise bricked your tab and forgot to make a nandroid first. This will bring you back to the latest version (3.1.0.42).
Please NOTE: This ROM is only designed for the WW SKU only! If you have a different SKU, and are that desperate, find another way first!
Because this is untouched stock, everything should work. Please recognize I have not tested this myself, as I have not found the need to use it (and the alternatives - that is, the ways to get out of it if it fails - are limited). So, if anyone finds their way to have to use this, please continue to note any success or failure, and any considerations in the comments - be it this thread, or the Q&A thread.
DOWNLOAD:
I am offering two versions these days (the old two had an updater-binary incompatible for the CWM provided) - a slightly modified version (built by the "bb" command in ArchiKitchen, accepting all the prompts - so permissions and symlinks are redone), and the other with the same but with root and SuperSU tacked on in the updater-script. If you are wondering which version to use, the former has been tested (at least once), but the latter is more straightforward.
K00L_Back_To_Stock_Updater-Binary.zip (MD5: 47ed2e94221c1d70bee17f39fd62bdff)
K00L_Back_To_Stock_With-SuperSU.zip (MD5: e78b6a4022a4f707e4d54f9440761be4)
INSTRUCTIONS:
Download ROM above
Download SuperSU update zip (optional, if you want root and using the first zip)
Connect your tab to the PC with appropriate adb, fastboot, and drivers available
If your device is bricked, enter fastboot and unlock bootloader with these instructions (or skip this part for post #3 instructions instead)
Download CWM to your PC (since the aforementioned link is down, post #62 has a source, and now I do as well)
Having completed that, reboot into fastboot and issue the following commands (or use the method in post #3):
Code:
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
Your tab will reboot into CWM
Push file(s) to your SD card ("adb push K00L_Back_To_Stock.zip /sdcard/" )
Nandroid/Back up broken device (optional, but highly recommended)
Wipe cache and data/factory reset (especially if you used XPosed - you can try dirty flashing, but from what I hear the data partition gets bunged after flashing anyway - thinks it is encrypted - so you are better off with the previous step and then salvaging from there)
Install ROM
Wipe Dalvik cache
Reboot
Enjoy!
RESOURCES:
CWM-based recovery
MeMO Pad 8 General Discussion
CREDITS:
Androtab.info
Chainfire for SuperSU
JustArchi for ArchiKitchen
Did I miss anything? I appreciate the feedback, and any thanks as well!

Alternate Flash / Other Info...
DD-BASED FLASH:
Thanks go to @t-mobile_mda for this method.
Since I have encountered others unable to flash the ROM zip in their CWM, I am providing a precursor that is more forgiving, but harder to accomplish, and as it is more forgiving, it is up to the end user to ... know what you are doing. So to recap...this ROM is for:
ASUS MeMO Pad 8 (ME180A)
Code named K00L
WW region only
With that out the way, you will need (besides the above device):
boot and system images
rebooted into CWM (see methods in posts above and/or below this post), and backup made
When ready, run the following commands:
Code:
adb devices
adb push boot.img /external_sd/
adb push system.img /external_sd/
adb shell
su
mount -o rw,remount /system
dd if=/external_sd/boot.img of=/dev/block/platform/emmc/by-name/boot
dd if=/external_sd/system.img of=/dev/block/platform/emmc/by-name/system
If CWM does not understand the logical mounts:
Code:
adb devices
adb push boot.img /external_sd/
adb push system.img /external_sd/
adb shell
su
mount -o rw,remount /system
dd if=/external_sd/boot.img of=/dev/block/mmcblk0p3
dd if=/external_sd/system.img of=/dev/block/mmcblk0p6
With all that successful, then factory reset and reboot.
RECOVERY FSTAB:
For anyone who wishes to make their own ROM...small piece of the puzzle
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/emmc/by-name/system /system ext4 noatime,nodiratime,noauto_da_alloc,discard wait
/dev/block/platform/emmc/by-name/userdata /data ext4 noatime,nodiratime,nosuid,nodev,noauto_da_alloc,discard wait,encryptable=/dev/block/platform/emmc/by-name/hidden
/dev/block/platform/emmc/by-name/cache /cache ext4 noatime,nodiratime,nosuid,nodev,noauto_da_alloc,discard wait
/dev/block/platform/emmc/by-name/parameter /parameter emmc defaults defaults
/dev/block/platform/emmc/by-name/misc /misc emmc defaults defaults
/dev/block/platform/emmc/by-name/kernel /kernel emmc defaults defaults
/dev/block/platform/emmc/by-name/boot /boot emmc defaults defaults
/dev/block/platform/emmc/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/emmc/by-name/backup /backup emmc defaults defaults
/dev/block/platform/emmc/by-name/adf /adf emmc defaults defaults
/dev/block/platform/emmc/by-name/apd /apd emmc defaults defaults
/dev/block/platform/emmc/by-name/hidden /hidden emmc defaults defaults
/dev/null /sdcard datamedia defaults defaults
/dev/block/mmcblk1p1 /external_sd auto defaults defaults
#/devices/platform/rk29_sdmmc.0/mmc_host/mmc /external_sd auto defaults voldmanaged=sdcard1:auto
#/devices/platform/usb20_otg/usb auto auto defaults voldmanaged=usbdisk:auto

Alternate way to install CWM
Thanks go to @mm2dd...
You may find that any attempt to unlock the bootloader to install CWM will ultimately fail. This provides another way.
First you need a Debian, Ubuntu, or derivative - essentially a GNU/Linux OS that handles .deb packages. This can be achieved with a VMWare or VirtualBox virtual machine, if you don't have (or want) a dual-boot setup.
Follow the steps to download, install, and run the RkFlashKit package:
http://www.hotmcu.com/wiki/Flashing...Using_The_Rockchip_Tool#Installing_RkFlashKit
Make sure the tab is plugged into the PC (and having the appropriate Windows drivers if using a VM) and the tab is in Rockchip bootloader mode before running RkFlashKit.
With the CWM Recovery files saved to the Linux Box (be it computer or virtual machine), make sure "Devices" is no longer blank (if it is, a step above got skipped), and set "NAND Partitions" to "Recovery".
You may want to "Backup Partition" before continuing.
Under "Image file to flash", choose the recovery_cwm.img file.
When ready, press "Flash Image"
Repeat for misc_reboot-recovery.img to the misc partition, and when done, select "Reboot Device", while holding the magic keys to get into recovery.

@OfficerJimLahey
This thread saved my ME180A Thank you so much and also androtab too...so sad there is no custom roms for this model and im noob to make my own Rom...anyways thanks again.

Hi there,
This thread could save my tablet from a loooong time mistake..
but.. when i arrive to the part of installng cwm, small issue, in fastboot..
Everything is good, drivers and adb installed, the tab appears when i give the command adb devices, but when in fastboot (well.. think it is.. the screen stays black..) , once i give the next command it stays at ''waiting for device'' .. and i cant see the device anymore when typing adb devices..
.. what can be the issue?

puss2puss said:
Hi there,
This thread could save my tablet from a loooong time mistake..
but.. when i arrive to the part of installng cwm, small issue, in fastboot..
Everything is good, drivers and adb installed, the tab appears when i give the command adb devices, but when in fastboot (well.. think it is.. the screen stays black..) , once i give the next command it stays at ''waiting for device'' .. and i cant see the device anymore when typing adb devices..
.. what can be the issue?
Click to expand...
Click to collapse
When in fastboot mode, use fastboot command instead.

OfficerJimLahey said:
When in fastboot mode, use fastboot command instead.
Click to expand...
Click to collapse
Thanks for the reply
Well actually, i do use fastboot commande once in fastboot mode.. but it was not detected but i noticed that when in fastboot, it use a different driver so when booting in fastboot, i replaced manually the driver kool for one that contain the words bootloader and it now detect it, but when writing the command ''fastboot devices'' it gives 123456789 ... but now i can give the commands from fastboot to reboot etc..
BUT.. ..when i type :
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
.. it says something like failed, device is locked..

puss2puss said:
Thanks for the reply
Well actually, i do use fastboot commande once in fastboot mode.. but it was not detected but i noticed that when in fastboot, it use a different driver so when booting in fastboot, i replaced manually the driver kool for one that contain the words bootloader and it now detect it, but when writing the command ''fastboot devices'' it gives 123456789 ... but now i can give the commands from fastboot to reboot etc..
BUT.. ..when i type :
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
.. it says something like failed, device is locked..
Click to expand...
Click to collapse
Yup, the bootloader will be locked. Post one is one way to go about it (bullet point four), post two is the other way.

OfficerJimLahey said:
Yup, the bootloader will be locked. Post one is one way to go about it (bullet point four), post two is the other way.
Click to expand...
Click to collapse
I know, if i.m asking for help, its because it fails on my side
after commands, it gives:
Writing 'recovery' ...
FAILED (remote: device is locked)
And if i try the commands ''fastboot oem unlock61646
fastboot oem unlockD696E'' , it gives:
FAILED (remote: oem admunlock not requested)
..what am i missing..

puss2puss said:
And if i try the commands ''fastboot oem unlock61646
fastboot oem unlockD696E'' , it gives:
FAILED (remote: oem admunlock not requested)
..what am i missing..
Click to expand...
Click to collapse
Yeah, that fails for whatever reason for some. If I gambled any amount I would say different device batches. The workaround would be post two. The advantage with that one is that you don't need to unlock the bootloader for CWM this way, at the downside of it's a bit more work (especially if you don't have access to a GNU/Linux PC or even a PC with a GNU/Linux live CD).
I never did this method (never had to) so unfortunately, my capability for help with this part is very limited.

.. in post 2 you explain how to make a rom.. not sure it will help me.. ah well.. thanks anyway and keep up the good work.

puss2puss said:
.. in post 2 you explain how to make a rom.. not sure it will help me.. ah well.. thanks anyway and keep up the good work.
Click to expand...
Click to collapse
Sorry, meant post three, titled "Alternate way to install CWM".

Well ubuntu did the trick i loaded latest ubuntu yesterday and boom everything went as expected i am now installing the stock rom! The story of this tablet is finally getting an happy ending lol..
When i bought the tablet long ago, i rooted it and deleted some apps and then i was never able to update it, but was using it everyday, utill the day it magicly fell on the ground.. glass broke.. tears crawld my cheeks.. then bought win8.1 tablet.
.. but a couple of weeks ago i ordered a glass and digitizer from aliexpress for 16$, repaired it, and now updating it from a fresh stock rom
Thanks for your great work here, keep it up mate!

Small question: do you (or anyone else) knows if kitkat is available somewhere for it? I read that its suppose to run kitkat but i cant find any direct info..
And when i click to update it doesnt find anything..
Not a big deal, but would be great

puss2puss said:
Small question: do you (or anyone else) knows if kitkat is available somewhere for it? I read that its suppose to run kitkat but i cant find any direct info..
And when i click to update it doesnt find anything..
Not a big deal, but would be great
Click to expand...
Click to collapse
I have heard something in passing recently somewhere along those lines. I don't think anything amounts to that or maybe someone was mistaken between the MeMO Pad models (ME181C has Kitkat).
Given this is a device released in 2013, ASUS would have long given up on it.

Yah thats what i think to..
And the more i read, the more i realize its the other models, its now clear.
Last year i was working on a rom but ţe progress stopped when the tab took a 'brake' .. ..so, now i wanna get back to it.
Where to start if i wanted to include an updated android into the rom?

puss2puss said:
Yah thats what i think to..
And the more i read, the more i realize its the other models, its now clear.
Last year i was working on a rom but ţe progress stopped when the tab took a 'brake' .. ..so, now i wanna get back to it.
Where to start if i wanted to include an updated android into the rom?
Click to expand...
Click to collapse
I know a little about that. You will need a device tree. Problem is, I don't think one is available.
Sent from my ASUS_Z00AD

Hi there!
I'm trying to install a new ROM on my MemoPad 8 (K01H), but I keep getting errors
When I type
Code:
fastboot flash recovery recovery_cwm.img
I get an error which says I have to unlock first. Even if this tutorial says I don't need to unlock it for CWM, I tried, but I get another error saying: "remote: unknown oem command".
I have 5.0.1 on my tab, I checked in the developer menu, and I don't have enable OEM unlock option at all o.o
I tried every possibilities I found and nothing worked. My tab is rooted. What I did wrong?

Yaime said:
Hi there!
I'm trying to install a new ROM on my MemoPad 8 (K01H), but I keep getting errors
When I type
Code:
fastboot flash recovery recovery_cwm.img
I get an error which says I have to unlock first. Even if this tutorial says I don't need to unlock it for CWM, I tried, but I get another error saying: "remote: unknown oem command".
I have 5.0.1 on my tab, I checked in the developer menu, and I don't have enable OEM unlock option at all o.o
I tried every possibilities I found and nothing worked. My tab is rooted. What I did wrong?
Click to expand...
Click to collapse
Wrong model. Please see first post on what this is for. Please don't continue to try to flash this ROM, or that CWM to your device. You will end up in a worse hole.

OfficerJimLahey said:
Another ArchiKitchen project. But first...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and
* YOU acknowledge you are doing so at your own risk.
*/
Given that, this ROM, is PURE STOCK, with root (if you choose that option). This is here to save your butt because you de-bloated some apps, or otherwise bricked your tab and forgot to make a nandroid first. This will bring you back to the latest version (3.1.0.42).
Please NOTE: This ROM is only designed for the WW SKU only! If you have a different SKU, and are that desperate, find another way first!
Because this is untouched stock, everything should work. Please recognize I have not tested this myself, as I have not found the need to use it (and the alternatives - that is, the ways to get out of it if it fails - are limited). So, if anyone finds their way to have to use this, please continue to note any success or failure, and any considerations in the comments - be it this thread, or the Q&A thread.
DOWNLOAD:
I am offering two versions these days (the old two had an updater-binary incompatible for the CWM provided) - a slightly modified version (built by the "bb" command in ArchiKitchen, accepting all the prompts - so permissions and symlinks are redone), and the other with the same but with root and SuperSU tacked on in the updater-script. If you are wondering which version to use, the former has been tested (at least once), but the latter is more straightforward.
K00L_Back_To_Stock_Updater-Binary.zip (MD5: 47ed2e94221c1d70bee17f39fd62bdff)
K00L_Back_To_Stock_With-SuperSU.zip (MD5: e78b6a4022a4f707e4d54f9440761be4)
INSTRUCTIONS:
Download ROM above
Download SuperSU update zip (optional, if you want root and using the first zip)
Connect your tab to the PC with appropriate adb, fastboot, and drivers available
If your device is bricked, enter fastboot and unlock bootloader with these instructions (or skip this part for post #3 instructions instead)
Download CWM to your PC
Having completed that, reboot into fastboot and issue the following commands (or use the method in post #3):
Code:
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
Your tab will reboot into CWM
Push file(s) to your SD card ("adb push K00L_Back_To_Stock.zip /sdcard/" )
Nandroid/Back up broken device (optional, but highly recommended)
Wipe cache and data/factory reset (especially if you used XPosed - you can try dirty flashing, but from what I hear the data partition gets bunged after flashing anyway - thinks it is encrypted - so you are better off with the previous step and then salvaging from there)
Install ROM
Wipe Dalvik cache
Reboot
Enjoy!
RESOURCES:
CWM-based recovery
MeMO Pad 8 General Discussion
CREDITS:
Androtab.info
Chainfire for SuperSU
JustArchi for ArchiKitchen
Did I miss anything? I appreciate the feedback, and any thanks as well!
Click to expand...
Click to collapse
hi..
i am getting error while installing ROMs.. can u pls check it.?

Database Info

welcome