yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Antagonist42:
Not just that but more complexity would mean a decoder, screen drivers (possibly) memory space to decompress & read it from....probably more trouble than it's worth to go hi-tech just for (basically) a splash screen in general but definitely would be worth (in my eyes) having a GUI you could run it through and alter the bit fields (sad oldie stuck on windows and no time to really get into linux :what: ).

Bashing away at my HTC Desire C
[Android Software/Hacking General [Developers Only]] makers_mark:
True! :good:
[Android Software/Hacking General [Developers Only]] makers_mark:
The following images were all extracted using option 8 - Extract Jpgs From File

AT&T Note 3

Crespo i9020
[Android Software/Hacking General [Developers Only]] makers_mark:
Note 3

Samsung Tab 2 7.0 & 10.1
[Android Software/Hacking General [Developers Only]] makers_mark:
Note 2

Sprint Galaxy Nexus (toroplus)

Nexus 10 Manta Jpgs
[Android Software/Hacking General [Developers Only]] E:V:A:
@makers_mark : Hi, we found something called Qmage. Apparently all images in Samsung 4.4.4+ firmware are in this proprietary qmg format, so no more PNGs.

They mention RGB565 and we're wondering if this is the same stuff as you've been working with?

If so, perhaps your tool can be extended to deal with these?
[Android Software/Hacking General [Developers Only]] makers_mark:
Thanks, that is very interesting. I've looked at qmgs before, and can see a repetition pattern in them, but the compression was unintelligible. I will definitely take another look at them though!

[edit]

I've never seen rgb5658. That is something, I'll have to keep an eye out for. That extra byte means so much when you're looking for an image encoding, especially with rgb565, as it is hard as hell to interperet two plain bytes as pixel data when you look at a whole image. ARGB8888 provides you with a static barrier of 1's between pixels (usually, unless the image actually takes advantage of the alpha channel)

I'll get back with you, with this new found knowledge, thanks again!
[Android Software/Hacking General [Developers Only]] E:V:A:
Just for thread completion, alireza7991 also has some png2rle in his GitHub.
[Android Software/Hacking General [Developers Only]] makers_mark:
I am all for thread completion and internet history, and think that it is vital (among lots of other things) as to trying to stay advanced with technology and also with perceived avenues of future technology.

I have to say though, that I have seen the source, and the thread. It involves the same two programs I gave credit to in the OP, but is sans credit. That's okay with me, as long as everyone else is okay as well, but the important thing to note is that, it only involves the run length encoding of rgb565; two byte count, two byte color. And if that is all you are focused on, you may as well call it a file extension. But, my thread is more about the concept of run length encoding. It is not an extension to me and I've seen different variations that make it a compression method, and not your typical file type. Since I wrote the original post, I've actually seen some kernel source that uses the 4 byte method.Here is one example But I still haven't found any kernel code utilizing the 1 byte count 3 byte color that is used in the Nexus 5 bootloader.

I am trying to infer that what they use in the bootloader may potentially be used in kernels, somewhere down the road. I don't know and don't care, but I can't go wrong in documenting and making a conversion tool, just in case.

I know you are not talking directly to me, but I am on the same page as you, and believe that all things should be documented. And I think that your drive is the same as mine.:good:
[Android Software/Hacking General [Developers Only]] makers_mark:
Last week they came out with the HTC Nexus 9. I was awkwardly eager to see the bootloader, to see how it was structured and what not. Google released the factory images, with `bootloader-flounder-3.43.0.0114.img` included. At first I didn't see anything that looked like images, but I did see a lot of `PK` headers. Which is "almost" always a zip file. I changed the `.img` extension to `.zip` and it worked.

So in true HTC fashion, they have allowed access to the partition which is the splash screen, given you're bootloader is not locked. The second file down is sp1.nb0, which is a non rle image in rgb565 pixel format. It resides in mmcblk0p9 on the device, and the image only takes up ~2/5 ths of the partition. I don't think the extra space is of any significant value, just a 1024*1024*1024.... space thing.

I haven't had a lot of time to see what other images are in the different files, but I did find some run length encoded images; like the 3 android skateboarders, and the htc logo with the reflection.

Now that I have a n9, it took me mere decaminutes to change the splash screen. It is as simple as `fastboot flash spash1 raw.rgb565.file.name.on.your.computer` I must say thank you XDA, I've never owned an HTC device, but reading through all the threads regarding HTC splash screens; in between the time I got the bootloader until the time I got home to the new device (I was out of town). It made my work easier. If anyone has a HTC Nexus 9 and would like to change it, here is my thread.

