To bring to whomever is reading this up to speed, I was trying to flash DN3 Rom to my note 2, and it just bootlooped and i thought it was because i didnt have an updated enough bootloader.
So i decided to download the bootloader from drketan's post here http://forum.xda-developers.com/showpost.php?p=52278651&postcount=24217
After i had flashed that using odin, my note just started flashing with the samsung logo. I couldn't boot into recovery, only into download mode.
After hours of searching for fixes, i think i might have a Nand rw corruption and i've tried nearly everything i can find. But each "solution" ends the same.
I've tried reflashing to stock using the sticky thread's instructions, but odin simply stalls at the "Getting PIT for mapping.."
Anyone out there that can help me out?
Additional Info: Not sure if it'd help out, but before my note said "i605" under "Product Name" and now it says GT7100.
Just tried to plug my phone into the wall charger, and its just flashing with the samsung logo again, no led or anything.
So let me get this straight.. you have a Verizon I605 correct? And you tried flashing N7100 boot loader? Umm yea your going to need a jtag service or a new mother board..
You CAN NOT flash a bootloader from a different device..bad things will happen..
Related
I odin to KA6 from KA5, including the sbl.bin. When I odin from KA6 to KA7 using the stock ROM, odin hanged at transfering sbl.bin. After waiting for 10 minutes or so, I have to disonncect, remove/reinsert the battery and reboot. The dreaded phone-dotted line-computer with an exclamation point appeared. I tried all the manuvers I can find on the forums but failed to get to the download mode screen. I was desperate and called T-mobile. The tech rep instructed me how to "master reset" the phone, without success. The rep transfered me to Samsung tech support. I was instructed to to the "master reset" a few time without success. I was transfered again to a second level Samsung tech support. I waited for nearly 30 minutes without reaching a human being. I hanged up and called T-mobile again. I was finally offered a replacement. After than, I tried again all the button/battery/usb adapter combinations without being able to get past the phone-computer-exclamation point screen. As the last resort, I tried flashing KA6 with Odin 1.3 in this "brick" mode. Surprisingly, Odin recognised the phone and added a modem port. I was successful in flashing KA6 without seeing the downlaod mode screen. I then flash KA7, again successfully. I just wish to report this for the reference of anybody encountering a similar situation. The new sbl.bin in KA6 may have altered the behavior of the bootloader so that the phone will be automatically be put in download mode if anything goes wrong. That essentially makes the vibrant unbrickable. Just my guess...
chtse53 said:
I odin to KA6 from KA5, including the sbl.bin. When I odin from KA6 to KA7 using the stock ROM, odin hanged at transfering sbl.bin. After waiting for 10 minutes or so, I have to disonncect, remove the battery and reboot. The dread phone dotted line computer with an exclamation point appeared. I tried all the manuvers I can find on the forums but failed to get to the download mode screen. I was desperate and called T-mobile. The tech rep instructed me how to "master reset" the phone, without success. The rep transfered me to Samsung tech support. I was instructed to to the "master reset" a few time without success. I was transfered again to a second level Samsung tech support. I waited for nearly 30 minutes without reaching a human being. I hanged up and called T-mobile again. I was finally offered a replacement. I tried all the button/battery/usb adapter combinations without success getting anything beyond the phone-computer-exclamation point screen. As the last resort, I tried flashing KA6 with Odin 1.3 in this "brick" mode. Surprisingly, Odin recognised the phone and added a modem port. I was successfully in flashing KA6 without seeing the downlaod mode screen. I then flash KA7, again successfully. I just wish to report this for the reference of anybody in a similar situation. The new sbl.bin may have altered the behavior of bootloader so that the phone will be automatically be put in download mode if anything wrong happens. That essentially makes the vibrant unbrickable. Just my guess...
Click to expand...
Click to collapse
wrong section for posting this
@birgertime....this sounds like what happened to you lol
Someone on the General thread had this happen also.. instead of anything working for the soft brick, when he plugged his phone in with ODIN open it brought up a COM port and he finally said "well, I'll try to flash it anyway" and it went.
Good "Need to Know" Info
I had a similar experience. I flashed KA7 and needed to flash another rom, so I went about flashing voodoo via ODIN and it failed and I was stuck at that screen.
I was freaking out a little because I couldn't get into download mode (even tried my jig).
Throughout the whole process I did notice ODIN recognized my phone as if it was in DL mode, which I thought was a little strange.
Anywho after trying everything I decided to try again. So I flashed the kernel again (in the phone ! pc screen) and it worked...
Sooooo...maybe the secondary bootloader allows you a way out if you screw up a flash............
jmcghee1973 said:
Sooooo...maybe the secondary bootloader allows you a way out if you screw up a flash............
Click to expand...
Click to collapse
or maybe it sucks worse than before and is easier to brick
I'd prefer your way though
i had the same thing hapopen to me today . odin hanged ,pulled battary out and dload mode shows phone dot computer icon , plugged in cable and started odin and it showed com port and reflashed it ..worked.
maybe that's the new download mode? lol
Sent from my SGH-T959 using XDA App
iynfynity said:
maybe that's the new download mode? lol
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It's not. I had a similar experience as some of the others in this thread, but it seems that it is some sort of extra failsafe mode. Because I could NOT get into download mode when this happened.
Is there any special reason you were using ODIN? ClockworkMod seems a far more reliable flashing method than Kies (Mini) or ODIN IMO. I only use ODIN when I can't use ClockworkMod. I like to think I have avoided many (soft)bricks this way. A co-worker of mine bricked his phone by using ODIN with a intermittently connecting USB cable, had he used ClockworkMod instead he likely would have been fine since there's no cable involved. This is an attempt to prevent future bricks, nothing more. Thankfully, I was able to fix it for him.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
I had the same issue. My phone would not boot or get into download mode so it wouldn't get recognized by Odin or ADB. All I could do it get the phone, exclamation point, computer graphic. After a ridiculous combination of things tried, I was able to get it to download mode by unplugging USB and battery out. Then while holding down volume buttons, plug in the USB cable. This [finally] allowed me to get back to download mode. Hope it helps.
Hi guys
I think i bricked my galaxy s3 (i9300)
my S3 was on android 4.1.2 official, but since the upgrade i noticed the charging problems many people had, with up to 6-7 hours to charnge fully with the original charger or more (the solution many sad was either to buy a direct charger, non usb, as for the S2 or turn back to its ICS 4.0.4..well at that moment i opted for getting back to ICS
But it seems with the new boot loader that Sammy introduced in the new software something went wrong when flashing the ICS firmware with the 3 Files (pda,modem.csc)..
It FAILED, i retried, then i got several times stuck and Nand Write Start or Setup Connection
Then i tried maybe flashing the firmware with a PIT file to repartition..the result was the same..
So in conclusion i think i made up a big mess in there...
At this moment my phone can only get in Download Mode with the 3 buttons combo (it also shows the counter etc), nothing more, it doesn't work at all..I' can't flash on it anything (except for the single PIT file) it's the only file that gets Successful installation in Odin, everything else gets stuck
(recovery, firmware..)
EDIT: after flashing the mx PIT file i have again the initian boot logo..but still get FAILED in flashing firmware process
HELP is MUCH appreciated! Thank you in advance!
I also have this problem, but mine happened when upgrading my rom (Foxhound). Can't enter recovery, only download mode works. Flashing back to stock has failed, I now want to try flashing the pit files.
timberlake88 said:
Hi guys
I think i bricked my galaxy s3 (i9300)
my S3 was on android 4.1.2 official, but since the upgrade i noticed the charging problems many people had, with up to 6-7 hours to charnge fully with the original charger or more (the solution many sad was either to buy a direct charger, non usb, as for the S2 or turn back to its ICS 4.0.4..well at that moment i opted for getting back to ICS
But it seems with the new boot loader that Sammy introduced in the new software something went wrong when flashing the ICS firmware with the 3 Files (pda,modem.csc)..
It FAILED, i retried, then i got several times stuck and Nand Write Start or Setup Connection
Then i tried maybe flashing the firmware with a PIT file to repartition..the result was the same..
So in conclusion i think i made up a big mess in there...
At this moment my phone can only get in Download Mode with the 3 buttons combo (it also shows the counter etc), nothing more, it doesn't work at all..I' can't flash on it anything (except for the single PIT file) it's the only file that gets Successful installation in Odin, everything else gets stuck
(recovery, firmware..)
EDIT: after flashing the mx PIT file i have again the initian boot logo..but still get FAILED in flashing firmware process
HELP is MUCH appreciated! Thank you in advance!
Click to expand...
Click to collapse
I have an i9205 that I am trying to fix for somebody. The phone was acting weird so he rebooted it and did a battery pull. After doing so the phone would just sit on the samsung boot screen. I could boot into download mode, but if you went into recovery mode it just said installing update. It would get to 100% restart and then just sit on the samsung logo. Everytime you booted into recovery it would do this. I downloaded kies and tried to reflash the phone. during the flash an error popped up and said to retry in emergency mode. That also failed and phone said "sw rev check fail fused 1 binary 0" on the screen. I am thinking now the only option is probably to flash with odin, but was wondering if anyone else had any ideas. thank you
After flashing a lot of samsung phone, I think the best way to reflash is Odin. Try to download the firmware you want and flash it with Odin. And then, reboot. This always save my phones.
For your recovery, have you tried to update your phone with OTA ? The download may be incomplete and make a soft brick.
Sorry for bad english I'm french.
Thanks for the reply. ya thats what I am going to try. There are a ton firmwares based on country and I am trying to figure out which one I need. It is not my phone so I am not sure if he tried to do an ota, but I think thats probably what happened. Tried to do an ota, phone ran poorly, hard rebooted, and finally resulted in a softbrick. I think that may be why the recovery boot keeps saying installing update as well. Also your English was not bad at all.
Great, let me know if that solution solve your problem.
If it don't, it should not but it's possible, try with pit file (never had to use it so it's really in case it don't work correctly).
Hey guys,
I flashed Cyanide L on Friday morning with a clean install etc.. and my phone seems to have bricked itself while on the charger from Friday night into Saturday morning. I used it most of the day Friday and it seemed fine other than 1 random reboot. My phone will not boot past the Galaxy Note II screen when the phone first turns on, I can boot into recovery (Philz) but I don't see anything on the screen when I do (I get haptic feedback when I touch anywhere on the screen but I can't do anything.)
I tried for about 5 hours to use Odin in download mode and return to either 4.1.1 stock or 4.1.2 (I know using Odin to restore 4.3 will lock my bootloader which I am not interested in doing). However, Odin keeps failing when trying to write the recovery image to the phone. Does anyone have any tips or suggestions for what I could do next?
ozo012 said:
Hey guys,
I flashed Cyanide L on Friday morning with a clean install etc.. and my phone seems to have bricked itself while on the charger from Friday night into Saturday morning. I used it most of the day Friday and it seemed fine other than 1 random reboot. My phone will not boot past the Galaxy Note II screen when the phone first turns on, I can boot into recovery (Philz) but I don't see anything on the screen when I do (I get haptic feedback when I touch anywhere on the screen but I can't do anything.)
I tried for about 5 hours to use Odin in download mode and return to either 4.1.1 stock or 4.1.2 (I know using Odin to restore 4.3 will lock my bootloader which I am not interested in doing). However, Odin keeps failing when trying to write the recovery image to the phone. Does anyone have any tips or suggestions for what I could do next?
Click to expand...
Click to collapse
Here's an older post with links that might be helpful ( http://forum.xda-developers.com/showthread.php?p=57944591 ).
Make sure you're using the pit file when flashing the appropriate firmware in Odin.
Some common issues with Odin also are to make sure you're using a USB 2.0 port on your computer and use the phone's original USB cable or a good quality one if you don't have the original any longer. Also run Odin with Administrative privileges, make sure that Kies is not running in the background because it interferes with ODIN, and disable antivirus programs when running Odin.
Yeah something went wrong in Odin when I flashed the stock recovery the last time and I corrupted my EMMC as Product Name: (Blank) is showing up now.
RIP Note II it was nice knowing you.
ozo012 said:
Yeah something went wrong in Odin when I flashed the stock recovery the last time and I corrupted my EMMC as Product Name: (Blank) is showing up now.
RIP Note II it was nice knowing you.
Click to expand...
Click to collapse
Man... that sucks! I wonder if it was actually Odin, or if the EMMC chip just died. Either way, it doesn't really matter now. RIP Note 2.
I was using @Lysergic Acid cm-13.0-20161114. I picked my S2 to check the hour and the screen didn't turn on so naturally I held the power button to restart it. The phone didn't boot past the "Galaxy S2 etc." screen. I tried to open TWRP and the splash screen appeared but it didn't get past that, no TWRP menu. I tried to flash stock ROM with Odin, it failed. The same happened trying to flash modified kernels with custom recoveries. So now I'm stuck with a message that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I've had to recover my phone many times in the past but TWRP always worked, this time it didn't.
Is there any way to solve this? I have important information inside the phone. Would a USB JIG be of any help?
Simeonico said:
I was using @Lysergic Acid cm-13.0-20161114. I picked my S2 to check the hour and the screen didn't turn on so naturally I held the power button to restart it. The phone didn't boot past the "Galaxy S2 etc." screen. I tried to open TWRP and the splash screen appeared but it didn't get past that, no TWRP menu. I tried to flash stock ROM with Odin, it failed. The same happened trying to flash modified kernels with custom recoveries. So now I'm stuck with a message that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I've had to recover my phone many times in the past but TWRP always worked, this time it didn't.
Is there any way to solve this? I have important information inside the phone. Would a USB JIG be of any help?
Click to expand...
Click to collapse
Odin should be able to flash the stock firmware while on the screen that says "upgrade encountered an issue" as long as you had USB debugging enabled.
You can also try booting a debrick.img from ext sdcard if you can find the debrick.img specific for your device.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Odin should be able to flash the stock firmware while on the screen that says "upgrade encountered an issue" as long as you had USB debugging enabled.
You can also try booting a debrick.img from ext sdcard if you can find the debrick.img specific for your device.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Nevermind, I tried flashing a 3 part stock JB rom that worked for some people. It didn't work for me and now the phone doesn't even turn on. RIP
Now I have a white S2 (Galaxy S2 forever lol) that a friend gave me until I buy a phone next year with the Snapdragon 660, or if I get a job (I'm a student), an even better phone with the Snapdragon 835.
Simeonico said:
Nevermind, I tried flashing a 3 part stock JB rom that worked for some people. It didn't work for me and now the phone doesn't even turn on. RIP
Now I have a white S2 (Galaxy S2 forever lol) that a friend gave me until I buy a phone next year with the Snapdragon 660, or if I get a job (I'm a student), an even better phone with the Snapdragon 835.
Click to expand...
Click to collapse
If the device vibrates when you hold power but doesn't boot then the debrick.img may still work, just in case you're curious enough to attempt fixing it for learning purposes.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
If the device vibrates when you hold power but doesn't boot then the debrick.img may still work, just in case you're curious enough to attempt fixing it for learning purposes.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
The S2 doesn't vibrate when you turn it on (at least the i9100 model), but don't worry it's completely dead. No boot, no recovery, no download mode, no nothing. If I'm bored enough I might buy a new motherboard from AliExpress in the future cause they're really cheap.