• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [AT&T] stuck

G

gueydejalisco

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 :)
 
gueydejalisco said:
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 :)
Click to expand...

find the stock ruu and flash back to original software
 
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
 
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?
 
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?
 
El Presidente said:
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.
Click to expand...

you took the words from my mouth before i could type them lol
 
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
 
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.
 
....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
 
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.
 
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.
 
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 :)
 
You must log in or register to reply here.
Back
Top Bottom