Database Users

[VIDEO] i9000 Boot Screen Replacement Tutorial

All links pulled due to XDA Request after an XDA member complained I was only out for profits to a moderator on a few products I have. Due to the fact I link to a product or two and a few other things in many videos, I was asked to pull any content relating to this.
I will still be offering all this great material at my website. Just go to google and search for MobileTechVideos.

Video will be fully live any minute...

very helpfull ...even drinking russian Vodka .. i was able to do it !!!

Added link to new boot screen page on my website. Check it out in the bottom of the original post!

Maybe you guys wanna use this one I just made? Looks great on our AMOLED screens

shishir95 said:
Maybe you guys wanna use this one I just made? Looks great on our AMOLED screens
Click to expand...
Click to collapse
Looks great. Care if I add it to my boot screen page on the site?

Go ahead!!

Added it...

Just attempted this and it went terribly wrong
everything was okay until it tried pushing the logo to my sdcard (which failed with "permission denied") - it then said it couldn't copy the file from sdcard because it didn't exist.
I proceeded to unmount the sdcard from the phone and try it again which seemed to work. I shut the phone down and when I attempted to turn it back on it just remained off... I was able to get into download mode with odin 1-click and flash to stock (thank God).
- Serendipity 5.7
- I9000 .rar package
- logo_ATNT.jpg < 20K
was it the unmounting that did the trick? and can I just manually move the file onto /mnt/sdcard/ and edit the .bat file to skip the push?

Worked perfectly for me I love the nexus boot screen with my nexus boot animation Thank you connexion

mdsannihilation said:
Just attempted this and it went terribly wrong
everything was okay until it tried pushing the logo to my sdcard (which failed with "permission denied") - it then said it couldn't copy the file from sdcard because it didn't exist.
I proceeded to unmount the sdcard from the phone and try it again which seemed to work. I shut the phone down and when I attempted to turn it back on it just remained off... I was able to get into download mode with odin 1-click and flash to stock (thank God).
- Serendipity 5.7
- I9000 .rar package
- logo_ATNT.jpg < 20K
was it the unmounting that did the trick? and can I just manually move the file onto /mnt/sdcard/ and edit the .bat file to skip the push?
Click to expand...
Click to collapse
I'm not sure but it sounds like you didn't make sure that busy box was installed. As for not turning back on, I'm surprised at that. I soft bricked a vibrant building the vibrant files and got out of it but that was my fault pulling the usb cable out accidentally before ODIN was done. The answer to your question is yes, you can just flash the param.lfs tar file, verify busy box apk is installed and so is busy box, then just manually move the file. The script is built for simplicity. I'm sorry you had trouble.

connexion2005 said:
I'm not sure but it sounds like you didn't make sure that busy box was installed. As for not turning back on, I'm surprised at that. I soft bricked a vibrant building the vibrant files and got out of it but that was my fault pulling the usb cable out accidentally before ODIN was done. The answer to your question is yes, you can just flash the param.lfs tar file, verify busy box apk is installed and so is busy box, then just manually move the file. The script is built for simplicity. I'm sorry you had trouble.
Click to expand...
Click to collapse
Also, you did let the phone try to boot for a sec right? In some cases when you don't have a boot screen after the flash you won't get a dirty pixel screen but it will be black for the 5-10 seconds it attempts to show you whats there. I just want to make sure you were not prematurely turning the phone off.

connexion2005 said:
Also, you did let the phone try to boot for a sec right? In some cases when you don't have a boot screen after the flash you won't get a dirty pixel screen but it will be black for the 5-10 seconds it attempts to show you whats there. I just want to make sure you were not prematurely turning the phone off.
Click to expand...
Click to collapse
yeah, i attempted to turn back on twice (hold power for about 3-4 seconds, wait about 10) after it seemingly succeeded - I pulled battery in between jic.
the .bat file said busybox install failed because it was already installed... how else can I verify that bb is installed?
I'm going to try again once I get another ROM back on my phone because I really want to get at&t off my phone
thanks for your hard work and responses

