Database Info

Modded recovery and boot images

Here is a zip file containing a modified recovery and boot image, as well as a few other things:
http://rapidshare.com/files/166164961/AndroidMod.zip
http://jf.nyquil.org/AndroidMod.zip
http://android-dls.com/forum/index.php?f=24&t=191&rb_v=viewtopic (see post for actual link to file)
NOTE: if you need a complete RC30 to v1.3 guide, see this page.
The recovery image (recovery_testkeys.img) uses the test keys that are distributed with the android platform source. This means that an OTA update or an update.zip update must be signed with the test key in order for it to install. In other words, it will no longer install OTA updates from t-mobile. You don't want them stealing back root access from you now do you? .
I've also included the test keys and the SignApk.jar tool, so you can sign your own update scripts (for use only with the modified recovery image). You can resign any image, even if it has been signed before. So for example, if you needed to install an "official" t-mobile update, you must re-sign it with the test keys first.
Another bonus in this recovery image is that ADB is enabled while in recovery mode. You can't adb into a shell (no sh binary), but you can at least use it to push and pull files from the device. For example, you could push an update.zip file to the sdcard.
The boot image (boot_nosecure.img) has been modified so that adb has root access by default. So when you do an adb shell, you automatically get a root shell. You can remount the system image using adb, and then push files directly to the system partition.
Finally, the "update - Restore Original RC29 Boot Image.zip" file is an update.zip file signed with the test keys, which will restore your boot partition back to the stock RC29 image. Useful if you accidentally hose your boot partition..
To install the recovery image onto your phone:
Code:
D:\Android\AndroidMod>adb push recovery_testkeys.img /data/local/recovery.img
912 KB/s (0 bytes in 1767424.001s)
D:\Android\AndroidMod>adb shell
$ su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system
cd /system
# cat /data/local/recovery.img > recovery.img
cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
flash_image recovery recovery.img
#
Note: You must place the recovery image at /system/recovery.img. the init.rc boot script automatically flashes the recovery partition with that file every time you boot up the phone.
At this point, it's probably a good idea to reboot the phone into recovery mode, and make sure it loads OK. If the recovery image is corrupt somehow, it will throw you back into SPL mode (the multi-color bootloader screen). If that happens, just boot the phone normally, and reflash recovery image.
Once it boots into recovery mode, press alt+L, and the next to top line of text should say something like "using test keys.". If it doesn't, then you're still using the original recovery image.
Note: If you are planning on installing the modified RC30 update, you can ignore the following - there is no need to install the boot image. The update already has a newer, modified boot image.
Now that you know you have the modified recovery image loaded, you can install the boot image:
Code:
D:\Android\AndroidMod>adb push boot_nosecure.img /data/local/boot.img
939 KB/s (0 bytes in 1533952.001s)
D:\Android\AndroidMod>adb shell
$ su
su
# flash_image boot /data/local/boot.img
flash_image boot /data/local/boot.img
# rm /data/local/boot.img
rm /data/local/boot.img
#
Now reboot the phone and let it boot normally. If the boot image was corrupted, it will boot into recovery mode instead. You can use the included update zip file to reload the original RC29 boot image.
Otherwise, if it boots up normally, open a command prompt however you like (telnet, adb, terminal emulator app, etc.) and type "getprop ro.secure". If it says 0, then you're running the modified boot image. Otherwise, if it says 1, you're still running the original boot image.

Attachement..
Hmm. It doesn't look like the attachment made it.. Does anyone have some space I could throw the file up at? It's around 5mb.

JesusFreke said:
Hmm. It doesn't look like the attachment made it.. Does anyone have some space I could throw the file up at? It's around 5mb.
Click to expand...
Click to collapse
I should have some space let me know

JesusFreke said:
Hmm. It doesn't look like the attachment made it.. Does anyone have some space I could throw the file up at? It's around 5mb.
Click to expand...
Click to collapse
Sent you an email with u/p if you need space.

test
anyway to test and make sure i did this correctly.. other than my phone booted and is not a paperweight

jriley60 said:
anyway to test and make sure i did this correctly.. other than my phone booted and is not a paperweight
Click to expand...
Click to collapse
To check the boot image, boot the phone normally, and then get a shell with adb. Type "id", and see if you are root
To check the recovery image, boot up the phone into recovery mode. Once you're in recovery mode, Press alt-l to show the text. The next to top line should say something like "using test keys"

