Database Users

[Q] Unsupport dev_mode in bootloader

Hi
I have I9505XXUAMDM firmware installed and tried to install I9505XXUAME2_I9505OXXAMDB_NEE.
When device is in download mode and I'll start installing new firmware with odin, it stops immediately and shows this in odin (both 1.85 and 3.07):
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed (succeed 0 / failed 1)
and this in device:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
START [224, 1440]
Unsupport dev_type
Tried also differen usb port. Using original cable. After that I'm able to boot back to old firmware. Any idea what's going on?

Hi,
I used Odin 3.04 to root my phone.
All went smoothly and without a hitch.
Sent telepathically from my S4

Thanks, got it working with 3.04.
Sent from my GT-I9505 using Tapatalk 2

Sm-n9005 help!!!

so this afternoon i tried to install kitkat but it just kep failing,
can someone tell me where i can download the stock firmware to use oddin to reinstall the old firmware please
i updateed to M16
thanks

Mathew202 said:
so this afternoon i tried to install kitkat but it just kep failing,
can someone tell me where i can download the stock firmware to use oddin to reinstall the old firmware please
i updateed to M16
thanks
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/
:good:

Mathew202 said:
so this afternoon i tried to install kitkat but it just kep failing,
can someone tell me where i can download the stock firmware to use oddin to reinstall the old firmware please
i updateed to M16
thanks
Click to expand...
Click to collapse
You can't go back once you've gone through Kitkat upgrade, chances are even though it has failed it will still have upgraded your bootloader.. you have to re-flash KK again

i have been trying all afternoon to get this working but nothing, i have come close now to reflashing 20 times and still nothing.

ok so i cant even install CWM
im not to fussed about knox being tripped
this is wht i currently have on my screen
ODIN MODE
PRODUCT NAME: SM-N9005
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICAL
REACTIVATION LOCK: OFF
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLED (CSB)
RP SWREV: S2, T2, A2, A3< P2
WRITE PROTECTION: ENABLE
UDC START
can someone help me please. im pullin my hair out.
this is what i get from odin
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.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

Mathew202 said:
ok so i cant even install CWM
im not to fussed about knox being tripped
this is wht i currently have on my screen
ODIN MODE
PRODUCT NAME: SM-N9005
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICAL
REACTIVATION LOCK: OFF
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLED (CSB)
RP SWREV: S2, T2, A2, A3< P2
WRITE PROTECTION: ENABLE
UDC START
can someone help me please. im pullin my hair out.
Click to expand...
Click to collapse
At this point I believe you have 2 choices:
a) wait for 4.4.2 for your region - that might be the only way to keep knox 0x0
b) use the method described somewhere around here for Hong-Kong N9005 that were bricked with 4.4.2 - but that will make your knox 0x1

if you find the link can you post it please.
thanks

Use another usb port it happened to me with my n2
Sent from my GT-N7100 using XDA Premium 4 mobile app

Mathew202 said:
if you find the link can you post it please.
thanks
Click to expand...
Click to collapse
If you quote my post I get notified that you replied, if not I must guess it
Also this:
http://forum.xda-developers.com/showthread.php?t=2612190
but IMHO you should read around more before doing anything. And remember that you will have knox 0x1 = no warranty.

well ive just tripped knox
i have external insurance for my phone, worse case is i throw it down the stairs and claim on home insurance,

Someone can now close this thread.
i seem to have fixed my issue.
im a Mac user and i was using VMWare to emulate windows, i saw somewhere someone had put a thread up about not using it as its crap. so i installed bootcamp and the rom installed 1st time no problems,

[Q] GT-I9505 Problems after water damage repair.

