[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!

---

Credits:
birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch.!
Thanks to SDX

Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into kernel /sbin, etc).

Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!

Current Device Support:
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: Samsung Google Galaxy Nexus (GSM & CDMA), HTC One S, EVO 4G LTE, EVO 3D CDMA and GSM, Amaze, Vivid/Holiday, EVO 4G, EVO Shift, Nexus 7, Nexus S/Nexus S 4G & LG Optimus
Check application version for updates

Custom Recovery
Supports both CWM and TWRP!

Future Support:
Will continue to test kernels as they are released to ensure compatibility!

Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:\downloads\FlashImageGUI.apk

Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI

Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!

FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No. Use Kernel Manager!

Screenshots:






Feedback:
Please post any helpful feedback. I'm always looking to improve the application!

Basic Troubleshooting:
Troubleshooting after Rebooting:

First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.

Issue #1: If the device hangs or reboots while on the splash screen, the kernel (or packaged ramdisk in the kernel) is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.

Thanks , this is a sweet app.

So I take it this is confirmed on Sprint. I use recovery image to flash the updated cwm touch image correct.

I am currently on JB Nightly.

Sorry just got the phone yesterday and reading the ins and outs of it. Got it rooted and set up almost to my normal operational preference.

Thanks Joey and SDX!

Good app to add to my tool box!

Originally Posted by latinmaxima

So I take it this is confirmed on Sprint. I use recovery image to flash the updated cwm touch image correct.

I am currently on JB Nightly.

Sorry just got the phone yesterday and reading the ins and outs of it. Got it rooted and set up almost to my normal operational preference.

Thanks Joey and SDX!

Yup, works on the Sprint version. Tried to articulate this in the OP by saying CDMA version of the Galaxy Nexus in order to cover both Sprint and Verizon.

Let me know if you have any other questions, feedback or ideas. Appreciate the support!

Does this give access to change the boot screen (Google and unlock icon)?

I see it appears to for other phones it looks like.

Originally Posted by latinmaxima

Does this give access to change the boot screen (Google and unlock icon)?

I see it appears to for other phones it looks like.

Great question. Unfortunately, I haven't seen any way to access the memory location where the boot screen is stored. If you see any threads/posts on here which describe a process, feel free to post them up here as a feature suggestion and I'll definitely research!

Thanks for the support!

Originally Posted by joeykrim

Great question. Unfortunately, I haven't seen any way to access the memory location where the boot screen is stored. If you see any threads/posts on here which describe a process, feel free to post them up here as a feature suggestion and I'll definitely research!

Thanks for the support!

I believe the two images (the Google logo and the unlock icon) on the boot screen are located in the sbl partition of the GNex. Have a look at this thread, particularly post 221.

I really would LOVE it if I could finally get rid of this ugly Google logo.

Sent from my Galaxy Nexus using Tapatalk 2

Originally Posted by efrant

I believe the two images (the Google logo and the unlock icon) on the boot screen are located in the sbl partition of the GNex. Have a look at this thread, particularly post 221.

Wow. Great thread. Appreciate the link and specifically your research and helping hand in keeping all that work going/organized.
Post 221 definitely seems to indicate there are JFIF tags (jpeg) images inside the sbl partition. That is a great start, but a lot of work remains.

Would need to analyze and answer some questions such as, if those really are the correct images being displayed on boot. How large are those images, what are the file size limits, how best to move new images into the sbl partition, what offsets to start/end at, and can the sbl be flashed from standard Android mode?

I think if all those questions were answered I would be able to judge how risky the process is and determine how much coding it'd require for me to include in my app, specific support for this device.

Unfortunately, I have too many demands on my time as it is and those questions will have to sit on the back burner for me until I have more time to research/answer. If anybody else has a chance to answer/pursue them or post up research, I'd def be interested. Seems like a project with a lot of potential!