Flash back to stock from CyanogenMod installer to activate on Sprint - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

I have a sprint gs4 that I used CyanogenMod installer to flash it. I need to activate it on Sprint, and it won't update. After calling customer service, I was instructed to dial ##72786# to get it to activate, but it won't work because the ## features don't work on CyanogenMod. I think I need to flash back to stock, and get it activated, then I can reflash CyanogenMod.
When trying to flash back to stock, I always get an error in Odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also on my screen after it fails, it says:
ODIN MODE:
PRODUCT NAME: SPH-L720
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB:0X30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
***then in red after flash fails:
start [224, 1440]
sw rev. check fail : fused : 4, binary : 1
The phone works fine with Cyanogenmod installed, but I can't activate to actually use it. I need to figure out how to activate it...any help will help! Thanks and Happy Thanksgiving!
-Rob

rob0762 said:
I have a sprint gs4 that I used CyanogenMod installer to flash it. I need to activate it on Sprint, and it won't update. After calling customer service, I was instructed to dial ##72786# to get it to activate, but it won't work because the ## features don't work on CyanogenMod. I think I need to flash back to stock, and get it activated, then I can reflash CyanogenMod.
When trying to flash back to stock, I always get an error in Odin:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:6)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
aboot.mbn
NAND Write Start!!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Also on my screen after it fails, it says:
ODIN MODE:
PRODUCT NAME: SPH-L720
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB:0X30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
***then in red after flash fails:
start [224, 1440]
sw rev. check fail : fused : 4, binary : 1
The phone works fine with Cyanogenmod installed, but I can't activate to actually use it. I need to figure out how to activate it...any help will help! Thanks and Happy Thanksgiving!
I noticed that you said that the Knox Warranty read 0x1. That right there is telling me that you are on the latest MJA. The reason its failing is because your trying to downgrade to MDC which will be impossible because Knox wont let you.. What you have to do is look for the stock MJA tar file, flash that and you should be back in business...
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget,8SMS(Stock Messaging,KitKat)
Click to expand...
Click to collapse

BIGSAMDA1ST said:
rob0762 said:
I have a sprint gs4 that I used CyanogenMod installer to flash it. I need to activate it on Sprint, and it won't update. After calling customer service, I was instructed to dial ##72786# to get it to activate, but it won't work because the ## features don't work on CyanogenMod. I think I need to flash back to stock, and get it activated, then I can reflash CyanogenMod.
When trying to flash back to stock, I always get an error in Odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also on my screen after it fails, it says:
ODIN MODE:
PRODUCT NAME: SPH-L720
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB:0X30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
***then in red after flash fails:
start [224, 1440]
sw rev. check fail : fused : 4, binary : 1
The phone works fine with Cyanogenmod installed, but I can't activate to actually use it. I need to figure out how to activate it...any help will help! Thanks and Happy Thanksgiving!
I noticed that you did that you said that the Knox Warranty read 0x1. That right there is telling me that you are on the latest MJA. The reason its failing is because your trying to downgrade to MDC which will be impossible because Knox wont let you.. What you have to do is look for the stock MJA tar file, flash that and you should be back in business...
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget,8SMS(Stock Messaging,KitKat)
Click to expand...
Click to collapse
i am on mja also tried to install stock mja and im bootlooped but mine says knox 0x0 and on binary it says official samsung but on system it says custom already odined mja twice and still doesnt want to boot up all the way
Click to expand...
Click to collapse

@steviee7 Is the phone booting up to the yellow sprint screen? If so all you have to do is go into recovery and just factory reset.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget,8SMS(Stock Messaging,KitKat)

BIGSAMDA1ST said:
@steviee7 Is the phone booting up to the yellow sprint screen? If so all you have to do is go into recovery and just factory reset.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget,8SMS(Stock Messaging,KitKat)
Click to expand...
Click to collapse
it does get stuck in the yellow boot screen but im not able to get into recovery only able to get into download mode.... when i try to get into recovery it says booting recovery then it just turns on regular

Why not grab the MJA Stock TW Flash, activate then go back to your ROM of choice
If that doesn't work you might want to try here too.

steviee7 said:
it does get stuck in the yellow boot screen but im not able to get into recovery only able to get into download mode.... when i try to get into recovery it says booting recovery then it just turns on regular
Click to expand...
Click to collapse
My wifes phone was in a similar situation. What I did was pull the battery, put it back in while the phone was powering back on, I went straight to recovery then did the factory reset.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget,8SMS(Stock Messaging,KitKat)

leaderbuilder said:
Why not grab the MJA Stock TW Flash, activate then go back to your ROM of choice
If that doesn't work you might want to try here too.
Click to expand...
Click to collapse
kept trying to get into recovery and it finally worked thank you so much i was able to do a reset and it finally booted all the way

leaderbuilder said:
Why not grab the MJA Stock TW Flash, activate then go back to your ROM of choice
If that doesn't work you might want to try here too.
Click to expand...
Click to collapse
Leaderbuilder,
I tried to flash the MJA stock .zip in recovery, it processed and rebooted, but it was still cyanogenmod, and the ## functionality still doesn't work and I can't activate on the Sprint network...any ideas?
Thanks!
Rob