this was going to be my boot image if anyone wants to use

mdsannihilation said:
yeah, i attempted to turn back on twice (hold power for about 3-4 seconds, wait about 10) after it seemingly succeeded - I pulled battery in between jic.
the .bat file said busybox install failed because it was already installed... how else can I verify that bb is installed?
I'm going to try again once I get another ROM back on my phone because I really want to get at&t off my phone
thanks for your hard work and responses
Click to expand...
Click to collapse
That will install the application on the phone. But, before you finish the rest of the batch script, you must open the app on the phone and make sure it's installed. It will look and tell you. If it's not click install busybox. When it's done, continue with the batch script. I'd start fresh also btw. Reflash with ODIN on the tar package then launch the script.

AReynante said:
Worked perfectly for me I love the nexus boot screen with my nexus boot animation Thank you connexion
Click to expand...
Click to collapse
Do you mind posting the boot screen?

can you give me a txt document guide? I can open the related web because of internet accessing control, thanks!

TheBassman369 said:
Do you mind posting the boot screen?
Click to expand...
Click to collapse
Yeah, it is in the OP, but I'll post it too. Credit goes to connexion
http://www.mobiletechvideos.com/blog/?page_id=317

AReynante said:
Yeah, it is in the OP, but I'll post it too. Credit goes to connexion
http://www.mobiletechvideos.com/blog/?page_id=317
Click to expand...
Click to collapse
Thanks, but I remembered that AFTER I asked you. I had a slow moment. Lol

TheBassman369 said:
Thanks, but I remembered that AFTER I asked you. I had a slow moment. Lol
Click to expand...
Click to collapse
Hah, no problem, we all do

[Q] Someone please help!!!

ok i recently got a european open to all networks samsung galaxy tab,
now i decided to install a custom rom last night with horrible results, my phone is now stuck on the samsung boot screen and will not load properly,
here are the steps i took that ended me up in this mess,
i installed rom manager from android market,
then installed clockwork mod from inside rom manager, following the exact steps i was given but heres where i think i went wrong,
at some point it asked u back up everything onto an sd card, now i thought i had an sd inside it already but i didnt and thats what i think caused all the trouble,
i backed up all my files anyway onto the internal memory b4 goin into recovery mode, after completely wiping the phone as it saids u shud do, i then proceeded to load the modaco rom that i had installed into the "download" section of my memory and thats where it said the exact following words....
Checking /system...
E: failed to mount /system (invalid argument)
/system may be rfs. checking...
checking /date...
checking /database...
checking /cache...
filesystems need to be converted to ext4.
a backup and restore will now take place.
if anything goes wrong, your backup will be named before-ext4-convert-1297008631. try restoring it incase of error.
E:failed to mount /sdcrard (no such file or directory)
now i've tried restoring it and backing it up but all it repeats is the same thing, i know i messed up but now all i want to know is how can i fix it?
please any help would be much appreciated.

KingofXings said:
ok i recently got a european open to all networks samsung galaxy tab,
now i decided to install a custom rom last night with horrible results, my phone is now stuck on the samsung boot screen and will not load properly,
[..]
now i've tried restoring it and backing it up but all it repeats is the same thing, i know i messed up but now all i want to know is how can i fix it?
please any help would be much appreciated.
Click to expand...
Click to collapse
A brandnew start from scratch with Odin and repartioning with the rom from Rotohammer JMIv1.0 or v2.0 wouldt be my advice. You need the pit-file as well. Can be found on his server.

Heppieboeddah said:
A brandnew start from scratch with Odin and repartioning with the rom from Rotohammer JMIv1.0 or v2.0 wouldt be my advice. You need the pit-file as well. Can be found on his server.
Click to expand...
Click to collapse
ok ive downloaded odin v4.03, downloaded the original samsung firmware version P1000XWJJ3.rar from this website and downloaded the european P1_EUR.pit file also but i'll be honest i'm very new to the android world and dont have a clue what to do from here, how do i repartion the rotohammer rom?
i know i'm gonna sound stupid but if u could please explain it step by step i would be very grateful, thank you

