Related
Well first off, ive been at this for 2 days and its frustrating. I am new to this flashing and rooting business and ended up bricking my phone from using the wrong files in metamorph and never backing my stock files up. It would give me a blank screen with the red LED lit up and all my home buttons on the bottom lit up. I followed the Odin directions and actually got my phone to stock. But it was extremely laggy and and i had no service and my SD card just kept connecting and reconnecting. Well i followed the flashing kernel threat because someone told me to try that so i can get the stock kernel or whatever on the phone. That failed and now im sitting here with my phone displaying a phone icon and a computer icon, then a caution symbol in the middle. Someone pleaseeee help me fix this.
l2,
I've been there 3 times this morning already as I hadn't flashed a new zImage to this particular device yet until this morning. What you need to do is get the stock files from http://rapidshare.com/files/415661977/SPH-D700-DG27-8Gb-REL.tar.html and s1_odin_20100513.pit (it must be 13, not 12). Boot into Download mode (hold 1 when powering on). Start Odin 3, check Auto Reboot and Debug En. Choose your PIT file, and under PDA choose the SPH-D700-DG27-8Gb-REL.tar. Plug in your phone, once it is recognized in Odin click Start. This takes about 10 minutes, I know it looks like it hangs up a couple of times but it should keep going. Let me know if that helps.
khalaan said:
l2,
I've been there 3 times this morning already as I hadn't flashed a new zImage to this particular device yet until this morning. What you need to do is get the stock files from http://rapidshare.com/files/415661977/SPH-D700-DG27-8Gb-REL.tar.html and s1_odin_20100513.pit (it must be 13, not 12). Boot into Download mode (hold 1 when powering on). Start Odin 3, check Auto Reboot and Debug En. Choose your PIT file, and under PDA choose the SPH-D700-DG27-8Gb-REL.tar. Plug in your phone, once it is recognized in Odin click Start. This takes about 10 minutes, I know it looks like it hangs up a couple of times but it should keep going. Let me know if that helps.
Click to expand...
Click to collapse
okay ill try all of that but Where can i get the 13 pit file?
It can be downloaded from this link.
http://www.4shared.com/get/6aSCPmEf/s1_odin_20100513.html
khalaan said:
It can be downloaded from this link.
http://www.4shared.com/get/6aSCPmEf/s1_odin_20100513.html
Click to expand...
Click to collapse
thanks so much man ill try it out. One question though. I already started this odin thing and its doing its thing. its about half way done but its using the 12...can i just shut my phone off and put it in download again when its done and use the 13 and it will work?
If you have it going with the 12 already I'd give that a try, if it doesn't work you can always get back into download mode and do it with 13. I couldn't get 12 to ever start it would always sit for 20m and do nothing.
khalaan said:
If you have it going with the 12 already I'd give that a try, if it doesn't work you can always get back into download mode and do it with 13. I couldn't get 12 to ever start it would always sit for 20m and do nothing.
Click to expand...
Click to collapse
okay yeah ill try. but its been sitting for like 10 min at half way on the status bar...
That is way the devil too long, go ahead and unplug your phone, hit reset in odin, set it up like I instructed, reboot your phone to download mode, and give it another go.
yeah lol okay i thought so. haha
Alllll fixed. Thank you guys soooo much for helping out. Im going to root again but i'm not gunna mess with metamorph this time lol, whats a good root? Im learning all this stuff and idk what one i should do.
http://forum.xda-developers.com/showthread.php?p=8628341#post8628341
>_>
Please Modify Title of Thread add
" Solved - Bricked Epic - tried everything "
I bricked my Epic last weekend and am feelin' ya on all the stuff you did to unbrick it. Glad to hear that all is well~
I screwed my setup up and had to do the Odin method yesterday. I didn't read this post before hand, and I used the ****12.pit instead of the 13. What is the difference in the two? My phone seems to be working just fine with the 12. One problem I found I don't believe I had before is theming the dialer_tab_activity.apk FCs the phone on hangup, but when I put another one in unthemed, it works fine.
help
I cannot get phone to load any tar completely.. they all stop and phone's screen goes purple. Most the time it hangs in odin at the zImage and then sometimes it gets a few bars going .. and hangs at factoryfs.rfs. Any help
You don't need the pit file when flashing a tar rom. It's only for modems and kernals. I have used Odin and haven't used the pit. Works just fine.
Okay, i just joined. Sorry if i sound ignorant (most likely cause I am) but i am fairly certain i semi-bricked my Epic, okay so it started when i flashed the CyanogenMod it was very laggy so i figured i did it wrong, quickly using clockwork i flashed VIPERrom (FRoZeN) DK28 all looked fine but then my phone's service started acting up, so i tried to re-flash CyanogenMod. This ***** it up worse it got stuck at the Samsung boot logo, now i am trying to revert to Stock but Odin nor my Cpu recognize the Device.
Extra info that might help, I have the Stock Tar, Odin 1.6 with Pit, can get into both download and CW recovery...
Help this ignorant fool please T_T
The Boxinator said:
Okay, i just joined. Sorry if i sound ignorant (most likely cause I am) but i am fairly certain i semi-bricked my Epic, okay so it started when i flashed the CyanogenMod it was very laggy so i figured i did it wrong, quickly using clockwork i flashed VIPERrom (FRoZeN) DK28 all looked fine but then my phone's service started acting up, so i tried to re-flash CyanogenMod. This ***** it up worse it got stuck at the Samsung boot logo, now i am trying to revert to Stock but Odin nor my Cpu recognize the Device.
Extra info that might help, I have the Stock Tar, Odin 1.6 with Pit, can get into both download and CW recovery...
Help this ignorant fool please T_T
Click to expand...
Click to collapse
You forgot to flash the EXT4 or RFS Kernel
http://android.stolenrobot.com/Epic4G/epic.htm
that comes with cyanogen it looks like just put either on your sd card then flash after you flash cyanogen in Cwm
Here is some more info
http://forum.xda-developers.com/showthread.php?t=935060&highlight=tutorial
iSaint said:
You forgot to flash the EXT4 or RFS Kernel
http://android.stolenrobot.com/Epic4G/epic.htm
that comes with cyanogen it looks like just put either on your sd card then flash after you flash cyanogen in Cwm
Here is some more info
http://forum.xda-developers.com/showthread.php?t=935060&highlight=tutorial
Click to expand...
Click to collapse
I did flash EXT4 "CM6EXT4kernel-1-2-2011" this one to be specific.
The Boxinator said:
I did flash EXT4 "CM6EXT4kernel-1-2-2011" this one to be specific.
Click to expand...
Click to collapse
did you wipe x3 ?
So, I just thought I would come here to let everyone know what the SBL actually does to your phone. Me, being a dev, am always flashing test stuff.
The SBL is actually a fix for the Phone-!-PC soft brick screen.
It allows you to flash with ODIN while on that screen. I've tested this SBL through and through and haven't seen any issues with it.
krylon360 said:
So, I just thought I would come here to let everyone know what the SBL actually does to your phone. Me, being a dev, am always flashing test stuff.
The SBL is actually a fix for the Phone-!-PC soft brick screen.
It allows you to flash with ODIN while on that screen. I've tested this SBL through and through and haven't seen any issues with it.
Click to expand...
Click to collapse
Hmmm never even heard of that screen before lol... but I was hearing stories of people able to get ODIN to recognize their phone while it was completely off. Can you confirm if that is true or not?
Wow that puts that scare to rest. thanks krylon of teamwhiskey!
I knew it....been sayin that all along.. thx for confirming that for us..
Settai said:
Hmmm never even heard of that screen before lol... but I was hearing stories of people able to get ODIN to recognize their phone while it was completely off. Can you confirm if that is true or not?
Click to expand...
Click to collapse
False. ODIN will not see the phone while it is off...
*looks at his dead vibrant sitting on the desk hooked to the PC with ODIN open.
The Phone-!-PC screen is the softbrick screen you get when you have a bad ODIN flash.
Thanks Krylon........ BTw your name is a brand of paint
thanks for the confirmation there krylon.
do you have any idea on why or how so many ppl ended up bricking trying to go to Bionix-v? originally, i thought it was the sbl doing it and that's why i never flashed it.
krylon360 said:
So, I just thought I would come here to let everyone know what the SBL actually does to your phone. Me, being a dev, am always flashing test stuff.
The SBL is actually a fix for the Phone-!-PC soft brick screen.
It allows you to flash with ODIN while on that screen. I've tested this SBL through and through and haven't seen any issues with it.
Click to expand...
Click to collapse
so that's what happened to me the other day...I had a bad flash in Odin and that screen came on....but Odin did reconnise the phone and I was able to flash it....I guess Sammy has been looking out for us the "flashers"
Oniyuri said:
thanks for the confirmation there krylon.
do you have any idea on why or how so many ppl ended up bricking trying to go to Bionix-v? originally, i thought it was the sbl doing it and that's why i never flashed it.
Click to expand...
Click to collapse
Bricking as in Soft Bricking? or Bricking as in the brick I have laying on my desk.
krylon360 said:
False. ODIN will not see the phone while it is off...
*looks at his dead vibrant sitting on the desk hooked to the PC with ODIN open.
The Phone-!-PC screen is the softbrick screen you get when you have a bad ODIN flash.
Click to expand...
Click to collapse
Ahhh got ya man thanks for the info, hope you get your new vibrant soon man
krylon360 said:
Bricking as in Soft Bricking? or Bricking as in the brick I have laying on my desk.
Click to expand...
Click to collapse
Brick as in your brick
Settai said:
Brick as in your brick
Click to expand...
Click to collapse
^yes that. some ppl in the Bionix-v thread here and the one on the TW forums have reported hard bricks after flashing (i think one was even coming from Nerov5 which stopped me in my tracks). Since I'm not in the US atm, I definitely don't want to take any chances.
Settai said:
Brick as in your brick
Click to expand...
Click to collapse
SBL wont do that.
You PBL (Primary Bootloader) crashed.
If some how the SBL became corrupt during the DL, it might have corrupted the PBL.
Mine bricked due to flashing the PBL and SBL for the 4G, then ODINing to JFD and flashing the JI6 SBL. my PBL was already hosed.
krylon360 said:
SBL wont do that.
You PBL (Primary Bootloader) crashed.
Click to expand...
Click to collapse
ah... but what could cause a pbl to crash while flashing? i really do wanna investigate the issue as ppl have also been bricking doing the otc froyo update too (but then again, i automatically figured it was kiesmini in the first place).
krylon360 said:
SBL wont do that.
You PBL (Primary Bootloader) crashed.
If some how the SBL became corrupt during the DL, it might have corrupted the PBL.
Mine bricked due to flashing the PBL and SBL for the 4G, then ODINing to JFD and flashing the JI6 SBL. my PBL was already hosed.
Click to expand...
Click to collapse
Looks like there was at least one more hard brick today, he was going to Bionix V BUT went to it following a bad Odin. Maybe others are doing the same thing, f-ing up an odin or flash and then trying to recover by flashing whatever is on their sdcard?
http://forum.xda-developers.com/showthread.php?t=936389
I suppose that is the downside to Bionix being so popular, it just happens to be the Rom they are flashing at that moment.
jellette said:
Looks like there was at least one more hard brick today, he was going to Bionix V BUT went to it following a bad Odin. Maybe others are doing the same thing, f-ing up an odin or flash and then trying to recover by flashing whatever is on their sdcard?
http://forum.xda-developers.com/showthread.php?t=936389
Click to expand...
Click to collapse
I can tell you that wasn't the scenario in my case. I had been running the same rom for a couple of days, saw that Bionix V was released, and decided to flash it. I backed up some updated apps with titanium, backed up call logs, sms, etc with MyBackup Pro, rebooted into clockworkmod recovery, did a nandroid, then flashed bionix V. The install finished and returned to the CMRecovery menu, I selected "reboot system now", and that was it. Phone was dead on arrival
jellette said:
Looks like there was at least one more hard brick today, he was going to Bionix V BUT went to it following a bad Odin. Maybe others are doing the same thing, f-ing up an odin or flash and then trying to recover by flashing whatever is on their sdcard?
http://forum.xda-developers.com/showthread.php?t=936389
Click to expand...
Click to collapse
I responded. I have a feeling it's when ODIN crashes thats causing the corruption within the PBL.
I've got a new flashing tool...(Not ODIN, nor Heimdall) Lets just say, it's for the Sidekick 4G as well as the Orion...oh, and I have a new ODIN version, and a new Pit file for the Sidekick 4G and Orion and Vib 4G...
Once I get my new phone, I'll test out the new flashing app.
Alkaloid said:
I can tell you that wasn't the scenario in my case. I had been running the same rom for a couple of days, saw that Bionix V was released, and decided to flash it. I backed up some updated apps with titanium, backed up call logs, sms, etc, rebooted into clockworkmod recovery, did a nandroid, then flashed bionix V. The install finished and returned to the CMRecovery menu, I selected "reboot phone now", and that was it. Phone was dead on arrival
Click to expand...
Click to collapse
When mine bricked, I had flashed an I9000 sbl, and then flashed a vibrant sbl while still on the I9000 rom - as soon as the flash ended it just went black and after just one $130 insurance claim I was up and running with a new phone..
Jellette, remember that 2.2.1 rom you were working on a while back that was posted in your repo over at TW forums? I was one of the ones who flashed that. I never could get it to work properly, but Ever since that flash my phone always booted with the "GT-I9000" start up screen then "Vibrant" screen. Also after that I always had to hold volume up and power to get into DL mode instead of vlume down or volume up & down + power which is the way I used to have to get into DL mode. I always wondered if it had some affect on the boot loader. Could this combined with the flash of the new SBL in the new boionix rom have caused the brick? It's the only thing I can think of as far as why or how my SBL shat itself.
jellette said:
When mine bricked, I had flashed an I9000 sbl, and then flashed a vibrant sbl while still on the I9000 rom - as soon as the flash ended it just went black and after just one $130 insurance claim I was up and running with a new phone..
Click to expand...
Click to collapse
hehe no insurance claim for me. Luckily I was able to get back to JFD before mine died, so just had to pay the $20 for expedited shipping.
Okay,
There is a growing number of us XDA members on the Vibrant platform who have just bricked out phones. Save for other DEV tools, which I have not used, do not have access, and do not know how to use, for all intensive purposes, this phone is Br'iKTed ! ! !
Here are the series of events
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
4. worked great for 2 days.
5. then on night 2, the phone was stuck on the DOW Green robot screen
6. could not get into Recovery mode (none of the recovery modes)
7. Phone would not boot
8. ODIN back to stock
9. After Vibrant screen, the phone turns off. No soft keys, Nada!
10. Flashed JI5, Ji6, Eugene's Non Bricking Froyo (ODIN Files)
11. Same result, Turned off after Vibrant
and
12. still cant' get into recovery
I am having problems with the phone starting up and loading what I flashed.
I flashed JI5 Ji6, and Eugene's non bricking Froyo Rom
These 3 are the only ones I was able to find that is ODIN flashable
Why you ask?
I cannot get into Recovery, but I can get into Download mode. I can't get into any recovery at all. NOTHING. This is why ODIN seems to be my only option.
But regardless of any ROM i flash, my phone shuts off right after the Vibrant screen. No splash screen, no loading, no booting. .Nothing. It just shuts off.
I can't charge it either.
i get a Charging bootloop. HOurglass - battery shows up for a bit, then restarts over and over.
So in other words. it's ****ed.
Hope that explains it sufficiently. if you have any more questions or suggestions, Im open man, Im open.
Help me
So I'm not sure how DEVs would like to proceed on this.
TW (I've always loved your roms. Been following you since the first BIONIX 1.8)
Morific (If it's the Kernel, i'd like to know about it)
Thanks for reading guys. I wanted to give everybody a heads up.
I don't know what the problem is, but I do know that the phone does not work.
I'd appreciate some suggestions or anything.
And to inform the community that this problem is out there. I hope there aren't any more bricked phones.
Cheers,
have you tried using odin with the repartition checked
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
a4 moda said:
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
Click to expand...
Click to collapse
have you tried to odin to ka6 or ka7? something with a bootloader
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
STiGLOGiC said:
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
Click to expand...
Click to collapse
Completely reasonable. This pertains to development because if there is an endemic problem with one of our ROMS or KERNELS (not pointing fingers, just pointing out the possibilities that I know of, there could be more), people in our community need to know. Hence, I titled it "PUBLIC SERVICE ANNOUNCEMENT"
Thanks. I hear you about Tmobile. I'd rather not have to dump my problem on Tmobile if I can fix it, because I flashed the rom. Despite the fact that Tmobile JFS leaves something to be desired, they did deliver me a working phone. So i'd like to exhaust all possibilities before calling it quits.
hackman17 said:
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
Click to expand...
Click to collapse
Exactly.
jaetm83 said:
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Click to expand...
Click to collapse
Thanks for the heads up. I've gone through this myself many times. And i'm sure your post will help others out there. My problem (as well as many others on here with the same ROM and KERNEL I used) seems to be different and unique. Something that ODIN won't cure.
vibrant2010 said:
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Yes, tried that too. Same result. Vibrant.. then shut off.
Thanks anyway.
I had actually just had Bionix-v 1.2.1 and the new DoW combo to try out Voodoo Sound. I really loved the sound quality, but battery drain was not adequate as being my daily driver, even though I set it to run at 1ghz and used a sleep profile. After just over 2 days of use, I backed out by ODIN'ing to JFD and I installed Bionix-v 1.2.1 again. Only thing I have noticed so far is GPS not initiating immediately after it's turned on. I would go into GPS Test app, and turn on GPS after the app is started, but I get no satellites for at least 1 min. I used to get a lock within seconds, not minutes. I will try ODIN again tomorrow and see if it fixes. I guess I was lucky enough not to get a bootloop again though.
But I can't see why you and I would have any issues after the Bionix+Dow combo. Wouldn't ODIN just clear everything up? I even repartitioned when flashing, so my guess is that my system, data, datadata, etc., are all reformatted completely? Am I missing something?
I had the same problem. I flashed DoW and then the next day my phone didn't want to turn on. I pulled the battery and restarted it. It didn't want to start up all the way. It got to the vibrant screen and shut off. luckily for me, my replacement phone that I ordered a week ago came in the same day. I sent off my old phone letting samsung/tmo take care of it.
This exact same thing happened to me.
I too had the phoen bricked after flashing the DOW after Bionix 1.2.1
I have been flashing since the G1. This is the first time I've ever bricked a phone.
Hoping to get it fixed this weekend
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
black spirit said:
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
Click to expand...
Click to collapse
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
If you have not already done this, I recommend doing this: http://forum.xda-developers.com/showthread.php?t=954509
Bay Wolf made a nice software for the computer that pretty much shows you a step-by-step instruction on how to flash to stock, reroot, and flash the new ROM of your choice. This program will push you into download mode, clockwork recovery, etc. There is a video on that link that will also show you a step-by-step instruction. Try that out if you haven't, and let us know how it goes.
That program comes with a PIT and TAR file for you to use as well.
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
drewdude007 said:
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
Click to expand...
Click to collapse
I thought the same when it happen to me.
Nothing would work, but went that approach and happy days.
s1_odin_20100512.pit
and
T959UVJFD.tar
are the only ones you need, and if your good with your flashing, just do a pit first, no pda.
And if your still getting to download mode, ect, and dont have the computer /!\ phone icon on the screen, sounds like a soft brick.
jellette said:
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
Click to expand...
Click to collapse
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
SamVib said:
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
Click to expand...
Click to collapse
Because he started off with his problem stated as:
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
Your phone probably IS charging.
Your /efs nodes may be messed up. Do you have a backup of your /efs?
Try reading here: http://forum.xda-developers.com/showthread.php?t=859914
Well, today I tried setting up ClockworksMod so I could easily backup and restore my phone as needed. (As previous work i had caused issues and it wouldnt reboot until i reinstalled the rom)
Well, clockworkmod recovery would not install through the app, so I installed the image through Odin, and that worked flawlessly. I was able to backup and restore.
After it booted back up I was unable to add a new google account or erase the old one. Factory resetting it would casue it to get stuck in the boot loop again, until i restored it or reflashed.
Eventually I tried flashing another image, with repartition turned on.
Well, without surprise Windows 7 semi crashed and killed Odin.
Now when my phone "turns on" all i see is black. Nothing happens. I cant do any of the 3 button combos to get into Recovery or Download mode
Can anybody help me? I need to get this working ASAP!
Thanks
Edit : I need to check my eyes. I thought you can get into download mode.
If you cannot get to download mode with the 3-button-combo then you'll need a jig.
Intratech said:
If you cannot get to download mode with the 3-button-combo then you'll need a jig.
Click to expand...
Click to collapse
Dosnt that only work if the image of the phone and computer show up on the screen?
Absolutly nothing shows up for me
Can I have your battery cover to keep as a spare.
bncplix said:
Dosnt that only work if the image of the phone and computer show up on the screen?
Absolutly nothing shows up for me
Click to expand...
Click to collapse
You need a jig.
Uhm, why did you check repartition?
Also yes, you will need a jig. That's pretty much the only thing that can get you into download mode in this situation.
Transmitted from a Galaxy far far away via XDA telepathy.
Intratech said:
You need a jig.
Click to expand...
Click to collapse
Okay, going to just order one off ebay.
Will this do? hxxp://cgi.ebay.com/Samsung-i9100-Galaxy-S-II-Download-mode-USB-Dongle-Jig-/250824932406?pt=AU_MobilePhoneAccessories&hash=item3a6654bc36
But actually, it says it has to show one of those two screens, when mine is all black?
geko95gek said:
Uhm, why did you check repartition?
Also yes, you will need a jig. That's pretty much the only thing that can get you into download mode in this situation.
Transmitted from a Galaxy far far away via XDA telepathy.
Click to expand...
Click to collapse
Because it said it was needed for that image i was flashing
bncplix said:
Okay, going to just order one off ebay.
Will this do? hxxp://cgi.ebay.com/Samsung-i9100-Galaxy-S-II-Download-mode-USB-Dongle-Jig-/250824932406?pt=AU_MobilePhoneAccessories&hash=item3a6654bc36
But actually, it says it has to show one of those two screens, when mine is all black?
Because it said it was needed for that image i was flashing
Click to expand...
Click to collapse
It can still work in some cases, lets hope it does in yours.
Did you get that advise about repartitioning from Samfirmware?
Intratech said:
It can still work in some cases, lets hope it does in yours.
Hopefully! I just ordered one
Did you get that advise about repartitioning from Samfirmware?
Click to expand...
Click to collapse
Yes I did, was that something I shouldn't have done?
It sat on repartitioning for about 15 minutes, then windoes said Odin stopped responding and it killed it :/
I've been telling everybody to stop using the .pit files and repartitioning the device for every flash as you're just increasing the possibilities of things going wrong but people don't seem to take notice. Sadly in your case something did go wrong. You only need to use the .pit files and repartition the device if you mess up your partition table.
Those guys at Samfirmware really need to stop telling people to repartition their device for every flash.
Intratech said:
I've been telling everybody to stop using the .pit files and repartitioning the device for every flash as you're just increasing the possibilities of things going wrong but people don't seem to take notice. Sadly in your case something did go wrong. You only need to use the .pit files and repartition the device if you mess up your partition table.
Click to expand...
Click to collapse
Well, lesson learned. Today was the first time I even tried installing another ROM
Thanks for the help
Once my Jig comes in, I'll let you all know how it goes!
check if the phone heatens up extremely as soon as you put the battery in. if yes, thats a really bad sign.
a jig will only help you if you see anything on the screen. if the phone/screen doesn't react to ANYTHING, that's a full brick (happened to me too, jig didn't help, nothing helped, phone was completely dead and i had to send it in. fortunately, they repaired it within warranty).
lazyb2k said:
check if the phone heatens up extremely as soon as you put the battery in. if yes, thats a really bad sign.
a jig will only help you if you see anything on the screen. if the phone/screen doesn't react to ANYTHING, that's a full brick (happened to me too, jig didn't help, nothing helped, phone was completely dead and i had to send it in. fortunately, they repaired it within warranty).
Click to expand...
Click to collapse
See, this is what I was trying to say! I read everywhere that if somethign is on the screen the Jig will work, otherwise it wont. Others are replying to me here saying it should still work for me
I'm not too worried about it. I have 4 of the phones. I work closely with Samsung and they were given to me. It would still be nice if it recovers, so we will see!
i guess in situations where it was reported to work under these conditions the owners didnt fully exploit all different possibilites to get it back on and so they just came up with this false assumption.
nonetheless, it's worth a try. at least, the jig is pretty useful to remove the yellow exklamation mark and to reset the flash counter .
lazyb2k said:
i guess in situations where it was reported to work under these conditions the owners didnt fully exploit all different possibilites to get it back on and so they just came up with this false assumption.
nonetheless, it's worth a try. at least, the jig is pretty useful to remove the yellow exklamation mark and to reset the flash counter .
Click to expand...
Click to collapse
That's another thing I am unsure of, whats the flash counter?
bncplix said:
See, this is what I was trying to say! I read everywhere that if somethign is on the screen the Jig will work, otherwise it wont. Others are replying to me here saying it should still work for me
I'm not too worried about it. I have 4 of the phones. I work closely with Samsung and they were given to me. It would still be nice if it recovers, so we will see!
Click to expand...
Click to collapse
I'm not saying it will work for sure, what I'm saying is depending on the damage done it may still get you into download mode so you can flash the firmware.
bncplix said:
That's another thing I am unsure of, whats the flash counter?
Click to expand...
Click to collapse
to be precise, it's the "custom binary counter" which counts up as soon as you flash something modified manually on your phone. has nothing to do with your problem, though.
We need to find the way to boot the device externally, i.e. bootloader on ext. SDCard or the likes....
Dont ask how but i managed to brick my SG3 CM7alpha4.
Was really stoopid
Like proper hard bricked it became.
screen wouldnt just turn on.
Phone's sitting in the service centre.
Told them official upgrade from 2.1 to 2.2 via kies failed.
Hope they dont find anything in the corrupted memory
chandradithya said:
Dont ask how but i managed to brick my SG3 CM7alpha4.
Was really stoopid
Like proper hard bricked it became.
screen wouldnt just turn on.
Phone's sitting in the service centre.
Told them official upgrade from 2.1 to 2.2 via kies failed.
Hope they dont find anything in the corrupted memory
Click to expand...
Click to collapse
I ll still ask how??
how you have bricked your i5800 really courios^^
Was converting filesystems the fugumod way,
I interupted it by dropping the phone and when i rebooted it wouldnt go past the logo.
So i flashed in ODIN with the data.rfs alone removed. hoping my data would be intact .
Instead it stuck in the middle.
when it was downloading factoryfs.rfs then i pulled out the battery.
Put it back on and a blank screen.
Couldn't see nothing on the display after that.
no battery charge indication, nothing!
Stoopid me
chandradithya said:
Was converting filesystems the fugumod way,
I interupted it by dropping the phone and when i rebooted it wouldnt go past the logo.
So i flashed in ODIN with the data.rfs alone removed. hoping my data would be intact .
Instead it stuck in the middle.
when it was downloading factoryfs.rfs then i pulled out the battery.
Put it back on and a blank screen.
Couldn't see nothing on the display after that.
no battery charge indication, nothing!
Stoopid me
Click to expand...
Click to collapse
Wait wait wait, did you have bootloader files in the ROM you were flashing??
dhirend_6d said:
Wait wait wait, did you have bootloader files in the ROM you were flashing??
Click to expand...
Click to collapse
Yup. I did.
The thing was it was just halfway through factoryfs.rfs i think,
When odin hung up on me.
Anyway, The service centre has taken my warranty and stuff, Hope warranty covers it
Just told em i was uypgrading to 2.2 via kies.