RegawMOD Bootloader Customizer | Full Application | Updated 10.09.13 - Android Software Development

Check Post #2 for plugins for your device!
Description
RegawMOD Bootloader Customizer is a utility for Windows that allows the
user to create a custom HTC firmware zip containing a custom bootloader image.
Your device has to be S-OFF for this to work!
If you are looking to create a plugin for your device so you can use this program go HERE
With this program, you are able to edit the *** UNLOCKED *** text on the top
to whatever you want it to say, change the S-OFF to S-ON, change the bootloader's version number,
update the bootloader's date and time stamp, and hide/customize the splash screen disclaimer.
Choosing the "Stock" look option automatically sets your banner to *** LOCKED ***,
changes S-OFF to S-ON and hides the HTC Development Splash Screen Disclaimer.
This program will NOT flash the zip for you, but it will allow you to save it to your computer to let you flash the zip yourself.
The process (flashing a new bootloader) is dangerous and may possibly brick your device if done incorrectly. You have been warned.
Just remember, anyone can make a plugin, and not everyone can be trusted.
Make SURE you only flash zips made from plugins by developers you trust!
Featured on the portal (Thanks PoorCollegeGuy!)
Screenshots
Requirements
Windows w/ .NET 4.0 - Get .NET 4.0
HTC Device that is either S-OFF or allows flashing of unsigned hboot
Usage
Download the plugin for your device (See post #2 for list of plugins)
Place the plugin in the same directory as the 'RegawMOD Bootloader Customizer.exe' on your computer
You can have as many plugins in the directory at the same time as you'd like
Run the 'RegawMOD Bootloader Customizer.exe'.
Begin customizing be choosing "Stock", or customize your own look and feel using the text box at the top and options below.
Press "Create Zip" to make the firmware zip
How To Flash A firmware zip (Devices with a removable sdcard)
Place the zip on the root of your external sdcard. (Copy it right onto your sdcard, not in any folder)
Reboot the phone into the bootloader by either:
Powering off your phone completely, then hold Volume-Down and Power until the phone boots into the bootloader
If you have the android sdk set up, type 'adb reboot-bootloader'
Use my RegawMOD Rebooter
Then select the menu option "Bootloader" and press the power button.
If you rebooted the manual way (Volume-Down + Power) You should already be at this menu
It will load the zip from your sdcard and ask you to accept the flash.
Press Volume Up to flash (On most devices, but could be a different button)
Once prompted, press Power to reboot (On most devices, but could be a different button)
Pro-Tip #1 (thanks dsEVOlve): Remove the firmware zip from your sdcard so it doesn't load next time you enter the bootloader.
How To Flash A firmware zip (Devices without a removable sdcard)
Reboot the phone into the bootloader by either:
Powering off your phone completely, then hold Volume-Down and Power until the phone boots into the bootloader
If you have the android sdk set up, type 'adb reboot-bootloader'
Use my RegawMOD Rebooter
Connect your phone to the computer (if it isn't already) and issue the fastboot command
Code:
fastboot oem rebootRUU
To flash the zip, issue the fastboot command
Code:
fastboot flash zip <[SIZE=2]YourZipName>.zip[/SIZE]
The device's progress bar may not be complete, but when the fastboot command says it's complete, issue the fastboot command
Code:
fastboot reboot
Warning
This program/created firmware zip comes with NO WARRANTY (express or implied), and NO GUARANTEE OF FITNESS for any particular task. I have made every effort I can to make this a safe process for users however the author disclaims any liability for damage to your phone or other materials or devices used during this process. The entire risk of flashing the created PJ75IMG.zip lies with you, the user. By creating and/or flashing the firmware zip, you acknowledge and accept that the author is not liable for any loss, material or otherwise howsoever caused.
Changelog
Version 2.1 | 10.09.13
Add Verizon HTC One support
Version 2.2.2 | 06.10.13
Updated to support HTC One varieties
Version 2.2 | 02.18.13
Added support for HTC One series (X, XL, V...) and Droid DNA
Download Latest Release
RegawMOD Bootloader Customizer
Download Info
RegawMOD Bootloader Customizer.exe MD5 - 9d642f7502fe0953b95e9c2ea578e1f1
Source Code
Github

List of user-made plugins:
HTC Evo 4G LTE - regaw_leinad
Hboot 1.12.0000
HTC Evo 4G LTE - liamstears
Stock Hboot 2.09
DirtyRacun Hboot 2.09
HTC One (Sprint) - eg1122
Stock Hboot 1.44.0000
HTC One (AT&T) - eg1122
Stock Hboot 1.44.0000
HTC One XL - liamstears
Hboot 2.14
Hboot 1.14
Hboot 1.09
Droid DNA - liamstears
ENG Hboot 1.39.2000
Stock Hboot 1.33
OTA Hboot 1.33
HTC One S - liamstears
Hboot 2.15
ENG Hboot 1.14.0004
Hboot 1.13
Hboot 1.06
HTC Vivid 4G - cruzin_cruzing
Hboot 1.85.0025
HTC Droid Incredible 4G LTE Thread - junkmail9

PLEASE read the entire OP. I don't want to sit here answering questions that are already answered in the OP.
And be sure to use the 'Thanks' button

So will using this new version/tool to create a new zip put the custom message back on the boot screen that disappeared after the 1.22 update? I have tried re-applying my zips from the original bootloader customizer for LTEvo after 1.22 and I only get the custom message when rebooting into Recovery. Just wondering if you found the fix for that yet.
Sent from my Meanie ICS LTEvo

Stock look option lists bootloader version as 1.12.2222 instead of 0000.

long_tall_texan said:
So will using this new version/tool to create a new zip put the custom message back on the boot screen that disappeared after the 1.22 update? I have tried re-applying my zips from the original bootloader customizer for LTEvo after 1.22 and I only get the custom message when rebooting into Recovery. Just wondering if you found the fix for that yet.
Sent from my Meanie ICS LTEvo
Click to expand...
Click to collapse
I think that change was in the kernel (or something else related to the boot.img), not the bootloader, so no, this won't "fix" that.

Also, great work on getting the purple banner background to display only behind actual banner characters even when there's less than 16 of them. Is it possible to get a post-OTA stock look option and a way to edit the entire HBOOT version number? Got a bit of a cognitive dissonance going between HBOOT 1.12.0000 / old build date and 1.05 radio.

I have my test Unit HTC HD2, is it supported?
i think its not,
ill just try another phone here...
great work man. really hard working
OT:
with your lib i created a drop and drop apk installer
great man
thanks

I made a .dll plugin file for the HTC Sensation with the help of cruzin_cloud. It is for the Sensation, Sensation XE, and Sensation 4g using Hboot 1.27.1100 and it will change the Hboot to 1.27.1111 unless you choose for it not to when making the .zip. I used the Hboot from unlimited.io. If the regaw_leinad updates his tool i will update the .dll file as needed. Thanks to regaw_leinad for this awesome tool. Also if regaw_leinad does not mind I will post a thread in the Sensation Android Development Forum for this.
Edit:
I thought I should also add that you have to have the 1.27.1100 Hboot version to use this. It is do th how the RegawMOD Bootloader Customizer works. I will make more but I will have yo flash different Hboots to my device to text so it might be a day or two befor I have a couple more ready
Thread in the Sensation Development forum.
HTC Sensation Download

Great work going to give it a try
Has anyone been able to create a profle for the HTC Incredible S (Vivo)

small bug found
There is a small bug in this DLL version of the customizer (as opposed to the Evo 4G LTE single EXE version in another thread)... if you pick the "stock" look and generate the PJ75IMG.zip file, you get a MessageBox informing you of the things that will change in the bootloader look. One of them is the hboot version will be set to "0000". However, with the latest LazyPanda hboot 1.12.2222 - this change does not take place when the zip is flashed; it remains 1.12.2222.
I noticed that when you click the stock radio button in the application, it defaults some of the checkboxes in the lower half and at the same time disables that group box. However, if you look closely, the boot "Version #" is not checked. Perhaps this is why the version number is not set. If I go the custom route and make the changes myself, it indeed changes the version number to "0000" when I put that in.
Anyone else noticing this behavior?

PillowMetal said:
Anyone else noticing this behavior?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=29100365&postcount=5

Yeah, I'll get to this in a bit. I am updating the plugin interface for the developers.

Is it trivial to update the first 3 digits of HBOOT version along with the last 4? Now that 1.19 is out, it would be nice to be able to display the latest version number to match the latest radios.
Also, is there a way to update the build date/time to something specific? I see the option in the Customizer menu, but no way to input the date/time.

Kisakuku said:
Is it trivial to update the first 3 digits of HBOOT version along with the last 4? Now that 1.19 is out, it would be nice to be able to display the latest version number to match the latest radios.
Also, is there a way to update the build date/time to something specific? I see the option in the Customizer menu, but no way to input the date/time.
Click to expand...
Click to collapse
If you just want an updated stock-looking HBOOT, I have that, and can post it.
You can update pretty much all that stuff with a simple hex editor.

Captain_Throwback said:
If you just want an updated stock-looking HBOOT, I have that, and can post it.
You can update pretty much all that stuff with a simple hex editor.
Click to expand...
Click to collapse
Fair enough, I just really like the whole concept of this tool, so I was trying to coax Regaw_leinad out of hiding.
If you do have the latest Lazy Panda HBOOT 1.12.2222 (with fastboot flash enabled) edited to look like 1.19 (with correct spacing/purple background for "*** LOCKED ***"), I'd love that. BTW, any recommendations for a bug-free hex editor under Win7? Also, do you have a pic of a stock HBOOT 1.19 bootloader? The perfectionist in me wants to get the correct build date/time.
And the last question: is the displaying of CID when S-OFF the last thing that still needs to be fixed in order to have a completely stock-looking bootloader screen?

Kisakuku said:
Fair enough, I just really like the whole concept of this tool, so I was trying to coax Regaw_leinad out of hiding.
If you do have the latest Lazy Panda HBOOT 1.12.2222 (with fastboot flash enabled) edited to look like 1.19 (with correct spacing/purple background for "*** LOCKED ***"), I'd love that. BTW, any recommendations for a bug-free hex editor under Win7? Also, do you have a pic of a stock HBOOT 1.19 bootloader? The perfectionist in me wants to get the correct build date/time.
And the last question: is the displaying of CID when S-OFF the last thing that still needs to be fixed in order to have a completely stock-looking bootloader screen?
Click to expand...
Click to collapse
Here's a picture of my current bootloader:
{
"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"
}
Of course the date has been updated to match the new version - I am also a perfectionist .
And yes, the only thing keeping this from looking exactly the same as stock is the CID line (which I assume, is by design).

Captain_Throwback said:
Here's a picture of my current bootloader:
Of course the date has been updated to match the new version - I am also a perfectionist .
And yes, the only thing keeping this from looking exactly the same as stock is the CID line (which I assume, is by design).
Click to expand...
Click to collapse
Ah, nice to meet a fellow perfectionist. Thanks for the pic and the clarification, would appreciate a download link and a hex editor recommendation.

Kisakuku said:
Ah, nice to meet a fellow perfectionist. Thanks for the pic and the clarification, would appreciate a download link and a hex editor recommendation.
Click to expand...
Click to collapse
Attached is the fastboot-enabled HBOOT from the LazyPanda site, modded to appear as 1.19.0000, with build date updated, and red dev text removed.
As far as a hex editor goes, I use the Free Hex Editor Neo on Windows, and HexEditor on my device.

Captain_Throwback said:
Attached is the fastboot-enabled HBOOT from the LazyPanda site, modded to appear as 1.19.0000, with build date updated, and red dev text removed.
As far as a hex editor goes, I use the Free Hex Editor Neo on Windows, and HexEditor on my device.
Click to expand...
Click to collapse
Much appreciated and thrice thanked.

Related

The Ultimate Guide to Flashing a ROM on the HD2 (Windows Mobile)

I already posted this in the general section but thought i would post it here as well as this is more of an appropriate forum for the thread.
Just thought i would share a tutorial i made about flashing ROMs
If this helps anyone in any way then i will be happy, i know there is already a few Flash guides out there but i wanted to have a go at my own.
Anyways if you find it helpful please leave a comment on the tutorial or if you have anything i could add leave a comment saying what it is.
Flashing a ROM is a simple procedure but for most the task sounds daunting. For those of you who are ready to take the leap and flash a ROM onto your phone i have good news for you. In this guide i am going to show you how to flash a ROM the easy way.
NOTE: This guide is based on the European version of the HTC HD2 (Leo) flashing process, flashing for other devices may vary. You must also make sure before starting this guide that you know which version of the HD2 you have so that you can flash the right ROM and Radio if needed. The European version of the HD2 has a 512 MB ROM and the US version has a 1024 MB ROM, the European version is also a little smaller than the US version and has less RAM, the US version has 576 MBs of RAM and the European version has 448 MBs. The US version also has a different Radio version that supports T-Mobile US's Frequencys. If you are unsure about which version of the HD2 you have then go to the Settings menu on your device, go to About Phone, and then look at Hardware information and Software information.
The first thing your going to need to check before you begin is that you have HSPL on your phone. If you don’t have any idea what HSPL is, take a step back and read up on it first. (Video on how to install HSPL) (XDA thread on HSPL with download link – For HD2 only) If your not using a HD2 then search XDA forums for the correct HSPL for your device.
Now that you have HSPL or for those that already had it, your going to need two things, a phone with Windows Mobile on it and a USB cable to connect your device to your computer.
NOTE: You may also need to update your devices Radio version depending on which ROM you flash.
So go ahead and plug your device in, a new screen should now show on your device. If not its probably because its your first time connecting the phone to your computer, don’t panic! just wait a while for the drivers to install and you should be up and running in about 20 seconds.
Select the Active Sync connection from the list.
{
"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"
}
And press done.
Now your device is connected properly you are ready to choose a ROM.
The best place to get ROMs is the XDA Forum. Point your browser to http://forum.xda-developers.com/ and then continue on to the next step.
The main page of the forum gives you a list of devices running Android and Windows Mobile and their respective threads.
Windows Mobile Forums are labelled with a Windows Mobile icon and Android Forums with an Android icon. Find your device and select the “ROM Development” Sub-Forum.
Once your in the Sub-Forum for your device browse through the ROM threads until you find a ROM that best suites you. For the sake of the tutorial we are going to choose the Energy GTX ROM.
As you can see in the screenshot above there are a lot of numbers involved. The only numbers you really have to worry about is the Windows Mobile Build Number. In this case its 21911 and 23673. The difference between the two is that a 21911 ROM has Windows Mobile 6.5 on it and a 23673 ROM has Windows Mobile 6.5.3 on it. There is not a major noticeable difference between the two Builds apart from the change in UI. In 6.5.3 the start menu, lock button and exit button are located at the bottom of the screen where as in 6.5 everything is located at the top, 6.5.3 also sports full multitouch support, threaded email and texting, Office Mobile 2010, the ability to drag and drop start menu icons and decreased page load time, improved memory management and gesture smoothing in Internet Explorer Mobile 6. In my opinion 6.5.3 looks better as it has a more up to date UI and on a device like the HD2 having everything at the bottom saves you a stretch. For more information on Windows Mobile Builds hit this link.
NOTE: Not all builds for 6.5.3 and 6.5 will have the same build number. However all builds with 21 as the first two digits will be windows mobile 6.5 and all builds with 23 as the first two digits will be windows mobile 6.5.3
Now you have chosen which ROM you are going to flash, you will need to download the files for that ROM. In my case the download link is on the second post of the thread.
NOTE: Don’t forget to check if the ROM needs a specific Radio version. Link to the HD2 Radio thread. For other devices search the XDA forum for your devices radio thread.
REMEMBER: Make sure you get the right ROM for your device and the right Radio version as flashing a Radio that is not for your device could brick it.
Hit the download link and save the file to the desktop. The file may be hosted of site but don’t worry, the sites are safe i assure you.
Once you have downloaded the ROM file you will need to extract it. In my case the ROM i downloaded was in the .7z format so i used WinRAR to extract it. WinRAR also works for .rar files and .zip files.
Now you have extracted the files you should have a folder that looks like this.
Inside the folder there should be two files, one .nbh file and one .exe file. If there are any other files in the folder you need not worry about them unless they are named “READ ME” or something similar to that.
NOTE: Do not move or remove any of the files inside the folder as it will cause the flashing process to not work.
The .exe file is the ROM flashing utility and the .nbh file is the actual ROM image that will be flashed to your device. Think of the ROM file as a .zip file and the ROM flashing utility as the extractor program which will extract it to your device.
Now we will begin the ROM Flashing process. MAKE SURE TO BACK UP ALL OF YOUR DATA AS THIS WILL WIPE YOUR DEVICE AND PUT IT BACK TO FACTORY SETTINGS. if you need a program to backup your data then i recommend using PIM Backup.
REMEMBER: Make sure your device is plugged in and set to active sync connection mode.
If your using XP run the .exe file which in my case is Leo_softwareUpgrade.exe and if your using Vista or Windows 7, right click the .exe file and choose run as administrator.
The ROM flashing utility will now open, read any warnings and click next.
Again read any warnings and click next
The utility will now take a few seconds to check the information on your HD2
The next screen will open after your information is verified. Click “Update” to proceed.
The next screen will tell you which ROM version you are currently using and which version you are about to flash. Double check that the ROM you are about to flash is the correct version and hit next.
The final screen will now show, read everything on screen and make sure you are ready to continue, if you changed your mind and don’t want to flash anymore you can hit the ESC to exit the program. Hit “Flash” to begin the flashing process.
NOTE: Once the flashing process has started you cannot stop it.
Once you have clicked “Flash” the flashing process will begin and a progress bar will appear onscreen.
REMEMBER: Make sure to read the warnings.
Your device will now restart and boot into the HSPL screen, don’t worry if this looks strange to you, its perfectly normal and safe.
If your device does not show this screen straight the way its probably because the drivers for HSPL mode are installing, be patient as this can time a while. Sometimes when the drivers aren’t already installed for HSPL mode the ROM Flashing utility may give you an error and say something like “Device not connected” or “Could not connect to device”. Don’t worry if this happens, just start the process again and follow the steps until you reach this point again.
The next screen you will see will look like this. So there should now be a progress bar onscreen on your computer and on your device.
NOTE: Flashing times may vary depending on the speed of your computer.
Once the flashing process has reached 100% you should see a confirmation on your computer screen saying “Congratulations your ROM update is now Complete”. Hit the finish button and you are done.
If the ROM has flashed successfully your device should restart and boot up as normal. Notice at the bottom of your screen it should display your new ROM version.
Your device may take longer to boot than normal but this is normal after a fresh ROM flash.
Most ROMs will have their own install screen so after the first boot screen you should see a screen like this.
The best thing about custom ROMs is that most of them have many of the usual settings already set up and skip unnecessary screens like the Screen Calibration setup and Typing Test screen.
The next screen that will show will be the carrier setup screen. Select the option that suites your plan and hit “Next”
NOTE: PostPay = Contract and PrePay = Pay As You Go
The next screen will confirm your selection and download the necessary settings.
Hit “Done” at the bottom when the download is complete.
The device will now load up your home screen, in my case that is GTX Sense.
And now your done! You now have a brand new ROM installed and set up on your device.
Credit to: Cotulla and DFT for the HSPL and NRG for the ROM
Excellent Guide for New Device Owners.
Sticky Recommended.
Excellent. I have only ever flashed official ROMs before, but nice to know that the process is the same for Custom ROMs. Looking to flash to the Energy Rom just so that I can get the FB tab! LOL.
Now to check how to flash a new radio.
good one !!!
very good guide, i'll be sure to use it when i decide to flash. cheers.........
Nicely done, one of the best ones that goes into detail. It assumes you know nothing, yet would turn you into a seasoned pro at the end!
Well done
morpheus1982 said:
Excellent. I have only ever flashed official ROMs before, but nice to know that the process is the same for Custom ROMs. Looking to flash to the Energy Rom just so that I can get the FB tab! LOL.
Now to check how to flash a new radio.
Click to expand...
Click to collapse
You won't go wrong with the Energy roms - have a look at my sig for rom and radio. And flashing the radio is the same as flashing the rom - it just takes less time to do!
Towserspvm2000 said:
You won't go wrong with the Energy roms - have a look at my sig for rom and radio. And flashing the radio is the same as flashing the rom - it just takes less time to do!
Click to expand...
Click to collapse
Thanks for the info.
thanks for positive response guys, much apreciated, glad to see it helped a few
A very good explanation,reminds me of the Iphone Redsnow tutorial,keep the good work.
I have never flashed custom ROM before ,I usually customize the oficial 1.66xxxx which came with my phone,but Im thinking to flash one soon,just couple of questions:
1-My OS version is 21xxx thats according to your guide must be WM 6.5,now can I install any version of custom ROM including one with 23xxx which is WM 6.5.3 or just the the same version currenty on my phone:.
2-Should I install the HSPl and the Radio first.it would be nice if you could make another tutorial on those two subject as well.Very confusing since there are so many versions of both.
Thanks.
And please make this thread sticky.
I have recently installed a new rom, it installed successfully but when the phone is on it stays on for one minute then it shuts off by its self. when i turn it back on stays on the T-mobile stick together screen. Also When I take the battery out for like 10 minutes the phone boots up to windows but turns off after 1-2 minutes. Please help, I have tired Reinstalling the rom again but that does not help

[UTILITY] Android Flasher 2.2.0.5! (12/12/11)

{
"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"
}
Android Flasher needs you!
Are you an experienced Android user?
We need people to update the Pro database for each device, this means the radio/bootloader/recovery for each device. PM me for more details.
This also includes HTC Magic, Samsung Galaxy S and S II, Motorola Atrix, and Sony Xperia Play.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
S-OFF is essential with ENG hboot
Features:
Multiple flashes without closing the application.
Deletes all used files leaving you with nothing more than what you had to start with.
Fully automatic, users only need to create a splash image or locate a recovery, hboot, or radio img.
Unified interface.
Coded entirely in C#
Now supports BMP, PNG, and JPEG images. Not just BMP like NBIMG.
Usable on your Desire, Desire Z, Desire HD, EVO 4g, EVO 3D, Desire S, Incredible S, Thunderbolt or Sensation.
The application checks image dimensions and the file sizes of splash images to prevent any errors.
Click to expand...
Click to collapse
Requirements for use:
USB debugging enabled.
HTC and Fastboot/Hboot drivers must be installed.
Windows with .net 4.0
Splash image, recovery img, hboot img or radio img. (not required for donate version)
Click to expand...
Click to collapse
What the application does:
This application flashes the specific parts of your device, ie. Bootloader, Recovery, Splash screen, and Radio.
It has taken many hours and much extensive research and testing on multiple devices to make a straightforward, efficient and reliable program to offer you the freedom in device customisation you are otherwise denied.
The app allows you to quickly customise your device in a way that is simple and alot goes on behind the scenes to guarantee you don't get caught with error messages.
The splash screen is the image before the boot animation, (by default the white HTC logo.) With this application you can change it in under a minute.
Click to expand...
Click to collapse
Credits to SA7039 for assistance and Google for fastboot, adb and dlls.
Android Flasher Splash Database Upload Tool
(like imageshack but just for splash screens)
http://deltaxent.com.au/af/upload.form.php
Search the DB using:
http://deltaxent.com.au/sa7039/Sorter/view.php
Got problems? Want to request features? Submit them here.
Click to expand...
Click to collapse
Changelog:
Code:
2.2.0.5
Donate - Added auto-login.
Donate - Added another "Download Archive" button for convienence.
Donate - Fixed a few exceptions.
Donate - Fixed some downloads.
Donate - Auto sort list by version.
Donate - Bigger image displayed on hover of image/splash.
Reworked flashing selection page.
Reworked about page.
Reduced timers from 7 to 2.
MessageBoxes for errors.
MessageBoxes on detection of S-ON and non-ENG bootloader.
Fixed backgroundworker on the flashing process.
Added "Errors/Requests" menu item under help.
Cleaned up code.
Added news page.
2.2.0.0
Added other devices for ALL other devices.
Added progress bar for initial downloads.
Added Wildfire S support.
All images are now resized for your device :).
Donate - Added download browser, contains an archive of radios, recoveries, hboots and splashes.
Donate - Official release.
2.1.0.5
Added: EVO 3D, Incredible S, Desire S and Thunderbolt.
Added recent device display as the first button.
Updated pictures to be higher quality.
Fixed redo progress bug.
Added WiMax
2.1.0.1
Fixed a device bug that affected everything except for the Desire and Sensation.
2.1
Fixed checkboxes
Added 'Already in fastboot' button
Rewrote logging
Fixed donate button ;)
Added update notifications
Auto downloads data folder
Added path conversion to unicode, should help with localisation.
Added Desire HD and EVO 4g support.
Added Device list pages - moved DHD to second page with EVO 4G.
2.0.5
MsgBox for invalid splash image dimensions
Image displays in the center when selected
When you unselect a checkbox, it says 'No file selected.'
Menu button added in the file menu
Label changed Z/HD
Added 'Donate' button ;)
Now verifies that the splash img file is the correct size for flashing
2.0
Brand new, recoded entirely from the ground up.
Supports multiple devices, and image extensions.
Please consider donating .
New!
With Download Browser for all supported devices:
Click here!
Click to expand...
Click to collapse
How is the bmp supposed to be configured?
BMP should be configured how ever you like. The program converts it from whatever configuration you saved it as. I personally use:
"File format: Windows"
"Depth: 24bit"
Wow...interesting...sounds good
Thanks..with kind regards..Alex
so now we can use our own boot pics right?
dosent work for me, just sits at waiting for device
hmm tried it with an .jpg
saved and renamed it as written to splash1.bmp but it didnt worked.
i have got the android now on a skateboard as bootscreen.
weird haha
you have to save the image as bmp, not jpg.
Cool, one minute before s-off and there is a thread to change the first boot screen ... will try it now ... black boot screen = save batt
WHAT RESOLUTION IS NEEDED? 800x480 or 392x65?
pa.pn2 said:
so now we can use our own boot pics right?
Click to expand...
Click to collapse
Yep, it does. I've got my own .
AndroHero said:
dosent work for me, just sits at waiting for device
Click to expand...
Click to collapse
Have you connected your phone in fastboot mode?
philJ said:
Cool, one minute before s-off and there is a thread to change the first boot screen ... will try it now ... black boot screen = save batt
Click to expand...
Click to collapse
Yeah, will help on reboots.
I'll bring out my next one which puts your device in fastboot flashes and then reboot for you soon.
danward said:
Have you connected your phone in fastboot mode?
Click to expand...
Click to collapse
it says hboot in the op sorry i will try again
i saved a .jpg on my pc from the internet
opened with photoshop and saved it as an .bmp again correct?
renamed it and placed it in the folder...
AndroHero said:
it says hboot in the op sorry i will try again
Click to expand...
Click to collapse
I'm testing the auto reboot version now. It'll be up soon. All you gotta do is have it connected to your comp with debugging on.
danward said:
I'm testing the auto reboot version now. It'll be up soon. All you gotta do is have it connected to your comp with debugging on.
Click to expand...
Click to collapse
Fine ... what res is needed for the pics?
philJ said:
Fine ... what res is needed for the pics?
Click to expand...
Click to collapse
It's up. Umm, it resizes it. But optimal is 480x800.
EDIT: 480x800 is required. Sorry guys.
Doesn't work for me. Created a bmp, renamed it to splash1 and ran the bat while phone was in fastboot mode.
This is essentially same as doing it via cmd using "fastboot flash splash1 *image*" ?
But im a bit confused as to what the image needs to be. Seen .nb's, nb0's, .img's and .rgb565's.
when i flash it, the image looks like its 4 identical images layered ontop of eachother
it changes my splash screen to "three androids playing skateboards", but I don't even know where this image comes from.
Jgruar said:
Doesn't work for me. Created a bmp, renamed it to splash1 and ran the bat while phone was in fastboot mode.
This is essentially same as doing it via cmd using "fastboot flash splash1 *image*" ?
But im a bit confused as to what the image needs to be. Seen .nb's, nb0's, .img's and .rgb565's.
Click to expand...
Click to collapse
Yeah, thats the basic thing. IMG files are what HTC use. I know they are supported. If it doesn't work, try the new one i just uploaded. I know it works on mine and a few others.
AndroHero said:
when i flash it, the image looks like its 4 identical images layered ontop of eachother
Click to expand...
Click to collapse
Check your BMP file. Save it again and reconvert it after. What did you use to make the BMP file?
ive solved my problem, its because it dosent resize it for you, make sure the dimentions of the .bmp are 480x800 and all will be fine

