Related
I have the Rogers HTC Dream which I bricked this morning.
It got to the state where holding camera + power did not bring up the fastboot menu, and holding home+power did not bring up the recovery menu. All I got was the dreaded Rogers logo.
1) Take out the battery and unplug the USB cable and wait 20 seconds
2) plug in the USB cable
3) The second you insert the battery your phone will automatically turn itself on. Therefore hold the camera button down while putting in the battery.
4) The phone should start up (again a black screen + Rogers logo) and you should see a red box in the top left corner saying "FAST USB"
5) The phone appears frozen, but now you can use ADP to send it a recovery.img.
Code:
fastboot boot recovery.img
For me I installed the recovery.img from "Haykuro's initial root kit" available in step 4 of this guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
6) After the fastboot command is finished your phone should automatically reset, and enter the Cyanogen recovery menu.
7) Now install the custom ROM as before
EDIT: After following these steps, I can now start my phone using CAMERA + POWER to get into the fastboot menu just like before I bricked my phone.
EDIT #2: I am currently running my phone with the cyanogen 4.1.999 ROM, so everything worked out for me in the end. I should probably mention that I did not "brick" my phone by flashing a new SPL while still running an older radio.img, so Im not sure how far this method will get some of you.
I'm afraid that your device was NOT BRICKED. You just had an incompatible or defective system image and didn't know how to use the bootloader.
THIS WILL NOT WORK on a device that is actually bricked.
martin_secretary said:
I have the Rogers HTC Dream which I bricked this morning.
It got to the state where holding camera + power did not bring up the fastboot menu, and holding home+power did not bring up the recovery menu. All I got was the dreaded Rogers logo.
1) Take out the battery and unplug the USB cable and wait 20 seconds
2) plug in the USB cable
3) The second you insert the battery your phone will automatically turn itself on. Therefore hold the camera button down while putting in the battery.
4) The phone should start up and you should see a red box in the top left corner saying "FAST USB"
5) The phone appears frozen, but now you can use ADP to send it a recovery.img.
Code:
fastboot boot recovery.img
For me I installed the recovery.img from "Haykuro's initial root kit" available in step 4 of this guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
6) After the fastboot command is finished your phone should automatically reset, and enter the Cyanogen recovery menu.
7)????
I am stuck here, Im still not sure how to proceed to fix my phone, but I know this will help others get to this point, and maybe someone with more expertise can point out where to move on from here.
EDIT: After following these steps, I can now start my phone using CAMERA + POWER to get into the fastboot menu just like before I bricked my phone.
Click to expand...
Click to collapse
Perhaps you are right and it was not "truly bricked", but it was in a state where home+power and camera+power did nothing.
Anyone on these forums that would describe this problem would automatically be told they have a new paperweight. Im sure many people just have the same problem as me.
From a POWEROFF state, press and hole HOME (for recovery) or BACK (for fastboot), then press the power button while continuing to hold the HOME or BACK button. That is all there is to it. No magic.
lbcoder said:
I'm afraid that your device was NOT BRICKED. You just had an incompatible or defective system image and didn't know how to use the bootloader.
THIS WILL NOT WORK on a device that is actually bricked.
Click to expand...
Click to collapse
have you personally tried this?
lbcoder said:
From a POWEROFF state, press and hole HOME (for recovery) or BACK (for fastboot), then press the power button while continuing to hold the HOME or BACK button. That is all there is to it. No magic.
Click to expand...
Click to collapse
No, that is not magic, but what is really impressive is that in the original post it is stated that
It got to the state where holding camera + power did not bring up the fastboot menu, and holding home+power did not bring up the recovery menu. All I got was the dreaded Rogers logo.
Click to expand...
Click to collapse
, and if the OP was actually able to find a way around this, it is the first time I have heard. Since registering, I have read numerous posts on XDA stating that if you cannot get to recovery by home+power and cannot get to fastboot via home+camera, then your phone is "probably bricked". I have yet to read one post with a solution to this situation (not to say they do not exist, just that they are not easy to find if they do exist). I think the OP found something that could be quite useful for many people that find themselves in this situation (such as after flashing the wrong radio for hero).
Now having said that, I must also say that your phone was not bricked. If it were bricked, you could not have made it this far. Thus, it either the case that this was a fluke, or the (quite wonderful, but usually with a low probability) case that you stumbled upon something new, and the concept of a "bricked G1" will need to be redefined.
We need more people in this situation to try this method, that will be the only way to really know what this is.
cloverdale said:
No, that is not magic, but what is really impressive is that in the original post it is stated that , and if the OP was actually able to find a way around this, it is the first time I have heard. Since registering, I have read numerous posts on XDA stating that if you cannot get to recovery by home+power and cannot get to fastboot via home+camera, then your phone is "probably bricked". I have yet to read one post with a solution to this situation (not to say they do not exist, just that they are not easy to find if they do exist). I think the OP found something that could be quite useful for many people that find themselves in this situation (such as after flashing the wrong radio for hero).
Now having said that, I must also say that your phone was not bricked. If it were bricked, you could not have made it this far. Thus, it either the case that this was a fluke, or the (quite wonderful, but usually with a low probability) case that you stumbled upon something new, and the concept of a "bricked G1" will need to be redefined.
We need more people in this situation to try this method, that will be the only way to really know what this is.
Click to expand...
Click to collapse
As I said, from a POWER OFF STATE.
And no, you do NOT hold home+power, you hold HOME, then PRESS AND RELEASE power while continuing to hold HOME.
He didn't get by anything. He simply didn't push the buttons properly (i.e. pressed them *too late* or while the device was STILL POWERED ON.
lbcoder said:
As I said, from a POWER OFF STATE.
And no, you do NOT hold home+power, you hold HOME, then PRESS AND RELEASE power while continuing to hold HOME.
He didn't get by anything. He simply didn't push the buttons properly (i.e. pressed them *too late* or while the device was STILL POWERED ON.
Click to expand...
Click to collapse
Why are you so sure about yourself about what buttons I pressed? I booted into recovery mode and fastboot mode MANY times before I "bricked" my phone, so i know how to press the buttons....
yo lbcoder i hold home+power at the same time for a LONG time and it still goes to recovery. Same with camera + power. As long as you hold home before you hold/press power you're good to go. We need more people to tryout this method.
I wonder why lbcoder is so sure of what hes saying....hes been wrong a lot of times in his previous postings...
I got a solution for this. How bout the OP or someone else actually brick there phone and try this method. If they get it back working then hey theres a solution but if not then you know it really wasn't a brick. So who wants a brick.
Plus I would like to know what was the initial problem to make the OP think he had a brick.
B-man007 said:
I wonder why lbcoder is so sure of what hes saying....hes been wrong a lot of times in his previous postings...
Click to expand...
Click to collapse
If you're going to make such an absurd statement, you better damn well be prepared to back it up.
But since you can't, I hereby nullify your statement and reserve the right to do so for anything you ever state.
@martin:
How can I be sure? Because after you tried several times it eventually worked. You didn't do anything differently the last time except pull the battery, which will have no effect except that you can be certain that you are starting from a fully powered off state. That being the difference proves that one of the following things happened on every one of your previous attempts;
1) You pushed the button too late in the boot sequence (everybody's done this a few times, sometimes several times in a row),
2) The device was never actually powered off. Yes, it can have the appearance of being off without actually being off.
As for other's trying this with their bricks, certainly it might help a very few people out, but no, this is not a magical fix for an IPL CRASH. If the SPL is simply not compatible with the IPL, then no matter what you try, the IPL will never be able to start the SPL. And yes, you MUST start the SPL since that is where the bootloader is, and the home or back or no button signals the bootloader on which way to boot (multiboot). It can go into fastboot (payload within SPL), recovery (recovery partition), normal (boot partition), etc.
lbcoder said:
If you're going to make such an absurd statement, you better damn well be prepared to back it up.
But since you can't, I hereby nullify your statement and reserve the right to do so for anything you ever state.
@martin:
How can I be sure? Because after you tried several times it eventually worked. You didn't do anything differently the last time except pull the battery, which will have no effect except that you can be certain that you are starting from a fully powered off state. That being the difference proves that one of the following things happened on every one of your previous attempts;
1) You pushed the button too late in the boot sequence (everybody's done this a few times, sometimes several times in a row),
2) The device was never actually powered off. Yes, it can have the appearance of being off without actually being off.
As for other's trying this with their bricks, certainly it might help a very few people out, but no, this is not a magical fix for an IPL CRASH. If the SPL is simply not compatible with the IPL, then no matter what you try, the IPL will never be able to start the SPL. And yes, you MUST start the SPL since that is where the bootloader is, and the home or back or no button signals the bootloader on which way to boot (multiboot). It can go into fastboot (payload within SPL), recovery (recovery partition), normal (boot partition), etc.
Click to expand...
Click to collapse
I've updated my post to state that I did not brick my phone by using an incompatible SPL. However I am saying my phone was in the state where I could not access fast boot or recovery mode.
Look through this thread: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
and see how many people say they can't access fastboot or recovery anymore....this is the same guide I followed and screwed up my phone. There is more than one way to brick your phone, and I think I found a way to unbrick it in this special case.
martin_secretary said:
I've updated my post to state that I did not brick my phone by using an incompatible SPL. However I am saying my phone was in the state where I could not access fast boot or recovery mode.
Look through this thread: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
and see how many people say they can't access fastboot or recovery anymore....this is the same guide I followed and screwed up my phone. There is more than one way to brick your phone, and I think I found a way to unbrick it in this special case.
Click to expand...
Click to collapse
Do you have any idea what proportion of "users" can't even press the "enter" button when told to?
And FYI: that thread talks about installing the deathspl (the one that usually makes your phone into a paperweight). Regardless of their statement that it is compatible, it is actually quite unknown/undocumented and therefore compatibility with it is NEVER certain.
The fact that you only THOUGHT you bricked your phone means that you are lucky. Lots of people have ACTUALLY bricked with that SPL.
lbcoder said:
If you're going to make such an absurd statement, you better damn well be prepared to back it up.
But since you can't, I hereby nullify your statement and reserve the right to do so for anything you ever state.
Click to expand...
Click to collapse
lbcoder said:
Why the app? winanything will BSOD just by looking at it.
Click to expand...
Click to collapse
I'm looking at windows right now...and it didnt bluescreen.....
Do you have any idea what proportion of "users" can't even press the "enter" button when told to?
Click to expand...
Click to collapse
Look at how many people use a rooted G1, then look at how many can't..... its a very low proportion. Just because you see some posts in which people complain about not being able to use their phone doesnt make it an accurate representation of "users"
Code:
The fact that you only THOUGHT you bricked your phone means that you are lucky. Lots of people have ACTUALLY bricked with that SPL.
ok, first off....hes using a rogers phones. The buttons are much easier to press than the g1. I highly doubt he would have messed up that many times. And if he couldn't access the SPL or Recovery, its effectively a brick for him. What does it matter how it happened if it did happen. a bad ipl/spl flash is not the only way to brick a phone (though its the most common and most documented) There are many factors to this "brick" that you may or may not know about
why the heck are you sitting here and arguing the definition of a brick. Hes trying to help people who have messed up their phone and giving them one more solution to try to fix their phone before spending money on replacing it. If it doesnt work, so be it. if it worked for even one person, its officially worthwhile for the post to be there.
there is no need to sit there criticizing someone whos trying to help by repeatedly posting the same thing over and over there. I think that your judging him because of his low post count. Martin has greater than adequate knowledge of the dream. but you wouldnt know that because anyone that doesn't have a post count > 100 "can't even press the 'enter' button when told to"
martin_secretary said:
I have the Rogers HTC Dream which I bricked this morning.
It got to the state where holding camera + power did not bring up the fastboot menu, and holding home+power did not bring up the recovery menu. All I got was the dreaded Rogers logo.
1) Take out the battery and unplug the USB cable and wait 20 seconds
2) plug in the USB cable
3) The second you insert the battery your phone will automatically turn itself on. Therefore hold the camera button down while putting in the battery.
4) The phone should start up (again a black screen + Rogers logo) and you should see a red box in the top left corner saying "FAST USB"
5) The phone appears frozen, but now you can use ADP to send it a recovery.img.
Code:
fastboot boot recovery.img
For me I installed the recovery.img from "Haykuro's initial root kit" available in step 4 of this guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
6) After the fastboot command is finished your phone should automatically reset, and enter the Cyanogen recovery menu.
7) Now install the custom ROM as before
EDIT: After following these steps, I can now start my phone using CAMERA + POWER to get into the fastboot menu just like before I bricked my phone.
EDIT #2: I am currently running my phone with the cyanogen 4.1.999 ROM, so everything worked out for me in the end. I should probably mention that I did not "brick" my phone by flashing a new SPL while still running an older radio.img, so Im not sure how far this method will get some of you.
Click to expand...
Click to collapse
i have G1 its stck on G1 screen ... i try to do as you did but wont work at all ???
i cant boot or flashe from sd card ...
any help ?
B-man007 said:
I'm looking at windows right now...and it didnt bluescreen.....
Click to expand...
Click to collapse
Are you so absolutely dense that you don't know what a JOKE is?
Look at how many people use a rooted G1, then look at how many can't..... its a very low proportion. Just because you see some posts in which people complain about not being able to use their phone doesnt make it an accurate representation of "users"
Click to expand...
Click to collapse
I'm talking about users IN GENERAL. I.e. forget about phones, forget about root. Most users are (from the programmer's perspective) absolute MORONS who are barely able to breath on their own. Give a "rooted" phone to a NORMAL user (i.e. a teenage girl), do you expect them to be able to get anything extra out of it? How about trying to talk an average (that's *AVERAGE*, not a geek) teenage girl through the process of rooting her phone? You think that will go well? Definitely not.
ok, first off....hes using a rogers phones. The buttons are much easier to press than the g1.
Click to expand...
Click to collapse
That is absolutely not relevant in any way. If he is pressing the buttons WITH THE THING POWERED ON, then it won't work, regardless of how "easy" the buttons are to press.
I highly doubt he would have messed up that many times.
Click to expand...
Click to collapse
You are therefore judging him to be of equal technical aptitude to yourself. What do you base this on? The first rule of anything technical is to assume that your end users are complete morons. If they aren't, then so much the better, but you can't make that assumption.
And if he couldn't access the SPL or Recovery, its effectively a brick for him. What does it matter how it happened if it did happen. a bad ipl/spl flash is not the only way to brick a phone (though its the most common and most documented) There are many factors to this "brick" that you may or may not know about
Click to expand...
Click to collapse
Fact: If the device is not physically damaged, contains a compatible and valid IPL and a compatible and valid SPL, then it *must* boot up to SPL *as long as the correct procedure is followed*.
The ONLY possible ways to make the device non-functional beyond the possibility of correcting using standard procedure is to have physical damage, corrupt or incompatible IPL, or corrupt or incompatible SPL. There are no other possibilities.
why the heck are you sitting here and arguing the definition of a brick. Hes trying to help people who have messed up their phone and giving them one more solution to try to fix their phone before spending money on replacing it. If it doesnt work, so be it. if it worked for even one person, its officially worthwhile for the post to be there.
Click to expand...
Click to collapse
No, he is not providing any information that is not already available for anyone to try. He did nothing at all beyond standard procedure. In his first attempts, he clearly failed to follow standard procedure, in his final attempt, he successfully followed standard procedure and was able to access recovery. This thread is misleading as it offers a solution which, quite frankly, doesn't exist.
there is no need to sit there criticizing someone whos trying to help by repeatedly posting the same thing over and over there. I think that your judging him because of his low post count.
Click to expand...
Click to collapse
I post to correct. I post to inform against useless information.
Martin has greater than adequate knowledge of the dream.
Click to expand...
Click to collapse
Again, not to put him down, but HOW DO YOU KNOW?
but you wouldnt know that because anyone that doesn't have a post count > 100 "can't even press the 'enter' button when told to"
Click to expand...
Click to collapse
Back to basics. You can absolutely NOT assume that everyone else knows what YOU know. You *MUST* assume that they know NOTHING.
Post count? Tell me where you got the impression that I even bothered to look at his post count. I don't care about post count. If the post makes sense and introduced NEW INFORMATION, then the author is making a worthy contribution. If they are just repeating the same crap that *everybody already knows*, then it is a worthless or potentially damaging contribution.
Duh, my phone don't work. I tried and tried and it didn't work. And then finally I followed the directions and it worked.
lbcoder: I am currently a software programmer working for the top 5 biggest tech companies in North America. I am also currently doing my masters in Computer Engineering. Every post of yours has hinted that you think I'm a moron, and you've been very insulting and unhelpful on this message board.
I've pointed out to you many times I did NOT brick my phone by flashing an incorrect SPL. Yes we get it, if an incorrect SPL has been flashed then there is probably no possible way to recover the phone.
However I'm saying that I bricked my phone some other way, and for some reason you wont get that into your head. Im beginning to wonder who the real "moron" is here.
This thread is meant to try and help people whose phones are in the same state mine was. You're just being an ass and hijacking this thread.
P.S. I bet B-man007 has his doubts about whether this method actually works. Yet hes taking a wait-and-see approach, not a calleveryoneamoroncuzIthinkimright approach.
iyass said:
i have G1 its stck on G1 screen ... i try to do as you did but wont work at all ???
i cant boot or flashe from sd card ...
any help ?
Click to expand...
Click to collapse
How did you brick your phone? What guide did you follow, and what step did it fail at?
after mailing SAMSUNG by Mr.Alzubair
from ce4arab website
about the Death screen
this is the answer :
-----
Dear Alzubair ,
Thank you for contacting Samsung Electronics.
Reference number:2104286715
Regarding your case, kindly note that the image you have displayed on
the screen of your phone, indicates that the device has entered the
Recovery Mode. The reason this happened, is because you have tried to
update the device’s Firmware, which isn’t actually released yet, and
that’s the reason why the Software crashed as well.
In order to get out of the Recovery Mode, please follow the steps below:
Recovery Process
1.Remove the battery and reinstall it. Power On your Phone
- Phone display “Connection picture for Phone to PC”
2. Recovery Mode in Kies
If upgrade failed in upgrade step, you can see next Pop-Up
- Select "Yes”
Firmware Upgrade program progress to recovery mode.
3. Select "Recovery" button.
4. Read the caution and check “all information has been verified”
- After this, it’s same with Firmware update Process
5. Click “Next”
- Firmwareversion display
- Firmware file is downloaded to PC
6. Firmware update
- After Firmware downloaded, Click “Next”
- Firmware update start
Caution
- Never disconnect or turn off the
device in thisstep
- If so, recover the phone refer to
recovery section
7.Complete
- After Firmware update complete, the device reboot
automatically
- Click “Next” Button
To do this manually instead of using Kies, please click on the Power
button, the Volume down button and the middle button all together all at
the same time. The phone would flash for 2 times, and on the 3rd time,
please remove your hands fromthe phone, and it should boot up normally.
I hope this has been of some assistance to you. If you do have any
further queries, please do not hesitate to contact us quoting your 210-4286715
reference number.
Kind Regards,
Aya Smith
Samsung Electronics UK
Customer Communication Centre
Tel.: 0845 726 7864 (All calls charged at Local Rate)
Homepage: samsung.com
[Product] GT-I9000
The reason this happened, is because you have tried to
update the device’s Firmware, which isn’t actually released yet, and
that’s the reason why the Software crashed as well.
Click to expand...
Click to collapse
Bwahahahhaahahahahh!!
cheetah2k said:
Bwahahahhaahahahahh!!
Click to expand...
Click to collapse
LOL XD
at least they help me
I just tried it ( by the Manual way ) and it Works
so this works on the semi-bricked, no 3-button combo enabled phones ??
.. let's say, after a bad/failed bootloader flash ?
someone please confirm ?
later edit:
from what I understand after reading this, Kies can force any (Phone--!--PC) SGS into recovery and/or download mode?
if so, can we "extract" this feature and make it into a stand alone solution for half-bricked phones?
That's not a real black screen, I got one and my phone got the BSOD: No possibility to power on, no charging, nothing.
The "phone ! computer" is just a semi brick, get back to download mode and reflash with odin...
But thanks for the info indeed.
franklin01 said:
The "phone ! computer" is just a semi brick, get back to download mode and reflash with odin...
Click to expand...
Click to collapse
Some SGSs can't access download mode from that screen because of the proper bootloader that's missing. (3 button combo fix needed, not so safe)
wish samsung also adds a feature to kies that fixes the IMEI =D
franklin01 said:
That's not a real black screen, I got one and my phone got the BSOD: No possibility to power on, no charging, nothing.
The "phone ! computer" is just a semi brick, get back to download mode and reflash with odin...
But thanks for the info indeed.
Click to expand...
Click to collapse
2day i triad it two times and it works
but from what i understand same thing happened to me today ..
i did the 3 times flashing way :
BE SURE THAT YOU disconnect THE CABLE!!
To do this manually instead of using Kies, please click on the Power
button, the Volume down button and the middle button all together all at
the same time. The phone would flash for 2 times, and on the 3rd time,
please remove your hands fromthe phone, and it should boot up normally.
Then its work and downloading mode appear i installed an official Ver. by odin ( check on Re-Partition ) then it will work (work for me after the same thing that happened : No possibility to power on, no charging, nothing. )
Does this means that the phone has a secondary bootloader or what I dont get it, I already sent my phone to samsung so I cant try, I had my phone bricked stuck at a black screen after the S logo.
hang on... so it sounds like samsung is saying that phones that dont go into download mode straight away from vol-down, home and power need to keep holding the power button until the power cycles 2 times, then let go on the third?
i cant test it now because after i bricked my phone (black screen no power on or charge) i sent it back and i got a new motherboard with 3-button enabled... but this does make sense because when i had a 3-button disabled phone previously i did manage to get it into download mode from the phone-!-computer screen by trying different timings. it took a long time but eventually worked.
so it would seem if this is the case, that it is just a different boot loader and a different key combination to access download mode, but working nevertheless?
can someone test this?
Cant believe it, if the phone does has a secondary bootloader then it cannot be bricked forever.
Sent from my GT-I9000 using XDA App
stephengoo said:
Cant believe it, if the phone does has a secondary bootloader then it cannot be bricked forever.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
We already knew it had a secondary boot-loader...
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions
This is what is patched to hotfix the 3BR in disabled phones.
3 times flashing way wont work for me, and at Recovery in Kies i cant see my Device!
Absolutly no USB!!!!
Sorry Guys!
So this forced download mode can be possible...
This guy here tried hard to explain same thing:
http://forum.xda-developers.com/showthread.php?t=812933
do you think it will work with korean version galaxy s?
No-Exit said:
3. Select "Recovery" button.
4. Read the caution and check “all information has been verified”
- After this, it’s same with Firmware update Process
To do this manually instead of using Kies, please click on the Power
button, the Volume down button and the middle button all together all at
the same time. The phone would flash for 2 times, and on the 3rd time,
please remove your hands fromthe phone, and it should boot up normally.
[Product] GT-I9000
Click to expand...
Click to collapse
"all information has bee verified" means put phone in download mode and connect it to PC (can't do it without working 3 buttons combo).
"manually instead of using Kies" = same thing, doesn't work without 3 buttons combo.
This doesn't works if you didn't have 3 buttons combo enabled. I used heat trick instead and then patch aires P-SBL.
I sent my phone back because of this black screen of death. I could get into Download mode, and the other (vol-up) mode too, but no upgrading or changing firmwares worked to fix it. And Kies didn't see it, though Odin eventually did.
Wondering now if the Black Screen of Death was fixable after all, but then would Kies have to recognize it first?
I have a phone ! pc bricked phone right in front of me, I've tried this and a million other combinations, nothing works. I'm not being super pessimistic or anything it really doesn't work. I've left it with a phone repair store overnight and they couldn't fix it either. Im going to visit samsung/optus tomorrow.
edit:
I also want to point out that that message contains some horrible english supposedly from samsung UK
d47:
I am exactly in your shoes. Even with the overnight leave at a GSM repair booth-thingy. Im also considering handing it back to the retailer, but havent tried the heating up trick yet... Maybe its worth a try ?
If your phone doesn’t boot into download mode and you have a black screen after flashing froyo heres how you unbrick it, it worked for me.
Step 1 – Prepare odin with the firmware u want to flash (in my case was I5800XXJPM) and get it ready to go;
Step 2 – Remove battery, SIM and SD card, next connect your galaxy 3 to the computer;
Step 3 – Hold Volume down + Power + Home button at the same time;
Step 4 – Insert the battery and wait a bit;
Step 5 – At this point Odin should have detected your SG3 ( Yellow rectangle should appear in your );
Step 6 – Click Start button in Odin and wait about 5 min.
If all goes well it should come back to life.
If You Find It Useful Click Thanks.
When you said Brick, it's Hardbrick or SoftBrick ?
Darius_AWS said:
When you said Brick, it's Hardbrick or SoftBrick ?
Click to expand...
Click to collapse
"If your phone doesn’t boot into download mode and you have a black screen after flashing froyo" => hard brick...
kyrillos13 said:
"If your phone doesn’t boot into download mode and you have a black screen after flashing froyo" => hard brick...
Click to expand...
Click to collapse
Lestat should try it
dude u shud have made this thread 3 months ago it wud have been very helpfull for me coz it wud save my 2hardbricks......hard luck though for me i got my motherboard chnged both times and the 2nd time they gave me i5800 motherboard but my model is i5801...l...so bloody hell samsung service centres......and i think they have given me a 2nd hand motherboard this time..,.....
Now no need to worry about hard brick. Do What you want to do with Your Samsung devices.
The above tutorial work with every device which support odin firmware flashing.
shreyasharusia said:
Now no need to worry about hard brick. Do What you want to do with Your Samsung devices.
The above tutorial work with every device which support odin firmware flashing.
Click to expand...
Click to collapse
That's a relaxing thought!
You can skip step 3 - after reboot phone WILL go thrue download phase - this is how the bootloader is built. Just connect your phone, switch it on and after you PC Odin detected it push START - that`s it!!!
aarrun said:
dude u shud have made this thread 3 months ago it wud have been very helpfull for me coz it wud save my 2hardbricks......hard luck though for me i got my motherboard chnged both times and the 2nd time they gave me i5800 motherboard but my model is i5801...l...so bloody hell samsung service centres......and i think they have given me a 2nd hand motherboard this time..,.....
Click to expand...
Click to collapse
they always replace with used motherboards....
had to wait one month for them to do that
dude you saved my ass. Thank you so much.
alcsilian said:
dude you saved my ass. Thank you so much.
Click to expand...
Click to collapse
did u really hard bricked and saved by this method?
Does its really working?
Unfortunately it is not working for me... After yesterday's attempting to upgrade to froyo I have a brick... Holding power down, trying enter the download menu, connecting USB cable - nothing happening - black screen. I have tried both methods described above and nothing happened
Hmmmm.... Im sorry if im asking something wihtout trying...
But is it really possible to boot the phone into Download Mode/Recovery/whatever WITHOUT the battery???
jinxskore said:
Hmmmm.... Im sorry if im asking something wihtout trying...
But is it really possible to boot the phone into Download Mode/Recovery/whatever WITHOUT the battery???
Click to expand...
Click to collapse
Who said without the battery. Connect the mobile to computer without battery,press and held both the volume rocker and then insert the battery . You will get the downloading mode and odin will detect your phone and then flash.
shreyasharusia said:
If your phone doesn’t boot into download mode and you have a black screen after flashing froyo heres how you unbrick it, it worked for me.
Step 1 – Prepare odin with the firmware u want to flash (in my case was I5800XXJPM) and get it ready to go;
Step 2 – Remove battery, SIM and SD card, next connect your galaxy 3 to the computer;
Step 3 – Hold Volume down + Power + Home button at the same time;
Step 4 – Insert the battery and wait a bit;
Step 5 – At this point Odin should have detected your SG3 ( Yellow rectangle should appear in your );
Step 6 – Click Start button in Odin and wait about 5 min.
If all goes well it should come back to life.
If You Find It Useful Click Thanks.
Click to expand...
Click to collapse
Im sorry. I dont mean to prove you or anyone wrong. Maybe i just got things wrong...
Step 2 says to remove battery.
Step 3 basically means trying to start the phone into Download Mode.
Step 4 Well, if its only me, i cant imagine Holding Volume Down+Home+Power buttons and manage to insert the battery at the same time.
NOTE: I just asked if something was possible. Not particularly in accordance to your Tut. I just asked a general question. Sorry again if i offended anyone.
EDIT: The main reason was my curiosity, if the phone could work on power from the USB. LoL
i think it powers the phone without the battery through the USB cable from PC. never tried it though but i think it works since the battery charges while plugged in usb cable (this means it has juice).
I think its starting download mode when you put in the battery :S
If you are really that curious as to whether it will enter download mode just on usb power you dont have to wait for your phone to get hard bricked, just try it.
shreyasharusia said:
Now no need to worry about hard brick. Do What you want to do with Your Samsung devices.
The above tutorial work with every device which support odin firmware flashing.
Click to expand...
Click to collapse
same here bro. i too changed my motherboard from samsung service center
and i dont this one is same as the previous one
unfortunately that doesn't work for me... stupidly enough, I tried to change something in the firmware file (just the logo.png file), and then it got stuck during flashing in Odin. So even more stupidly, I disconnected the phone, and when it didn't turn off I just took out the battery, and since then it behaves as a total brick, and doesn't even show any sign of life when I try to turn it on, or when I try the above mentioned methods (Odin doesn't detect anything).
Any other ideas, or things that I may have done wrong trying to revive it? and do you think that the JIG method could work?
thanks
I somehow lost the backup of my premangostate after updating to mango. I'm having issues with my device overheating and I need to mail it in to AT&T. But doesn't the Mango beta technically void your warranty? If it does, I need to revert to premango in order to send it in... what should I do? I've tried everything. I downloaded a ROM but I don't know how to use it! HELP!!
eaglesfreak53 said:
I somehow lost the backup of my premangostate after updating to mango. I'm having issues with my device overheating and I need to mail it in to AT&T. But doesn't the Mango beta technically void your warranty? If it does, I need to revert to premango in order to send it in... what should I do? I've tried everything. I downloaded a ROM but I don't know how to use it! HELP!!
Click to expand...
Click to collapse
It does void it. Flash UCJK2 ROM from here. Just tell them you didn't update.
EnderPsp said:
It does void it. Flash UCJK2 ROM from here. Just tell them you didn't update.
Click to expand...
Click to collapse
Do you think you could post a step by step of what to do? I tried going through the forum you suggested but had no luck following the steps. I'm a US AT&T customer.
eaglesfreak53 said:
Do you think you could post a step by step of what to do? I tried going through the forum you suggested but had no luck following the steps. I'm a US AT&T customer.
Click to expand...
Click to collapse
There isn't one for Focus but if you follow the step by step guide for Omnia 7 with the Focus Rom, you should be okay as it's exactly the same. Just use the Focus UCJK2 Rom instead of the Omnia7 one.
Here's the short version:
You will not need the "Samsung WP7 Flash Program" as it is included in the ROM (Samsung-i917-Focus-firmware-UCJK2-ATT-USA.exe).
Install Samsung Mobile USB Drivers v5.2
Put the phone in download mode. Make sure battery is at least 80% when you do.
Turn off the phone
Turn on the phone, holding down the Power + Volume UP + Camera buttons simultaneously.
When the phone turns on, release the power button.
A yellow triangle with an exclamation mark and a "download mode” message should appear.
(there are 2 ways to get out of this mode: flash a rom or remove the battery).
1. Copy "Samsung-i917-Focus-firmware-UCJK2-ATT-USA.exe" in a new folder and run it (Install). After running you will see these files:
signed_CSC_Cetus_ATT_i917ATTJK2.csc
signed_eboot_Cetus_ATT.eb0
signed_pda_Cetus_ATT.nb0
signed_phone_Cetus_ATT.bin
WP7 Downloader Ver 7.21 for All Device (Publish version).exe
WP7_Downloader_Ver_7.05_for_Retail_Device_(Product_Force_Select_MD5_X).exe
The fhash program you need to run is
WP7_Downloader_Ver_7.05_for_Retail_Device_(Product_Force_Select_MD5_X).exe
2. Run it and load in it the files in this folder (click Phone, Eboot, PDA, CSC)
3. If the port isn't green, disconnect the phone from USB and reconnect.
You should be good to go with all this.
eaglesfreak53 said:
Do you think you could post a step by step of what to do? I tried going through the forum you suggested but had no luck following the steps. I'm a US AT&T customer.
Click to expand...
Click to collapse
I'll be reflashing my Rogers Samsung Focus yet again since I've been trying to change MMS settings so it will work with FIDO. Anyway, I'll be reflashing this weekend. PM me if you want some walk through steps.
[Q]Restoring backup after flashing rom
Hi,
I have a At&t samsung focus running 8107 and phone's power button started acting weird. If i press it nothing happen at first, then the slide down to power off appear. I would press back but it would shut off anyways. It wouldn't reboot right and usually took about 20 tries to boot it. I have two backups saved one mango beta and one for current version. The problem got worse (wouldn't boot at all unless on usb power) so i restored it to my current version backup. Everything worked but after a week the problem came back and the phone was dead. I decided to flash it to factory rom (had problems getting it to boot to rebuild) but I eventually got it to boot. The power button still did nothing. I updated it back to 8107 and tried to restore to my backup. I keep getting error code 801812E0. My question is do you have to use the same update path to restore a backup? I had the mango beta, refresh, then cleanup to get to 7720 Mango build. The second time around I used official update path. Do you think this is hardware related?
Thanks in advance
From your description, it sounds like your power button is getting stuck in the pressed position. "Always Pressed". Occasionally, when messing with it, it will release. Also, when plugged in, that forces it to start up.
Try cleaning around the button, or remove any cases/screen protectors that might be sticking it down. If that does not work, you might need to take apart to clean or replace the button. Only attempt if you are comfortable with that type of job, otherwise, send in for repair.
Thanks for the quick response. I will try that.
Also would the power button being stuck affect the hard reset menu and download mode? I can still access download mode but the hard reset menu disappears after about 10 seconds. The only way I can reboot the phone is to plug into USB power via computer and touch the metal springs where the battery connects with a tweezers.
xyzyzyxx99 said:
Also would the power button being stuck affect the hard reset menu and download mode? I can still access download mode but the hard reset menu disappears after about 10 seconds.
Click to expand...
Click to collapse
Yes. If you hold the power button in Any mode, it forces a shutdown after a few seconds.
Took the phone apart and cleaned around the button. Still won't boot, is it possible the phone's drivers to communicate with the power button are bad? And any idea why my backups failed to restore after flashing the rom?
xyzyzyxx99 said:
Took the phone apart and cleaned around the button. Still won't boot, is it possible the phone's drivers to communicate with the power button are bad? And any idea why my backups failed to restore after flashing the rom?
Click to expand...
Click to collapse
I think this has gotten off topic from the original thread. I'll send you a private message, and we can continue there. I've been around a while, so I might get into trouble keeping it going here, since I should know better.
Does anyone have a working link to download the Samsung Focus USB drivers?
All the multiupload links are down and i am stuck with a bricked phone.
Mirror or alternate link appreciated..
Thanks
NilayS said:
Does anyone have a working link to download the Samsung Focus USB drivers?
All the multiupload links are down and i am stuck with a bricked phone.
Mirror or alternate link appreciated..
Thanks
Click to expand...
Click to collapse
Download Samsung drivers from here.
Can I get the long version of flashing a Focus I917. Yes noob, if by chance there are some pics would be helpful also! Thanks in advance!
SteelLife said:
Can I get the long version of flashing a Focus I917. Yes noob, if by chance there are some pics would be helpful also! Thanks in advance!
Click to expand...
Click to collapse
Follow this post.
Alright, so I had just installed TWRP and Magisk, made backups of my ROM and EFS, everything is going well. I go to install LuisROM.
I go into TWRP, click install, and click on the LuisROM package. Says it doesn't find a digest file, but installation is continuing, so I figure it's no big deal. Reboot, and I get the Unlocked Bootloader warning that I've just recently began to familiarize myself with, but at the bottom of the screen, say the bottom half inch or so, is crazy static. Completely jumbled nonsense. It's not animated or anything, just randomly colored static pixels. Odd.
Next screen? Black. Nothing. Plugged into the computer and the she makes the familiar beeps that a device has been plugged in. For a time I find myself stuck in a boot loop trying to get back into recovery via power + vol down, but nothing. Seems to instant reboot back into the warning then black screen.
Now: I can't even seem to turn the phone off! If I plug into the laptop, I hear the familiar sounds, but can't do anything about it that I know of. If I hold the power button for 30-60 seconds: nothing.
I saw a few posts on here saying something about a complete power drain and recharge, so that's my next best guess, but I'm hoping someone else has a better idea.
lynxon said:
Alright, so I had just installed TWRP and Magisk, made backups of my ROM and EFS, everything is going well. I go to install LuisROM.
I go into TWRP, click install, and click on the LuisROM package. Says it doesn't find a digest file, but installation is continuing, so I figure it's no big deal. Reboot, and I get the Unlocked Bootloader warning that I've just recently began to familiarize myself with, but at the bottom of the screen, say the bottom half inch or so, is crazy static. Completely jumbled nonsense. It's not animated or anything, just randomly colored static pixels. Odd.
Next screen? Black. Nothing. Plugged into the computer and the she makes the familiar beeps that a device has been plugged in. For a time I find myself stuck in a boot loop trying to get back into recovery via power + vol down, but nothing. Seems to instant reboot back into the warning then black screen.
Now: I can't even seem to turn the phone off! If I plug into the laptop, I hear the familiar sounds, but can't do anything about it that I know of. If I hold the power button for 30-60 seconds: nothing.
I saw a few posts on here saying something about a complete power drain and recharge, so that's my next best guess, but I'm hoping someone else has a better idea.
Click to expand...
Click to collapse
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
DarthVader said:
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
Click to expand...
Click to collapse
The phone is currently stuck in a state where the screen is black, but is stuck powered on. I cannot seem to power down manually.
That being said, after going to the thread you've directed me to, it does appear in the device manager under the name indicated by the thread! I will report back once I've tried all I can with this lead, thank you very much.
lynxon said:
The phone is currently stuck in a state where the screen is black, but is stuck powered on. I cannot seem to power down manually.
That being said, after going to the thread you've directed me to, it does appear in the device manager under the name indicated by the thread! I will report back once I've tried all I can with this lead, thank you very much.
Click to expand...
Click to collapse
Good Luck.
Alright, so right now I'm getting "Sahara Communication Failed, please try again after power off phone."
So, I guess I'm back to waiting for the phone to run out of battery on its own. I'll try the MSM Download Tool again once that time comes :good:
lynxon said:
Alright, so right now I'm getting "Sahara Communication Failed, please try again after power off phone."
So, I guess I'm back to waiting for the phone to run out of battery on its own. I'll try the MSM Download Tool again once that time comes :good:
Click to expand...
Click to collapse
I think you're forgetting the 3-button-magic of your device. Press power + vol-up + vol-down simultaneously for 10 seconds to make it power down.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
I think you're forgetting the 3-button-magic of your device. Press power + vol-up + vol-down simultaneously for 10 seconds to make it power down.
Click to expand...
Click to collapse
I did actually try that as well, to no avail.
DarthVader said:
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
Click to expand...
Click to collapse
Good news is that this time the MSM Download Tool could recognize the phone, however I received "Images do not match with the phone." I had to download 9.0.12. as it seems that 9.0.13. actually got removed from that server as I was in the middle of downloading it. I found another source for 9.0.13. and am downloading that now. Hopefully that's the correct version...
lynxon said:
I did actually try that as well, to no avail.
Good news is that this time the MSM Download Tool could recognize the phone, however I received "Images do not match with the phone." I had to download 9.0.12. as it seems that 9.0.13. actually got removed from that server as I was in the middle of downloading it. I found another source for 9.0.13. and am downloading that now. Hopefully that's the correct version...
Click to expand...
Click to collapse
Is your phone a T-Mobile Converted
DarthVader said:
Good Luck.
Click to expand...
Click to collapse
And the phone is alive again! Hallelujah! I had to use the T-Mobile version of the MSM Download Tool, which is funny because I had bought the phone used and there was no T-Mobile screen at boot before, but there is now, but she is alive!!!
Thank you again for your help. You're doing great work since returning to the light side, Vader
lynxon said:
And the phone is alive again! Hallelujah! I had to use the T-Mobile version of the MSM Download Tool, which is funny because I had bought the phone used and there was no T-Mobile screen at boot before, but there is now, but she is alive!!!
Thank you again for your help. You're doing great work since returning to the light side, Vader
Click to expand...
Click to collapse
Glad to know you're back up. You bought it off eBay I assume? That would explain the no TMo Splash Screen earlier. Now if you'd like to revert to International again, there is a Guide you can use to convert your TMo into International and then update to latest 10.3 or Flash a Custom ROM as you please. It's in the Guides Section.
May the Force be with You.
DarthVader said:
Glad to know you're back up. You bought it off eBay I assume? That would explain the no TMo Splash Screen earlier. Now if you'd like to revert to International again, there is a Guide you can use to convert your TMo into International and then update to latest 10.3 or Flash a Custom ROM as you please. It's in the Guides Section.
May the Force be with You.
Click to expand...
Click to collapse
Yes! Back up and then immediately down... So, I followed the procedure to remove the T-Mobile info and that worked well, back to stock OxygenOS 9.0.13. Followed the directions here for unlocking the bootloader, running TWRP and Magisk. All good.
Last time I flashed with RR and crashed. This time I flashed with LineageOS 17 and... Exact same crash. Static on the bottom of the screen, bootloop and all. So, now I'm stuck waiting again for the battery to die down before I can reflash to T-Mobile, then to international, then unlock the bootloader.
Any idea what I can do differently this time so I can have a custom ROM?
Not eBay, but I was using OfferUp and found a local shop selling it so I was able to sidestep the middleman.
lynxon said:
Yes! Back up and then immediately down... So, I followed the procedure to remove the T-Mobile info and that worked well, back to stock OxygenOS 9.0.13. Followed the directions here for unlocking the bootloader, running TWRP and Magisk. All good.
Last time I flashed with RR and crashed. This time I flashed with LineageOS 17 and... Exact same crash. Static on the bottom of the screen, bootloop and all. So, now I'm stuck waiting again for the battery to die down before I can reflash to T-Mobile, then to international, then unlock the bootloader.
Any idea what I can do differently this time so I can have a custom ROM?
Not eBay, but I was using OfferUp and found a local shop selling it so I was able to sidestep the middleman.
Click to expand...
Click to collapse
Could you perhaps provide an image of Said Crash? And a couple more things. Which ROM were you trying to Flash. What was your OOS version before trying to Flash the ROM. And what TWRP did you use? Because this sounds like a Crash Dump which is common if you use the wrong Vendor Firmware.
DarthVader said:
Could you perhaps provide an image of Said Crash? And a couple more things. Which ROM were you trying to Flash. What was your OOS version before trying to Flash the ROM. And what TWRP did you use? Because this sounds like a Crash Dump which is common if you use the wrong Vendor Firmware.
Click to expand...
Click to collapse
Well, hopefully I won't crash again as I have to wait a day for the battery to train to fix the crash haha. It happened so far with RR and LineageOS. OxygenOS 9.0.13. And...
Woah. Just now seeing that my TWRP Zip file is 3.2.3-2 and Img file is 3.3.1-1. Perhaps that is the culprit?
EDIT: Nope! Just tried with TWRP 33.1-1, LineageOS 16 official build as of 1/11/2020. Included is a photo of the boot warning page, and apparently I can fastboot right now as well, but there's no particular information on either page that I can imagine is useful.
Boot warning
Fast boot
This time I also tried wiping the Dalvik. I also notice that on the bootloader unlocking directions it says to not update with partial OTAs (under 1GB) as this can cause a soft-brick. All of the ROMs I've been trying to flash are about 500mb. Is this the problem?
lynxon said:
Well, hopefully I won't crash again as I have to wait a day for the battery to train to fix the crash haha. It happened so far with RR and LineageOS. OxygenOS 9.0.13. And...
Woah. Just now seeing that my TWRP Zip file is 3.2.3-2 and Img file is 3.3.1-1. Perhaps that is the culprit?
Click to expand...
Click to collapse
It is. Always use the latest version of TWRP, OOS, Magisk, etc UNLESS said otherwise.
DarthVader said:
It is. Always use the latest version of TWRP, OOS, Magisk, etc UNLESS said otherwise.
Click to expand...
Click to collapse
I seem to have edited my last post without noticing your reply. Updated both copies of TWRP, img and zip, to the latest and still crashed. Though if you look at my last post there is one other potential, though I'm not sure what to do about it, I also uploaded pics.
This magic right here!!
After following the directions in this video, I have achieved a custom rom. RR is loading right now. It would seem the major difference is that I wasn't decrypting my data, which is included in this video.
Thanks again for sticking with me and being so patient. ?
lynxon said:
This magic right here!!
After following the directions in this video, I have achieved a custom rom. RR is loading right now. It would seem the major difference is that I wasn't decrypting my data, which is included in this video.
Thanks again for sticking with me and being so patient. ?
Click to expand...
Click to collapse
Hmm. Glad to know that you're up and running. If you don't mind, could you tell me what you did different when flashing this time? And how were you flashing before that lead to the bricks.
DarthVader said:
Hmm. Glad to know that you're up and running. If you don't mind, could you tell me what you did different when flashing this time? And how were you flashing before that lead to the bricks.
Click to expand...
Click to collapse
Basically it comes down to the directions here, which I used as a base, and the directions in this video.
The unlocking bootloader directions didn't have anything about installing a custom ROM, so I figured that once I had everything else set up: unlocked bootloader, TWRP, root, then all I had to do was go to "install" in TWRP and flash the new ROM, which had led to the crash with static at the bottom of my screen.
But then, when using the video tutorial, this guy did things in a particular way. The very first thing was decrypting the data, which I didn't know was necessary, but probably made the difference. This was done under "wipe" and then "format data" in TWRP. He also instructed on flashing the newest version of OxygenOS and TWRP twice, apparently this installed it under both A/B partitions. After installing the custom ROM he also wiped the "data" and "cache." Lots of steps in the video, I felt as if they didn't need to be done exactly the way he directed, but in this case I trusted his method and I'm glad I did.