[MENTION=4372730]E:V:A[/MENTION]

I haven't had time to test some of the QMG source, yet.. I did however learn that they are pretty complex, two stages of decompression with a dozen algorithms. I found some source for a program named `wave remaker` right here on XDA and a couple of threads that are very interesting. Most of the interesting stuff came from two different people and neither one of them use the forums anymore, or if they do, they use a different account. But one of them did briefly post that qmgs right now are different than they use to be. And I have no idea how they got the source that they used, it was probably some sort of corporate liscense or something of that nature. I will start testing whether that statement is true or not in a couple of months.
[Android Software/Hacking General [Developers Only]] E:V:A:
Interesting, that is actually a Qualcomm Tegra (?) binary blob, that could be part of the boot loader itself, or the modem firmware, depending on what your partition table says about P9 content. Those type of files are flashed by emmc loader... Do have a look in my threads related to Qualcomm...

EDIT: Nope, I may be wrong, that file seem to be the (Bootloader) Splash Screen, so yes, it's probably an image. I'm just wondering why it need to be 6MB?

Also, please link to those other threads, relating to QMG. I bet they got the code from either the Code Aurora or the Android Sources repo's.
[Android Software/Hacking General [Developers Only]] makers_mark:
The rest of the images are behind this button:
[Android Software/Hacking General [Developers Only]] Iceman_jkh:
Hi Makers_Mark.

I've tried to follow along with your commentary here so that I could mod my N7-2013 Deb boot screen. (It uses the bootloader-deb-flo-04.04.img)

Firstly, even though I haven't been able to follow it to conduct the mod, thanks for the informative write up - I managed to get the gist of it :)

My Nexus 7-2013 is mounted in the dash of my car, in a reverse landscape orientation.

All I'd like to change for the splash screen is to remove the Google text (just replace it with black) and to turn the padlock 90 degrees (so it's upright when the tablet is in reverse landscape). Fairly simple (I think).

Is there any chance you can do a very quick write up for me on this so I can do the mod?

I just haven't managed to connect the dots between your commentary and what I'm trying to do.

Thanks in advance :)
[Android Software/Hacking General [Developers Only]] osm0sis:
Since the Nexus 2013 is now EOL for OTA updates, here are the highlights I just found for our final bootloader:

bootloader-flo-flo-04.08.img

4 byte pp

bgr0

(offsets are in decimal)

logo:

search string 9C030000 00000000 01000000 09090900

size 518x179

length 43768

offset 1187772 (311688 in aboot)

offset 3270044 (2393960 in aboot)

offset 3955364 (3079280 in aboot)

offset - (3167460 in aboot

only

)

lock:

search string 1C000000 00000000 01000000 24242400

size 72x94

length 4616

offset 1127848 (251764 in aboot)

offset 1267360 (391276 in aboot)

offset 3102124 (2226040 in aboot)

Worth restating that the corresponding partition on-device containing the images, mmcblk0p12 (as mentioned several times by [MENTION=5448769]makers_mark[/MENTION]), is named aboot. When the device is locked, abootb (mmcblk0p19) is a byte-for-byte copy of aboot with the exception of the bootloader's lockstate storage area located near 5242368 with another "ANDROID-BOOT!". When unlocked this is also the case, and the only further change is at the lockstate offset in aboot.

Also.. *cough*

Now.. to generate a replacement image and see about hacking it in... ;)
[Android Software/Hacking General [Developers Only]] makers_mark:
I will make a lock image that has a long white line ,corresponding to their oblivious pixel, and replace it in all three spots. It will contain no more and no less data (no padding in testing scenarios). If you want to "dd" it to the partition or use otherwise "cough" mentions, then feel free. Very nice find there. I used a popular internet archive to get the source (thread) that I was referring to. The cough seems about the same caliber as far as knowledge and insight.

Let me know if you want me to make a 4.08 bootloader for you. I will not go off of your offsets, I will re-verify all that and quintuple check everything. You can do the same as well if you want to be extra sure. If that was the case we would have bianrily exact files. When I wrote this thread, the N7 was the only (and first) android that I owned. Hence it was not sacrificial to me, but an enjoyment that I couldn't just test like that. It is dead now (probably just the battery) and getting ready to set sail on an equitable distribution-end of life garbage cycle, or straight to the data recovery center for cheating wives who want to find any dirt they can to make themselves look better :laugh:

