BRICK - Accidentally flashed N900P firmware to N9005 - Galaxy Note 3 Q&A, Help & Troubleshooting

Hello,
i got a device to repair. I am not so familiar with samsung devices so i would apreciate some advice/help.
I dont know how to flash correctly the n9005 firmware.
I cant go to recovery and when try to boot there is shown on the screen "kernel is not seandroid enforcing, set warranty bit : kernel" and the device is rebooting to this text over and over.
It Is N9005 (is written under the battery).
But when i go to download mode it is listed this:
Code:
Odin Mode
product name: SM-N900P
Current Binary: Samsung Official
System Status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
Qulcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A3, P1
Write Protection: Enable
I assume the owner accidentally flashed an n900P firmware to his n9005 device.
I tried many ODIN bversions (3.10.7,3.10.6,3.07,1.85) and stock 5.0, 4.4.2, 4.3 firmwares, various n9005 PIT files
when flashing a stock 4.4.2 firmware (only AP file from sammobile)
Code:
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> SingleDownload.
<ID:0/016> sbl1.mbn
<ID:0/016> NAND Write Start!!
<ID:0/016> FAIL! (Auth)
when flashing a stock 5.0 firmware (only AP file from sammobile)
Code:
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
when flashing a 4.4.? csc file for n9005
Code:
<ID:0/015> Odin engine v(ID:3.1100)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Re-Partition operation failed]
closest i got with this:
in ODIN 3.07 when flashing kitkat csc file i got
Code:
<ID:0/015> Firmware update start..
<ID:0/015> cache.img.ext4
<ID:0/015> NAND Write Start!!
<ID:0/015> hidden.img.ext4
<ID:0/015> FAIL
and on the device was shown:
Code:
secure check fail : PIT
Set warranty bit : cache
Unsupport dev_type

nobody?
I make a step further.
Now i can flash system (AP) or i can flash twrp recovery or root trough ODIN, but i cant flash the whole stock, because it will fail everytime on sbl1.img, aboot or hidden.image.ext4
So now i can boot the system, but with N900P modem, kernel and othe rpartitions, so wifi dont work ect.
Now it would be superb to have a zip file with stock modem,sbl,aboot,non-hlos to flash it trough TWRP.
please any advice?

Sorry for my English!!
Download your region firmware from sammobile and pit file for your device n9005 note 3 open europ from xda.
Open odin select pit then the rom on itch specific place flash everything...
Let me know if you've got a positive result.
Sent from my SM-N910F using XDA-Developers mobile app

tried this dozen times. It gives me error when Odin tries to write the sbl1 or aboot or modem partition (as i wrote in OP). It gives error because the pit file doesn't match.

Is it possible the phone's motherboard was swapped for a 900p?

don't know... maybe. so you suggest to imstall stock N900P firmware?

https://mega.nz/#!kQtGnCYZ!7jko1XT7fPc9mIGHE8JLZhOvaeGH6qQbaW7Y6RYBQjU
This is a pit file for n9005 Europe
I advice you to reflash the rom of your original specific model with the pit file with wipe partition checked
Let me know wen u did
Sent from my SM-N910F using XDA-Developers mobile app

I will try. I avoided to wipe partitions while users say here on xda that it is a one way ride. ?

Samsung seems to have pretty good security measures in place to prevent flashing incorrect ROMs via Odin.
The failure to flash the 9005 aboot file tells me the bootloader on the rom and the bootloader in the phone do not match.

so how it can be, that i have an n9005 device with n900p Firmware and all partitions?

Does the imei in the phone match the imei on the printed label under the battery?

And why not your device would be a N900P ? Remove battery and see...
Maybe your USB is bad (it happened to me : 4 cables, 3 not working, 1 working hopefully)
Or maybe your downloaded ROM can't been flashed (weird, but it happened also to me), so flash the same model, but other revision (exemple OD3 doesn't work, try with OJ3, in my case)
Good luck !

use kies to install firmware. from kies select tools then "Emergency firmware recovey".

