Database Info

Bootloader splash screen not appearing

I'm having a strange issue with the T-Mobile/myTouch 4G slash screen not always appearing when the phone is booting. It's not ROM-related since it's happened with several different ROMs installed. What happens is I'll press the power button, the phone will vibrate, but rather than the white MT4G screen appearing, a completely black screen will. After that, the ROM's splash screen pops up and the boot continues normally. This happens during roughly 1 out of 10 boots, otherwise the MT4G screen appears normally. My concern is that something is corrupt with my bootloader. Does anyone have any idea what's going on here?

More probably something is corrupt with splash1 partition. But yes, something isn't well.
You could try reflashing the splash1, given that you have engineering bootloader, and see if it helps any.

What do you mean when you say "isn't well"? Do I have a potential brick on my hands?
I'm not sure how something could have become corrupted as I haven't messed with the bootloader at all. About a year ago, I rooted via the Visionary/root.sh method and have not flashed many different ROMs.
What exactly is "splash1" and how would I flash it?

That's just weird but I would have to agree with the splash partition thing. One thing you could try is drew blues splash screen editor and relash the stock img. That might fix the issue. Its some where in the apps section.

mark manning said:
That's just weird but I would have to agree with the splash partition thing. One thing you could try is drew blues splash screen editor and relash the stock img. That might fix the issue. Its some where in the apps section.
Click to expand...
Click to collapse
Thanks for the tip. I'll look into it. Do you have any idea what the consequence of a problem with the splash partition is? It still appears normally in 9 out of 10 boots.

Or also open up the pd15img and delete everything except the splash Img. (May not be called splash but you should be able to figure out which of the files it is) Then flash the pd15img accordingly
Edit: splash file and the updater script!!!!!

TeeJay3800 said:
Thanks for the tip. I'll look into it. Do you have any idea what the consequence of a problem with the splash partition is? It still appears normally in 9 out of 10 boots.
Click to expand...
Click to collapse
No I don't but I wouldn't think it could or would completely fail without loosing the entire eMMc chip.
Sent from my Google Nexus 12... yep I'm from the future where Apple is no more!

Btw tj I have to say this. Wrong section buddy lol. ;-)
Jk jk

mark manning said:
Btw tj I have to say this. Wrong section buddy lol. ;-)
Jk jk
Click to expand...
Click to collapse
Haha, I knew someone would give me s**t. I debated if it really belonged in Q&A. Still not sure. Maybe you're right.

I am thinking about flashing a new bootloader flash screen via fastboot by following the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=866474. If anyone has any input I'm all ears.

mark manning said:
That's just weird but I would have to agree with the splash partition thing. One thing you could try is drew blues splash screen editor and relash the stock img. That might fix the issue. Its some where in the apps section.
Click to expand...
Click to collapse
you mean this one?
http://forum.xda-developers.com/showthread.php?t=956434
if not, this one works very well, just used it yesterday, worked amazingly.

TeeJay3800 said:
I am thinking about flashing a new bootloader flash screen via fastboot by following the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=866474. If anyone has any input I'm all ears.
Click to expand...
Click to collapse
I'd say - go for it. In the worst case, you'll get a customized splash screen, in the best case - your problem will disappear.
If it doesn't help - you could try (re)flashing Engineering HBOOT.
And if both didn't help - then you should hope that this would be the only semi-bad sector your eMMC has (most probably the problem appears because eMMC isn't read correctly, but since it's on splash1 partition - the only harm is not seeing the image).

Jack_R1 said:
I'd say - go for it. In the worst case, you'll get a customized splash screen, in the best case - your problem will disappear.
If it doesn't help - you could try (re)flashing Engineering HBOOT.
And if both didn't help - then you should hope that this would be the only semi-bad sector your eMMC has (most probably the problem appears because eMMC isn't read correctly, but since it's on splash1 partition - the only harm is not seeing the image).
Click to expand...
Click to collapse
Thanks for the info. I do have the "good" eMMC, so hopefully this fixes the issue and I have no further problems.

[FIX] Flashed Wrong Recovery image