rob0762 said:
Leaderbuilder,
I tried to flash the MJA stock .zip in recovery, it processed and rebooted, but it was still cyanogenmod, and the ## functionality still doesn't work and I can't activate on the Sprint network...any ideas?
Thanks!
Rob
Click to expand...
Click to collapse
Seems you're not getting a real/true wipe.
Make sure you grab Philz or latest TWRP 2.6.3 recovery and put it on you SD card so you can flash either of those for wiping and installing - remember you can install a recovery and then reboot the recovery to then be in your 'newly' flahsed one and to clear and nasties too.
Boot to recovery and wipe your system completely - cache, dalvik, system, data, internal SD etc.
For TWRP:
Make sure to select the "Use rm -rf instead of formatting"? (be sure to select the Home symbol at the bottom after it's checked.) Then...
Select Wipe > Advanced Wipe
Select Dalvik, System, Data Cache, and Internal Storage (I do this step 3 times)
Swipe
Format Data (I do this step 3 times)
Reboot into recovery mode
Select Install Zip
Locate your Rom and Swipe to install
For Philz:
Go to recovery:
Go into mounts & storage ---> format: cache, data, system & internal (sd card)... do this 2-3 times
Go to "install zip"
Wipe cache
Now "factory wipe to install new ROM" (let it run...)
DO NOT FLASH ROM YET!!!
Reboot recovery
Now flash ROM and enjoy!

leaderbuilder said:
Seems you're not getting a real/true wipe.
Make sure you grab Philz or latest TWRP 2.6.3 recovery and put it on you SD card so you can flash either of those for wiping and installing - remember you can install a recovery and then reboot the recovery to then be in your 'newly' flahsed one and to clear and nasties too.
Boot to recovery and wipe your system completely - cache, dalvik, system, data, internal SD etc.
For TWRP:
Make sure to select the "Use rm -rf instead of formatting"? (be sure to select the Home symbol at the bottom after it's checked.) Then...
Select Wipe > Advanced Wipe
Select Dalvik, System, Data Cache, and Internal Storage (I do this step 3 times)
Swipe
Format Data (I do this step 3 times)
Reboot into recovery mode
Select Install Zip
Locate your Rom and Swipe to install
For Philz:
Go to recovery:
Go into mounts & storage ---> format: cache, data, system & internal (sd card)... do this 2-3 times
Go to "install zip"
Wipe cache
Now "factory wipe to install new ROM" (let it run...)
DO NOT FLASH ROM YET!!!
Reboot recovery
Now flash ROM and enjoy!
Click to expand...
Click to collapse
LeaderBuilder,
Thanks for the response...no dice on installing these new installers. I went into recovery and tried to "update form external sd card" both Philz or TWRP, but while installing, it says it fails "signature verification fails" and then it restarts. Not sure what is causing this error, but this is probably what happened when I tried to flash the MJA stock rom.
Any support would be excellent! thanks!
-rob

rob0762 said:
LeaderBuilder,
Thanks for the response...no dice on installing these new installers. I went into recovery and tried to "update form external sd card" both Philz or TWRP, but while installing, it says it fails "signature verification fails" and then it restarts. Not sure what is causing this error, but this is probably what happened when I tried to flash the MJA stock rom.
Any support would be excellent! thanks!
-rob
Click to expand...
Click to collapse
Right before you swipe the bar down below to start the installation, look right above that and unchecked the signature verification box.

Related

[Q] [HELP] - Undoing MH8 update

So... Like a fool, having successfully rooted my phone a couple of days ago on the I9505XXUBMGA firmware, I saw this appear in Kies when I plugged my phone into Kies this morning. I thought (yeah you know where this is heading) "Oooh shiny new update, must download".
So although I had root I didn't think it would be a problem I'd just re-root afterwards. And hey if it didn't work I'd just downgrade the firmware and repeat the original process.
Trouble is I now have a message saying "SuperSU has been forced to stop for an unauthorized attempt to access system in your device. It may be solved by the policy update service. It may be safe to delete an application obtained from an unauthorized route. Check now?". I then have the option to not show for 30 days and then Cancel, Update or OK. Trouble is now when I attempt to revert the firmware back to an earlier version.
So now when I go into Download mode I see:
Code:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
If I try and Odin a new (stock) firmware on I get a write error from Odin and on the I9505 I get the following below the above text:
Code:
START [224, 1440]
SW REV. CHECK FAIL : fused: 2, Binary : 1
Odin shows:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
So, kind of stuck now. If the phone tries to restart I get the message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". For a while I couldn't get the phone to boot, and Kies doesn't see the phone, but oddly re-partitioning via Odin using the PIT file means the phone will boot. From there I still get the SuperSU message but can switch it off and get into recovery mode, does that mean there is a chance I can re-flash things via adb / fastboot?
Yep I'm an idiot for trying and being the Guinea pig, but as I don't know how to proceed if anyone wants to help out and see if we can get it back and un "Knoxed" (which I think might be the issue) I'm more than happy to help.
Limitations currently are that I am running Windows XP 32-bit via Parallels virtual machine. The unbricking steps seem to indicate needing a 64-bit machine? I could probably do that but would have to get hold of and install 64-bit Windows 7 as a VM.
In terms of Android hacking I'm a noob, but can follow instructions, and am comfortable with a Unix/Linux command line if that's any help to anyone who wants to take pity on me...
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Boolean = True said:
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Click to expand...
Click to collapse
So, assuming you are stuck at the "there was a problem stage" you need to turn off the phone and get it into download mode (hold volume down, home + power - I guess you know this but just in case). I found this a bit fiddly I think because the phone is auto-rebooting, so try pressing power off and just holding the volume down and home buttons.
Then in Odin I used the PIT file listed in this thread. In the 'Re-partition' section and the boxes for Auto Reboot, Re-Partition, and F. Reset Time were all checked. I left all the other boxes empty (including the Files section). Click start and then after a while the phone reboots. It take a minute or two but if you see the Samsung logo it should boot.
Hope that helps... now to find a way around the MH1 firmware... oh and glad it wasn't just me that was daft enough to go and try it.
No, not just you mate. I had a hell of a time last night. Flash pre-rooted MGG firmware via odin, which bootlooped. I couldn't flash MGA firmware again.
So I flashed Stock MGG which booted but the security measures implemented have stopped me from changing my font using ifont.
I have now flashed MH8 over the top and it's working better than MGG, but still can't use some apps due to the new security measures.
I was able to flash Omega V10 from TWRP and it booted fine, but no wifi and I'm unable to flash LTE modem to correct it.
Looks like I'm stuck unrooted on MH8 for the time being.
There are some instructions on this thread on how to root this firmware, they're a bit lengthy tho.
http://forum.xda-developers.com/showthread.php?p=45283966
Sent from my GT-I9505 using Tapatalk 4
Bugger.
To add insult to injury it appears that WiFi is now no longer working either.
I'll look into the post you linked too, but I can't see how it will update that all, i.e. it says to use Odin which currently fails for me.
Odin doesn't fail for me when flashing kernels or recoveries, just when I try and flash full firmware earlier than MGG which includes the bootloader.
Flash full MH8 firmware from samfirmware, I have no issues except for the security problems.
Sent from my GT-I9505 using Tapatalk 4
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
jd1639 said:
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
Click to expand...
Click to collapse
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
shrubz said:
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I hadn't realised that flashing the same or newer would work (it does). But WiFi is still borked... any ideas?
Tiny amount of progress, more out of hope I tried to flash a pre-rooted ROM - obviously this didn't work, but when I reflashed MH8 again I noticed the device made the start up sound (which it hadn't been) and WiFi is now working.
As a bonus if I go into Device Status it is now showing as Official, which is nice!
I think I'll leave it there for now, but will keep an eye out for progress, hopefully the bootloader will be "fixed" in due course.
Chainfire is working on a fix for CF-Root. So hopefully all will be good soon.
Sent from my GT-I9505 using Tapatalk 4

Fixed - I9505 - kernel is not seandroid enforcing - Reboot & Hangs ! Easy !

S4 I9505
Problem:
Start up screen top left corner shows:
kernel is not seandroid enforcing
Hangs up or Reboots.
I updated my S4 to Version: I9505XXUEMKE
Then I used Odin to Flash a Root with Stock recovery & SU, something went WRONG!
Knox is now 0x1, which should not have happened, but what can I say.
BaM, I got the Reboots & Hang ups.
But, I still could get into Recovery & Download Mode!
SO HERE IS THE FIX:
1. Download, Odin 3 - THx 2 - daerragh
--- I used Ver.: Odin 3.07
2. Download, http://www.sammobile.com/firmwares/2/
--- Register
--- And download your Firmware, if you know which you had before it crashed choose that one otherwise Upgrade to latest.
--- For me it was the latest version - I9505XXUEMKE ---- THx 2 -- Repulsa for the tip.
3. Start Odin 3.07 --- [Should it "FAIL" Read note at the Bottom #6].
--- Make sure - Auto Reboot & F. Reset Time are checked - Nothing else.
--- Click on PDA choose your Firmware file in my case "I9505XXUEMKE"
--- this can take a minute or two, WAIT, the PDA will check mark itself.
4. To start Turn off your phone completely ! Now hold following buttons to get into Download Mode,
--- Volume Down
--- Home
--- and last Power
--- S4 will enter into DL Mode
Seeing you have already tried to root you phone, you should have you Samsung USB drivers.
5. Press Start
--- This will take time, after it Reboot itself,
--- remove the USB Cabel & wait
--- at least 5 minutes don't remember how long, I came back after 5 Minutes and it was done,
---------- so then if everything went well for you, have fun :good: .
6. FAIL
--- Should it Fail while uploading to your phone,
--- A. Remove Battery
--- B. Remove USB cabel
--- C. Restart.
--- Should it Fail again (which happend to me), then Do A. B. C. again.
--- and this time Touch your screen about every minute.
I Know that sounds weird, but it worked for me maybe something to do with "Stand by? no clue".
If this has help you in anyway please hit that :good: Thanks Bottun
I AM NOT RESPONSIBLE for anything happening to your phone as a result of you flashing this Rom.
[Help Please] TMO-S4- Kernel is not seandroid enforcing
Hello,
Let me start off by saying, I'm a complete newbie when it comes to rooting (Infact - It took me a few days to even convince myself to do this) and I did look around for several guilds on how to remove this error (Downloaded Odin - Got Stock TAR.MD5) But I still get this error on my phone when I start the phone, it wouldn't be much of a probelm, except it hangs for a while and then restarts.) It also gets stuck for a long time at the T-Mobile load screen. The Wifi Wont turn on their... Please Help.
Galaxy S4: SGH-M919
T-Mobile...
I'm not an expert in Android OS but I think this is not an error. It is more of a notification that the STOCK KERNEL has been change to a CUSTOM one.
eclpsues said:
I'm not an expert in Android OS but I think this is not an error. It is more of a notification that the STOCK KERNEL has been change to a CUSTOM one.
Click to expand...
Click to collapse
You are right :highfive:
Hi guys
A friend and I tried to update my rooted Samsung S4 i9505 to the official kitkat version. Had the unofficial one before. Unfortunatly we didn't turn on the usb debugging and there wasn't enough space on my memory card. After removing the data from the sd card it still didn't work (usb debuging?). My friend then tried to install a custom rom of some sort (I'm the noob here. He has some skills). No whenever I try to start my cell up the message KERNAL IS NOT SEANDROID ENFORCING pops up in the top left corner. Can I turn on the usb debugging from the pc? What should I do?
Thanks
illias9 said:
Hi guys
A friend and I tried to update my rooted Samsung S4 i9505 to the official kitkat version. Had the unofficial one before. Unfortunatly we didn't turn on the usb debugging and there wasn't enough space on my memory card. After removing the data from the sd card it still didn't work (usb debuging?). My friend then tried to install a custom rom of some sort (I'm the noob here. He has some skills). No whenever I try to start my cell up the message KERNAL IS NOT SEANDROID ENFORCING pops up in the top left corner. Can I turn on the usb debugging from the pc? What should I do?
Thanks
Click to expand...
Click to collapse
I tried to install the Gummy Rom but I got the same problem. It gets stuck in the rebooting or something. It wont pass the samsung start screen. What should I do?
Tried all of the above and no go.
Hi i have CM on my Australia XSA Samsung 19505 and i am trying to get it back to stock though when i try to flash it in Odin it fails all the time i cant get into recovery though i am able to access download mode.
I am using Odin 3.09 with the correct stock rom for my device and when i run it i get this error message
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505XSAEMK3_I9505XXUEMK9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my device is error message
start [224,1440]
sw rev check fail fused 4 binary 3.
I also have the "kernel is not seandroid enforcing" message.
When i restart my device i get an error message "Firmware upgrade encountered an issue please select recovery mode in kies and try again"
I have tried to use Kies both versions and it doesn't work, The only way to get it to work is flash CWM which allows me back into my device.
Any ideas on how to get back to stock Thanks?
Natza09 said:
Hi i have CM on my Australia XSA Samsung 19505 and i am trying to get it back to stock though when i try to flash it in Odin it fails all the time i cant get into recovery though i am able to access download mode.
I am using Odin 3.09 with the correct stock rom for my device and when i run it i get this error message
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505XSAEMK3_I9505XXUEMK9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my device is error message
start [224,1440]
sw rev check fail fused 4 binary 3.
I also have the "kernel is not seandroid enforcing" message.
When i restart my device i get an error message "Firmware upgrade encountered an issue please select recovery mode in kies and try again"
I have tried to use Kies both versions and it doesn't work, The only way to get it to work is flash CWM which allows me back into my device.
Any ideas on how to get back to stock Thanks?
Click to expand...
Click to collapse
Use a different usb port. Always use the ports on the back of your pc not the ones on the front.
Lennyz1988 said:
Use a different usb port. Always use the ports on the back of your pc not the ones on the front.
Click to expand...
Click to collapse
Thanks Lennyz for the reply, I tried the back usb 2.0 and 3.0 and both failed with the same error message as originally posted. Can i just restore the kernel some how and will that fix the issue?
Natza09 said:
Thanks Lennyz for the reply, I tried the back usb 2.0 and 3.0 and both failed with the same error message as originally posted. Can i just restore the kernel some how and will that fix the issue?
Click to expand...
Click to collapse
I think I know what you did. You try to flash an older stock firmware on to your device. Pick a newer firmware because downgrading is not possible.
Lennyz1988 said:
I think I know what you did. You try to flash an older stock firmware on to your device. Pick a newer firmware because downgrading is not possible.
Click to expand...
Click to collapse
I have tried to flash several Roms that are 4.4 and that are compatible with my device using clock work mod and it doesn't work as i keep getting a Status 7 error which i have found a possible fix for here in the forum i will attempt to resolve and report back.
---------- Post added at 11:40 PM ---------- Previous post was at 11:05 PM ----------
Natza09 said:
I have tried to flash several Roms that are 4.4 and that are compatible with my device using clock work mod and it doesn't work as i keep getting a Status 7 error which i have found a possible fix for here in the forum i will attempt to resolve and report back.
Click to expand...
Click to collapse
Ok so i put TWTP back on and i was able to install Goldeneye Rom 4.4.2, Which is working great. However when i reboot im still getting the Kernel is not seandroid enforcing message in red. As i can not restore to stock Rom as Australia XSA 4.4 isn't out yet is there any other way to get rid of this message. Thanks again.
did anyone tried this ??
Natza09 said:
Hi i have CM on my Australia XSA Samsung 19505 and i am trying to get it back to stock though when i try to flash it in Odin it fails all the time i cant get into recovery though i am able to access download mode.
I am using Odin 3.09 with the correct stock rom for my device and when i run it i get this error message
I have tried to use Kies both versions and it doesn't work, The only way to get it to work is flash CWM which allows me back into my device.
Any ideas on how to get back to stock Thanks?
Click to expand...
Click to collapse
iuts coz you are trying to downgrade the aboot file which is associated with know security check .. u have to flash the same or upgrade
franny23dmt said:
iuts coz you are trying to downgrade the aboot file which is associated with know security check .. u have to flash the same or upgrade
Click to expand...
Click to collapse
Yeah its all sorted now as version 4.4.2 has been officially released as stock on my Samsung S4, So back to "factory" now and no more message. Off to ebay it goes and Hello HTC One M8 .
Hi,
I'll Install WizCyan custom Rom on My GT-I9505 by TWRP mode. Its not a Error its a Premission That are allow when we use other roms.
●Press Volume Up and Volume Down Key at same
time and Hold it. This methode is use to Force Start your Rom