Munawar Mehmood said:
use kies to install firmware. from kies select tools then "Emergency firmware recovey".
Click to expand...
Click to collapse
the kies dont see my device.

cedric3 said:
And why not your device would be a N900P ? Remove battery and see...
Maybe your USB is bad (it happened to me : 4 cables, 3 not working, 1 working hopefully)
Or maybe your downloaded ROM can't been flashed (weird, but it happened also to me), so flash the same model, but other revision (exemple OD3 doesn't work, try with OJ3, in my case)
Good luck !
Click to expand...
Click to collapse
as i wrote under thebbattery is written n9005. usb is good use it to flash other phones. tried to flash about 4 stock roms.

DallasCZ said:
as I wrote, under the battery is written N9005. USB is good : I use it to flash other phones. I tried to flash about 4 stock roms.
Click to expand...
Click to collapse
Install Kies ot SmartSwitch (Kies' replacement)
Go to Emergency
Enter N9005 in device model
Enter the S/N number (written under the battery)
Connect your phone (don't worry if it is not recognized)
Go !
It will download the right update and install it : be patient, don't disconnect the phone or internet...
Good luck

jemis1983 said:
https://mega.nz/#!9BtkxK4A!Gy7muVwEtYBQFtxktDfCFK3VfcMZanfOMdOP9Elrm1U
This is a pit file for n9005 Europe
I advice you to reflash the rom of your original specific model with the pit file with wipe partition checked
Let me know wen u did
Sent from my SM-N910F using XDA-Developers mobile app
Click to expand...
Click to collapse
this is only a bat file to store the pit from the device.There is no pit file inside.

cedric3 said:
Install Kies ot SmartSwitch (Kies' replacement)
Go to Emergency
Enter N9005 in device model
Enter the S/N number (written under the battery)
Connect your phone (don't worry if it is not recognized)
Go !
It will download the right update and install it : be patient, don't disconnect the phone or internet...
Good luck
Click to expand...
Click to collapse
smart switch sys that my device dont support iniciation (after i added the sn number and mobile number.

DallasCZ said:
smart switch sys that my device dont support iniciation (after i added the sn number and mobile number.
Click to expand...
Click to collapse
Ok, and have you found the PIT file for your device ?

cedric3 said:
Ok, and have you found the PIT file for your device ?
Click to expand...
Click to collapse
I have the pit file for N9005 i flashed it using ODIN ..it was all ok
When i try to flash the AP image of stock (that cotains all parts BL,AP,CSC, CP) the flash ends by starting with flashing BL partitions sbl1.img)
When try to flash BL (bootloader) there is error in flashing sbl1.img.
the same goe with CSC and CP images (always show some error in flashing aboot.img and other partitions and ODIN stops.
I can flash AP (the AP that is only the system,recovery,boot) it goes well, the device starts but has some errors (because of missing parts in CSC and CP?.). wifi dont work i see full signal but there is no simcard inserted
Now i can boot the device the imei that is shown in the android systme is other than the imei on the back (under the battery).
I think someone tried to flash a N900P firmware over the N9005.
Now i cant flash the rest of the partitions.

Related

FAIL Flashing stock 4.2.2

Ive been desperately trying to return to stock to unroot my phone for 2 days to no avail.
Holding the power button takes me to the Samsung bootloop.
I used Odin 1.85 to flash a HOME.tar.md5 file getting this message:
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it says the following:
ODIN MODE
Product Name:GT-i19505
Current binary: Custom
System status: Custom
Knox Kernel lock: 0x0
Knox warranty void: 0x1
CSB-CONFIG-LSB: 0x30 (have no idea what this is)
Write protection: Enable
eMMC Burst mode: enabled
START [224, 1440]
Any ideas?
poninaine said:
Ive been desperately trying to return to stock to unroot my phone for 2 days to no avail.
Holding the power button takes me to the Samsung bootloop.
I used Odin 1.85 to flash a HOME.tar.md5 file getting this message:
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it says the following:
ODIN MODE
Product Name:GT-i19505
Current binary: Custom
System status: Custom
Knox Kernel lock: 0x0
Knox warranty void: 0x1
CSB-CONFIG-LSB: 0x30 (have no idea what this is)
Write protection: Enable
eMMC Burst mode: enabled
START [224, 1440]
Any ideas?
Click to expand...
Click to collapse
are you putting it in download mode
http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/
jaythenut said:
are you putting it in download mode
http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/
Click to expand...
Click to collapse
Yes, I specifically wrote down what it said on the top left side in download mode,too.
poninaine said:
Yes, I specifically wrote down what it said on the top left side in download mode,too.
Click to expand...
Click to collapse
Did you:
Use the cable that came with your device.
Use the usb ports in the back of your computer. Don't use a hub.
Try on a different computer.
Get firmware from sammobile.com
These are all things that you should check. Also, I've had Odin fail a number of times and the for whatever reason decide to work. It can be finicky.
jd1639 said:
Did you:
Use the cable that came with your device.
Use the usb ports in the back of your computer. Don't use a hub.
Try on a different computer.
Get firmware from sammobile.com
These are all things that you should check. Also, I've had Odin fail a number of times and the for whatever reason decide to work. It can be finicky.
Click to expand...
Click to collapse
I also found certain versions of Odin didn't work with some ROMS. When I tried using a 3.1x version of Odin to root my I9505G, it didn't setup properly, but using the 3.07 version did.
jd1639 said:
Did you:
Use the cable that came with your device.
Use the usb ports in the back of your computer. Don't use a hub.
Try on a different computer.
Get firmware from sammobile.com
These are all things that you should check. Also, I've had Odin fail a number of times and the for whatever reason decide to work. It can be finicky.
Click to expand...
Click to collapse
Yes I have tried all of those things. I also downloaded all the Odin versions and tried them. Unfortunately all of them failed. Is there any idea of what the failure in the original post means?
poninaine said:
Yes I have tried all of those things. I also downloaded all the Odin versions and tried them. Unfortunately all of them failed. Is there any idea of what the failure in the original post means?
Click to expand...
Click to collapse
In the last fail the box on the bottom left side said "Leave CS" what does this mean?
poninaine said:
Yes I have tried all of those things. I also downloaded all the Odin versions and tried them. Unfortunately all of them failed. Is there any idea of what the failure in the original post means?
Click to expand...
Click to collapse
Do you know what firmware you were on? And what country and carrier are you.
jd1639 said:
Do you know what firmware you were on? And what country and carrier are you.
Click to expand...
Click to collapse
You mean now or before the root? And my country is Estonia which has no stock .tar file anywhere on the internet. I read somewhere that you can just use a random countrys one and change the csc later so I decided to do that.
poninaine said:
You mean now or before the root? And my country is Estonia which has no stock .tar file anywhere on the internet. I read somewhere that you can just use a random countrys one and change the csc later so I decided to do that.
Click to expand...
Click to collapse
Yes, before root.
I even tried re-partition. Still failed instantly.
jd1639 said:
Yes, before root.
Click to expand...
Click to collapse
Before root I was on the stock Android 4.2.2. The first time I flashed anything it was the new leaked 4.3 which worked just fine.
Then I flashed CM 10.1 and it worked but the problems started when I wanted to get back to stock.
poninaine said:
I even tried re-partition. Still failed instantly.
Click to expand...
Click to collapse
I'm pretty sure it's the firmware version you're flashing that's the problem. If you know what it was before you rooted I'd look for the same version.
I have a similar problem
Hello there,
I have a similar problem but in odin it is a success but then i get stuck at boot.
To flash the file as a success, remove your device then flash again. By looking at your info, it says you have samsung knox which is a bummer (i'm in the same boat), you'll have to flash the same stock firmware as you did last time
Let me know how you get on mate
LimitedStreak said:
Hello there,
I have a similar problem but in odin it is a success but then i get stuck at boot.
To flash the file as a success, remove your device then flash again. By looking at your info, it says you have samsung knox which is a bummer (i'm in the same boat), you'll have to flash the same stock firmware as you did last time
Let me know how you get on mate
Click to expand...
Click to collapse
If Odin is successful but you get stuck at boot, do a factory reset in the stock recovery and it'll get you past the boot loop.
Would that delete my internal sd card folders etc?
---------- Post added at 10:12 PM ---------- Previous post was at 10:04 PM ----------
jd1639 said:
If Odin is successful but you get stuck at boot, do a factory reset in the stock recovery and it'll get you past the boot loop.
Click to expand...
Click to collapse
Would that delete my internal sd cards folders, prictures etc?
What if I flash another recovery then try wiping?
LimitedStreak said:
Hello there,
I have a similar problem but in odin it is a success but then i get stuck at boot.
To flash the file as a success, remove your device then flash again. By looking at your info, it says you have samsung knox which is a bummer (i'm in the same boat), you'll have to flash the same stock firmware as you did last time
Let me know how you get on mate
Click to expand...
Click to collapse
What do you mean I have Samsung Knox? I dont know how to find the same stock firmware as I dont know what I exactly need. As in if I need the exact same as it was when I bought it then I probably wont have no luck because my countrys csc firmware is nowhere for download.
I just realised - Im probably a huge idiot - I just checked the store site from where I bought my phone and it says the OS version is 4.2 not 4.2.2. Im going to try that but does every site only has 4.2.2!

[Q] SM-N9005 bricked, help needed!

I managed not only brick one, but two SM-N9005, trying to do the Root de la Vega (yes, I used the right files).
After entering download mode, Odin failed after a short time (blue status bar was 2mm long).
Now the phone only says: Firmware upgrade encountered an issues. Please select recovery mode in Kies & try again.
But:
- Kies recovery fails
- I can't go into recovery mode, only download mode.
- Can't install stock ROM with Odin, fails as well.
- Can't CF-Auto-Root, Odin fails.
Note: Reactivation lock is OFF.
Any ideas?
k3000 said:
I managed not only brick one, but two SM-N9005, trying to do the Root de la Vega (yes, I used the right files).
After entering download mode, Odin failed after a short time (blue status bar was 2mm long).
Now the phone only says: Firmware upgrade encountered an issues. Please select recovery mode in Kies & try again.
But:
- Kies recovery fails
- I can't go into recovery mode, only download mode.
- Can't install stock ROM with Odin, fails as well.
- Can't CF-Auto-Root, Odin fails.
Note: Reactivation lock is OFF.
Any ideas?
Click to expand...
Click to collapse
try a different odin
jaythenut said:
try a different odin
Click to expand...
Click to collapse
Tried that, did not help. Thanks for the input. Used v1.85 mainly, though.
k3000 said:
Tried that, did not help. Thanks for the input. Used v1.85 mainly, though.
Click to expand...
Click to collapse
Try 3. what ever the number is i think it's better
jaythenut said:
Try 3. what ever the number is i think it's better
Click to expand...
Click to collapse
Odin3v185
That's the one I used.
k3000 said:
Odin3v185
That's the one I used.
Click to expand...
Click to collapse
No not that one v 3.07
jaythenut said:
No not that one v 3.07
Click to expand...
Click to collapse
Just tried it again with ODIN v3.07 and got the same error message in ODIN
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<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)
This is getting really frustrating...
I tried different ODINs running on XP, Win 7 and Win 8.
I ran ODIN as Admin or Standard user and I used different USB ports and cables.
Nothing seems to help.
For example, trying to flash stock ROM gives me this error in ODIN:
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What's the error on the phone?
Example:
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE.....
toker_X1 said:
What's the error on the phone?
Example:
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE.....
Click to expand...
Click to collapse
There is no error message on the display... that's exactly the text I see as well.
The only things that happens on the display the moment ODIN displays "FAIL", the blue progress bar freezes... I'd day it doesn't get further than 1-2%.
Normally there should be a red line with the error code/message.
All I can suggest is you try flashing stock rom using the several files (Kernel, PDA, CSC) method if you already havent done so already.
toker_X1 said:
Normally there should be a red line with the error code/message.
All I can suggest is you try flashing stock rom using the several files (Kernel, PDA, CSC) method if you already havent done so already.
Click to expand...
Click to collapse
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.
k3000 said:
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.
Click to expand...
Click to collapse
Why didn't you use ODIN 3.09 like guide here on XDA says?
Have you tried with that version?
k3000 said:
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.
Click to expand...
Click to collapse
Thats not 'Download Mode', thats phone firmware recovery mode.
Can you get to 'Download Mode'? - ie. Green Andriod Robot screen? (Pull out the battery, Vol Down, Home and Power)
When I soft brinked my phone, I eventually got it working by doing this..
1) Boot into 'Download Mode'
2) Using Odin 3.09 flash Stock Kernel (my kernel file was 'KERNEL-BTU-N9005XXUBMJ3-1381515654.tar'), this enabled boot to 'Recovery Mode' where is was not working before.
3) Using Odin 3.09 flash CSC (my CSC file was 'N9005OXABMJ3_CSC.tar.md5')
4) Boot into 'Recovery Mode' and wipe all (System, Data, Cache etc..)
5) Using Odin 3.09 flash Stock Firmware (my file was 'N9005XXUBMJ3_N9005OXABMJ1_N9005XXUBMJ2_HOME.tar.md5') - this will fail.
6) Using Kies 3 Beta - Perform a 'Emergency Firmware Recovery', recovery code is required - this got be back to normal
Hope this helps.
toker_X1 said:
Thats not 'Download Mode', thats phone firmware recovery mode.
Can you get to 'Download Mode'? - ie. Green Andriod Robot screen? (Pull out the battery, Vol Down, Home and Power)
When I soft brinked my phone, I eventually got it working by doing this..
1) Boot into 'Download Mode'
2) Using Odin 3.09 flash Stock Kernel (my kernel file was 'KERNEL-BTU-N9005XXUBMJ3-1381515654.tar'), this enabled boot to 'Recovery Mode' where is was not working before.
3) Using Odin 3.09 flash CSC (my CSC file was 'N9005OXABMJ3_CSC.tar.md5')
4) Boot into 'Recovery Mode' and wipe all (System, Data, Cache etc..)
5) Using Odin 3.09 flash Stock Firmware (my file was 'N9005XXUBMJ3_N9005OXABMJ1_N9005XXUBMJ2_HOME.tar.md5') - this will fail.
6) Using Kies 3 Beta - Perform a 'Emergency Firmware Recovery', recovery code is required - this got be back to normal
Hope this helps.
Click to expand...
Click to collapse
Just tried... I get stuck at 2) again trying to flash the Kernel.
k3000 said:
Just tried... I get stuck at 2) again trying to flash the Kernel.
Click to expand...
Click to collapse
try stock firmware from www.samfirmwares.com with odin v3.09
k3000 said:
Just tried... I get stuck at 2) again trying to flash the Kernel.
Click to expand...
Click to collapse
Uhm, probably a dumb question, but did you use the CSC file as well? Didn't see that in the SS.
nabilsweet007 said:
try stock firmware from www.samfirmwares.com with odin v3.09
Click to expand...
Click to collapse
Unfortunately, no progress. Fails at the very same stage all where all my other efforts have failed, too.
Note: I am using the standard USB 3.0 cable which came with the Note 3. I have tried about 5 different USB 2.0 I have at home. Windows would not recognize a USB device being connected, but the Note 3 itself starts to charge the battery.
What was the csc of the phone before you tried the first flash?
Sent from my SM-N9005
SUCCESS!!
I went to the basement and dug out an old Win XP laptop, approx. 2002 vintage, which has not been used since probably 2005.
Plugged in my Note 3 with the USB 3.0 cable (of course at USB 1.0 speeds), re-ran Root de la Vega from scratch and voilĂ , it worked!
LESSON LEARNED: Do not use VMWARE FUSION/MAC to root. IT WILL BRICK YOUR PHONE.

