I've updated my phone to the current firmware and rooted it. I used a custom boot logo that I have used before but now there's a bunch of number in front of the red part of the image below. From what I can read it doesn't seem to match my serial, IMEI or any other number in my phone.
I could try to get a picture, but I need an actual camera can't screenshot during boot.
kmssd said:
I've updated my phone to the current firmware and rooted it. I used a custom boot logo that I have used before but now there's a bunch of number in front of the red part of the image below. From what I can read it doesn't seem to match my serial, IMEI or any other number in my phone.
I could try to get a picture, but I need an actual camera can't screenshot during boot.
Click to expand...
Click to collapse
Usually you find the words "bad key" in this line. But if you use a patched and new signed boot.img (e.g. Magisk) "bad key" turns into a hex string. It's like hash string of your boot.img
What ever the device is showing in this line, it won't be covered by the logo. This line is always in foreground with a white font and the reason for all the custom logos. As you can see on your logo, the whole area where "bad key" appears is white.
WoKoschekk said:
Usually you find the words "bad key" in this line. But if you use a patched and new signed boot.img (e.g. Magisk) "bad key" turns into a hex string. It's like hash string of your boot.img
What ever the device is showing in this line, it won't be covered by the logo. This line is always in foreground with a white font and the reason for all the custom logos. As you can see on your logo, the whole area where "bad key" appears is white.
Click to expand...
Click to collapse
So this is just a side affect of the current root method? If so, I'll just mess around with custom images and see what I can do.
kmssd said:
So this is just a side affect of the current root method? If so, I'll just mess around with custom images and see what I can do.
Click to expand...
Click to collapse
"bad key" is shown if boot is stock
"N/A" when booting TWRP
hex string if boot.img is signed with a new key
This message is created in relation to the unlocked bootloader. A stock boot.img shows only bad key if your bootloader is unlocked. If it's locked again the same boot.img shows nothing.
WoKoschekk said:
"bad key" is shown if boot is stock
"N/A" when booting TWRP
hex string if boot.img is signed with a new key
This message is created in relation to the unlocked bootloader. A stock boot.img shows only bad key if your bootloader is unlocked. If it's locked again the same boot.img shows nothing.
Click to expand...
Click to collapse
It seems like I just have to deal with it if I'm to remain rooted. Thanks for all your help.
kmssd said:
It seems like I just have to deal with it if I'm to remain rooted. Thanks for all your help.
Click to expand...
Click to collapse
You can use this one. I created it myself to hide the message.
WoKoschekk said:
You can use this one. I created it myself to hide the message.
Click to expand...
Click to collapse
Beat me to it! I was gonna test various colors and images until it was hidden.
kmssd said:
Beat me to it! I was gonna test various colors and images until it was hidden.
Click to expand...
Click to collapse
Did you use the "Moto Boot Logo Changer" for Windows?
WoKoschekk said:
Did you use the "Moto Boot Logo Changer" for Windows?
Click to expand...
Click to collapse
I use Motorola Boot Logo Maker from another member named caitsith2. It's probably the same program though.
kmssd said:
I use Motorola Boot Logo Maker from another member named caitsith2. It's probably the same program though.
Click to expand...
Click to collapse
It's the same. I no longer knew the name exactly and asked only out of interest.
Related
Is there anyway to change it? I hate looking at the X with an unlocked lock underneath it.
I am not talking about the boot animation.
This message was deleted by its author
Is this possible?
Clearly explain your problem ...
It will help me to solve your problem fastly...
When I use the ASUS UNLOCK APP to unlock my TF701T
the tablet is stuck at the ASUS Logo during boot and there is a message on the top left "the Device is UnLocked"
Can I remove the massage ?
HnCvj said:
Clearly explain your problem ...
It will help me to solve your problem fastly...
Click to expand...
Click to collapse
jqw1943 said:
When I use the ASUS UNLOCK APP to unlock my TF701T
the tablet is stuck at the ASUS Logo during boot and there is a message on the top left "the Device is UnLocked"
Can I remove the massage ?
Click to expand...
Click to collapse
This is written in the bootloader.
On the HTC One we managed to alter the bootloader to get the warning during boot removed by extracting the bootloader partition and remove the message by hand and flash it back, so maybe it is possible on the bootloader of the TF701.
I have found the location of that string, but I hesitate changing it, because a) this will not fix your warranty and b) I have no reliable info if the EBT has a checksum.
lpdunwell said:
I have found the location of that string, but I hesitate changing it, because a) this will not fix your warranty and b) I have no reliable info if the EBT has a checksum.
Click to expand...
Click to collapse
On the HTC One we did it by alterering the bootloader with a hex editor.
We just had to check if the filesize was exactly the same. I don't know if ASUS performs a crc or Md5 check right before bootloader will be flashed.
Also you need to know exactly which memblock must be flashed.
Snah001 said:
On the HTC One we did it by alterering the bootloader with a hex editor.
We just had to check if the filesize was exactly the same. I don't know if ASUS performs a crc or Md5 check right before bootloader will be flashed.
Also you need to know exactly which memblock must be flashed.
Click to expand...
Click to collapse
oh alright...
well i have unpacked the blob, there's a thread about that already.
If only size matters, you can edit the blob contents and repack...
lpdunwell said:
oh alright...
well i have unpacked the blob, there's a thread about that already.
If only size matters, you can edit the blob contents and repack...
Click to expand...
Click to collapse
I said maybe it is only the size, and probably it will be.
Will check the update script tomorrow to find out if they use a short of crc check or not.
You can try to flash a modified bootloader on your own risk of course
**Warning! This is a potentially hazardous procedure! Do not proceed unless you are willing to deal with the consequences if you do something wrong.** I am not responsible if you brick, blow up, catch on fire, or do any other damage to your phone. Do this at your own RISK! Now that I have that out of the way.
If you feel that you have the necessary skills then proceed. You don't have to wait for someone to make a No Red Text firmware zip, or flashable aboot. It is so easy to create your own no red text aboot zip, or a no-red-text firmware zip. This will work on all M9's and other HTC devices. M8, M7, etc hboot's.
You will need 7zip, and a hex editor. Just open up the firmware zip with 7zip, and extract the signed-aboot. Now open the aboot with a hex editor. In search type the first couple of words of the red text "This Build", and hit enter. That will take you to the line you need to edit to remove that annoying Red Text. On the M9 I believe it will be line 00086F2E or 0008EF3A. Once you have found the lines that appear in red on your screen after you unlocked your bootloader, navigate to the numbers on the left that coincide with the letters. Don't remove any! Type in 20,and watch the letters disappear. Do this for the entire text, and only for that text. The 20 creates a blank space that won't show on the screen. Save it, and put it back in the zip. Flash in download with fastboot. Enjoy. To make a flashable aboot take your modified aboot and android_info.txt from your device, and zip them up together. Then flash in download with fastboot.
You can also do the fake locked mod the same way. Just type in unlocked, in search, and look for the place that has locked, unlocked, and relocked together. Then do the same thing you did for the development warning to the "un" in "unlocked".
Cheers
I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9
thanx
thanx its working
thank you.
singhshb said:
thanx its working
Click to expand...
Click to collapse
You're welcome!
daydream3r said:
thank you.
Click to expand...
Click to collapse
batinica said:
This no doubt a noob question but when you say "Just open up the firmware zip with 7zip, and extract the signed-aboot" how do I go about get the zip from my device?
Click to expand...
Click to collapse
You don't get the zip from your device. What you need to do is search for a firmware zip here on XDA and use it. You will probably find someone who has already made a no red text firmware zip and use the ABOOT from it, but where's the fun in that. You could make your own firmware zip, but that's not the purpose of this thread. Search for a thread on XDA to teach you how to make a firmware zip if you are interested in doing that as well.
Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9
help please
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
bakh1 said:
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
Click to expand...
Click to collapse
Sorry my friend but looks like hard brick if it won't power on. there's nothing you can do but jtag.
This is a dangerous thing to do and could destroy your device. You are hex editing the a boot, which is cannot be compromised in any way or you will end up with a paperweight. You see, your bootloader is no longer operational. That's why your phone won't power on. In this case, allowing somebody to do it, that had no clue what they were doing, was extremely risky and foolhardy and looks to have destroyed your device.
bakh1 said:
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
Click to expand...
Click to collapse
I'm sorry to hear that your brother made a mistake editing the ABOOT. Like @Behold_this said you are now going to have to take your phone to a repair shop that has the professional tools to restore your phone to a working condition. If you are with T-Mobile and bought the phone through them you may be able to take it to them and get it replaced. Just don't mention that you modified the ABOOT. Also, if you are a US customer and you haven't used your Uh-Oh protection you can try that. I know that Mo Versi had said rooting your phone would not void the Uh Oh protection, but I don't know about modifying the ABOOT. They're all worth a try. I wish you the best with this. There's always a risk when you modify a device like we do here on XDA. The key is to always follow directions carefully, and if you're not a 100% sure of what you are doing don't do it.
Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9
please help me
i am currently out of us and not going back soon so i gave to local repair shop here they said they cant help me because jtag can only be done on m8 not m9 something like that and my brother said give me one more try he said something about htc unbrick project what should i do please
bakh1 said:
i am currently out of us and not going back soon so i gave to local repair shop here they said they cant help me because jtag can only be done on m8 not m9 something like that and my brother said give me one more try he said something about htc unbrick project what should i do please
Click to expand...
Click to collapse
As far as I know that project was for the M7 and won't work on the M9. Besides that method required for the phone to boot to bootloader or fastboot I believe. Since your phone won't boot at all the only thing I can think to do is go through your carrier or HTC. HTC has repaired or replaced many bricked devices free, but I have heard of a few cases where they would charge. If you don't mind not telling them the complete truth about how it was bricked you could tell them it was in the process of updating when it happened. That has actually happened on the M7. This is the first time I have actually heard first hand of a M9 hard bricking. All of the other ones I have heard about were able to boot to download, htc ftm, or bootloader mode and could be recovered. You have tried to boot to htc ftm by holding the power and volume up buttons continuously?
Using XDA to unleash the power of Android in my S7 Edge, One M9, and S6 Edge Plus
jbfountain said:
**Warning! This is a potentially hazardous procedure! Do not proceed unless you are willing to deal with the consequences if you do something wrong.** I am not responsible if you brick, blow up, catch on fire, or do any other damage to your phone. Do this at your own RISK! Now that I have that out of the way.
If you feel that you have the necessary skills then proceed. You don't have to wait for someone to make a No Red Text firmware zip, or flashable aboot. It is so easy to create your own no red text aboot zip, or a no-red-text firmware zip. This will work on all M9's and other HTC devices. M8, M7, etc hboot's.
You will need 7zip, and a hex editor. Just open up the firmware zip with 7zip, and extract the signed-aboot. Now open the aboot with a hex editor. In search type the first couple of words of the red text "This Build", and hit enter. That will take you to the line you need to edit to remove that annoying Red Text. On the M9 I believe it will be line 00086F2E or 0008EF3A. Once you have found the lines that appear in red on your screen after you unlocked your bootloader, navigate to the numbers on the left that coincide with the letters. Don't remove any! Type in 20,and watch the letters disappear. Do this for the entire text, and only for that text. The 20 creates a blank space that won't show on the screen. Save it, and put it back in the zip. Flash in download with fastboot. Enjoy. To make a flashable aboot take your modified aboot and android_info.txt from your device, and zip them up together. Then flash in download with fastboot.
You can also do the fake locked mod the same way. Just type in unlocked, in search, and look for the place that has locked, unlocked, and relocked together. Then do the same thing you did for the development warning to the "un" in "unlocked".
Cheers
I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9
Click to expand...
Click to collapse
I finally found your effort of writing this "recipe".
Thanky for sharing!
Is the "red text" referred to here the notice about the reporting software and that HTC will collect information about what your phone is doing, etc.? If so, will the procedure actually remove the software or stop it from running, or does it just get rid of the notice?
ETA: Is that reporting software an issue to worry about for battery use/privacy/whatever else reasons?
drfarmkid said:
Is the "red text" referred to here the notice about the reporting software and that HTC will collect information about what your phone is doing, etc.? If so, will the procedure actually remove the software or stop it from running, or does it just get rid of the notice?
ETA: Is that reporting software an issue to worry about for battery use/privacy/whatever else reasons?
Click to expand...
Click to collapse
The red text that appears on your phone after unlocking it doesn't have any functionallity. Some just do not want to see it. That's what this is all about. If you don't want to see it use this method. If it doesn't bother you don't do it.
Cheers
Sent from my HTC 10 using XDA Labs
Okay, so I bought this phone a year ago, I unlocked the bootloader, rooted it, did the whole nine yards. Learned some. F2ucked my phone up. The usual. I dont know what happened. My best guess is that I installed a VERY wrong rom on my phone. I don't know what rom, and I don't know how to find out. The phone turns on. It reaches the "Bootloader Unlocked" Warning. It stops here. It does nothing else. There is a black box on the screen, it covers almost the entire "Bootloader Unlocked" warning. If I boot the phone into Flashboot, recovery takes me to a blank puke green screen (The aforementioned black box is visible here too, however it looks like Missingn0 (from pokemon)). Selecting factory reset simply reboots the phone and puts it back at the "Bootloader Unlocked" warning. What is my problem, and is there any way to fix it?
FrustratedPhoneUser said:
Okay, so I bought this phone a year ago, I unlocked the bootloader, rooted it, did the whole nine yards. Learned some. F2ucked my phone up. The usual. I dont know what happened. My best guess is that I installed a VERY wrong rom on my phone. I don't know what rom, and I don't know how to find out. The phone turns on. It reaches the "Bootloader Unlocked" Warning. It stops here. It does nothing else. There is a black box on the screen, it covers almost the entire "Bootloader Unlocked" warning. If I boot the phone into Flashboot, recovery takes me to a blank puke green screen (The aforementioned black box is visible here too, however it looks like Missingn0 (from pokemon)). Selecting factory reset simply reboots the phone and puts it back at the "Bootloader Unlocked" warning. What is my problem, and is there any way to fix it?
Click to expand...
Click to collapse
You'll probably have to restore to stock, or you could clear data, system, cache, and dalvik and flash another ROM. It would be easier to help if you knew which ROM you flashed. You should really pay attention to what ROM you flash. It's pretty important.
Ragarianok said:
You'll probably have to restore to stock, or you could clear data, system, cache, and dalvik and flash another ROM. It would be easier to help if you knew which ROM you flashed. You should really pay attention to what ROM you flash. It's pretty important.
Click to expand...
Click to collapse
try my easy installer in signature pick correct one for your phone model i.e xt106x
Ragarianok said:
You'll probably have to restore to stock, or you could clear data, system, cache, and dalvik and flash another ROM. It would be easier to help if you knew which ROM you flashed. You should really pay attention to what ROM you flash. It's pretty important.
Click to expand...
Click to collapse
reefuge said:
try my easy installer in signature pick correct one for your phone model i.e xt106x
Click to expand...
Click to collapse
This was few months ago. I may have found the name of the Rom, But I am unsure if this is the Rom that caused the problem, or another Rom that I simply had on my PC. Also, I have just encountered another problem. The battery will not charge, It won't allow me to flash anything to the phone while its at low battery.
Okay, In reference to my last reply, After opening the Bat file and allowing the CMD to open, I had to run option 3 before running option 1. This seems to have fixed hatever the problem was, both with the charging and the device not working.
FrustratedPhoneUser said:
Okay, In reference to my last reply, After opening the Bat file and allowing the CMD to open, I had to run option 3 before running option 1. This seems to have fixed hatever the problem was, both with the charging and the device not working.
Click to expand...
Click to collapse
:good:
I am aware that Soldier has found a way to change the warning screen, does anyone have information on how to make a custom warning screen?
Also has anyone managed to change their boot animations?
For anyone interested in changing the warning screen, soldier says you need to edit the UP_PARAM.bin.
https://forum.xda-developers.com/ga...stom-splash-screen-s8-sm-g955f-t3623368/page1
I found a tutorial here for the s8, I shall give it a shot when I can (few days time)
So I'm guessing your phone is an Exynos version and rooted.
Tel864 said:
So I'm guessing your phone is an Exynos version and rooted.
Click to expand...
Click to collapse
You are correct,
Sorry I should have specified.
Please tell us then!
Soldier has posted a few options in his Telegram-channel with different screens you replace with flashing his zip of choice in TWRP. Works fine.
//P