yashsingh1/xdaforums huggingface dataset:
[HTC One S] eckbauer:
Just got the Play Store update.Thanks:)

A Rock Solid App.:good:
[HTC One S] Rapier:
Latest version 1.50 identify the device correctly. Thanks

Sent from nowhere over the air...
[HTC One S] htheod:
Does this app work on Samsung Galaxy S i9000?
[HTC One S] KeemGoodFella:
thanks for this
[HTC One S] drzamp:
Thanks..i'm happy to buy an app which i use almost every day :D:p ...
[HTC One S] joeykrim:
Perfect. Thanks for the positive confirmations around the bug fix!

No, because I haven't had a knowledgeable tester to work with. If you are familiar with ADB, using a custom recovery and have a few hours to test or know somebody with the device who fits these criteria, please send me a PM. Thanks!

Appreciate the positive support! On a slight side note of reflection, I think this device has the most highly concentrated set of users providing positive, quick and helpful feedback of all the devices supported by Flash Image GUI.
[HTC One S] dhigby:
Internal Memory Unlock Confirmation

I was perplexed when I installed the app and started it, and it asked if I had the internal memory unlocked. I didn't know if this was something else that I needed to do. But after looking around, I am guessing that this is referring to what HTC calls unlocking the bootloader.

If this is the case, then it would be nice if the wording on the warning referred to an unlocked bootloader rather than memory. If it is not the case, and there is something else I need to do before using this, then please let me know.

BTW, I have spent hours trying to help a far away friend get his computer set up with the correct drivers, etc to flash a boot.img file and we never suceeded because of Windows driver issues I wasn't able to resolve from a distance. Thank you for this solution!
[HTC One S] Rapier:
Yes, the question is about unlocked bootloader, you don't need to do something else. For me it works like this. Also, the question is asked only at the first application start. If you use it second time, it won't ask again for this.

About the wording...well this only the dev can change it if he considers appropiate

Sent from nowhere over the air...
[HTC One S] joeykrim:
Thanks for the feedback. The exact text of the dialog reads, "HTC locks the internal memory (NAND/EMMC) which prevents the flashing of custom kernels and recoveries. Completing the HTC Unlock method or a 3rd party method will unlock the internal memory. Please confirm you have unlocked the internal memory before continuing?"

I thought explicitly referencing the "HTC Unlock method" would be sufficient for most, but perhaps I also need to add in the phrase bootloader since that seems to be commonly used.

What do you think of this: "HTC locks the internal memory (NAND/EMMC) which prevents the flashing of custom kernels and recoveries. Completing the official unlock method from HTC, commonly referred to as unlocking the bootloader, or completing a 3rd party method should unlock the internal memory. Please confirm you have unlocked the internal memory before continuing?"
[HTC One S] Rapier:
This will be much better, especially considering that even if it's a dev section, not all people who read here are technical or know all the technical terms specific to Android/phones...they just want to flash a ROM or solve their problems.

Sent from nowhere over the air...
[HTC One S] dhigby:
Thank you, this takes away the confusion. But for economy of words, I'd think the following would suffice:

Please confirm your bootloader has been unlocked.

In any case, both will work. Thanks for considering this!

Sent from my HTC One S
[HTC One S] joeykrim:
I'm all about concision but the difficulty I face is not wanting to write a custom message for each HTC device. Some 3rd party "hack" messages do not specifically unlock at the bootloader level, but unlock at a lower radio level which is reflected/displayed by the bootloader.

Once again, this is probably too technical, as the original feedback suggested, but I'd prefer to be accurate and use the correct/best terminology in the hope users can be educated through proper discussion.

Perhaps in an effort to be concise, as previously suggested, the following will suffice: "HTC locks write access to the internal memory which prevents the flashing of custom kernels and recoveries. Please confirm the internal memory has been unlocked by completing the official unlock method from HTC, referred to as unlocking the bootloader, or completing a similar 3rd party method?"

The reason I have this dialog was to prevent temporary root users from being confused when the application didn't work. Temporary root methods are becoming less common and thus this dialog is also becoming less needed. Perhaps at some point I can remove it, but I think for a once per install prompt, there are probably other areas of the application I can spend time improving rather than this dialog.