Alright, so we all know it's confusing to differentiate the One XL from the One X, especially since Rogers and AT&T insist on calling it the One X.
IF YOU HAVE A "ONE X" FROM ROGERS/AT&T, YOU HAVE THE ONE XL. DON'T EVEN BOTHER VISITING THE ONE X FORUMS.
Now, you've gone and downloaded CWM from the One X forums and flashed it to your One XL, and you're semi-bricked. Let's get you out of that pickle. Please note that I have not done any of this to my own One XL, as there's no ROMs or custom recovery images or kernels for our phone yet. However, just this morning I performed a similar operation on my Jetstream, and the steps will be identical. I take no responsibility for any problems you experience.
First, you'll need to download the leaked RUU that can be found here: http://forum.xda-developers.com/showthread.php?t=1550930
EDIT: designgears has offered a newer recovery image. I'm not sure what advantages it would bring, but at least there's a second option: http://www.gigashare.in/53885
Please note that this is marked as the AT&T RUU, so there's no guarantee this will work for Rogers. However, your recovery mode is screwed anyway, so in my opinion, it couldn't hurt to try.
Once you've downloaded the RUU, run it. You don't need to install the RUU itself, we just have to have the application running. Once running, it'll create a "rom.zip" file in a temp folder somewhere in your user profile. While the RUU is open, just search for "rom.zip" and you should find it. Open this file and extract "recovery_signed.img" to your computer, into the same folder as your "fastboot" application. Once you've done this, close the zip file and exit the RUU.
Now, boot your device into fastboot mode
Code:
adb reboot bootloader
Once in bootloader mode, you may need to select "fastboot" from the menu.
Now that you're in fastboot mode, you can flash the recovery we extracted from the RUU:
Code:
fastboot flash recovery recovery_signed.img
Your screen will go through a couple brief steps, something like "sending recovery_signed.img" then "writing recovery_signed.img" and then "OK."
Try to boot into recovery now, and you should see the standard HTC recovery mode!
I really hope this helps everyone out. I'll iterate again that I have no tried this with my One XL, so I have no actual proof that this will work. But, if you've already flashed the wrong recovery image, you should be somewhat familiar with these steps already.
EDIT: Please post your success with this method. As I haven't tested, I'd like to know if everything's kosher, and I can change the instructions accordingly if something's wrong.

Hey, sorry I didn't get back to you sooner, went to bed.
Here is just the recovery image for a newer, unreleased leak.
http://www.gigashare.in/53885
1.61.502.1 CL49502

designgears said:
Hey, sorry I didn't get back to you sooner, went to bed.
Here is just the recovery image for a newer, unreleased leak.
http://www.gigashare.in/53885
Click to expand...
Click to collapse
Heh, don't apologize to me, my phone's locked and running fine. (I've had the phone since Friday... I think this is the longest I've ever gone without rooting an Android phone.)
I'll put that link up in the first post, thanks!
EDIT: Oh! And is that AT&T or Rogers?

craig0r said:
Heh, don't apologize to me, my phone's locked and running fine. (I've had the phone since Friday... I think this is the longest I've ever gone without rooting an Android phone.)
I'll put that link up in the first post, thanks!
EDIT: Oh! And is that AT&T or Rogers?
Click to expand...
Click to collapse
It's AT&T recovery.

Flashed but still having trouble. Got into recovery but can't boot.
Going to see if re-locking the bootloader may help. Only thing different I've done is that I ran that flash_boot.zip thing that Leedroid had on his page. It just seems to push a boot.img file and clear the fastboot cache.
Does anyone have that particular boot.img file? Pretty please?

For myself I will leave it for now and wait until an official rogers RUU or custom recovery to make sure I don't break it again
Sent from my HTC One X

bongd said:
Flashed but still having trouble. Got into recovery but can't boot.
Going to see if re-locking the bootloader may help. Only thing different I've done is that I ran that flash_boot.zip thing that Leedroid had on his page. It just seems to push a boot.img file and clear the fastboot cache.
Does anyone have that particular boot.img file? Pretty please?
Click to expand...
Click to collapse
The rom.zip file from the AT&T ruu should have the boot.img file in it. you can flash it with
Code:
fastboot flash boot boot.img
However, the boot partition is a WEE bit more critical to the phone's function than the recovery partition. Dunno if I'd be flashing it myself, at least not to a Rogers phone.
Sent from my HTC One X using xda premium

