yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] crushalot:
Yes, as noted in the comments section on the downloads page, the older hboot file from the GE dump is what gives the bootloader the dark look. My dark bootloader firmwares will always be hboot 1.54 unless they release a new one for the GE.
[One (M7) Android Development] Balikesirli:
:eek:

Is there difference between GE and Sense Firmware??

İf Yes, What Are the differences?

I am Only using Venom Viper
[One (M7) Android Development] crushalot:
Well, technically there is a little difference. Firmware as whole can contain a bunch of different partitions that may be somewhat optimized for the GE software since the libs are slightly different. Meaning for example the ADSP.img inside a GE firmware might make audio perform better on the GE software rather than sense.

However since the GE isn't a true ASOP phone and is based on the Sense kernel and the same exact hardware, basically for sake the sake of simplification, not really much difference. The GE firmware will always run ok, but usually it is better to have a firmware package based for the software that will be running on the phone.

Hope that wasn't to confusing.
[One (M7) Android Development] MaximN97:
yes of course i have s-off:D
[One (M7) Android Development] my_android:
hi guys

Im using viper one rom.is better to use 3.17 frimware dark bootloader or 3.17 frimware with no text warning?:confused:
[One (M7) Android Development] michmeister:
1.54 is old version. Should update to 1.55

To be safe and compatible with custom roms. Also need to downgrade firmware if you ever need to s-on cause you will brick phone if you don't. If stay away from. 1..54
[One (M7) Android Development] crushalot:
Respectfully [MENTION=5210621]michmeister[/MENTION], you don't know what the heck you are talking about. The hboot file has nothing do with rom compatibility. The hboot file is upgraded by htc mainly to remove exploits for hacking. Those with S-off have been running modified hboot files sine the the week the phone was released. The hboot file is simply the bootloader, meaning it tells the phone which partition to boot to. The rest of the partitions in the firmware is what would have an effect on rom compatibility and phone performance.

There is no technical reason why s-off user can't use any hboot they please, from the testing of the ENG (engineering) hboot to the original hboot 1.44, which a lot of s-off users prefer to run since you can boot directly to a custom recovery without installing it. So they downgrade their hboot after every firmware flash.

Also hboot 1.54 is not old. There are still many regions that are still running 1.54 as their default hboot. If the hboot version was so important then HTC wouldn't keep updating the hboot file without changing the version number as there about 4 different 1.44 hboot and 3 different 1.54 hboot revisions that all show the same version.

In conclusion, there is nothing wrong with running any hboot version you please. My firmware packages are sound and tested before release.
[One (M7) Android Development] crushalot:
I am on ViperOne and Elementalx kernel and I still prefer to run the 3.10.502.2 firmware as I have heard that 3.17 can cause issues with custom kernels.
[One (M7) Android Development] rappinlarry:
I was led to believe it stems mostly from the new radio, but you never know I guess.
[One (M7) Android Development] runganwt:
Just an information, I am running ARHD 21.0 with Elemental X 5.2 on firmware 3.17.401.2 with 4A.18 Radio.

Everything work great. Now I'll try 3.17.401.2 Dark without Radio coz 4T.xxx is bad. :D

Edited: After try 3.17.401.2 Darkboot. It's run ok. So, I am now back to 1.55
[One (M7) Android Development] crushalot:
Like the day after I posted that I flashed the 3.17 firmware. Its been running great. ViperOne 2.6 ElementalX 3.1, and I have no issues with the 4T radio.

What issues have you seen with that radio?
[One (M7) Android Development] runganwt:
Maybe it just in my country, I got bad wifi reception, some time it take ages to connect and authenticated. With 3G and H as well always switch around even I stay at the point that I am 100% sure it have perfect signal coverage (next to the cell site). After switch back to 4A.18 all those issues are gone. :D
[One (M7) Android Development] mobileman88:
I still find that the. 18 firmware the best too
[One (M7) Android Development] nightwind84:
it's ok the radio 4T.20.3218.03 for the european users? :confused: thx
[One (M7) Android Development] crushalot:
Best Radio might be different for everyone depending on location. You will have to look at the radio threads and see what other users in your area are saying. Like user above noted the 4A.18 radio worked best for them, but I ma fine on the other. You just have to try them and see.

Radios are easily changed.
[One (M7) Android Development] nightwind84:
thx :)

How install Inverted splash screen?

and if i want install a RUU for return to stock its allright with this hboot? :)