Thanks for the feedback and support!
[HTC One S] Darknites:
Ya I would go with the new wording and make it only first run pop up.
[HTC One S] dave il barbaro:
two days ago app works great... but now when i tap over the icon, the app won't start... i uninstalled it, clear cache and installed again, but nothing...the app won't start.

i have the latest version 1.51 and i am on Dark Jelly S 9.1 ROM

EDIT: solved: Disable force rendering gpu under developer option
[HTC One S] Chris Boyer:
I have used with great success on just about every JB sense ROM, however I get recoverable boot loop trying to flash a number of ICS roms. Any thoughts?
[HTC One S] joeykrim:
Boot loop generally means Flash Image GUI was successful is loading the kernel but the kernel is either not compatible with the device or the kernel is not compatible with the ROM.

Can you be more specific by providing the exact link to which ICS rom files that resulted in a boot loop?

Also, as a side note, there are generally two types of boot loops, the boot loop at the animation, where the animation keeps repeating and the boot loop at the static 1st logo screen. Specifying which one of these occurred also provides another helpful level of detail.
[HTC One S] blaze82:
my # 1 app

yup... im a flashaholic, always testing new ROMs / updates

and this has come in very handy, thank you
[HTC One S] WhiTeRhiNo:
One of my favorite apps. Saved me a bunch of time and headaches
[HTC One S] eckbauer:
Paid Version

I'm using the paid version now since day one with no problems at all.

It works great,although i can s-off my phone i see no need to do so with this app.:)
[HTC One S] DisruptiveMind:
I feel exactly the same, no point having S-Off with this program as the 'benefits' are not all that impressive and well I don't care about resizing partitions if they ever figure it out because I'm happy with how its set now. Long live the FIGUI! (My new word of the day, scream it loud and proud!) :D
[HTC One S] eckbauer:
Well said.:D
[HTC One S] Darknites:
All I'm going to say to that is Boot Splash Screen lol.
[HTC One S] joeykrim:
I'm definitely interested in adding support for this but am skeptical HTC allowed write access to this memory location while booted in Android.

Regarding the boot splash screen, is there any known method of loading/flashing this while booted in Android?

Can somebody confirm the known methods used to flash the boot splash screen so far?

1) Through fastboot?

2) Through a .zip file picked up by the bootloader?

Thanks!
[HTC One S] Darknites:
I was saying that for a reason to S-Off and can't be done without it or the lower Hboot and its a zip you can use here but can be dd in.
[HTC One S] joeykrim:
The link is extremely helpful. For those who meet the unlocking requirements, I might be able to add splash screen flashing support to FIG.

Will need two things:

1) knowledgeable tester with time

2) demand for the feature
[HTC One S] Darknites:
If I wasn't busy I would but think its not really needed maybe if it could get round the Hboot issue then ya it would be sweet but other then that it not hard to flash a zip after all they did S-Off so should be able to flash it lol.
[HTC One S] jentzschman2000:
AMAZING

Thank you so much for this! It completely fixed my booting issue.

Now I no longer need to fastboot boot boo.img if I need to reboot or power down!

I will buy this app as well now!

Thank you again!
[HTC One S] addsfsds:
I bought it too, saved me so much time :D Thanks!
[HTC One S] kennethrkennedy:
awesome tool

Thanks for this awesome app. It saved me big time when I had to revert twrp back to am older version.
[HTC One S] b_ignatov:
When will be available for HBOOT 2.15>>
[HTC One S] Darknites:
It should work for that Hboot.
[HTC One S] b_ignatov:
I'm asking because in the first post is written "Confirmed Compatible Hboot Versions:

1.06, 1.09, 1.13, 1.14 (US and EU)"