craig0r said:
The rom.zip file from the AT&T ruu should have the boot.img file in it. you can flash it with
Code:
fastboot flash boot boot.img
However, the boot partition is a WEE bit more critical to the phone's function than the recovery partition. Dunno if I'd be flashing it myself, at least not to a Rogers phone.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks, man. Someone said they flashed the entire RUU to their Rogers phone so I don't think it could be too harmful.
I only have my Ubuntu machine and Wine is being fussy and not extracting the rom.zip archive properly. I'll see if something gets released soon. I rarely see Rogers RUU so hopefully I'm not waiting too long. Reactivated my SIM for my Galaxy Nexus but still sad lol

I feel your pain!
bongd said:
Thanks, man. Someone said they flashed the entire RUU to their Rogers phone so I don't think it could be too harmful.
I only have my Ubuntu machine and Wine is being fussy and not extracting the rom.zip archive properly. I'll see if something gets released soon. I rarely see Rogers RUU so hopefully I'm not waiting too long. Reactivated my SIM for my Galaxy Nexus but still sad lol
Click to expand...
Click to collapse
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.

krepler said:
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
Click to expand...
Click to collapse
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL

bongd said:
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
Click to expand...
Click to collapse
Ok, I'm in the middle of downloading the evita leaked files. I can't extract it from my phone since I need root... unless you know a way other than adb shell? Either way, I don't think you can access it without root. I've tried a few ways with no luck.
I see you can't access the evita files so the best I can do for you is extract it from there for you. Download is slow as hell, so bear with me!

krepler said:
Ok, I'm in the middle of downloading the evita leaked files. I can't extract it from my phone since I need root... unless you know a way other than adb shell? Either way, I don't think you can access it without root. I've tried a few ways with no luck.
I see you can't access the evita files so the best I can do for you is extract it from there for you. Download is slow as hell, so bear with me!
Click to expand...
Click to collapse
No need to ask for my patience, bro. It's hugely appreciated! Thanks a ton!

bongd said:
No need to ask for my patience, bro. It's hugely appreciated! Thanks a ton!
Click to expand...
Click to collapse
My new issue is I'll have to make a couple more posts before I can add urls to them, since I never post on the forums. Gotta start somewhere...
Scratch that, you the good 'ol copy and paste.
http://www.gigashare.in/d4129 = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 recovery_signed.img
http://www.gigashare.in/8adee = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 boot_signed.img

krepler said:
My new issue is I'll have to make a couple more posts before I can add urls to them, since I never post on the forums. Gotta start somewhere...
Scratch that, you the good 'ol copy and paste.
http://www.gigashare.in/d4129 = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 recovery_signed.img
http://www.gigashare.in/8adee = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 boot_signed.img
Click to expand...
Click to collapse
and the latest:
http://www.gigashare.in/0029e = Cingular 1.68.502.1 Radio 0.16.32.09.01 boot_signed.img
http://www.gigashare.in/03695 = Cingular 1.68.502.1 Radio 0.16.32.09.01 recovery_signed.img
Should've just waited and posted these ones... buuuuuuut, I have no patience.
Hopefully the boot.img works for you! Let me know how she goes.

bongd said:
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
Click to expand...
Click to collapse
Bongd, The recovery works for you? My situtation is in the same boat with Krepler minus the boot.img. I am little bit worry if I load the AT&T recovery and that will conflict the boot.img in Rogers phone.
---------- Post added at 07:25 AM ---------- Previous post was at 07:22 AM ----------
krepler said:
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
Click to expand...
Click to collapse
Krepler, Can you tell me how did you solve your recovery? I am in your sisutation as well, flash the wrong recovery and once I boot to recovery and it will occur the boot loop, however I am still able to use the One X (Semi-bricked). Did you flash the stock recovery from Rogers or the one that you just posted from AT&T?

Elin28 said:
Bongd, The recovery works for you? My situtation is in the same boat with Krepler minus the boot.img. I am little bit worry if I load the AT&T recovery and that will conflict the boot.img in Rogers phone.
Click to expand...
Click to collapse
One does not interfere with the other. Recovery is pretty much its own operating system, completely segregated from the rest of the phone. It can neither hinder nor enhance the booting of your phone in normal mode. You could theoretically flash a random sequence of ones and zeros to the recovery partition, and the phone would continue to boot just fine. Until you try and go into recovery mode that is. Flashing the recovery_signed.img as per my instructions is safe in regards to the phone's normal operation. I can't promise that it's a working recovery, however, as I've not tried it myself.

