Develop Bugs

Boot Screen Flasher 3000 by dom2684 & Octoberriot

THis is a very simple batch file to assist you in flashing a boot screen
it still uses the same files as before its just put together in one section for ease of use as you can see
thanks to xMemphisx for supplying the required files for this to work
{
"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"
}
1.Extract BSF3000 and open the BSF300 Folder
2. Run CreateG1Splash.exe and choose your boot image (320 x 480 PNG for best results)
3. run the bootflash.bat and follow the on screen steps
* Reboot into fastboot
* IF you're on the older spl then u have 2 screens to flash so you're gonna follow step 3 and 4. and reboot
*If you're on the newest spl the you're just going to flash 1 screen by following step 2 and reboot
4. VIOLA!!! u have a new bootscreen with no copying and pasting
Original Boot Screen
http://www.mediafire.com/?wdmuuzhmmnw
BSF3000.zip

I don't get it. What is classified as the "special" SPL, and what is the "other" spl's? Create a list please .
I'm using Haykuro's Danger SPL...I assume that's "special"?

im assuming special is haykuros and other is any other spl

grr...I hate having a Mac! lol
Anyway someone could setup something like this for linux or Mac users. Pretty please.

Yes sorry for any confusion ....haykuros spl is the special spl

Where is it pulling mysplash.rgb565 from? Says mine cannot load it.
Edit: Fixed the problem. I placed the .bat file in my Android SDK Tools folder, intended to work next to ADB. Didn't know you could run the .bat from the extracted zip folder itself.
Problem: Haykuro's SPL only flashes the first screen, the T-Mobile G1 screen, correct?

lukekirstein said:
Where is it pulling mysplash.rgb565 from? Says mine cannot load it.
Click to expand...
Click to collapse
if u created ur own bootscreen it should be pulling it from the folder

Alright. Got everything to work. Might want to flash back to the original G1 screen, because having that first T-Mobile screen is crucial to me.
On a side note, a couple of apps and widgets broke upon rebooting. Some widgets wouldn't load, other apps lost data connections. Ran a fix_permissions, everything works fine now
Curious question, does anyone have the original "T-Mobile G1" boot screen?

lukekirstein said:
Alright. Got everything to work. Might want to flash back to the original G1 screen, because having that first T-Mobile screen is crucial to me.
On a side note, a couple of apps and widgets broke upon rebooting. Some widgets wouldn't load, other apps lost data connections. Ran a fix_permissions, everything works fine now
Curious question, does anyone have the original "T-Mobile G1" boot screen?
Click to expand...
Click to collapse
Theres a thread with them. You can check the bootscreen tutorial thread, its in there as well

lukekirstein said:
Alright. Got everything to work. Might want to flash back to the original G1 screen, because having that first T-Mobile screen is crucial to me.
On a side note, a couple of apps and widgets broke upon rebooting. Some widgets wouldn't load, other apps lost data connections. Ran a fix_permissions, everything works fine now
Curious question, does anyone have the original "T-Mobile G1" boot screen?
Click to expand...
Click to collapse
what build are u on?
original boot screen >>> http://www.mediafire.com/?wdmuuzhmmnw

dom2684 said:
what build are u on?
original boot screen >>> http://www.mediafire.com/?wdmuuzhmmnw
Click to expand...
Click to collapse
In my siggy

i love this its alot easier than b4 IMO

nice work dom. It was quite a bit easier this way. I noticed after flashing the danger spl that i could only change one boot screen. Anyone know why that is? Not super important since the first one only last a couple seconds anyways.

*BUMP YO need some feed back on this

Can this batch file also install a .gif splash screen? I'm wanting the HTC splash with the little android that peeks out.

uansari1 said:
Can this batch file also install a .gif splash screen? I'm wanting the HTC splash with the little android that peeks out.
Click to expand...
Click to collapse
no its only for the primary boot screen

added original boot screen to 1st post

I noticed after flashing the danger spl that i could only change one boot screen. Anyone know why that is?
Click to expand...
Click to collapse
"danger" SPL only has 1 boot screen to flash, there's a thread about it somewhere, think i read it in the old thread somewhere
note about the tool, VERY fast, VERY easy, even a n00b like me could do it. If you have "danger" SPL you will need updated USB drivers, but i'm sure you know that already
The script litterally is, put your image into the folder, run the bat, press 2 <enter> (for special SPL that is)and you're done, really couldn't be simpler if you tried