Never mind...I'm gonna try it ahd confirm it.
[HTC One S] Darknites:
Ya that's because it wasn't out at the time the app come out.
[HTC One S] DisruptiveMind:
I'll confirm it works on 2.15. That's my good deed for the decade.
[HTC One S] joeykrim:
Thanks!! Updated the OP to show compatible with hboot 2.15 and linked back to the post from DisruptiveMind
[HTC One S] Sneakyghost:
AW: [APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!

Joeykrim if you really need the splash flash in your app and want that feature tested I can maybe spare some time as I'm currently not testing much for anyone.

Just let me know and pls also what way you want to do fast communication (gTalk?).

Sent from Viper 2.2
[HTC One S] el_smurfo:
Great app, but question

When I first tried this app with older hboot 1.06 (just for fun) and an extracted boot.img, I got a system that wouldn't boot. Now that I have hboot 2.15, I really need this app and allowing it to extract the boot.img itself and flash it seemed to work great.

Now my question. During the flash kernel process, it seemed to be extracting several other unrelated files and copying them to system directories. What are these files...seemed like maybe .ko files? Drivers? What is the purpose of this if you are just going to flash a ROM over the top of these files immediately following and is there a way to just extract and flash the boot.img alone through the app?
[HTC One S] joeykrim:
There are multiple questions in the post, I'll answer them in the order they're presented.

Yes, these .ko files are drivers and are mostly loaded into /system/lib/modules/.

The purpose is to ensure the required files for the kernel are loaded at the same time as the kernel. If only a kernel and kernel modules are flashed from Flash Image GUI, and the kernel is compatible with the currently loaded ROM, the flashing from recovery process can sometimes be skipped.

Hope that helps. Thanks for the support!
[HTC One S] gelo01:
Will this work even when i'm only S-On?
[HTC One S] el_smurfo:
Yup... that's the point.
[HTC One S] el_smurfo:
Hi Joey,

After using this for a month, it has really saved me a lot of hassle. I wonder if you are still developing the app, and if you are open to suggestions? After using Flashify a bit, it sure would be cool if a little bit more of the task of flashing a ROM was automated. The ideal sequence might go like this:

1. Select ROM zip

2. Choose whether TWRP backup is made or not.

3. FlashImageGUI extracts and flashes boot.img, then reboots to recovery and flashes ROM zip

I suspect you can get a lot of the code to automate this by looking at the CM updater stuff on github. There are a lot of apps that do the automatic recovery flash of zips, so I'm guessing these open recovery scripts are well documented?
[HTC One S] joeykrim:
Yes, I am still developing the app and I am open to suggestions.

Interesting, I hadn't heard of Flashify before, but seems to be a decent app, although device support appears to only be provided for the Nexus devices according to the Google Play description.

I've intentionally stayed away from duplicating features the custom recoveries performs, such as backups and restoring backups. Although, I'm not clear from your comment what action you'd expect FIG (Flash Image GUI) to take if a TWRP backup is not made? Have FIG create only a kernel backup or a full system backup? Or have FIG pass off the backup command to TWRP?

I do understand the convenience in passing off the same ROM .zip file for the custom recovery to flash after FIG has flashed the kernel portion. I know TWRP has "open recovery script" support with some decent detail: http://www.teamw.in/OpenRecoveryScript . Not sure if CWM would be easily to support or not.

The only downside is that I haven't received this request from many other members. If this seems to be a common feature that would help a lot of people, I can move it up the priority list.

Thanks for the suggestion and support!
[HTC One S] el_smurfo:
Hi Joey,

Thanks for being open to suggestion. When I said "backup", I was intending the backup to be performed by TWRP as well via script, but it was only really a "wish". The majority use of this for HTC devices is just flashing boot.img followed by reboot to recovery and ROM flash, so that's why I said it would make our lives easier if the ROM flash was automated via script.
[HTC One S] joeykrim:
Excellent. I've added this to my feature list.

Thanks for the feedback and let me know if you have any other suggestions or ideas!
[HTC One S] el_smurfo:
You know you should never ask a user on XDA for suggestions :o

1. Dump the splash (or give option in settings). Don't have any other apps that do this.

2. Allow for config of "default directory", rather than having us navigate to download directory each time. Even cooler would be a selection box on the main screen of each zip in the default directory for one click flashing.

3. Allow config of default operation, i.e. extract and flash boot.img, then automatically reboot to recovery (maybe easier than auto flash recovery script).

4. I know you're trying to cover yourself, but rather than the block of text at the top, since you can already detect the phone, just have a popup for unsupported devices. You can add the block of text to the settings/help/about page.

5. A slightly cleaner UI...perhaps just use the new roboto fonts from the 4.3 dump instead of the green outlined text. Other settings option checkboxes can also be moved to a settings screen, freeing the main screen for display of all ROMs in the default directory/mini file browser.

You did ask for it...:D I'll keep using no matter what, but it ain't the prettiest thing...
[HTC One S] joeykrim:
Lol. This is probably some of the best feedback I've had.

No claims for FIG being the prettiest app out there as it was designed two years ago for Froyo / Gingerbread and old Android devices, but I've kept updating the internal logic as new devices have come out since people have enjoyed using it.

I spent a good 12 hours going through the app cleaning up the UI and getting a consistent holo theme for new and older Android devices (Android 2.1+). Unfortunately, the compatibility libraries are a bit large and have doubled the size of the application, but alas, I think it looks much better.

1) Done. Default is now off but can be toggled on in the settings

