Database Develop

[Q] Any fix for mobiles without Recovery/Download mode?

Long story short my phone originally came without the three button mode, yet I applied the fix and used to work but now it's gone.
Phone won't boot to either to download or recovery mode. I've tried all possible key configurations yet without any result.
My phone could only boot to the "Galaxy S" screen and stays their or the "Forced upload by key pressing".
Whenever I use Odin it stays at the "SetupConnection.." line.
Your feedback would be highly appreciated whether there is fix or sadly no.
Thanks.

I guess there is no straight answer for this issue....

Homemade USB Connector to Force the Phone into the Download Mode to recover from a Brick:
http://forum.xda-developers.com/showthread.php?t=819551
Boot Loader Update to fix the 3 Button Download and Recovery. It requires Odin to flash.
http://forum.xda-developers.com/showthread.php?t=785201
Since you have had issues at SetupConnection, I would recommend you to stick with the First method because it is the safest. A Failed Bootloader Flash Attempt will Brick the Phone and there would be now way of recovering the phone except for servicing it by Samsung or using the JTAG.
Make the USB Jig and keep it. It would be more than enough to recover from a Bad Flash.

dhiru1602 said:
Homemade USB Connector to Force the Phone into the Download Mode to recover from a Brick:
http://forum.xda-developers.com/showthread.php?t=819551
Boot Loader Update to fix the 3 Button Download and Recovery. It requires Odin to flash.
http://forum.xda-developers.com/showthread.php?t=785201
Since you have had issues at SetupConnection, I would recommend you to stick with the First method because it is the safest. A Failed Bootloader Flash Attempt will Brick the Phone and there would be now way of recovering the phone except for servicing it by Samsung or using the JTAG.
Make the USB Jig and keep it. It would be more than enough to recover from a Bad Flash.
Click to expand...
Click to collapse
I see what you mean but if your connection is good enough to install a new ROM, wouldn't it automatically also not be good enough to install a new bootloader?