:)
[Android Software/Hacking General [Developers Only]] osm0sis:
Hmm, I'll have to check out the popular internet archives since perhaps the pictures, etc. would still be intact in their coughs.. :highfive:

I tried hacking the bootloader.img already and fastboot throws a "signature failed!" error, so it seems aboot is the only way to go.

I decided to get crazy with it so I already tried replacing the lock image with the new version in all 3 places in aboot and flashing it and it hard bricked my device. But not so hard that I couldn't recover it myself with some more poking around. ;)

So it seems your original assessment may have been correct, or perhaps I was just a bit cavalier since the new lock image was shorter in data length than the old and required some minor 00 padding. Since I can reliably recover my device (tried it again by fully zeroing aboot), I'm definitely up for some more testing, and agree that a more methodic/scientific approach where the data is the same length (perhaps just changing a single pixel or something to start with) would probably be the best approach. :laugh::cowboy:
[Android Software/Hacking General [Developers Only]] makers_mark:
You have done your research on the bootloader in question, and maximized efficiency in a recovery of a failed attempt. Good job!

One of the good things about RLE (pertaining to this particular scenario) is that you don't have to alter just one pixel to make the image size the same. That is actually really difficult based on the image. I was simply putting out there the random white dot at the bottom right of the lock as a "shove it" move, whereas the ideal way would be to move some pixels that do not go from a white/grey to another white/grey (or black/grey vice versa). The solution was obvious (after the fact):

. It is the exact same size and doesn't have to mess with any of the grey areas, and should not be hard to recognize if it takes and boots. I just made a black line white by changing 000 at byte 2884 (in the cut out image, not the complete bootloader) to ÿÿÿ. Here is the data for it.
[Android Software/Hacking General [Developers Only]] osm0sis:
No luck. Tried it in all 3 locations, tried it in only last 2 and last 1 just to see, and still nothing. Then returned to untouched manually by changing the bytes back and flashing that, and that unbricked with no issue (just to rule out something weird with the editing/flashing process).

I guess our only hope would be to figure out where/how the signature is stored and update it (probably trustzone/tz?), but the same could be said for a whole bootloader.img and that might be a safer prospect mediated by fastboot. And of course figuring out the signing procedure/key might be next to impossible. No new logo for us. :(;)
[Android Software/Hacking General [Developers Only]] Nevaloud:
What about rotating the image 90 degrees.

Is That mostly likely locked away also.
[Android Software/Hacking General [Developers Only]] L.F.B.:
Thats a bummer.... I thought it was easy to chaange splash screen like on nexus 5...

Ii just wanted the new Google logo updated on splash screen...
[Android Software/Hacking General [Developers Only]] BIade:
Anyone here can create a imgdata ultility for the huawei watch (1st gen) ?

