• Welcome to the all-new Android Central Forums! - We're still moving some things around, so you may see a few quirks here and there, but we're working on getting things fully completed as soon as possible. For now, take a look around, and if you run into any major issues, please let us know in this thread!

Problem since installing KitKat test build

peejay1977

New member
Mar 26, 2010
207
0
0
Hey all, I realise this is largely my own fault but I have encountered an issue with reverting to stock since I installed the leaked test build of Samsungs KitKat ROM.

I flashed the ROM as described here :

I9505XXUFNA5 Android 4.4.2 KitKat Test Firmware for Galaxy S4 Leaked

All worked fine except the CSC code was changed from VOD (Vodafone UK) to DBT. Once the ROM was installed I was able to change the CSC code to BTU for United Kingdom and the ROM worked without issues. I then noticed though that the external SD card wasn't showing properly in file explorers other than Samsung's own and some apps such as PowerAmp show the card as "unmounted" even though it IS reading the contents.

This prompted me to revert back to stock. I had CyanogenMod 11 installed before I updated to the test build in case it's relevant.

I have switched between stock 4.3 and CM11 a number of times without issue but this time when flashing the stock ROM with Odin I get a failure when it gets to ABOOT.MBN and a mention of AUTH fail.

No attempts to correct this have worked so I have put CM11 back on but just wondered if anyone has encountered this and knows of a way round it. I have flashed a PIT file as suggested on some XDA threads.

Many Thanks



Paul.
 

Kelly Burby

Banned
Nov 26, 2013
693
0
0
Hey all, I realise this is largely my own fault but I have encountered an issue with reverting to stock since I installed the leaked test build of Samsungs KitKat ROM.

I flashed the ROM as described here :

I9505XXUFNA5 Android 4.4.2 KitKat Test Firmware for Galaxy S4 Leaked

All worked fine except the CSC code was changed from VOD (Vodafone UK) to DBT. Once the ROM was installed I was able to change the CSC code to BTU for United Kingdom and the ROM worked without issues. I then noticed though that the external SD card wasn't showing properly in file explorers other than Samsung's own and some apps such as PowerAmp show the card as "unmounted" even though it IS reading the contents.

This prompted me to revert back to stock. I had CyanogenMod 11 installed before I updated to the test build in case it's relevant.

I have switched between stock 4.3 and CM11 a number of times without issue but this time when flashing the stock ROM with Odin I get a failure when it gets to ABOOT.MBN and a mention of AUTH fail.

No attempts to correct this have worked so I have put CM11 back on but just wondered if anyone has encountered this and knows of a way round it. I have flashed a PIT file as suggested on some XDA threads.

Many Thanks



Paul.

This is completely normal as these ROMs are not stable, these ROMs are not good for the users, these ROMs are used by the developers. Now I guess in order to get everything back on track you need to factory reset your device.
 

tech_head

Q&A Team
Aug 25, 2010
783
15
0
Looks like you might have been bitten.
They may have slid a signed bootloader in there.
The authorization failure in aboot is a red flag.

Have you tried a different USB port or computer?
I suspect the signed bootloader though.
 

peejay1977

New member
Mar 26, 2010
207
0
0
Looks like you might have been bitten.
They may have slid a signed bootloader in there.
The authorization failure in aboot is a red flag.

Have you tried a different USB port or computer?
I suspect the signed bootloader though.

I think you're right, it always fails at the ABOOT.MBN regardless of what PC I use or port. I am going with the bootloader even though the stock 4.3 ROM has a bootloader I extracted just the bootloader and tried to flash that and get the same issue.

I'd stick with the test build but external SD card support isnt working properly which kind of negates the usefulness of it for me. I've gone back to CM11 for now until the official release comes out.