Awesome! Just booted up, my man. A thousand fellatios to you!! Please message me your Paypal address so I can buy you a beer or two.
Haven't tried the Cingular ones but the AT&T ones worked just fine. I'm betting it'll be damn near identical, save probably a few radio adjustments or very minor adjustments.
Booted to the main screen so I should be able to set things up. But I'll chime in and report if there are any major issues. Thanks again!!

Hey I am happy your phone boot up man!!
I am still having trouble with the recovery. I try flash the att& the cingular recovery. good thing is no bootloop I see an image showing black phone and a green circle. then I end up with image of a phone with red triangle with a "!" inside. and then the phone reboots.
am I doing something wrong?
Thanks
bongd said:
Awesome! Just booted up, my man. A thousand fellatios to you!! Please message me your Paypal address so I can buy you a beer or two.
Haven't tried the Cingular ones but the AT&T ones worked just fine. I'm betting it'll be damn near identical, save probably a few radio adjustments or very minor adjustments.
Booted to the main screen so I should be able to set things up. But I'll chime in and report if there are any major issues. Thanks again!!
Click to expand...
Click to collapse

@bongd
Awesome bro!!!! Glad you got your hox up and running.
Sent from wherever I am!

yoohoohoo said:
Hey I am happy your phone boot up man!!
I am still having trouble with the recovery. I try flash the att& the cingular recovery. good thing is no bootloop I see an image showing black phone and a green circle. then I end up with image of a phone with red triangle with a "!" inside. and then the phone reboots.
am I doing something wrong?
Thanks
Click to expand...
Click to collapse
Have you tried running "fastboot erase cache"?
What other steps have you done as well? The killer for me was the boot.img file that Leedroid created as part of his ROM installation. The AT&T recovery is what I had used. For a moment I thought I might need to try flashing the system.img file like redwreck had to, but I didn't need to.
Perhaps someone could upload that as well, please? If you need to flash that, it's "fastboot flash system system.img" and it'll flash that too. I always do "fastboot reboot" after as well.
I trust that these should work. Hopefully there'll be a full Rogers RUU so we can flash that just to be on the safe side. Best of luck! I'll keep an eye on this thread as well.
Since I posted earlier I've been setting things up and it's working like a damn charm. Tried exhausting every weird and quirky feature I thought might screw up, but I can't find anything that's not working.

[Q] Tampered above unlocked, and development purposes only before splash screen

OK.. here we go.. I bought my VERIZON M8 the day it was released. I came to this site, after having successfully put the viper Timon my DNA. Not exactly.new to this but I'm in a bit of a mess. I have tampered above unlocked on my bootloader screen and when I boot into the ROM I am using... A message flashes at the bottom saying for development use only and other legal stuff from HTC. What steps can I take to remove those? I have permanent s-off and weaksauce still installed. Is there a toolkit like for the m7 or am I missing something? Help is appreciated.

