We are proud to announce that the Amaze 4G is now UNbrickable. Users with the QHSUSB_DLOAD issue can now fully recover their phones and get them fully functional.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it
The "core" of the unbricking project dev team:
MOVZX
RussianBear
Fuses
Dexter93
Testing stuff and irc support:
globatron
Deceptivechaos
dburgd84
Snake_skw
Other stuff:
dmcb123
xIndirect
Hawke84
Thanks to trevE, xHausx and the rest of the evo3d team that gave us the basic info to work on and made us curious to see if we could get something out of it. Also thanks to ief and his team @revolutionary for helping us understand the bootloaders better. We should also not forget to thank cxb01 of malshenzu.com and xda members arthurire and untrueparadox who helped in translation.
Prerequisites
a linux box/live cd with automount disabled and without unity
the appropriate package for the device
the latest RUU for your device
a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
a usb cable
some basic linux experience
patience
DISCLAIMER: We do NOT guarantee that this method will work for you, or that it is flawless. We are also not responsible if your phone is completely dead after the procedure, or your house burns down because your phone exploded. You are doing this in YOUR OWN RISK.
Instructions
NEW: Detailed video on the process. Its displaying the process on a Sensation, but its pretty much the same thing. Thanks to kgs1992
Boot the linux box and download the appropriate package for the device.
Extract the package in the home directory
Open up a terminal
Remove SIM, microSD card and battery and connect the device using the USB cable. This procedure must be done without battery
Detect the device using the script provided. Type this in the terminal
Code:
./brickdetect.sh
You should get something like sdX. We are interested on that "X"
Unplug the usb cable from the device
Backup the hboot currently in the phone by using this command. Plug the device in ONLY when asked to
Code:
sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12
Replace the "X" with the letter the script gave you
Follow the on-screen instructions from emmc_recover
Hexdump the b_hboot to check the hboot version
Code:
hexdump -C b_hboot.img |less
The output should be like this:
Code:
00000000 05 00 00 00 03 00 00 00 00 00 00 00 00 00 10 40 |[email protected]|
00000010 d8 fc 0f 00 d8 fb 0f 00 d8 fb 1f 40 00 01 00 00 |[email protected]|
00000020 d8 fc 1f 40 00 00 00 00 12 00 00 ea 31 2e 39 30 |[email protected]|
00000030 2e 30 38 30 38 00 00 00 38 32 36 30 20 53 50 4c |.0808...8260 SPL|
00000040 00 00 00 00 00 f0 20 e3 53 48 49 50 00 00 00 00 |...... .SHIP....|
00000050 00 f0 20 e3 00 f0 20 e3 48 42 4f 4f 54 2d 38 32 |.. ... .HBOOT-82|
00000060 36 30 00 00 00 f0 20 e3 32 64 61 64 30 66 36 32 |60.... .2dad0f62|
This is the typical hex of a hboot. We are interested to check if that is the hboot partition and if it is, to get to know the version. In this case it is 1.90
If in the above step you failed to identify the hboot, unplug all devices connected to that pc, reboot and try again
Unplug the device
Check again it is the right version, because if you do a mistake here, you won't be able to go back
You can only flash the same version as the one in the device.
!!!!!DO NOT ATTEMPT TO FLASH ANOTHER VERSION OR DOWNGRADE!!!IT HAS BEEN PROVEN FATAL!!!!
Flash the hboot on the device. Replace "V.VV" with hboot version (eg. 1.90, 1.93) and "X" with the one you got from the detect script. Plug the device in ONLY when asked to
Code:
sudo ./emmc_recover --flash rubyV.VV.nb0 --device /dev/sdX12 --backupafter hboot_f.nb0
Follow the on-screen instructions from emmc_recover. A successful flash should have this output:
Code:
511+1 records in
511+1 records out
1047808 bytes(1.0 MB) copied
Unplug the device, put SIM, microSD card and battery in and power on
Congratulations, the device is unbricked.
FLASH THE RUU IMMEDIATELY AFTER RECOVERING!! The device will be unstable after the recovery if you don't flash it.
Notes on the procedure:
If the device doesn't power on, get a copy of the hboot_f.nb0 and b_hboot.img (should be located in the home directory) and contact us
The connection between the device and the pc will be unstable, and will time out. You have to be quick when doing the above, specially while flashing. If the connection times out don't panic, just unplug and replug the device
Unity and automount are known to cause issues in ubuntu 11.04 and 11.10. We recommend getting rid of both, or use a 12.04, or 10.04/.10 liveCD
USB3 ports do not work properly. Please plug the device in a USB2 port
How to disable automount on ubuntu
Code:
gsettings set org.gnome.desktop.media-handling automount false
Downloads
For Amaze 4G( Ruby):
32bit version MD5: bf5029e39ba13061e96a98509c6ae27f
64bit version MD5: 58b74be539eb6db0c9973dd045aa9edf
Don't have a linux distro installed on your pc? We highly recommend this livecd
Awesome !!!
Amaze 4G ENERGY ICS
WOO!
10char
What exactly does this mean. The s-off method will back fire or that it has defects
Sent from my HTC Amaze 4G
S-Off
Eng-Hboot
On: Android Revolution HD 2.2.1
Sense 3.6
Android 4.0.3 Ice Cream Sandwich.
Alan Corona said:
What exactly does this mean. The s-off method will back fire or that it has defects
Sent from my HTC Amaze 4G
S-Off
Eng-Hboot
On: Android Revolution HD 2.2.1
Sense 3.6
Android 4.0.3 Ice Cream Sandwich.
Click to expand...
Click to collapse
It has happen....I'm a victim of it lol...but I have a new phone at least
Sent from my HTC_Amaze_4G using Tapatalk
Hey Dexter 93 sorry I can't help..I had to send my phone back to TMobile
Sent from my HTC_Amaze_4G using Tapatalk
Flipnfr3ak said:
It has happen....I'm a victim of it lol...but I have a new phone at least
Sent from my HTC_Amaze_4G using Tapatalk
Click to expand...
Click to collapse
Same here. Never had issue with my g2
Sent from my HTC_Amaze_4G using XDA
Flipnfr3ak said:
It has happen....I'm a victim of it lol...but I have a new phone at least
Sent from my HTC_Amaze_4G using Tapatalk
Click to expand...
Click to collapse
What happens? You didn't answer my question.
Sent from my HTC Amaze 4G
S-Off
Eng-Hboot
On: Android Revolution HD 2.2.1
Sense 3.6
Android 4.0.3 Ice Cream Sandwich.
Alan Corona said:
What happens? You didn't answer my question.
Sent from my HTC Amaze 4G
S-Off
Eng-Hboot
On: Android Revolution HD 2.2.1
Sense 3.6
Android 4.0.3 Ice Cream Sandwich.
Click to expand...
Click to collapse
Did the wire trick.....then just all of a sudden it didn't turn on....stayed black with a new battery and some other things.that hyuh the crew told me to do....but in the the wire trick bricked my phone
Sent from my HTC_Amaze_4G using Tapatalk
What is this?
I really wish there was more information posted about what this would do. I'm assuming it's a tool to unbrick bricked devices? If so, that would be amazing. It would also make me fearless going forward with future ROM installation and tinkering.
Alan Corona said:
What happens? You didn't answer my question.
Sent from my HTC Amaze 4G
S-Off
Eng-Hboot
On: Android Revolution HD 2.2.1
Sense 3.6
Android 4.0.3 Ice Cream Sandwich.
Click to expand...
Click to collapse
I want to know as well.
Sent from my HTC Amaze 4G
mischivo said:
I really wish there was more information posted about what this would do. I'm assuming it's a tool to unbrick bricked devices? If so, that would be amazing. It would also make me fearless going forward with future ROM installation and tinkering.
Click to expand...
Click to collapse
be patient, it's been on the sensation forum for a lil over 2 months now
http://forum.xda-developers.com/showthread.php?t=1522351
i can't wait my self cuz i gota vivid in need of some tlc lol
on my amaze the s-off went smooth with no issues
Flipnfr3ak said:
Did the wire trick.....then just all of a sudden it didn't turn on....stayed black with a new battery and some other things.that hyuh the crew told me to do....but in the the wire trick bricked my phone
Sent from my HTC_Amaze_4G using Tapatalk
Click to expand...
Click to collapse
I'm sorry for your loss.
Sent from my HTC Amaze 4G
S-Off
Eng-Hboot
On: Android Revolution HD 2.2.1
Sense 3.6
Android 4.0.3 Ice Cream Sandwich.
Alan Corona said:
I'm sorry for your loss.
Sent from my HTC Amaze 4G
S-Off
Eng-Hboot
On: Android Revolution HD 2.2.1
Sense 3.6
Android 4.0.3 Ice Cream Sandwich.
Click to expand...
Click to collapse
TMobile replaced it though..... It just went dead....but that's ok.
Sent from my HTC_Amaze_4G using Tapatalk
My phone work for days and suddenly freeze and never wake up again.
Unbricking
I consider myself an advanced noob, I have flashed phones for years and never managed to brick my device. If you all follow the directions and read everything than you will have success, if you decide to go about it blindly then you will fail.
call it the noob unbricker.............lol
nat4u said:
I consider myself an advanced noob, I have flashed phones for years and never managed to brick my device. If you all follow the directions and read everything than you will have success, if you decide to go about it blindly then you will fail.
call it the noob unbricker.............lol
Click to expand...
Click to collapse
Bricks happen. I have been fortunate to never brick any of my devices, and you are right reading and understanding the directions is paramount. However I have seen very talented developers brick their devices, and seen it happen to very veteran members.
Sometimes bricks happen even of you do everything right.
I have a healthy fear of doing something for the first time. Until I understand it completely, I will keep reading/researching especially the "OMG HELP" posts...s o I can see what steps people are missing. But I promise, you don't have to be a noob or not follow the directions to brick your phone...bricks happen.
krook6023 said:
Bricks happen. I have been fortunate to never brick any of my devices, and you are right reading and understanding the directions is paramount. However I have seen very talented developers brick their devices, and seen it happen to very veteran members.
Sometimes bricks happen even of you do everything right.
I have a healthy fear of doing something for the first time. Until I understand it completely, I will keep reading/researching especially the "OMG HELP" posts...s o I can see what steps people are missing. But I promise, you don't have to be a noob or not follow the directions to brick your phone...bricks happen.
Click to expand...
Click to collapse
I couldn't agree more, even going back to my days with the kaiser, luckily mtty was able to revive it. same thing with 1 of my hd2s, another hd2 decided to lose its usb port when i flashed windows mobile from android, so all in all in happens to the best of us.
on a lighter note, i have a vivid that i got as is and i'm willing to bet that it is soft bricked by someone trying to s-off but i could be wrong, so i'm waiting for this tool to come out, if not htc has an rma already for me so hope they can fix it
good luck to everyone, stay positive and hey life goes on
Release bump
Related
Free SIM Unlock for SGS2 by Odia. (ONLY for HW Version MP 1.200)
1. Root your phone.
2. Extract your nv_data.bin
3. Look at the file with an hex-editor and goto offset 0x181460 (Ultra Edit, HxD, Hex-Workshop etc)
4. Take the hashes from 0x18146e (20 bytes), 0x18148e, 0x1814ae, 0x1814ce, 0x1814ee
5. If the hash is 7D 3E 17 CF CD 81 6C AC D4 E0 25 FA A6 50 04 FD D1 7D 51 F8 ignore it since that is 00000000
6. Put the hash into the BF exe for example:-
ighashgpu.exe /h:EF63BF26E2382917D96850CCF9632458EE6E6C77 /t:sha1 /c:d /max:8 /min:8 /salt:0000000000000000
and wait for it to finish, do that for each hash which is not zeros, the Found password: [50681318] is the code.
7. Put unaccepted simcard in the phone and when it asks for the unlock code enter them in order
8. Job done, phone is now unlocked for free.
If you cannot find a block which looks like hashes @ 0x181460, then search for SSNV and add 5216, but from the files which I have seen the block appears to be fixed @ 0x181460.
If it will not accept the code which you believe to be correct, it means the attempts have been used up, so you need to use the MCK code to unfreeze your phone, note it will not request unfreeze code, just say network lock unsucessful even your code is valid. (MCK HASH is @ offset 0x180049)
Added an example for what you need to look for.
Mastercode
Dynamic located PERSO section, holds the mastercode (MCK / unfreeze), search for PERSO and look for a hash, can be multiple old sections, added screendump with an example.
MCK HASH is also in the SSNV section @ offset 0x180049
Direct Offsets
GT-I9100
NET 0x18146e -
SUB 0x18148e -
SP 0x1814ae -
CP 0x1814ce -
MCK 0x180049 -
GT-I9000
NET 0x18154b -
SUB 0x18155f -
SP 0x181573 -
CP 0x181587 -
MCK 0x1815af -
If this saved you a few quid, maybe you would like to buy me a beer
View attachment 602403
View attachment 602464
I could not have made this solution and proved my theory without the special help from pulser_g2 and Fall Guy.
I have been advised by pulser_g2 that Chainfire will make a software solution next week using this information.
(APK is here http://forum.xda-developers.com/showthread.php?t=1092451)
Im happy to test for you. Mine is locked, tried tmobile earlier today, and it required a code, im rooted so i can provide anything.
nintendolinky said:
Im happy to test for you. Mine is locked, tried tmobile earlier today, and it required a code, im rooted so i can provide anything.
Click to expand...
Click to collapse
Grab that file from the device and pop me a PM. I presume you know how to get ADB up and running?
OK. Sorta bad news. I can't see a way to retrieve the code itself from the file...
On another note, I DO notice that at address 0x181468, we see the semi-familiar pattern of FF 01 00 00 00 00 ...
On an unlocked phone, that was FF 00 00 00 00 00 (I checked earlier)
This fits in with the information at http://forum.xda-developers.com/showthread.php?t=761045, namely "Change any 0x01 to 0x00 (or 0x00 to 0x01 to lock for warranty)"
That suggests there is a possibility a free unlock could be gained by editing this file. But there would likely be consequences. As such I'm not going to recommend that, nor give instructions for it... If anyone chooses to, they do it 100% at their own risk, and should bear in mind that they NEED a backup of that and the corresponding md5sum first.
But I can't see an unlock code in plaintext
Anyway, that should be food for thought for someone who has a desire to mess about with their device. I won't be trying it for now, and I recommend you don't unless you know what to do to fix this, and are aware you are messing with stuff I don't know much about...
P
pulser_g2 said:
OK. Sorta bad news. I can't see a way to retrieve the code itself from the file...
On another note, I DO notice that at address 0x181468, we see the semi-familiar pattern of FF 01 00 00 00 00 ...
On an unlocked phone, that was FF 00 00 00 00 00 (I checked earlier)
This fits in with the information at http://forum.xda-developers.com/showthread.php?t=761045, namely "Change any 0x01 to 0x00 (or 0x00 to 0x01 to lock for warranty)"
That suggests there is a possibility a free unlock could be gained by editing this file. But there would likely be consequences. As such I'm not going to recommend that, nor give instructions for it... If anyone chooses to, they do it 100% at their own risk, and should bear in mind that they NEED a backup of that and the corresponding md5sum first.
But I can't see an unlock code in plaintext
Anyway, that should be food for thought for someone who has a desire to mess about with their device. I won't be trying it for now, and I recommend you don't unless you know what to do to fix this, and are aware you are messing with stuff I don't know much about...
P
Click to expand...
Click to collapse
Scared are we?
Pretty understandable tbh, I was kinda hoping it was as easy to unlock as the SGS but maybe there is still a way...let's hope so.
Just want to say, hex editing doesnt work. Doesn't detect sim and you get no signal, just put old file back and all works. Looks like we're gonna need another fix.
Quick question, can anyone who has an unlocked device please send me there nv_data.bin.
I want to see if there are any other differences that could be keeping it locked.
dh2311 said:
Just want to say, hex editing doesnt work. Doesn't detect sim and you get no signal, just put old file back and all works. Looks like we're gonna need another fix.
Quick question, can anyone who has an unlocked device please send me there nv_data.bin.
I want to see if there are any other differences that could be keeping it locked.
Click to expand...
Click to collapse
I diffed an unlocked and locked one, and there's a lot of differences at binary level
I would need to ask the guy whose unlocked nv_data I borrowed if he was OK with that, or see if someone else has one...
Also, I did think. Perhaps it "rejects" the file if the MD5 thing doesn't match. If it's a salted MD5, then it could check the md5 of the bin file salted against a "secret" string, and then compare to the contents of the md5sum file...
When I tried putting the old file back i used all the same commands, and it said there was no md5 sum. Which would be expected to be honest. But maybe it requires one. Ill try again this time leave the md5. Doubt it'll work, but its worth ago
EDIT: Faliure again!
Also as a note, cannot be anything to do with the md5 sum, just removed and it still works, so it cannot be checking values against it.
dh2311 said:
Also as a note, cannot be anything to do with the md5 sum, just removed and it still works, so it cannot be checking values against it.
Click to expand...
Click to collapse
OK. So it seems to be checking this file is "valid" somehow then...
pulser_g2 said:
OK. So it seems to be checking this file is "valid" somehow then...
Click to expand...
Click to collapse
is the file size identical? That's a usual standard check for validation.
risq said:
is the file size identical? That's a usual standard check for validation.
Click to expand...
Click to collapse
Should be. We are switching a bit from 0 to 1 - not adding anything
You can have my nv_data.bin if you want... my handset used to be locked to O2 but has been unlocked.
(and I've manually changed the ProductCode by editing nv_data.bin as well, not that that should make a difference)
Let me know, and I'll PM it to you
stuclark said:
You can have my nv_data.bin if you want... my handset used to be locked to O2 but has been unlocked.
(and I've manually changed the ProductCode by editing nv_data.bin as well, not that that should make a difference)
Let me know, and I'll PM it to you
Click to expand...
Click to collapse
Yeah it's worth a shot. Do you have your original file as well? This suggests you managed to edit it fine, and it still worked...
We have tried switching the flag for locked to 0x00, from 0x01, but it didn't work. Would be interesting to see the file though after using a code, to see if the flag is now at 0x00
Really what we might need is a BEFORE and AFTER from an unlock.
ie. anyone getting a code, could you get a dump of this file BEFORE the unlock, then enter the code, and then RE-dump to another file. Call them before and after perhaps? Then we can see what actually happened after the unlock - perhaps a checksum gets re-calculated, or a second "backup" bit was flipped that we missed?
My email, for anyone wanting to send their file (it's only 2 MB so goes fine as an attachment) is (the lines stop OCR gathering it for spam =D)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Email on its way
Something tells me it wont be as easy as on the previous Galaxy S. Remember, the Exynos sports an in die crypto engine.
stuclark said:
Email on its way
Click to expand...
Click to collapse
Will look at yours shortly
mathieulh said:
Something tells me it wont be as easy as on the previous Galaxy S. Remember, the Exynos sports an in die crypto engine.
Click to expand...
Click to collapse
Per http://forum.xda-developers.com/showpost.php?p=13526163&postcount=13 it is evidently possible to edit nv_data.bin and have the phone still work...
stuclark said:
Email on its way
Click to expand...
Click to collapse
any chance of emailing me the nv_data aswell?
mathieulh said:
Something tells me it wont be as easy as on the previous Galaxy S. Remember, the Exynos sports an in die crypto engine.
Click to expand...
Click to collapse
Hey Math,
there are I9103-devices with tegra2-chipsets out there. Not sure how different the firmware would be for those but I guess samsung had to find a way to make the one mechanism work for both sgs2-devices...
We are proud to announce that the Evo 3D is now UNbrickable. Users with the QHSUSB_DLOAD issue can now fully recover their phones and get them fully functional.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it
The "core" of the unbricking project dev team:
MOVZX
RussianBear
Fuses
Dexter93
Testing stuff and irc support:
globatron
Deceptivechaos
dburgd84
Snake_skw
Other stuff:
dmcb123
xIndirect
Hawke84
Thanks to trevE, xHausx and the rest of the evo3d team that gave us the basic info to work on and made us curious to see if we could get something out of it. Also thanks to ief and his team @revolutionary for helping us understand the bootloaders better. We should also not forget to thank cxb01 of malshenzu.com and xda members arthurire and untrueparadox who helped in translation.
Prerequisites
a linux box/live cd with automount disabled and without unity
the appropriate package for the device
the latest RUU for your device
a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
a usb cable
some basic linux experience
patience
DISCLAIMER: We do NOT guarantee that this method will work for you, or that it is flawless. We are also not responsible if your phone is completely dead after the procedure, or your house burns down because your phone exploded. You are doing this in YOUR OWN RISK.
Instructions
NEW: Detailed video on the process. Its displaying the process on a Sensation, but its pretty much the same thing. Watch out for partition differences. Thanks to kgs1992
Boot the linux box and download the appropriate package for the device.
WARNING: IT IS DEVICE SPECIFIC. DO NOT USE THE CDMA VERSION ON A GSM EVO AND VICE VERSA. SAME GOES FOR THE INSTRUCTIONS
Extract the package in the home directory
Open up a terminal
Remove SIM, microSD card and battery and connect the device using the USB cable. This procedure must be done without battery
Detect the device using the script provided. Type this in the terminal
Code:
./brickdetect.sh
You should get something like sdX. We are interested on that "X"
Unplug the usb cable from the device
Backup the hboot currently in the phone by using this command. Plug the device in ONLY when asked to
Code:
sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX13
Replace the "X" with the letter the script gave you
Follow the on-screen instructions from emmc_recover
Hexdump the b_hboot to check the hboot version
Code:
hexdump -C b_hboot.img |less
The output should be like this:
Code:
00000000 05 00 00 00 03 00 00 00 00 00 00 00 00 00 10 40 |[email protected]|
00000010 d8 fc 0f 00 d8 fb 0f 00 d8 fb 1f 40 00 01 00 00 |[email protected]|
00000020 d8 fc 1f 40 00 00 00 00 1a 00 00 ea 31 2e 34 30 |[email protected]|
00000030 2e 30 30 30 30 00 00 00 38 32 36 30 20 53 50 4c |.1100...8260 SPL|
00000040 00 00 00 00 00 f0 20 e3 53 48 49 50 00 00 00 00 |...... .SHIP....|
00000050 00 f0 20 e3 00 f0 20 e3 48 42 4f 4f 54 2d 38 32 |.. ... .HBOOT-82|
00000060 36 30 00 00 00 f0 20 e3 62 62 35 35 33 39 32 62 |60.... .bb55392b|
This is the typical hex of a hboot. We are interested to check if that is the hboot partition and if it is, to get to know the version. In this case it is 1.40
If in the above step you failed to identify the hboot, unplug all devices connected to that pc, reboot and try again
Unplug the device
Check again it is the right version, because if you do a mistake here, you won't be able to go back
You can only flash the same version as the one in the device.
!!!!!DO NOT ATTEMPT TO FLASH ANOTHER VERSION OR DOWNGRADE!!!IT HAS BEEN PROVEN FATAL!!!!
Flash the hboot on the device. Replace "V.VV" with hboot version (eg. 1.30, 1.40, 1.50) and "X" with the one you got from the detect script. Plug the device in ONLY when asked to
Code:
sudo ./emmc_recover --flash shooterV.VV.nb0 --device /dev/sdX13 --backupafter hboot_f.nb0
Follow the on-screen instructions from emmc_recover. A successful flash should have this output:
Code:
511+1 records in
511+1 records out
1047808 bytes(1.0 MB) copied
Unplug the device, put microSD card and battery in and power on
Congratulations, the device is unbricked.
FLASH THE RUU IMMEDIATELY AFTER RECOVERING!! The device will be unstable after the recovery if you don't flash it.
Notes on the procedure:
If the device doesn't power on, get a copy of the hboot_f.nb0 and b_hboot.img (should be located in the home directory) and contact us
The connection between the device and the pc will be unstable, and will time out. You have to be quick when doing the above, specially while flashing. If the connection times out don't panic, just unplug and replug the device
Unity and automount are known to cause issues in ubuntu 11.04 and 11.10. We recommend getting rid of both, or use a 12.04, or 10.04/.10 liveCD
USB3 ports do not work properly. Please plug the device in a USB2 port
How to disable automount on ubuntu
Code:
gsettings set org.gnome.desktop.media-handling automount false
Downloads
For EVO 3D CDMA( Shooter):
32bit version MD5: 5f49aff0347b7b839f666f590bfb3f76
64bit version MD5: e9087359552b622cf07cb5d67adb991b
Don't have a linux distro installed on your pc? We highly recommend this livecd
!Luke
Sent from my Galaxy Nexus using Tapatalk 2
nice!
Looking forward to this!
What is this for?
If you follow their instructions you can make your 3d unbrickable. Meaning you can flash whatever including a gsm rom in your cdma and be able to recover from it. Definitely excited dexter thanks
Sent from my SPH-D710 using Tapatalk 2
This sounds awesome... Will make it safer to follow the downgrade guide for hboot 1.5 users, meaning if they true brick, they can recover...
sent from my downgraded hboot 1.50 3vo running ZR3D injected with anthrax... s-off HTC, thanks to the real developers, I now have control of my device again
I <3 anticipation threads..
myn said:
I <3 anticipation threads..
Click to expand...
Click to collapse
/me starts myn ICS anticipation thread..
to this post:
:O whaaaaaaat that's awesome
Sent from my PG86100 using xda premium
Unbrickable? Shut the front door!
Works great!
Astronomical dev work. Hats off truly to all involved. I'll be picking up another 3d as well and this just gives me more incentive.
#Root-Hack_Mod*Always\
Amazing work with all parties involved. Thanks again for all the hard work and dedication.
Sent from my PG86100 using xda premium
luis4ever said:
What is this for?
Click to expand...
Click to collapse
ru joking??? lolz
Funny how they have disclaimers. The phones already bircked is it possiable to have an ultra bricked device?
Sent from my PG86100 using Tapatalk
Where was this a few months ago?! Hehe.
Great work to all those involved!
Sent from my PG86100 using Tapatalk 2
dexter93 said:
We are proud to announce that the Evo 3D is now UNbrickable. Users with the QHSUSB_DLOAD issue can now fully recover their phones and get them fully functional.
Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it
The "core" of the unbricking project dev team:
MOVZX
RussianBear
Fuses
Dexter93
Testing stuff and irc support:
globatron
Deceptivechaos
dburgd84
Snake_skw
Other stuff:
dmcb123
xIndirect
Hawke84
Thanks to trevE, xHausx and the rest of the evo3d team that gave us the basic info to work on and made us curious to see if we could get something out of it. Also thanks to ief and his team @revolutionary for helping us understand the bootloaders better. We should also not forget to thank cxb01 of malshenzu.com and xda members arthurire and untrueparadox who helped in translation.
Click to expand...
Click to collapse
Nice to Finally see the goings ons of unbricking, however any chance of this at some point becoming an unbrickable mod
sweeeeeeeet thanks guys will bookmark this. Though I am a very paranoid tester so I doubt I will ever brick my device
ok, I've had some pms about this. Maybe I didnt stress it enough in my sig, but I cannot give support by pm. I simply can't respond to all of them. Please post here so that if someone faces the same issue , will have the answer
Thanks guys
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We are proud to announce that the EVO 4G LTE is now fully supported by the HTC Unbrick Project!
Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported.
Prerequisites
the appropriate package for the device
the latest RUU for your device
a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
a usb cable
some basic linux experience
patience
DISCLAIMER: We do NOT guarantee that this method will work for you, or that it is flawless. We are also not responsible if your phone is completely dead after the procedure, or your house burns down because your phone exploded. You are doing this in YOUR OWN RISK.
Instructions
Boot the linux box and download the appropriate package for the device.
Extract the package in the home directory
Open up a terminal
Remove microSD card and connect the device using the USB cable.
Detect the device using the script provided. Type this in the terminal
Code:
sudo ./brickdetect.sh
You should get something like sdX. We are interested on that "X"
Hexdump the hboot to check the version
Code:
sudo ./emmc_recover --device /dev/sdX12 --hexdump 00000000:00000060
Replace the "X" with the letter the script gave you
Follow the on-screen instructions from emmc_recover
The output should be like this:
Code:
00000000 05 00 00 00 03 00 00 00 00 00 00 00 00 00 20 80 |.............. .|
00000010 d8 fc 0f 00 d8 fb 0f 00 d8 fb 2f 80 00 01 00 00 |........../.....|
00000020 d8 fc 2f 80 00 00 00 00 12 00 00 ea 31 2e 31 35 |../.........[B]1.15[/B]|
00000030 2e 32 32 32 32 00 00 00 38 39 36 30 20 53 50 4c |.2222...8960 SPL|
00000040 00 00 00 00 00 f0 20 e3 53 48 49 50 00 00 00 00 |...... .SHIP....|
00000050 00 f0 20 e3 00 f0 20 e3 48 42 4f 4f 54 2d 38 39 |.. ... .HBOOT-89|
00000060 36 30 00 00 00 f0 20 e3 64 69 72 74 79 2d 33 63 |60.... .dirty-3c|
This is the typical hex of a hboot. We are interested to check if that is the hboot partition and if it is, to get to know the version. In this case it is 1.15
If in the above step you failed to identify the hboot, unplug all devices connected to that pc, reboot and try again
Unplug the device
Check again it is the right version, because if you do a mistake here, you won't be able to go back
Flash the hboot on the device. Replace "V.VV" with hboot version (eg. 1.12, 1.15, 1.19) and "X" with the one you got from the detect script. Plug the device in ONLY when asked to
Code:
sudo ./emmc_recover --flash jewelV.VV.nb0 --device /dev/sdX12 --chunksize 24576 --backupafter hboot_f.nb0
Follow the on-screen instructions from emmc_recover and wait until the process is finished
Unplug the device, put microSD card in and power on
Congratulations, the device is unbricked.
FLASH THE RUU IMMEDIATELY AFTER RECOVERING!! The device will be unstable after the recovery if you don't flash it.
Notes on the procedure:
We recommend using a Ubuntu 12.04(or higher) liveCD
USB3 ports do not work properly. Please plug the device in a USB2 port
Downloads
For HTC EVO 4G LTE(Jewel)
32bit version MD5: 94615b3ec8eebdb16f078d6389cf6d0b
64bit version MD5: 05be37af94fcb2298920d1950ed017e1
Awesome!
also first...
2# thanks for this!!
For real?
Thanks. Mass.
hurled from my AOKP'd Evo LTE. Enjoy.
Is this going to help people that have bricked when downgrading firmware? It'd be awesome if we can find a way to do that . . .
I hope to see an all in one downgrader/ unbricker someday. Ik its not being worked on for windows but even a basic live cd with just the nesacities in it
I find myself in great need of something like this it seems. Is there an ETA of when this is up?
i have a bricked EvoLTE if ya'll need it. just PM me
Captain_Throwback said:
Is this going to help people that have bricked when downgrading firmware? It'd be awesome if we can find a way to do that . . .
Click to expand...
Click to collapse
Agreed, if that can be figured out, a lot of perma bricks could be salvaged. Very interested to see where this goes.
Sent from my EVO using xda app-developers app
pre2epic4g said:
i have a bricked EvoLTE if ya'll need it. just PM me
Click to expand...
Click to collapse
Are you looking to get it working again or just get rid of it?
-SLS-
Awesome!! Thank you. So this is different than the unbrick method at the unlimited.io lazy panda site?
Sent from my EVO using xda premium
scottspa74 said:
Awesome!! Thank you. So this is different than the unbrick method at the unlimited.io lazy panda site?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
this method supports other types of bricks( as listed in the OP)
the lazypanda unbricker is specific for bricks caused by lazypanda
Looks like I could've used this on my first bricked LTE (if I still had it). Nice work!
So, I may have bricked my device with no returning but I figured I'd ask.
Was trying to get s-off and the process got hung up. Rebooted and now I get no response. Tried to use RacunHunter but apparently all I get is Bus 002 Device 042: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode) in Ubuntu.
Is there anyway to revert this or what should I do?
Tripp-phpBB said:
So, I may have bricked my device with no returning but I figured I'd ask.
Was trying to get s-off and the process got hung up. Rebooted and now I get no response. Tried to use RacunHunter but apparently all I get is Bus 002 Device 042: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode) in Ubuntu.
Is there anyway to revert this or what should I do?
Click to expand...
Click to collapse
Go to the DirtyRacun IRC, they are very helpful with fixing these types of issues.
DNarsingh said:
Go to the DirtyRacun IRC, they are very helpful with fixing these types of issues.
Click to expand...
Click to collapse
I tried but one guy swears I have to send it in. I bought it off Craigslist and have it on Boost Mobile so I don't think that's really an option. I've done a ton of searching and it seems like it might be possible to unbrick it but I have no idea. So I came here in hopes someone can help me.
You might check the stickies for a thread by yarrimapirate or macguyver. Those guys were doing a lot of bricking and unbricking to get s-off and seem really knowledgeable and helpful. I'm not saying dexters tool won't work, I'm not familiar with it.
Best of luck.
Sent from my EVO using xda premium
Tripp-phpBB said:
I tried but one guy swears I have to send it in. I bought it off Craigslist and have it on Boost Mobile so I don't think that's really an option. I've done a ton of searching and it seems like it might be possible to unbrick it but I have no idea. So I came here in hopes someone can help me.
Click to expand...
Click to collapse
It should be recoverable.
I would try the irc channel for dirtyracun again. It sounds like the exact scenario they created a recovery tool for.
However, if they are unable to help, you can pm me and I can try to help. Please try their recovery tool first though, as it's most likely the solution you'll need.
-SLS-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Requirements]
1. Motorola drivers installed
2. Uncompressed file.
[Downloads]
Motorola drivers
New Motorola Logo by Fabio PAB
[Instructions]
1. Download files LOGO
2. Extract to a location easily accessible
3. Start the device in fastboot mode
(With the unit off, press VOL UP + POWER
Select AP Fastboot (Volume - Volume + moves and selects))
4. Open the file VAI.bat
5. Follow the installation steps ('s only 3 Enter)
Bonus:
Logo Moto X by Fabio PAB
Download:
http://www.mediafire.com/?lf05xcl7ey38h3e
Only replace the logo.bin mod topic and have applied.
Credits: Fabio PAB Forum Portal Android Brazil
If copy, cite CREDITS.
Hey Fabio, you think you could please make a logo bin file based on an image that has the correct motorola mobility colors in the logo, like these ones do, please? Thank you so much. ,)
ajape said:
Hey Fabio, you think you could please make a logo bin file based on an image that has the correct motorola mobility colors in the logo, like these ones do, please? Thank you so much. ,)
Click to expand...
Click to collapse
Id kill to see someone make a bootanimation out of this. Maube with the ring spinning? I like my bootloader unlocked warning bootlogo though, dont really wanna change it. is it possible to make a single, stationary image into a bootanimation?
ajape said:
Hey Fabio, you think you could please make a logo bin file based on an image that has the correct motorola mobility colors in the logo, like these ones do, please? Thank you so much. ,)
Click to expand...
Click to collapse
Thanks friend
fabiobatera said:
Thanks friend
Click to expand...
Click to collapse
Err... Well of course, you´re more than welcome my friend, but... can you do it, please, or is it not possible for some reason? Thank you...
ajape said:
Err... Well of course, you´re more than welcome my friend, but... can you do it, please, or is it not possible for some reason? Thank you...
Click to expand...
Click to collapse
Posted the mod. already with the corrected image.
Thanks
fabiobatera said:
Posted the mod. already with the corrected image.
Thanks
Click to expand...
Click to collapse
Wow, mighty fast... lol thanks buddy! Oh! And it looks really good, thanks again! ;D
ajape said:
Wow, mighty fast... lol thanks buddy!
Click to expand...
Click to collapse
I thank you.
Hey Fabio, would you perhaps happen to know why there is an interruption between the appereance of the boot screen and the start of the animation? I distinctly remember that while using the original red motorola logo, the transition to the animation was completely seamless, to the point that the logo itself appeared to dissolve and convert into the first part of the animation. Now, there are three seconds of black empty screen between one and the other, which is strange? I remember in the old HD2 there were actually two stages for the boot screen, and if you only loaded one of the graphics there would be a black gap between the bootscreen and the animation as well, Could something similar be the issue here, perhaps?
ajape said:
Hey Fabio, would you perhaps happen to know why there is an interruption between the appereance of the boot screen and the start of the animation? I distinctly remember that while using the original red motorola logo, the transition to the animation was completely seamless, to the point that the logo itself appeared to dissolve and convert into the first part of the animation. Now, there are three seconds of black empty screen between one and the other, which is strange? I remember in the old HD2 there were actually two stages for the boot screen, and if you only loaded one of the graphics there would be a black gap between the bootscreen and the animation as well, Could something similar be the issue here, perhaps?
Click to expand...
Click to collapse
friend, since this time difference may be due to the bootanimation, now when I see the difference in 3 segungos not imply anything, at least not bothering me.
Test with another bootanimation and check that decreases this time, because I am currently using the google.
hug.
It's the boot animation, I see practically no delay from my Atrix HD...
Oh, and thanks for making this awesome logo for us to use :3
53 65 6e 74 20 66 72 6f 6d 20 6d 79 20 41 74 72 69 78 20 48 44 20 75 73 69 6e 67 20 74 61 70 61 74 61 6c 6b 2e 2e 2e
That's really strange, because when I use the original Motorola red logo there is no such delay in place, it seems to melt seamlessly into the red color of the first frames of the boot animation. Anyways, you should be thanking Fabio, because all I did was get the graphics correctly but Fabio was the one that actually made it into a usable boot screen
Sent from my XT925 using xda app-developers app
This is great! Thanks!
Sent from my XT926 using Tapatalk 4 Beta
@fabiobatera Could you please put together a guide showing how to do this so we can make our own? Thanks.
Everything work, thanks a lot!
ajape said:
Hey Fabio, would you perhaps happen to know why there is an interruption between the appereance of the boot screen and the start of the animation? I distinctly remember that while using the original red motorola logo, the transition to the animation was completely seamless, to the point that the logo itself appeared to dissolve and convert into the first part of the animation. Now, there are three seconds of black empty screen between one and the other, which is strange? I remember in the old HD2 there were actually two stages for the boot screen, and if you only loaded one of the graphics there would be a black gap between the bootscreen and the animation as well, Could something similar be the issue here, perhaps?
Click to expand...
Click to collapse
like fabio said i would think this is due to your bootanimation.
im on carbon rom and i done see any interruption between motorola logo and the bootanimation
hugodefcon said:
like fabio said i would think this is due to your bootanimation.
im on carbon rom and i done see any interruption between motorola logo and the bootanimation
Click to expand...
Click to collapse
I'm not too sure, unless it's something related to my Rom that is. I mean, lately I've tried many boot animations, and I have the same delay in ALL of them so far Here, take a look:
Add new logo Moto X by FabioBatera
Hug.
Must, flash... Thank you!
53 65 6e 74 20 66 72 6f 6d 20 6d 79 20 41 74 72 69 78 20 48 44 20 75 73 69 6e 67 20 74 61 70 61 74 61 6c 6b 2e 2e 2e
So Sweet!!!
fabiobatera said:
[Requirements]
1. Motorola drivers installed
2. Uncompressed file.
[Downloads]
Motorola drivers
New Motorola Logo by Fabio PAB
[Instructions]
1. Download files LOGO
2. Extract to a location easily accessible
3. Start the device in fastboot mode
(With the unit off, press VOL UP + POWER
Select AP Fastboot (Volume - Volume + moves and selects))
4. Open the file VAI.bat
5. Follow the installation steps ('s only 3 Enter)
Bonus:
Logo Moto X by Fabio PAB
Download:
http://www.mediafire.com/?lf05xcl7ey38h3e
Only replace the logo.bin mod topic and have applied.
Credits: Fabio PAB Forum Portal Android Brazil
If copy, cite CREDITS.
Click to expand...
Click to collapse
I absolutely love this logo! Thanks a bunch!!!
Please note that this has only been testing on MTCB Head units.
As with all mods, do so at your own risk. I take no responsibility if you brick your unit.
The instructions set out below work for me and I have done been successfully using this method for over a year now.
The unit I testing it on was an Xtrons TD696a RK3188 800x480.
I have determined that this process works on Malaysk 4.4.4 roms up to about March, the same with booroondook roms. As far as I can make out it works with all 5.1 custom roms
I haven't testing much on stock firmwares but I see no reason why it won't work with all of them.
If you follow the steps correctly the worst that can happen is that it will load with your custom boot logo once then revert back to the original without causing any harm to your unit.
Tool required
gimp - https://www.gimp.org/
HxD - https://mh-nexus.de/en/programs.php
RK3xxx firmware tools by SergioPoverony - http://vondroid.com/threads/rk3xxx-firmware-tools-by-sergiopoverony.14718/#post-44489
Terminal Emulator - http://www.apkmirror.com/apk/jack-palevich/terminal-emulator/terminal-emulator-1-0-70-release/terminal-emulator-1-0-70-android-apk-download/
The guide is split into 4 sections.
1. Modifying kernel to determine image size
2. Making the image
3. Importing image to kernel
4. Installing kernel to system
5. Modifying kernel.img inside backup.img
I think I have covered everything but no doubt as time goes on things will be changed or added.
I stress again As with all mods, do so at your own risk. I take no responsibility if you brick your unit.
Modifying Kernel to determine image size.
1. Using RK3xxx decompile the update.img you are using or going to use. Click "Select Img" then browse for your update.img.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1a. Then Click Extract.
2. Click on "Logo tools" then "Run logo Changer" (A new window will open).
3. Click on "File" then "Select kernel.ing" and browse for the kernel (it will be in temp/Android/Image).
4. If the kernel boot logo loads you should see an image in the right hand box
And in the box below you should see something like:
Code:
KernelPass:rkdroid
Kernel image size: 800 * 480
Supported Image Size: 800 * 480
If you see an image you are sooooooo lucky and can skip to Making the image section.
If the kernel boot logo doesn't load you will see no image and also in the box below something like this:
Code:
KernelPass:rkdroid
ÃÜÂë´íÎó!
ÔØÈëkernelʧ°Ü
5. Open Hxd and open kernel.img (click "File" then "Open" and browse for the kernel.img).
5a. Click "Search" then "Find" and search for "rk logo password" (don't include the quotation marks "") and make sure Datatype is set to "Text-string".
5b. In the last column (furthest right) highlight between the 1st character
after "password" and before the 1st character of "rk29_backlight" (you will see that the middle section has now been highlighted as well, a total of 44 pairs of characters).
Here's where it gets a bit complicated.
5c. In the middle section take a note of the 1st set of characters and last set. In the above picture they are 93 and C0.
Left click somewhere above to clear all the highlighted code.
5d. Now in the middle section highlight everything from the 1st pair and last pair. (the 2 pairs you took a note of above). You should have 44 pairs of characters highlighted now.
5e. Right mouse click and copy then left click somewhere above again to clear any highlighted characters.
5f. Click on "Search" then "Replace", change Datatype to "Hex-values" and in the 1st box (search for) right mouse click and paste. It should have pasted the 44 pairs of characters.
5g. Copy the below set of codes and paste into the 2nd box (Replace with).
Code:
31 57 8D EB 18 4B A9 41 D9 47 EA 2F 7E 60 B1 67 6C 6F 67 6F 2E 6E 6F 6C 6F 67 6F 00 00 00 00 00 FC F3 AC C0 60 BD AB C0 C8 42 AD C0
Then click "OK".
If the changes were successful the values in the centre and right hand columns will have changed to red.
Double check that the values in the centre column match:
Code:
31 57 8D EB 18 4B A9 41 D9 47 EA 2F 7E 60 B1 67 6C 6F 67 6F 2E 6E 6F 6C 6F 67 6F 00 00 00 00 00 FC F3 AC C0 60 BD AB C0 C8 42 AD C0
5h. Save and exit HxD. (A backup of the original kernel.img has been made if you balls it up at any point).
6. Open RK3xxx again. Click on "Logo tools" then "Run Logo Changer" (a new window will open).
7. Select "File" then "Select kernel.img". Locate the kernel you have just modified.
If you did everything correct in HxD your image should load in the right hand box.
You should also see:
Code:
KernelPass:rkdroid
Kernel image size: 800 * 480
Supported Image Size: 800 * 480
or
Code:
KernelPass:rkdroid
Kernel image size: 1024 * 600
Supported Image Size: 1024 * 600
Image size is very important before you can continue. I have found that some kernels although from a 1024x600 unit have a 800x480 boot logo and visa versa.
If after doing the steps above you find that is the case. You MUST use the image size stated (Supported Image Size even though it doesn't match your unit resolution.
You have been warned.
That is pretty much the hardest section. You can now go to Making the image.
Making the image
1. Now that you have established the image size make sure the image you intend to use for a boot logo is the exact same resolution.
2. Open Gimp and open the image you want to use as a boot logo.
2b. Click on "Image", "Mode", "Indexed".
2c. Set Maximum number of colours to 224 (very important). Then click "Convert".
If you find that the quality of the image isn't as good play around with the colour dithering settings
but never change the Maximum number of colours from 224.
2d. Click on "File" then "Export as".
2e. Click on "Select File Type (By Extension).
2f. Scroll down and select "PPM Image" then "Export"
2g. Data formatting select "ASCII" (Very Important), then "Export"
Getting easier, isn't it . Off to Importing image to kernel.
Importing image to kernel
1. Using RK3xxx click on "Logo tools", then "Run Logo Changer"
2. Click "File" then "Select kernel.img" and load the kernel.img you modified earlier.
3. Click on "File" then select "PNM logo image" and load the PPM image you created in Gimp.
4. If both loaded ok
Simply click on "Replace" and the image in the right side box should change to your custom logo. Click "Exit"
Forgot to take a screenshot of it but it will move the image in the left box over to the right.
And that my pedigree chums is your kernel.img ready to be installed on your unit.
Last but not least . Installing kernel to system.
Installing kernel to system
There is a difference between kitkat and lollipop so please make sure you follow the correct instructions.
1. Copy kernel.img to external_sd.
2. Open terminal emulator.
3a. If you are using Kitkat Android 4.4.4.
Type the following. Make sure to press enter between each line:
Code:
su
cd /mnt/external_sd
dd if=kernel.img of=/dev/block/mtd/by-name/kernel
3b. If you are using Lollipop Android 5.1.
Type the following. Making sure to hit enter between each line:
Code:
su
cd /mnt/external_sd
dd if=kernel.img of=/dev/block/platform/emmc/by-name/kernel
Regardless of which one you use, you should get a few lines of confirmation. Forgot to take another screenshot but it should look something like this:
Code:
12345+1 records in
12345+1 records out
12345 bytes transferred in 0.198 secs
If it failed then it will look something like this:
Code:
12345+0 records in
12345+0 records out
12345 bytes transferred in 0.198 secs
Fingers crossed that you have the 1st output result.
You can simply type "Reboot" in terminal emulator and it will reboot the system and again, fingers crossed you will see your nice new boot logo.
I have taken a lot of time and effort to put this guide together. I know it's not perfect but I hope it helps :good:
GREAT
Example Boot Logos for Head Units
New Boot Logos on Request! Be sure, that you use the correct resolution! All files are optimized to PPM format. So you can skip Step 2 "making the image"! All downloads are direct downloads from my server!
TOYOTA
DOWNLOAD 1024x600
VAUXHALL
DOWNLOAD 1024x600
VAUXHALL ASTRA
DOWNLOAD 1024x600
Will this work with "Update_4_4_4_FUSE_800X480_RK3066_40_MAL_12_06_2016_FIX_RADIO_MTCB" - Last modified 26-Jun-2016?
Thanks
cat2115 said:
Will this work with "Update_4_4_4_FUSE_800X480_RK3066_40_MAL_12_06_2016_FIX_RADIO_MTCB" - Last modified 26-Jun-2016?
Thanks
Click to expand...
Click to collapse
Read the OP
I have determined that this process works on Malaysk 4.4.4 roms up to about March, the same with booroondook roms. As far as I can make out it works with all 5.1 custom roms
I haven't testing much on stock firmwares but I see no reason why it won't work with all of them.
Click to expand...
Click to collapse
MTCD not MTCB work ?
Hello and thank you for your work.
I can use them on bootlogo MTCD not MTCB?
If so how to do it please? The basic procedure does not.
Thanks a lot.
Goodbye
zoxenrbg said:
Hello and thank you for your work.
I can use them on bootlogo MTCD not MTCB?
If so how to do it please? The basic procedure does not.
Thanks a lot.
Goodbye
Click to expand...
Click to collapse
I think I did say in the OP that it was only tested on MTCB units. I don't know what the differences are between the 2 so I really can't comment or give you advice on MTCD units.
I use an 5.1.1 RK3188 China directly.
MCU GS 1.6...
MTCD. I help you ?
Tell me what I have to tell you please do and how to put the logo annimé (I can not find procedure).
Thanks for your help !
Jaihoidundso said:
Example Boot Logos for Head Units
New Boot Logos on Request! Be sure, that you use the correct resolution! All files are optimized to PPM format. So you can skip Step 2 "making the image"! All downloads are direct downloads from my server!
VAUXHALL
DOWNLOAD 1024x600
VAUXHALL ASTRA
DOWNLOAD 1024x600
Click to expand...
Click to collapse
Hey man! I would really appreciate it if you could make a Toyota boot logo for me please? Thank you so mcuh!
jacobreed222 said:
Hey man! I would really appreciate it if you could make a Toyota boot logo for me please? Thank you so mcuh!
Click to expand...
Click to collapse
I believe this was meant so anyone could change the 1st boot logo. It is very simple as I have finished mine a couple hours ago. This post is not a request for logo but for a user make his/her own. Follow the OP procedures and you will not have any issues. This is my first time to extract anything from a ROM and change something and make it work.
bsavoir22 said:
I believe this was meant so anyone could change the 1st boot logo. It is very simple as I have finished mine a couple hours ago. This post is not a request for logo but for a user make his/her own. Follow the OP procedures and you will not have any issues. This is my first time to extract anything from a ROM and change something and make it work.
Click to expand...
Click to collapse
It's the 1st time I've written a guide so how did it go for you following the procedure?
Goose247 said:
It's the 1st time I've written a guide so how did it go for you following the procedure?
Click to expand...
Click to collapse
It was pretty straight forward. The steps were easy to follow and I had no issues with the guide. The only issue i had was with GIMP and resizing my image, for some reason i only got it to 800x500, but after playing around with it i found that I had already created and save a 800x480 resolution copy.
jacobreed222 said:
Hey man! I would really appreciate it if you could make a Toyota boot logo for me please? Thank you so mcuh!
Click to expand...
Click to collapse
Which resolution do you have?
Jaihoidundso said:
Which resolution do you have?
Click to expand...
Click to collapse
I have the JOYING 1024x600
jacobreed222 said:
I have the JOYING 1024x600
Click to expand...
Click to collapse
You can find your image here: http://forum.xda-developers.com/showpost.php?p=68535050&postcount=7 #7
Jaihoidundso said:
You can find your image here: http://forum.xda-developers.com/showpost.php?p=68535050&postcount=7 #7
Click to expand...
Click to collapse
Thank you so much man!