Bootloader version after URDLV + firmware or modem downgrade - Galaxy Note 3 Q&A, Help & Troubleshooting

Hey
Something I don't understand.
It is always written to check *#1234# to get the bootloader version.
On my side, If I do that I get :
AP : MK2
CP : MJ7
CSC : MK3
What I don't understand is that I am rooted since MI7.
I was branded Orange - used URDLV rooting method to MI7 - URDLV to MJ3 (november) and URDLV to MK2 (last week)
without tripping knox
As I am not satisfied of MK2 (due to very strange location update from time to time), I'd like to go back to MJ3.
But all comments I read are all saying this is not possible (which might be true anyway). But all posts are always based on the *#1234# result....
I understood that URDLV was not changing the bootloader (I didn't flash the famous aboot.mbn).
So now after using URDLV method, should I understand that I got the new bootloader somehow ?
My concern is really only on this location that is sending me all around the world regularly and I think this is linked to the modem. So the idea was to downgrade the modem but can't find any experience on that. It seems modems are now linked to particular firmwares. So I wondered if I could go back to MJ3.
Some screenshots seem showing Modile Odin Pro displaying the bootloader version... but don't feel like buying an app just to get this information once and never use it...
Ahhhhhh I miss my Note 2 The only missing feature on it was the S-Pen not being able to use the "menu" and "back" button (which I already missed on the Notes1 )
Cheers

GalaxHe said:
Hey
Something I don't understand.
It is always written to check *#1234# to get the bootloader version.
...
Click to expand...
Click to collapse
No, a slightly better way to get the bootloader version is:
Code:
adb shell getprop ro.boot.bootloader
But even this one can be fooled.
Downgrading the modem is a different thing and on Note3 can be tricky.

I might be missing something here, but you used Vega to do all the upgrades. That means you still have the original bootloader - why can't you simply use the MJ3 ROM process with RDLV again to flash a root version of MJ3?
I'd back up the data then do factory reset and act as if you're doing the original RDLV again.
Do you think there would be a problem with that?

xclub_101 said:
No, a slightly better way to get the bootloader version is:
Code:
adb shell getprop ro.boot.bootloader
But even this one can be fooled.
Downgrading the modem is a different thing and on Note3 can be tricky.
Click to expand...
Click to collapse
I get an error "device not found" with this command on a terminal
What do you think about with "tricky" with the modem downgrade ?

Journyman16 said:
I might be missing something here, but you used Vega to do all the upgrades. That means you still have the original bootloader
Click to expand...
Click to collapse
I agree... but to verify this, lots of post tell to do a *#1234# - which does not return any information about MI7 (I am not supposed to have the mj3 bootloader).
Haven't found threads of people having done a downgrade using "regular" Odin...

hummm I am not supposed to type the 'adb shell' but only 'getprop ro.boot.bootloader' when using terminal on the phone........
so yes I am still on MI7
N9005XXUBMI7

No downgrade possible
Well... now I know it's not possible to downgrade !
On Odin's side :
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MJ1VEGA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> boot.img
<ID:0/012> NAND Write Start!!
<ID:0/012> modem.bin
<ID:0/012> rpm.mbn
<ID:0/012> FAIL! (Auth)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Errors in download mode on the phone screen :
When downgrading to URDLV MI7 / MJ1 / MJ3
SW REV CHECK FAIL : [rpm]Fused 2 > Binary 1
When downgrading to stock MI7
SW REV CHECK FAIL : [sbl]Fused 2 > Binary 1
I had to reflash the firmware I had previously (so MK2 URDLV) to be be able to use the phone back. I was stuck on download mode - no more recovery and default boot was saying the phone need urgent recovery through Kies - which was not usefull either as it's not able to do anything when you never used the software before...
Anyway, I might give it a try tomorrow to downgrade the modem only - see if that's possible.
btw, my knox is still 0x0

To complete this thread, I tried to downgrade the modem.bin + non-hlos.bin from MJ7 (provided with MK2 firmware) to versions I had on my PC :
MJ3
MJ1
MI7
with no luck.
Phone boots but there is no network service anymore.
I downloaded MJ4 branded to my provider and was able to flash the modem + non-hlos.bin and have that work. Unfortunatelly, it hasn't change my issue of bad location being detected. Seems this could be coming from somewhere else...
Need to try if downgrading to MJ3 works or not now that the modem is not mj7 anymore.

stuck note3
GalaxHe said:
To complete this thread, I tried to downgrade the modem.bin + non-hlos.bin from MJ7 (provided with MK2 firmware) to versions I had on my PC :
MJ3
MJ1
MI7
with no luck.
Phone boots but there is no network service anymore.
I downloaded MJ4 branded to my provider and was able to flash the modem + non-hlos.bin and have that work. Unfortunatelly, it hasn't change my issue of bad location being detected. Seems this could be coming from somewhere else...
Need to try if downgrading to MJ3 works or not now that the modem is not mj7 anymore.
Click to expand...
Click to collapse
i downloaded the 4.4.2 rom poland and flash it on hongkong one but flash was refused and stuck on boot menu,
any ideas please.

ahmekh said:
i downloaded the 4.4.2 rom poland and flash it on hongkong one but flash was refused and stuck on boot menu,
any ideas please.
Click to expand...
Click to collapse
I don't understand the link with this thread... it's about downgrading and not about upgrading.

Reflash the HK one that you had. I had similar results trying to flash an Australian version - not sure why. Instead of going back to MI7 I flashed HK MK1 version using the RDLV method - now on MK1, rooted, Knox on 0x0.
Will work on getting to Aust CSC later when I have had the phone more than 2 weeks and willing to risk warranty.

How do i do the RDLV method
Sent from my GT-I9300 using XDA Premium 4 mobile app

ahmekh said:
How do i do the RDLV method
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Go to http://forum.xda-developers.com/showthread.php?t=2498850 and have a read through. Galaxhe posted a clear explanation of how to do it in (I think) post 1127, but do some reading of the thread as well so you understand what is going on.

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

Note 3 is "not supported" by Kies 3

EDIT: At this point, I'm just trying to flash official firmware via ODIN but every attempt is ending with ODIN: Invalid ext4 image on various firmwares and via various USB ports
Hi everyone,
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I have tried reinstalling Kies, different USB ports (USB 2.0 & 3.0) after turning off USB 3.0 charging too, reseating the battery etc but each time, Kies tells me "The connected device is not supported by Kies 3. Check which devices are supported and try again." except Kies 3 is what the Note 3 uses...
Reinstalling the driver as well doesn't appear to do anything either. The Note 3 shows up in device manager as SAMSUNG Mobile USB Modem so it's detected but I can't exactly say if that is correct?
Anyway, any help is appreciated! I'll see when Samsung's contact centre is open next being Christmas and all and since I was only flashing official firmware, my Knox counter is still at 0x0 so my warranty is still in place should the need to use it arise.
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
ione2380 said:
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
Click to expand...
Click to collapse
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Having the same problem
Sentryism said:
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Click to expand...
Click to collapse
What's the solution? Do you already could find the problem?
bgantenbein said:
What's the solution? Do you already could find the problem?
Click to expand...
Click to collapse
Well, I don't have one yet. I'm still going through various firmwares but the second one I've tried threw up the same error. Basically, I'm just waiting for firmwares to download at the moment. I'll report back if I manage to fix it. I would assume it's due to not having debugging mode enabled but I can't exactly enable it in my current situation.
Here is the ODIN log if it is of any use:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> aboot.mbn
<ID:0/009> rpm.mbn
<ID:0/009> tz.mbn
<ID:0/009> sdi.mbn
<ID:0/009> NON-HLOS.bin
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> system.img.ext4
<ID:0/009> FAIL! (Ext4)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
It seems that you might have a severe case of bad blocks on the eMMC (internal flash) - that in itself should be enough reason for a warranty replacement.
If you can not do a warranty replacement you should look (inside Odin) into erasing all NAND and repartitioning (there are some posts around with similar info, read a few of those until you understand what you are doing before starting to do anything on that direction).
Hello!
I made the switch from iOS to Android a couple of days ago and as well own a Note 3 device. After a couple of days of reading around the forums I decided to flash the MK2 Uk rom since in my country we're only up to MJ7 and I've been experiencing very weird battery drains. I am aware that the update won't likely fix them and I'll have to wait for the next one in January but I hope to at least make things better. Unfortunately today I downloaded Kies3 and I'm getting the same error when I click on the firmware check or upgrade menu (or whatever it is called). I haven't tried Odin yet because the firmware was taking too long to download and I had tl go out for work. Still I very doubt it will work since the official program isn't even working.
tl;dr; Please post in the topic when you find a solution as I am experiencing the same problem as well. Especially if I have to do a warranty replace since I have a wiggly button and I was wondering whether to do that in the first place.
Possible not a genuine Note 3?
This is absurd, I said I am new to Android, this doesn't mean I have grown in a pot. My device came with all the appropriate stickers, branding and everything and is purchased through a local carrier. Unfortunately I got one from Vietnam with the wiggly home button but it is a legit device. Anyways I even tried contacting my local support but they were most unhelpful, only forwarded me to an Authorized Service Provider (what an awful chat app, they disconnected me and I even lost the details). I think I will soon try flashing a custom firmware through CWM or something..
Sentryism said:
...
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
...
Click to expand...
Click to collapse
I believe KIES 3 in Emergency Firmware Recovery mode does NOT YET support the updated bootloaders - so if your device has a bootloader >= MJ3 it will not be seen in KIES 3. I am still using Kies v3.1 but I have seen a v3.2 available, however I do not know if the problem is solved.
Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
Hi
Just had exactly the same problem as yours, and odin continuously failed just after 'hidden img'. Tried several roms to no avail. Phone was already rooted before the issue, and knox flag was already 0x1. I decided to flash cwm recovery (via odin) from here:
http://forum.xda-developers.com/showthread.php?t=2454079
The note 3 (SM-N9005) booted all the way surprisingly but with some issues (back button not working/Samsung keyboard stopping). I can now flash rom zip.
Tip: As your Knox flag is 0x0, try flashing stock recovery via odin.
Flashed Rom zip. Note 3 back to health.
shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
Hi
I flashed Djembey's deodexed pre-rooted jb 4.3 SM-N9005 XXUDMJ7 superslim rom (cwm) from here (second post):
http://forum.xda-developers.com/showthread.php?t=2461929
I used CWM recovery. After flashing the superslim rom, I was able to flash stock rom via odin.
Shayind4
---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------
androidlover287 said:
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
Click to expand...
Click to collapse
You are right.
If you tried to flash a firmware from another country than the original one, it might be that the partition size is not correct. You probably need to flash a pit file that is matching the partition size of the new firmware. Try to search for one that is matching to one of the firmware you downloaded and flash it with the new firmware ( tick repartition in Odin - this will erase your data !!!).
This is just a proposal and I do not know it it will work, but I got that hint from a thread in a German forum about changing from EU version to DBT firmware.
Im having a similar issue, except my note3 is the exynos (sm-n900), kies3 says my phone is not supported and odin fails at flashing my phone, it shows this
<ID:0/026> Added!!
<ID:0/026> Removed!!
<ID:0/027> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900ZSUCML1_N900OZSCML1_N900ZSUCMJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/027> Odin v.3 engine (ID:27)..
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> modem.bin
<ID:0/027> NAND Write Start!!
<ID:0/027> sboot.bin
<ID:0/027> boot.img
<ID:0/027> cache.img
<ID:0/027>
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have no idea on what else to do, any help please?
I've got the system.img.ext4 issue as well. Knox is still 0x0 and I was only trying to flash (Odin) a ROM from Sammobile - MI7, same level as the original but XSA instead of TGY. Bloody annoying.
Anyone got the Aussie Samsung support number?
I resolved my issue by DL'ing and flashing the TGY ROM - got an MI7 version so I should be still OK for RDLV. Apparently flashing with the ROM from another country is a problem - Odin passed teh XSA one without an issue, so I don't think it was a corrupt DL. I did see a reference in my searching to perhaps the partitions are different sizes in different CSC's or something.
So, now to enjoy my Note for a few days before rooting...

[Q] Flashing via ODIN (9506)

Hello, i have searched the forums for a flashable firmware upgrade from 4.2.2 to 4.3 for my sgs4 (i9506) and can't find it anywhere, could someone please locate me to the correct directions or atleast tell me something working? Thanks
mattish.91 said:
Hello, i have searched the forums for a flashable firmware upgrade from 4.2.2 to 4.3 for my sgs4 (i9506) and can't find it anywhere, could someone please locate me to the correct directions or atleast tell me something working? Thanks
Click to expand...
Click to collapse
Check sammobile.com then firmware for ur phone. Have a nice day
Sent from my Phone.
Edit: or here http://www.sammobile.com/firmwares/2/
Repulsa said:
Check sammobile.com then firmware for ur phone. Have a nice day
Sent from my Phone.
Click to expand...
Click to collapse
I just flashed the "I9506XXUBML5_I9506FTMBML1_I9506XXUBMK7_HOME.tar.md5" and i get "failed" and now i can't acces my phone, only download mode... please help
mattish.91 said:
I just flashed the "I9506XXUBML5_I9506FTMBML1_I9506XXUBMK7_HOME.tar.md5" and i get "failed" and now i can't acces my phone, only download mode... please help
Click to expand...
Click to collapse
Download odin 3.09 then select PDA, and find the file you download now connect the one cable to your PC and press power+volume down to your phone until u reach download mode and connect the other cable to your phone and click start.
Edit: Dont root your device you might Void your warranty after updating.
mattish.91 said:
Hello, i have searched the forums for a flashable firmware upgrade from 4.2.2 to 4.3 for my sgs4 (i9506) and can't find it anywhere, could someone please locate me to the correct directions or atleast tell me something working? Thanks
Click to expand...
Click to collapse
What u flashed is only for France Orange branded. They dont have 4.3 for others still
Repulsa said:
Download odin 3.09 then select PDA, and find the file you download now connect the one cable to your PC and press power+volume down to your phone until u reach download mode and connect the other cable to your phone and click start.
Edit: Dont root your device you might Void your warranty after updating.
Click to expand...
Click to collapse
Read this .. http://forum.xda-developers.com/showthread.php?t=2582135&page=2
---------- Post added at 02:12 AM ---------- Previous post was at 02:12 AM ----------
mattish.91 said:
I just flashed the "I9506XXUBML5_I9506FTMBML1_I9506XXUBMK7_HOME.tar.md5" and i get "failed" and now i can't acces my phone, only download mode... please help
Click to expand...
Click to collapse
Read this..... http://forum.xda-developers.com/showthread.php?t=2582135&page=2
If you do really want to upgrade after you read the upper report i can help you cause Odin and Heimdall are no more supported and you cant downgrade anymore to 4.2.2
So think about it twice
And please read here too http://forum.xda-developers.com/showpost.php?p=45666586&postcount=1 ^^
I got 5 buttons in odin and no one says "PDA" i know it's not "PIT" and the other ones are "BL, AP, CP, CSC" i guess it should be "AP" since that button is in the same place as "PDA" should be, and i still get failed when using Heimdall, i have also tried to download root, but since the download speed is so damn low from that site i cant get it... what am i doing wrong?
This is what i get:
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
xenix96 said:
Read this .. http://forum.xda-developers.com/showthread.php?t=2582135&page=2
---------- Post added at 02:12 AM ---------- Previous post was at 02:12 AM ----------
Read this..... http://forum.xda-developers.com/showthread.php?t=2582135&page=2
If you do really want to upgrade after you read the upper report i can help you cause Odin and Heimdall are no more supported and you cant downgrade anymore to 4.2.2
So think about it twice
And please read here too http://forum.xda-developers.com/showpost.php?p=45666586&postcount=1 ^^
Click to expand...
Click to collapse
Hey mate Read this :Edit: Dont root your device you might Void your warranty after updating < its a warning
mattish.91 said:
I got 5 buttons in odin and no one says "PDA" i know it's not "PIT" and the other ones are "BL, AP, CP, CSC" i guess it should be "AP" since that button is in the same place as "PDA" should be, and i still get failed when using Heimdall, i have also tried to download root, but since the download speed is so damn low from that site i cant get it... what am i doing wrong?
This is what i get:
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Bro Please remember if you update your phone to newest 4.3, there is no more chance for you to downgrade your system , and if you root/custom your phone / you will Void your Warranty , just like they said on i9506 thread to wait until someone make a custom rom in order NOT to void that warranty for your phone.
Repulsa said:
Hey mate Read this :Edit: Dont root your device you might Void your warranty after updating < its a warning
Bro Please remember if you update your phone to newest 4.3, there is no more chance for you to downgrade your system , and if you root/custom your phone / you will Void your Warranty , just like they said on i9506 thread to wait until someone make a custom rom in order NOT to void that warranty for your phone.
Click to expand...
Click to collapse
Yea. i got that, but now i can't use the phone so how do i reset it? kies doesnt work, and i can't find a proper 4.2.2 that i can flash with odin, root is not required atm...
mattish.91 said:
Yea. i got that, but now i can't use the phone so how do i reset it? kies doesnt work, and i can't find a proper 4.2.2 that i can flash with odin, root is not required atm...
Click to expand...
Click to collapse
Hello again , try here http://www.sammobile.com/firmwares/1/?model=GT-I9506&pcode=EVR#firmware Hope it helps and choose your country.
Repulsa said:
Hello again , try here http://www.sammobile.com/firmwares/1/?model=GT-I9506&pcode=EVR#firmware Hope it helps and choose your country.
Click to expand...
Click to collapse
Still can't download from those sources since they are too slow, can someone upload it somewhere else please? im allways getting interupted download...
mattish.91 said:
Still can't download from those sources since they are too slow, can someone upload it somewhere else please? im allways getting interupted download...
Click to expand...
Click to collapse
I cant try to download the file i have a 50/50 mbps and make a mirror for you but i need to know what file are you tring to download baseband, country , Carrier and such. have a nice day.
Repulsa said:
I cant try to download the file i have a 50/50 mbps and make a mirror for you but i need to know what file are you tring to download baseband, country , Carrier and such. have a nice day.
Click to expand...
Click to collapse
This is the file: http://samsung-updates.com/details/18144/Galaxy_S4_LTE-A/S800/GT-I9506/HTS/I9506XXUAMJ2.html the source is your's Thanks you'r awesome!
mattish.91 said:
I got 5 buttons in odin and no one says "PDA" i know it's not "PIT" and the other ones are "BL, AP, CP, CSC" i guess it should be "AP" since that button is in the same place as "PDA" should be, and i still get failed when using Heimdall, i have also tried to download root, but since the download speed is so damn low from that site i cant get it... what am i doing wrong?
This is what i get:
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Yes, AP is correct. Try a different data cable.
Enviado desde mi GT-P7510 usando Tapatalk 2
mattish.91 said:
This is the file: http://samsung-updates.com/details/18144/Galaxy_S4_LTE-A/S800/GT-I9506/HTS/I9506XXUAMJ2.html the source is your's Thanks you'r awesome!
Click to expand...
Click to collapse
Hello again here is the 4.2.2 firmware for your GT-I9506 , Make sure to Follow the instruction. and hoping to fix your problem, Have a nice day.
Gt-19506 4.2.2 Firmware https://mega.co.nz/#!XV4wRZ6b!LEDB9WuyI9SLUjqDsPrlBhTRSo9z1Sz6uWRCiq74qE8
Instructions For Flashing Firmware:
- Extract (unzip) the firmware file
- Download Odin3 v3.09 (From https://mega.co.nz/#!UdRRyCAT!H4FyVxYynNWvXqRNmnpMGQRCP-dG3uykgP2pT4rh8Ek)
- Extract Odin .ZIP file
- Open Odin3 v3.09
- Restart phone in download mode (Press and hold Power + Volume down buttons) in order to reach download mode.
- Connect phone and wait until you get a blue sign in Odin
- Add I9506XXUAMJ2_I9506HTSAMJ2_I9506XXUAMI1_HOME.tar.md 5 to AP
- Make sure re-partition is NOT ticked
- Click start button, and wait a few minutes.
-Your phone should automatically reboot after completion
-You can now disconnect your phone from computer .
- If you encounter any issues with the firmware (Any FC, Bootloop etc)
- Boot into recovery mode (power+vol up)
- Choose to wipe/factory reset. (THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!)
- Then choose reboot and you should be good to go!
Repulsa said:
Hello again here is the 4.2.2 firmware for your GT-I9506 , Make sure to Follow the instruction. and hoping to fix your problem, Have a nice day.
Gt-19506 4.2.2 Firmware https://mega.co.nz/#!XV4wRZ6b!LEDB9WuyI9SLUjqDsPrlBhTRSo9z1Sz6uWRCiq74qE8
Instructions For Flashing Firmware:
- Extract (unzip) the firmware file
- Download Odin3 v3.09 (From https://mega.co.nz/#!UdRRyCAT!H4FyVxYynNWvXqRNmnpMGQRCP-dG3uykgP2pT4rh8Ek)
- Extract Odin .ZIP file
- Open Odin3 v3.09
- Restart phone in download mode (Press and hold Power + Volume down buttons) in order to reach download mode.
- Connect phone and wait until you get a blue sign in Odin
- Add I9506XXUAMJ2_I9506HTSAMJ2_I9506XXUAMI1_HOME.tar.md 5 to AP
- Make sure re-partition is NOT ticked
- Click start button, and wait a few minutes.
-Your phone should automatically reboot after completion
-You can now disconnect your phone from computer .
- If you encounter any issues with the firmware (Any FC, Bootloop etc)
- Boot into recovery mode (power+vol up)
- Choose to wipe/factory reset. (THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!)
- Then choose reboot and you should be good to go!
Click to expand...
Click to collapse
This is my result:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUAMJ2_I9506HTSAMJ2_I9506XXUAMI1_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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so this wasn't working, any idea? xD
mattish.91 said:
This is my result:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUAMJ2_I9506HTSAMJ2_I9506XXUAMI1_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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so this wasn't working, any idea? xD
Click to expand...
Click to collapse
You are trying to flash a stock 4.2.2 over a 4.3 knox bootloader!!!! If course you will get error!!!!
Since you have 4.3 knox bootlader, you only can flash stock 4.3 roms. Download the last update for your model from sammobile and reflash again with same process.
Enviado desde mi GT-I9500 usando Tapatalk 2
jaswinky said:
You are trying to flash a stock 4.2.2 over a 4.3 knox bootloader!!!! If course you will get error!!!!
Since you have 4.3 knox bootlader, you only can flash stock 4.3 roms. Download the last update for your model from sammobile and reflash again with same process.
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
im sorry, im totally lost and confused, what am i missing, there is only one 4.3 rom that is flashable throu odin and thats the french version and that should work in Sweden aswell, when i flash that rom i'm still getting that error, should i try to flash root before continuing? incase yes, which one? Im really grateful for all your help.
mattish.91 said:
im sorry, im totally lost and confused, what am i missing, there is only one 4.3 rom that is flashable throu odin and thats the french version and that should work in Sweden aswell, when i flash that rom i'm still getting that error, should i try to flash root before continuing? incase yes, which one? Im really grateful for all your help.
Click to expand...
Click to collapse
hello again , i did not know that you have a the newest bootloader for your phone and yet you requested a 4.2.2 anyways since your Knox void warranty is not 0x1 yet go ahead and send it back for repair , im sure they will fix this problem, since you did not void your warranty yet that's the best solution i can give you. or wait to someone here on xda know's how to fix this issue. have a nice day.
Repulsa said:
hello again , i did not know that you have a the newest bootloader for your phone and yet you requested a 4.2.2 anyways since your Knox void warranty is not 0x1 yet go ahead and send it back for repair , im sure they will fix this problem, since you did not void your warranty yet that's the best solution i can give you. or wait to someone here on xda know's how to fix this issue. have a nice day.
Click to expand...
Click to collapse
The problem is solvet simply flashed root, the only thing not working (so far) is keyboard xD and it is running 4.3

Serious problem with my Note 3 (SM-N9005 SFR)

After tried flashing rom from other regions (e.g. XME, TGY, THL, SFR) with odin 3.09, but fail every time. Now, I cannot use my phone. When turn on my Note 3, it will be in Odin Mode, cannot get into recovery mode at all.
So, I let someone help to solve this problem, but it get worse as show in below link.
Could anyone help me with this problem??
imagizer.imageshack.us/v2/800x600q90/191/w28d.jpg
Solved this issue by this link: http://forum.xda-developers.com/showthread.php?t=2614787
wittaya73 said:
After tried flashing rom from other regions (e.g. XME, TGY, THL, SFR) with odin 3.09, but fail every time. Now, I cannot use my phone. When turn on my Note 3, it will be in Odin Mode, cannot get into recovery mode at all.
So, I let someone help to solve this problem, but it get worse as show in below link.
Could anyone help me with this problem??
imagizer.imageshack.us/v2/800x600q90/191/w28d.jpg
Click to expand...
Click to collapse
Did you try to upgrade to 4.4.2?
radicalisto said:
Did you try to upgrade to 4.4.2?
Click to expand...
Click to collapse
Not yet. I've just tried with 4.3
Here are Odin shown to me:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005SFRDMJ4_N9005XXUDMJ7_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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
can anyone help me, please?
Try flash back your origin country ROM. What had you tick at PC Odin?
and you mention TGY, if not wrong that is for Hong Kong.
Hong Kong N9005 is unfriendly with any others country ROM, it can't cross flashing.
Andrewtst said:
Try flash back your origin country ROM. What had you tick at PC Odin?
and you mention TGY, if not wrong that is for Hong Kong.
Hong Kong N9005 is unfriendly with any others country ROM, it can't cross flashing.
Click to expand...
Click to collapse
I did flash back to origin country, which is SFR (France) with Odin, but it still fail.
In Odin, I tick "Auto Reboot" and "F. Reset time".
wittaya73 said:
I did flash back to origin country, which is SFR (France) with Odin, but it still fail.
In Odin, I tick "Auto Reboot" and "F. Reset time".
Click to expand...
Click to collapse
It's failing on bootloader, did you attempt to upgrade to 4.4.2 and change your mind? Or trying to downgrade ?
radicalisto said:
It's failing on bootloader, did you attempt to upgrade to 4.4.2 and change your mind? Or trying to downgrade ?
Click to expand...
Click to collapse
I've never attempted to upgrade to 4.4.2.
I've just tried to flash with international firmware in order to get local language menu.
My Note 3 is SM-N9005 SFR, but I want to flash with SM-N9005 THL or XME. But flash fail every time, and it cannot go into normal screen, even recovery mode. I just stuck in Odin mode when I turn on my phone.
Andrewtst said:
Try flash back your origin country ROM. What had you tick at PC Odin?
and you mention TGY, if not wrong that is for Hong Kong.
Hong Kong N9005 is unfriendly with any others country ROM, it can't cross flashing.
Click to expand...
Click to collapse
Hi, sorry to hijack, but how do I know if a ROM is going to be compatible with my phone?
I don't think the ROM thread would say what country's Note 3 it will be compatible/incompatible with, right? I'm getting a Note 3 and planning to flash a custom ROM.
fterh said:
Hi, sorry to hijack, but how do I know if a ROM is going to be compatible with my phone?
I don't think the ROM thread would say what country's Note 3 it will be compatible/incompatible with, right? I'm getting a Note 3 and planning to flash a custom ROM.
Click to expand...
Click to collapse
You are right. I don't know either. I only get the ROM which others already did before.
wittaya73 said:
Not yet. I've just tried with 4.3
...
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What does it say on the "download mode" initial screen? (knox and the other flags).
Was the phone carrier-locked on SFR?
wittaya73 said:
I've never attempted to upgrade to 4.4.2.
I've just tried to flash with international firmware in order to get local language menu.
My Note 3 is SM-N9005 SFR, but I want to flash with SM-N9005 THL or XME. But flash fail every time, and it cannot go into normal screen, even recovery mode. I just stuck in Odin mode when I turn on my phone.
Click to expand...
Click to collapse
Flash BTU firmware, it should be OK.
Find the download link below:
- BTU MJ7: http://www.sammobile.com/firmwares/3/?download=21277
- BTU MK2: http://www.sammobile.com/firmwares/3/?download=23215
Firstly try BTU MJ7
xclub_101 said:
What does it say on the "download mode" initial screen? (knox and the other flags).
Was the phone carrier-locked on SFR?
Click to expand...
Click to collapse
knox 0x1
aboot fused 3 > binary 2
I did try with BTU firmware, but it still fail flashing with Odin 3.09
Thanks for your replys
I had this error (among others) when I soft bricked & couldn't get MJ7 to flash but it worked after flashing pit, BTU MK2, modem & csc with Odin 3.0.4
zoso28 said:
I had this error (among others) when I soft bricked & couldn't get MJ7 to flash but it worked after flashing pit, BTU MK2, modem & csc with Odin 3.0.4
Click to expand...
Click to collapse
Can you give me the instruction to flashing pit, BUT MK2, modem & csc with odin? Thank you.
wittaya73 said:
knox 0x1
aboot fused 3 > binary 2
I did try with BTU firmware, but it still fail flashing with Odin 3.09
Thanks for your replys
Click to expand...
Click to collapse
Which version of BTU have you tried?
Did you try MK2 BTU?
vndnguyen said:
Which version of BTU have you tried?
Did you try MK2 BTU?
Click to expand...
Click to collapse
Yes, I've flashed (AP) MK2 BTU with Odin 3.09 and 3.04; but result still the same, Fail !!
I don't know that the first error (fail) was because I chose BL instead of AP or not.
I noticed that I did wrong after I clicked start button; and Odin told me Fail, then I flashed again with odin in AP with the same file.
wittaya73 said:
Yes, I've flashed (AP) MK2 BTU with Odin 3.09 and 3.04; but result still the same, Fail !!
Click to expand...
Click to collapse
What is the bootloader version of XME, TGY, THL firmware you have used to flash?
Make sure the bootloader of the firmware is being flash (BTU) should be equal or higher the bootloader version of the above firmwares.
You can not use a lower bootloader to flash over a higher one.
vndnguyen said:
What is the bootloader version of XME, TGY, THL firmware you have used to flash?
Make sure the bootloader of the firmware is being flash (BTU) should be equal or higher the bootloader version of the above firmwares.
You can not use a lower bootloader to flash over a higher one.
Click to expand...
Click to collapse
With my stupid, I didn't look what was my current bootloader that came with the mobile phone. I've just downloaded "N9005XXUDMJ7_N9005OLBDMK2_THL", and flashed it with Odin.

Stuck at Odin mode ? Please help

Hi,
I wanted to reinstall the stock rom via odin and i was trying to put it to odin mode but I didn't know my Pda csc so I decided to reboot it before flashing to make sure I got the correct firmware but now it won't reboot and it's stuck at odin mode despite removing the battery and inserting it again .
Is the phone an i337 or i337m?
audit13 said:
Is the phone an i337 or i337m?
Click to expand...
Click to collapse
IT's i337 and it has the letters UD in the same line and it's from AT&T btw and I checked sammobile website and I think there are two firmware to download but I don't know which one
Thanks for your reply.I could have replied earlier but I didn't get the notification
In download mode, do you see anything about knox or warranty bit?
Id this the stock ROM you tried to flash: http://www.sammobile.com/firmwares/database/SGH-I337/ ?
audit13 said:
In download mode, do you see anything about knox or warranty bit?
Id this the stock ROM you tried to flash: http://www.sammobile.com/firmwares/database/SGH-I337/ ?
Click to expand...
Click to collapse
the knox count is :0
and I didn't even try to flash.I was seeing if i can put it into download mode and then I went to download the firmware and then found out there are two of them so when I tried rebooting to check which one I need from the system info , it got stuck.
Looks like neither of the firmware files from sammobile.com will work as your phone is running at least a 4.3 bootloader as indicated by the presence of the "Knox" in download mode. Your bootloader may be locked as well.
You can't boot into recovery either?
audit13 said:
Looks like neither of the firmware files from sammobile.com will work as your phone is running at least a 4.3 bootloader as indicated by the presence of the "Knox" in download mode. Your bootloader may be locked as well.
You can't boot into recovery either?
Click to expand...
Click to collapse
No I can't
Okay, this may help: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
audit13 said:
Okay, this may help: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Click to expand...
Click to collapse
Ok I will try and let you know.I am currently trying to restore with kies
If kies doesn't work, try smart switch.
audit13 said:
If kies doesn't work, try smart switch.
Click to expand...
Click to collapse
I am getting the same error from kies and odin which is sw rev check fail : fused :5 ,binary :1
and this is odin's log :
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I might try the files in the guide but I don't know which bootloader I have
The rom can't be flashed because the rom you are flashing has a bootloader that is older than the bootloader on the phone. This is evidenced by the failed to flash the aboot.mbn file.
Where did you get the rom file?
audit13 said:
The rom can't be flashed because the rom you are flashing has a bootloader that is older than the bootloader on the phone. This is evidenced by the failed to flash the aboot.mbn file.
Where did you get the rom file?
Click to expand...
Click to collapse
I have just checked and I think kies was downloading the one with the mdl bootloader and I think it's the same one I tried flashing with odin.The first one from this link http://www.sammobile.com/firmwares/database/SGH-I337/
Thanks again
Looks like kies will not restore the phone. You'll have to flash a newer rom using Odin. Check out the link I posted earlier.
audit13 said:
Looks like kies will not restore the phone. You'll have to flash a newer rom using Odin. Check out the link I posted earlier.
Click to expand...
Click to collapse
It only has 2 firmwares and I already tried 1 and the second has a different bootloader.
Edit: If you mean the guide,then it is stated at the end that I shouldn't use it with MDL
http://forum.xda-developers.com/showpost.php?p=65534997&postcount=8
If your phone has the mdl bootloader, the mdl sammobile.comm firmware should work. If the mdl firmware can't be flashed to the phone, this tells me the phone is not running an mdl bootloader.
Yes, the guide should not be used if the bootloader is mdl but this may not be the case with your phone as there is a reference to "knox" in download mode.
audit13 said:
If your phone has the mdl bootloader, the mdl sammobile.comm firmware should work. If the mdl firmware can't be flashed to the phone, this tells me the phone is not running an mdl bootloader.
Yes, the guide should not be used if the bootloader is mdl but this may not be the case with your phone as there is a reference to "knox" in download mode.
Click to expand...
Click to collapse
I don't know what's wrong but kies and smartswitch are downloading the one with the mdl bootloader
It's probably picking the mdl because that is the only full rom available for the i337. Any updates beyond 4.2 were only released as ota updates. You will have no choice but to flash in accordance with a locked bootloader.
audit13 said:
It's probably picking the mdl because that is the only full rom available for the i337. Any updates beyond 4.2 were only released as ota updates. You will have no choice but to flash in accordance with a locked bootloader.
Click to expand...
Click to collapse
There is also the one with the mdb and I tried it too but I didn't work.I didn't understand the second sentence? Should I follow the guide and install one of the firmwares ? Which one do you recommend ? or are they the same ?

Categories

Resources