Read the following thread that explains how to flash Rotohammer JMI ROM
http://forum.xda-developers.com/showthread.php?t=939360
Give it a good read and then ask if you have any questions before you start the process again.

KingofXings said:
ok ive downloaded odin v4.03, downloaded the original samsung firmware version P1000XWJJ3.rar from this website and downloaded the european P1_EUR.pit file also but i'll be honest i'm very new to the android world and dont have a clue what to do from here, how do i repartion the rotohammer rom?
i know i'm gonna sound stupid but if u could please explain it step by step i would be very grateful, thank you
Click to expand...
Click to collapse
First extract the P1000XWJJ3.rar. You shouldt be left with a single tar-file?! If so
Well if you have the right files. Start Odin. On the left you see the option 'repartion', tick that box. On the left you see pit. Tick that box and load the pit-file. Tick the box PDA and load the tar.file you extracted.
Start the tablet in download modus and attach it to youre pc. You shouldt see on top left a yellow box. Then just press start in Odin
beware that all on yore tablet will be deleted.
here is a very good guide with pictures.
http://leemn.wordpress.com/2011/01/25/galaxy-tab-flashing-a-new-rom-rotohammer-jme/

Heppieboeddah said:
First extract the P1000XWJJ3.rar. You shouldt be left with a single tar-file?! If so
Well if you have the right files. Start Odin. On the left you see the option 'repartion', tick that box. On the left you see pit. Tick that box and load the pit-file. Tick the box PDA and load the tar.file you extracted.
Start the tablet in download modus and attach it to youre pc. You shouldt see on top left a yellow box. Then just press start in Odin
beware that all on yore tablet will be deleted.
here is a very good guide with pictures.
......ok i followed the steps from above which was to install the Roto JMI Pre-Rooted Firmware v2 it got me pass the boot screen and everything on the tab works except it wont let me make phone calls, everything else works but it picks up no network and when i enter into settings it wont even let me access it?? almost like this is a wifi only rom ive installed??
what do i do from here to get it back to a phone?
Click to expand...
Click to collapse

KingofXings; said:
......ok i followed the steps from above which was to install the Roto JMI Pre-Rooted Firmware v2 it got me pass the boot screen and everything on the tab works except it wont let me make phone calls, everything else works but it picks up no network and when i enter into settings it wont even let me access it?? almost like this is a wifi only rom ive installed??
what do i do from here to get it back to a phone?
Click to expand...
Click to collapse
Ok great. at least you got it working again....
Now you need to flash the baseband-modem that you can find in the download link below. Flash it in Odin. Uncheck repartion. Check 'phone' and load the modemfile you downloaded. Its a tar.file. Leave it as it is. Then press start and the baseband will be installed.
Then you have to set-up the APN from youre telecom-provider and you will be up and running.....
http://forum.xda-developers.com/showpost.php?p=11148313&postcount=129

Heppieboeddah said:
Ok great. at least you got it working again....
Now you need to flash the baseband-modem that you can find in the download link below. Flash it in Odin. Uncheck repartion. Check 'phone' and load the modemfile you downloaded. Its a tar.file. Leave it as it is. Then press start and the baseband will be installed.
Then you have to set-up the APN from youre telecom-provider and you will be up and running.....
ok i downloaded the p100-radio-xxjmf.tar file and followed the instructions u gave but it failed and said this message...
<ID:0/004> set up connection.
<ID:0/004> cant open the serial (COM) port.
OSM All threads completed ( succeeded 0/ failed 1)
i dont understand why it would say that, could it be cos the .tar is xxjmf and the Rom by roto uses jmi? u think u could help? thanks again honestly, you've been a life saver.
Click to expand...
Click to collapse

