So I lost my galaxy s symbol that shows up when booting your vibrant on,so now that part of the boot up is just blank.
Does anyone know how to replace it with something else? I heard you can replace it with roms or zips or something?
the boot sequence on the vibrant is two .qmg files. The are located on /system/media and they are called bootsamsung.qmg and bootsamsungloop.qmg. just replace those two files and you should get it back. you can grab them from one of the many threads regarding "replacing boot and shutdown sequence"
How about you look at the top of the page and read the sticky
http://forum.xda-developers.com/showthread.php?t=732458
lqaddict said:
How about you look at the top of the page and read the sticky
http://forum.xda-developers.com/showthread.php?t=732458
Click to expand...
Click to collapse
I just flashed the Vibrant boot screen. Didn't work - the boot sound occurs but no image.
I'll try the other one and see what happens.
EDIT: Same thing. Got sound but no image.
strictlyrude27 said:
I just flashed the Vibrant boot screen. Didn't work - the boot sound occurs but no image.
I'll try the other one and see what happens.
EDIT: Same thing. Got sound but no image.
Click to expand...
Click to collapse
your not op?
Ill give it a shot and keep you posted. It looks as though I am not the only one with this issue. If anyone gets it to work before I do,please post how you did it. Thank you.
im facing the same thing here.. cant get the boot animation and cant login to google account anymore.. what a day..
Same thing happened on mine. Those files must get deleted somehow on that operation which is odd.
Sent from my SGH-T959 using XDA App
Well I tried it,but still no luck. Can anyone help?
Can somebody please tell me why my yesterday's post was deleted? I was asking for help like the others who faced the same problem and I wanted to bring the topic back to attention. Any comments from the admins??
marshallrockstarr said:
Can somebody please tell me why my yesterday's post was deleted? I was asking for help like the others who faced the same problem and I wanted to bring the topic back to attention. Any comments from the admins??
Click to expand...
Click to collapse
you didn't look very hard
http://forum.xda-developers.com/announcement.php?f=747
Sorry for not having looked thoroughly enough, I seem to have been too worried about my phone. Won't happen again.
Related
I recently used Odin to flash Lidroid's 2.5.0 2.3 ROM, now my phone says "Galaxy S GT - I9000" then Vibrant when it first boots up.
AND YES I have gone back straight to stock. Several times..
I was just wondering if anyone knows how to fully get rid of that?
SOLVED!
mugenfiji0327 said:
Actually there is a way to get rid of it and I'm the one that created the thread that was asking about it. Give me a couple of minutes and I'll find the odin files I used to get rid of it.
EDIT: Here are the files I used now remember, use the pit,pda and uncheck repartion.
PDA:http://dl.dropbox.com/u/23420259/Eugene_JK2_Froyo.tar.md5
PIT:http://dl.dropbox.com/u/23420259/s1_odin_20100512.pit
Also when this boots for the first time it's going to go straight into recovery and error out, that's okay just hit reboot system now and then flash back to stock 2.1 through odin. From stock 2.1 you can flash whatever you want and you will be rid of that ugly ass GT-i9000 bootup screen. One more thing please make sure you uncheck repartition because it will brick your phone if you don't.
Click to expand...
Click to collapse
This actually worked work me it got rid of the "Galaxy S GT - I9000" boot logo from coming before the Vibrant logo. Now ONLY my Vibrant logo comes up.
I want to personally thank, mugenfiji0327, he was the only one who actually posted something of help. Thank you!
EDIT this also fixed my problems flashing the newest CM7 ROMs I was getting baseband unknown and it made the ROM pretty much useless to me. Well if you are having those troubles maybe this came become of great help to you!
Congratulations, you've an i9000 bootloader. As for the boot screen, well you can't get rid of it as far as I know, you might end up losing it after a couple of flashes though.
That Rom is ported from I9000 framework, so it has the 9000 bootloader, the animation is embedded in that part of the code. I know there was a thread that was trying to figure out how to change that or remove. But, I am pretty sure they never did figure out how to do that
Actually there is a way to get rid of it and I'm the one that created the thread that was asking about it. Give me a couple of minutes and I'll find the odin files I used to get rid of it.
EDIT: Here are the files I used now remember, use the pit,pda and uncheck repartion.
PDA:http://dl.dropbox.com/u/23420259/Eugene_JK2_Froyo.tar.md5
PIT:http://dl.dropbox.com/u/23420259/s1_odin_20100512.pit
Also when this boots for the first time it's going to go straight into recovery and error out, that's okay just hit reboot system now and then flash back to stock 2.1 through odin. From stock 2.1 you can flash whatever you want and you will be rid of that ugly ass GT-i9000 bootup screen. One more thing please make sure you uncheck repartition because it will brick your phone if you don't.
Abu-7abash said:
Congratulations, you've an i9000 bootloader. As for the boot screen, well you can't get rid of it as far as I know, you might end up losing it after a couple of flashes though.
Click to expand...
Click to collapse
You can't just tell somebody they can't get rid of it. Especially when you don't know. There's always a way to do something when it comes to the software. Don't be so negative.
Why would you want to get rid of it, if you do you will experience rainbows on boot, and the only reason people do not flash it is because it can brick, but it did not brick you so no need to get rid of it.
mugenfiji0327 said:
You can't just tell somebody they can't get rid of it. Especially when you don't know. There's always a way to do something when it comes to the software. Don't be so negative.
Click to expand...
Click to collapse
Had you actually read my post you would have come across the two parts where I specifically say "as far as I know" and "you might lose it after a couple of flashes". If anything you're the negative looking for just that to pounce on.
ali1276 said:
Why would you want to get rid of it, if you do you will experience rainbows on boot, and the only reason people do not flash it is because it can brick, but it did not brick you so no need to get rid of it.
Click to expand...
Click to collapse
You will not experience rainbows on boot after getting rid of these bootloaders. Are you serious with that statement? Did you not read what I posted ? I have done the steps that I have posted to get rid of those bootloaders and I can say with 100% confidence that 1. This guy that I quoted has absolutely no idea what he is talking about and 2. IT DOES NOT CAUSE YOU TO HAVE RAINBOWS ON BOOT. People want to get rid of it because it's annoying and ugly.
Abu-7abash said:
Had you actually read my post you would have come across the two parts where I specifically say "as far as I know" and "you might lose it after a couple of flashes". If anything you're the negative looking for just that to pounce on.
Click to expand...
Click to collapse
I'm not looking to pounce on anyone or anything,but coming across NEGATIVELY like you did saying that there is no way that he can get rid of it is rediculous. Especially when you have no idea and you're just guessing. My point is your post wasn't helpful at all, IT WAS NEGATIVE. Anyway OP you should let us know if what I posted helped you, so that if it didn't someone else might be able to.
mugenfiji0327 said:
You will not experience rainbows on boot after getting rid of these bootloaders. Are you serious with that statement? Did you not read what I posted ? I have done the steps that I have posted to get rid of those bootloaders and I can say with 100% confidence that 1. This guy that I quoted has absolutely no idea what he is talking about and 2. IT DOES NOT CAUSE YOU TO HAVE RAINBOWS ON BOOT. People want to get rid of it because it's annoying and ugly.
Click to expand...
Click to collapse
Actually, I do know what I am talking about, he said he was on lidroid which is GINGERBREAD, and on gingerbread if you have the regular vibrant bootloaders it will cause you to have rainbows. You should probably take time to understand a statement before you go shouting.
Sent from my GT-I9000 using XDA App
mugenfiji0327 said:
I'm not looking to pounce on anyone or anything,but coming across NEGATIVELY like you did saying that there is no way that he can get rid of it is rediculous. Especially when you have no idea and you're just guessing. My point is your post wasn't helpful at all, IT WAS NEGATIVE. Anyway OP you should let us know if what I posted helped you, so that if it didn't someone else might be able to.
Click to expand...
Click to collapse
Didn't realise we're in the Amazing Race For The Most Helpful XDA member here. My apologies sir.
And for the record, if anything, you're waaaaaaaay more negative than you rate other people to be.
Sorry to post back, I currently am trying to do the method mugenfiji0327 came up with on here. Will post in a few if it worked and got rid of the Samsung GT I9000 boot logo.
Problem solved!
Please check the first post for a fix on my issue maybe you too?
according to what i see the file to download and flash is froyo. it will revert back to froyo and this is not a gingerbread rom. this is EUGENE JK2 FROYO.tar. md5
when flashing a and using as a pda it will wipe and restore to FROYO.
this method will not work to load gingerbread.
cheers.
smali26 said:
according to what i see the file to download and flash is froyo. it will revert back to froyo and this is not a gingerbread rom. this is EUGENE JK2 FROYO.tar. md5
when flashing a and using as a pda it will wipe and restore to FROYO.
this method will not work to load gingerbread.
cheers.
Click to expand...
Click to collapse
Yes, I am well aware of this. But my original question was to get rid of the Samsung IT - 9000 boot screen before my Vibrant logo appeared. It works. After I flashed this I flashed stock Odin, Rooted, and running CM7, again. Without the boot screen of the IT - 9000
IDK what's up with it. It's made out of 15 PNGs and the desc.txt file but for some reason I get a black screen.
Can someone point me in the right direction?
The permissions are the same as the one that's in Viper's Rom.
unzip COLDH33t.zip and put the zip(Sprint_bootanimation inside in /system/customize/resource )using root explorer or adb
let me if you have any problems
Deleted
1010101
My rice krispies told me what to say
No dice, still get a black screen.
ColdH33t said:
No dice, still get a black screen.
Click to expand...
Click to collapse
have you try any others and do they work?
i'll mess around with it and see if i can fix it and i'll post it up later.
edit: try this one and let me know(same rules as the first one)
this may seem like dumb question, but did you change the perms? bootanim is rwxrr or chmod 744, same with downanim. hope this helps.
I'm having the same issue. I am new to android and I am thinking its a id10T error
Any advice on what i did wrong?
mrloserpunk said:
I'm having the same issue. I am new to android and I am thinking its a id10T error
Any advice on what i did wrong?
Click to expand...
Click to collapse
try this
let me know if you have any problems
dased14 said:
try this
let me know if you have any problems
Click to expand...
Click to collapse
Dased14,
I totally botched this upload I put a working down animation up instead of my own boot animation. Do you mind looking at this one?
i dont know if this is in the correct section, but i REALLY need someones help. basically i rooted my friends phone, installed cwm recovery, and then i went to test cwm recovery to see if it was working ok,( i dont have the optimus v so im not too familiar with it) any ways, i couldnt figure which button was used to select an option in cwm. so i figured something went wrong when i installed cwm, i basically gave up and just did a factory resest from within the stock rom(not in cwm) forgetting you need stock recovery to do this. now it wont go to anything BUT the cwm recovery screen, i figured out the camera button is the select button, but i tried flashing a few roms via cwm, and when i reboot the phone it just goes straight to cwm recovery everytime..some one please help, i dont wanna buy him a new phone, im pretty sure this is fixable. if you can help, a big thanks from me
Have ya tried this...
http://forum.xda-developers.com/showthread.php?p=14028102
I had to do something similar when I first started customizing my phone. Good luck!
~Azrael's Kiss~
Yyou could also try this as it's a little easier...
http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/97470-how-fix-most-boot-loop-issues-caused-factory-reset.html
AzraelsKiss said:
Have ya tried this...
http://forum.xda-developers.com/showthread.php?p=14028102
I had to do something similar when I first started customizing my phone. Good luck!
~Azrael's Kiss~
Click to expand...
Click to collapse
thank you!!! worked perfectly!!now why couldnt i find that!? haha this thread can be removed now
it won't be removed most likely, but you can edit the title to say [SOLVED] at the beginning so it's clear.
bigsupersquid said:
it won't be removed most likely, but you can edit the title to say [SOLVED] at the beginning so it's clear.
Click to expand...
Click to collapse
alright, thank you
bigsupersquid said:
Yyou could also try this as it's a little easier...
http://forums.androidcentral.com/op...st-boot-loop-issues-caused-factory-reset.html
Click to expand...
Click to collapse
lol... I came back to post that solution in case the one I posted didn't work. Guess ya beat me to it. lol
Sk8... Glad ya got out of the boot loop. Have a good one!
~Azrael's Kiss~
I was trying to return to stock using Heimdall. It failed for some reason. Whenever I have tried to use it it always says it failed but this time it went further then usual but the end result was a fail. I think it just repartitioned but I'm not sure. Anyways the only thing it would do is boot into cwm and download mode. So I restored a backup a previously made. Same thing it only booted into download mode and cwm. So I went and tried to flash through odin. Everything worked fine and still the same thing. So then I followed the unbrick thread on XDA and flashed the file and everything finished and said successful but my device would not boot up at all. Doing a little more research it seems that the unbrick method was for 5.0 devices only which I don't know why it isn't placed in plain sight for everyone to see but anyways now I have a dead device. Has anyone had any success with fixing this problem?
Can someone please help me
fresh85 said:
Can someone please help me
Click to expand...
Click to collapse
Ok so:
1. This isn't even talking about development so why are you putting it into dev section?
2. Have you tried a jig to get you back into download mode?
zaclimon said:
Ok so:
1. This isn't even talking about development so why are you putting it into dev section?
2. Have you tried a jig to get you back into download mode?
Click to expand...
Click to collapse
I posted here because I have learned that only here is where people respond but anyways yes I have tried a jig and nothing happens.
fresh85 said:
I posted here because I have learned that only here is where people respond but anyways yes I have tried a jig and nothing happens.
Click to expand...
Click to collapse
Wrong attitude, man. XDA is a free service and you are soliciting unpaid help. Follow the forum rules.
Most, if not all, of our Galaxy Player forum developers and contributors pay attention to all threads and you will get an answer from someone who knows.
If not, look in the development forum and find a developer and send a PM.
Don't clutter the wrong forum with your pleas for help, acting like you're the only one with that problem.
fresh85 said:
I posted here because I have learned that only here is where people respond but anyways yes I have tried a jig and nothing happens.
Click to expand...
Click to collapse
And you expect really having an answer here? You are serious right? Please tell me 1 recent thread on general that haven't been replied and then we can see if we never replies. Geez people are never grateful from what I see...
You guys are getting upset for the wrong reason. I have no attitudes and I'm just looking for help. I tried the other forum and didn't get any reply so I moved it to this forum and I am seeing some activity. I didn't know it was a crime. I was asked a question and an answer was given. Don't mistake a straight forward answer for an attitude. Thanks for your input. Now is there a solution for my problem? The SGP is my little nephews and I experimented with it and messed it up. All I want is a point in the right direction.
It might be a kernal issue. Try flashing a kernal for the 4 and see if that works.
Sent from my Chip 1.5 ROM + Entropy512's Kernal Samsung Galaxy Player 5.0 U.S.
fresh85 said:
You guys are getting upset for the wrong reason. I have no attitudes and I'm just looking for help. I tried the other forum and didn't get any reply so I moved it to this forum and I am seeing some activity. I didn't know it was a crime. I was asked a question and an answer was given. Don't mistake a straight forward answer for an attitude. Thanks for your input. Now is there a solution for my problem? The SGP is my little nephews and I experimented with it and messed it up. All I want is a point in the right direction.
Click to expand...
Click to collapse
Alright, let's all take a deep breath and chill. We empathize with you, dude, we really do.
We need to address another XDA rule that you overlooked. (Understandably. No biggie. Not calling you out, just saying.)
When you post on XDA, you need to be as thorough about your problem as possible, so we don't clutter the thread with Q&A.
1. Symptoms of the problem: What works and doesn't?
2. Any reactions to button presses? Lights? Screen? Sound?
3. Any evidence that it's booting?
4. Does your computer register that it's being plugged in?
That'll help you get started. List anything else that might be noteworthy. Someone will help you.
Also, nightfire brings up a good point. Try flashing the stock kernel for your device via ODIN.
EDIT:
What procedure did you go through when you were following the (wrong) un-brick instructions? Because, if your device is totally unresponsive, you've probably got yourself a Galaxy Paper Weight. If it's not something as dire as that, there may still be hope.
Did you attempt to flash a 5.0 bootloader on a 4.0? A wrong kernel flash wouldn't screw up your device as badly as that. You may need to re-partition some things (/efs and PIT, perhaps) and re-flash stock ROM.
But, please, work with us here and be specific about exactly what you did that led up to the current.
Screen doesn't turn on at all and odin doesn't recognize it.
I used this method....."[10/13]Brick Station! Here to solve your brickable needs! BOOTLOADERS AVAILABLE!!!". I'm not even sure anymore why I felt I needed to use that method but before I followed those steps my SGP would only go into download mode and CWM. I flashed roms and kernels using odin and it said pass...reset. I even restored an old backup but no matter what I did it always rebooted back into CWM. I followed the brick station steps but not the un-resurrectable part because my problem wasn't that extreme but after following through with those steps I now have a device that requires the un-resurrectable method but now I know that it's only for the 5.0. When I connect my device to my laptop it makes a sound like there is some life but nothing pops up...turns on or flashes. I even used a usb jig to try and get it to download mode but nothing at all.
Thank you guys for the help.
where are you now
check this thread out it might help---http://forum.xda-developers.com/showthread.php?t=1903252---Good luck
fresh85 said:
I used this method....."[10/13]Brick Station! Here to solve your brickable needs! BOOTLOADERS AVAILABLE!!!". I'm not even sure anymore why I felt I needed to use that method but before I followed those steps my SGP would only go into download mode and CWM. I flashed roms and kernels using odin and it said pass...reset. I even restored an old backup but no matter what I did it always rebooted back into CWM. I followed the brick station steps but not the un-resurrectable part because my problem wasn't that extreme but after following through with those steps I now have a device that requires the un-resurrectable method but now I know that it's only for the 5.0. When I connect my device to my laptop it makes a sound like there is some life but nothing pops up...turns on or flashes. I even used a usb jig to try and get it to download mode but nothing at all.
Thank you guys for the help.
Click to expand...
Click to collapse
I have done the samething. I food get it going. Is this a US model.
Samsung Epic 4G Touch on xda premium
tim1089 said:
I have done the samething. I food get it going. Is this a US model.
Samsung Epic 4G Touch on xda premium
Click to expand...
Click to collapse
Yes it's the U.S model
Have you tried this ?http://forum.xda-developers.com/showthread.php?t=1531850. So what I gather is you can get to the download mode. If you can then you can fix it. The link I posted here is a good place to get everything you need. Use Hemidall method this was the only way to fix it. I had no luck with Odin. If your PC is not seeing your player go into device manager and remove everything under universal USB. after that click on the action menu and scan for new hardware. It will reinstall the usb stuff. reboot PC. Then get the samsung USB drivers install them. Next if you correctly installed hemidall it should work and see your deivice. Read the info ib this link carefully pick the right player. Down load the PIT file for your player. Then in hemidall install the partitions in the correct order as in the instruction. Let me know if this helps or if I can help you more
Made any progress, fresh85?
Higgs_Boson said:
Made any progress, fresh85?
Click to expand...
Click to collapse
No progress with getting my SGP working. I don't think I'm explaining my problem correctly because people are telling me to follow the steps that got me to this point lol but all the help is appreciated.
If you press and hold POWER + VOLUME DOWN for about 10 ~ 15 seconds, do you see a screen with a yellow construction-like sign appear? If so, you are in download mode, and that is a good thing. Try it and let me know.
Nope nothing turns on at all. I dont think its a complete brick yet because i get a beep sound from the computer when i connect it but no signs of life on the device.
Sent from my SGH-T769 using xda app-developers app
Hello XDA!
Alright, I know that this subject has come up a couple of times on these forums and that there is no solution yet. But the last couple of days this has become a sort of personal vendetta kind of thing for me, and I want to see if we can maybe get a little further on this subject.
Bear with me a little bit because I am still quite noobish so things I say might not be true or make any sense.
So, what I am talking about is the removal of the BOOTLOGO, not to be mistaken with the BOOTANIM. I already know how to change the BOOTANIM and changed it to some delicious visuals, so this is not needed.
Furthermore I know that you can change the BOOTLOGO on the american versions of the Galaxy S3 with a simple .zip. This is of course is really awesome and stuff, but sadly I only have an international I9300, so it won't work for me.
So my first idea was to dig into the boot.img and see what I could do to make sure the BOOTLOGO just won't show. So I looked at the init.rc and found the following line:
export ANDROID_BOOTLOGO 1
I thought I had hit jackpot! not to rub any dirt on anyone's face, but I thought, "How could nobody on XDA have found this out????!!?!" So I changed it to:
export ANDROID_BOOTLOGO 0
Installed my ROM with this boot.img in it and waited, and .... still saw a BOOTLOGO, also a BOOTANIM... so.. it didn't work... Also when I pulled the init.rc using Android Commander is still showed the line "export ANDROID_BOOTLOGO 0" but apparently to no avail.
So I had kind of given up... I had read on different threads that the BOOTLOGO image is buried far into the depths of the filesystem that it isn't even changed when you install a rom! So I thought I would give up...
Until..:
A friend of mine had done something horribly wrong with his glass over his proximity sensor, so instead of just changing the glass we decided to do this software wise. I had found this thread where you could re-calibrate the sensor rewriting something in the efs file system. And this worked! quite easily actually.
And suddenly it hit me, it is probably the efs folder where the BOOTLOGO image is stored! So I made a backup of my efs folder and opened that.. (this took more tries, and I'm not sure with which steps I took to do this, but I'm willing to look it up .)
I found a couple of files but only 3 files bigger than 1kb (this is the only thing my windows 8 wants to show) and I think that the file with the image in it will probably be bigger than 1 kb.
So searching google and XDA I learned that if you want to do crazy things with IMEI and unlocking your phone and such you target the file .nv_data.bak, which is one of the bigger files. So I tried opening it with Notepad++ and HxD but I cannot make any sense of it...
The truth is I was hoping to find a .rle in this folder, which I could magically replace with my own BOOTLOGO and that would be it.
Bottom line:
I was hoping that someone could tell me if I am looking in the right direction (the efs folder and the .nv_data.bak file) and maybe even give directions on how to go further on from here to change the BOOTLOGO...
any ideas?
I would really really really like to get this thing done.
Frank
Info:
Phone: Samsung Galaxy S3 International (I9300)
Rom: SuperNexus 3.0 (would like to use SuperNexus 4.0 but I somehow get problems with Android Commander...)
Kernel: no clue (the one that came with SuperNexus)
Install Xposed Installer and search the module called "Xblast Tools" ! It has an option to disable Bootanimation
Andr3y29
Thanks for your reply!
The thing you are talking about seems to be about the boot animation what I referred to as BOOTANIM. This is the animation that shows stuff like Cyanogenmod or something related to android or your carrier.
I'm talking about the BOOTLOGO, which comes before the BOOTANIM. The BOOTLOGO only shows a black screen with white letters saying "SAMSUNG GALAXY SII (I9300)" and this is what I want to remove.
Frank
Bootlogo is contained within the bootloader, this has never been modified for the i9300 as there is no need -the American S3 is very different in many ways.
Sent from my GT-I9300 using Tapatalk
As above and see many identical posts .
boomboomer, thanks!
So, i guess looking in the efs folder is definitely the wrong place.
googling for the bootloader I found the following thread. Here someone is trying to change the bootlogo, and the conclusion seems to be that I need to change the sboot.bin.
So, i guess I'm going to research that!
thanks!
Frank
Ok, I made some progress
I downloaded the I9300 firmware from Sammobile.com and unpacked it and opened up the Sboot.bin. I couldn't open it with any archiving software but I could with HxD (Hexidecimal editor). There was a lot of gibberish but also some normal sentences and filenames, so I thought it looked a lot like a normal folder (or archive) that I just cannot open normally. But I thought that I might find the BOOTLOGO here in hex code.
So I opened up the logo.jpg from the param.bin in HxD and found ".Adobe Photoshop CS4 Windows.2012:04:23 14:30:18" in the header. In sboot.bin I looked for "Adobe Photoshop" and it came up just once. Looking at how the logo.jpg from param.bin looked and how big it was I copied the same from sboot.bin and saved it as a jpg. And it worked! So this is probably the logo that we see when we turn on our phone. (in the attachments)
I thought this would be it, just replace the hex code of the jpg with other jpg code and then flash this sboot.bin... but sadly this didn't work, Odin failed when it came to the sboot.bin. I started thinking that maybe the .bin knows where a file starts, so when I put a bigger or smaller .jpg in the sboot.bin it will mess up.. So I decided to change a few bits, which would make the image slightly more blue, but wouldn't make the file bigger, and it failed to flash... I though that it might be that the jpg is now broken and windows might be doing its best to interpret it but for the sgs3 it needs to be perfect, so I changed the header, turning Photoshop into Photopoop ( ), it failed to flash... Then I started thinking that the .bin file checks itself by making a sum of all its bytes, and if it is different it fails. So instead of making up my own bytes, I exchanged two bytes in the Photoshop string, making it Photohsop. But this still made the flashing fail.
I started thinking it might be HxD that messes up the sboot.bin file, so I tried to first change one byte, saved it, changed that byte back and saved it again. This time it flashed without a problem...
Now I'm kind of at an end, I have no clue how to solve this or how to go further... Does anyone maybe know how to edit sboot.bin, or how it is secured? Maybe the sboot.bin is checked against something else? Or I am doing something really stupid and there might be an easy fix (please please please)?
Kind Regards!
Frank
I think I need to bump this a little,
But does anyone know how the sboot.bin is checked by the sgs3 or odin?
Cheers!
Frank
mad-freaky said:
I think I need to bump this a little,
But does anyone know how the sboot.bin is checked by the sgs3 or odin?
Cheers!
Frank
Click to expand...
Click to collapse
Yes. Samsung do.
Sent from my GT-I9300 using xda app-developers app
The China unicom i9300 is not the same.
wangdaning said:
The China unicom i9300 is not the same.
Click to expand...
Click to collapse
Its funny how this post is not even related to this thread.
Sent from my GT-I9300 using xda app-developers app
Ai, I was afraid of that....
Does anyone else maybe have an idea?
Frank
You are attempting to flog a dead horse, no-one has bothered to decompile the bootloader for the i9300 as there is no point, it isn't locked. Only one American model had a lock, which was modded to enable flashing, nothing else.
Just to change the boot logo is a lot of work, for something that lasts just a few seconds.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
You are attempting to flog a dead horse, no-one has bothered to decompile the bootloader for the i9300 as there is no point, it isn't locked. Only one American model had a lock, which was modded to enable flashing, nothing else.
Just to change the boot logo is a lot of work, for something that lasts just a few seconds.
Click to expand...
Click to collapse
Dear BoomBoomer! Thanks for your reply!
Sorry, I haven't replied in a while, but I looked a bit further into the sboot.bin and downloaded a couple more to see how they are different and are still able to flash. What I found is that the only difference is their build date and series nr. and 4 blocks of 256-byte signature (not sure if signature or checksum or something but I have to call it something..)
So I guess I need to figure out how to decompile these 256-byte signatures and make my own... to become awesome!
Dear BoomBoomer, I tried searching google and xda to find anything about the american model with sboot.bin but I found nothing. Do you maybe know the thread or person that modded the sboot.bin of the american version?
Thanks!
Frank
Nope, sorry.
Sent from my GT-I9300 using Tapatalk
Adding Incentive
Hey guys,
I'm out on a limb here, but do you think I can maybe pay someone to help me with this?
Cheers,
Frank
Please can someone get me the quaraqumus QS-i9300-KK-v2.6 resumable link
Hello guys,
It has been a while since i started this threat but i'm still searching for a way to remove the bootlogo.
Do you guys have any ideas left i can try?
I'm willing to try everything even if there is a risk of bricking the phone.
I have 5 galaxy s3's here and i am willing to risk them to find a way to remove it.
If anyone has a method i can try please let me know.
Thanks!
any updates
mad-freaky said:
Hello guys,
It has been a while since i started this threat but i'm still searching for a way to remove the bootlogo.
Do you guys have any ideas left i can try?
I'm willing to try everything even if there is a risk of bricking the phone.
I have 5 galaxy s3's here and i am willing to risk them to find a way to remove it.
If anyone has a method i can try please let me know.
Thanks!
Click to expand...
Click to collapse
Frank
Did you make any progress on this. i have been looking also
Donal
Wanna do the same!!! But like instatt the Samsung s3 logo this AoKp Unikorn like the Pic attached, and boot animation from Rom Toolbox Bootanim. The bionic animation. But on my phone s3 international rooted i dont get this animation started. Downloaded more animations and installed it turned on Animations in App but dont work !!! What do i have to do ??? Have made animated Files too for bootanimation but dunno how i can turn them on or where i must place them to get them started !!! Please help me !!! Thanks !!!!
Ps:droid-pro.zip should be the bootanimation and aokplogo the vs. Samsung bootlogo, would look very cool thx !!!