JesusFreke said:
To check the boot image, boot the phone normally, and then get a shell with adb. Type "id", and see if you are root
To check the recovery image, boot up the phone into recovery mode. Once you're in recovery mode, Press alt-l to show the text. The next to top line should say something like "using test keys"
Click to expand...
Click to collapse
When will we see the files? Can you just upload to RS and we will mirror?

neoobs said:
When will we see the files? Can you just upload to RS and we will mirror?
Click to expand...
Click to collapse
Look at the original post. I added a link for the zip file..

boot.img is in correct. assuming typing id in telnet returning uid=0(root) gid=0(root) means i'm root then i'm good, thank you so much. looks like i really should install the emulator it might make things a little easier

JesusFreke said:
Look at the original post. I added a link for the zip file..
Click to expand...
Click to collapse
thank you. Sorry

jriley60 said:
boot.img is in correct. assuming typing id in telnet returning uid=0(root) gid=0(root) means i'm root then i'm good, thank you so much. looks like i really should install the emulator it might make things a little easier
Click to expand...
Click to collapse
Well, that does mean you have root, but that doesn't say anything about whether the boot.img was installed correctly. If you're telneting in, then you would have root access regardless of whether you are running a stock boot image or my modified one.
My boot image allows adb to connect to the phone as root. If you don't use adb, there's no reason to install my modified boot image.
Actually, there's an easier way to tell if you're running my boot image. Get to a command prompt (telnet, adb, terminal emulator app, whatever), and type
getprop ro.secure
If it says 0, then you correctly installed my boot image. Otherwise, if it says 1, you're still running the stock image.

Thanks! Was waiting for this.
Now to screw with my phone like crazy

Not that I don't trust you... but...
Ok... I don't trust you implicitly enough to reflash my phone with your stuff
Any chance you can post diffs against the android source tree so I can apply your changes and build it myself?
No offense - I just like to know what's going on...