I tried, but im way too noob :(

bootloader.img
[Android Q&A, Help & Troubleshooting] liquidreamz06:
Plan to support phone...

everyone is welcome...
[Nexus 7 (2013) Accessories] Samantha022:
Hi! I need your opinion so I can decide if I should buy this keyboard for my Nexus 7. Two months ago I purchased a Bluetooth keyboard for my Nexus 7 but it stopped working last week and I felt bad. Bought it for $80 and it only lasted for two months. I am not rich, and if I was I think I would still feel bad for buying expensive accessories that won't last longer.

Now, I wanted to buy a new Bluetooth keyboard and I found one from amazon. Users reviews aren't topnotch but I think it is a great keyboard as I also found another review for it from a popular website. I don't want to buy another expensive keyboard for my Nexus 7 and would end up feeling frustrated and I think buying this one which is on sale would be a good choice though I haven't made up my mind yet. I think I can if I would hear your opinion guys. Thanks!
[Nexus 7 (2013) Accessories] Samantha022:
Here is the link to the keyboard by the way.
[Nexus 7 (2013) Accessories] andijoe:
You can try this produc h*ttp://ww*w.amazon.com/Minisuit-Bluetooth-Keyboard-Nexus-Rubberized/dp/B009WSCW4S
[T-Mobile Samsung Galaxy Note 3] sunnyboymark:
I'm on a Stock Rooted with Custom Recovery. how Can I update the firmware?
[T-Mobile Samsung Galaxy Note 3] Misterjunky:
re: NE6 upgrade

You need to download and Odin flash the official stock N900T NE6 firmware.

Here is the direct fast download link for it:

http://www.androidfilehost.com/?fid=23501681358537528

The zip file also contains Odin, CF-Autoroot and TWRP 2.7.0.1 recovery.

Unzip the file into a new folder in windows desktop.

Be sure to go into recovery before Odin flashing NE6 and do a factory data reset

and a full wipe. Then Odin flash the TAR/MD5 firmware.

After successful odin flash, put the phone into download mode again and

flash cf-autoroot and the TWRP 2.7.0.1 tar files.

If you want more information and or instructions here is the link:

http://xdaforums.com/show...60&postcount=2

Good luck!
[T-Mobile Samsung Galaxy Note 3] sunnyboymark:
???

Ok So I did all the above and it worked good. I have all the New "Features". However, Baseband is still NB4 while the Build Version is NE6. Shall i try to fix this or leave well enough alone?
[T-Mobile Samsung Galaxy Note 3] mdiaz33685:
run triangle away v3.26.apk from chainfire, when you apply the info. it will shut down, power off, then boot to bootloader and flash firmware, that was the easiest way for the modem, baseband to stick....
[T-Mobile Samsung Galaxy Note 3] @l3X:
Fix it! I think the baseband is partly to blame for the the data drops in nb4. And I'm getting way better battery life as well. To get the new baseband to stick download Triangle Away then reflash in Odin. Worked for me. Id recommend you wipe your data too. http://xdaforums.com/galaxy-s2/orig-development/2013-10-04-triangleaway-v3-10-t1494114
[T-Mobile Samsung Galaxy Note 3] golfcartguy:
Same question....

Same question? Or do I need to update the Modem? (Baseband)?

---------- Post added at 08:33 PM ---------- Previous post was at 08:27 PM ----------

Sorry, got the answer. (You guys replied before I refreshed the browser page)

Thanks all. 5 min wait....
[T-Mobile Samsung Galaxy Note 3] sunnyboymark:
Triangle Away

I Don't see how using Triangle Away can help me update my baseband to NE6. I installed it to my phone but see no options for updating. I need more details on what to do here.....thx :)
[T-Mobile Samsung Galaxy Note 3] CravingMender9:
Use Triangle Away to reset your flash counter and make it official. Then flash NE6 with Odin/Mobile Odin to get latest baseband.
[T-Mobile Samsung Galaxy Note 3] peacewarrior:
do i need to be on stock nb4 kernel then use triangle away or does using triangle away good enough to start the process?
[T-Mobile Samsung Galaxy Note 3] SEB1109:
Just did this today, you need to be on a stock samsung kernel for triangle away the warning is VERY clear in the app. Personally, when a developer says "do it this way, or you will have a problem" I take their advice.

Read carefully and follow ALL of the instructions very carefully as well.

There are at least two different threads covering how to flash this. One has "stock ODEX" {{ http://xdaforums.com/showthread.php?t=2713354 }}, the other has "stock Deodexed" {{ http://xdaforums.com/showthread.php?t=2761451 }}

Good luck
[T-Mobile Samsung Galaxy Note 3] dragonstalker:
There is "NO" way to update officially to NE6 if you have rooted, modded, used a custom recovery in the past on you Note 3.

If you have tripped knox in any way, you will already have the bootloader you need to be on, and can flash the new stock rom from the forum.

If you have not tripped knox, have no custom recovery, have never done anything to your phone, then you are free to get the update as TMO pushes it out.
[T-Mobile Samsung Galaxy Note 3] mocsab:
I am looking for a thread that has just the modem files I need to flash to either update my modem or flash the previous modem if I have data issues.

I have searched and I know the thread exists (at least for the older modems) but for the life of me I can't find it -

Any help? Do you have the Note 3 TMOBILE modem bin's you can give me (or provide me a link? For the latest update and in the event there are issues for me to return to the previous version?

Any help is appreciated!
[T-Mobile Samsung Galaxy Note 3] noobtoob:
It does exist, but just flashing the modem alone won't solve your problem. I tried it yesterday. Seems to need something else. I flashed just modern and left the rest of phone the same. Still having to toggle every so often with the ne6 modem in here.

http://xdaforums.com/showthread.php?t=2760743

Fusionized tweaking tapatalker here...
[T-Mobile Samsung Galaxy Note 3] mocsab:
thanks - I will find something....
[T-Mobile Samsung Galaxy Note 3] noobtoob:
Good luck. I'm switching to at&t this next week. Just paid off my eip. I just want functionality. Going to hit up an aosp ROM later today to compare. When I cone back to touch wiz maybe *all new roms will be updated to ne6. It's weird though because I used to not have any issues, then a week ago I couldn't connect to anything on lte. Was hoping it was just a modem issue, but probably needs kernel as well.

Fusionized tweaking tapatalker here...
[T-Mobile Samsung Galaxy Note 3] mocsab:
I stopped buying ATT Phones after my S4 and have been very happy using TMOBILE phones on ATT network. Speeds are awesome - and having the ability to easily root and flash makes it all worthwhile.

Good Luck!
[T-Mobile Samsung Galaxy Note 3] noobtoob:
That's what I told the t-mobile rep the other day. Phones will be bought through t mobile, but as far as reliability I'm going to have to go with att. I would have stayed with t mobile if they didn't cancel my companies discount program. It was 15%, but my company decided to no longer offer the program. With att I will have a 25% and no contract. Can't really beat it.

Fusionized tweaking tapatalker here...
[T-Mobile Samsung Galaxy Note 3] mocsab:
I also tried TMOBILE services - I could not get any signal strength inside my home so the only way to make calls was to use WIFI Calling - (probably why they built that feature in the first place)

Then the data speeds were very slow - the fastest speed I could get around town was around 6mps - but on ATT I get consistent speeds over 20MBS and soemtimes 35MBS and higher - download speeds have been also very good -

I have seen others praise TMOBILE for the high speeds they get - so maybe things are better in their market? Don't know - just that they suck where i live...
[T-Mobile Samsung Galaxy Note 3] noobtoob:
In my area they are great if outdoors, but don't cover the whole city. I also have zero indoor penetration. They have bought a ton of 700 MHz spectrum off of Verizon, so that portion should get better soon.

Their LTE is fast where I live if you can get it. I got 35 Mbps the other day. But again, I have to travel outside of the city on jobs and am quite frequently without Wi-Fi or service.... So the jump is going to be made. I use my personal cell phone for work, and if I don't have signal, that is money lost...

Fusionized tweaking tapatalker here...
[T-Mobile Samsung Galaxy Note 3] theannihilator:
that is so wrong, i just did it, i used triangle away to reset my counter rebooted to let it do its thing, then chose download mode, flashed ne6 rebooted and i was at the updated baseband.
[T-Mobile Samsung Galaxy Note 3] parusia:
He is talking about officially, as OTA from tmobile. If you are on custom Rom you can't receive an OTA upgrade as far as i know. What you did is not official you flashed via Odin if I'm not wrong.
[T-Mobile Samsung Galaxy Note 3] mikef2501:
Hello, and thanks for all the great info, both in this post and in others. I am in a related situation, but please let me know if I should have put this in another post.

I have a stock un-rooted Note 3 on T-Mobile running Android 4.4.2 with firmware/baseband N900TUVUCNB4, and I was about to follow another post to root the device (http://xdaforums.com/showthread.php?t=2673780), when I happened upon the fact that some T-Mobile customers had already started receiving the update to the N900TUVUDNE6 build. I had my phone check to see if an OTA update was available, but it was not.

I was wondering, should I just wait until my phone receives an OTA update, or is there an easy/safe way to update my phone to the new build? Also, once I am on the new build, what is the best way to root the device - should I just use the procedure I linked to above? I would really prefer not to perform a factory reset/wipe, if possible. Additionally, the linked procedure uses the Philz recovery. Is there any reason I could/should not use something like ClockworkMod or TWRP after I root the device?

Thanks in advance!

--MikeF
[T-Mobile Samsung Galaxy Note 3] jdidtht:
Here ya go man, just follow this thread here. Its super easy. I prefer philz touch recovery, but while I'm in Odin and after I've flashed the fw, and root, I'll flash twrp, boot up, grab recovery tools, and just flash philz image. This guide is simple and easy, and should take more than 5 mins or so. Good luck man..

http://xdaforums.com/showthread.php?t=2765014
[T-Mobile Samsung Galaxy Note 3] mikef2501:
Great - thanks!

Just to double-check: this doesn't require me to clear my data or do a factory reset, right? I didn't see that explicitly stated in the guide you linked to, but I just thought I'd ask.

Thanks,

Mike