Ok i just changed the usb ports and it works perfectly, the phone is back online and i didnt even have to fiddle with the apn settings, 3G just works fine,
thank you so much for ur help, i couldnt of done any of this without u, if ur ever around in north west london, u got a drink on me lol

KingofXings said:
Ok i just changed the usb ports and it works perfectly, the phone is back online and i didnt even have to fiddle with the apn settings, 3G just works fine,
thank you so much for ur help, i couldnt of done any of this without u, if ur ever around in north west london, u got a drink on me lol
Click to expand...
Click to collapse
Good to read youre up and running again...
Cheers....

Heppieboeddah said:
Good to read youre up and running again...
Cheers....
Click to expand...
Click to collapse
Hey mate, seems I am in a similar predicament here. Just 2 days back I flashed my Tab to Roto JMI v2 from a stock Asian firmware (DDJK3 I suppose) due to a bad Modaco flash that went really bad. Wiped off my data from god knows what areas. Now I am facing an issue that I am not able to understand or solve.
I was using Titanium Backup to remove a system app without Chuck Norris mode, which meant I had to reboot device and it would delete it OS level and say reboot to system. But once I click on reboot system an Exclamation mark just comes across the screen and NOW I CAN'T BOOT INTO my system. neither to i see the options it was earlier showing me upon Pwer + Vol Key up. The only option left for me is to reflash it using Odin.
Any Ideas mate? Reflashing again and again is not the solution right?
Thanks & Cheers!

sahildeswal said:
Hey mate, seems I am in a similar predicament here. Just 2 days back I flashed my Tab to Roto JMI v2 from a stock Asian firmware (DDJK3 I suppose) due to a bad Modaco flash that went really bad. Wiped off my data from god knows what areas. Now I am facing an issue that I am not able to understand or solve.
I was using Titanium Backup to remove a system app without Chuck Norris mode, which meant I had to reboot device and it would delete it OS level and say reboot to system. But once I click on reboot system an Exclamation mark just comes across the screen and NOW I CAN'T BOOT INTO my system. neither to i see the options it was earlier showing me upon Pwer + Vol Key up. The only option left for me is to reflash it using Odin.
Any Ideas mate? Reflashing again and again is not the solution right?
Thanks & Cheers!
Click to expand...
Click to collapse
Well, first of all. Removing system app ad hoc is not really clever to do. But you cant get into the recovery so you are able to clear cache and do a factory-reset? Volume-up+Power on and holding the volume-upbutton untill you get into the recovery?
If not you have to reflash from scratch with Odin. Use the pit/file and check repartion.

[STOCK ROM]Use for going back to stock before flashing a custom ROM with minimum risk

\\\\\\\\\\\\warning///////////
It seems that phones batch 1010 and newer dont like this method of going back to stock. If you're caught in a boot loop try flashing the official froyo for Captivate. One source can be found here
\\\\\\\\\\\\warning///////////
Disclaimer: Anything you do with the content found in this thread and the content that this thread links to, is your own choice and you are fully responsible for what happens to your phone.
This method is for ATT Captivate ONLY!
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
The purpose of this thread is to give flash addicts/custom ROMs users a more secure way to go back to stock - JF6 - without risking bricking their devices.
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
This package contains NO BOOTLOADERS and NO PARAM.LFS!
Download the package from here
Download Samsung Kies and install it. It will install the latest Samsung drivers.
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot in Download Mode (see below)
Run Odin3 v1.3.exe
Click on the button PDA
Choose JF6_secure.tar.md5
Click start.
Wait and do not unplug cable until it is finished
How to boot in download mode:
There are 3 methods:
Method 1: (ADB) - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons
Plug in the USB cable and continue holding both Volume buttons
Method 3: (JIG)
Link
If moderators believe this does not belong in development, I have nothing against to moving it to General. However, I think the community would appreciate if it would remain here.

Works fine
I used this to flash the latest Continuum 3.5 and everything worked fine. Thanks!