RyeBrye said:
Ok... I don't trust you implicitly enough to reflash my phone with your stuff
Any chance you can post diffs against the android source tree so I can apply your changes and build it myself?
No offense - I just like to know what's going on...
Click to expand...
Click to collapse
Not at all
The recovery tool is just a stock build (almost) from the android source, using the test keys, which is the default if you don't specify keys of your own. The only change I made was to make it print out "using test keys" when it runs, just to make it easy to tell if it's running. I can give you a diff if you really want.. but it's a simple change though, and doesn't affect the actual functionality.
For the boot image, I replaced the initramfs image in the boot.img included in the official RC29 update, with the initramfs image from a default build of the android source, which has the ro.secure property set to 0.
I first tried the boot.img that was generated by the default android build, but I had issues with getting wifi to work, so I tried merging the initramfs image with the RC29 boot.img, and it seems to work fine.
I suspect you could accomplish the same thing by extracting the initramfs image from the RC29 boot.img, un-gzipping and un-cpioing it, and then modifying the default.prop file to set ro.secure to 0. Then you would have to package it back up and stick it back into the RC29 boot.img.
ro.secure is the property that the adb service looks at to determine if it should use root user, or drop to the shell user. When ro.secure is 0, adb will run as root.
It can be a bit of a pain to get the android source to build though. Make sure you get the dream specific product files (they aren't downloaded by default when you do a "repo sync"). You'll also encounter issues where it can't find libaudio.so or librpc.so. You'll have to copy these from the phone to a couple of output folders in order for the build to proceed.
If you get stuck, feel free to give me a holler and I'll try and help out.
Be warned.. the build takes quite a while.. on the order of an hour or two at least. But then again, I was doing it in a VM.. it may be faster if you do it on a native linux box.

i cant get it to work i know I'm doing something wrong can you(everyone)help me out(i have Vista 64) i get this error
this i what i type​# C:\Android\AndroidMod>adb push recovery_testkeys.img /data/local/recovery.img​
this is the error​C:AndroidAndroidMod: not found​
please and thank you
EDIT: could we do it off the sdcard?
EDIT2: i think i found my own mistake this cant be done in Windows i need to have shell with adb meaning time to whip out VM

JesusFreke said:
For the boot image, I replaced the initramfs image in the boot.img included in the official RC29 update, with the initramfs image from a default build of the android source, which has the ro.secure property set to 0.
I first tried the boot.img that was generated by the default android build, but I had issues with getting wifi to work, so I tried merging the initramfs image with the RC29 boot.img, and it seems to work fine.
Click to expand...
Click to collapse
Can you talk more about this step of the process? How did you do this "merging"? Did you use mkbootimg?
JesusFreke said:
I suspect you could accomplish the same thing by extracting the initramfs image from the RC29 boot.img, un-gzipping and un-cpioing it, and then modifying the default.prop file to set ro.secure to 0. Then you would have to package it back up and stick it back into the RC29 boot.img.
Click to expand...
Click to collapse
And this could be done without going through the whole process of doing an Android build, right? I'm just thinking about how one might build a simple utility to allow editing of the ramdisk.

alansj said:
Can you talk more about this step of the process? How did you do this "merging"? Did you use mkbootimg?
Click to expand...
Click to collapse
I just used the good ol hex-editor. The gzip file starts with a few specific bytes (don't remember them offhand..), so you can search through the image. There are 2 gzip files, the initramfs is the last one. In mine, it starts at offset 0x00154000.
Once you find it, just cut it out and dump the new one in (there is some 00 padding after the gzip file ends.. not sure if you need to keep the padding or not). You also have to update the size of the initramfs, which is at offset 0x00000010.
alansj said:
And this could be done without going through the whole process of doing an Android build, right? I'm just thinking about how one might build a simple utility to allow editing of the ramdisk.
Click to expand...
Click to collapse
Yes.

Anyway to make this using the update.zip sd card method?

JesusFreke, per some requests in #android on freenode I have setup a wiki (not a device wiki like xda's but more like an "information about android/g1 and how to tweak it" wiki) and would like to put this on there. Let me know if you care (unless you would like to add it in your own words), the wiki is http://android-dls.com/wiki and its still very new, but im trying to to get it built up (RyeBrye is doing most of the work).

humble said:
i cant get it to work i know I'm doing something wrong can you(everyone)help me out(i have Vista 64) i get this error
this i what i type​# C:\Android\AndroidMod>adb push recovery_testkeys.img /data/local/recovery.img​
this is the error​C:AndroidAndroidMod: not found​
please and thank you
EDIT: could we do it off the sdcard?
Click to expand...
Click to collapse
First of, you do know that when we refer to "C:\..." we refer to windows via a command prompt (or "cmd") and when you see "# ..." we refer to a shell connection to the Android phone.
Second, you do have the Android SDK right? If not download it HERE. Now extract that to a folder, preferably close to the C: root. (ex. C:\AndroidSDK)
1)Either extract/copy the files from the "AndroidMod.zip" to the Android Tools folder from the SDK (ex. C:\AndroidSDK\Tools) OR copy "adb.exe" and "AdbWinApi.dll" from the Android Tools folder from the SDK (ex. C:\AndroidSDK\Tools)to the folder where you have extracted the "AndroidMod.zip" to.
2)Open up a command prompt. Start -> Run (or Windows key + R) and type "cmd"
3)CD to the directory where the files are.
EXAMPLE:
C:\Users\[your_user_name_here]> cd \
C:> cd androidsdk\tools
C:\AndroidSDK\Tools>
4) Now follow the Instructions.

[Root for the HTC Magic/Sapphire] (from haykuro) (updated 5/23)

I was reading the threads in the dream forum and found his progress and instructions. I added them to my wiki so they can be continually edited and updated as new methods are found. I did not have any part in this but I noticed that there was not a formal post here about it yet so I decided to make one.
http://android-dls.com/wiki/index.php?title=Magic_Rooting
Please feel free to thank him with some nesquik if you find this helpful!
I was pasting the new instructions here every time they changed but they seem to change often. Please visit the above url to see the current instructions. They were placed on the the wiki so anyone could make edits and changes to them, which is useless if this post needs to be updated each time. I wish vbulletin had some sort of wiki quote that could auto read that page and insert it here for me

Great!
If would be great if this post were a sticky. It also would be nice it the post was updated to include the instructions here as well.
Thanks,
Anders