[Q] How to Root on G900FXXU1BNL7 5.0?

Hello I was trying to root my G900F that is currently running Lollipop BNL7 with CF-Auto-Root-klte-kltexx-smg900f and Odin 3.09 after enabling USB debug but Failed at the end of the process. Had to restore stock G900FXXU1BNL7 to get phone back working.
Try it two times always fails at the end.
Any other method or have to wait for updated version of CF-Auto?
Does G900FXXU1BNL7 is rootable?
Is there a way to downgrade to 4.4 safely as I try already and end up in nightmare and dont have EFS backup that is why I want to root first.?
Code:
<OSM> Please wait..
<OSM> CF-Auto-Root-klte-kltexx-smg900f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
egejo said:
Hello I was trying to root my G900F that is currently running Lollipop BNL7
Click to expand...
Click to collapse
You haven't done anything serious. Don't worry. You can only use SuperSU 2.38 or above versions. No other method works for TouchWiz Lollipop so far.
Reactivation lock
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I think you already enable (Reactivation lock) from setting --> security
Just uncheck the option and i hope it will work fine
Thanks for the advice but did not work.
I have try these way so to first load a custom recovery via odin to root and install SUperSu tested with both Philz and TWRP but failed also on Odin at the end of the process of each of them.
Had to put stock BNL7 again to recover the phone from "firmware upgrade issue" screen
Does BNL7 has some locked bootloader security or so I cant mod anything neither root it now...
lingowistico said:
You haven't done anything serious. Don't worry. You can only use SuperSU 2.38 or above versions. No other method works for TouchWiz Lollipop so far.
Click to expand...
Click to collapse
egejo said:
Thanks for the advice but did not work.
I have try these way so to first load a custom recovery via odin to root and install SUperSu tested with both Philz and TWRP but failed also on Odin at the end of the process of each of them.
Had to put stock BNL7 again to recover the phone from "firmware upgrade issue" screen
Does BNL7 has some locked bootloader security or so I cant mod anything neither root it now...
Click to expand...
Click to collapse
Yes some people say that it only works with Fusion TWRP 2.8.2.0. I don't know if it's true because I already flashed it before flashing SuperSU 2.38 beta And of course it worked.
i cant install recovery mode on bnl7 . Tried it whole day and all i get is stock recovery mode.
Help ?
lingowistico said:
Yes some people say that it only works with Fusion TWRP 2.8.2.0. I don't know if it's true because I already flashed it before flashing SuperSU 2.38 beta And of course it worked.
Click to expand...
Click to collapse
Thanks, sorry to be such a noob but downloaded the Fusion TWRP you post got the zip... but how to install if unzipped there is no odin Tar or such flashable file...neither like and apk, sorry lost in here?
Lastly to let you know that now I'm in Stock G900FXXU1ANCE, dowgraded from BLN7 to BLN2, then ANJ1 and then ANCE. On all of them I have been trying to root or put a custom recovery, used CF-Auto-Root-klte-kltexx-smg900f, openrecovery-twrp-2.8.1.0-klte or philz_touch_6.57.8-klte with same results always Failing Odin at the end of process... The thing I notice is that always it shown on the dowload mode screen
"QUALCOMM SECURE BOOT: ENABLED (CSB)"
Even after downgrade, could these be the issue?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.57.8-klte.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Made a little progress here,
As I'm now on G900FXXU1ANCE I used towelroot and finally gain root access it Work installed SuperSu from Gplay and then finally made an EFS backup with samsung tool...
But still dont know why it does not work all other methods and ODIN rooting and cant have a custom recovery neither...But for now I feal a little safer having my EFS on Dropbox to be sure....
Will keep playing trying to get a working custom recovery so to flash customs roms later...But looks like I will have to wait for updates now...
egejo said:
Made a little progress here,
As I'm now on G900FXXU1ANCE I used towelroot and finally gain root access it Work installed SuperSu from Gplay and then finally made an EFS backup with samsung tool...
But still dont know why it does not work all other methods and ODIN rooting and cant have a custom recovery neither...But for now I feal a little safer having my EFS on Dropbox to be sure....
Will keep playing trying to get a working custom recovery so to flash customs roms later...But looks like I will have to wait for updates now...
Click to expand...
Click to collapse
had the same problem as you use this twrp it worked perfect in the end make you scroll down to where it says THE GOODS TWRP ODIN its near the bottom of first post in this link http://forum.xda-developers.com/showthread.php?t=2697762
pnr2020 said:
had the same problem as you use this twrp it worked perfect in the end make you scroll down to where it says THE GOODS TWRP ODIN its near the bottom of first post in this link http://forum.xda-developers.com/showthread.php?t=2697762
Click to expand...
Click to collapse
Thanks but tested an did not work Odin Fails flashing it.
I can only flash stock roms and root on those old enough for towelroot...
I'm starting to think these brand new S5 SM-G900F is starting to come with locked bootloader....
Is there a way to verify these...?
egejo said:
Thanks, sorry to be such a noob but downloaded the Fusion TWRP you post got the zip... but how to install if unzipped there is no odin Tar or such flashable file...neither like and apk, sorry lost in here?
Click to expand...
Click to collapse
This is the story that I heard and followed, after which I got root on bln2:
You can only get root on Samsung Lollipop with SuperSU v2.38 and above, but the only 100% sure way to flash SuperSU v2.38+ is by flashing it in Fusion TWRP 2.8.2.0.
So you do it like this:
1 Flash rom in odin
2 Flash custom recovery in Odin (CWM/TWRP doesn't matter)
3 Now boot custom recovery and flash the Fusion TWRP 2.8.2.0 zip file
4 Reboot recovery
5 Flash SuperSU v2.38+ zip
6 Enjoy root
lingowistico said:
This is the story that I heard and followed, after which I got root on bln2:
You can only get root on Samsung Lollipop with SuperSU v2.38 and above, but the only 100% sure way to flash SuperSU v2.38+ is by flashing it in Fusion TWRP 2.8.2.0.
So you do it like this:
1 Flash rom in odin
2 Flash custom recovery in Odin (CWM/TWRP doesn't matter)
3 Now boot custom recovery and flash the Fusion TWRP 2.8.2.0 zip file
4 Reboot recovery
5 Flash SuperSU v2.38+ zip
6 Enjoy root
Click to expand...
Click to collapse
I cant flash any custom recovery at all it always fails and softbricks the phone... Looks like these G900F is now bootloader Locked...
If so samsung is now selling them from factory locked not just ATT versions...
egejo said:
Thanks but tested an did not work Odin Fails flashing it.
I can only flash stock roms and root on those old enough for towelroot...
I'm starting to think these brand new S5 SM-G900F is starting to come with locked bootloader....
Is there a way to verify these...?
Click to expand...
Click to collapse
dont know to be honest mine only 2 weeks old from uk was on BTU but now on polish version
egejo said:
Looks like these G900F is now bootloader Locked...
Click to expand...
Click to collapse
I don't think so, everything works fine for me..
i also cant install recovery but i dont get soft bricks , just normal stock recovery mode all over.
"qualcomm secure boot: Enabled (csb)
hello everyone
if you got error in odin when flash any custom recovery just deactivate reactivation lock from setting>security.

[Q] -CM- What to update to

Hi guys, I have a Samsung Galaxy S4 from Canada, specifically Rogers. The phone is currently on the CM11 Nightly ROM. (I can check specifically which nightly, my phone is just backing up at the moment so I can't see!)
I have this problem, which is, when the phone automatically locks or I myself lock it, the radio signal completely drops. Sometimes the signal will come back, but to get it back for sure is to turn the phone on airplane mode then off again. It is annoying because when the phone is locked for a while, it will receive signal at some point. During that time I'll get a call and it'll ring but once the screen turns on the signal will drop, also dropping the call. I have a slight understanding that it could be a problem with the phone's radio firmware?
Now that you guys have an understanding about my problem, this is what I am hoping to accomplish. I want to update the phones ROM, as it is probably old, along with the proper fix to the phone's radio firmware. How do i go about doing this? The kind of ROM that I want is something in between stable version and nightly (not nightly as I think nightly was the one that caused my radio problem), I think that's SNAPSHOT M12? Please correct me if I am wrong. I would rather not lose any of my data but if I have to then I will but please do guide me because I am scared to lose any of my data.
Thank you guys for reading my long post, I hope my English and grammar is fine! I look forward to hearing from you guys!
The current version of Cyanogenmod is 12.1 (Android 5.1.1). The two release channels for 12.1 are nightlies and snapshots. As of yet there has been no CM12.1 snapshot I'm aware of, meaning all CM12.1 ROMs are nightlies.
You haven't said what version of the stock ROM you had before moving to CM11, but if the radio is too old, you'll want to update it. You'll need Odin and either the modem file, or a complete ROM, which you can download from here. If you choose to install the stock ROM, be aware that you will have to root your device again, using CF-Autoroot. Flashing the stock ROM or modem won't wipe your data unless you tell Odin to partition the S4, so you don't want to do that. What you do want to do before you attempt to do anything is make a nandroid backup as well as move any important files off the internal storage. While you won't need to wipe the S4 prior to installing the new stock ROM or the modem, you will need to do so when installing the new version of Cyanogenmod.
P. S. In the future, you want to direct your questions to the AT&T Galaxy S4 forums as this is the International S4 forum, which doesn't cover North American S4 devices. Your question however is general enough that we should still be able to help you.
Thanks for the reply!
Strephon Alkhalikoi said:
You haven't said what version of the stock ROM you had before moving to CM11
Click to expand...
Click to collapse
I don't know how to answer this, It's been quite a long time since I moved to CM11. Basically what I did was, when I bought the phone I went home and installed CM11 on it, haha.
Strephon Alkhalikoi said:
You'll need Odin and either the modem file, or a complete ROM, which you can download from here. If you choose to install the stock ROM, be aware that you will have to root your device again, using CF-Autoroot. Flashing the stock ROM or modem won't wipe your data unless you tell Odin to partition the S4, so you don't want to do that. What you do want to do before you attempt to do anything is make a nandroid backup as well as move any important files off the internal storage. While you won't need to wipe the S4 prior to installing the new stock ROM or the modem, you will need to do so when installing the new version of Cyanogenmod.
Click to expand...
Click to collapse
I am quite confused, sorry. What I'm doing right now is I'm downloading the newest radio firmware from the link you have given me. After that I'm going to follow the instructions of:
Extract (unzip) the firmware file
Download Odin v3.10.6
Extract Odin ZIP file
Open Odin v.3.10.6
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
That will fix my radio problems?
Now to update my ROM. This is where I am mostly confused. In your opinion, should I stick with CM11 Nightly? Can I somehow go from nightly to a more stable version like cm11 snapshot m12? Should I update to CM12? Will my phone keep up with the CM12 ROM?
Strephon Alkhalikoi said:
P. S. In the future, you want to direct your questions to the AT&T Galaxy S4 forums as this is the International S4 forum, which doesn't cover North American S4 devices. Your question however is general enough that we should still be able to help you.
Click to expand...
Click to collapse
Sorry I will keep that in mind! Mind you, I carefully chose this and looked at all my other options. I didn't see the AT&T forum to fit because AT&T is in the United States and my carrier is in Canada, I just didn't want to have problems with anything else
Guys, I think i screwed up.... So when i downloaded that firmware from Sammobile. I flashed it with ODIN and made sure re-partition was not checked. Everything looked fine and when my phone rebooted (its still rebooting at the moment) the welcome screen was the default "samsung" splash screen, not the Cyanogen Mod . I thought this method was only going to flash the phone's modem, not the ROM too
EDIT:
No....my worst nightmare came true .........NO!!!!
So my phone finished rebooting and its just a black screen. All I can see is the status bar at the top right that displays the WiFi signal and the Phone's network signal and the battery. Okay so I figured something out. When the phone is locked and I press the Home button, Battery Doctor's charging wallscreen shows up, meaning my device wasn't wiped ? When I tried to unlock from Battery Doctor's charging screen, it would just show the black screen with just the status bar .... PLEASE HELP ME !!!
It flashes a complete ROM, which is part of the reason I mentioned making a backup. Now you'll need to root your S4 again, as I mentioned, install a custom recovery, and then you can install Cyanogenmod (12.1 recommended). By flashing the complete ROM it also ensures you have a clean slate from which to move forward. Now all the firmware pieces "match" and you avoid any odd effects by having a mismatched bootloader and baseband.
Strephon Alkhalikoi said:
It flashes a complete ROM, which is part of the reason I mentioned making a backup. Now you'll need to root your S4 again, as I mentioned, install a custom recovery, and then you can install Cyanogenmod (12.1 recommended). By flashing the complete ROM it also ensures you have a clean slate from which to move forward. Now all the firmware pieces "match" and you avoid any odd effects by having a mismatched bootloader and baseband.
Click to expand...
Click to collapse
D'awww Well I guess a clean slate isn't so bad. I backed up my text messsages and my photo's should be backed up onto the google drive anyways. I don't know if you saw my edited post but the UI is not loading. Its just showing the status bar at the top right (signal, wifi signal, battery).
Thanks.
If you're going to install CM12.1 I wouldn't worry about Touchwiz not starting. Just go ahead and prep the phone for Cyanogenmod, as the most important parts - baseband and bootloader - are apparently working properly.
EDIT: ROM installs don't wipe data when done through Odin unless you tell Odin to partition the device. Thus you'd need a factory reset to ensure Touchwiz works. But where you're going to put Cyanogenmod on, don't worry about Touchwiz.
Strephon Alkhalikoi said:
If you're going to install CM12.1 I wouldn't worry about Touchwiz not starting. Just go ahead and prep the phone for Cyanogenmod, as the most important parts - baseband and bootloader - are apparently working properly.
Click to expand...
Click to collapse
The problem is, I can't. There's nothing there on the phone. Its just a black screen. Unless, thats what you meant.
I tried searching for a CM 12.1 Canadian version and I found this thread. http://forum.cyanogenmod.org/topic/104233-jfltesgh-i337m/
apparently theres no canadian version of the CM 12.1
what should I do ?
Use the Optimized CM12.1 here in I9505 Original Android Development. It's supposed to work with all Qualcomm S4s except the Value Edition S4.
Oh, and you don't need CF-Autoroot. Simply install the recovery using Odin, then install Cyanogenmod. Wipe data and cache, then reboot. Everything should be back to normal about ten minutes after rebooting, as the ART compiler compiles the apps.
Strephon Alkhalikoi said:
Use the Optimized CM12.1 here in I9505 Original Android Development. It's supposed to work with all Qualcomm S4s except the Value Edition S4.
Oh, and you don't need CF-Autoroot. Simply install the recovery using Odin, then install Cyanogenmod. Wipe data and cache, then reboot. Everything should be back to normal about ten minutes after rebooting, as the ART compiler compiles the apps.
Click to expand...
Click to collapse
Thanks for the replies! I'm sorry if im asking for too much but could you please confirm that this is the right one? link
So, I don't need to root? how can i verify that my phone is still rooted? If my phone is still rooted, I download Canadian Galaxy S4 SGH-i337M (Bell, Rogers, Telus) – CWM Recovery v6.0.4.4
Then flash that with Odin ?
edit: I think I know why this failed miserably....On Odin V3.10.6 I clicked "AP" for some reason, when I was flashing the firmware. Could that be the problem? If so, is there a fix ? i can't access my phones SD card .
Right link, but Clockworkmod is not a good choice for a recovery to flash through Odin. Use TWRP instead as Clockworkmod is no longer updated.
Cyanogenmod is pre-rooted, though until you open the developer options in settings you can't access it. That's why you don't need to root beforehand. There is no harm however if you choose to root anyway before installing.
Clicking Odin like that shouldn't do anything. But where you've encountered problems, read the instructions here to wipe the storage. Then install the stock ROM again through Odin to see if that resolves the problem.
i just installed cm-12.1-20150625-NIGHTLY-jfltexx on my s4 with cm-12.1-20150623-NIGHTLY-jfltexx but there is a problem with the phone functions. It can't make any call. .it do not find my sim card!! Same thing with cm-12.1-20150624-NIGHTLY . The last one that works is 20150623 . Is there anyone that can confirm my problem?
Strephon Alkhalikoi said:
Right link, but Clockworkmod is not a good choice for a recovery to flash through Odin. Use TWRP instead as Clockworkmod is no longer updated.
Cyanogenmod is pre-rooted, though until you open the developer options in settings you can't access it. That's why you don't need to root beforehand. There is no harm however if you choose to root anyway before installing.
Clicking Odin like that shouldn't do anything. But where you've encountered problems, read the instructions here to wipe the storage. Then install the stock ROM again through Odin to see if that resolves the problem.
Click to expand...
Click to collapse
I am following this:
Code:
TWRP Recovery v2.8.7.0 is suggested for installation
First time or clean install:
Download the ROM from the link above
Download GApps package for Lollipop 5.1
Put the zip files on your SDCard
Reboot in Recovery
Wipe Data / Factory Reset
Optional: convert to F2FS
Select "Install zip from SDCard"
Choose ROM's zip file
Choose GApps zip file
Reboot system
Unfortunately, I am stuck though. I can't put the zip files in my phone because my phone is semi-bricked. I can't access my SD card. I don't have another device that I could plug my SD card into, and I don't have an SD card reader either!
edit: sorry im really like uneasy right now and im thinking that I don't want to lose all my data, so i'm exploring a bit. I booted up CWM because I had a backup made from there. I saw the backup, but when I tried to restore it, it said "MD5 Mismatch" is there ANY way I could get that backup of mine to restore? I would have a peace of mind and then we can restart this process from there.
flipboi15 said:
I am following this:
Code:
TWRP Recovery v2.8.7.0 is suggested for installation
First time or clean install:
Download the ROM from the link above
Download GApps package for Lollipop 5.1
Put the zip files on your SDCard
Reboot in Recovery
Wipe Data / Factory Reset
Optional: convert to F2FS
Select "Install zip from SDCard"
Choose ROM's zip file
Choose GApps zip file
Reboot system
Unfortunately, I am stuck though. I can't put the zip files in my phone because my phone is semi-bricked. I can't access my SD card. I don't have another device that I could plug my SD card into, and I don't have an SD card reader either!
edit: sorry im really like uneasy right now and im thinking that I don't want to lose all my data, so i'm exploring a bit. I booted up CWM because I had a backup made from there. I saw the backup, but when I tried to restore it, it said "MD5 Mismatch" is there ANY way I could get that backup of mine to restore? I would have a peace of mind and then we can restart this process from there.
Click to expand...
Click to collapse
I assume your model is i337M. Check it in download mode. If that's the case, then follow this.
1. Flash this:
http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758
2. Flash TWRP
3. Flash the rom you want.
That's all. You are making it to difficult.
Lennyz1988 said:
I assume your model is i337M. Check it in download mode. If that's the case, then follow this.
1. Flash this:
http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758
2. Flash TWRP
3. Flash the rom you want.
That's all. You are making it to difficult.
Click to expand...
Click to collapse
So step 1 and 2 flash that with Odin? Do I wipe or no? If i decide not to wipe, will i still have my old stuff from my phone back?
I am confused with step 3. How do I flash the ROM? Using ODIN? Or TWRP? If its through TWRP, how do I get the ROM in my SD card?
edit: I flashed the first link and this is my log, it failed
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried a second time, it still failed
I think my phone is bricked. Its stuck on "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
latest log im digging myself a deeper hole :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!
Flashing CM is easy. It doesn't require root access because this phone has no bootloader lock. Download a custom recovery with TAR file format, install drivers, go to the download mode of your phone, connect your phone to your computer, and use Odin to flash the recovery. Then copy CM zip file to a SD card and flash it in recovery. That's all!?
For recovery I recommend TWRP: teamw.in
If you've installed Kies you should have drivers on your computer. Otherwise install Kies or only drivers if you can find them on Samsung official website.
flipboi15 said:
So step 1 and 2 flash that with Odin? Do I wipe or no? If i decide not to wipe, will i still have my old stuff from my phone back?
I am confused with step 3. How do I flash the ROM? Using ODIN? Or TWRP? If its through TWRP, how do I get the ROM in my SD card?
edit: I flashed the first link and this is my log, it failed
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried a second time, it still failed
I think my phone is bricked. Its stuck on "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
latest log im digging myself a deeper hole :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!
Click to expand...
Click to collapse
Use a different usb port / different usb cable.
Thanks for all the help guys I really do appreciate it and I can't thank you all enough. I have the stock rom working at the moment. I have TWRP installed and I put the ROM and GAPPS into my SD card. I booted into TWRP recovery and clicked on install then i chose the ROM zip but, it fails. This is the error attached picture.
flipboi15 said:
Thanks for all the help guys I really do appreciate it and I can't thank you all enough. I have the stock rom working at the moment. I have TWRP installed and I put the ROM and GAPPS into my SD card. I booted into TWRP recovery and clicked on install then i chose the ROM zip but, it fails. This is the error attached picture.
Click to expand...
Click to collapse
Try redownloading the .zip file. Maybe it's corrupt.
So after trying to install the ROM in TWRP and failing. I couldn't load up the phone anymore, it got stuck at the Samsung Logo screen. I am now re-flashing I337MVLUGOC4 - 5.0.1 Lollipop.
edit:
So at the moment, my phone is working fine on stock rom. I redownloaded the CM-12.1 optimized. I moved it into my SD card. I need to know if there are certain steps I need to do to get this right. These are the steps I took the first time.
Rebooted into TWRP recovery mode, then clicked install then I navigated to the CM-12.1 ROM zip and swiped to install.
Was I supposed to wipe anything? The only time I wiped(the default wipe in twrp) was after I installed the 5.0.1 Lollipop firmware. By the way, i noticed that my phone's internal memory is almost full, it only has 2GB of 9.69GB left in the internal. I checked it out and all my old files were still there!

i9507 Could not do normal boot, Odin mode

Hi,
I wouldn't normally post unless I really need help and I do, I've been at this for days, I'm stressing out because I really need my phone for work and I can't fix it myself...
My phone is stuck in a loop where every time I turn it off/on it goes straight into download mode.
It's doing this because I foolishly (without knowing what I was doing) used a .pit file I downloaded off of the internet.
I installed Clockworkmod 11 on my i9507 with the jfltexx i9505 rom.
It worked flawlessly except the 3G would drop out every time I locked the screen. Only 2G would work.
To try and fix it I downloaded a I9505DVUAMD8_MODEM.tar because I'm on Australia's 3G Telstra network through ALDI (medion) mobile.
The problem I had was that when I tried to flash the new modem, Odin would say that it failed.
So without knowing what I was doing, I used CSB_signed_Fusion3_TDD_0906_V2.pit
Now my phone is stuck in a loop where it goes straight into download mode.
Can someone please tell me how to fix this, I'm stressing out because all of my work is on this phone.
Please help, I'd really appreciate it.
Just flash a stock rom for the I9507 and you will be fine.
Lennyz1988 said:
Just flash a stock rom for the I9507 and you will be fine.
Click to expand...
Click to collapse
This is a really noob question but would you be able to save me a heap of time and link me to one please? My head is going to explode soon...
Edit:
I found this, which has the stock optus rom but it's an extremely slow (10 hour) 1.7gb download. I don't think this is right...
http://www.mrcrab.net/viewstockrom/30638-gt-i9507.html
alex8337 said:
This is a really noob question but would you be able to save me a heap of time and link me to one please? My head is going to explode soon...
Edit:
I found this, which has the stock optus rom but it's an extremely slow (10 hour) 1.7gb download. I don't think this is right...
http://www.mrcrab.net/viewstockrom/30638-gt-i9507.html
Click to expand...
Click to collapse
http://samsung-updates.com/details/41041/Galaxy_S4_TD-LTE/GT-I9507/OPS/I9507XXUFOA1.html
Neither mirror in that link works.
The download starts but doesn't actually download anything... It just sits at 0% with '10 hours left'.
Edit: Now it's jumped up to 22 hours left...
alex8337 said:
Neither mirror in that link works.
The download starts but doesn't actually download anything... It just sits at 0% with '10 hours left'.
Edit: Now it's jumped up to 22 hours left...
Click to expand...
Click to collapse
You can also try to reflash the recovery and then reflash the custom rom you were on. That should also work.
Lennyz1988 said:
You can also try to reflash the recovery and then reflash the custom rom you were on. That should also work.
Click to expand...
Click to collapse
Noob again... Sorry. How do I do that? Reflash the recovery I mean.
I really appreciate your help. At least I don't feel like I'm about to burst into tears anymore.
Edit: I've got recovery-clockwork-touch-6.0.4.7-jfltexx.img on my desktop, I just don't know how to use it with Odin.
alex8337 said:
Noob again... Sorry. How do I do that? Reflash the recovery I mean.
I really appreciate your help. At least I don't feel like I'm about to burst into tears anymore.
Edit: I've got recovery-clockwork-touch-6.0.4.7-jfltexx.img on my desktop, I just don't know how to use it with Odin.
Click to expand...
Click to collapse
Put it in AP/PDA (depends on the Odin version). Uncheck auto-reboot and flash it in download mode.
Lennyz1988 said:
You can also try to reflash the recovery and then reflash the custom rom you were on. That should also work.
Click to expand...
Click to collapse
I don't understand what you mean by 'reflash recovery'?
I downloaded clockworkmod touch 6.0.4.7 but its a .img file and I don't know how to use it with Odin.
So I continued with what you told me to do the first time.
Lennyz1988 said:
Put it in AP/PDA (depends on the Odin version). Uncheck auto-reboot and flash it in download mode.
Click to expand...
Click to collapse
I9507XXUFOA1_I9507OPSFOA1_I9507XXUFOA1_HOME.tar.md5 with Odin 3.09, AP.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9507XXUFOA1_I9507OPSFOA1_I9507XXUFOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I reset the phone a good 10min after and now it still boots into Odin mode but this is on the screen instead.
Odin mode
Product name: GT0i9507
Current binary: Samsung official
System status: Custom
Knox kernel lock: 0x0
Knox warranty void: 0x1
Csb-config-lsb: 0x30
Write protection: Enable
eMMC BURST MODE: Enabled
START [224, 1440]
ODIN : Invalid ext4 image
FIRMWARE UPGRADE ENCOUNTERED AN ISSSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN.
You must flash the zip file,dont unpack the zip file,put the zip file in PA or PDA
ludoke said:
You must flash the zip file,dont unpack the zip file,put the zip file in PA or PDA
Click to expand...
Click to collapse
The zip file on its own doesn't show up when I click open in Odin though?
When I click AP/PDA and the Open box pops up, it doesn't show the zip file.
file name must be PDA File (*.tar, *.md5, *.smd, *.gz, *.tgz)
What am I supposed to do...
alex8337 said:
The zip file on its own doesn't show up when I click open in Odin though?
When I click AP/PDA and the Open box pops up, it doesn't show the zip file.
file name must be PDA File (*.tar, *.md5, *.smd, *.gz, *.tgz)
What am I supposed to do...
Click to expand...
Click to collapse
Open Odin ,connect your phone to pc via usb ,developers options enabled in ...settings ...about phone ..tap 6 or 7 times on build and enable usb ...foutopsporing in Dutch...also enable unknown sources .gO IN download mode ..search for how to do it. When phone is recognized in Odin
(If in the section ID COM is blue or yellow with a number it ,youre ready to go...
Tap on AP and it will ask for a file ...navigate on your pc to the location where you have stored the file,at first choose the Chainfire root file(,leave all the settings in Odin as the are) .it will appear in the AP section and hit Start ,wait until PASS appears in Odin...Disconnect phone from pc ,shut down Odin , Start the phone again in Download mode connect to pc and follow the same steps as with root,NOW UNCHECK automatic reboot in Odin,hit start and wait for Pass.
This should do the trick
---------- Post added at 01:10 PM ---------- Previous post was at 12:56 PM ----------
For root you need .tar file so unzip the zip file only once and flash that .tar file . For TWRP use the zip file,it contents the recovery.img NO need to unzip!!!
Sorry if i put you on the wrong leg.
I kept getting the same fail message in Odin.
I've fixed it now. I used Samsung Kies > Tools > Firmware upgrade and installation. It's taken the phone back to the stock Australian Optus rom. Not the original optus rom with baseband XXUAMH2 but a newer one running 4.2.2 with baseband XXUFOA1. Unfortunately I've lost all data on it but thankfully the phone still works. I was stressing out of my mind.
Thanks to everyone for helping, I appreciate your input

Categories

Resources