[Q] Milestone 2 on CM9 unknoweird issues!

Hi everybody, this is my first post, though I've been a reader from a long time ago.
Long story short: I received this milestone 2 from my brother, my other phone is a defy (cm7), I use both of them, updated to cm9 on milestone, milestone kaput, need help, has anybody got a clue on what is going on with my phone?
Last night or so I grabbed a copy of the latest CM9 rom from the forum, installed it and really loved it. Except for two messy TINY things. except for that I cannot believe I got almost 2 days of battery out of it!!!
First issue: Google apps, I mean anything google related, won't work and FC. even if I am am on the browser, and try to type an address, the second google search kicks in to show suggestion dara! dead google crap.
Second Issue: Home button won't do anything. I mean the phone does vibrate when it is pressed, by the way I already chcked for key assignments, not even long-pressing it will show any response except for the vibration.
Third issue: Say Im reading something, lock my phone... when unlocking it, it won't show me the lockscreen, even though it is activated.
at first I said "ok let's swap launchers maybe I can make it go away" and so Ive tried ADW ex, trbuchet and a couple more, with no success, going back to ADW regular, a very nice thing here, is that video recording has worked well since the first time I flashed the rom.
Thanks for your eventual responses!!
I almost forgot: this is what I have done until now: flashed and reflashed at least 6 times, flashed gapps, flashed gapps fix, in many combinations, wiping the hell out of the phone every time... I'm really stuck in here!
Ive also searched not only the forums but the internet aswell, and I find my googling skills pretty decent to be fair
New developments!
So, I got a little curious.. I had installed on my milestone the ics alike cm7... or so I remember, (if it was a theme my bad, anyway...) I was going through phone information, and I noticed something strange:
Android version: 2.3.7
mod version: CyanogenMod-72-111215..........NIGHTLY Milestone 2 gb
Build number: Gingerbread GWK74 CyanogenMilestone 2
so one does not have to be a genius to just see that I *may* have not applied the update, or that the updating process was somehow incomplete.. question has anybody who has ever applied CM9 on their phones came to this issue?? have you applied the update via cwmod or stock recovery or wtf am I doing wrong here uh?
I am really, really puzzled!!
cm7 has a theme that make it looks like ICS but its still a gingerbread (2.3.x android version).
CM9 is the real ICS.
You installed CM7 with a ICS theme, as we can see in your mod version: CyanogenMod-72-111215..........NIGHTLY Milestone 2 gb
knew that already!
yup dude, you are totally right, I may have confused you people along my post...
I have had installed CM7 with the ICS theme, the one with the 2.3.6 android
However, I grabbed a copy of CM9 from this forum (the one based on tezet's work, that first one on the dev thread...)
I flashed that file via cwm..
and I've had, as I state on mi first post here, flashed, reflashed, recontraflashed the thing, and resseted my phone to factory so much that it has got to be newer than brand new now... just kidding..
anyway, thanks for your interest man, my bad!
I've just re-read my post.. I never mentioned that I already had installed CM7 on my milestone!
LOL.
Try this:
In the bootmenu you can choose between "stock" "custom or "latest" recovery, try with a different one i think it worked for me when i used custom recovery.
LOL :S
Dude lol I think I've just messed up BIG TIME.....
well seeing how it didnt seem to work out any way, thanks for pointing out the other recovery methods btw.
I may have not told you the whooole story
the freaking usb connection wont work.. it hasn´t worked since I got the phone nor it has worked now.. the charge led will never turn on, or will the pc or mac or whatever I plug it into react somehow to it.
anyway, I may have flashed the rom again in stock recovery and this is where things got nasty... It doesnt get past the boot logo, which by the way, was the red M logo, the last time I remember it to boot (even after re re re re re re flashing the CM9 rom!!!!!) it had another one.... weird uh????
now it gets even weirder just read this thing!!!
The phone will get past the red M logo, then the screen goes black, but I can see it is lit...
I waited for a really long time (more than 30 minutes) to see no response..
took out the battery... did not power it on again as i had stuff to do..
I dont know why, but I plugged it into the usb cable.. (I was working on the computer) And the phone turned on!!!!!!! so I guess It is not a busted usb port???
I went on ahead to go to bootloader, and when I plug the cable it is shown as such!!!
sadly, rsd does not recognize the phone as plugged, even though the phone says it is indeed plugged in...
what the hell is wrong????
is there any way I can flash anything if Im stuck after the red M?
this sucks
Oh man...
There are 2 versions of gingerbread kernels, the chinese and the European. As i understand you've flashed the wrong version (CH rom over EU GB kernel or otherwise).
You can try flashing the fixed_sbf which is the CH kernel. Or you can try the below, which is my suggestion:
Download the 2.3.4 EU (UK) SBF flash it through RSDlite and then root, installl bootstrap, bootmenu and then the CM9 EU GB rom.
TWO IMPORTANT THINGS: NEVER INSTALL 2.3.6 VIVO OR PERSONAL ARGENTINA SINCE THEY ARE UNROOTABLE!! And also never use RSDlite when you are running low on battery.
And the MS2 is safe for flashing since it has a locked bootloader so its VERY hard to brick it. Your screen is black because it is in the bootloader mode.
Do not Vivo and Claro 2.3.6 roms
Be careful, VIVO and CLARO roms should not be used.
dafuq!
Nite! my man, I´ve been careful enough to avoid flashing wrong kernels so no, the answer is not there..... sadly...
I cannot interact in NO way with the device via USB, so flashing through RSD is a no-go.........
I do have another phone though.........
so the main prob here is now I do know what to do.. I think I´ve always knew rsd is the way to go.. as for the locked BL, yeah! Ive been into motomodding since the c350.. I really think I do know my way in the motorola mess if you know what I mean, OS may have changed but the system's structure's still the same **** from the old days!...
Basically now my question is this:
what the **** can I do given what I have??? (a non working usb connection, and a phone stuck at Bootloader OR stock Recovery....)
donlloreda said:
Nite! my man, I´ve been careful enough to avoid flashing wrong kernels so no, the answer is not there..... sadly...
I cannot interact in NO way with the device via USB, so flashing through RSD is a no-go.........
Click to expand...
Click to collapse
if power+up arrow and then flashing via rsd don't work for you
you only have two options - first is power+x and then @ which gets you to build in recovery (try to wipe or find an update.zip that can be flashed [if there is any - never did that myslef])
or flashing from your custom recovery if you have one installed
that is all i know (but i only have milestone since tuesday )
good luck anyway
Geez man!!!
So have you tried using another usb cable? Cause i've exhausted my theories about your problem... sorry
every freaking cable
As I got it as a gift, I thought my defy´s charger was "not powerful enought" even though that was absolutely ridiculous...
I went and try to buy the charger but nobody in here seems to know the pnhone so I would be kind of afraid to take it to service
Une petit question
so I think I found a really good site with *loads* of firmwares, branded debranded, official etc...
just to be sure, I tried to flash the update again in stock recovery (pwer + x) but at some point the installer promted some error about signature verification in the whole file.
so my question(s) are:
can I make a file *signed* in any way? if so can you point me out where and how to start?
and just to be on the safe side: If only if only I can grab something that I would be able to flash via stock recovery... I should flash a 2.3.7 based one right? If I do try and flash something lower I would make my problems worst right???
btw, If the phone freezes or sometimes goes through the red M, but there is no led lighting up, can I still go into custom recovery eg. CWM???
About the signing the zip file, yes you can, but i don't know how search in the "Android Development" section. But sbf files cannot be signed... if you discover how you will be the MS2 savior!
In the CWM you can flash just about anything as it can be reversed by flashing sbf's, on the otherside, YOU SHALL NOT FLASH!! Any VIVO or PERSONAL ARGENTINA 2.3.6 rom (sbf) cause they are unrootable. You should do just fine flashing the 2.3.4 UK.
And i don't think you will be capable of entering the CWM if the led doesn't flash cause it's an error that happens before CWM is started. In this cases you will have to flash sbf's, root.... all over again.
thaks man, but......
then the only way give I cannot flash under RSD, is making a "completeupdatewhateverCMorMIUUdafuq.zip" signed so I can load it through stock recovery rite???
remember CWM not availible.. nor USB interface...
will search though on "signing" an update file, yes that 2.3.4 UK you said.. from there I'll just try to make it match my defy
a little discovery!
Source: http://www.londatiga.net/it/how-to-sign-apk-zip-files/
When publishing an application or a custom rom you need to sign the .apk or .zip files with a certificate using a private key. The Android system uses the certificate to identify the author of an application and establish trust relationship between applications.
The classic way of doing this was to use keytool then sign it with jarsigner. In this tutorial i’ll explain an alternative method which is relatively easy to use for most people using a tool called SignApk.jar.
SignApk.jar is a tool included with the Android platform source bundle, you can download it from here.
To use SignApk.jar you have to create a private key with it’s corresponding certificate/public key. To create private/public key pair, you can use Openssl. Openssl is relatively easy to use under unix/linux system. For Windows user, you can download Windows version of Openssl here.
How to create private/public key pair using openssl (windows version)
Download openssl package from google code link.
Extract it anywhere...
Within openssl directory type (using cmd admin mode: ctrl+shift+r then cmd):
- openssl genrsa -out key.pem 1024
- openssl req -new -key key.pem -out request.pem
- openssl x509 -req -days 9999 -in request.pem -signkey key.pem -out certificate.pem
- openssl pkcs8 -topk8 -outform DER -in key.pem -inform PEM -out key.pk8 -nocrypt
{
"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"
}
(dload SignApk.rar)
Extract it anywhere
If you don’t have java installed, download and install it.
Copy certificate.pem and key.pk8 into your extracted SignApk directory
Within SignApk directory type (again using cmd admin mode: ctrl+shift+r then cmd):
java -jar signapk.jar certificate.pem key.pk8 your-app.apk your-signed-app.apk
OR
java -jar signapk.jar certificate.pem key.pk8 your-update.zip your-signed-update.zip
Note:
If you don’t want to create your own public/private key pair, you can use test key included in SignApk.rar.
Sooooo now what the hell do I have to sign???
LOL I'll go for the update I was trying to install at first... if anything goes wrong I'll just take it to service I guess have the USB repaired and RSD the hell out of it.. after all this is a reaaaaly great great phone uh?
maybe I should go first with the UK you suggested man?
About my last post
Hello everyone, so... the signing didnt went well LOL -.-
I guess I have to make the "signature" to match moto's right?
how can I get hold of that signature information? I mean can I download a signed (official) update, which is flashable via stock recovery (is there any???) extract the signature information, and then apply it to my package??????
Ok, now just to put things on the clear side: the instructions in the last post were not written well, but you may already knew that if you read the post.
anyway, as for the problems I ran into:
1: ctrl shift r does not do ****... just typoe cmd on the start menu, right-click it and run as admin.
2: It is EASIER if you copy everything to the root of your drive, and give files and folders short names!
3:
openssl genrsa -out key.pem 1024 <here you may run into an error regarding openss.conf.... just copy openss.conf from openss directory to openss/bin/ directory....
openssl req -new -key key.pem -out request.pem
openssl x509 -req -days 9999 -in request.pem -signkey key.pem -out certificate.pem
openssl pkcs8 -topk8 -outform DER -in key.pem -inform PEM -out key.pk8 -nocrypt
ok from now on it is pretty straightforward, I haven't got time to play around but, There is a step in which the program asks for your Company's name, adress, etc.. maybe if you knew what info is in motorola's signature you can make this fields match??
well I don't know.. but ill try and discover it!
donlloreda said:
I mean can I download a signed (official) update, which is flashable via stock recovery (is there any???) extract the signature information, and then apply it to my package??????
Click to expand...
Click to collapse
Nope and nope. Please learn something about signatures, how they work etc. You can't (obviously) "extract" the private key from the signed file... The signing would be useless then - don't you think?
donlloreda said:
anyway, as for the problems I ran into:
Click to expand...
Click to collapse
Seriously? I think you are not from IT industry, right?
donlloreda said:
ok from now on it is pretty straightforward, I haven't got time to play around but, There is a step in which the program asks for your Company's name, adress, etc.. maybe if you knew what info is in motorola's signature you can make this fields match??
well I don't know.. but ill try and discover it!
Click to expand...
Click to collapse
Stop it. You just wasting your time.
Your real options:
1) Get signed update.zip from Moto (I don't think there is any and I did not saw any)
2) get your USB port fixed and flash it via RSDLite. (if it is HW problem - just fix or get it fixed, otherwise, you are doing something wrong)
RSDLite and SBF flash is your only realistic option.
RSDLite works everytime. You can not break (except for HW issue) your M2 the way, it will not work with RSDLite.

