iRecovery commands? - Stuck in recovery mode

Discussion in 'Jailbreaks and iOS Hacks' started by eleven7, Nov 17, 2009.

  1. eleven7 macrumors regular

    Joined:
    Mar 14, 2009
    Location:
    Japan
    #1
    Almost all tutorials online telling you how to get your phone out of recovery mode by using iRecovery say to use the command printenv to check the value of auto-boot boolean. The problem is, whenever I use the command, nothing happens, it just returns to the prompt. It's the same as for the other commands I type e.g.

    setenv auto-boot true
    saveenv
    fsboot

    None of them gives any visual response, they all just return to the prompt so I'm not sure if they are doing anything. Can anyone see if I am doing something wrong? Am I miss a switch or something?

    The only command that seems to do anything is "reboot" which isn't much help as it does just that, reboots into the previous, stuck on apple logo state.
     

    Attached Files:

  2. millsg macrumors newbie

    Joined:
    Nov 19, 2009
    #2
    Same here

    I have exactly the same problem! Can anyone shed some light on this please?
     
  3. millsg macrumors newbie

    Joined:
    Nov 19, 2009
    #3
    Ok, I've made some progress. I restored using an older version of the firmware, and now my printenv command is working... Will try the rest of the sequence now.

    The firmware version I restored with was iPhone1,2_3.0_7A341_Restore
     
  4. arickdm macrumors newbie

    Joined:
    Jan 18, 2010
    #4
    i am having trouble. im stuck with usb cable and itunes logo on my screen.

    i believe it was 3.0 and it is a 3g if that matters. i have tried restoring to 3.1.2 and 3.0 and always get error 28

    anyone have any ideas?
     
  5. dhlizard macrumors G4

    dhlizard

    Joined:
    Mar 16, 2009
    Location:
    The Jailbreak Community
    #5
    Start up iTunes, hold down the home button while plugging in the phone cable. Keep holding the home button until iTunes pops up a message saying it has detected a phone needing restore. Release the home button and try to restore it.
     
  6. arickdm macrumors newbie

    Joined:
    Jan 18, 2010
    #6
    that didnt seem to work. still got the same error
     
  7. -aggie- macrumors P6

    -aggie-

    Joined:
    Jun 19, 2009
    Location:
    Where bunnies are welcome.
    #7
  8. arickdm macrumors newbie

    Joined:
    Jan 18, 2010
    #8
    i have tried in DFU mode many times as well

    also this phone was jailbroken and unlocked at 3.0 before this happened. its my friends and i guess some water got on it somehow and the backlight wasnt working. he was trying to reset it but ended up going into recovery mode. when i first got it from him to try and fix the backlight was working just fine. i have tried some stuff with irecovery, redsn0w, and balckra1n and still nothing
     
  9. -aggie- macrumors P6

    -aggie-

    Joined:
    Jun 19, 2009
    Location:
    Where bunnies are welcome.
    #9
    You should've mentioned the water damage in the beginning. Probably nothing you can do, but use an out of warranty replacement option for $199.
     
  10. arickdm macrumors newbie

    Joined:
    Jan 18, 2010
    #10
    well im not sure if there really is water damage or not. its possible it didnt get into the phone. it was only on the back of it
     
  11. thelatinist macrumors 603

    thelatinist

    Joined:
    Aug 15, 2009
    Location:
    Connecticut, USA
    #11
    Why the hell didn't you mention that your phone was water damaged before? Good grief.
     
  12. dhlizard macrumors G4

    dhlizard

    Joined:
    Mar 16, 2009
    Location:
    The Jailbreak Community
    #12
    Looks like enough water likely got in to stop the backlight function and keep the phone from re-booting.
     
  13. arickdm macrumors newbie

    Joined:
    Jan 18, 2010
    #13
    the backlight works now and it does reboot. its just stuck in recovery
     
  14. straff-attack macrumors newbie

    Joined:
    Feb 24, 2010
    #14
    iRecovery Message Meanings

    I've tried every suggestion from all over the internet.
    I have a 3G iPhone, stuck in recovery mode with the "connect to iTunes" logo and usb cable.

    Some facts:
    - It wont go into DFU mode (I've done it a million times before), it just restarts.
    - When I try to restore in iTunes, I get an error 9 every time (I've gotten a couple others, but 99% of the time it's "9")
    - I have tried several different firmware versions - I'm not sure the last working version that was on it; it came to me this way.
    - there's no apparent water damage - stickers are still white.
    - the only thing I can get it to do in iRecovery is reboot.

    I was hoping somebody could make some sense of my iRecovery Terminal log. Maybe something in here will tell me what's wrong?

    Any help is appreciated...

    =======================================
    ::
    :: iRain for n82ap, Copyright 2009, Apple Inc.
    ::
    :: BUILD_TAG: iBoot-636.66
    ::
    :: BUILD_STYLE: RELEASE
    ::
    :: USB_SERIAL_NUMBER: CPID:8900 CPRV:30 CPFM:03 SCEP:05 BDID:04 ECID:00000341AC05CD8E IBFL:01 SRNM:[5K9244Y61R4]
    ::
    =======================================

    [FTL:MSG] Apple NAND Driver (AND) RO
    [NAND] Device ID 0xb655d7ec
    [NAND] BANKS_TOTAL 4
    [NAND] BLOCKS_PER_BANK 8192
    [NAND] PAGES_PER_BANK 1048576
    [NAND] SECTORS_PER_PAGE 8
    [NAND] BYTES_PER_SPARE 128
    [FTL:MSG] FIL_Init [OK]
    [FTL:MSG] BUF_Init [OK]
    [FTL:MSG] FPart Init [OK]
    read old style signature 0x43303035 (line:371)
    [FTL:MSG] VFL Register [OK]
    [FTL:MSG] VFL Init [OK]
    [FTL:MSG] VFL_Open [OK]
    [FTL:MSG] FTL Register [OK]
    [FTL:WRN] Failure running _LoadFTLCxt!
    [FTL:WRN] Recovering NAND Data Structures - this will take some time!
    [FTL:WRN] _FTLRestore OK!
    [FTL:SG] FTL_Open [OK]
    Boot Failure Count: 0 Panic Fail Count: 5
    Entering recovery mode, starting command prompt
    (Recovery) iPhone$
     
  15. darkfader macrumors newbie

    Joined:
    Feb 6, 2008
    #15
    Another iPhone adds to the list... (3.1.2 3GS)
    It seems like it started with crashes sometimes when starting an app from the springboard. Garbage on the screen and then automatically reboots.
    I guess after a few times, this was too much and would not boot anymore.
    It stays on the apple logo for a very long time (full NAND R/O restore & fsck on boot volume). After another unexplainable delay (after the AppleBCMWLAN stuff), a very long list of crash data scrolls by and the iPhone reboots itself again. Too bad it scrolls so fast that it's not readable.

    Without much success, I've tried redsn0w (3.1.2 with boot log enabled) and iRecovery to try getting it booting without wiping my data.
    The first time I start iRecovery, it shows this:

    [FTL:MSG] Apple NAND Driver (AND) RO
    [NAND] Found Chip ID 0x3295DE987A on FMI0:CE0
    [NAND] Found Chip ID 0x3295DE987A on FMI0:CE1
    [NAND] Found Chip ID 0x3295DE987A on FMI1:C8
    [NAND] Found Chip ID 0x3295DE987A on FMI1:CE9
    [FTL:MSG] FIL_Init [OK]
    [FTL:MSG] BUF_Init [OK]
    [FTL:MSG] FPart Init [OK]
    read new style signature 0x43313133 (line:375)
    [FTL:MSG] VSVFL Register [OK]
    [FTL:MSG] VFL Init [OK]
    [FTL:MSG] VFL_Open [OK]
    [FTL:MSG] YAFTL Register [OK]
    yaFTL::YAFTL_Open(l:2630): CXT is not valid . Performing full NAND R/O restore ...
    [FTL:MSG] FTL_Open [OK]
    Boot Failure Count: 15 Panic Fail Cont: 0
    Entering recovery mode, starting command prompt

    The Boot Failure Count seems pretty constant each time I look.
    iRecovery does not show any response to my commands but seems to take at least the reboot command. Perhaps someone thought it would be nice to disable the output.
    At this point, I might still try a different firmware version with redsn0w. It would be nice to know where it went wrong though.

    [edit]given up already. shift-restore it is... cannot live without working iPhone hehe[/edit]
     
  16. baseman101, Jan 10, 2011
    Last edited: Jan 10, 2011

    baseman101 macrumors newbie

    Joined:
    Jun 13, 2010
    #16
    Solved!

    Hello,
    Your iPhone is, in fact following the commands in CMD or Terminal. It uses the program libusb to actually link to a device in the USB outlet. Instead of seeing the error messages or anything, the commands input into your iPhone. However, some current apple devices, are not compatible with the commands. Some people, who are in recovery will have to restore. YOU SHOULD ALWAYS BACKUP BEFORE ATTEMPTING TO GET IN DFU MODE!
     

Share This Page