nice work! ;)
[One (M7) Android Development] zaphodbeeb:
Very cool.
[One (M7) Android Development] nightwind84:
no one?
[One (M7) Android Development] jugih:
-Download inverted splash

-Connect your phone onto computer

-Boot your phone into bootloader

-Open terminal from computer

-type: fastboot oem rebootRUU

-After phone reboots into RUU-mode, type fastboot flash zip [downloaded.zip]

-type: fastboot reboot and You're all set!

Just flash in recovery and you're all set :good:

PS. you have to be S-OFF
[One (M7) Android Development] nightwind84:
thx! for return to all stock i can installing the RUU after installation of this dark boot? :)
[One (M7) Android Development] jugih:
RUU reverts all
[One (M7) Android Development] crushalot:
The package you linked to is not flashed in fastboot.

You just flash/install that zip in Recovery to change the splash.

And yes the RUU will reset everything, splash screen, hboot, firmware, etc.
[One (M7) Android Development] jugih:
Yes, sorry! i was still oriented in firmware flashing :silly:

I'll correct this to my previous posts
[One (M7) Android Development] nightwind84:
thx and thank you for your job... is great! ;)
[One (M7) Android Development] crushalot:
Dark Bootloader for 3.22.1540.1

I have created the Dark Bootloader mod for the new firmware release that came with the 4.3 RUU for the Developer Edition.

All is working great with this new firmware and radio:

The download has been added to the OP and can be found here:

http://www.htc1guru.com/dld/3-22-1540-1_firmware_darkboot-zip/

Enjoy!
[One (M7) Android Development] wzu7:
was it a little grey lock icon at the bottom still there?! possible to remove it ?
[One (M7) Android Development] crushalot:
Yes, still there. Possible but you would have to create a modified hboot which is really hard to create.
[One (M7) Android Development] wzu7:
possible to take/make/customise from normal hboot (white screen + red text remove) plus all the file contenst is the same ?!

i mean with white background color version, maybe !
[One (M7) Android Development] crushalot:
I can post the same firmware with the stock hboot tomorrow.
[One (M7) Android Development] 99piotrek:
any chance to have 3.22 with black bootloader?

thx.
[One (M7) Android Development] mobileman88:
Its already posted 1 page ago
[One (M7) Android Development] shaman91:
hboot 1.54 in zip.

Not 1.55 hboot_signedbyaa.img

P.S. sorry, my english is bad.
[One (M7) Android Development] crushalot:
The dark bootloader is simply the GE hboot file. Until the GE gets another update the hboot in the dark bootloader packages will remain 1.54.

The stock firmware for 3.22.1540.1 (with the 1.55 hboot) will be in the next post.
[One (M7) Android Development] crushalot:
As requested here is the firmware package for 3.22.1540.1 as it came in the RUU Zip, pure stock.

http://www.htc1guru.com/dld/3-22-1540-1_firmware-zip/

Enjoy.
[One (M7) Android Development] 99piotrek:
Just wanna make it clear...

Firmware package posted page earlier includes dark hboot 1.54 and the rest from 3.22...

Am I correct?

Thanks
[One (M7) Android Development] crushalot:
Yes sir.
[One (M7) Android Development] nightwind84:
sorry but this firmware contains the new drivers for the touch? :)
[One (M7) Android Development] descenpet:
same as 2.24
[One (M7) Android Development] crushalot:
Yes, they are the same as 2.24. Sorry I misspoke as I wasn't comparing the correct checksums.
[One (M7) Android Development] nightwind84:
i have a problem... after installation of dark boot and viperone 2.7.0 with full wipe the htc synch with facebook dosen't work anymore!!! i have try full wipe and flash rom many times.... anyone know the solution? i have think use a RUU... but with this dark boot returns me a "error 155"... why?
[One (M7) Android Development] crushalot:
Did you try posting in the ViperOne thread? I am still on ViperOne 2.6 and I don't have any issues.

If you think it is related to the firmware, then just flash one of the older versions.

If you can boot into the OS and you have a working data connection, then I doubt app specific failures have anything to do with firmware.

Did you try to wipe data for those 2 apps? Also check the ElementalX thread as maybe there is an issue with that kernel of the new 2.7.
[One (M7) Android Development] AndyLeJizm:
Works great on 3.22, insertcoin 4.03 with custom kernel, thanks so much :)

A beer coming your way!
[One (M7) Android Development] wzu7:
[MENTION=4139782]crushalot[/MENTION]