I'm glad everyone likes it

my adb work find, but for some reason this script stay at wating for device, any input?

New Android Splash screens and Bootanimations (New Splash 15 Aug!)

As some of you have already asked for replacements for the Windows Mobile splash screens, I decided to make a couple.
To install these:
Download the NBH file by clicking the link below the image.
Copy the NBH to SD card, Rename to KAISimg.nbh, Flash by powering on while holding down camera button, same as flashing to nand.
These splash screens will not alter your nand flashed Android in any way, they simply replace the old splash screen.
{
"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"
}
http://rapidshare.com/files/362920041/donut.nbh
http://rapidshare.com/files/362920042/eclair.nbh
http://rapidshare.com/files/363232957/flan.nbh
http://rapidshare.com/files/366368841/droid2.nbh
http://rapidshare.com/files/373128811/newdroid.nbh
Note: the filenames are just names, they don't mean you have to use the donut splash with donut or anything, they are just semi-random names to call them
I used this tutorial to put together these splashes: http://forum.xda-developers.com/showthread.php?t=334907
Please add your own splashes here, then we can keep em in one place
(just decided to include my favourite bootanimation as an update.tar)
http://rapidshare.com/files/363292725/androidupdate.tar
Heres another, this ones all my own work
http://rapidshare.com/files/364249019/matrix.tar
To use this one, just copy to SD card, rename to androidupdate.tar, and.. well update , Enjoy

HERE is my contribution

Thanks loserskater, always liked those ones too, kept meaning to ask you where you got the font from, can see that coming in handy