Just quoting the solution here..
First of all, everyone owes Haykuro a great big thanks for working on this and helping create the solution without even owning a magic. The following is his method just reworded slightly.
1. To gain root access on your HTC Magic/Sapphire you will need to download the magic-root-boot.img zip file and unzip it so that you have boot-new.img in a location you can find.
2. On your device, enter the bootloader by trying one of the following
* Turn off your device and while it is off hold down home while you press power.
* Turn off your device and while it is off hold down volume down while pressing power
3. Make sure your usb cable is inserted and you have Fastboot installed and ready to use.
4. Type the following commands on your desktop (not on the device):
Code:
fastboot boot boot-new.img
5. wait for the following to flash and the phone to reboot:
Code:
downloading 'boot-new.img'... OKAY
Code:
booting... OKAY
6. make sure you have ADB installed and run the following commands from your desktop (not on the device):
Code:
adb push boot-new.img /sdcard/boot-new.img
Code:
adb shell flash_image boot /sdcard/boot-new.img

anyone tried this?

I was going to post the actual text here but the reason for doing it in the wiki is because the methods seem to change very often (the g1 method changed almost daily for a while). I would still recommend viewing the instructions on the wiki before performing the method to be sure they are the same at the time of use.

Full procedure so far!
1. Download boot-new.img.zip from http://www.droiddeveloper.com/hrbuilds/boot-new.img.zip
2. extract boot-new.img to computer.
3. Download recovery-new.img.zip from http://www.droiddeveloper.com/hrbuilds/recovery-new.img.zip
4. extract recovery-new.img to computer.
5. power off device
6. hold BACK+POWER (or VOLUME_DOWN+POWER) to boot into bootloader.
7.
Code:
[b]fastboot boot boot-new.img[/b]
wait for device to boot.
[b]adb push boot-new.img /sdcard/boot-new.img[/b]
[b]adb push recovery-new.img /sdcard/recovery-new.img[/b]
[b]adb shell flash_image boot /sdcard/boot-new.img[/b]
[b]adb shell flash_image recovery /sdcard/recovery-new.img[/b]
[b]adb shell reboot[/b]
you now have root build, and can flash whatever build you like (test keys and all)

First post and wiki updated to show these changes in more detail.

Hi,
I have a french Magic and I test this solution.
I have a problem, when I use the adb shell, I am "root", but when I use a terminal shell on the phone I'm not "root". I use "id" for my test.
How can I do ?
Thanks.
Edit : Ok I found the problem.
I make these commands after in adb shell:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd system
# cd bin
# cat sh > su
# chmod 4755 su
# sync
# reboot
Thanks

n00b here
can we flash ROMs for dream too or need to wait for magic ROMs ?

it's possible to backup the current firmware of my magic (with or without root), before flashing a new one?
thank you for rooting the magic
thank you for your help

ok i have a big problem when i put (fastboot boot boot-new.img) the phone is restarting every time in htc presentation :S

i put the phone in recovery mode ( fastboot usb ), but then i have the same problem, when i put fastboot boot boot-new.bin, the phone restart always with "boot.bin" , no with "boot-new.bin"...
i try to give the complete path, but always the same result

hello i have a problem.
if i write fastboot boot boot-new.img the console says: the comand "fastboot" is incorrect or bla bla ...
i have a german magic.

sr-ha said:
hello i have a problem.
if i write fastboot boot boot-new.img the console says: the comand "fastboot" is incorrect or bla bla ...
i have a german magic.
Click to expand...
Click to collapse
do you have installed de SDK ¿?

hmm no i dont
should i install it the android sdk 1.5 windows ??
i hve downloadet it but i cant find a icon or sth. to install the sdk

nicola_it said:
it's possible to backup the current firmware of my magic (with or without root), before flashing a new one?
thank you for rooting the magic
thank you for your help
Click to expand...
Click to collapse
nandroid backup 2.1, avaible in recovery mode, doesn't works

sr-ha said:
hmm no i dont
should i install it the android sdk 1.5 windows ??
i hve downloadet it but i cant find a icon or sth. to install the sdk
Click to expand...
Click to collapse
unrar de SDK, and in the "tools" directory you have the ADB and FASTBOOT aplications ( use in the console mode )

Works perfectly with XP, not with vista or win7

sorry but i dont understand what schould i do.
with use in thee console
i think i have to install fastboot or open it. but i cant do nothing of both. if i click on the fastboot exe it blobs open and fast close again.