[TUTORIAL] How to change the MODEL ID of the HTC One including video link

MOD EDIT
Seems this guide, if not properly followed will cause a (soft)brick. Also there are more up to date guides.
[how to]change your MID without the eng bootloader
[TOOL] MID change without ENG HBOOT | Aroma GUI
In the interests of all users the guide is hidden, below.
If you wish to follow it go ahead. If you brick your handset, you were warned.
FIRST OF ALL THANKS AND CREDITS GOES TO THE FOLLOWING XDA MEMBERS
@fnoji111​ for working on the ENG HBOOT in the Droid DNA forum
@Argumentation​ for creating the flashable zip that I used for this tuttorial
@daddioj​ for doing the leap of faith and used the ENG HBOOT on his device which lead me to writing this tutorial
NOTE: I created this tutorial because HTC One has different variants. After reading mike1986. article on HTC One variants I realized why I can't install OTA updates with my model ID (MID). Now since we have S-OFF I wanted to get updates from the UK. But since I have a different MID to the UK version, I can't install OTA updates. And this is the only solution I found to work at this time. So I hope it will help people who wants to change their MID​
VIDEO LINK AT THE BOTTOM OF THIS POST​
REQUIREMENTS:
1: S-OFF
2: KNOWLEDGE OF ADB COMMANDS
3: PATIENCE
PLEASE MAKE SURE YOU PAY ATTENTION TO EVERY STEP ON THIS TUTORIAL
***** I WILL NOT BE HELD RESPONSIBLE IF YOU BRICK YOUR PHONE*****​
STEP 1:
Make sure you don't have HTC Sync Manager installed, if you do uninstall it!! Also make sure you have HTC drivers installed!
Step 2:
Go here http://forum.xda-developers.com/showpost.php?p=38180376&postcount=6 and download the Argumentation's zip file
Step 3:
After downloading the PL83IMG.zip you will need to edit the android-info-txt inside. Please see sample picture below:
{
"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"
}
Step 4:
Now you have to place the zip file in C:\Android SDK\sdk\platform-tools folder. I know some people don't have the same directory as I have so this is just an example. Just make sure you place in the platform-tools folder.
Step 5:
Now connect your HTC One (MAKE SURE YOUR DEVICE HAS PLENTY OF CHARGE) to your PC and start a command prompt in the "platform-tools" folder. The quickest way to do this is (see picture below):
Step 6:
When you start your command prompt follow the steps in the picture below. PLEASE BE PATIENT!! After flashing the ENG HBOOT your HTC One will not boot up but you'll just get a gray spotted screen. Your device is not bricked. You can still use adb commands to write the model ID and CID even with a gray screen. WHEN REBOOTING HOLD DOWN POWER BUTTON FOR A FEW SECONDS. You might have to press and hold power button and volume down button when rebooting your phone.
NOTE: When you run the RUU and it says "waiting for bootloader" you will need to restart your phone manually by holding down the power button for a few seconds until it reboots. EACH TIME (does it twice) the RUU says "WAITING FOR BOOTLOADER" you will need to restart the phone manually​
You will not lose S-OFF and still have unlocked bootloader. I suggest that backup all important stuff before doing this I hope it helps.
If the mods feels that this doesn't belong here, please feel free to remove it. Thanks.
Here's a short video that shows how I changed my MID (model ID) on my HTC One
Just a side note: better to edit all kind of text with notepad++.
1) It formats text better (not just one single line)
2) It keeps Unix coding if needed
EDIT 05.12.2013 by the request of user @alray
THIS METHOD WILL NOT WORK USING WINDOWS 8.1
After flashing ENG hboot, Windows 8.1 won't detect the device and fastboot won't work, so you can't change MID and execute the RUU. (win 8.1 drivers issue).
I'll give this a go shortly
The warning on step six makes no sense
Does it automatically reboot after flashing the zip or what
Sent from my HTC One using xda app-developers app
tyler1234567 said:
The warning on step six makes no sense
Does it automatically reboot after flashing the zip or what
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Which warning? Like it states in the last picture when you flash the ENG HBOOT it will get stuck at 3/4 of a way in the status bar. You will need to restart the phone yourself. Then you will get a gray screen and won't be able to see anything. You might think it's bricked but it's not. You just have to proceed with adb command to write the MID and then another adb command to write the CID.
Once you have changed the MID and CID. You may have to reboot your phone and then run the RUU even when it's only a gray screen you see. The RUU will flash back the proper HBOOT and you will see the RUU screen (black screen with HTC logo). Just be patient and wait until the RUU is finished its operation. And that is it.
I will make a video when I get home to assure people that this mod works.
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
shadowboy23 said:
Which warning? Like it states in the last picture when you flash the ENG HBOOT it will get stuck at 3/4 of a way in the status bar. You will need to restart the phone yourself. Then you will get a gray screen and won't be able to see anything. You might think it's bricked but it's not. You just have to proceed with adb command to write the MID and then another adb command to write the CID.
Once you have changed the MID and CID. You may have to reboot your phone and then run the RUU even when it's only a gray screen you see. The RUU will flash back the proper HBOOT and you will see the RUU screen (black screen with HTC logo). Just be patient and wait until the RUU is finished its operation. And that is it.
I will make a video when I get home to assure people that this mod works.
Click to expand...
Click to collapse
Oh ok I got ya. Didn't see that before.
Xstop said:
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
Click to expand...
Click to collapse
If it doesn't belong here then the mods can delete that is fine by me.
EDIT:
Just sent a message to one mod so he can delete this thread if it doesn't belong here.
thank you very much it worked like a charm just changed a tmous mid so far so good waiting to install ota
Xstop said:
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
Click to expand...
Click to collapse
False. How is this not developement. And if this isn't developement then neither is the cid thread, or all the stock rom threads.
shadowboy23 said:
If it doesn't belong here then the mods can delete that is fine by me.
Click to expand...
Click to collapse
No harm, just easier to follow one thread since I am interested in this.
I converted my ATT One to the Dev Edition (hoping that nothing ATT is on m phone now except service), easy since both have the same MID but will be doing this for the PN0710000 soon.
Thank you for the tutorial. :good:
so to make sure i just put the same info from the YOUR text file picture in the one i downloaded ?
CheesyNutz said:
so to make sure i just put the same info from the YOUR text file picture in the one i downloaded ?
Click to expand...
Click to collapse
Which one? Do you mean the "android-info-txt"? If that's what you meant then you have to put in your current model ID, CID and ROM version..If it's the same as mine then you just copy what is written in the first picture. Just remember that Argumentation's zip file is intended for Droi DNA but all you have to edit id the "android-info-txt" and you don't have to touch the HBOOT.nb0.
A video lesson would be perfect
Tried to do something, but adb is not for me, I guess...
It would be perfect to change from carrier to free uk version..
darenas said:
A video lesson would be perfect
Click to expand...
Click to collapse
Uploading now, will post it in the OP when finished. The video is not a tutorial of some sort but more of a guide. It just shows you the process of actually flashing the ENG HBOOT and what I typed using adb/fastboot commands.
shadowboy23 said:
Uploading now, will post it in the OP when finished. The video is not a tutorial of some sort but more of a guide. It just shows you the process of actually flashing the ENG HBOOT and what I typed using adb/fastboot commands.
Click to expand...
Click to collapse
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly...
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
darenas said:
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly...
Click to expand...
Click to collapse
I see already.
darenas said:
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly..
Click to expand...
Click to collapse
Well my phone has S-OFF and have a unlocked bootloader. S-OFF is a MUST! You will see in the video very clearly what I type in adb/fastboot so I'm pretty sure people can work it out.
Video link is up! It is at the bottom of the OP. I hope it helps people.
Done with OTA :thumbup:
Sent from my HTC One using Tapatalk 2