2a) Done. Added an option to the preferences that allows the user to set the default browsing directory.

2b) Having a selection box doesn't necessarily save much effort as right now the process involves two presses. In between the two presses I prefer to first analyze the selected file and show the user the analysis before the file is flashed. I'm leaning towards the side of caution as I've even accidently selected the wrong file. Perhaps, I can add a toggle in the Preferences for one click flashing that'll immediately flash the selected file?

3) Interesting .. This would save one popup dialog but not sure I'm convinced it is worth it as the option will need to be made elsewhere, probably in the preferences.

4) Done.

5) I did get rid of the outlined text, that was from a previous generation of applications! Not completely sold on the mini file browser concept yet. Might need more details or a similar app that uses this concept to see how it looks/functions?

6) BONUS: I added an invert theme option for the holo theme as some people prefer dark over light!

I've uploaded the new version to Google Play, which takes a few hours to process before making public and I've updated the direct download link off my hosting in the OP.

Let me know if you have any other ideas, features or suggestions as well as more detail on any of the items I wasn't sure about. Thanks for the support!
[HTC One S] el_smurfo:
Wow...that's amazing. App looks a million times better and the black theme will make my midnight ROM flashes a little easier on the eyes.

I've never actually had someone listen to me here on XDA :confused:. Don't have a ROM update to flash, but I'll feedback as soon as I give it a whirl.
[HTC One S] Darknites:
Nice update, loving the black :laugh:.
[HTC One S] chris1ee:
One of the best apps ever used. Excellent job!
[HTC One S] haq.adnan:
Hello guys can i flash custom kernel using flash image guj on my evita s-on h-boot 1.14
[HTC One S] haq.adnan:
Is there anyone who can answer my question
[HTC One S] joeykrim:
If the device is unlocked through the HTCDev.com process, yes. If not, then no.

Hope that helps!
[HTC One S] el_smurfo:
Hi Joey,

I've been using the update for a while and it's a big improvement. You were awesome about implementing some of my previous suggestions, so I thought I would repeat one and add a few others.

In my normal use I flash the boot.img then either reboot to recovery and manually flash the ROM, or use the CM updater function to automate this (doesn't work after cache clear though, as system is too unstable). It would be awesome for usability in my case, and any others who need to flash boot.img outside of recovery if you could revisit:

1. After flashing boot.img, have an option to automatically flash the ROM they were extracted from via open recovery script. I would do this without user intervention, but a button on the popup or third button under Flash Image would be fine.

2. I might consider moving some more UI elements to a settings menu. I unselect the Clear Dalvik and Clear Cache each time (except when I forget), so making these permanent selection in the settings menu would be fine. Seems half done as they are to be duplicated in settings, but toggling off in settings then return to main, then back to settings and they're on again...should stick and be removed from main screen.

3. The popup after flashing could also be made optional...you could add "automatically reboot/reboot recovery" settings, in addition to #1 above (i.e. after flash, it either installs ROM via Open Script Recovery, it reboots, reboots recovery or does nothing.)

4. One more settings option...I have no need to flash kernel modules, since I'm going to reboot into recovery and flash ROM...I would bet the majority use case for the app is simple boot.img flashing due to unlock issues with some devices.

5. Minor UI wank...The line "Use Browse - Example" is a little weird...most folks know how to browse for a file, so maybe just "Browse SD card for image" would be clearer.

I personally would think making these premium features would make it worth a few hours of your time, and most would willingly pay to automate a bit more of the work.
[HTC One S] ferreinf:
Don´t want to spam, but really Thank you working fine on my One S :)
[HTC One S] asdfasdfvful:
Right.. I do believe that the wifi issue was a recent thing due to changes? The main issue I had was that one time I tested bubba on twistedkat and it got into a bootloop. Thankfully, I had a TWRP backup, but if having a zip just for a boot is possible, it sure would have saved me a lot of time and trouble!
[HTC One S] kred9k:
Not work on htc one S villec2