Joeymaz73 said:
OK.. here we go.. I bought my VERIZON M8 the day it was released. I came to this site, after having successfully put the viper Timon my DNA. Not exactly.new to this but I'm in a bit of a mess. I have tampered above unlocked on my bootloader screen and when I boot into the ROM I am using... A message flashes at the bottom saying for development use only and other legal stuff from HTC. What steps can I take to remove those? I have permanent s-off and weaksauce still installed. Is there a toolkit like for the m7 or am I missing something? Help is appreciated.
Click to expand...
Click to collapse
I see a message about "Development use only for HTC" or whatever when booting into the bootloader (or recovery...or both...I can't remember), but it doesn't affect anything. Is that what you're referring to? Also, remove Weaksauce like the S-Off instructions told you to do.
And what exactly is this "mess" you're in? If a message flashes across your screen and then your phone finishes booting into the ROM, that doesn't exactly sound like a mess to me...

sfreemanoh said:
I see a message about "Development use only for HTC" or whatever when booting into the bootloader (or recovery...or both...I can't remember), but it doesn't affect anything. Is that what you're referring to? Also, remove Weaksauce like the S-Off instructions told you to do.
And what exactly is this "mess" you're in? If a message flashes across your screen and then your phone finishes booting into the ROM, that doesn't exactly sound like a mess to me...
Click to expand...
Click to collapse
I guess I'm just ocd. I dont like seeing those messages if i dont have to.I had originally. Removed weaksauce.. but put it back on when the permanent. Root didn't take effect properly. Is everyone seeing tampered? If not I'd prefer to be able to get rid of it as well.

Joeymaz73 said:
I guess I'm just ocd. I dont like seeing those messages if i dont have to.I had originally. Removed weaksauce.. but put it back on when the permanent. Root didn't take effect properly. Is everyone seeing tampered? If not I'd prefer to be able to get rid of it as well.
Click to expand...
Click to collapse
If flashing the superuser zip didn't work correctly for you, that's an issue you should probably look into...
Like I said, I don't see it say "tampered", I just see the "This build is for development purposes only" message when I boot into recovery. You're sure you see it when booting normally into the ROM itself?

sfreemanoh said:
If flashing the superuser zip didn't work correctly for you, that's an issue you should probably look into...
Like I said, I don't see it say "tampered", I just see the "This build is for development purposes only" message when I boot into recovery. You're sure you see it when booting normally into the ROM itself?
Click to expand...
Click to collapse
go here: http://forum.xda-developers.com/showthread.php?t=2709976

kwkw480 said:
go here: http://forum.xda-developers.com/showthread.php?t=2709976
Click to expand...
Click to collapse
Yeah, but unless if he also flashed a custom boot.img (or a ROM that has a custom boot.img included), or is actually booting into recovery when he sees it, he shouldn't be seeing it when he boots into the ROM itself.
Edit: I just misread the OP, apparently he may be using a custom ROM, I didn't notice that before.

sfreemanoh said:
Yeah, but unless if he also flashed a custom boot.img (or a ROM that has a custom boot.img included), or is actually booting into recovery when he sees it, he shouldn't be seeing it when he boots into the ROM itself.
Edit: I just misread the OP, apparently he may be using a custom ROM, I didn't notice that before.
Click to expand...
Click to collapse
Sorry Guys, I should have told you which ROM I had flashed to.. SKYFALL★| |►1.12.605.11◄|4.4.2|VZW||ODEX/DEODEX||►1.2◄|April.10. I'll follow the directions pointed to in the thread above when I get home.. Still leaves me with "tampered" when I boot into recovery or bootloader.

kwkw480 said:
go here: http://forum.xda-developers.com/showthread.php?t=2709976
Click to expand...
Click to collapse
Ok.. That zip file, for the red letters worked great. thank you..

after a bunch of searching.. I found this..http://forum.xda-developers.com/showthread.php?t=2708565
thanks for everyone's help. I appreciate everything you do.

Or you can go here where there are a variety of options including making your phone look like it is still s-on
http://forum.xda-developers.com/showthread.php?t=2710503

Thanks for that tool page. I love learning new things about these phones. 20 years I've just been a PC guy.. learning how to do some of this can be tricky. Thank goodness for this forum and the people on it.

Removing red text from splash screen?

I have to go get a new SIM from Verizon. When they put it in, they're going to see my splash screen that says I have a developer ROM or whatever it says (I'm on stock rooted). Does this matter to them? Can I cover that up somehow?

PsiPhiDan said:
I have to go get a new SIM from Verizon. When they put it in, they're going to see my splash screen that says I have a developer ROM or whatever it says (I'm on stock rooted). Does this matter to them? Can I cover that up somehow?
Click to expand...
Click to collapse
On the normal boot? Mine only does that when I go into recovery... I guess you could try finding a default boot animation .gif and puting it in the boot animation location, but idk if that will actually work.

jshap70 said:
On the normal boot? Mine only does that when I go into recovery... I guess you could try finding a default boot animation .gif and puting it in the boot animation location, but idk if that will actually work.
Click to expand...
Click to collapse
mine shows the red warning text on every boot. any way to remove?
running a custom rom, but it shows up with stock as well. (i am s-off)

PsiPhiDan said:
I have to go get a new SIM from Verizon. When they put it in, they're going to see my splash screen that says I have a developer ROM or whatever it says (I'm on stock rooted). Does this matter to them? Can I cover that up somehow?
Click to expand...
Click to collapse
Here ya go bud: http://forum.xda-developers.com/showthread.php?t=2709976

[MOD][6.0 hboot][no red writing]