[Script] AAHK2 - Root, Debrand, SIM Unlock, S-OFF, SuperCID & Custom Recovery

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
{
"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"
}
For HTCDEV unlocked devices :
Phiber2000 said:
Unlocked devices via HTCdev need to be prepared via Option 'h' in main menu.
This will do the downgrade too.
Click to expand...
Click to collapse
As you know, the AAHK has expired and is no longer being developed by the author and there is no official support more!
For this reason, there is now Phiber's 2000 AAHK2, which has already grown according to your wishes and will continue to grow.
The original script was adapted, bugs were fixed, and unnecessary things were removed and slightly the HBOOT was modified.This should also work with Unlocked DHDs by HTCDEV.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
​​​​
The Requirements:
-PC with Windows XP, Windows 7 or (Windows 8)
-Charged battery at least 75%
-Original HTC USB Cable
-Make sure that the USB cable and the USB port of your phone and PC are in order (loose contact)
-Use USB2.0 port on the back of a PC ( Don't use an USB 3.0 port or USB Hub )
-If you use a laptop please charge the battery and use the Charger.
- original ROM
Original boot image ( this is not the HBOOT)
original Recovery
Formatted SD card (AFAT32 4KB sector size)from one of the following brands:
Samsung
SanDisk
Patriot Memory
ADATA
CAUTION: If you use an incompatible SD card, the HBOOT will not working. Android also now no longer boots. This fix is expensive and risky!
Among others the following brands lead to a soft-brick: Agfa, Hama, Trascend, No Name
-Enable USB-DEBUGGING : Settings » Applications » Development » USB debugging
-Connection Type "Charge Only": Settings » Connect to PC » Default connection type » Charge only
-HBoot-Status: *** LOCKED *** or *** LOCKED (OOW) *** or *** RELOCKED *** , or without lock status displayed
When the mode of the bootloader is "ENG S-OFF", the LOCK status does NOT play a role!​
Instructions:
Install HTC Drivers v4.0.1.001
Extrackt AAHK2
Start The script with Administrator Rights (aahk2.cmd)
In the main menu "1" and confirm.
Follow the instructions on the PC strictly.
If a downgrade was necessary, the procedure must be repeated. (If you dont know you have to downgrade or not, use the script it will tell you if you need it or not)
Flash the current, (modified by Phiber2000) HTC image to prevent later problems with GPS/WiFi and sound (see FAQ).
Optional: Finally, copy a Custom ROM on the SD card and flash in recovery.
​Downloads:
HTC Driver v4.0.1.001(only if you had'nt installed already driver)
AAHK2 v2.15 - Mirror
HTC WWE 3.12.405.1 with ROOT - GPS FIX(Radio: 12.65.60.29/26.14.04.28 M) (HBoot-Image) - Mirror
Required RUU images are requested by the script: (In original Thread are more mirrors)
PD98IMG DOWNLOAD LINKS
MEGA:
PD98IMG-GB1.zip
PD98IMG-GB2.zip
PD98IMG-GB3.zip
PD98IMG-GB4.zip
PD98IMG-GB5.zip
PD98IMG-GB6.zip
PD98IMG-GB7.zip
PD98IMG-GB8.zip
PD98IMG-GB9.zip
FAQ:
How do I get into the HBOOT loader and which version do I have?
-Disable Fast boot: Settings »Power» Fast boot
-Switch off you phone
-Hold "Volume Down" and "Power" button
-Once the HBOOT loader appears, release the keys
-In the upper part of green written is now available the relevant information:
-0(evtl. rosarote Zeile)Lock-Status
1 ACE PVT...HBoot-Loader Modus & Security Flag
2 HBoot-...HBoot-Loader Version
3 MICROP-...not relevant
4 TOUCH PANEL-...not relevant
5 RADIO-...RADIO-Image Version
6 ...not relevant
How do I get to FASTBOOT mode?
-Start HBOOT loader (see above)
- Navigate with the volume keys to "FASTBOOT"
-Confirm by pressing the Power button
Which CID I have ?
-Start FASTBOOT mode (see above)
-On the PC, open existing Android SDK in CMD
-Type "fastboot getvar all"
-In the line "INFOcidnum ..." is now your current CID. (8 digits)
CAUTION: Apps like CID GETTER don't work properly. Because the App asks the Build.Prop and everybody could change the build.prop.
How do I install after successfully rooting the latest ROM from HTC(modified by Phiber)? (This also fixes problems with GPS/Wifi/Soumd on custom ROMs!)
-Unzip the "RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.6 0.29_26.14.04.28_M_release_225512_rooted.zip"
-Copy the "PD98IMG.zip" as a single file on the SD card
-Start HBOOT loader and wait few seconds
-Confirm query with "Volume Up"
-After successfully flashing confirm the query with "Power"
-Remove the SD card
-Let android boot
-Insert SD card
-Delete the "PD98IMG.zip" from the SD card
Credits:
Hyuh
attn1
shad0wf0x
Anthony1s
Revskills
Genepoole
Phiber2000
Donation:PAYPAL LINK
If you want to help Phiber2000 to continue his work please donate to him ! The support takes also much time on Android-Hilfe.de
What to do next?
Read some FAQs and sticky Threads
Update the Recovery
Make a Nandroid/Backup
Install a Custom Rom {DHD Development List: ROMs, Kernels, and More}
Great but the download link i would mirror as it currently stands there is no free download slots at all so no one can download the file. Just a heads up. Use Mega if possible.
Yep but i think Phiber2000 dont wants it. So we cant mirror it.
Well Phiber2000 will find easily that people will not download the file then. Putting it on a host that has no free download slots from time to time where there is something like Mega where there is no free user slot limit is stupid. Its upto the OP all i was doing was stating a issue. I don't need AHHK i have my own way of doing the same thing from work i have done with a fellow member on here.
Ok i will ask Phiber2000
"I don't need AHHK i have my own way of doing the same thing from work i have done with a fellow member on here. "
I am interested in your work. Could tell me something more (PN)?
Its basically like AAHK using the same source but was scripted a different way. It used the same files but had more options on the recovery.img's and was also a two batch file system.
Only Difference was the Hboot after says AHHK and OP's just says Unlocked.
I asked Phiber and He said that he doesnt want mirrors. Nobody is forced to download AAHK2. If somebody is feeling sick because oft the download speed then its his personal problem.
3498BoyZ said:
I asked Phiber and He said that he doesnt want mirrors. Nobody is forced to download AAHK2. If somebody is feeling sick because oft the download speed then its his personal problem.
Click to expand...
Click to collapse
you can't even get to the part where you download it.that's a 100% chance that it won't be used.
Which is what i said but everyone to there own.
Yup, can't download, therefore I find this thread useless...
ilans93 said:
Yup, can't download, therefore I find this thread useless...
Click to expand...
Click to collapse
No free slots for free users! Hmm.. mods pls close this thread lol.
On the serious note, for someone who really really want to s-off their dhd, just use aahk. Even though it is no longer supported, if you really knows what you are doing, s-off is easily achieved. The documentation is PERFECT and all the FAQ is provided. Although the file is no longer in attn1 server, you can still download it from this thread:
http://forum.xda-developers.com/showthread.php?t=2193681 (READ THIS THOROUGHLY)
For someone who actually not confident to do this but still want to try custom rom, unlocking bootloader will be a better choice. So, ask yourself what do you really want and how is your comprehension skills. :cyclops:
Why are here all against the DL Link. If there arent any Slots then just wait. You could be some more thankful
Gesendet von meinem HTC One X mit Tapatalk 2
Because we can't use it... If the dev would make a mirror, then we would be thankful. Here, it's all about sharing.
Sent from my Desire HD using xda app-developers app
If Phiber2000 dont want mirror then i cant uplaod it on a other site
You have just wait some minutes/hours/days then you can download it.
You and I have to respect Phibers descion
-----------------------------------------------------------------------
yumm91 said:
No free slots for free users! Hmm.. mods pls close this thread lol.
On the serious note, for someone who really really want to s-off their dhd, just use aahk. Even though it is no longer supported, if you really knows what you are doing, s-off is easily achieved. The documentation is PERFECT and all the FAQ is provided. Although the file is no longer in attn1 server, you can still download it from this thread:
http://forum.xda-developers.com/showthread.php?t=2193681 (READ THIS THOROUGHLY)
For someone who actually not confident to do this but still want to try custom rom, unlocking bootloader will be a better choice. So, ask yourself what do you really want and how is your comprehension skills. :cyclops:
Click to expand...
Click to collapse
AAHK destroyed my friends DHD!
AAHK is only for skilled people!
AAHK2 is for Noobs and skilled people AND IT WILL NOT BRICK YOUR DEVICE
EDIT: THE FILES WERE MIRRORED
I was asked to test the free download links on this.
I was begining to think it was true that there are actually no Free download slots. I tried many times over several minutes and every time it said no free download slots. BUT after some minutes of clicking the "return to download link" it did actually give me free slots for all the downloads.
Not ideal, but it does seem possible to get a free download.
Mike
Thnks and as I said the files were mirrored to uploaded because of the problem with share-online
aahk was also made for noobs, but people were too dumb to read the freaking manual. that's mostly the reason why attn1 closed the door for aahk. the aahk wouldn't brick your device unless there was some human error involved.
also if anyone has the file i can mirror it.
Sent from my S4 GT-I9505
pitastrudl said:
aahk was also made for noobs, but people were too dumb to read the freaking manual. that's mostly the reason why attn1 closed the door for aahk. the aahk wouldn't brick your device unless there was some human error involved.
also if anyone has the file i can mirror it.
Sent from my S4 GT-I9505
Click to expand...
Click to collapse
I have finally managed to get the file and I could also mirror it, but the dev said that we can't mirror it...
---------- Post added at 10:45 PM ---------- Previous post was at 10:22 PM ----------
Just to be sure... @3498BoyZ Am I supposed to download all 9 PD98IMGx.zip, unzip them and zip them back together as one, or am I supposed to download only one? -that's a bit unclear to me...
[/COLOR]Just to be sure... @3498BoyZ Am I supposed to download all 9 PD98IMGx.zip, unzip them and zip them back together as one, or am I supposed to download only one? -that's a bit unclear to me...
Click to expand...
Click to collapse
No just Start then aahk2.cmd and follow the points. It will tell you which file From the 9 you will need
[email protected] from my Mobile [email protected]!

Resources