Error Flashing Modem: Secure Check Fail: mdm

I'm trying to flash an updated modem on my i337M which is running a custom DANDVH-GE-4.4.2-01162014-INTNL-STOCK.ZIP which is a Google Play work alike. I am trying to change the modem because it keeps droping the data connection and will only stay stable in 2G mode. Right now its modem is on AMDJ. I've tried to flash both the XXUEMKF, XXUFNA1, modems but I keep getting the following error:
Code:
<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> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1
I'm adding the modem.bin to the CP portion of Odin 3.09. I've tried doing this on all my USB ports using two new cables (all w/ the updated samsung drivers). I am using Win 8.1. All the same results. My phone says:
Code:
Odin Mode
Product name: SGH-I337M
Current Binary: Samsung Official
System Status: Official
CSB-OEM_CONFIG_LSB: 0x30
Write Protection: Enable
Then when I start flashing the following to messages appear right under the write protection message:
Code:
Start [224, 1440]
Secure Check Fail: mdm
After doing this I have to restart the phone for odin to pick it up again. It boots fine normally, and the original AMDJ modem still shows.
What's going on with this? I've looked in our forums but I can't find anything. I have TWRP installed, and I am rooted.
AHLASSICH said:
I'm trying to flash an updated modem on my i337M which is running a custom DANDVH-GE-4.4.2-01162014-INTNL-STOCK.ZIP which is a Google Play work alike. I am trying to change the modem because it keeps droping the data connection and will only stay stable in 2G mode. Right now its modem is on AMDJ. I've tried to flash both the XXUEMKF, XXUFNA1, modems but I keep getting the following error:
Code:
<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> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1
I'm adding the modem.bin to the CP portion of Odin 3.09. I've tried doing this on all my USB ports using two new cables (all w/ the updated samsung drivers). I am using Win 8.1. All the same results. My phone says:
Code:
Odin Mode
Product name: SGH-I337M
Current Binary: Samsung Official
System Status: Official
CSB-OEM_CONFIG_LSB: 0x30
Write Protection: Enable
Then when I start flashing the following to messages appear right under the write protection message:
Code:
Start [224, 1440]
Secure Check Fail: mdm
After doing this I have to restart the phone for odin to pick it up again. It boots fine normally, and the original AMDJ modem still shows.
What's going on with this? I've looked in our forums but I can't find anything. I have TWRP installed, and I am rooted.
Click to expand...
Click to collapse
Hey there, I'm trying to update my I337M's modem as well (I have a post in this forum) so I'm in the same boat as you. From the looks of it, it seems like you're not using the correct modem firmware. If you'd want to update I believe it's something like UMUEMK6 for our phones, I've tried looking around and I can't find it anywhere. Hopefully that offers some direction but I'm waiting to see as well since I'm having the same problem with Google ROMs as well (The data signal never works).
Hello once again,
After a bit of work, I managed to update the modem on my phone to MUMUEMK6 (which is the newest baseband version for the I337M). Since flashing the modem firmware, I've re-installed Danvdh-GE-4.4.2-01232014b.zip and I haven't had a problem since, works without a hitch. What you need is this file which I've RARd up for you :
(Sorry, I have to obfuscate the URL since I'm a new user on these forums, just replace *dot* with a dot)
rtigue *dot* ca/files/SGH-I337M_MK6 *dot* rar
Once you've downloaded the file, simply just boot your phone in ODIN mode, open up ODIN, add the 'modem.bin' to the Phone section in ODIN and click Start. Wait a few moments and after that you should be good to go.
Let me know if anything comes up
For some reason, yours is the only version of the mk6 modem file that worked for my i337m after I was on 4.3 GE and went to old MDJ modem to try sim unlock. Which didn't work, sigh... Thanks!
SimonPalmieri said:
Hello once again,
After a bit of work, I managed to update the modem on my phone to MUMUEMK6 (which is the newest baseband version for the I337M). Since flashing the modem firmware, I've re-installed Danvdh-GE-4.4.2-01232014b.zip and I haven't had a problem since, works without a hitch. What you need is this file which I've RARd up for you :
(Sorry, I have to obfuscate the URL since I'm a new user on these forums, just replace *dot* with a dot)
rtigue *dot* ca/files/SGH-I337M_MK6 *dot* rar
Once you've downloaded the file, simply just boot your phone in ODIN mode, open up ODIN, add the 'modem.bin' to the Phone section in ODIN and click Start. Wait a few moments and after that you should be good to go.
Let me know if anything comes up
Click to expand...
Click to collapse
@ SimonPalmieri
Hello. I'm also running a rooted i337m (Bell) with 4.2.2 i337mvluamg1 stock rom.
Please let me know if the new modem MUMUEMK6 changes the bootloader with KNOX integrated.
Thanks.
jk2rd said:
@ SimonPalmieri
Hello. I'm also running a rooted i337m (Bell) with 4.2.2 i337mvluamg1 stock rom.
Please let me know if the new modem MUMUEMK6 changes the bootloader with KNOX integrated.
Thanks.
Click to expand...
Click to collapse
Bootloader and modem are not tied together..... MK6 is the latest modem and works with 4.4.2 roms (for I337M), once the actual 4.4.2 update drops for i337m we will be able to update to that modem.
Thanks for replying Gage_Hero.
So I'm then assuming that it's NOT a good idea to flash the mk6 modem.bin on my current rom?
MK6
jk2rd said:
Thanks for replying Gage_Hero.
So I'm then assuming that it's NOT a good idea to flash the mk6 modem.bin on my current rom?
Click to expand...
Click to collapse
First you need to decide if you want to sim unlock the phone, still possible on mvluamg1, not possible on MK6. I would make sure you have a copy of modem.bin for mvluamg1 first, just incase. Then flash the MK6, I run MK6 on 4.4.2 GErom since we don't have a kitkat modem for i337m yet... once there is I will be updating.....
PS if you can find files that have md5 checksum, that is always good because then you can check the file to make sure it is complete. I had that issue flashing the MK6 modem, first file I downloaded failed in Odin, plus it had no md5 for me to check. Second one I donwloaded had the md5, which I checked and it flashed perfectly....

GT-I9500CHN Product Name Change

I need help how Change Product Name GT-I9500CHN TO GT-I9500
I try Sboot but on KK version Not working show error when i write sboot
<ID:0/012> Added!!
<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> sboot.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL!
Click to expand...
Click to collapse
and in phone ( SW REV: Invalid Magic String
There is any other sboot file for KK version or other solution thanks in advance
still waiting for solution anyone help me
imeicodes said:
I need help how Change Product Name GT-I9500CHN TO GT-I9500
I try Sboot but on KK version Not working show error when i write sboot
and in phone ( SW REV: Invalid Magic String
There is any other sboot file for KK version or other solution thanks in advance
Click to expand...
Click to collapse
Hi mate,
Not 100% sure what you want to do but as far as i know the only difference between the Chinese version and the international was the PIT , in the Chinese the internal SD is bigger about 11.5gb
If you want to use the non chinese rom you have to change the PIT
Check here.
http://forum.xda-developers.com/showthread.php?t=2265477
Thanks for reply
u read that thread but my firmware version updated on Kitkat 4.4.2
And there is available Sboot to 4.2.2 u have 4.4.2 Sboot Firmware
Code:
Note 6: If you flash I9500 stock firmware for China region, it will flash sboot.bin with it, that leads to have a Chinese bootloader (download mode will be in Chinese language and boot splash name will change). Even if you flash other stock firmware, it will not change the bootloader. So flash "GT-I9500_sboot.tar" (attached) as pda in Odin and it will fix the issue. (works on 4.2.2 firmwares!)
imeicodes said:
Thanks for reply
u read that thread but my firmware version updated on Kitkat 4.4.2
And there is available Sboot to 4.2.2 u have 4.4.2 Sboot Firmware
Code:
Note 6: If you flash I9500 stock firmware for China region, it will flash sboot.bin with it, that leads to have a Chinese bootloader (download mode will be in Chinese language and boot splash name will change). Even if you flash other stock firmware, it will not change the bootloader. So flash "GT-I9500_sboot.tar" (attached) as pda in Odin and it will fix the issue. (works on 4.2.2 firmwares!)
Click to expand...
Click to collapse
Hi,
That is a different case , that is if you wish to keep the old firmware
I would flash the PIT with a the NEW firmware
Note 2: If you have a corrupted partition table (Odin says: "there is no pit partition" or "Re-Partition operation failed"), flash pit file for your device (attached, dont forget to unzip it) (put it in pit window) with your firmware (some users reported that it worked without firmware), in this case "Re-Partition" must be marked.
Select the new firmware plus select PIT on Odin ..so it will flash the new firmware with the already included sboot with the new Partition tables (PIT)
Flash it all together

system upgrade, firmware, USB debugging problem

Hello everybody,
I bought a Samsung Galaxy Note 3 (SM-N9005) phone. Firmware: N9005ZHUENF1. Android 4.4.2.
I tried to update the system, but the phone said "I am fresh". But, it is not true, because my girlfriend has a same phone and it updated across the OTA.
I installed the KIES to the my PC and my phone do not work with it. When I connect the phone to the PC with a USB cable, not working. When I connect my girlfriends phone everything nice.
I enabled the USB debugging mode, but it is not working. When I connect the phone to the PC with a USB cable the question is not arrive that I would like to enable the debugging mode. When I connect my girlfriends phone everything nice.
I think my phone is rooted, because I checked it with an app, and the app said "Yes, rooted".
My questions are:
- is it possible to upgrade my phone to the Lollipop?
- is it possible to put into the phone the original firmware (if it will be necessary)?
- is it possible to enable the USB-debugging mode?
I am waiting for your asks.
Best regards,
Zoltan
is it possible to upgrade my phone to the Lollipop?
Yes flash a firmware via Odin see stickies .
- is it possible to put into the phone the original firmware (if it will be necessary)?
Yes as above .
- is it possible to enable the USB-debugging mode?
Yes but its not required .
This the message in the Odin window:
<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)
And on the phone:
SECURE CHECK FAIL: about
Please help!
What are you flashing ??
I downloaded the 5.0 lollipop and I would like to upgrade.
What firmware there are multiple firmwares for many variety 's of Note .
In the phone:
N9005ZHUENF1
ok, now i see that not the same what i downloaded
Odin failed flashing aboot.mbn which means the rom was not made for the phone or the bootloader in the rom is too old.
OK, I do not understand.
When I step into the download mode (volume down+home+power) I see these:
Odin mode
Product name: SM-N900A
Current binary: Samsung official
System status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
Qualcomm Securebot : Enable (CSB)
Ap SWRev: S2, T2, R2, A3, P2
Write Protection: Enable
OK, but in the settings menu my model number is: SM-N9005.
SM-900A or SM-N9005?
Please help somebody!
SM900A.
If that's what Odin mode says .
If its a new phone return to the vendor .
What does it say under the battery ??
under the battery: SM-N9005
in the recovery menu: kot49h.n900aucucnc2
Reads as possible fake.
Sent from my SM-N920C using XDA-Developers mobile app
The phone is a note 3 with a motherboard from AT&T based on the model number of Sm-n900a in download mode.
It appears that the phone has an AT&T motherboard in a note 3 international body.
So, what can I do?
All you can do is flash the latest rom for the n900a which is lollipop. The bootloader is probably locked which means you cannot install cwm or twrp. Only custom recovery that will work is safestrap.
thx, but I do not find it. Give me a link please.
gutanier said:
thx, but I do not find it. Give me a link please.
Click to expand...
Click to collapse
Your device is an AT&T Note 3 disguised as an international one, as said before.
I already had this experience with a Sprint Note 2.
So if you want simply upgrade to Stock Lollipop, here is the stock image.
If you want root, custom recovery and maybe custom ROMs, please follow this guide.
There are many customs roms supporting your device, so head to the AT&T Note 3 forum for more infos.
Good luck
THX folks, I did it, I have Lollipop on my Note 3. THX again. :good:
Hi folks again.
Mission 2: root.
How can I do it simple? SM-N900A Lollipop 5.0
http://forum.xda-developers.com/note-3-att/general/root-lollipop-att-note-3-safestrap-t3132475

Categories

Resources