Welcome to the Android Central Forums Create Your Account or Ask a Question Answers in 5 minutes - no registration required!
Results 1 to 5 of 5
  1. Thread Author  Thread Author    #1  

    Default Problem since installing KitKat test build

    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.
  2. #2  
    Kelly Burby's Avatar
    Banned

    Posts
    702 Posts
    Global Posts
    706 Global Posts

    Default Re: Problem since installing KitKat test build

    Quote Originally Posted by peejay1977 View Post
    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.
  3. Thread Author  Thread Author    #3  

    Default Re: Problem since installing KitKat test build

    Already done that, but no change I'm afraid. Thanks for the help though.
  4. #4  

    Default Re: Problem since installing KitKat test build

    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.
  5. Thread Author  Thread Author    #5  

    Default Re: Problem since installing KitKat test build

    Quote Originally Posted by tech_head View Post
    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.

Similar Threads

  1. Replies: 4
    Last Post: 01-30-2014, 02:57 PM
  2. Problems with my battery
    By dsl4life in forum Google Nexus 4
    Replies: 5
    Last Post: 01-22-2014, 05:53 PM
  3. Avi problem
    By Livorno99 in forum Samsung Galaxy S4 Mini
    Replies: 2
    Last Post: 01-22-2014, 08:19 AM
  4. I think I may have found a problem on my Nexus 7 2013 :(
    By Sassi666 in forum Google Nexus 7 Tablet (2013)
    Replies: 1
    Last Post: 01-22-2014, 01:03 AM
  5. Group text problem downloading
    By ohsnapsitsLE in forum T-Mobile Samsung Galaxy S4
    Replies: 0
    Last Post: 01-21-2014, 08:16 PM

Posting Permissions