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 ?
My vibrant has an error of can't mount mmcblk0p1 and I can't use my external sd or install apps in recovery I can still access my external sd for some odd reason I installed a rom and then flashed voodoo and it wouldn't with after a great while so I battery pulled and used odin trio get to eugene froyo that cannot brick and my partitions aren't being read I can fix thus all if I can change the voodoo/enable-lagfix file to disable it can someone please suggest how to fix this issue I'm almost literally in a panic over this please help it'd be much obliged
I haven't had a need to but you can try to ODIN back to stock and start over again
If there's a better solution someone will post it soon here
Well thats the solution right there... Your probably gonna need eugenes froyo that doesnt brick and either JK2 or JFD .tar and ODIN back to get your phone restored to a stock version.
z0phi3l said:
I haven't had a need to but you can try to ODIN back to stock and start over again
If there's a better solution someone will post it soon here
Click to expand...
Click to collapse
I tried it won't help I'm current on the eugene that doesn't brick I just need a solution I've fixed this kind of problem before but only cuz I could access my internal sd when I boot up I can only access it through recovery now
jmcghee1973 said:
Well thats the solution right there... Your probably gonna need eugenes froyo that doesnt brick and either JK2 or JFD .tar and ODIN back to get your phone restored to a stock version.
Click to expand...
Click to collapse
I'm on eugenes froyo with no brick and I've flashed back to jfd and I get a black screen
Yea... eugenes froyo is just a step in the process. Its not a daily driver rom..You have to go back into D/L mode and ODIN JFD.tar without Repartition checked
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
So I was never into rooting phones I never really cared that much and my friend said it was really awesome so he rooted my phone then never told me anything to do with it so I seriously didn't change a single thing. I also guess he didn't mention you can't reset factory settings which is what I did and it is stuck on the samsung logo. I searched for this and read the "flash odin" that means zero to me. I absolutely have no idea what any of that is, can anyone help me? Thanks in advance!
Alas, I don't have any links to give you, but hopefully I can clarify what you need to do.
Odin is simply a program that is used for flashing software to your phone. All you do is download said program, as well as a recovery file and a PIT file (which is what is used to repartition the phone's internal memory). Your safest bet is to download the DL09 package, which will get you back to the stock android 2.1 that your phone came with. From there you can run your phone's system update to upgrade to the current version. There are instructions on how to flash through Odin, so I won't go into that. What you'll want to look for, though, is a full odin package, which means that it includes EVERYTHING, and you won't have to flash the system, radio, modem, etc. separately.
Hopefully that clears things up a bit. I was in the same boat as you recently.
EDIT: The most important thing to do is relax. I know it's scary to get such a bad error on your first crack into rooting, but Odin makes it REALLY hard to brick this phone. It's a little intimidating at first, but once you start flashing through Odin, no android issue will phase you.
http://forum.xda-developers.com/showthread.php?t=1026746 This is the thread I used when I screwed up my Fascinate. May it serve you well.
Ok, you will definitely be able to get out of this situation. Try this link https://docs.google.com/document/d/1cZAF3hzDIHSMEkf0QcFs2cLLrF5PmOUEXcM268FoIzk/edit?hl=en&authkey=CKqWypcP for some basic info. Look through these forums/internet and download ODIN (any version should do). Find a link to the DL09, ED01, or ED04 odin files for the full rom and a link for the atlas_v2.2.pit file. Make sure the samsung usb drivers are installed on your PC for your phone. Pull the battery. Open up ODIN. plug in the usb to your computer and phone. Hold down the "volume down" button until a yellow android comes up for your phone that says "downloading". At this point ODIN should turn yellow in the first box. Click "Pit" and select the atlas_v2.2.pit file. Click PDA!!! and select the rom that you downloaded. Hit "Start" and wait about 5 minutes until ODIN turns green and tells you "success". Disconnect the USB. Put battery back in. Boot up and hopefully you should have a stock phone back. All of your settings will be gone and you may have to OTA upgrade to the latest ROM through verizon, but all your data on the SD card will still be there. Good luck!
Mikes30000 said:
Find a link to the DL09, ED01, or ED04 odin files for the full rom
Click to expand...
Click to collapse
I would recommend against the ED01. That's a leaked ROM, and if you ever need to send your phone in for Warranty, they'll know you were up to no good. DL09 and OTA update is usually the safest bet.
seraphls said:
I would recommend against the ED01. That's a leaked ROM, and if you ever need to send your phone in for Warranty, they'll know you were up to no good. DL09 and OTA update is usually the safest bet.
Click to expand...
Click to collapse
EB01 was the leaked Froyo ROM. ED01 was the first official Froyo build released from verizon/samsung. Since then there has been official upgrade builds of ED03 and ED04. The newest, ED05 is a leak. So no problem flashing ED01. I personally prefer to flash DL09 then let the phone OTA to ED04.
landshark68 said:
EB01 was the leaked Froyo ROM. ED01 was the first official Froyo build released from verizon/samsung. Since then there has been official upgrade builds of ED03 and ED04. The newest, ED05 is a leak. So no problem flashing ED01. I personally prefer to flash DL09 then let the phone OTA to ED04.
Click to expand...
Click to collapse
And that, kids, is why you don't post on XDA before your morning tea - you forget how to read! My bad - I stand corrected.
I've never been good at pulling and producing logcats, and I'm using some Logcat Extreme app I found on the Play Store, so I'm not sure if this is going to help at all.... here's the background on the subject:
I just went from NB1 to NC1 by doing a full Odin of stock NB1, then flashing the NC1 update file, then got root and recovery from these steps here, all went very smoothly. The reason I did this was to fix a problem I've been having with placing and receiving calls - for some reason, my phone will make a call one minute and then not make one the next, usually connecting to whoever it is I'm calling, but no audio is produced at all. I use Bluetooth in the car, but that isn't the issue, it happened regardless of where I was.
So, I figured something was screwed up in the ROM, and since I don't have the time to reinstall everything even with using Titanium Backup as help, I got NC1 on the phone and then restored my data using Safestrap recovery from NB1 - while I'm very aware that I most likely brought my problem with me, I do believe that restoring data from TiBU would likely do the same thing, and I hate to be so busy right now that I can't even get my phone working by starting clean and then adding back everything one by one in order to ensure working condition, I just have to fix the problem on the back end of this right now....
So now that my phone is on NC1, calls are working okay right now (that may change) but the Bluetooth module will not come on at all. I turn it on, it turns it right off. I can't figure it out and don't even want to pretend I know what I'm doing with reading logcats, so I've attached it below. It contains a filtered logcat using the term "Bluetooth" as a filter. If someone can point me in the right direction, that would be great and I really appreciate it!
EDIT - I have wiped the ROM and installed everything from TiBU, everything works as normal now, just wish I didn't have to set my phone all back up from scratch again, I like using the restore data function of recovery, while not foolproof, it works great to quickly change ROMs and put all the data back on the phone as before
What baseband do you have or did you flash a modem?
Gage_Hero said:
What baseband do you have or did you flash a modem?
Click to expand...
Click to collapse
I did flash a modem, previous to getting NC1, I flashed the NC1 baseband.
Sounds like either something got restored from System data incorrectly or a hardware issue. The only way to confirm is the flash back to oute stock and see if it all works correctly. Then do not restore data from previous ROM and see if it works. Then use Tibu and restore one app at a time and check if it is/is not working.
Also the flash able modems do not contain the non-hlos.bin, so possibly if you have the NC1 or NB1 non-hlos.bin installed from flashing the stock rom, then flashing the modem that ONLY contains the modem.bin it may be a conflict? I do not recall that issue happening on previous firmwares that HAD TO use the matching modem.bin and non-hlos.bin but maybe Sammy did something in the newest releases?
I have used ALL the modems in my thread with no issues. But I am STILL on MDB boot loader, never flashed a non-hlos.bin, and ONLY flashed the modem.bin. I have not had ANY issues at all on any like you describe.
Sent fron I337 Red BadAss Themed ShoStock 7.0
I also have yet to flash non-hlos.bin with any modem.... only modem.bin. I used odin pc 3.07, uncheck the auto reboot, flash the modem, reboot back to download mode, flash the modem again and it has always been good to go.
If it was me, I would download the moden again, check the md5 to ensure the download is good and flash it twice... if that doesn't work.. I would go back to stock..... typically, if I flash a rom, I skip trying to restore anything.... I just let the apps redownload...
Downloaded again, checked MD5, flashed three times (I'm not flashing through Odin, just using the ones RR provided through Safestrap), and still no Bluetooth....
Sounding more and more like I'm going to have to start from scratch instead of dealing with it here, and if I have to do this now and get a new phone in the next few months (come ON Sammy, hurry up with the S5 Prime / Galaxy F / Galaxy Alpha already!), I'm gonna be pissed!
KryptosXLayer2 said:
Downloaded again, checked MD5, flashed three times (I'm not flashing through Odin, just using the ones RR provided through Safestrap), and still no Bluetooth....
Sounding more and more like I'm going to have to start from scratch instead of dealing with it here, and if I have to do this now and get a new phone in the next few months (come ON Sammy, hurry up with the S5 Prime / Galaxy F / Galaxy Alpha already!), I'm gonna be pissed!
Click to expand...
Click to collapse
I don't follow Safestrap too much but don't you have to flash a certain module to get it to work correctly? Again I am not up on Safestrap but I know I have seen a module talked about
Sent fron I337 Red BadAss Themed ShoStock 7.0
RockRatt said:
I don't follow Safestrap too much but don't you have to flash a certain module to get it to work correctly? Again I am not up on Safestrap but I know I have seen a module talked about
Sent fron I337 Red BadAss Themed ShoStock 7.0
Click to expand...
Click to collapse
I have seen something about that too, but like you, I don't know enough about it.... I thought for a modem file, I don't need that, but I've been wrong before!
EDIT - I have wiped the ROM and installed everything from TiBU, everything works as normal now, just wish I didn't have to set my phone all back up from scratch again, I like using the restore data function of recovery, while not foolproof, it works great to quickly change ROMs and put all the data back on the phone as before