you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered NO BOOTLOADERS! @@ YAY

Yep, updated, thanks!

Thanks for this and I appreciate all your work.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Success !!
Just used this to go back to stock prior to flashing another ROM. Worked with no problems and only took about 5 minutes. Will use this from now on to avoid the possible brick.
Again, really appreciate you providing this for us.

Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???

sircaper said:
Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???
Click to expand...
Click to collapse
Here you go again, is in the OP
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
Click to expand...
Click to collapse

on top of the read phail, i would add that you dont need to flash stock between roms, you only need to do it after a failed flash or a "no wipe" rom that depends on original files, **which they dont do anymore**. All the good full roms do a wipe before flashing. so there is no point going to stock! hope that clearifies!

icezar1 said:
Here you go again, is in the OP
Click to expand...
Click to collapse
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?

sircaper said:
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?
Click to expand...
Click to collapse
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?

icezar1 said:
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?
Click to expand...
Click to collapse
Makes sense. Is there ever an instance where those files need to be wiped, though?

sircaper said:
Makes sense. Is there ever an instance where those files need to be wiped, though?
Click to expand...
Click to collapse
Not really. Only if you flashed a boot loader from a different SGS model.

icezar1 said:
Not really. Only if you flashed a boot loader from a different SGS model.
Click to expand...
Click to collapse
Thanks. Appreciate you clearing things up for me.

Trusselo said:
you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered
Click to expand...
Click to collapse
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.

Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.

WickedNite said:
Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.
Click to expand...
Click to collapse
Yes, is OK

Has anyone flashed the three button fix? I really want to. just wanna verify its ok.

likiud said:
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.
Click to expand...
Click to collapse
take a look here

double RL said:
Has anyone flashed the three button fix? I really want to. just wanna verify its ok.
Click to expand...
Click to collapse
You dont have the 3 button fix?
EDIT: yes, is OK, I tested it. Make sure you run a md5 checksum after putting it on your sdcard

Help - S4 WONT BOOT or enter RECOVERY!

Hello
My S4 (XUBMGA) wont boot, it kept crashing so i used Odin to fresh install the OS, but it wouldnt let me enter recovery mode after so then I googled and found this website which gave me steps to recover my OS via Odin and also re-partion the recovery mode via a PIT File.
Now my S4 wont boot (stays stuck on the Samsung 9505 logo) and when i try enter recovery the blue text 'Recovery Boot' or something stays there but it wont enter. The phone doesnt boot up but I can still enter download mode?
What can i do! Also im a newb at this so simple please
Thanks in advance!

Get a stock rom from Samfirmware, flash it with Odin. That's the only way you're fixing it. How ? Search.

MistahBungle said:
Get a stock rom from Samfirmware, flash it with Odin. That's the only way you're fixing it. How ? Search.
Click to expand...
Click to collapse
I did i downloaded the BTU United Kingdom Version but im not 100% sure which one to download? I bought the phone unlocked over eBay so im not sure which firmware to download exactly? I cant turn the phone on and go to about device as it wont boot to check all the numbers. Im sure it ended in MGA though
Any help?

BUMP

