Related
I have Galaxy S4 i9505. I downloaded latest MEA firmware from sammobile I wanna update via odin. WHen I get into download mode. It says Write Protection : Enable. Will this effect from flashing via odin? Is it safe to flash? I have not rooted my phone, original stock rom doesn't give me the latest update of firmware. So I would like to update it myself. Even kies doesn't have it.
Please assist me. Thank you all.
I really don't want an expensive brick.
Yep just flash newest firmware whit odin
Sent from my GT-I9505 using xda premium
Mine said exactly the same... nothing to worry about, just flash as normal through Odin
I tried flashing CWM recovery instead. it says success but I still do not get CWM recovery. What did I do wrong?
yvliew said:
I tried flashing CWM recovery instead. it says success but I still do not get CWM recovery. What did I do wrong?
Click to expand...
Click to collapse
for boot into CWM , you hold "power + volume up + home" after shutdown phone
I have a "GT-I9505". I was able to Odin TWRP. My objective is actually to turn it into an SGH-I337M, a bootloader unlocked version of SGH-I337, which is locked. All 3 are S4 variants. The mainboard of my SGH-I337M recently died. Since I couldn't find a replacement I337M board anywhere, and my research shows the mainboard of these 2 variants are interchangeable, hardware-wise, I bought an I9505 mainboard and dropped it in. An I9505 certainly comes with I9505's bootloader and baseband. Since I live in the U.S., I'd like to replace at least the baseband to North America, ie. my original I337M baseband. However, when I tried to Odin either the entire I337M stock ROM or just the baseband alone, it kept failing due to (AUTH). Since I was able to Odin TWRP, does it not imply the bootloader of my I9505 is unlocked? If it is unlocked, why is it preventing the baseband or the entire ROM from being flashed? I do have this "WRITE PROTECTION: Enable" message on my download mode screen too, but you guys have determined it can be ignored. Thank you in adv for any tips.
luckysoul777 said:
Since I live in the U.S., I'd like to replace at least the baseband to North America, ie. my original I337M baseband. However, when I tried to Odin either the entire I337M stock ROM or just the baseband alone, it kept failing due to (AUTH).
Click to expand...
Click to collapse
The I9505 is bootloader unlocked and comes that way by default; it's the US that loves locking bootloaders. Regardless, you CANNOT mix and match boards and basebands, as the low-level firmware in the S4 will detect the mismatch and reject the change. I know, as I attempted it with a flashable zip on my I9505. The device refused it and would not install it. Odin will reject it as well, for the same reason.
You would have to re-program the cellular radio's low level firmware to accept North American bands. People have tried it, including myself, but most of them were unsuccessful, including me. There is a thread in the forums here explaining what to do. Read it, and good luck.
I want to flash an Aussie ROM on my HK 32GB n9005. I've been doing some reading and what I think I need to do is as follows...
ghibli3's thread at http://forum.xda-developers.com/showthread.php?t=2550823 specifically addresses this issue and thanks to those contributing there and elsewhere.
Now to check I understand what they are saying before I brick my phone.
I have these:
CSB_signed_HLTE_EUR_OPEN_32G_0718.pit
CSB_signed_HLTE_EUR_OPEN_32G_0805.pit
ghibli3-N9005.pit
ratcom-N9005.pit
I also used ghibli3's N9005-SaveMyPit from http://forum.xda-developers.com/attachment.php?attachmentid=2426123&d=1385903491 to get a copy of my current pit.
I have my original HK MI7 stock, a HK stock MK2 (used to root my phone originally using RDLV) and both an MI7 and MJ7 Aussie ROMs.
So... here is what I think I need to do... Please let me know if this is correct or tell me how to do it better.
Using Odin and with phone in DL mode, USB Debugging on, Samsung drivers and ADB setup on PC...
1. Load a PIT file in [PIT] in Odin and tick [Re-Partition] then [Start]
(1st question, do I reboot the phone or just go to the next step?)
2. Follow RDLV steps to flash the Aussie MJ7 to root the phone.
(2nd question, should I drop back to the MI7 version for the root operation? I don't think it is needed as when I rooted my phone with HK version, I had HK MI7 on the phone and used HK MK2 to root it)
(3rd question, I have Kies 3 on my PC - should I uninstall it before doing any of this or might it be helpful to have it still installed?)
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Journyman16 said:
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Click to expand...
Click to collapse
For using PIT file, you need to add the PIT to Odin when you flash so it'll repartition as it's flashing. However, don't take that as a solid cause I am not 100% sure myself as I haven't messed with PIT files (yet) - but from what I have read that is how it is done. - Have a scan through the HK bricked (solved) threads to be doubley sure cause yeah, it's easy to end up with a brick
Thanks for that. Kinda what I was planning to do but I'm not sure if I do the PIT flash first then do the rest or if I do it all as one process. I'll check out that thread... been looking anywhere I could find a PIT reference.
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Journyman16 said:
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Click to expand...
Click to collapse
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
So this gets a bit strange now... I downloaded Phone Info from Play Store and ran it. I did that because I noticed I was having Wifi issues - it was working but kept thinking it was off - I'd click it to turn it on and the button wouldn't go green, but I had signal in the Notification bar. Going to Recovery to clear cache showed it was now applying CSC-code as BTU instead of TGY, so SOMETHING worked when I was doing the PITs.
So, Phone Info shows my Region Code as BTU, my CSC country as UK/IRE and my CSC Country ISO as GBBut I have a mix of ROM info:
Bootloader: ZHUBMI7
Baseband: ZHUDMJ9
PDA: XXUDMK2
CSC: OXADMK2
So, PDA and CSC are from a UK MK2 I tried to use early on and failed with, while BL and BB are from the original HK MI7 (BL) and the HK MK1 I rooted with.
So my question is now, can I now flash a BTU or other normal ROM onto my phone, using the RDLV process to make sure I get root and don't trip Knox?
IIRC I think the process works up to MK2 (and certainly does to MK1 as that what I used originally) so I should be able to DL (say) XXUBMJ1 to use for the BL and use XXUDMK2 for the root process. (i.e. the same as I did using HK MI7 for the BL and HK MK1 for the root process)
3 questions:
1. Is it the PDA that determines the partition Hong Kong users have such problems with? Or is it the Bootloader?
2. Can anyone think of a reason why this would not work? (now my CSC is BTU)
3. Could I now use an Aussie ROM to run the RDLV process?
FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Journyman16 said:
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Click to expand...
Click to collapse
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
Unfortunately, PIT's don't seem to come easy. As above I have about 4 of them I tried. There seems a bit of a disconnect between what the AP/CP/CSC are and what the files in a ROM are e.g. in XXUBMH1 there's boot.img, recovery.img, system.img.ext4, userdata.img.ext4, persdata.img.ext4, persist.img.ext4 and in XXUBMI7 there's sbl1.mbn, aboot.mbn, rpm.mbn, tz.mbn, sdi.mbn, NON-HLOS.bin, boot.img, recovery.img, system.img.ext4, modem.bin, cache.img.ext4, hidden.img.ext4
While I've been around a while now, this seems to be a blank spot for me at present - how do I flash a CSC? From reading it seems some ROM.s come with 4 or 5 files, e.g. see attachment - but I haven't been able to find one yet. (the one in the pic was hosted on Hotfiles which is now defunct thanks to the Almighty USA draconian control freaks. )
Update: I think I have found a copy of it so I can try that when it finishes DL'ing.
Other than that, anyone know of where there might be another such ROM to DL? Also if I am flashing a CSC file do I flash the PIT as well (i.e. at the same time) or do the PIT first?
Which Odin options get ticked for a PIT? I tried [F. Reset Time] [Re-Partition] [Auto Reboot] [Nand Erase All] previously and it didn't seem to work. I saw a recovery type post that suggested ticking [Phone EFS Clear] but seems to me that is a tick towards Brick - and the Recovery being offered was to a KK ROM anyway.
FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Journyman16 said:
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Click to expand...
Click to collapse
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
FeralFire said:
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
Click to expand...
Click to collapse
Well, it let me flash the vega BTU MK2 ROM but now there's a wifi problem. Still waiting for cygwin to download so I can RDLV on the XSA ROM. There seems to be some kind of conflict between BTU and Australian settings. Says to turn on wireless and actually finds my SSID's but then doesn't connect properly. le sigh...
Well it's been coming up to 24 hours with no phone but I seem to have found my way.
The problem seems to have been a mismatch between BL, CSC and PIT. In trying to get off the Hong Kong set up I wound up with a ZHU BL, BTU CSC and XSA CP and AP. It worked but I had no wifi. tried a few things to get it working and in trying to flash an XSA CSC (I think it was XSA) I got the Knox bit change. With no wifi I thought maybe the problem was the BUT-based CP needed changing. In trying to fix that, somehow I triggered Knox
I tried DL & Install of Omega 6 (it's a 4.3 - not ready to go KK yet) but although it completed nicely (so many ROM's got hidden or system errors in Odin) the phone didn't start. I tried installing Philz so I could run things from the extSDcard but an XSA wouldn't work nor would anything I had below MJ7. Last Phone Info view I had I still had a ZHU CP, even though AP and CSC were XSA-based.
Finally I got the MJ7 ROM from http://forum.xda-developers.com/sho...9005xxudmj7-pre-rooted-knox-free-odex-bl-free and it did the trick.
It's been a learning experience but I'd be happier if I knew for sure both what triggered the Knox bit (I was being very careful about it) and why some of the other ROM installs simply didn't work.
Resurrecting this one because I'm looking for info on flashing my 32G HK Note 3, but it came with KK pre-installed. So I'm not sure what differences I have to be aware of. Any tips?
For whoever still experiences issues with HK 32GB n9005 devices, After wasting half a day on that crap, i was able to flash N9005ZSUGOK2_N9005OZSGOK2_TGY from sammobile coupled with the PIT attached.
sm-n900
sm-900 and pit
Hi all,
Long time lurker, first time poster
I've been experimenting with a spare i9505 that I have, flashing roms etc (it was having serious wifi issues so I was trying to fix it)
However something's gone wrong and I now have the 'Firmware upgrade experienced an issue' screen, and Knox Warranty is 0x1. I don't really care about it as it's a spare, but I'd like to flash a ROM to it so that it at least works.
I'm not exactly a power user when it comes to this stuff, more an 'enthusiastic amateur'. I followed instructions in a similar thread to flash TWRP and use that to Advanced Wipe before flashing a new ROM, which I've done, but the threads I've found feature loads of ROMs and I don't know which one to use. I found a couple that I tried to use, but Odin is failing every time and SW Rev Check Fail pops up on the screen, which I believe (from more lurking!) means I'm trying to use the wrong firmware.
Was hoping someone here could point me in the right direction!
Just to recap the phone status:
- S4 i9505
- UK based (came from Vodafone if that matters?)
- Firmware update encountered an issue
- Knox Warranty Void 0x1
- Previously running 4.2.2
Thanks guys
Knox warranty void cannot be recoverd till now
Sent from my GT-I9500 using Tapatalk
aayushkhajuria2842 said:
Knox warranty void cannot be recoverd till now
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
I'm not worried about the warranty, I've read up on it and I know that's a lost cause. I just want the phone to work really as it's currently displaying 'Firmware update encountered an issue' on boot. I only mention the 0x1 thing as from my research I understand that it limits you in terms of what ROMs you can install, meaning I would need a particular one to get the phone working again.
Thanks!
Then install stock firmware via odin first
Sent from my GT-I9500 using Tapatalk
aayushkhajuria2842 said:
Then install stock firmware via odin first
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
... That's kinda the point of my post. I know what I need to do, I just don't know which file to use.
For example, this thread http://forum.xda-developers.com/showthread.php?t=2250824 has a bunch of stock firmware files, but I don't know which one I would need to download, for my specific circumstance.
What firmware u tried to install? If u tried to install android 4.3 or android 4.4.2 maybe ur bootloader is updated and u cant flash android 4.2.2. Give us more info :fingers-crossed:
Joku1981 said:
What firmware u tried to install? If u tried to install android 4.3 or android 4.4.2 maybe ur bootloader is updated and u cant flash android 4.2.2. Give us more info :fingers-crossed:
Click to expand...
Click to collapse
I was worried that might be the case.
OK so I've tried two md5 files so far:
I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.tar.md5
I9505XXUFNB8_I9505BTUFNB3_I9505XXUFNB8_HOME.tar.md5
To PROPERLY go back and re-cap from beginning...
- Phone was stock, wi-fi didn't work (worked for a bit, then cut off and wouldn't come back on)
- Ran CyanogenMod Installer to update and hopefully fix the issue
- Install was successful but didn't fix wi-fi issues
- Used Odin to flash the 2nd md5 listed above, went back to stock but wi-fi still didn't work
- Tried to flash the 1st md5 listed above, didn't work and must have errored at some point as now I get that 'Firmware upgrade encountered an issue' message.
- Looked up the issue in a thread on here, followed instructions to flash TWRP, boot into Recovery > Wipe > Advanced wiping everything bar last two options, and then 'install your stock recovery firmware'
Only issue I have now, I don't know which file that is As I say the last two I tried (above) give me the SW Rev error, so they're clearly incorrect.
I don't care about warranty, and I don't care about root either really... just want the phone to work again, even on stock!
Well. Step by step:
- You will have to WIPE all
- If the phone is branded to Vodafone is one thing, if not is other.
- I let u the correct firmware for ur phone with Vodafone: HERE or HERE
- If ur phone is unbranded the correct firmware is: HERE
- Download it and flash it through ODIN
- If u have problems with ODIN, paste it here and good luck :highfive:
Awesome! Thanks man, the phone came from Vodafone initially but I don't think it's branded (no logos on the phone, no Vodafone logo on boot)
I'm downloading both just to make sure. Will let you know results ASAP! Thanks again :good:
I recently bit off more than I could chew with my S4 (I337). I had 4.4.2 KitKat on it and wanted to root it to add teathering. I decided thought there was no root for 4.4.2 so I thought I would try downgrading to 4.3 then root. This seemed best because I didn't like the way the SD card is handled in 4.4.2 and some of my apps (like ftp server) have stopped working.
When I got the phone back up from flashing with Odin it says it has version 4.3. My WiFi will not turn on. If I slide the switch to on it slides right back to off and the phone tells me that an operation was block (can't remember the full verbage. I have installed and attempted to install many things on my phone. I have used recovery mode / Odin3 and Kies (Kies doesn't allow much).
At this point I just would like to get my phone back to 4.4.2 with the WiFi working. Then I can restore my backup and be back to square one with a lesson learned.
I have an I337 that currently thinks it has version 4.3 on it. The baseband version is I337UCUFNC1 currently. The build number is JSS15J.I337UCUEMK2.
If anyone can help I would greatly appreciate it. I have read and tried many things over a two day period and finally decided to ask for help.
Had this issue before on my Bell Canada S4, but don't recall exact way to fix it.
Think the solution was to find an older (might be newer) stock. I think I used a different version like the Telus Canada version as well and it ended up working. Then you update through kies after.
jbrudda said:
I recently bit off more than I could chew with my S4 (I337). I had 4.4.2 KitKat on it and wanted to root it to add teathering. I decided thought there was no root for 4.4.2 so I thought I would try downgrading to 4.3 then root. This seemed best because I didn't like the way the SD card is handled in 4.4.2 and some of my apps (like ftp server) have stopped working.
When I got the phone back up from flashing with Odin it says it has version 4.3. My WiFi will not turn on. If I slide the switch to on it slides right back to off and the phone tells me that an operation was block (can't remember the full verbage. I have installed and attempted to install many things on my phone. I have used recovery mode / Odin3 and Kies (Kies doesn't allow much).
At this point I just would like to get my phone back to 4.4.2 with the WiFi working. Then I can restore my backup and be back to square one with a lesson learned.
I have an I337 that currently thinks it has version 4.3 on it. The baseband version is I337UCUFNC1 currently. The build number is JSS15J.I337UCUEMK2.
If anyone can help I would greatly appreciate it. I have read and tried many things over a two day period and finally decided to ask for help.
Click to expand...
Click to collapse
Root, install safestrap then flash this ROM and you will be good to go: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
Thanks
muniz_ri said:
Root, install safestrap then flash this ROM and you will be good to go: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
Click to expand...
Click to collapse
Quite a few steps in those threads but I got it working again. I really appreciate all the help/advice given. Now to decide if I want to remove the safestrap screen on boot. Again Thanks.
Same problem,need help plz
Hi guys,
I have the same problem as jbrudda.i wiped everything using Odin3_v3.09 and AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar . and now my wifi is not working. when i try to turn it on a security message pop up (the device has detected an application attempting to perform actions that are not permitted these actions have been blocked)and ask me to reboot, then it does a factory reset on its own. but the problem is still there no wifi. my baseband is diffrent than jbrudda's. mine is I337UCUAMDB. can someone plz help. thank you
karim8888 said:
Hi guys,
I have the same problem as jbrudda.i wiped everything using Odin3_v3.09 and AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar . and now my wifi is not working. when i try to turn it on a security message pop up (the device has detected an application attempting to perform actions that are not permitted these actions have been blocked)and ask me to reboot, then it does a factory reset on its own. but the problem is still there no wifi. my baseband is diffrent than jbrudda's. mine is I337UCUAMDB. can someone plz help. thank you
Click to expand...
Click to collapse
Wifi does not work because of the modem/kernel mismatch, i.e. MDB modem and MK2 kernel. Not sure what your goal was when you began flashing your phone but since you fortunately did not flash teh MK2 bootloader you are still able to locate the MDB full odin tar and flash back to stock which will resolve your issue.
muniz_ri said:
Wifi does not work because of the modem/kernel mismatch, i.e. MDB modem and MK2 kernel. Not sure what your goal was when you began flashing your phone but since you fortunately did not flash teh MK2 bootloader you are still able to locate the MDB full odin tar and flash back to stock which will resolve your issue.
Click to expand...
Click to collapse
I did Root it with saferoot and safestarp.the wifi didnt work so i had to find a script here on xda and i run it throughout universal init.d . i didnt like the way my phone was running . so i decided to unroot it . so you think im using the wrong TAR file ???
karim8888 said:
I did Root it with saferoot and safestarp.the wifi didnt work so i had to find a script here on xda and i run it throughout universal init.d . i didnt like the way my phone was running . so i decided to unroot it . so you think im using the wrong TAR file ???
Click to expand...
Click to collapse
It depends on what you are trying to accomplish. Are you trying to upgrade to MK2 or higher while maintaining your unlocked MDB bootloader?
muniz_ri said:
It depends on what you are trying to accomplish. Are you trying to upgrade to MK2 or higher while maintaining your unlocked MDB bootloader?
Click to expand...
Click to collapse
I'm just trying to take it back to the why it was. and upgrade to kitkat. i have now build number JSS15J.I337UCUEMK2 baseband : I337UCUAMDB
what do you think i should do?? I appreciate your help.
karim8888 said:
I'm just trying to take it back to the why it was. and upgrade to kitkat. i have now build number JSS15J.I337UCUEMK2 baseband : I337UCUAMDB
what do you think i should do?? I appreciate your help.
Click to expand...
Click to collapse
If you don't care about losing your MDB unlocked bootloader you can get to the latest kitkat firmware by flashing the NB1 full odin tar from here:
http://forum.xda-developers.com/showthread.php?t=2674223, then once flashing is complete go to settings/more/about phone/software update then take the ota update to NC1 which is the latest kitkat version for our phone.
But what I would do is keep your unlocked MDB bootloader and since you already flashed the MK2 AP file you can get your phone running well again by flashing the MK2 modem: https://mega.co.nz/#!pwESna5I!YK7EKG37xXIG1ReB-Z-mfSMoXNkXQ9t2EdMK9ofgJKg
From there, there are still a number of options available to get to kitkat which I won't get into.
muniz_ri said:
If you don't care about losing your MDB unlocked bootloader you can get to the latest kitkat firmware by flashing the NB1 full odin tar from here:
http://forum.xda-developers.com/showthread.php?t=2674223, then once flashing is complete go to settings/more/about phone/software update then take the ota update to NC1 which is the latest kitkat version for our phone.
But what I would do is keep your unlocked MDB bootloader and since you already flashed the MK2 AP file you can get your phone running well again by flashing the MK2 modem: https://mega.co.nz/#!pwESna5I!YK7EKG37xXIG1ReB-Z-mfSMoXNkXQ9t2EdMK9ofgJKg
From there, there are still a number of options available to get to kitkat which I won't get into.
Click to expand...
Click to collapse
I will try this steps and let you know.thanks a lot.
It worked "muniz_ri". Thanks a lot for your help, I really appreciate it. :laugh::good:
karim8888 said:
It worked "muniz_ri". Thanks a lot for your help, I really appreciate it. :laugh::good:
Click to expand...
Click to collapse
Hey guys.
I lost al sounds on my phone now.Wifi is running , I thought the fix worked but the sound is out now. any suggestions???
Thank you.
jbrudda said:
I recently bit off more than I could chew with my S4 (I337). I had 4.4.2 KitKat on it and wanted to root it to add teathering. I decided thought there was no root for 4.4.2 so I thought I would try downgrading to 4.3 then root. This seemed best because I didn't like the way the SD card is handled in 4.4.2 and some of my apps (like ftp server) have stopped working.
When I got the phone back up from flashing with Odin it says it has version 4.3. My WiFi will not turn on. If I slide the switch to on it slides right back to off and the phone tells me that an operation was block (can't remember the full verbage. I have installed and attempted to install many things on my phone. I have used recovery mode / Odin3 and Kies (Kies doesn't allow much).
At this point I just would like to get my phone back to 4.4.2 with the WiFi working. Then I can restore my backup and be back to square one with a lesson learned.
I have an I337 that currently thinks it has version 4.3 on it. The baseband version is I337UCUFNC1 currently. The build number is JSS15J.I337UCUEMK2.
If anyone can help I would greatly appreciate it. I have read and tried many things over a two day period and finally decided to ask for help.
Click to expand...
Click to collapse
I told you not to drink and root.
jbrudda said:
Quite a few steps in those threads but I got it working again. I really appreciate all the help/advice given. Now to decide if I want to remove the safestrap screen on boot. Again Thanks.
Click to expand...
Click to collapse
excited to give this a try. rooted with the downgrade method a couple months ago but left with a non-wifi device. my only issue is that the thread says it's for I337UCUFNC1 and our devices are on jss15j.i337ucuemk2. will this fix still work? I've heard on other threads on the subject that the modem kernel doesn't match up with the flashed rom or build number or something.
bux
karim8888 said:
Hi guys,
I have the same problem as jbrudda.i wiped everything using Odin3_v3.09 and AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar . and now my wifi is not working. when i try to turn it on a security message pop up (the device has detected an application attempting to perform actions that are not permitted these actions have been blocked)and ask me to reboot, then it does a factory reset on its own. but the problem is still there no wifi. my baseband is diffrent than jbrudda's. mine is I337UCUAMDB. can someone plz help. thank you
Click to expand...
Click to collapse
Do you already fix it??? cause i have the same problem
Same question, different thread!
Not even an hour ago did I answer the same question in a different thread: How do I get WiFi working on my S4?
Well here you go.
My original answer: http://forum.xda-developers.com/gal...-4-4-2-nb1-t2850878/post54978150#post54978150
The problem is, in order to get WiFi working, you need to install the NB1 modules, but to do that, you need to install Safestrap. However, you can not install Safestrap because the app keeps closing on you. There is a simple fix to this, which I will explain later. For now, just read this WHOLE post BEFORE you do anything, and keep in mind that I am NOT held liable if you mess up your phone. Use this at your own risk.
1.) Root your phone
If you're already rooted with something like SuperSU or Superuser, skip this. If not, read ahead. Download and install the Towelroot APK file attached to this post, open it, and click 'make it ra1n'. If your phone didn't reboot, now you have root (they need to trademark that). Now, down below, I also included the APK for SuperSU. Download and install it. Now open it. When you open it, let it install the 'Normal' way, not via the 'TWRP/CWM' way. Also, when it asks you to disable KNOX, say yes, wait a couple of minutes (it will still be loading) and reboot your phone. Open up SuperSU again, click 'Yes' to disable KNOX again, and now you have a good base to start from.
2.) Install Safestrap AFTER fixing the error
The error your are getting is easily fixed. Go to the Play Store and install 'SELinux Mode Changer'. Open it, grant it root access, and change the mode to 'Permissive'. Now, open up Safestrap again (you mentioned you already installed it), and it shouldn't force close. Click 'Install', and if the 'Reboot to Recovery' option below is not grayed out after that then it worked.
3.) Download and install the NB1 modules
On your phone, download the included NB1 modules ZIP file I attached for you, and once that is done you need to reboot. After the Galaxy S4 logo, you'll see a screen that says 'SAFESTRAP: DISABLED' and there will be a little robot. TIP: To enter Safestrap, press the menu button (physical, hardware key) under 'Recovery' at that screen. To continue to Android, press the back key (again, physical) under the 'System' tab. For now, press the menu button under 'Recovery'. Now, click 'Install' which should be in red, click 'Add zips', and navigate to your Downloads folder. Now click on the NB1 modules ZIP you just downloaded. Swipe to install, and reboot. This time, hit the back key under 'System'.
All done!
Now, Android should (and will) boot up, and you'll have working WiFi! If, for some odd reason, you don't have WiFi- do NOT panic! Just search around for the MF3 modules and flash those! All is good, all is good. A lot of this guide was taken from my post about my personal method of SIM unlocking the AT&T Galaxy S4 without the dialer codes or an AT&T SIM. It was just modified a little to work for you.
Remember, hit thanks!
Click to expand...
Click to collapse
Those are my exact words. Also, the attached files (NB1 modules, SuperSU, Towelroot, etc.) can be found attached to my post in the link above. Have a good night, and best of luck! :good::good::good:
Had the Wifi Not Working - Fixed
muniz_ri said:
If you don't care about losing your MDB unlocked bootloader you can get to the latest kitkat firmware by flashing the NB1 full odin tar from here:
http://forum.xda-developers.com/showthread.php?t=2674223, then once flashing is complete go to settings/more/about phone/software update then take the ota update to NC1 which is the latest kitkat version for our phone.
But what I would do is keep your unlocked MDB bootloader and since you already flashed the MK2 AP file you can get your phone running well again by flashing the MK2 modem: https://mega.co.nz/#!pwESna5I!YK7EKG37xXIG1ReB-Z-mfSMoXNkXQ9t2EdMK9ofgJKg
From there, there are still a number of options available to get to kitkat which I won't get into.
Click to expand...
Click to collapse
I just flashed I337MK2StockModem.tar.md5 and now it works!! I'm on the MK2 and rooted with saferoot and safestrap recovery 3.72
iqcomputers said:
I just flashed I337MK2StockModem.tar.md5 and now it works!! I'm on the MK2 and rooted with saferoot and safestrap recovery 3.72
Click to expand...
Click to collapse
See the thread I started with a similar problem.
http://forum.xda-developers.com/galaxy-s4-att/help/rogers-samsung-s4-4-2-2-i337m-wifi-t3256535
Would I be able to use this fix?
I have galaxy s5 stuck in download screen. I have been through several "tutorials " on fixing, with no luck. I'm having a hard time finding original firmware for this model. Any help would be appreciated, I have a pic of the screen with info on it, but couldn't figure out how to post here.
Flash the original firmware?
Blackmonjr said:
I have galaxy s5 stuck in download screen. I have been through several "tutorials " on fixing, with no luck. I'm having a hard time finding original firmware for this model. Any help would be appreciated, I have a pic of the screen with info on it, but couldn't figure out how to post here.
Click to expand...
Click to collapse
Here you can download the latest firmware update for that model:
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900R7/ACG/download/G900R7WWU3CPL1/120072/
Seems like the SM-G900R7 is a carrier specific device only. I have no experience with those. But I suspect they flash with odin just like the other models.
Did a bit of searching cause I was interested. If you (by chance) want root, there is an auto-root created by chainfire.
There is also a current official lineageOS build (LOS 14.1 = Android N) for that variant by haggertk (was merged into klte build months ago).
So looking good for you I'd say if you get it running.
I've tried what I think is flashing the original firmware. Tried a different autoroot and nothing. I think I'm doing things right, but always manage to have some kind of small issue, e.g. Connecting phone to Odin, or flash not taking. If another process for flashing original firmware is out there that doesn't use Odin, it may work. Thanks for the responses.
Blackmonjr said:
I've tried what I think is flashing the original firmware. Tried a different autoroot and nothing. I think I'm doing things right, but always manage to have some kind of small issue, e.g. Connecting phone to Odin, or flash not taking. If another process for flashing original firmware is out there that doesn't use Odin, it may work. Thanks for the responses.
Click to expand...
Click to collapse
So what's the problem exactly? We need more info on what you want to accomplish and what you did (step by step) and what result you got.
Does Odin pick up your device? What file you tried to install (Link please!). What Odin log messages do you get? etc. etc.
Be as specific as possible. And go step by step! Try getting stock firmware to run first... no root, no custom recovery, no nothing.
Remove the battery for about a minute, boot directly to download mode via 3-button-combo, then try connecting to ODIN.