Related
Continuing my quest for confirming an unlocked/locked bootloader, I have stumbled across a key combo for getting into download mode! When the phone is off, hold the volume up button and plug in the micro usb cable, the phone should then boot up (on its own, do not touch the power button) to a screen with a grey box with a down arrow that says download mode. For anyone that used to own a Samsung Galaxy S phone, this mode was the primary mode for flashing roms via Odin and Heimdall. Now we just need a recovery rom and flashing software (possibly [AIO] ROMTools, I will fiddle around with it tonight).
Confirmed on Bell Optimus LTE, unit must be off, hold up while plugging in USB cord.
gte460z said:
Continuing my quest for confirming an unlocked/locked bootloader, I have stumbled across a key combo for getting into download mode! When the phone is off, hold the volume up button and plug in the micro usb cable, the phone should then boot up (on its own, do not touch the power button) to a screen with a grey box with a down arrow that says download mode. For anyone that used to own a Samsung Galaxy S phone, this mode was the primary mode for flashing roms via Odin and Heimdall. Now we just need a recovery rom and flashing software (possibly [AIO] ROMTools, I will fiddle around with it tonight).
Click to expand...
Click to collapse
This is great news! I've been needing to re-flash the stock ROM since day one (when I hosed my root with a bad busybox)...
Very nice find... I had been able to get into download mode before, but I didn't realize it was the usb connection that allowed it.
If you look in some of the other threads you will see that I have been able to locate the boot and recovery partitions - just 'standard' emmc partitions. I have pulled the data off the device and unpacked them so that I am able to look at the data within the partitions. Next is to start to understand what is inside the files - mainly init.rc and the other .rc files.
Currently I think part of the lack of recovery for us has to do with a line in init.rc:
service adbd /sbin/adbd recovery
disabled
Something tells me this will disable the recovery capabilities for the phone... but still looking around to figure it out. Will keep everyone posted.
Please do! Sounds like we are making progress as a whole!
great news guys!
thx 4 ur hard work!
hope ur next good news~
Wonderful news we are getting this past week!! Much progress has been done I'm getting so excited at where all this will lead us to Glad to be part of a sub-forum with tons of fiery passion and dedication. I'm not much of a help since I'm not good with any of these things, but I'll contribute in any way possible
Just got this phone for Christmas, but they were out of stock at 2 nearest stores to me. Have to wait a day or 2 for it to be shipped alas.
If you set it so that start adbd in recovery is enabled, what happens when you use ROM Manager to boot into recovery? I tried booting into recovery without editing the init.rc and I got a little Android guy with an open box and an arrow coming out for a sec, but then it kicked me out by rebooting.
Sent from my LG-P930 using xda premium
I will be attempting to do that some time this evening. Before I attempted it I wanted to be sure I wasn't going to be stuck with a brick. It will also let us finally figure out if out bootloader is locked or not.
schwin97 said:
I will be attempting to do that some time this evening. Before I attempted it I wanted to be sure I wasn't going to be stuck with a brick. It will also let us finally figure out if out bootloader is locked or not.
Click to expand...
Click to collapse
Good luck and God Speed Sir!! Bring home the bacon!
So has anyone figured out what we can use this mode for?
If it means anything, that was the mode I had it in while I flashed the SU640 rom.
Good to know, I figured it was the mode that the LG tool used to flash the phone.
Warning
This particular model (SGW or GT-i8150) is extremely prone to soft bricking due to unknown reasons. The phone will get stucked in a boot loop, recovery will NOT be accessible however download and RAMDUMP mode will. There is only ONE warning before your phone brickes forever which is, everything starts to Force Close. And if that happens to you, may I remind you to NEVER EVER restart your phone as that will brick it. Quickly navigate to settings and reset to phone to factory defaults. This problem happened to me when I was using Cow's Bionic ROM (V6) and a few others. And no, this is not caused by left-over data as I have carefully wiped clean any previous data. This happened days after I flashed a custom ROM. I have no idea why this happens and I hope this incident will not happen to you. Some of you advise me to reflash but that does not do anything, Odin will tell me it is successful but when I remove the USB cable it will just get stuck in another infinite boot loop.
Definition
To render your phone useless, as useless as a brick.
Causes
Wrong kernal flashed.
Flashed new ROM without wiping left-over data.
Corrupted ROM
Interrupted flashing
Wrong partition size
Prevention
Always wipe data BEFORE flashing any ROM.
Make sure phone/computer battery is above 50%
Make regular Nandroid backups.
Types
Soft/Semi Bricked
Hard Bricked
A soft brick is when your phone can no longer boot normally to Android. This is easily fixable with re-flashing.
A hard brick is when your phone CANNOT boot at all. This can be fixed with a USB Jig.
Fixing
Soft Brick
Boot phone to download mode with the three button combination (Home+Volume Down+Power).
Download Samsung Kies, Stock ROM , Ancora.ops and Odin Multi Installer.
Connect phone to your computer with the USB cable supplied by Samsung.
Select Ancora.ops as OPS file.
Tick "One Package"
Select One Package file (The Stock ROM that you have previously downloaded)
Click start and wait for approximately 15 minutes.
Disconnect USB when Odin inputs "PASS"
Enter recovery with three button combination (Home+Volume Up+Power) and wipe cache and do a factory reset.
Restart and enjoy!
Hard Brick
Unfortunately, there is no way of fixing a hard brick by yourself without replacing the entire mainboard. You may however send it to any Samsung Service Center if you're under warranty.
Notes (Very Important)
Samsung's warranty does NOT cover bricked phones however you may say that Samsung Kies bricked your phone while upgrading and they MAY repair it for you for free. This repair normally takes around a week or two.
To be even more safe, charge your phone/computer to at least 80% before upgrading anything.
To enter download mode, use the three button combination only until you see an android logo, at that time you must stop pressing the buttons. Press Volume Down to proceed.
To enter recovery mode, use the three button combination to boot and release the power button once you see the Samsung logo. Press on the left touch key once you see an android with a box.
Click here to download Samsung Kies
Click here to download Stock ROM (Search for "I8150" and pick the most suitable ROM.)
Click here to download Ancora.ops and Odin Multi Installer
Sorry if there are any grammar or spelling errors as I'm only 13 years old.
Please hit the "Thanks" button if you think this post is helpful.
Thank you for reading!
Well done n welcome you to the club
Sent from my GT-I8150 using xda premium
thx for the guide ^__^
just got a lil problem, odin is taking forever to install the stock rom, too long that my phone of 100% charged shutted down.. lefted a whole day with no resulte
help ;(
Did you try reflashing again?
Sent from my GT-I8150 using xda app-developers app
Thanks for the guide. I tried to update my firmware today using Samsung Kies. When the phone restarted, every thing seemed fine until it got to my lock screen. It will not respond to any touch, gesture or motion I make on the screen. The only keys that work are the home, volume and power on/off.
I followed your guide, downloaded ODIN and the 2.3.6 ROM with value pack and did the flash only to get the same problem. I tried a ROM from April and January only to get the same thing happening.
Do you have any other suggestions that I could try?
thanks for this post... im new in here.... wanted to flash new rom.. so now i know the risk
I did everything you mentioned here, but whenever ODIN resets my phone, the infinite boot loop with the battery charging and Samsung begins. Any idea what to do? :crying:
i just get my phone back yesterday for the same reason, stuck at samsung logo and no other method can fix it
just go back to samsung and they will change the mainboard for you
Just send it for servicing few hours back, getting it next week with new mainboard
More questions
I have a few questions here:
1. On almost any guide on rooting and flashing, the author will give a warning about bricking. How often do they actually happen? (especially for flashing as I can see it is a more delicate process.)
2. If I happen to hard brick my phone and sent it to scc, what will they do to my phone? And how much will I have to pay? (assuming warranty does not cover)
3. Also, in some of the tutorials, it says that bricking "has been reported with the asian firmware". Does this implies that Asian firmware are especially vulnerable to bricking?
Thanks in advance.
yihangho said:
I have a few questions here:
1. On almost any guide on rooting and flashing, the author will give a warning about bricking. How often do they actually happen? (especially for flashing as I can see it is a more delicate process.)
Click to expand...
Click to collapse
If you stick with tried & true methods (that is, one specifically designed for W and/or extensively tested by users) that does *not* involve Odin, very rarely.
Be very Very VERY careful when using Odin, though. One slight mistake (like forgetting to check a checkbox), and off to brickland you go...
yihangho said:
2. If I happen to hard brick my phone and sent it to scc, what will they do to my phone? And how much will I have to pay? (assuming warranty does not cover)
Click to expand...
Click to collapse
Usually they will first do some hardware checks to ensure that there's no problem with the mainboard. Then they will flash a stock ROM -- and wipe all storage memory -- using Odin.
As to the cost, I don't know. I guess somewhere in the range of 10-30 USD.
yihangho said:
3. Also, in some of the tutorials, it says that bricking "has been reported with the asian firmware". Does this implies that Asian firmware are especially vulnerable to bricking?
Thanks in advance.
Click to expand...
Click to collapse
Asian firmware is quite a bit larger due to having to support multi-byte character encoding. Plus, there are some kludges within some app to handle multi-byte encoding. Some mods did not take this into account.
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --
pepoluan said:
If you stick with tried & true methods (that is, one specifically designed for W and/or extensively tested by users) that does *not* involve Odin, very rarely.
Be very Very VERY careful when using Odin, though. One slight mistake (like forgetting to check a checkbox), and off to brickland you go...
Usually they will first do some hardware checks to ensure that there's no problem with the mainboard. Then they will flash a stock ROM -- and wipe all storage memory -- using Odin.
As to the cost, I don't know. I guess somewhere in the range of 10-30 USD.
Asian firmware is quite a bit larger due to having to support multi-byte character encoding. Plus, there are some kludges within some app to handle multi-byte encoding. Some mods did not take this into account.
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --
Click to expand...
Click to collapse
in my experience, the samsung center start by flashing my phone to stock , but unluckily it doesn't work. so the samsung take 2nd step by checking my phone and tadaaa my mainboard was damaged :|
hadidjapri said:
in my experience, the samsung center start by flashing my phone to stock , but unluckily it doesn't work. so the samsung take 2nd step by checking my phone and tadaaa my mainboard was damaged :|
Click to expand...
Click to collapse
Yeah, too many people flashed custom ROMs that they changed the order of testing now
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --
j0rd4nkzf said:
Warning
This particular model (SGW or GT-i8150) is extremely prone to soft bricking due to unknown reasons. The phone will get stucked in a boot loop, recovery will NOT be accessible however download and RAMDUMP mode will. There is only ONE warning before your phone brickes forever which is, everything starts to Force Close. And if that happens to you, may I remind you to NEVER EVER restart your phone as that will brick it. Quickly navigate to settings and reset to phone to factory defaults. This problem happened to me when I was using Cow's Bionic ROM (V6) and a few others. And no, this is not caused by left-over data as I have carefully wiped clean any previous data. This happened days after I flashed a custom ROM. I have no idea why this happens and I hope this incident will not happen to you. Some of you advise me to reflash but that does not do anything, Odin will tell me it is successful but when I remove the USB cable it will just get stuck in another infinite boot loop.
Definition
To render your phone useless, as useless as a brick.
Causes
Wrong kernal flashed.
Flashed new ROM without wiping left-over data.
Corrupted ROM
Interrupted flashing
Wrong partition size
Prevention
Always wipe data BEFORE flashing any ROM.
Make sure phone/computer battery is above 50%
Make regular Nandroid backups.
Types
Soft/Semi Bricked
Hard Bricked
A soft brick is when your phone can no longer boot normally to Android. This is easily fixable with re-flashing.
A hard brick is when your phone CANNOT boot at all. This can be fixed with a USB Jig.
Fixing
Soft Brick
Boot phone to download mode with the three button combination (Home+Volume Down+Power).
Download Samsung Kies, Stock ROM , Ancora.ops and Odin Multi Installer.
Connect phone to your computer with the USB cable supplied by Samsung.
Select Ancora.ops as OPS file.
Tick "One Package"
Select One Package file (The Stock ROM that you have previously downloaded)
Click start and wait for approximately 15 minutes.
Disconnect USB when Odin inputs "PASS"
Enter recovery with three button combination (Home+Volume Up+Power) and wipe cache and do a factory reset.
Restart and enjoy!
Hard Brick
Unfortunately, there is no way of fixing a hard brick by yourself without replacing the entire mainboard. You may however send it to any Samsung Service Center if you're under warranty.
Notes (Very Important)
Samsung's warranty does NOT cover bricked phones however you may say that Samsung Kies bricked your phone while upgrading and they MAY repair it for you for free. This repair normally takes around a week or two.
To be even more safe, charge your phone/computer to at least 80% before upgrading anything.
To enter download mode, use the three button combination only until you see an android logo, at that time you must stop pressing the buttons. Press Volume Down to proceed.
To enter recovery mode, use the three button combination to boot and release the power button once you see the Samsung logo. Press on the left touch key once you see an android with a box.
Click here to download Samsung Kies
Click here to download Stock ROM (Search for "I8150" and pick the most suitable ROM.)
Click here to download Ancora.ops and Odin Multi Installer
Sorry if there are any grammar or spelling errors as I'm only 13 years old.
Please hit the "Thanks" button if you think this post is helpful.
Thank you for reading!
Click to expand...
Click to collapse
Thank for the sharing, i'll know what to do if I have bricked my Galaxy W :fingers-crossed:
pepoluan said:
If you stick with tried & true methods (that is, one specifically designed for W and/or extensively tested by users) that does *not* involve Odin, very rarely.
Be very Very VERY careful when using Odin, though. One slight mistake (like forgetting to check a checkbox), and off to brickland you go...
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --
Click to expand...
Click to collapse
Wow. Honestly I always think that Odin is the least risky part of the chain. So, do you mind telling me what does each checkbox do? (Most tutorials only tell us which to check and which not to check without explaining the effect of those checkboxes. That makes me very curious.)
Sent from my GT-I8150 using xda-developers app
yihangho said:
Wow. Honestly I always think that Odin is the least risky part of the chain. So, do you mind telling me what does each checkbox do? (Most tutorials only tell us which to check and which not to check without explaining the effect of those checkboxes. That makes me very curious.)
Sent from my GT-I8150 using xda-developers app
Click to expand...
Click to collapse
Well, Odin is a tool that talks directly with the Samsung Download Recovery. It has full access to *all* partitions. It is also complex; it relies on .ops files to tell it what to install where. And, there's *no* guarantee that an .ops file that works with a certain version of Odin will work the same way on a different version.
Plus, Odin does not ever try to recognize the packet(s) it's trying to install. The onus is on the user to tell it what the heck is being installed. (After all, Odin is a *professional's* tool, meant to be used by people who know exactly what they're doing).
I haven't used Odin since I sold my Galaxy Ace for the Galaxy W, so I've kinda forgotten how to use Odin Never need to use it after all; I use CWM to flash ROM and kernel, and never touched my baseband.
Honestly, I found CWM to be much safer: when flashing, all one needs to do is to select the updatezips. No checking/unchecking any checkbox.
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --
pepoluan said:
Well, Odin is a tool that talks directly with the Samsung Download Recovery. It has full access to *all* partitions. It is also complex; it relies on .ops files to tell it what to install where. And, there's *no* guarantee that an .ops file that works with a certain version of Odin will work the same way on a different version.
Plus, Odin does not ever try to recognize the packet(s) it's trying to install. The onus is on the user to tell it what the heck is being installed. (After all, Odin is a *professional's* tool, meant to be used by people who know exactly what they're doing).
I haven't used Odin since I sold my Galaxy Ace for the Galaxy W, so I've kinda forgotten how to use Odin Never need to use it after all; I use CWM to flash ROM and kernel, and never touched my baseband.
Honestly, I found CWM to be much safer: when flashing, all one needs to do is to select the updatezips. No checking/unchecking any checkbox.
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --
Click to expand...
Click to collapse
But how did you install CWM without Odin? Did you use ROM Manager? I read on several posts around the Internet that ROM Manager is causing some bricking...
GT-I8150 - ClockworkMod v6.0.1.2 - CyanogenMod 9 Beta 3 by arco
yihangho said:
But how did you install CWM without Odin? Did you use ROM Manager? I read on several posts around the Internet that ROM Manager is causing some bricking...
GT-I8150 - ClockworkMod v6.0.1.2 - CyanogenMod 9 Beta 3 by arco
Click to expand...
Click to collapse
I use Terminal and the dd command.
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --
hI guys,
Please help me, I'm cut off civilization, my andro is the only way I can stay connected to my family.
1. dalvik, cache reset
2. Cow ROM instaled with CyanoGenMod 6
3. CPU boosted with 1.8GHz for around 3 hours
4. Phone bricked. Boot loop.
Download mode runs, but with Odin doesn't download anything.
Recovery mode doesn't appear.
RAMDUMP mode appears.
After inserting external sd download mode doesnt run
I noticed that the Cow ROM perceived external SD as the internal SD (so all apps are instaled on the external sd)
OneClick doesn't detect the telephone
ADB desn't detect it either.
Please help me, my life here depends on it.
sunwukongdan said:
hI guys,
Please help me, I'm cut off civilization, my andro is the only way I can stay connected to my family.
1. dalvik, cache reset
2. Cow ROM instaled with CyanoGenMod 6
3. CPU boosted with 1.8GHz for around 3 hours
4. Phone bricked. Boot loop.
Download mode runs, but with Odin doesn't download anything.
Recovery mode doesn't appear.
RAMDUMP mode appears.
After inserting external sd download mode doesnt run
I noticed that the Cow ROM perceived external SD as the internal SD (so all apps are instaled on the external sd)
OneClick doesn't detect the telephone
ADB desn't detect it either.
Please help me, my life here depends on it.
Click to expand...
Click to collapse
IIRC, you asked this question too in the Q&A subforum...
I think your phone has bitten the dust; running overclocked (at 1.8 GHz!) is a surefire way to fry a chip.
Best way to fix? SSC.
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --
Before I begin, this is my first post here. I've used XDA before for help and love you guys. Now I need you more than ever. Thanks in advance for the help!
At first, my phone started to act all weird. By that I mean the Espier launcher wouldn't even load. It kept crashing. So I decided to unroot my phone. I used Odin to attempt to put the factory firmware and stuff on my phone but ended up prematurely ending the install, thus bricking my phone. When I turn my phone on I see the "Firmware upgrade encountered an issue" screen. So I did some research and attempted to fix the problem myself. After downloading and installing Kies (on three computers) I attempted to connect my phone to Kies. The USB port works, but none of my computers sees my phone. I've tried different USB ports, reinstalling Kies, using the connection debugging tool within Kies, changed the USB cable, taking the battery out, everything. If I am able to connect my phone to my computer I'll be able to fix the problem. If anyone could help me, that'd be lovely.
Can you get to download mode?
Sent from my SAMSUNG-SGH-T989 using xda premium
The only USB cable I've been able to use Odin or Kies with is the original cable that came with the phone. I have a ton of other micro USB cables, they all will charge but nothing else will do any sort of data transfer. Even then, I sometimes have to change USB ports and have encountered two PCs with won't recognize the phone no matter what. Keep trying.
It's odd, because my old HTC Hero was happy to connect and charge with any cable that fit.
rdsnyder said:
The only USB cable I've been able to use Odin or Kies with is the original cable that came with the phone. I have a ton of other micro USB cables, they all will charge but nothing else will do any sort of data transfer. Even then, I sometimes have to change USB ports and have encountered two PCs with won't recognize the phone no matter what. Keep trying.
It's odd, because my old HTC Hero was happy to connect and charge with any cable that fit.
Click to expand...
Click to collapse
Maxed22a said:
Can you get to download mode?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, I'm able to get into download mode. And I've also used the original cable that has provided with the phone.
Id try to odin the stock rooted kernel with what you have. I assume you still have a copy of what you rooted with... if not
http://forum.xda-developers.com/showthread.php?t=1433101
There you go.
Sent from my SPH-D710 using XDA
drinxtir said:
Id try to odin the stock rooted kernel with what you have. I assume you still have a copy of what you rooted with... if not
http://forum.xda-developers.com/showthread.php?t=1433101
There you go.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
The problem is none of my computers will detect my phone when I plug in the USB. I can't do anything else unless I can plug in my phone. I've tried installing the drivers, everything. Nothing works.
Ayotom said:
The problem is none of my computers will detect my phone when I plug in the USB. I can't do anything else unless I can plug in my phone. I've tried installing the drivers, everything. Nothing works.
Click to expand...
Click to collapse
Try a brand new high quality USB cable. Once in download mode try the new cable and Odin back to stock - sfhubs one-clicks are the life saver here.
Also. Have you tried 'stock' recovery/factory reset? This may get you to a good place. Then you can install a good stock ROM with root and recovery (again check out sfhub's posts)
Factory reset via stock recovery:
Hold down the Volume Up and Power buttons simultaneously.
Continue holding the Volume Up and Power buttons until the Samsung Galaxy S II logo screen is displayed.
When the Galaxy S II logo screen is displayed, release the Power button but continue holding the Volume Up button until the Android System Recovery menu is displayed.
Once you are on the Android System Recovery menu, select the wipe data/factory reset option. Moving the selection up and down is done with the Volume Up and Volume Down buttons. Once you have the wipe data/factory reset option highlighted, you select it by touching the Home button.
Once you have chosen the factory reset option, you will see a confirmation screen. Highlight the Yes — delete all user data option and touch the Home button to select it.
The procees of wiping the phone should only take a few seconds and when it is finished, you will be returned to the Android System Recovery menu.
Highlight and select the reboot system now option.
I sound like a broken record on the USB cable thing in many of my posts but that has been a cause for so much frustration for me and countless others. And the stock cable from Sammy sucks ass too.
Good luck.
leaderbuilder said:
Try a brand new high quality USB cable. Once in download mode try the new cable and Odin back to stock - sfhubs one-clicks are the life saver here.
Also. Have you tried 'stock' recovery/factory reset? This may get you to a good place. Then you can install a good stock ROM with root and recovery (again check out sfhub's posts)
Factory reset via stock recovery:
Hold down the Volume Up and Power buttons simultaneously.
Continue holding the Volume Up and Power buttons until the Samsung Galaxy S II logo screen is displayed.
When the Galaxy S II logo screen is displayed, release the Power button but continue holding the Volume Up button until the Android System Recovery menu is displayed.
Once you are on the Android System Recovery menu, select the wipe data/factory reset option. Moving the selection up and down is done with the Volume Up and Volume Down buttons. Once you have the wipe data/factory reset option highlighted, you select it by touching the Home button.
Once you have chosen the factory reset option, you will see a confirmation screen. Highlight the Yes — delete all user data option and touch the Home button to select it.
The procees of wiping the phone should only take a few seconds and when it is finished, you will be returned to the Android System Recovery menu.
Highlight and select the reboot system now option.
I sound like a broken record on the USB cable thing in many of my posts but that has been a cause for so much frustration for me and countless others. And the stock cable from Sammy sucks ass too.
Good luck.
Click to expand...
Click to collapse
All the help is appreciated, I just wanted to let you know that. If my tone is bitter, I apologize. I use this phone for emergencies. I have indeed tried a high quality USB cable (just bought it) and it will not connect. I attempted to use Odin to restore my phone back to normal but the process was interrupted and caused my phone to be in the phone....!....computer screen with the message "firmware upgrade has encountered a problem" etc. I have attempted to plug in my phone while Odin opened. Nada. I've tried this in download mode using the button commands you have listed. I hope I'm not getting too annoying, I just feel so lost without my phone. Had everything on it. Sorry.
Ayotom said:
All the help is appreciated, I just wanted to let you know that. If my tone is bitter, I apologize. I use this phone for emergencies. I have indeed tried a high quality USB cable (just bought it) and it will not connect. I attempted to use Odin to restore my phone back to normal but the process was interrupted and caused my phone to be in the phone....!....computer screen with the message "firmware upgrade has encountered a problem" etc. I have attempted to plug in my phone while Odin opened. Nada. I've tried this in download mode using the button commands you have listed. I hope I'm not getting too annoying, I just feel so lost without my phone. Had everything on it. Sorry.
Click to expand...
Click to collapse
Are you sure you were installing the right firmware? If you flashed an international verion then you did kill the device and will need to get it jtag'd or replaced.
And exactly how did it 'get interupted? Did it just 'stop' or was it interupted by a power outage, or impatience of quiting the appolication?
How did you get root? Did you use sfhub's autoroot?
And what ROM did you use? Again sfhub's Stock One-Clicks are the safest and only way to go in my book.
Not trying to be a **** just trying to get a better understanding of what happened.
leaderbuilder said:
Are you sure you were installing the right firmware? If you flashed an international verion then you did kill the device and will need to get it jtag'd or replaced.
And exactly how did it 'get interupted? Did it just 'stop' or was it interupted by a power outage, or impatience of quiting the appolication?
How did you get root? Did you use sfhub's autoroot?
And what ROM did you use? Again sfhub's Stock One-Clicks are the safest and only way to go in my book.
Not trying to be a **** just trying to get a better understanding of what happened.
Click to expand...
Click to collapse
I might have accidentally installed the wrong firmware while attempting to repair it. Unless the different SII model firmware wouldn't hurt my phone, such as the AT&T SII.
And battery laptop died.
I had my brother root it. It used Syndicate.
And no worries dude, I'm just glad you're helping!
I am not sure if anyone specifically tried the att gs2 firmware, but since att is gsm, chances are it is the same as flashing the intl gs2 firmware. Flashing the latter would basically disable your usb port. It does sound like that is what happened.
If you still had cwm or root you could flash from the phone, but i think you mentioned you lost those too.
Your remaining options are probably jtag or return to sprint.
Thank you very much for your help. It seriously means a lot. Next time I'll pay more attention so I won't end up screwing things up again.
Well if you tried to use the AT&T SG II (SGH-I777) firmware you did probably kill it for sure. These phones are very specific and individual when it comes to the actual hardware and base firmwares. Kind of like putting diesel into a gas engine - good things don't happen. If you can't get it recognized at all no matter what you do a jtag service or simply taking it back and playing dumb might help. Here is a post with almost the same issue, just a different but still wrong firmware: http://forum.xda-developers.com/showthread.php?t=1506630 As for the guys at ACS they are very good too (most of them are around here too by the way). Spend some time and read a whole lot and you will learn what you need. Best bet if you simply can't get it recognized by Odin is to take it back to Sprint and play dumb and see if they get you a replacement. With insurance you should get it free without I think you pay $35.
This might sound a little crazy... But have you tried heimdall to see if you get dirrerent results?
Update
So I decided to check out the JTAG service. Guess what I found out? The dude that repairs phones lives 20 minutes away from me! I went over to his place yesterday and he fixed my phone right in front of me. It was totally worth the $50! His service is amazing, and he's friendly also. I would highly recommend him! Read my review (I'm John Montoya): http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
Thanks everyone for the help. Next time I'll be sure not to put in the wrong firmware!
LOL that's pretty funny having the mobiletechvideos guy living in your town, and getting to watch the JTAG repair in person. Not many people can say they've seen that in person, myself included. Glad you got it resolved.
Sent from my SPH-D710 using Tapatalk 2
Ayotom said:
So I decided to check out the JTAG service. Guess what I found out? The dude that repairs phones lives 20 minutes away from me! I went over to his place yesterday and he fixed my phone right in front of me. It was totally worth the $50! His service is amazing, and he's friendly also. I would highly recommend him! Read my review (I'm John Montoya): http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
Thanks everyone for the help. Next time I'll be sure not to put in the wrong firmware!
Click to expand...
Click to collapse
Glad to see you got it resolved! I've recommended that service to a few. Thanks for posting. Many don't so we never know the final outcome. This helps the whole community. Enjoy your great phone.
Ok before I go all beserk-o n ****... I Just had a 800 dollar error.... Code 7 after installing this rom latest version [ROM][XXBLG9][12/08]CriskeloRomV6►15 Toggles ►AROMA ►OTA►NANDROID ON LINE!... and now I cannot reboot or go into download mode all i get is the QHSUSB_DLOAD.... HELP!!!
I'm no novice but this is definitely getting to me... Been searching and all I get is da' normal Hard Bricked BS... If you know something I don't or have not come across so far let me know
By the way here are the steps I took
1. Download ROM & Kitchen
2. Reboot into CWM recovery 5.0.2.8
3. Install from internal SD the ROM only
4. CODE 7 fair "aka WTF!?!?!?!?!"
5. Bask in failure
No lights, No nothing just plug in DLOAD BS........... arghhhhhhhh
She was a GALAXY SPH-L710 SIII SPRINT and I was just coming from flashing, then rooting and installing Busy Box (installing that also) and doing Super User permissions and all... So I was setup correctly... Didn't see a reason to backup data but it wouldn't have mattered in this case if I did anyway... arghhhhhhhh
BTW it gave me a "GAPPS Error" when I was copying it over to the phone... Think that was internal memory failing and I flashed a partially copied ROM because of this.... I OK'd it and continued to power off and boot into recovery?????
OH... There wasn't a SD Card in the phone either... Not that I think that matters all that much..
Here's another thread I started which is the ROM page.... Thanks to all that chime in...
http://forum.xda-developers.com/showthread.php?p=32365555#post32365555
Post #1510
Wrong ROM for Device ??? i9300 vs SPH-L710 US oh f*** I believe I just hit it on the head????????
Your first step is to turn the phone off and try to get into download mode (Vol Down+Home+Power), If you can still enter download mode, you are soft bricked and can recover.
So IF you can access download mode, watch this video, All the links you need will be in the description. http://www.youtube.com/watch?v=ypmqJbZqOaU
Credit to qbking77 for the tutorial.
Yes, you flashed an international ROM for a US variant.
Follow the post above, good luck.
Sent from my BAKED SIII
QHSUSB_DLOAD=KISS OF DEATH. Congrats on tha new doorstop. Ignore the first post, I promise you aren't getting into download mode or any mode at that. The best unbrick service around http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Well, he did say he can't get in download mode, i guess there's no point telling him to do it in the conventional way. If that's the case, from what i read around your only chance is a usb jig to force that download mode (which you didn't say you tried). You can get them dirt cheap from ebay
http://www.ebay.com/itm/USB-Jig-Don...858103?pt=PDA_Accessories&hash=item46056ecc77
not recommending this link in particular, just showing they go for about a buck). For that price i'd def try it and you'll also get a very useful tool as benifit (reset flashing counters, etc...)
or even make one yourself (very easy too). Plenty of instructions about.
No harm in trying. Other than that, you'll need a repair center, i guess.
kaynpayn said:
Well, he did say he can't get in download mode, i guess there's no point telling him to do it in the conventional way. If that's the case, from what i read around your only chance is a usb jig to force that download mode (which you didn't say you tried). You can get them dirt cheap from ebay
http://www.ebay.com/itm/USB-Jig-Don...858103?pt=PDA_Accessories&hash=item46056ecc77
not recommending this link in particular, just showing they go for about a buck). For that price i'd def try it and you'll also get a very useful tool as benifit (reset flashing counters, etc...)
or even make one yourself (very easy too). Plenty of instructions about.
No harm in trying. Other than that, you'll need a repair center, i guess.
Click to expand...
Click to collapse
JIgs are no good either. They will not work here. Promise
He flashed an international rom which overwrote bootloader partitions with nonsense. The partitioning is f*cked now
Khilbron said:
Your first step is to turn the phone off and try to get into download mode (Vol Down+Home+Power), If you can still enter download mode, you are soft bricked and can recover.
So IF you can access download mode, watch this video, All the links you need will be in the description. http://www.youtube.com/watch?v=ypmqJbZqOaU
Credit to qbking77 for the tutorial.
Click to expand...
Click to collapse
Nice try but I already attempted to get into download mode of course. Good lookin' though... I know a soft brick but yeah that's easy as pie to deal with, I wish this was the case
Billard is correct! Exactly what I thought I did... Oh my bad for not throwing out there that I did try my JIG... It was the 3rd or 4th thing I did and was like damnit I think I just ****ed myself LMFAO and I actually laughed (but cried inside) LOLOLOLOLOL jajaja Thanks broski's... Now off to JTAG land
For others that (there are ALWAYS others) here ya go.... save ya some time:
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!
still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?
phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying: