Hello,
I was running the stock ROM, but decided to flash the Energy ROM. I first flashed the JB.4.2.1.Bootloader.and.partitions.zip and then the new ROM. However it just got stuck at the ASUS splash screen. After several unsuccessful attempts I flashed the JB.4.1.1.Bootloader.and.partitions.zip and restored by backup, only for it get stuck in the ASUS splash screen again. I tried to flash the stock 4.1.1 from ASUS, but it fails every time along with any other custom 4.1.1 ROMs I try!
Can anyone help me? I can have still access to fastboot and TWRP. I have been searching these forums for days with no luck.
Edit: the only time I've gotten past the splash screen is if i flash the JB.4.2.1.Bootloader.and.partitions.zip then restore my stock 4.1.1 backup, but then it just hangs in the boot animation. I tried hen to flash the 4.1.1 stock over it only for TWRP to say it has failed.
is your boot loader unlocked ?
careful with TWRP and the JB 4.2.1 bootloader. You can only use the custom TWRP specifically made for the JB 4.2.1 bootloader.
I'm new to this forum and find the i717 a wee bit more complicated than my old phone. (a Galaxy S 4g.)
I've managed to get CWM touch 5.5.0.4 on the phone and have successfully flashed the deodexed stock jelly bean rom. However when I try to flash any of the "quincy.att" based rom, CWM gives me an error, which I imagine means that I need a more recent CWM. Before I flashed stock jelly bean, I was able to get the 6.0.3.6 quincy.att CWM on the phone using the terminal but when I tried using it, it did not see the external sdcard and I could not get there to flash any rom. I tried using ODIN to flash CWM 5.8.4.3 but ODIN just sat there and nothing got loaded onto the phone at all.
So it is kind of a chicken and egg situation here. What is the minimum version of CWM I need to flash any of the quincy.att roms and how do I get it on there and working? Or am I supposed to use TWRP? I haven't tried that. I remember it from the 4g and it was a pain to use on that phone. I have tried to flash the 10.1 quincy.att plain Cyanogen and the chameleon rom and I just get error messages from CWM,
Just use twrp.....your probably getting error 7 ...install twrp
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
TWRP is piece of cake here. you will never look back
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
longhairdaddy said:
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
Click to expand...
Click to collapse
If 6.0.4.3 touch works "fine", why don't you just use that?
veningTrMarchal
tube517 said:
If 6.0.4.3 touch works "fine", why don't you just use that?
Click to expand...
Click to collapse
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
longhairdaddy said:
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
Click to expand...
Click to collapse
Try CM11 for KitKat. It's very stable.
tube517 said:
Try CM11 for KitKat. It's very stable.
Click to expand...
Click to collapse
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
longhairdaddy said:
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
Click to expand...
Click to collapse
I had the same issues with 4.4 kitkat roms. Did you format system in CWM when wiping? This solved my bootloop issues. Also, make sure you have a clean download of the ROM. Flash the ROM twice back to back when flashing a new kitkat rom
I have a HTC One from T-mobile and it is currently stuck on a GPE rom I got from HTConeroot.com - m7_GPe_JWR66V_deodexed-signed.zip. I tried to upgrade to android kitkat 4.4 using the same website I mentioned earlier and followed directions to install rom manager so I could get CWM recovery instead of TWRP. I flashed CWM 6.0.3.1 and then rebooted into recovery to flash the latest 4.4 ROM but the flash failed. I had a backup at the time to stock Sense but somehow deleted it out of frustration. The phone then became bricked. I sideloaded the above mentioned GPE rom w/4.3 and now I'm stuck here. I have a Dell Windows 8.1 computer and can no longer use fastboot to flash any other recoveries. Rom manager says it has flashed TWRP but when I reboot it is still CWM 6.0.3.1. Does anyone have any suggestions on how to flash a different recovery or a different rom????
Hey guys,
I recently flashed a new 4.3 rom to my S3 (Imperium 21.0).
After a while i decided to update the kernel to Googy Max, downloaded it from OTA and went to install it via TWRP, after installing the galaxy decided it wouldn't boot and just returned to the recovery all the time, i thought it must be the broken kernel and re-flashed the rom, everything was fine until i went back to the recovery (to backup the rom), after i finished backup and tried to restart my S3 the same happens, the galaxy just reboots back to the recovery, and the only way i found to get of it is to re-flash the rom :/
I don't want to re-flash it again... Any ideas what can i do?
fr0z1k said:
Hey guys,
I recently flashed a new 4.3 rom to my S3 (Imperium 21.0).
After a while i decided to update the kernel to Googy Max, downloaded it from OTA and went to install it via TWRP, after installing the galaxy decided it wouldn't boot and just returned to the recovery all the time, i thought it must be the broken kernel and re-flashed the rom, everything was fine until i went back to the recovery (to backup the rom), after i finished backup and tried to restart my S3 the same happens, the galaxy just reboots back to the recovery, and the only way i found to get of it is to re-flash the rom :/
I don't want to re-flash it again... Any ideas what can i do?
Click to expand...
Click to collapse
Can close thread, after installing another recovery via Odin it was fixed
Mid year I decided to root and flash Cm 11 onto my little s3 mini (gt-i8190) and everything went great. Recently I read on the Novafusion website that they recommend using TWRP instead of CWM, searched on Google and saw it was safe to flash over custom recoveries. I used Odin to flash over the TWRP I downloaded from the Novafusion site. When odin completed its process my phone rebooted into TWRP and it all seemed fine, then I proceeded to flash the latest version of the Cm 11 4.4.4 rom. Again everything went great and my phone booted up normally.
I got the zip file for the Android L keyboard and I used Rom manager to reboot into recovery and showed the "Samsung Galaxy sIII mini gt-i8190 screen and just went black for 10 seconds, rebooted and continued going black then rebooting. I pulled the battery out and booted up my phone again then used rom manager to flash CWM again and it worked! I used CWM to flash the keyboard apk and it worked.
I was a little bit worried about the recovery bootloop and decided to make a nandroid backup. I couldnt reboot into recovery, manual way or with Rom manager.
I have used odin to flash CWM and TWRP a few times now without any luck. My phone just reboots normally when odin finishes.
If anyone could shed some light on this issue I would be grateful.
Thank you.