Wysłane z mojego HTC One S przy użyciu Tapatalka
[HTC One S] joeykrim:
Has Flash Image GUI ever worked on your device or is this your first time? Are you running a custom ROM or kernel?

Can you post up a screenshot of Flash Image GUI? In addition, I'm wondering if you're on a variant version of the One S?

Thanks for the feedback and more detail will definitely be helpful!
[HTC One S] el_smurfo:
Pretty sure C2 has a different processor, MSM8260 vs MSM8960 in the original Ville (which works great)

http://www.gsmarena.com/htc_one_s_c2-4836.php
[HTC One S] kred9k:
Stock rom jb

Wysłane z mojego HTC One S przy użyciu Tapatalka
[HTC One S] joeykrim:
Yes, it does make sense this is a variant. Thanks for the insight as it helps confirm my research.

I'll want to walk through the flashing process with a tester, who has the device, to ensure everything is working properly. I don't expect there to be any issues, but if anybody with the C2 is knowledgeable with the custom recovery and ADB, please send me a PM and I'll send them a version of Flash Image GUI for the C2 that we can test the features with.

Thanks for the support!
[HTC One S] oll0:
Works nicely, thanks! Thumbs up
[AT&T Samsung Galaxy Note I717] redeuxx:
Recently my phone has used so much data that for the first time I've reached over 5GB of data in the middle of the month. Data usage in system settings tells me "Android OS" and Onavo tells me it's "HTC Apps" that's using all the data. It doesn't tell me which specific service or app is using it. This has started happening since Slim Bean 2.7. Anyone have any ideas?

Much thanks!
[AT&T Samsung Galaxy Note I717] jelliottz:
Mine did the exact same thing this month except I'm on BlackStar. I downloaded and flashed a bunch of rooms though, redownloading apps if I forget to use TB, and videos eat up data.

I use T-Mobile so I switched to the truly unlimited data plan for $30. No more worries.

I would pull up your online statement and check your usage. It shows you when and how much data you're using. I'm guessing you have a rogue app. I would look at the HTC apps pulling data. Not sure how you have a HTC app on your Samsung phone.
[Desire Q&A, Help & Troubleshooting] Max128:
Hi, I have a big problem with my desire!

I lent several months my old desire a family member .. It has not been very careful and had no protective case he does not like it .. The phone was still working when I was handed.. However, the fully plastic housing was very scratched and small pines broken.

So i order a housing from ebay. I followed this video on youtube to disassemble the phone : http://www.youtube.com/watch?v=sXZqIjtFoAU&feature=relmfu

I assembled the phone later and I have a problem with the screen. I tried several times to reset the screen .. the screen is beautiful no scratched.

Here is my picture:

please help!!
[Desire Q&A, Help & Troubleshooting] Max128:
Help??
[Desire Q&A, Help & Troubleshooting] belliash:
The screen is broken, you need to replace it.
[Desire Q&A, Help & Troubleshooting] jmcclue:
Dunno but i would take it apart again and just make its all put back together properly, u never know, u coulda missed something or something not connected right.

Sent from my HTC Desire
[Desire Q&A, Help & Troubleshooting] Max128:
Hi,

I disassemble several times and everything seems normal. Except that the GPS connector is broken because its a very thin wire .. but I do not think it is connected!
[Desire Q&A, Help & Troubleshooting] belliash:
The glass do not have to be broken, but as i said before this looks like faulty lcd or the connector. However i would say it's fault lcd, 'cos connector would rather give you a light gray screen.

Looks like it gets 'bloated'...
[Desire Q&A, Help & Troubleshooting] Max128:
This is strange because the screen is in good condition and the connector too as everything is connected. So you think it is the lcd has a problem .. I disassemble again yesterday and no improvements. However, the volume buttons on the connector that is connected to a part of the motherboard's detached. Possible to fix?
[Desire Q&A, Help & Troubleshooting] belliash:
Screen doesn't need to be broken to be fault.

If it was me - i would say the screen is broken and i would replace it as it looks so. But i can't promise that's it, sorry.
[Desire Q&A, Help & Troubleshooting] Max128:
I'll wait in case , thanks for your time!