Hope Poly does not mind me including this here :
polyrhythmic said:
Custom splash screen for Kaiser! (I don't have the files to build this for Vogue or Polaris)
[ Download Here ]
Click to expand...
Click to collapse

Great work Zenity, cheers.

No problem, Kinda feel like I need to give at least something back
I see at least a few of you have downloaded the splashes and bootanimation, please let me know if there are any problems.

I flashed the FLAN.NBH, all runs OK, no problems.

zenity said:
Thanks loserskater, always liked those ones too, kept meaning to ask you where you got the font from, can see that coming in handy
Click to expand...
Click to collapse
I actually made the K S and E myself using gimp. Searched high and low for the actual font but its not released. I thought about changing the S and E to fit the rest of the font better but haven't got around to it.

Did wonder about that, been searching all over the place for that font, lol, but since it's not supposed to be used on anything other than official google andoid logos, I'll just have to use what I have

Beackman said:
I flashed the FLAN.NBH, all runs OK, no problems.
Click to expand...
Click to collapse
Glad you like it

Where is that old funny boot animation from android where the android use to look out of screen? That was for me the best boot animation.

Don't know that one, if you find it please post it here

Ok managed to build a half decent 3D model of the Android.
Added a new bootsplash to post #1

new splash
created this from a file posted at PPCG, nbh file included.

Nice work, y'all

clmartin22 said:
created this from a file posted at PPCG, nbh file included.
Click to expand...
Click to collapse
Yeah... I love so much.
I convert it for Polaris right now
Thanks.
Cheers.

clmartin22 said:
created this from a file posted at PPCG, nbh file included.
Click to expand...
Click to collapse
WOW
thanks!

did you see these http://forum.xda-developers.com/showthread.php?t=624480%29-

Just thought I'd share my latest wallpaper, amazing what fun you can have with a decent 3D model

New bootsplash added

what does this mean?

can anyone tell me why my htc desire is stuck at this screen when i put in the battery?
-- 1 minute later --
well, i can't post a pic since not allowed to link until after 8 posts
it looks like a boot screen with 3 android dudes on the bottom.
any ideas?

Your stuck at the bootloader. Means that there is no boot.img. You've done something to it. Just flash a rom and it'll be fine. Don't forget to wipe data.

ok, thats positive news so far
the things is, i think its water damage but not much water at all really. just a bit from snowing while skiing.
the power and volume buttons do not seem to respond AND the ohone turns on by itself when i insert the battery.
is it still just a case of 'flash a ROM'? or is there more?

oh, and here is the image..... finally,
{
"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"
}

You don't have root or a custom recovery, correct? You just want to go back to the stock Froyo?

I think if the power buttons don't work it may be a bit of a problem selecting options in that menu, since the power button works as "select" in that menu.
I think you could boot to recovery using command prompt, but I am not 100% sure about that.
Also, are you rooted? Do you have a custom recovery installed?

What is 'Kali CM7 Apps2SD'? Is that just another name for S2E?

sonoftobit said:
What is 'Kali CM7 Apps2SD'? Is that just another name for S2E?
Click to expand...
Click to collapse
--- confusion ensues ---

my phone is NOT rooted NOR does it have anything custom.
i would simply like to go back to the original v2.2 that i had before this happened.
thanks for all suggestions and help

liquidmonkey said:
my phone is NOT rooted NOR does it have anything custom.
i would simply like to go back to the original v2.2 that i had before this happened.
thanks for all suggestions and help
Click to expand...
Click to collapse
Do you have a note of which rom was installed in your device? Is it carrier locked? Branded?

Select the newest RUU that fits your phone & carrier from http://shipped-roms.com/shipped/Bravo/. Extract the ROM, rename to PB99IMG.zip, place in root dir of sd-card and reboot. Should do everything else automatically.

don't really follow the whole ROM question?
my phone has android v2.2, is NOT branded, is NOT locked and NO rooting.

and i should add that i am sweden if that matters.

The file you download from shipped roms is an exe file. When you execute the file it will extract a couple of files to your harddrive. Among those is a file named ROM.zip. That's the one you're looking for.
When I extracted it the file was here C:\Users\*User Name*\AppData\Local\Temp\{722DC7D5-7B69-4EBC-B6FB-B63AE38C01DE}\{50F2F878-636A-496F-A7CB-544C067E0C4B}
The ROM on shipped ROMs are all the standard carriers version that are unmodified.

liquidmonkey said:
don't really follow the whole ROM question?
my phone has android v2.2, is NOT branded, is NOT locked and NO rooting.
Click to expand...
Click to collapse
Yeah but there are different versions of 2.2 depending on carriers etc, thats why I was asking!
I *think* any of the ROMS here with RUU at the beginning & WWE in the filename should work. (I am not 100% sure about this, as I have not had an official rom installed for AGES).
You will then have to follow sonoftobit's instructions I think, don't ask me how to extract the ROM though, as I don't know how to do it!
PS sonoftobit - Ignore this liquidmonkey!
If you go to the CM7 nightly thread and go to the 2nd post, Kali has a script for enabling Apps2SD. That is what I am running, tried to use S2E but it screwed things up royally and I had to restore a Nandroid!

Yeah, I had the same problems with S2E. I'm using DarkTremor App2SD now which has worked flawlessly ever since (both Sense Froyo and CM7). Also there's A2SDGUI for DarkTremor now which makes it even better.

StuMcBill said:
PS sonoftobit - Ignore this liquidmonkey!
Click to expand...
Click to collapse
why on earth would you write that?

so check it out!!!
i have had the phone off for a few more days and then put in the battery and BANG, it started up after a little while.
problem was that my battery only lasted 10 seconds so i was not able to fully test things.
then i put the battery in again and i was back where i started, crappy boot screen.
is there something in the phone that keeps memory of the boot screen and then disapates after a day which would explain why it started today.... or?

ZE551ML Bootloader Keeps Rebooting

As the title says, I installed the ASUS Official Unlock tool (and didn't really read it, as you should) and it attempted a boot unlock without SU. The funny thing is, it did exactly what it said it would do and rebooted into the Bootloader. The Bootloader said (and still does) it was a success and that the phone will reboot in 5 seconds. Which is fine, except it's doing that every single time I enter the Bootloader. I can't get it to stop doing that so I can actually do the root and re-do the unlock. The phone still functions perfectly fine otherwise.. any advice? (Yes, I can get it into recovery mode) Hopefully that didn't ban me from OTA.
EDIT: It also turned my boot screen white, and I also tried to use the sideloader, but I already have the latest ASUS firmware so that didn't help. However, in my loader I noticed some weird stuff showing about a MOD_SDUPDATE.ZIP not being found.. I don't know what's that about. It was doing that before I tried to use the sideloader.
{
"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"
}

dunno what exactly happened, but you can do " Using Stock.zip from ASUS site:" from here, that should fix basically everything: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
P.S.: your data won't be lost, however your app ache will be cleared, meaning you'll be logged out everywhere. So if you have some game and no account, that game state will be lost.

So I tried that, first with the ROM that's installed on the phone the .97 version. Then with the original version. It appears to actually install the .97 version, but that does absolutely nothing for the phone and if I try an older version it just tells me it can't flash an older version. Should flashing the same version over-top have taken care of the problem? Doesn't look like it did anything. The boot loader is probably unlocked, but I can't keep it in ADB mode long enough to do anything useful and you can't sideload a recovery to my knowledge.
EDIT: I named the file wrong in my tiredness. I did it again and loaded in recovery...
EDIT2: That did not work.

You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....

ultramag69 said:
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
Click to expand...
Click to collapse
I don't actually know what you mean by that? With the ASUS unlocking tool causing it to reboot in the bootloader improperly or the booting of the file from Recovery?
The phone isn't actually "broken" but now... I can't do anything to it without the use of ADB.. Which blows.
EDIT: Also, can you point me to these threads?

http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.

m3t4lw01f said:
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
Click to expand...
Click to collapse
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.

bewaffled1 said:
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
Click to expand...
Click to collapse
Yep. We're hoping @ASUS_Khang gets a solution from HQ next week to get us back on track!

How to get rid of the "Your device is corrupt message"?

This looks like a pretty hard nut to crack. I don't know exactly what caused it. I was rooted for a few days and was just reflashing Magisk (messing about you could say) when it turned up. Previously, I just had the warning with yellow text which is what everyone gets after unlocking the bootloader. So here goes the overview, please bear with me:
===> I reset the phone by flashing OnePlus5TOxygen_43_OTA_006_all_1712062242_69a5125fb2eb4d87.ZIP (OxgengenOS 4.7.4). <===
Exact steps on how I did that:
1) I flashed the stock recovery image via fastboot ( I got it from Oneplus's website)
2) I booted into the stock recovery I flashed in step 1 and flashed the entire ZIP (the one with the long name above). Probably flashed the recovery twice but yeah.
But no dice. It will absolutely not go away. The zip does not contain any other IMG's apart from boot.img and recovery.img so I can't really flash other partitions like system via fastboot. I CAN flash system via my nandroid backup, and I did, but that still did not help.
Here is the error I got. It's from a google search but it resembles the error on the OPO5T very nicely. So can the experts chime in please?
{
"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"
}

Not used to posting my own answer but maybe this will help someone. You need a full reflash with the Qualcomm tools. OPO support can do this, or anyone with the flashing tool, the correct firmware image, and drivers (the latter being easy to find).
There are tutorials online to do this, the only thing missing is the correct firmware image.
To summarise the requirements:
1) Qualcomm drivers (easy to find)
2) Qualcomm Flash tool MsmDownloadTool V4.0.exe (fairly easy to find)
3) The correct *.ops firmware image (hard to find and you need the password)

Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info

Bradl79 said:
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Click to expand...
Click to collapse
I can tell you its lenght if that helps? That should narrow down the amount of combinations. Unless its different per download link they send.

Yes please that would cut down a lot

Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.

If we already have the opt file someone could just set up a keylogger on their machine and have op support do the remote flash and thus capture the password from them lol

Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
Jeroen1000 said:
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
Click to expand...
Click to collapse
Has any one had any luck with the password? I'm in the same soup as well!

randallstevens said:
Has any one had any luck with the password? I'm in the same soup as well!
Click to expand...
Click to collapse
still going... only on 4th character out of 10 been running for a couple days

Bradl79 said:
still going... only on 4th character out of 10 been running for a couple days
Click to expand...
Click to collapse
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.

randallstevens said:
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
Click to expand...
Click to collapse
It is Bruteforcing meaning I started with 10 characters
1111111111
And it's still trying to decrypt, I am at something aroun
111111gw7&
So it's going one by one going through each character