I tried following some guide online to get my S3 rooted and running stock Jelly Bean and all was going so well...Casual Root worked like a charm, cyanogen all set. But when I went to install the ROM and Gapps in recovery it kept getting hung up. I assumed this was due to encryption on the device from my work email, so I went back to factory andremoved the account and decrypted the device.
Then it was back to recovery to flash the ROM and Gapps. All seemed to go well,the ROM installed fine, Gapps installed fine, but reboot got stuck at the cyanagenmod loop. I had mad a backup of the original ROM, but I must have saved it to the internal SD card by accident before i factory wiped. I thought my best bet would be to load the Gapps and ROM onto my external SD and flash from there, but I cant get it to mount.
The one good thing that I can do is get to the Odin boot screen. Anyone think there's a chance I can get Odin to flash something that will boot? And does anyone have suggestions of what to flash?
Related
HELP!
I tried loading some ROMs on my Samsung Captivate and after a couple of successful attemps ( i just didnt like the look of them ) i tired another one and it didn't work. My phone would no longer fully boot. And after me screwing around for a while, everything on the internal sd card got erased and i no longer have any ROMs there to install. And now the phone wont startup and i cant see it on the computer.
Is there anyway I can install a ROM from either my ex sd card, or my computer and is there a way to put the ROM onto the phone.
Well since you wiped your SD card, your. update. zip for clockwork recovery is gone. So you wont be able to just go into recovery now and mount your SD card to add a new rom from pc or re-install one saved. If only you wouldn't have wiped the SD. Easiest way i can think of would be just go in downloadmode and flash back to stock, depending on your revisiion ( mine is 1008) I'd use the A10 toolbox/ captivate toolbox. It has everything you'll need. So.. stock, re-root ( either superoneclickroot or A10 toolbox ) get rom manager, flash clockwork, go into stock recov. And re install packages twice, put a rom. On your phone , back to recovery, install zip from SD.
Sent from SGS Captivate CM7 or MIUI with Escapist orTKGlitch using XDA premium app.
Try putting it into download mode (I forgot how to do it so google it). And then once your in download mode, download the original firmware onto your computer, and then use Odin to flash back to stock . This process has worked with my old Vibrant time and time again.
Hello, I'm new to the forums and I feel bad I'm already screwing things up :/
Anyway on to the problem... I've had CM9 running on my phone for about two weeks now but I wanted to get rid of the rainbows in CWM and at boot. Today I downloaded Rom Manager from the market place, and when I ran it, it prompted me to install CWM recovery to my SD card, although I already had it installed I thought I'd give it a try. Bad idea, now I can't leave recovery mode, my phone will continually reboot into recovery, I've tried wiping all data and clean installing CM9 again and still nothing. I've even tried the exitrecovery.zip script to no avail
Any suggestions or ideas on how to fix it and boot into my ROM again?
Thanks!!
I would venture to say you might have to reflash...or start over from stock...
i would reload stock....then reload ics or the rom of your choice...
Thanks a lot! Worked like a charm, I used Odin and flashed factory stock 2.2.1, now I'm off to getting ICS back.
Thanks again!
Does anyone know why this happens? I've noticed that anytime I open CWM and choose the boot to recovery option is when I get stuck with CWM Recovery looping. I then have to go back to stock and start over again.
I'm not entirely sure why it happens, my guess was that it puts up a bad flag not compatible with ICS that keeps it from booting that, that was why I tired the exitrecovery script, I looked through it and it appeared to me to change a flag for booting. I'm not sure why it happens but I'd say just use the reboot to recovery option that the ROM provides in the shutdown menu, I know that always works.
Hello all,
Last night I was trying to install the latest Gummy release on my Verizon Galaxy S3. This was the first time I have tried to flash a rom on this phone. It failed, and I rebooted my phone, and now it will only boot into the clockwork recovery.
I thought it may have been damaged as i was transferring the file to the device. I had an SD card in my droid X, So I put it in my Galaxy and formatted it with clockwork. Then I transferred the gummy release (that I also re-downloaded) from my computer to the SD card via a memory card reader. I put it in my Galaxy and tried to install the release, and it gave me a different error
Code:
E: Can't Open /external_sd/Gummy-2.1-01-09-14-NIGHTLY-d2vzw.zip
(bad)
Installation aborted.
Edit: Tried a few other roms and they had the same issue, but Cyanogen Mod 10.2 worked. Anybody have any guesses why?
Edit2: Further developments, Trying to do the latest nightly fir the CM yields the same issue that Gummy's release gave me initially. It reports as follows:
Code:
E: Error in /external_sd/cm-11-20140110NIGHTLY-d2vzw.zip
(Status 7)
Installation aborted
Is there possibly a firmware issue at play?
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
twistedillutions said:
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
Click to expand...
Click to collapse
Sorry, forgot to mention, I did unlock with EZunlock. Would the clockwork on the play store be the latest one, or is there another place with more up to date versions?
Cappurnikus said:
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
Click to expand...
Click to collapse
Do you get the same error on install that I'm getting, ro are the installs finishing, but not booting?
Try goo manager or ez-recovery to install the latest recovery
right now i can think of
factory reset format data. Make sure u backup ur internal
Wen changing from rom to rom is a good thing to do a clean install
get the right gapps.
The 1st boot always takes time at least on me.
Sorry i cant think of more helpful things.. Been drinking
Looks like my recovery just needed an update. Thanks everyone.
Sent from my Nexus 7 using Tapatalk
Confirmed also an old recovery for me as well. Thank you very much!
I started to install pacrom on my verizon galaxy s4 and am havings troubles. I'll start from the beginning.
I rooted the phone via Towelroot app and checked it with rootchecker.
Then i downloaded the following.
downloadandroidrom.com/file/GalaxyS4/SCH-i545/roms/PACMan/pac_jfltevzw-nightly-20130913.zip
downloadandroidrom.com/file/gapps/PA/pa_gapps-full-4.2-20130610-signed.zip
androidfilehost.com/?fid=95784891001603023 this is safestrap for "FOR USERS OF MJ7/MK2" IDK the difference between that and ME7/MI1 but i used MJ7/MK2
From here I opened up the safestrap app and installed the recovery and loaded it up. I left it on the stock rom slot while i continued to wipe everything and install the rom and GAPPS. This was a mistake, however, because i it bootlooped. I tried wiping and installing many different ways and still ended up with a bootloop. I realized in needed to use a rom slot and set that up. I wiped all the necessary things and installed the rom and GAPPS. Still it bootlooped. I have even tried to install without GAPPS with no avail. I forgot to make a backup of the stock and the stock slot just bootloops the pacrom boot screen. I cant find a way to add filed from my computer because whenever i connect it during the boot screen it shows up as a disc drive on my computer. Normally i would choose USB settings and make it where i can transefer data files, but i cant do this. I really need some help with this as I have done all I know to do. The downloads may be the problem, but from what i understand they are the correct ones. Thanks
Download this rom, move it to your phone and flash with recovery.
If you can't get the file on the phone I will help you out.
Long story short I was running latest nightly of cm13, I decided to flash to cm14 to try nougat. I had backups, during the process I pulled an idiot and wiped everything dalvik, system,data,internal storage,cache . So now I have no backups, I can still get into TWRP and attempt to flash Roms but I've tried countless ones and same outcome, TWRP just restarts half a second after it tries to flash, I've even tried the stock rom with no luck.it starts and gets to MTP enabled installing "name of rom" and then reboots . I've been using a tablet to install the Roms onto an sdcard and then using the sdcard to flash, I'm hoping it's an sdcard issue and I'm waiting to get the laptop to try and put the Roms on internal phone storage and try. I'm hoping I won't have to go back to unroofed stock using kdz tot. If anyone knows what's wrong please help.
Well I tried flashing to stock and can't get into download mode, computer won't recognize phone. So I decided to try updating Twrp flashed the image, rebooted and now I'm stuck on [11050] fast boot mode started. Nothing gets me out of that.