under windows xp all ok
under windows vista no!!!

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

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!

[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.

Returning to stock, where can I find the stock image?

I need to warranty a phone but I need to turn it back to stock. I am using an older version of TWRP, I am guessing here but do I just download the factory image and flash it and I am done? It seems like everything I get when searching is geared towards the Pixel XL and using ADB rather than TWRP.
Thanks in advance.

Beacuse I part time as an internet troll, I have to chastise you for not reading threw this forum, because well that's why it's there, but hey we all can't use our Brian's all the time, but yes download the factory image for your phone Marlin for Pixel XL and Sailfish for Pixel unzip the file, make sure you have lastest usb drivers installed and click the flash all.bat.

Fastboot and flash factory image.
A wonderful guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886

jerryhou85 said:
Fastboot and flash factory image.
A wonderful guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Click to expand...
Click to collapse
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?

twilk73 said:
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
Click to expand...
Click to collapse
I'm not a good developer so I cannot answer you that question, but on Google official page, it is recommended to use fastboot or adb to flash factory images...

twilk73 said:
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
Click to expand...
Click to collapse
Because recovery and boot are sort of intermingled now. You would be writing over twrp at the same time you are trying to use it to flash.
Use the flashall bat file. If you want to save data edit out the -w from the bat file.

twilk73 said:
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
Click to expand...
Click to collapse
I am on linux let me just get that out of the way.
So I used adb to fastboot the factory image but nothing happens
the file is in downloads and in the fastboot file. So I type cd Downloads, cd fastboot, fastboot sailfish-nmf260 it all looks good and you can tell adm is working but nothing happens on the phone.
I am current only able to get the phone into fastboot mode I dont know what I messed up but I can no longer even boot into TWRP.

I must have succesfully removed the twrp recovery because no i get the no command screen. If I hold power and press up I can get into the stock android recovery. Is there a way to install the factory image still? Or is the process still the same and I need to adb fastboot? I might need to just do the abd fastboot on a windows computer at work tomorrow.

twilk73 said:
I must have succesfully removed the twrp recovery because no i get the no command screen. If I hold power and press up I can get into the stock android recovery. Is there a way to install the factory image still? Or is the process still the same and I need to adb fastboot? I might need to just do the abd fastboot on a windows computer at work tomorrow.
Click to expand...
Click to collapse
Download the factory image you want here. Unzip the entire contents to the same folder fastboot is located in. Then boot the phone to the bootloader, then plug it in to you computer. Then, if you're using Linux, double click the flash-all.sh file that got unzipped to your fastboot folder. If you're using a Windows computer, double click on the flash-all. bat file instead of the flash-all.sh file. Then sit back and wait. That's about all there is to it. One note. If you want to save your data, open the script you're going to use in a text editor and remove the -w toward the end of the script (remember to save your changes). If you want the phone wiped clean and like new again, just leave it as is.

robocuff said:
Download the factory image you want here. Unzip the entire contents to the same folder fastboot is located in. Then boot the phone to the bootloader, then plug it in to you computer. Then, if you're using Linux, double click the flash-all.sh file that got unzipped to your fastboot folder. If you're using a Windows computer, double click on the flash-all. bat file instead of the flash-all.sh file. Then sit back and wait. That's about all there is to it. One note. If you want to save your data, open the script you're going to use in a text editor and remove the -w toward the end of the script (remember to save your changes). If you want the phone wiped clean and like new again, just leave it as is.
Click to expand...
Click to collapse
ive done these steps but its failing to work. This is exactly what I am doing.
1. Download factory image.
2. Extract factory image into fastboot file.
the fast boot file is in the dowloads folder so I type.
cd Downloads
cd fastboot
fastboot flash-all.sh
iv also tried fastboot the sailfish-nmf260.img and boot.img and flashall. Ive tried several different ways this is what happens no mater what I type.
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
Click to expand...
Click to collapse
On the phone nothing happens. It appears that all I am getting is a list of options but none of the options seem to be working either.
I might add that the fastboot folder I am using was downloaded back when I installed twrp is it possible my fastboot file doesnt have the correct files to get the job done?

twilk73 said:
ive done these steps but its failing to work. This is exactly what I am doing.
1. Download factory image.
2. Extract factory image into fastboot file.
the fast boot file is in the dowloads folder so I type.
cd Downloads
cd fastboot
fastboot flash-all.sh
iv also tried fastboot the sailfish-nmf260.img and boot.img and flashall. Ive tried several different ways this is what happens no mater what I type.
On the phone nothing happens. It appears that all I am getting is a list of options but none of the options seem to be working either.
I might add that the fastboot folder I am using was downloaded back when I installed twrp is it possible my fastboot file doesnt have the correct files to get the job done?
Click to expand...
Click to collapse
Have you tried putting phone in fastboot mode and doubble click the flash all.sh file? That's how it is done on Windows.
Sent from my Google Pixel using XDA Labs

Sgace said:
Have you tried putting phone in fastboot mode and doubble click the flash all.sh file? That's how it is done on Windows.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Basically yes. But with linux you cant just double click. So in terminal I typed "cd Download, cd fastboot, fastboot flash-all.sh" that command will attempt to launch that file.
I feel like the issue is with adb on my laptop I tried making sure its updated but i got nothing so ill try to do it on a work computer when I get free time.
Its pretty crappy right now because I am without a phone but heck I pet the dog today during lunch instead of reading the news feed off my phone so I guess the dog is happy lol.

twilk73 said:
Basically yes. But with linux you cant just double click. So in terminal I typed "cd Download, cd fastboot, fastboot flash-all.sh" that command will attempt to launch that file.
I feel like the issue is with adb on my laptop I tried making sure its updated but i got nothing so ill try to do it on a work computer when I get free time.
Its pretty crappy right now because I am without a phone but heck I pet the dog today during lunch instead of reading the news feed off my phone so I guess the dog is happy lol.
Click to expand...
Click to collapse
I don't think you can flash it with fastboot. In Windows, at the command prompt, you just type flash-all.bat and the batch file will run. It contains all the necessary fastboot commands. Perhaps that's where you're going wrong. Try just typing flash-all.sh. Leave the fastboot out.

twilk73 said:
Basically yes. But with linux you cant just double click. So in terminal I typed "cd Download, cd fastboot, fastboot flash-all.sh" that command will attempt to launch that file.
I feel like the issue is with adb on my laptop I tried making sure its updated but i got nothing so ill try to do it on a work computer when I get free time.
Its pretty crappy right now because I am without a phone but heck I pet the dog today during lunch instead of reading the news feed off my phone so I guess the dog is happy lol.
Click to expand...
Click to collapse
Try this for sailfish (fix accordingly if marlin, username of course is common sense, if still confused, you shouldn't be using linux)
I build and use debian sid
Code:
cd /home/username/Downloads
tar xvf sailfish-opr3.170623.008-factory-bb8bb3a3.zip -C /home/username
cd /home/username/sailfish-opr3.170623.008
tar xvf image-sailfish-opr3.170623.008.zip
cd /home/username/sailfish-opr3.170623.008
./flash-all.sh
If you need the latest adb/fastboot name it something like google.sh
Code:
#!/bin/bash
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
cp platform-tools/adb /usr/bin/adb
cp platform-tools/fastboot /usr/bin/fastboot

piperx said:
Try this for sailfish (fix accordingly if marlin, username of course is common sense, if still confused, you shouldn't be using linux)
I build and use debian sid
Code:
cd /home/username/Downloads
tar xvf sailfish-opr3.170623.008-factory-bb8bb3a3.zip -C /home/username
cd /home/username/sailfish-opr3.170623.008
tar xvf image-sailfish-opr3.170623.008.zip
cd /home/username/sailfish-opr3.170623.008
./flash-all.sh
If you need the latest adb/fastboot name it something like google.sh
Code:
#!/bin/bash
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
cp platform-tools/adb /usr/bin/adb
cp platform-tools/fastboot /usr/bin/fastboot
Click to expand...
Click to collapse
Sorry I wish I could try this. I had access to a windows computer at work and I was able to get everything done. After doing it at work I have a feeling I wasnt placing the files in the correct folder together to get it to start the update. It can be hard doing this on something other than windows for a dummy like me because most of the tutorials for things like this seem to be windows oriented. Regardless its done. I couldnt lock the boot loader on the windows computer though oddly but no big deal because I can do it on my laptop.
Thanks for all the help guys.