I was annoyed at having to look at the red text after flashing the recently released MM firmware so I thought I would share this modified hboot.img where I removed it.
A faux hboot was also requested which falsely shows locked & s-on. It's unclear what exactly people want this for but I discourage using this to sell or return a phone under the false pretenses of it being bone stock, locked, s-on. There are steps you can take to properly achieve that.
These have been tested with fastboot (RUU mode) but the sdcard method (0p6bimg.zip on the root of removable storage) should work just fine.
Downloads
6.21.605.3 hboot with red text removed
https://www.androidfilehost.com/?fid=24438995911975964
6.21.605.3 faux hboot with red text removed, locked, s-on
https://www.androidfilehost.com/?fid=24457741883932708
Credits
Shout out to @Tigerstown for a little bit of hand holding and for being a generally cool dude.
These were made by starting with the firmware files posted by @dottat found here:
http://forum.xda-developers.com/verizon-htc-one-m8/development/stock-m-firmware-nand-recovery-t3330972
Directions
boot into bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
wait for flashing process to complete
fastboot reboot-bootloader
fastboot reboot
profit

Glad to see you got it. I'll go ahead and close my thread and link them here.

Very appreciated guys!
Sent using XDA One

Will this work by placing file in SD ext and changing file name to 0P6BIMG?

eriknors said:
Will this work by placing file in SD ext and changing file name to 0P6BIMG?
Click to expand...
Click to collapse
Yeah, exactly how I always flash them

Any chance a faux locked bootloader can be made? They come in handy when needing to show a vzw rep ur phone to prove its "stock"

eriknors said:
Any chance a faux locked bootloader can be made? They come in handy when needing to show a vzw rep ur phone to prove its "stock"
Click to expand...
Click to collapse
Maybe. I'm curious to look into this as well. No promises as this seems at least a little more involved and the last thing I'm gonna do is brick my (or someone else's) phone just for the sake of satiating my budding curiosity.

Sweet. Thanks.

This is always the first thing I'm looking for after a firmware update. Thank you!
Sent from my m8wl using Tapatalk

THIS!!

v1ral said:
THIS!!
Click to expand...
Click to collapse
Evocm7 said:
This is always the first thing I'm looking for after a firmware update. Thank you!
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
schneid said:
Sweet. Thanks.
Click to expand...
Click to collapse
Looking like people are very happy you contacted me to help you do your own. Now everyone wins...nice contribute to community
cntryby429 said:
Maybe. I'm curious to look into this as well. No promises as this seems at least a little more involved and the last thing I'm gonna do is brick my (or someone else's) phone just for the sake of satiating my budding curiosity.
Click to expand...
Click to collapse
If your interested in doing this I'm more then willing to help you, if you even need it.

eriknors said:
Any chance a faux locked bootloader can be made? They come in handy when needing to show a vzw rep ur phone to prove its "stock"
Click to expand...
Click to collapse
Added faux locked s-on noredtext hboot to OP.

Working Perfect...!!!
Thank you... :highfive:

Does this work on all variants? I have an international GSM and want to give it to HTC to get a new battery. That red screen might get them un s-offing me.

I have a question...
What did you do to make it work through the SD card method, I am trying to change my splash screen without using ADB.

v1ral said:
I have a question...
What did you do to make it work through the SD card method, I am trying to change my splash screen without using ADB.
Click to expand...
Click to collapse
It's simply a matter of zipping up the file(s) you want flashed that have been named correctly alongside an android-info.txt file that matches you phone. If you download one of the firmware files I linked to you can see what the correct filenames are. I think the splash screen are named splash1.<something>.
The android-info.txt file doesn't actually say anything about the other files alongside it to be flashed. It serves as a sort of validation check that the whole zip is meant for the phone. My zips only contain the hboot while the ruus have like 15 files but the android-info.txt files are identical.
A proper android-info.txt file + correctly named files + being zipped = sd card OR RUU mode flashable.

Will this work on a S-ON device ? I kinda wanna get rid of the red text at boot...but my device is S-ON

dodgedroid said:
Will this work on a S-ON device ? I kinda wanna get rid of the red text at boot...but my device is S-ON
Click to expand...
Click to collapse
No it will not. How did you end up with the red text but s-on? Is it a vzw device?

Nope, it's Internation GSM variant

dodgedroid said:
Nope, it's Internation GSM variant
Click to expand...
Click to collapse
An unlocked bootloader only gives you access to flash unsigned files to a few partitions like boot (kernel) and system, probably another one or two.
S-off is required to flash unsigned files to other partitions like hboot. Not to mention, the files in this thread are specific to the vzw hboot so even if you could flash them I wouldn't recommend it.