[Q] Is my phone bricked?? :(

I need help..
I have a rooted SGS with the lagfix. I uninstalled the lagfix then I updated to the latest firmware via Kies.
Now my SGS will not boot past the logo screen. The menu and back buttons are lit and all vibrates every 60 secs or so.
I have tried removing the battery for 30 secs but that didn't work.
Please help me. What do I need to do to get it started?

it is not bricked so dont panic. I assume you have the 3 button combo for recovery and download mode ??
If so firstly try to do a factory reset in recovery, if that dont fix the problem you will have to flash a new ROM via 'Odin'
Try to get a firmware with all 3 files. they can be found on here XDA under the general section. or you can go to www.samfirmware.com Both contain all the files / programs you need plus step by step instructions.
If this is your first time Please Please read carefully.

I have tried the three buton thing but that doesn't help.
I was afraid I would have to use Odin.

dont be afraid its nothing to worry about, its as easy as 1, 2, 3,
There are gazzillions of tutorials out there, just take your time

azzledazzle said:
dont be afraid its nothing to worry about, its as easy as 1, 2, 3,
There are gazzillions of tutorials out there, just take your time
Click to expand...
Click to collapse
The problem is I can't enter download mode. Don't I need this to be able Odin to start?
I have installed Odin and the required files etc. (seems pretty straightforward as you said).

most likely kies upgraded ur bootloader.. this happened to me once, i fixed it using this thread http://forum.xda-developers.com/showthread.php?t=785201

[Q] Have I ruined my in law's phone? Can anyone help me please?

My father in law bought a new phone SGS on O2 and I offered to unlock it as I have unlocked my husbands last week (he's was on O2 as well but in 2.1 or 2.2.1 version I think-froyo?)
Before I continue may I say I know you guys out there know so much more than me and I really need your help. I really tried to help unlocking this phone and for hours I searched and read things like reboot, download mode, recovery mode, flashing, JKV and so many other words and letter that I could not understand. Very few I understood in the end but may have messed up badly (?).
Please, I need help and please treat me as if I were your mum or even grandma. Step by step in simple normal English please.
My father in law's version is 2.3.3
I tried unlocking it the way I unlocked my husband's but didn't work. After looking for hours I thought that the best way to do it would be to downgrade from 2.3.3 (gingerbread (?)) to 2.2.1 (froyo (?)) and then unlock it.
I found this:
http://forum.xda-developers.com/showthread.php?t=1089989
and tried to follow it.
I downloaded EZRom and EZboot-Froyo-1.0.tar.md5 from the same post.
I followed:
•Download the right version from section above
•Reboot your phone into Download mode
•Connect your phone to computer
•Run EZOdin
•Select EZboot-Froyo-1.0.tar.md5 or EZboot-GingerBread-1.0.tar.md5as a PDA file in EZOdin
•Check the "Phone Bootloader Update" checkbox
•Click Start
I waited for the phone to turn off and feel the little vibration but didn't. Instead it just froze at the first screen when you turn on the phone. The black background with white letters: Samsung Galaxy...
I waited and waited and as nothing was happening I then I took the battery out. Put it back in and tried turning it on. I wouldn't it would just stop and that same screen, the black and white one.
I reread
•Wait until phone reboots and make it reboot into Recovery
SO then I remembered in the many threads I read about the recovery mode so 3 clicked vol up + button at them bottom and turn on bottom.
It gives me a few options. When I click on reboot all it does is show me the black and white screen again and nothing else. ah!!!
I took the battery off and put it back on many times, I also selected the fatory reset option and tried different buttons but nothing. Please help me.
I'm happy to phone any of you guys to help me and guide me even if it's just to put the phone back to what it was before, turning on normally, etc. I'm feeling really sad and a bit stressed as these days are supposed to be a nice time to spend with my little ones and family.
Anyway, please ask me anything.
Thank you so much in advance. I really hope I didn't do anything wrong and I'm just stuck because I'm ignorant in this matter. Thank you

I was never a fan of EZ-stuff.
That said, think you can easily solve that flashing your phone with odin and a proper rom. At this point i am unclear about what bootloaders you have on your phone since you've tried a downgrade.
Without getting into further details (sorry, at work atm). You can get tutorials easy for all of this around this forum.
I'd get Odin, get a proper stock rom from samfirmware with bootloaders included and flash it fresh from start with that. Doesn't really matter if it's froyo or ginger as long as it includes bootloaders.
You'll be left with a working phone at this point.
From here, if you still want to try to unlock it, i'd flash a kernell that would get me root (like the ChainFire one) since i find this the safest and easiest way of getting root on your phone and do a backup of your EFS partition (preferably saved in your computer or wherever outside your phone). This is very important, if you lose of mess up with this part of your phone it will be a pain.
Now, there are several ways of unlocking this phone, the only one i found to be most reliable (but not the easiest one) is to manually edit the nv_data.bin file (located in your EFS partition in hexadecimal.
There's a tut right here
http://forum.xda-developers.com/showthread.php?t=761045&highlight=unlock

Thank you so much for taking the time to reply although you are working!!! Really appreciate it.
I'll try your suggestion but I don't know how to choose the right stock rom with bootloader from samfirmware. I went to the website and registered but don't really know what to do.
I know you are working so might not be able to help me, may be someone else?
Here's where I am. Update. I found a list of firmware. This is the last one on Samfirmware.com.
Europe Samsung I9000 Firmwares.
I9000XXJVS ##
512.PIT
2.3.5
2011 September 8
CSC = I9000OXAJVS
DOWNLOAD
Things I need: (I think)
-Download a firmware (should I use the lastest one?) or 2.2 or 2.3.3? . Is there one better than the other? or is it my choice? How can I choose the best one for me?
-Odin. I have OdinMultiDownloader v4.03 in my desktop. Is that the best thing to use or should I use Ezodin. I don't know what the difference is.
-(Do I need to download or do anything else?)
Things I should do:
-Put phone in download mode
-Plug it to the laptop
-Open Odin (or Exodin?)
-click PDA. Choose the fie I downloaded-firmware.
(-after this I don't know what else I should do or tick or untick)
Am I in the right track or completely off it?
Thank you again to anyone taking the time to read this.

Download Jvt From sammobile. com, you need Odin on your PC (1.7 or 1.8) plus Samsung drivers. Read there flashing guides carefully, check you have download
Mode, battery charged > 50% etc
There is also a video on youtube which shows you how to upgrade to jvt.
Sent using TCP/IP

Sounds like you've got the boot-loop problem, which means that you most likely "soft-bricked" the phone. Don't worry, this isn't that big of a deal and can be fixed with relative ease. I agree with the posters above, a clean flash with Odin will probably fix your problem and get you out of the boot-loop.
I'll go into a bit more detail with some steps (feel free to correct me if I missed anything)
1. Download Odin 1.85 here.
2. Head over to Samfirmware.com and grab the latest firmware for the phone. I recommend Gingerbread 2.3.5 (JVT).
3. Make sure your computer has the proper drivers installed so it can communicate with your Samsung Galaxy GT-I9000. If you've flashed the phone before with your computer then you probably have the drivers installed, but here's a link for them just in case: Samsung USB Drivers
4. Enter download mode on your phone, depending on your firmware, it could be Vol down + power + home OR Vol up + power + home. Pull the battery out, pop it back in, and hold those three buttons until the phone turns on.
If you can't enter download mode with the 3-button hold method, then you might have to do so via ADB with the command "reboot download".
Getting into download mode is pretty critical, as you cannot progress further without it.
5. Once you're in download mode (should see a triangle with an Android shoveling stuff in it), plug your phone into your computer's USB port and open Odin. In Odin, press "Reset" on the right hand side. Odin should be able to detect your phone (this is indicated by a yellow box on the left side). I'm using a PC, so inside the yellow box I see something like this: 0:[COM9]. On a Mac it probably says something different, but as long as you see the yellow box appear then it's all good.
If you don't see the yellow box, then there's no communication between your phone and the computer, which means that you may have to reinstall the Samsung USB drivers.
6. With the contents in the firmware package that you downloaded from Samfirmware.com extracted, load them onto Odin accordingly.
PIT: use s1_odin_20100512.pit
PDA: JVT (sometimes the PDA is labeled CODE instead)
PHONE: JVT (sometimes labeled as MODEM instead)
CSC: use HOME-MULTI-OXAJVT (should be about 9.5 MB in size)
Since your father-in-law's phone was originally 2.3.3, you shouldn't have to alter the bootloader with Odin, so leave the bootloader field empty.
7. Once you've loaded up all the necessary files, make sure Re-partition and Auto-reboot is checked. Leave the rest of the checkboxes as it.
8. Press Start. This should initialize the flashing of the new firmware. After the phone has been flashed, it should reboot automatically and should hopefully be able to get past the Galaxy S black and white logo (aka. boot loop).
9. The phone should be in working order now. I used this method to unlock my SGS: SIM Unlock on the SGS. With this method, your phone needs to be rooted, so head on over to ChainFire's thread here to install his kernal which is already rooted.
Flashing firmware can be pretty scary since nobody wants to end up with a brick that costed $400 and it seems like so much can go wrong, but hopefully the steps I've provided helped. Good luck!

[Q] galaxy ace s5830D in BOOT LOOP, no access to 'RECOVERY'

Hi gals and guys, I bought a new galaxy ace s5830D (gingerbread) from Telus and decided to unlock it the following way:
1. root using Universal_GB_ROOT_v10.zip
2. installed SuperOneClickv2.1.1-ShortFuse.zip on PC
3. installed Root Explorer (File Manager) v2.19.apk
4. used ADB shell on PC to read ST5L for unlock code
here is where the problem begins:
-- upon reboot phone goes in a bootloop (screen lights for a sec without Samsung logo)
-- I CANNOT put phone in recovery via home + power
--I CAN put phone in 'download' via power + home + vol dwn; or to RamDump with vol Up; or to Emergency Dload Mode by holding both up and dwn
I have tried the following:
-- flash stock telus rom S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar using ODIN. The flash goes successful but upon reboot goes back to bootloop? And still cannot enter 'recovery'
-- tried to flash cwm-recovery-ace.tar.md5 using ODIN. The flash is successful but on reboot goes to bootloop. Still no acess to 'recovery'
-- tried QtADB but cannot connect to phone
-- tried OneClickUnbrick but it will not recognize connection to phone either
-- tried AndroidSDK however cannot get to recognize device
So any ideas considering the main thing is I cannot get to 'recovery' and flashing with ODIN still results in bootloop.
Thanks for any advice

tedxdadevelopers said:
Hi gals and guys, I bought a new galaxy ace s5830D (gingerbread) from Telus and decided to unlock it the following way:
1. root using Universal_GB_ROOT_v10.zip
2. installed SuperOneClickv2.1.1-ShortFuse.zip on PC
3. installed Root Explorer (File Manager) v2.19.apk
4. used ADB shell on PC to read ST5L for unlock code
here is where the problem begins:
-- upon reboot phone goes in a bootloop (screen lights for a sec without Samsung logo)
-- I CANNOT put phone in recovery via home + power
--I CAN put phone in 'download' via power + home + vol dwn; or to RamDump with vol Up; or to Emergency Dload Mode by holding both up and dwn
I have tried the following:
-- flash stock telus rom S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar using ODIN. The flash goes successful but upon reboot goes back to bootloop? And still cannot enter 'recovery'
-- tried to flash cwm-recovery-ace.tar.md5 using ODIN. The flash is successful but on reboot goes to bootloop. Still no acess to 'recovery'
-- tried QtADB but cannot connect to phone
-- tried OneClickUnbrick but it will not recognize connection to phone either
-- tried AndroidSDK however cannot get to recognize device
So any ideas considering the main thing is I cannot get to 'recovery' and flashing with ODIN still results in bootloop.
Thanks for any advice
Click to expand...
Click to collapse
What ROM are you trying to flash with ODIN, because I couldn't find any on SamFirmware. Also in order to use ADB, you need the drivers, make sure you have them installed (they automatically install when you install Kies).

tedxdadevelopers said:
Hi gals and guys, I bought a new galaxy ace s5830D (gingerbread) from Telus and decided to unlock it the following way:
1. root using Universal_GB_ROOT_v10.zip
2. installed SuperOneClickv2.1.1-ShortFuse.zip on PC
3. installed Root Explorer (File Manager) v2.19.apk
4. used ADB shell on PC to read ST5L for unlock code
here is where the problem begins:
Click to expand...
Click to collapse
The stl5 method might damage the efs partition. It's a coinflip, with 3 outcomes:
-all goes well and you get an unlocked ace.
-your imei becomes 00000000000000 in which case you get aa working ace, but many carriers deny service to that imei, so no calls, no sms, no movile data.
-completely f****d up efs partition. You loose your imei. That's it, you're toast. No amount of flashing fixes this, it's not a hardbrick, but no rom will boot appropriately.
Try and flash a full package with odin. Make sure you use the correct odin version for your model and have the correct firmware. Then go into recovery and wipe everything, see if it boots. If it boots, open up your call app and dial *#06#* to see your imei (to make sure its still there).
If you have successfully flashed with odin before, and still won't boot or go into recovery, then maybe your efs partition got messed up.

Return the phone to telus, just don't tell them what you did.

thanks for the suggestions.. few more questions
-- any suggestions as to what to tell telus that is believable that happened? (phone is 3 days old and i bought it outright)
-- also re Efs partition damage, is there any way to repartition the phone and rewrite imei (isn't it on the stickers behind the battery)?
with ODIN i flashed (several times - all successfully) the stock rom made for the TELUS D version on the Ace. Its someone that build it from a stock Ace. Its available if u google it and many ppl have returned their Telus phones to stock telus\koodoo status via that rom with proprtietary carrier startup screen and all. The Model D of the Ace is not at all available on the SamFirmware site.
I also flashed only the CWM Recovery - sucessfully and still no access to 'recovery' menu.
ODIN i am using is the right version according to all i have read (4.42); and the .ops file is made, as I understand it, for partitions of the D version of the Ace. (odin + ops + rom was all one package that many ppl from telus have said to have used sucesfully to return their phones to stock.)
-- should i try to flash with odin a cyannogen mode 7.2.0; could that make a difference vs stock rom, or does the cyannogen just go on top of the stock rom; ie will not function without a proper stock rom? (i guess what i am asking is cyannogen a complete self contained os?)
--If the efs partition is damaged does it make sense then, that the ADB, oneclick unblock etc.., will not recognize the phone? Am i supposed to be able to even connect to ADB when phone is in 'download mode'? or its made to work only when phone is already booted up?
thanks guys again.. T

tedxdadevelopers said:
thanks for the suggestions.. few more questions
-- any suggestions as to what to tell telus that is believable that happened? (phone is 3 days old and i bought it outright)
-- also re Efs partition damage, is there any way to repartition the phone and rewrite imei (isn't it on the stickers behind the battery)?
with ODIN i flashed (several times - all successfully) the stock rom made for the TELUS D version on the Ace. Its someone that build it from a stock Ace. Its available if u google it and many ppl have returned their Telus phones to stock telus\koodoo status via that rom with proprtietary carrier startup screen and all. The Model D of the Ace is not at all available on the SamFirmware site.
I also flashed only the CWM Recovery - sucessfully and still no access to 'recovery' menu.
ODIN i am using is the right version according to all i have read (4.42); and the .ops file is made, as I understand it, for partitions of the D version of the Ace. (odin + ops + rom was all one package that many ppl from telus have said to have used sucesfully to return their phones to stock.)
-- should i try to flash with odin a cyannogen mode 7.2.0; could that make a difference vs stock rom, or does the cyannogen just go on top of the stock rom; ie will not function without a proper stock rom? (i guess what i am asking is cyannogen a complete self contained os?)
--If the efs partition is damaged does it make sense then, that the ADB, oneclick unblock etc.., will not recognize the phone? Am i supposed to be able to even connect to ADB when phone is in 'download mode'? or its made to work only when phone is already booted up?
thanks guys again.. T
Click to expand...
Click to collapse
Hey again, changing IMEI is illegal in some countries:
Here is a link on how to change it though.
when I go to repair my phone, they normally don't ask why does this happen, they just ask what's the problem. ALso, you have to pretend you are really angry, because the phone broke just 3 days after buying it. That's all. Just be sure that the boot animation is from the stock ROM, as well as the currently installed ROM.

Good deal, had phone exchanged for a new one. That should serve as a lesson to those trying to screw with their efs/ that sometimes it may actually NOT work!!
Thanks guys Cheers!

GT-S5830V Won't enter download mode

It goes into Recovery mode ok but no download mode.
Power + vol down (or vol down + vol up) + home makes it loope the galaxy screen once then it just loads the built in rom.
After I first bought it I could get it into download mode. But after rooting her so many times she refuses to play ball.
I have tried unrooting it and uninstalling busybox / CWM etc but don't know what else to try.
is there anyway of resetting the "bios" of the phone to default or something?
I tried restoring the stock build.prop.
Dunno what else to do.
Any advice much appreciated.
Regards.

did u tried entering download mode through terminal?
in the terminal :
su
reboot download
and u ll be in download mode n if this doesnt work then try flashing new rom
Sent from my OCTA CORE I9500

He can't get into download or recovery because 5830v is an Aussie version with secure kernel. He needs a USB Jig to get his phone into download mode. However he can root the device by enabling USB debugging and installing the latest drivers and then running an exploit like Moto-Chopper (same as I have done). Then I'd advise using Galaxy Toolbox to unlock the device and backup the EFS. Then I would generate the PIT file and use EFS to do all full image backups of the device. I would buy/make a USB jig and then flash a custom recovery. Then flash new kernel. Then after all of that you may now flash a new ROM. Avoid Odin where ever possible. The 5830v is NOT the same as the 5830i. The i can handle software from the v but not visa versa.
Take that as a word of warning.
Edit: I posted in this thread because there is very little information of XDA about the Galaxy Ace GT-5830v

AdroidOre said:
It goes into Recovery mode ok but no download mode.
Power + vol down (or vol down + vol up) + home makes it loope the galaxy screen once then it just loads the built in rom.
After I first bought it I could get it into download mode. But after rooting her so many times she refuses to play ball.
I have tried unrooting it and uninstalling busybox / CWM etc but don't know what else to try.
is there anyway of resetting the "bios" of the phone to default or something?
I tried restoring the stock build.prop.
Dunno what else to do.
Any advice much appreciated.
Regards.
Click to expand...
Click to collapse
Hi have you tried using a JIG

please help
Jarmezrocks said:
He can't get into download or recovery because 5830v is an Aussie version with secure kernel. He needs a USB Jig to get his phone into download mode. However he can root the device by enabling USB debugging and installing the latest drivers and then running an exploit like Moto-Chopper (same as I have done). Then I'd advise using Galaxy Toolbox to unlock the device and backup the EFS. Then I would generate the PIT file and use EFS to do all full image backups of the device. I would buy/make a USB jig and then flash a custom recovery. Then flash new kernel. Then after all of that you may now flash a new ROM. Avoid Odin where ever possible. The 5830v is NOT the same as the 5830i. The i can handle software from the v but not visa versa.
Take that as a word of warning.
Edit: I posted in this thread because there is very little information of XDA about the Galaxy Ace GT-5830v
Click to expand...
Click to collapse
Hey Jarmezrocks!
I have an Australian Samsung galaxy ace gt s5830V. I am finding incredibly hard to find any info on how to fix the bootloop on my screen. As per your advice I have purchased a usb jig ( to get my phone into dl mode). But as my phone is not rooted and I have never put any upgrades or roms on it I'm a bit puzzled as to why it has done this and how to fix it. In your post you say not to use Odin. Why is that and what can I do instead?
Your help would be greatly appreciated because all the info on here is mainly directed at s5830i.
Thanks

scarletshay said:
Hey Jarmezrocks!
I have an Australian Samsung galaxy ace gt s5830V. I am finding incredibly hard to find any info on how to fix the bootloop on my screen. As per your advice I have purchased a usb jig ( to get my phone into dl mode). But as my phone is not rooted and I have never put any upgrades or roms on it I'm a bit puzzled as to why it has done this and how to fix it. In your post you say not to use Odin. Why is that and what can I do instead?
Your help would be greatly appreciated because all the info on here is mainly directed at s5830i.
Thanks
Click to expand...
Click to collapse
Avoid Odin trying to flash a custom ROM, use it only when you need to. Flashing a more insecure kernel that enables download mode without the use of the USB jig in other words.
For you it maybe as simple as booting into recovery mode and simply doing a factory data reset? That should wipe any data that maybe stopping the device from booting correctly? After factory reset you should be able to flash a custom recovery zip from the factory recovery? I can re-upload what I used that was successful with the S5830V if you are stuck?