iPhone Bootlogo not working iPhone 6+

Discussion in 'Jailbreaks and iOS Hacks' started by Enigmafan420, Feb 10, 2015.

  1. Enigmafan420 macrumors 6502a

    Enigmafan420

    Joined:
    Apr 18, 2008
    Location:
    Puget Sound, U.S.A.
    #1
    I cannot get bootlogos to work on my iPhone 6+. Installed animate for 8.0 prior to installing any logos, and have tried at least a half dozen. They all work in preview but all I see are "wavy line" on reboot.

    Not that it should matter but, iPhone 6+, 64 GB, ATT/GSM, not the "bad/slow" memory.

    Anyone with a similar phone getting these to work? Would love some suggestions.

    Thanks!
     
  2. Enigmafan420 thread starter macrumors 6502a

    Enigmafan420

    Joined:
    Apr 18, 2008
    Location:
    Puget Sound, U.S.A.
    #2
    Anybody out there have bootlogos working correctly on iPhone 6 +?
     
  3. Johnnymarks18 macrumors newbie

    Joined:
    Dec 27, 2012
    #3
    I have the same issue. Someone stated that it could be the type of flash storage the phone has (I don't know if that's what you mean by "bad/slow" memory. They are essentially the same in comparison other than the code used to access them). There are two types. The new MLC memory and the old TLC NAND memory. To check, go to Cydia and see if you have the MLC version by installing terminal and iokit tools and running the command ioreg -lw0|grep “Device Characteristics” Look for the string default-bits-per-cell and if it equals 2 you have MLC and if it equals 3 than it is TLC. Unfortunately I have the new MLC type and still have the problem, which means it's something else. It is expected to not work if your memory type is TLC NAND. I wish someone could help! I can't find anything on this topic!
     
  4. Enigmafan420 thread starter macrumors 6502a

    Enigmafan420

    Joined:
    Apr 18, 2008
    Location:
    Puget Sound, U.S.A.
    #4
    I also have the "new" MLC memory. Glad it took a while to get my phone :)

    Anyway so yes it is not a memory problem but is very frustrating and there seems to be almost NO info about this problem on the web.
     

Share This Page