1) You absolutely do not bump threads after 25 minutes. This isn't your personal technical support hotline :-|
2) It makes no difference which firmware you use, as long as you use one for your specific model, tho I personally would use the latest one my carrier has released (if there was more than one). You may prefer to use an unbranded one for your country if there is one (I have no idea if there is/isn't one of these for the UK).
If you want to fix this, it's going to take a bit of effort on your part, we can't do it for you.
Edit - You really need to learn 'the basics' (people need to do this before they start messing with their phones, not after they bork them). Once you've fixed it, read the Stickies before you bork it permanently.

MistahBungle said:
1) You absolutely do not bump threads after 25 minutes. This isn't your personal technical support hotline :-|
2) It makes no difference which firmware you use, as long as you use one for your specific model, tho I personally would use the latest one my carrier has released (if there was more than one). You may prefer to use an unbranded one for your country if there is one (I have no idea if there is/isn't one of these for the UK).
If you want to fix this, it's going to take a bit of effort on your part, we can't do it for you.
Edit - You really need to learn 'the basics' (people need to do this before they start messing with their phones, not after they bork them). Once you've fixed it, read the Stickies before you bork it permanently.
Click to expand...
Click to collapse
I have and am trying. Im new to Samsung, just moved after years of iPhone, hence though rooting would be similar to jailbreaking the iPhone.
Ive tried multiple ROMs now using Odin 3.07, it says it passes etc but the phone stays on the Samsung Galaxy S4 logo, it doesnt still let me enter recovery mode, but allowss me to get into download mode.
Any advice? Thanks

Download the last Twrp recovery(tar format) for your phone from their website flash it with odin 3.07
Noticeut your tar file with PDA
uncheck the reboot box.let only the reset box checked.
Don't check for any reason the partition case.
GO to download mode with your phone:hold down volume+power+home
After volume +button to continue
You are now on the download mode.connect your phone to your computer
If the box in the left corner become blue .it ok
If in the message box you see "added".it ok
Now press the start (the button to begin the process)
Wait till you will see PASSED in the left upper case.(take around 2min)
Unplung your phone,remove the battery.
Reput the battery and swicht on your phone :hold hight volume+home+power
2nd notice:when you see the samsung logo appear for the first time and going,remove your hand and you will see the beautiful twrp interface.
By the way,you should already have download SuperSu 1.51 and put that somewhere In your extsd card.
Go to install(always in the twrp recovery)
And select the Super su 1.51 or 1.41,cause they are stable)(you know the path where you will put the SuperSu app)
Installation succefull.touch the reboot button on the interface .your phone will reboot and you will see this mesage "Android upgrading"
Ok.i think you have understood.
Sent from my GT-I9500 using xda app-developers app

Minou32 said:
Download the last Twrp recovery(tar format) for your phone from their website flash it with odin 3.07
Noticeut your tar file with PDA
uncheck the reboot box.let only the reset box checked.
Don't check for any reason the partition case.
GO to download mode with your phone:hold down volume+power+home
After volume +button to continue
You are now on the download mode.connect your phone to your computer
If the box in the left corner become blue .it ok
If in the message box you see "added".it ok
Now press the start (the button to begin the process)
Wait till you will see PASSED in the left upper case.(take around 2min)
Unplung your phone,remove the battery.
Reput the battery and swicht on your phone :hold hight volume+home+power
2nd notice:when you see the samsung logo appear for the first time and going,remove your hand and you will see the beautiful twrp interface.
By the way,you should already have download SuperSu 1.51 and put that somewhere In your extsd card.
Go to install(always in the twrp recovery)
And select the Super su 1.51 or 1.41,cause they are stable)(you know the path where you will put the SuperSu app)
Installation succefull.touch the reboot button on the interface .your phone will reboot and you will see this mesage "Android upgrading"
Ok.i think you have understood.
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply.
I followed your steps and also a youtube video but when my phone reboots and you have to enter recovery mode (to get to TWRP) it doesnt go beyond the blue font at the top left and the samsung logo. It stays there
Any advice mate
Thanks

bump - im desperate to get this sorted

hus2k7 said:
bump - im desperate to get this sorted
Click to expand...
Click to collapse
Bump

I think you 1.didn't check the reboot box
2.you removed the batterie after seing the passed message
3.and you removed your hand (all)after the samsung logo disapear
4.you download the last twrp for you model.
What is your phone model in fact?
If you want to see that go to 1.setting
2.more
3.about device
Mine is gt-i9500 simply
No at
No lce or others ones
Sent from my GT-I9500 using xda app-developers app

[Q] Galaxy Young Startup with Red screen of death

