I recently got a GS4 in my hands. The details are mentioned below:
Model: GT-i9505
Android version: 4.2.2
Baseband: I9505DXUAME2
Build number: JDQ39.I9505DXUAME2
kernel: 3.4.0-526204
I pulled the source code for the same from the Samsung website. Compiled and deployed it without making any changes to the stock code (ensuring that the instructions are followed neatly...I have been doing it successfully on other Samsung models). My device boots fine but stops detecting the SIM card. I don't know what may be wrong here.
I am not sure if it has to do something with the code which I picked from the Samsung website. I tried using two different source codes but the result remained the same. I see in the kernel logs that exfat_fs and exfat_core drivers are not being loaded due to version mismatch. But I don't think it could be the reason behind my problem.
Any hints as in how can I debug this issue? What can I check in the kernel logs to get to the root cause of this issue?
epitoro said:
I recently got a GS4 in my hands. The details are mentioned below:
Model: GT-i9505
Android version: 4.2.2
Baseband: I9505DXUAME2
Build number: JDQ39.I9505DXUAME2
kernel: 3.4.0-526204
I pulled the source code for the same from the Samsung website. Compiled and deployed it without making any changes to the stock code (ensuring that the instructions are followed neatly...I have been doing it successfully on other Samsung models). My device boots fine but stops detecting the SIM card. I don't know what may be wrong here.
I am not sure if it has to do something with the code which I picked from the Samsung website. I tried using two different source codes but the result remained the same. I see in the kernel logs that exfat_fs and exfat_core drivers are not being loaded due to version mismatch. But I don't think it could be the reason behind my problem.
Any hints as in how can I debug this issue? What can I check in the kernel logs to get to the root cause of this issue?
Click to expand...
Click to collapse
Flash stock rom via odin.
I want to modify one of the drivers in the stock code and that is why I downloaded and compiled the kernel code. But before making my changes, I tried to do a sanity and ran into this problem. Going back to stock is not going to help me. So, essentially I have to find out the reason as in why it is not working with the stock code. Any clues for debugging this issue?
epitoro said:
I want to modify one of the drivers in the stock code and that is why I downloaded and compiled the kernel code. But before making my changes, I tried to do a sanity and ran into this problem. Going back to stock is not going to help me. So, essentially I have to find out the reason as in why it is not working with the stock code. Any clues for debugging this issue?
Click to expand...
Click to collapse
Oh understood. Unfortunately Im not good with that, but you can open thread here http://forum.xda-developers.com/forumdisplay.php?f=2321 Im sure devs will help you.
thanks!!
But I am not allowed to post in that forum as I am a new joinee and only experienced users may post. If that is the case, how can I reach out to the developers?
epitoro said:
thanks!!
But I am not allowed to post in that forum as I am a new joinee and only experienced users may post. If that is the case, how can I reach out to the developers?
Click to expand...
Click to collapse
Is type imei still there or is it corrupted?
Sent from my GT-I9505 using xda premium
sxi200 said:
Is type imei still there or is it corrupted?
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
good point
No. Settings menu doesn't show imei as well as the baseband version once i flash the compiled kernel. But both return as soon as i flash back the stock kernel. Shall i try to recover imei as it essentially doesn't get lost. I believe the real problem is somewhere else and loosing imei is just a side effect of that.
Sent from my GT-I9300 using xda app-developers app
I have verified that the contents of the efs folder don't change between the two kernels.
I mentioned in my first post that ext_fs drivers are not being loaded by the new kernel. Are these two things somehow correlated: efs and ext_fs. Namewise it seems that ext_fs driver reads efs folder. Its just a guess. Does it makes sense to someone else?
Sent from my GT-I9300 using xda app-developers app
Any comments please.
Sent from my GT-I9300 using xda app-developers app
epitoro said:
Any comments please.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I come from an i9000, where imei issues like these are always solved by flashing the stock rom again. Then you can make a backup of your efs folder and start your iterations again. Might also work this way for the s4.
Verstuurd van mijn GT-P5100 met Tapatalk
I was using a wrong config file for the kernel.
Sent from my GT-I9300 using xda app-developers app
One may use the following cmd to genrate the correct config:
make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig SELINUX_DEFCONFIG=jfselinux_defconfig ARCH=arm
Sent from my GT-I9300 using xda app-developers app
Hi im having this issue recently, im not very gppd when it comes to this sort of thing have u sorted out? & if so how did u resolve the issue?
Sent from my GT-I9505 using Tapatalk
eddie500_1 said:
Hi im having this issue recently, im not very gppd when it comes to this sort of thing have u sorted out? & if so how did u resolve the issue?
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
You need to compile the source code available from Samsung Open Source with the attached config file. Steps will be:
1) Goto to the root of your kernel source tree and run this cmd:
make mrproper
2) Extract .config file from zip and place it in the root dir or your kernel source tree
2) Compile using gcc for ARM architecture (ARCH=arm) using the toolchain
Related
Pls am having issues with my bluetooh, I can seem to receive files from any other device, don't know what's wrong pls any helpful info will be nice.
Sent from my FIH-FB0 using xda premium
This is just a guess: I had multiple issues with a "used in mint condition" model I bought from amazon as an import. It had super user on it already and the rom had been debloated and was OBVIOUSLY not stock. Wether the importer got it this way or took a return and tried to fix it, I'm not sure. Check to see if your baseband version and build version (in setting>about device>status or someplace...) are the same or different. If they're different, then its a firmware version/rom mismatch. This messed up mms, wifi connectivity, radio switching from hsdpa/hspa etc...(pain in the ass!)
If you bought your device used, check to make sure this isn't the problem.
Downloading the firmware version for your region and flashing via mobile odin was easiest.... you've got to have a windows comp because the files are compressed using an executable self extractor... its the <name_of_file>.tar.md5 that you want to flash with odin.
Sent from my GT-P6800 using XDA Premium HD app
So I posted a thread here asking for help (the phone was functional at this point) and one user suggested a root method to try out in the comments there http://forum.xda-developers.com/showthread.php?t=2379833
After running this root method my wifi is now dead. It's killing me! Someone please help me out here.
My phone model is a Japanese Softbank 201 M with the 4.1.2 update. It's not rooted but is unlocked. The phone is the developer edition if that helps any.
System version
9.3.102.201M.SBM.en.JP
Model No
201M
Android version
4.1.2
Baseband
SM_T_BP_1539.000.35.03P
Kernel Version
3.0.42-g721d60d
Build Number
9.8.2Q-34_SMJ-102
HBogard said:
So I posted a thread here asking for help (the phone was functional at this point) and one user suggested a root method to try out in the comments there http://forum.xda-developers.com/showthread.php?t=2379833
After running this root method my wifi is now dead. It's killing me! Someone please help me out here.
My phone model is a Japanese Softbank 201 M with the 4.1.2 update. It's not rooted but is unlocked. The phone is the developer edition if that helps any.
System version
9.3.102.201M.SBM.en.JP
Model No
201M
Android version
4.1.2
Baseband
SM_T_BP_1539.000.35.03P
Kernel Version
3.0.42-g721d60d
Build Number
9.8.2Q-34_SMJ-102
Click to expand...
Click to collapse
Ouch. Your WiFi is broken because he told you to flash a US VZW (XT-907) firmware.
Okay. First, you should try to find a 201M restore file. That will get your WiFi back. Next, since you've got a Dev edition, you can bootloader unlock and install a custom recovery, then flash a root zip
EDIT: Found it
http://sbf.droid-developers.org/scorpion_mini_xt902/list.php
Use one of those to restore your WiFi
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Ouch. Your WiFi is broken because he told you to flash a US VZW (XT-907) firmware.
Okay. First, you should try to find a 201M restore file. That will get your WiFi back. Next, since you've got a Dev edition, you can bootloader unlock and install a custom recovery, then flash a root zip
EDIT: Found it
http://sbf.droid-developers.org/scorpion_mini_xt902/list.php
Use one of those to restore your WiFi
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
While the link I gave him was unidentified as to warnings to non vzw users (now fixed) , the flashing of vzw sw comes in step 8 clearly he would have had to have pulled it from a xml himself if he even got that far. And if he did it would have been from reading the rzr op. As the bare motochopper has no vzw sw inside.
aviwdoowks said:
While the link I gave him was unidentified as to warnings to non vzw users (now fixed) , the flashing of vzw sw comes in step 8 clearly he would have had to have pulled it from a xml himself if he even got that far. And if he did it would have been from reading the rzr op. As the bare motochopper has no vzw sw inside.
Click to expand...
Click to collapse
Oh my bad. Thought you sent him to your other post... Still I suspect he got to step 8 and pulled the vz firmware.
OP: Download one of those restore files for the 201M and flash it. That should repair any damage done...
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Oh my bad. Thought you sent him to your other post... Still I suspect he got to step 8 and pulled the vz firmware.
OP: Download one of those restore files for the 201M and flash it. That should repair any damage done...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I didn't get the system img at all. I just wanted to flash the superuser files to /data which I thought would set me up to flash the whole thing with Rom manager.
Anyway, thank you for the help. I am downloading the firmware you linked to now. This guide tells me to edit the XML file and remove the getvar text from it, should this apply here as well? (Edit: Cant post outside links, but I think you get my point)
I'm going to use RSD 6.1.4 to restore the firmware. Any further instructions would be appreciated as I have never done this before.
HBogard said:
I didn't get the system img at all. I just wanted to flash the superuser files to /data which I thought would set me up to flash the whole thing with Rom manager.
Anyway, thank you for the help. I am downloading the firmware you linked to now. This guide tells me to edit the XML file and remove the getvar text from it, should this apply here as well? (Edit: Cant post outside links, but I think you get my point)
I'm going to use RSD 6.1.4 to restore the firmware. Any further instructions would be appreciated as I have never done this before.
Click to expand...
Click to collapse
Don't think you'll need to since it's designed for your device. You can try without the edit and do it if it doesn't work. I'll try to find a guide for RSDLite (been a while since I used it myself - fastboot is usually what I use now...
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Don't think you'll need to since it's designed for your device. You can try without the edit and do it if it doesn't work. I'll try to find a guide for RSDLite (been a while since I used it myself - fastboot is usually what I use now...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Dear sir,
I'd like you to buy a ticket to Karachi right now because I'd run all the way to the airport to KISS YOU until the police dragged me away.
The process worked. My wifi just turned back on. Thank you very much for the weekend stress relief!
I think I'm gonna give up on the idea of rooting this thing until there's a more reliable method available. Also, if anyone has the same issue then take note: I did remove the getvar commands when using RSD.
HBogard said:
.....
Click to expand...
Click to collapse
I am glad SC took care of you & I am sorry I lead you in that direction.
Please fill in some details for others?
How do you have a path to the newer sw? Is it your carriers ota? If you can obtain the same in the xml form there is an easy root using a modded ver w/ unlocked phone. The ota.zip could also be useful if you take it while you have root. It resides in /cache.
Thank you
aviwdoowks said:
I am glad SC took care of you & I am sorry I lead you in that direction.
Please fill in some details for others?
How do you have a path to the newer sw? Is it your carriers ota? If you can obtain the same in the xml form there is an easy root using a modded ver w/ unlocked phone. The ota.zip could also be useful if you take it while you have root. It resides in /cache.
Thank you
Click to expand...
Click to collapse
It wasn't your fault for trying to help, so it's ok. I'm glad a solution existed.
I'm more than willing to answer the questions, but I am a layman here so please explain some things for me: What do you mean by SW? I just installed the update by going into about phone -> system update on Wifi. The carriers here don't even support 3G, much less 4G (So now you know why Wifi was important for me).
The phone came unlocked day one when I bought it from a friend's friend. I don't know if he did it that way or if it comes unlocked because it is the developer edition.
I installed CW Recovery using Fastboot. I installed the incorrect superuser file using Motofail which wrote the superuser file but failed at all other steps. I was then unable to either access or remove this superuser apk file.
Since I am back on 4.0.4. now, what's the easy way to get root access and superuser permissions that you mention? I wish other XT902 owners would post here too, generating interest would really help in getting development support for this phone.
HBogard said:
Dear sir,
I'd like you to buy a ticket to Karachi right now because I'd run all the way to the airport to KISS YOU until the police dragged me away.
The process worked. My wifi just turned back on. Thank you very much for the weekend stress relief!
I think I'm gonna give up on the idea of rooting this thing until there's a more reliable method available. Also, if anyone has the same issue then take note: I did remove the getvar commands when using RSD.
Click to expand...
Click to collapse
Lol no problem, glad to know it worked. Getting root is actually really simple since you're unlocked. All you need to do is flash a custom recovery and flash a root .zip from there... No exploits required
I can try to write up a guide to that if you want
Sent from my XT907 using Tapatalk 4
sloosecannon said:
Lol no problem, glad to know it worked. Getting root is actually really simple since you're unlocked. All you need to do is flash a custom recovery and flash a root .zip from there... No exploits required
I can try to write up a guide to that if you want
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
I tried that, and while it did install superuser, it seemed to have no effect. I couldn't get permissions for any app and using ROM manager's functions would just freeze up that particular application. Any ideas?
HBogard said:
It.
Click to expand...
Click to collapse
Once you root on 404 you can grab your update.zip & copy it to your sd . Any rooting exploit would evolve from that Or the newest xml ver of the 404 you just flashed from rsd. You may be able to request it from your carrier.
---------- Post added at 01:21 PM ---------- Previous post was at 12:40 PM ----------
You can paste the mods from my vzw restore (no vzw software will be used) into the 404 xml & obtain root from a preinstalled cwmr! Then maintain root with voodoo for your ota.
I will help you just read the op. Link is in my signature.
HBogard said:
I tried that, and while it did install superuser, it seemed to have no effect. I couldn't get permissions for any app and using ROM manager's functions would just freeze up that particular application. Any ideas?
Click to expand...
Click to collapse
Hmm... Which zip did you use?
Sent from my XT907 using Tapatalk 4
sloosecannon said:
Hmm... Which zip did you use?
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
http://www.aosp.us/wp-content/files/Root.zip <- This one.
HBogard said:
http://www.aosp.us/wp-content/files/Root.zip <- This one.
Click to expand...
Click to collapse
I am making a xml to gain root. Which of the two xmls did you flash? & why.
the smj-165 must be newer.
aviwdoowks said:
I am making a xml to gain root. Which of the two xmls did you flash? & why.
the smj-165 must be newer.
Click to expand...
Click to collapse
7.7.1Q-164_SMJ-143_SCORPION_MINI_SBM_SIGNED_CFC
I used this one. Why? I saw them posted somewhere else as while while doing a little research on using RSD and saw that the mirrors on that other link mentioned JP in the file name - I have the Japanese softbank model so I figured this was the one specific to my phone. Turned out to be right.
HBogard said:
http://www.aosp.us/wp-content/files/Root.zip <- This one.
Click to expand...
Click to collapse
Try this. Which recovery are you using? ClockworkMod or TWRP?
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Try this. Which recovery are you using? ClockworkMod or TWRP?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I did use this one. It didn't work for me. Clockwork mod always gave an error for writing superuser.apk or something.
HBogard said:
I did use this one. It didn't work for me. Clockwork mod always gave an error for writing superuser.apk or something.
Click to expand...
Click to collapse
I'm an idiot and forgot the link...
http://forum.xda-developers.com/showthread.php?t=1538053
Sent from my Nexus 7 using Tapatalk 4
HBogard said:
7.7.1Q-164_SMJ-143_SCORPION_MINI_SBM_SIGNED_CFC
I used this one. Why? I saw them posted somewhere else as while while doing a little research on using RSD and saw that the mirrors on that other link mentioned JP in the file name - I have the Japanese softbank model so I figured this was the one specific to my phone. Turned out to be right.
Click to expand...
Click to collapse
Can you upload the xml only ~ 1kb
Hey @ll. I've just gotten a new SGH-I337M (build number JDQ39.I337MVLUAMG1) from Bell in Canada. I've been trying every root method I can find on the net and they all fail. I started with motochopper running from linux and eventually tried a manual method running psneuter on the device and no go. Tonite I've gotten a winblows vm going and tried odin. FAIL!... I've finally noticed (with a magnifying glass) that when in download mode, the last line of the tiny text in the top right says: WRITE PROTECTION: Enable. From what I've read, I think this means it has a locked bootloader. Is this right? Has anyone heard of this happening with Canadian Bell phones and is there any way around it?
Thanks in advance.
I just checked my download mode.
It says the same, so I think there not locked. But I can flash whatever I want.
Did you try ctautoroot from chainfire?
Or try updating your driver for samsung
Sent from my SGH-I337M using xda app-developers app
---------- Post added at 06:38 AM ---------- Previous post was at 06:37 AM ----------
Or try a real windows pc not a vm under Linux.
Sent from my SGH-I337M using xda app-developers app
crzygrmn said:
I just checked my download mode.
It says the same, so I think there not locked. But I can flash whatever I want.
Did you try ctautoroot from chainfire?
Or try updating your driver for samsung
Sent from my SGH-I337M using xda app-developers app
---------- Post added at 06:38 AM ---------- Previous post was at 06:37 AM ----------
Or try a real windows pc not a vm under Linux.
Sent from my SGH-I337M using xda app-developers app
Click to expand...
Click to collapse
Yeah, cfautoroot was the latest one I tried which uses odin. The phone was recognized in the vm and connected to odin just fine so I don't thing using a vm is the problem. As I said, I tried a few methods on the linux system with the phone directly connected as well and got the same results. Everything seems to be working until the point where something has to be written to the device and it fails. Even a manual method where psneuter is transfered to the device and run from there and it won't work.
Well the only thing I can say is try a reall windows machine not some windows vm
Sent from my SGH-I337M using xda app-developers app
crzygrmn said:
Well the only thing I can say is try a reall windows machine not some windows vm
Sent from my SGH-I337M using xda app-developers app
Click to expand...
Click to collapse
Thanks anyways.
Now can anyone at least tell me how to determine if the device has a locked bootloader?
if it is a 337M (with the M) it does not have a locked bootloader. PERIOD
TRusselo said:
if it is a 337M (with the M) it does not have a locked bootloader. PERIOD
Click to expand...
Click to collapse
Well thats encouraging. It does have the 'M' but several attempts at rooting with recognized methods have all failed. What else could be the problem?
According to the CFAutoroot thread, MG1 should work just fine. You might want to go to that thread (or go back to it) and make sure you read / re-read the entire thread to make sure you are using the proper procedure. Good luck.
did you download the NEW cfautoroot? it was updated for our phone last month or so...
*#7284# change back to pda
*#9090#, make sure its usb and not uart,
*#0808#
Your phone should root now using proper computer , driver and root required files.
Sent from my LG-D801 using xda app-developers app
gotshoaib said:
*#7284# change back to pda
*#9090#, make sure its usb and not uart,
*#0808#
Your phone should root now using proper computer , driver and root required files.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply gotshoaib, but I need more info. The first code does nothing on my phone, the second brings me to a 'ServiceMode' screen. What settings should I have here? The third brings me to 'USBSettings'. What should be the settings here?
Well success at last! I allowed the new update to 4.3 (MVLUEMK6), used the CFAutoRoot process again and it worked this time. I have no idea why but it did.
SGS4 I337M Bootloader Is Unlocked
TRusselo said:
if it is a 337M (with the M) it does not have a locked bootloader. PERIOD
Click to expand...
Click to collapse
I just purchased an S4 BELL SGH-I337M which was on AMG1 when I received it. I flashed TWRP on it and then decided to install stock firmware AMDJ. Then I flashed GUMMY ROM which is pre-rooted. Since I did all this flashing, that also proves it is unlocked so I will have to go along with TRusselo. It is unlocked. :good: I won't say period though, BELL and canadian carriers could change their minds and start locking them.
AHLASSICH said:
I just purchased an S4 BELL SGH-I337M which was on AMG1 when I received it. I flashed TWRP on it and then decided to install stock firmware AMDJ. Then I flashed GUMMY ROM which is pre-rooted. Since I did all this flashing, that also proves it is unlocked so I will have to go along with TRusselo. It is unlocked. :good: I won't say period though, BELL and canadian carriers could change their minds and start locking them.
Click to expand...
Click to collapse
Yeah, nothing is set in stone!
rijo79 said:
Hey @ll. I've just gotten a new SGH-I337M (build number JDQ39.I337MVLUAMG1) from Bell in Canada. I've been trying every root method I can find on the net and they all fail. I started with motochopper running from linux and eventually tried a manual method running psneuter on the device and no go. Tonite I've gotten a winblows vm going and tried odin. FAIL!... I've finally noticed (with a magnifying glass) that when in download mode, the last line of the tiny text in the top right says: WRITE PROTECTION: Enable. From what I've read, I think this means it has a locked bootloader. Is this right? Has anyone heard of this happening with Canadian Bell phones and is there any way around it?
Thanks in advance.
Click to expand...
Click to collapse
I377m is not locked. No Canadian handsets are. Locked boot loaders seem to be an American phenomenon
Sent from my SGH-I337M
azuziel said:
I377m is not locked. No Canadian handsets are. Locked boot loaders seem to be an American phenomenon
Sent from my SGH-I337M
Click to expand...
Click to collapse
Mexican version is also i337M. Is its bootloader locked?
I rooted my i337m with CF-auto root and no problems what so ever.
Currently using Philz touch recovery 6.00.8 and Slimbean 4.3 build 2.2.
Everything you need is here on xda just need to look for "Samsung latest drivers, cf-auto root, Odin 1.85" plug your phone in and root
Slim Roms powered
1337m
4.3.1. build 2
Hello XDA.
I have a:
Galaxy S4 SGH-I337M (IT'S EITHER A BELL/ROGERS PHONE)
BASEBAND VERSION: I1337MVLUAMDJ
KERNAL VERSION: 3.4.0-1529758 [email protected]#1
BUILD NUMBER: K0T49H.1337MVLUFNE1
The problem is, I had rooted my phone long time ago and wanted to recently unroot and update to the latest KitKat version (I was on jellybean). It would not let be update because it said the device was modified or something of that sort. I tried to unroot by following a tutorial online and flashing with a stock rom.
I did exactly as it says but now my phone is totally messed up. My Wifi no longer works, the apps keep crashing and nothing is working like its suppose too. I do not know what to do to fix this. How do I return my phone back to factory settings as if it is brand new? I have tried flashing stock roms 3 times new (3 different ones using ODIN) and nothing seems to work. I have tried samsung kies and it is still doing the same thing!
Please help.
ruckfules99 said:
Hello XDA.
I have a:
Galaxy S4 SGH-I337M (IT'S EITHER A BELL/ROGERS PHONE)
BASEBAND VERSION: I1337MVLUAMDJ
KERNAL VERSION: 3.4.0-1529758 [email protected]#1
BUILD NUMBER: K0T49H.1337MVLUFNE1
The problem is, I had rooted my phone long time ago and wanted to recently unroot and update to the latest KitKat version (I was on jellybean). It would not let be update because it said the device was modified or something of that sort. I tried to unroot by following a tutorial online and flashing with a stock rom.
I did exactly as it says but now my phone is totally messed up. My Wifi no longer works, the apps keep crashing and nothing is working like its suppose too. I do not know what to do to fix this. How do I return my phone back to factory settings as if it is brand new? I have tried flashing stock roms 3 times new (3 different ones using ODIN) and nothing seems to work. I have tried samsung kies and it is still doing the same thing!
Please help.
Click to expand...
Click to collapse
Where did you get the stock firmware? Go to sammobile.com if you haven't already done so
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Where did you get the stock firmware? Go to sammobile.com if you haven't already done so
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I will try now quickly and post my results. I have tried from 3 different sites and no luck.
ruckfules99 said:
I will try now quickly and post my results. I have tried from 3 different sites and no luck.
Click to expand...
Click to collapse
You have to register but it's free. You'll download a zip. Use 7-zip to extract a .tar.md5 file. Use that in Odin
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You have to register but it's free. You'll download a zip. Use 7-zip to extract a .tar.md5 file. Use that in Odin
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The websites downloads are very slow. I am currently downloading it and will attempt to flash it. The problem is, I believe I have already tried this and might have somehow messed something else up such as the kernel or something.
Do you know if this could be the case?
ruckfules99 said:
The websites downloads are very slow. I am currently downloading it and will attempt to flash it. The problem is, I believe I have already tried this and might have somehow messed something else up such as the kernel or something.
Do you know if this could be the case?
Click to expand...
Click to collapse
No, it would not be the case. Odin flashes the entire firmware, kernel and all. Sammobile is an official site for the firmware so if it doesn't work you might have a hardware issue. But wait for the download.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
No, it would not be the case. Odin flashes the entire firmware, kernel and all. Sammobile is an official site for the firmware so if it doesn't work you might have a hardware issue. But wait for the download.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'll definitely try flashing this one. Any specific instructions with ODIN for this? (I might be doing something wrong). Also, I do not believe its a hardware issue as it was fine before I attempted to unroot it today and make it factory default stock rom
ruckfules99 said:
I'll definitely try flashing this one. Any specific instructions with ODIN for this? (I might be doing something wrong). Also, I do not believe its a hardware issue as it was fine before I attempted to unroot it today and make it factory default stock rom
Click to expand...
Click to collapse
Just load it into PDA and only have auto-reboot and f.reset checked
Sent from my Nexus 5 using XDA Free mobile app
I have flashed the official one from that website and same problem. My WIFI does not work and there are random glitches like the phone being slow and etc. I don't understand what I could have done to cause this and what could possibly be done to fix it.
I think the modem may be an issue. Can someone please confirm?
ruckfules99 said:
I have flashed the official one from that website and same problem. My WIFI does not work and there are random glitches like the phone being slow and etc. I don't understand what I could have done to cause this and what could possibly be done to fix it.
I think the modem may be an issue. Can someone please confirm?
Click to expand...
Click to collapse
When you say Wi-Fi doesn't work what do you mean?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
When you say Wi-Fi doesn't work what do you mean?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It literally does not work. Does not let me connect to it. I cannot even make calls. I have tried everything. I think it's something to do with modem. Same issue this user had:
http://forum.xda-developers.com/showthread.php?t=2753001
ruckfules99 said:
It literally does not work. Does not let me connect to it. I cannot even make calls. I have tried everything. I think it's something to do with modem. Same issue this user had:
http://forum.xda-developers.com/showthread.php?t=2753001
Click to expand...
Click to collapse
So when you try to slide to turn on Wi-Fi it just pops back to off? The other guy had an i337 which is different than yours. What worked for his isn't going to work for you
What firmware version did you flash in Odin?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
So when you try to slide to turn on Wi-Fi it just pops back to off? The other guy had an i337 which is different than yours. What worked for his isn't going to work for you
What firmware version did you flash in Odin?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
When I try to slide the WIFI tab, it slides back to off by itself. My phone is i337M and mine and his have a similar issue but different phone type. I flashed 4.4.2 with Odin.
I honestly believe that it's a problem with the kernel/modem. Do you know of a way to change EVERYTHING back to factory settings?
Odin flashes everything back to stock, like new. Try the mk6 version of the firmware.
Edit, what version of Odin ate you using?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Odin flashes everything back to stock, like new. Try the mk6 version of the firmware.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Could you tell me what that means exactly? I'm new to all of this stuff and have no idea. Anything to fix my phone....
ruckfules99 said:
Could you tell me what that means exactly? I'm new to all of this stuff and have no idea. Anything to fix my phone....
Click to expand...
Click to collapse
Mk6 is android 4.3
Sent from my Nexus 5 using XDA Free mobile app
I've tried. Still doesn't work :'(
ruckfules99 said:
I've tried. Still doesn't work :'(
Click to expand...
Click to collapse
Not sure what else to tell you. If Odin isn't working you may have a hardware issue. Odin should return engaguing to like new. The only thing I can think of is you have an issue with the emmc memory, which isn't good.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Not sure what else to tell you. If Odin isn't working you may have a hardware issue. Odin should return engaguing to like new. The only thing I can think of is you have an issue with the emmc memory, which isn't good.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It won't even boot up. It's stuck on the samsung logo.
ruckfules99 said:
It won't even boot up. It's stuck on the samsung logo.
Click to expand...
Click to collapse
Can you boot into recovery? Do a factory reset in recovery
Sent from my Nexus 5 using XDA Free mobile app
I've been wanting to put Cyanogenmod on my S4 ever since I got it, but everywhere I look seems to tell me I can't.
Which leads to why I'm here, I want to know once and for all, can I load Cyanogenmod (Or any custom ROM for that matter) onto my phone?
It is rooted. If you need to know more please ask.
Model Number: SAMSUNG-SGH-I337
Android Version: 4.2.2
Baseband Version: I337UCUAMF3
Build Number: JDQ39.I337UCUAMF3
Serial Number: R31DB10A7EE
MF3 and above are locked, you are unable to install CM, but read about Safe Strap in order to install other ROMs
@daxter304 Dude, you really should not post your imei number. Edit you post to remove it.
Sent from my Nexus 5 using XDA Free mobile app
Thank you for the replies, and that is unfortunate to hear =\
What about the IMEI number makes it so I shouldn't post it? I checked and it seemed to just be info about my phone but nothing personal I thought.
daxter304 said:
Thank you for the replies, and that is unfortunate to hear =\
What about the IMEI number makes it so I shouldn't post it? I checked and it seemed to just be info about my phone but nothing personal I thought.
Click to expand...
Click to collapse
People can use it on a stolen phone where the real imei is black listed
Sent from my Nexus 5 using XDA Free mobile app