what is the differ. between this 3.22.1540.1 Firmware ?

i mean was it hboot not same, firmware for both = 3.06.1700.10 firmware based on the GE 4.3 Dump ?! pls correct me ..which one recommended ?!
[One (M7) Android Development] @(^_^)@:
Can we get this for sprint since we got 4.3
[One (M7) Android Development] crushalot:
The stock version has the original hboot from the 3.22.1540.1 package and that is version 1.55 (White HTC Bootloader)

The Dark Boot version has the hboot from GE (3.06.1700.10) which is hboot 1.54 (Dark Unbranded Bootloader) inside the 3.22.1540.1 firmware

Personal choice really. They both perform the same. I personally like the dark bootloader which is why I continue to make these.
[One (M7) Android Development] crushalot:
Maybe. I just started working with the sprint roms, but I still don't have a sprint phone to test with.

I am not sure of the partition table on the sprint variant, and if they are different apart from the radio, it won't be easy to make one for sprint unless they release a Google Edition version as well.
[One (M7) Android Development] @(^_^)@:
The partitions i can send u if u want.....and yes it is just about radio which is different. I would love the black hboot. I can test if needed.
[One (M7) Android Development] crushalot:
If you could post or PM me that partition list, that would be great. I will work on it.
[One (M7) Android Development] Sneakyghost:
I'd like to take a look at the sprint partitions too if you don't mind.

There is a full list with some info in it on my thread just in case you don't know. You can use it to compare to the GSM variant if you still need such a thing.

I have also dropped a commandline toolbox (very basic) that has a dump script to dump all partitions of a phone, which could be useful to obtain a first complete stock dump of the HTC ONE CDMA version.

Only prerequisite is a modified kernel that allows execution of adb shell as root (insecure boot its called) - need some rom dev familiar with it to make one first.

My thoughts on the Firmware for sprint are: technically the device is the same, so firmware should work, but just as with the t-mobile AWS bands, it could prove rather hard to convert one into the other. So, since its definitely the radio being different, which is easily exchangeable, i think there must be some serious switch hidden somewhere in other places thats preventing conversion. We do not know how HTC realizes that, but we have to assume its in some firmware partition (i can't think of this being a hardware lock, really). To sum it up: i think there is no harm in trying out the GSM firmware on the CDMA device, but i wouldn't put my hopes up to high. Chances are, there are more differences than just the radio and those will be there for good reason.

I'd be happy to hear about results from people trying though.

regards,

Sneaky
[One (M7) Android Development] my_android:
server poroblam

I cant download 3.22.1540.1 Firmware Darkboot, becouse the server speed is very low.

can any one give a new link please?:confused:
[One (M7) Android Development] @(^_^)@:
Hey dude. Heres sprints partition table as requested.

dev: size erasesize name

mmcblk0p19: 000ffa00 00000200 "misc"

mmcblk0p36: 00fffe00 00000200 "recovery"

mmcblk0p35: 01000000 00000200 "boot"

mmcblk0p37: 73fffc00 00000200 "system"

mmcblk0p26: 00140200 00000200 "local"

mmcblk0p38: 27fffe00 00000200 "cache"

mmcblk0p39: 680000000 00000200 "userdata"

mmcblk0p22: 01400000 00000200 "devlog"

mmcblk0p24: 00040000 00000200 "pdata"

mmcblk0p27: 00010000 00000200 "extra"

mmcblk0p33: 04b00200 00000200 "radio"

mmcblk0p16: 03c00400 00000200 "adsp"

mmcblk0p15: 00100000 00000200 "dsps"

mmcblk0p17: 007ffa00 00000200 "radio_config"

mmcblk0p20: 00400000 00000200 "modem_st1"

mmcblk0p21: 00400000 00000200 "modem_st2"

mmcblk0p29: 00040000 00000200 "skylink"

mmcblk0p30: 01900000 00000200 "carrier"

mmcblk0p28: 00100000 00000200 "cdma_record"

mmcblk0p18: 02000000 00000200 "reserve_1"

mmcblk0p32: 034ffa00 00000200 "reserve_2"

mmcblk0p34: 05fffc00 00000200 "reserve_3"

mmcblk0p31: 04729a00 00000200 "reserve"
[One (M7) Android Development] Sneakyghost:
Hey mate thanks for sharing, have added your information to a new "Sprint" sheet in my GSM device partition List Google Doc.

https://docs.google.com/spreadsheet/ccc?key=0AjqWaJywIe10dExiQ0gtZmhBQ0F5NmY1V2pJVkMwdkE&usp=sharing

Please let me know if you find out more about any partition. Particularly 23 and 26 are marked with ?? as your read-out doesn't contain any info on them.

I suspect they are the same as on the GSM variant.

There is a partition shift by 2 from 28 onwards due to 2 extra partitions by the names of "SkyLink" and "Carrier" (29 and 30), Before those everything seems identical and after them, the order is the same, just 2 more and shifted by 2...
[One (M7) Android Development] crushalot:
Yesterday there was an issue with file downloads. It should be fixed now.
[One (M7) Android Development] phonepersonality:
Outstanding!!!
[One (M7) Android Development] 99piotrek:
flash 3.22 with dark hboot 1.54....

great job ... GREAT JOB :good:

THANKS
[One (M7) Android Development] crushalot:
Updated the OP to include the new AT&T 3.17.502.3 Firmware with Dark Bootloader.

Direct link:

http://www.htc1guru.com/dld/3-17-502-3_firmware_darkboot-zip/
[One (M7) Android Development] santod040:
Looks like the 1.54 bootloader partitions list in your OP, are the same as on my Verizon HTC One which has 4.2.2 and a 1.54hboot.

It's S-off and bootloader unlocked.

Do you think it could work with this GE bootloader on it?

This is the partition list from the Verizon HTC One (M7wlv):

dev: size erase size name

mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 8bfffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 2ffffe00 00000200 "cache"
mmcblk0p37: 660000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
[One (M7) Android Development] crushalot:
Looks like the partitions do match so there is a good chance. Only issue is if the hboot file is compatible and will boot the Verizon model.

As long as you are prepared for the worse, I would day give a shot.

santod040 - By the way I just wanted to say that I love your NuSenseX ROM for the Thunderbolt. Still making that little thing useful. Very awesome work.

Only reason I switched away from Verizon is that I got tired of waiting for the One to be released.

Let me know if you try the dark bootloader. So you would just take the hboot.img out of one of my firmware packages and insert it into a Verizon package right? Not sure if the other parts of my firmware packages would have an issues on that model.

Thanks for stopping in!
[One (M7) Android Development] santod040:
:good: Glad to hear you made some use of one of my roms on the old Bolt.

That one was fun. I always liked trying to make things work that were never meant to, lol.

So here I am. :)

Yeah, I would insert the hboot.img into a zip relevant to my device and try it that way.

I'm very curious of the outcome and may well try it.

I do know the potential risk though and that may or may not keep me from attempting it, for now anyway.

Maybe I will do a hex compare first and see just how similar/different they are.

Anyhow, thanks for posting this, seemed like a potential alternative to using the Regaw Mod, which still wouldn't invert it, but does remove the red text.

P.S. I got tired of waiting for the One as well, but have no other carrier options here.

Luckily someone bought me a DNA a while back and that definitely held me over. As I still use it as much as my One.

Back on topic: If I do try, I will certainly let you know.
[One (M7) Android Development] zaphodbeeb:
PN071****

Hi,

I flashed the 3.22.1540.1 version some time ago and noticed that model is now shown as PN071****. Previously this was PN0710000. Will this make any difference if i decide to use a RUU to get back to stock or if I want to get the 4.3 OTA. Also are the * wildcards? ie any model?

I have searched but cant find anything about PN071****.
[One (M7) Android Development] crushalot:
Odd, the package shouldn't change anything with your model id.

The * are just wildcards, so it shouldn't effect your ability to run a ruu. Also as long as you are s-off, you can change your model id.
[One (M7) Android Development] zaphodbeeb:
Thanks for that, can I just change the model id by flashing the relevant firmware for PN0710000, or do I need to change model id then flash the stock PN0710000 firmware to return the phone to stock. Im a little nervous about bricking the device, but like to know I can get back to stock i.e showing PN0710000, (just in case).

EDIT: Thanks for your email help. I changed MID to sort this.
[One (M7) Android Development] wzu7:
[MENTION=4139782]crushalot[/MENTION]

can you make 3.07.1700.1 GOOGLE EDITION OTA firmware .. seems not have at OP !!
[One (M7) Android Development] MarcellesWolles:
:good: :good: Tested it for quit a while now. Signal is better and the dark bootloader looks awesome :D
[One (M7) Android Development] crushalot:
I will look, but that is a GE firmware so it should already have the dark bootloader. I think there is a new hboot from it but I don't think there is a reason to update all of the previous version with that new one.
[One (M7) Android Development] crushalot:
3.57.401.500 Dark Bootloader Firmware added