First of all, I did some research, en noticed someone with the same problems. (http://forum.xda-developers.com/showthread.php?t=2707763)
He did not get an answer.
I cleaned the phone, and tried to boot.
- It hangs at spash screen. (so cant boot into android)
- can't go in recovery mode
- CAN GO IN DOWNLOAD MODE
- Is recognized by Odin
- Can flash images
- Device is not rooted
UPDATE:
-Tried to flash a rom on the device using downloadmode/ODIN
Rom version: I9505XXUFNC9-OXAFNB8-PRE-ROOTED-KNOX-FREE-ODEX-FULL
UPDATE2:
Tried original Vodafone rom wih original PIT file, does not work.
This is a phone bough in Holland with a Vodafone rom.
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> NON-HLOS.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> recovery.img
<ID:0/003> rpm.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> system.img.ext4
<ID:0/003> tz.mbn
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After this the device shuts down, and tries to boot into recovery mode (after manually restarting), wich hangs.
After this i tried rebooting via download mode. Again phone hangs at spash screen.
Can anyone provide me with a solution. I would like to be able to boot into recovery and/or flash a new rom (witch is not possible atm because of the device not being rooted)
If I forgot something. Ask me, and i'll update the start post with the info necessary.
Thanks in advance.

Can you add a pic of your "DOWNLOAD MODE" pls? Ty :highfive:
* Maybe?: You are flashing wrong firmware if you own a SGH-I337. You must flash this firmware via ODIN: HERE

galaxynote3update
com
/wp-content/
uploads/2013/10/
Samsung-Galaxy-Note-3-Download-Mode.jpg
It's not an actual photo of my device, but it looks the same as mine. ( i cant post picures yet, so mangled the link)

Addict_1337 said:
galaxynote3update
com
/wp-content/
uploads/2013/10/
Samsung-Galaxy-Note-3-Download-Mode.jpg
It's not an actual photo of my device, but it looks the same as mine. ( i cant post picures yet, so mangled the link)
Click to expand...
Click to collapse
Lol, ok. I need the info that appears in your DOWNLOAD MODE. The text. Write it pls :fingers-crossed:

Joku1981 said:
Lol, ok. I need the info that appears in your DOWNLOAD MODE. The text. Write it pls :fingers-crossed:
Click to expand...
Click to collapse
ODIN MODE: (in red)
PRODUCT NAME: GT--I9505
Current binary: Samsung official
system status: official
knox kernel lock: 0x0
knox warrenty void: 0x1 (been trying some roms)
csb-config-lsb: 0x30
Write protection: Enable
eMMC BURST MODE: Enable
I you need more info, let me know

Addict_1337 said:
ODIN MODE: (in red)
PRODUCT NAME: GT--I9505
Current binary: Samsung official
system status: official
knox kernel lock: 0x0
knox warrenty void: 0x1 (been trying some roms)
csb-config-lsb: 0x30
Write protection: Enable
eMMC BURST MODE: Enable
I you need more info, let me know
Click to expand...
Click to collapse
Try to flash THIS firmware normally (without .pit file). Like in the pic attached.

Samsung Galaxy S4 (I9500): Bricked After Trying To Install Custom Recovery

Hello.
I got a new Galaxy S4 (I9500) this October, and decided I would go ahead and install custom recovery on it. Me thinking I can get anything to work did not heed the warnings that this model does not support it go ahead and try anyway. After several failed attempts I find some software on the Play store that seems promising. Long story short, I no longer have a functioning recovery partition, and my phone will always try to boot into recovery mode unless I boot in Odin mode.
I have tried to follow several guides, most of which tell me the same thing:
Get Samsung drivers (not Kies)
Download Odin (one version or another)
Get the I9500 Firmware and install using Odin.
My phone is (from the sticker below the battery):
MODEL:GT-I9500
FCC ID: A3LGTI9500
SSN:-I9500GSMH
It is also factory unlocked.
I did notice however that the text in the top left when in Odin mode says it is a SGH-I337
The full text:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
I have tried flashing both 4.4.2 (as it was delivered with) and 5.0.1, but I get the same error:
<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> boot.img
<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)
The error that is displayed on the phone is:
SECURE MAGICCODE CHECK FAIL : boot
Any help would be greatly appreciated!
Edit: Added phone error

Note 4 Boot Loop - Tried KIES and Flashing Stock ROM - Still Looping

Hey ya'll, this past Saturday my Note 4 started a boot loop while using Baconreader. I was using stock ROM, unrooted, T-Mobile. I first deleted the cache partition, then did a factory reset, but neither worked.
I tried flashing with Odin v3.09, using ROMS from SamMobile:
4.4.4 ANK4
5.0.1 COD6
5.0.1 COG2
Each time I would get
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone in download mode was:
Odin Mode (High Speed)
Product Name: SM-N910T
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox Warranty Void: 0x0
Qualcomm Secureboot: Enable (CSB)
AP Swerv: S1, T1, R1, A2, P1
Secure Download: Enable
UDC Start
SW Rev Check Fail : [aboot]Fused 2 > Binary 1
[1]eMMC write fail: ABOOT
I then used the latest ROM from SamMobile, 6.0.1 EPE3, and everything worked. Odin flashed it and the installation was good. But as soon as it finished and booted for the first time the boot loop started again. I tried using KIES to do a emergency firmware restore but it would not pick up my Note 4 (Using a Samsung USB Cord) I tried it with and without Samsung USB Drivers installed. I'm starting to think it may be a hardware problem, honestly though I have no idea. I would like to get some other opinions before I send off for a new one. (No warranty over a year old) Thanks in advance, and sorry if the formatting is long, I figured it would be easier to read if everything was spaced out. Thanks in advance.