[AT&T] stuck


Last Updated: 2012-10-28 01:03:18
  1. gueydejalisco

    gueydejalisco Well-Known Member

    ok so i succsesfully unlocked and rooted my phone it all went perfictly so the i i was flashing the aokp jb nightlys and it bootloped when trying to fix it it would get stuck at android upgrading so i was reading a few topics on diffrent forums about similiar issues sense i cant seem to find my exact problem anyways i found this one topic that said to do a factory reset sooo...i think this was the mistake i formated it from the bootloader...anyways now cwm says E:cant mount \sdcard\.....and i dont know what to do i looked everywhere could someone please help me it would be much appriciated :)

    Advertisement
  2. El Presidente

    El Presidente Beware The Milky Pirate! Moderator

    Which version do you have, the AT&T/Rogers (Snapdragon 4) variant of the Tegra 3, International version?
    scotty85 likes this.
  3. KJohns

    KJohns ROM/Application Developer Developer

    find the stock ruu and flash back to original software
  4. gueydejalisco

    gueydejalisco Well-Known Member

    at&t s4 and im trying to flash the ruu right now the boot_signd.img is fine the sytsem.img wont do anything it just says C:\android>fastboot flash system system.img
    sending 'system' (1048572 KB)...
    FAILED (remote: data length is too large)
    finished. total time: 0.006s and i have no idea what to do and the phone wont charge on cwm either so i think i have a limited amount of time
  5. gueydejalisco

    gueydejalisco Well-Known Member

    ugh im freaking out i have no clue what to do i have about a million tabs open and not oone is helping im thinking the RUU will fix it the only thing is i cant get the system.img to flash what should i do?
  6. El Presidente

    El Presidente Beware The Milky Pirate! Moderator

    The no charging thing was an issue on previous versions of CWM (for the International version, if you're getting the same problem, I presume on the S4 variant too). Install an updated version of CWM, or go with something like TWRP. Charge it up then.

    Don't try anything fancy with the RUU either, plug for phone into the PC, boot to fastboot, then run the RUU.exe.

    You could always just restore your backup too?
    scotty85 likes this.
  7. KJohns

    KJohns ROM/Application Developer Developer

    you took the words from my mouth before i could type them lol
    scotty85 likes this.
  8. gueydejalisco

    gueydejalisco Well-Known Member

    C:\android>fastboot flash recovery openrecovery-twrp-2.1.7-evita.img
    error: cannot load 'openrecovery-twrp-2.1.7-evita.img'

    i must be doing somthing wrong when trying to flash twrp
  9. El Presidente

    El Presidente Beware The Milky Pirate! Moderator

    I've found that if the recovery name is long like that, I get the same sort of error message. Change the filename to something like recovery, or TWRP and see if that works.
    scotty85 likes this.
  10. gueydejalisco

    gueydejalisco Well-Known Member

    ugh all its saying is that it cannot load the .img file
  11. gueydejalisco

    gueydejalisco Well-Known Member

    i did i changed it to twrp, recovery, stock nothing works it just says

    C:\android>fastboot flash recovery recovery.img
    error: cannot load 'recovery.img'
    scotty85 likes this.
  12. El Presidente

    El Presidente Beware The Milky Pirate! Moderator

    Are you definitely in fastboot, not hboot? Does it say Fastboot USB about a 3rdof the way down the screen?
    scotty85 likes this.
  13. gueydejalisco

    gueydejalisco Well-Known Member

    yes i am fastboot highlighted in red
  14. El Presidente

    El Presidente Beware The Milky Pirate! Moderator

    Ok, can you restore the nandroid you took before flashing AOKP?
  15. gueydejalisco

    gueydejalisco Well-Known Member

    ....yea thats the thing..i never made a backup..dont ask why i wasnt thinking also i cant really flash anything from cwm because i cant acsses the sd card...sigh i shoulda never flashed that stupid rom...the unlock and root were smooth as butter it was the rom
  16. gueydejalisco

    gueydejalisco Well-Known Member

    wait is there anyway i can manuelly flash a nandroid backup?
  17. geewhiz

    geewhiz Well-Known Member

    It sounds more like your Recovery is fubar and not the rom.

    I've only read of flashing a nandroid from your SD card in recovery.
  18. gueydejalisco

    gueydejalisco Well-Known Member

    is there anyway to fix it? or is it good as brickd???
  19. El Presidente

    El Presidente Beware The Milky Pirate! Moderator

    Do you have the correct RUU? Just relock your bootloader, run the exe file and don't try to do anything with the img files it contains.

    Do you have any way of telling how much battery you have left? If it's below 30%, the RUU won't flash.
    scotty85 likes this.
  20. El Presidente

    El Presidente Beware The Milky Pirate! Moderator

    Is your bootloader still unlocked? Could that be the reason you got the error messages when you tried to flash the recovery.
  21. gueydejalisco

    gueydejalisco Well-Known Member

    ok fixed it a houre ago thanks for all your help i did as you said relocked the bootloader and reran the ruu and viola lol but yea thank you guys:D
    scotty85 likes this.
  22. El Presidente

    El Presidente Beware The Milky Pirate! Moderator

    Good stuff! Next time you try, remember and take a backup before flashing anything. :)
    scotty85 likes this.
  23. gueydejalisco

    gueydejalisco Well-Known Member

    oh dont worry i did and atleast i know what to do if worst comes to worst
    scotty85 likes this.
  24. geewhiz

    geewhiz Well-Known Member

    :beer:
    scotty85 likes this.
  25. scotty85

    scotty85 Guides Guide

    its next to impossible to brick an s-on,unlocked device with software flashes of system or boot,htcdev unlock is extremely safe since it is protecting the bootloader and radios.

    when you have trouble,you should always be able to relock and run an ruu. :)

    you can re-unlock with your original token,and try again. as was said,this time make a backup ;)

    if youre on software 2.20.502.7,make sure you understand how to flash the boot image seperately,as the newest hboot is preventing recovery from installing the kernel. you also should try to launch your recovery into memory,rather than booting to is with the command: fastboot boot recoveryname.img on other devices,this lets the kernel flash,just like an s-off device,defiantely simplifying the install process :)

    not sure why you were having trouble installing twrp... thats the recovery i run on mine,not being fan of clockwork. did you have the image inside the same folder with adb/fastboot? it wasn an .img file correct,not a .zip or .nbh,or some other type of file?

    technically,you can install things a PxxxIMG files,but i personally avoid that when s-on unlocked,as the phone is still doing checks and the android info text document info comes into play,and makes it a PITA

    just holler if you have any questions :)

Share This Page