Added the latest firmware with Dark Bootloader to the OP.

It is running awesome, in fact it seems much better to me that last version.

3.57.401.500 Firmware - Included Radio: 4A.20.3263.30

Enjoy!
[One (M7) Android Development] ReM0815:
Can i install this over the new 3.57 Firmware with the 1.55hboot? Or i have to downgrade first to 1.54 hboot ?

Really like the darkmod . Thumbs up ;)

Send from my IceColdOne
[One (M7) Android Development] crushalot:
Yes you can install it over the stock firmware and it will just downgrade the hboot when flashed.
[One (M7) Android Development] ReM0815:
Thx for your quick response.

Send from my IceColdOne
[One (M7) Android Development] The Great Dane:
just flashed latest darkboot firmware and works like a charm. Good job done :good:
[One (M7) Android Development] 99piotrek:
Thanks works amazing....

Hey [MENTION=4139782]crushalot[/MENTION] you know what game we have tonight...right? ;)
[One (M7) Android Development] yxtl:
this one wipe partition?
[One (M7) Android Development] 99piotrek:
NO
[One (M7) Android Development] yxtl:
Thx for answer
[One (M7) Android Development] VodkaPlease:
Quick question before i installed a modified firmware with no red warning and TWRP inside all in one..so can i flash this instantly?or i have to flash other things too?my device is ATT thanks!
[One (M7) Android Development] 99piotrek:
I always flash firmware than latest version of recovery of your choice...

Thats it!
[One (M7) Android Development] VodkaPlease:
yes but before i installed a modified firmware 3.22.1540.1(means no red warning and TWRP inside all in one) i dont remember which and i want to flash this new firmware 3.57.401.500 can i flash this this instantly?i remember someone said flashing other firmware could brick my device

---------- Post added at 07:32 PM ---------- Previous post was at 07:10 PM ----------

Ok i remembered which one i installed before i installed this firmware

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

and now i want to install this latest dark firmware can i flash instantly?
[One (M7) Android Development] 99piotrek:
Yeah i remember sth. I dont know exacly because ive never flashed that but the best way is to ask there...

I dont think it will be a problem with that but better be safe than sorry
[One (M7) Android Development] VodkaPlease:
they locked the thread...
[One (M7) Android Development] 99piotrek:
It was sth ... "You have to flash sth before going back to stock,otherwise you will brick your device ."
[One (M7) Android Development] crushalot:
As long as you already have TWRP installed then you will have no issues and really even if you don't you should be fine just use the latest version of recovery.

You can flash this over it and it will replace that modded hboot with the GE dark bootloader and it won't mess with your recovery.
[One (M7) Android Development] crushalot:
Yes I know about the game. My wife works for the Hurricanes and has to work most of the games, so I have to look after our daughter.

I'm sure you guys will win as we really stink this year.
[One (M7) Android Development] VodkaPlease:
yeah but the guy above you said i have to flash sth first if not it will brick my device??what is sth??cant i just flash this firmware instantly and thats it?
[One (M7) Android Development] crushalot:
I don't know what that is.

I think what you are thinking of is if you were running a modified hboot and then you s-on you would brick your device.

Just flashing a firmware package won't brick your device unless the package is bad.

While you would still not want to S-on with this firmware, it shouldn't brick your device because it is not a modified hboot but rather a HTC hboot from the GE.
[One (M7) Android Development] VodkaPlease:
sorry for bothering but as you can see what i flashed here http://xdaforums.com/showthread.php?t=2457069 is a modified hboot..and you're saying the dark firmware is a stock firmware so if i will flash a stock firmware it will brick my device no?
[One (M7) Android Development] crushalot:
That is not a modified hboot, but just a custom firmware package he put together.

This will not brick your device. You can flash it over what you have now.

This firmware doesn't include or mess with your installed recovery or kernel.
[One (M7) Android Development] VodkaPlease:
thank you very much!!i still dont get the thingy how to check if my device is UL or not..i don't understand that table i got my htc device from ATT.

Edit:will this firmware wipe my sd or other things?
[One (M7) Android Development] crushalot:
AT&T is a UL. It's good to go.

No this firmware will not wipe any data.