Hi, i would like to find a way to fix a red screen problem.
A year ago i had a black screen and fixed it, used that solution for the red one but doesn't work.
Click to expand...
Click to collapse
When i start my galaxy young after the Galaxy Young GT-S5360 splash it turns into a red screen then shuts down.
Click to expand...
Click to collapse
I originally used Qualcomm NV Tools to read the SPC Code,
then i went into ADB shell & did su + setprop ril.MSL 123456, it worked fine, and the phone started good, but still no MSL / SPC Code, also used MSL Reader but didn't work. Also it didn't ask for root permissions.
Click to expand...
Click to collapse
Then here problems come. A red screen of death appears.
I tried using my USB Jig (even if download mode works without) to put the phone in download mode,
it worked, then connected to the computer using its original USB cable, before using Odin.
I though there could be a difference between "Factory" and "Odin" mode.
Used Odin version is 3.07 : The one that comes with "T Flash, Flash Lock, Nand Erase All".
Click to expand...
Click to collapse
I thought it was an efs problem. But how could i flash efs if totoro.pit comes with an EFS partition that doesn't have an img file? (the --11 Entry EFS without Image flash name).
I used PIT Magic (part of EFS Pro) to insert "efs.rfs" in Flash Name + FOTA, saved the file.
Click to expand...
Click to collapse
I checked re-partition and selected the totoro.pit file, i also've written "PhoneEnable=1" in Odin3.ini to use Phone Bootloader Update feature.
I inserted the Bootloader, PDA, Modem, & CSC Files. I checked Phone Bootloader Update.
The flash was fine, & efs.rfs (my most recent EFS backup image) flashed correctly into phone's.
Click to expand...
Click to collapse
But the phone still shows the red screen. I think the red screen is caused by "setprop ril.MSL 123456",
as i used qualcomm NV Tools many times and phone always worked fine.
Click to expand...
Click to collapse

The efs partition is usually not mountable in a galaxy y
Remove the sd card from your phone
Go into download mode
Flash the firmware from my firmware thread (links in my signature)
Never flash a pit file or bootloader - if you choose the wrong one you will brick your phone as you have discovered
If you can't successfully boot the phone after that you will have to flash the correct bootloader via a jtag - if you don't have one goto a repair shop as they cost about £200 UK pounds
If after that it still doesn't work might have to replace motherboard but you might as well put the money towards a new phone

Hi marcussmith2626,
I flashed Bootloader in the s5360 ODD package and used totoro.pit file
marcussmith2626 said:
If after that it still doesn't work might have to replace motherboard but you might as well put the money towards a new phone
Click to expand...
Click to collapse
Then i think it will be cheaper to buy a fresh new phone
Thank for your help anyway :good:

I fixed the problem 1 week after your reply, i could post solution if someone needs.

Killnolife said:
I fixed the problem 1 week after your reply, i could post solution if someone needs.
Click to expand...
Click to collapse
How you fix ?? i need so much !!! Please Help me ...

thiefxhunter said:
How you fix ?? i need so much !!! Please Help me ...
Click to expand...
Click to collapse
I took an hex editor and started the phone in download mode,
i took totoro.pit and added cal.bin under 'cal' partition name, and flashed custom pit.
(restarted and made a custom odin package with this cal.bin).
then i sent my latest cal backup (call this EFS Backup) and sent to device my cal.bin inside TAR file.
Then the phone restarted without problems.
Do you have an EFS (in fact cal) backup of your phone?
It's the bml15 block of your device. :good:

Killnolife said:
I took an hex editor and started the phone in download mode,
i took totoro.pit and added cal.bin under 'cal' partition name, and flashed custom pit.
(restarted and made a custom odin package with this cal.bin).
then i sent my latest cal backup (call this EFS Backup) and sent to device my cal.bin inside TAR file.
Then the phone restarted without problems.
Do you have an EFS (in fact cal) backup of your phone?
It's the bml15 block of your device. :good:
Click to expand...
Click to collapse
Can you upload the file?, this red screen of death is a common issue in the samsung galaxy young. thanks