I have an MDK S4 with TWRP 2.6.3.1 and I have been flashing CM-11 nightlies about every week. Currently I'm on the 12/25 KK build and its working fine but I decided to update anyway. I made a backup and then proceeded to flash the 1/1/14 build however my S4 wouldnt go past the Samsung custom screen. I restored my backup and it worked fine. I proceded to flash a stock based ROM wiping everything and still it would not go past the Samsung Custom Boot screen. The only thing that works now is the build I have backed up nothing else boots. I have wiped data and evened ODIN'ed back to 4.2 MDK and rerooted and re TWRP'd and still I cant flash anything besides the one kitkat build I have backed up, any other ROMS dont go past the initial screen it just vibrates and shuts off and loads TWRP again. Any suggestions of what I can do to fix this?
Thanks in advance
Related
So was running an old version of PA 2.16 by Th3Bill and I kept having a problem where Apollo would crash. So I decided I was going to do a clean install of the newest version of PA 2.99 Final. Verify the MD5 and install with the guide on his page here: http://th3bill.com/?page_id=150
Making sure I have the proper CWM Recovery and Aroma Prep installed. At first it took the ROM, but it kept hanging a few seconds after boot and then rebooting infinitely. Tried doing a complete wipe and starting the process over. Now it CWM Recovery locks up and the screen glitches out during the ROM install at 40%. I tried the CM10 ROM it does the same thing. I tried to restore my backup of PA 2.16 and it took the files, but it just looped endlessly. Lastly I tried restoring a backup of a GB ROM and that booted and worked perfectly, but I'd prefer to get back on JB.
Anyone know what could be wrong and where I should start?
So up until today I was running this rom: http://forum.xda-developers.com/showthread.php?t=1912596
It was getting really buggy, so I decided to update to the latest CM10.1 nightly. I updated safestrap to the latest version, and I saw that on the changelog for the CM nightlies that the rom could be installed on any slot. For some reason, there was no rom slot 1, even though that's what I had the current rom installed on. I made a backup of the stock rom slot, wiped system/cache/factory reset, and installed CM 10.1 on the stock slot. That didn't boot up. So I tried to restore my backup. My backup of my current rom didn't show up, but the initial stock rom backup that I made when I first rooted the phone showed up, so i wiped everything again and tried to boot from that. On that, the boot animation showed up and went through, but it sat there for a few minutes without booting, so I did a hard reset and went back into recovery. I then made a romslot-1, wiped for precaution, then tried to install the cm nightly. The install went fine, but when I try to boot, the phone just vibrates initially like it's going to boot up, but there is no boot animation or anything on the screen, and it just sits there. Is there anything I can do to get this thing up and running again? I am not at the least opposed to returning it to stock, but I'm not sure if I need to restore to stock ICS or JB, since I'm pretty sure the rom I had running was using the ICS kernel. Here's the link to the rom I just tried to install: http://forum.xda-developers.com/showthread.php?p=39330661&highlight=boot#post39330661
Any help on the matter would be greatly appreciated.
I've been having a problem getting any 4.3 ROM to boot after the initial boot. I've seen a few other people with the same problem and I can't figure out a fix. Thought I'd ask the general Q&A.
I've used Beanstalk and Carbon (great ROMs) a few carbon 4.3 nightlies and Beanstalk 4.3.00. I installed their 4.3 builds (after checking sums to verify download) flash gapps, wipe cahce/dalvik and boot up. Set up goes great and rom runs great. but even without installing any other apps, using no backups or anything if I reboot it sticks on samsung screen and can't get past it. Every time, I even rebooted without finishing setup and wouldnt advance past samsung.
I even flashed 4.3 rom and gapps, let it reinstall apps from market then booted to recovery and made a backup. Then could'nt reboot. But if I wipe and restore the backup it will boot fine the 1 time, but again any attempts to reboot stick on samsung screen. Wiping cache/dalvik from recovery does not help, fix permissions from recovery does not help.
Anybody have this problem and find a fix?
Ok, I tried slim bean beta 2, no luck, tried ktoons kernel, no luck. Guess I'm staying with 4.2.2 until there is some movement on this issue.
What fixed it for me:
I had made a backup through TWRP 2.6.3.0, but then upgraded to 2.3.6.1 after. Not sure why it didn't work on 3.1, I flashed back to 2.6.3.0, flashed my backup, and everything works again.
So, I've been having one hell of a battle trying to get MJ9 and ROMs based off it to work in the last couple days. In the end, I have decided to go back to my Liquid ROM that I have a backup of yesterday morning in TWRP. This backup, until now, has served me well and has gotten my phone back to how it was.
Until now.
I wiped everything through TWRP and tried to recover my ROM image... Now when I boot, it's stuck at Samsung Galaxy Note 2 screen, and stays there indefinitely. I can boot to recovery if I pull the battery. How does this happen? I was recovering back to this backup just fine until now.
I've deleted system/cache/internal storage, flashed, then deleted cache, no luck.
I flashed Beans stock deodexed 4.3 image. That booted ok, but when I go back to recovery, my Liquid backup still will just hang at the Note 2 screen.
What can I do from here to get it working? Do I need to ODIN a pit file? I'm at a loss.
Hey guys, I kinda at my wits ends.
I have a Note 2 and I was running Sophisticated rom 3.1 just fine. I wanted to try Beans new Alliance 23 Rom. So I booted into TWRP 2.6.3.1 and backed up Sophisticated 3.1 first, then wiped everything and flashed Beans 23. Phone would not get past the boot animation. I tried to use the restore I had just created and TWRP fails. Tried upgrading TWRP to 2.6.3.2, didn't work, now any rom I try to install or recover from I get errors in TWRP saying too many files open and a second one about data/data/com.contacts. I tried Philz CWM recovery, I even tried downgrading back to TWRP 2.6.3.0 and nothing. I can not get a rom to boot past the boot animation. Please help. I have unlimited data and I can't go use an upgrade.
Dugall12 said:
Hey guys, I kinda at my wits ends.
I have a Note 2 and I was running Sophisticated rom 3.1 just fine. I wanted to try Beans new Alliance 23 Rom. So I booted into TWRP 2.6.3.1 and backed up Sophisticated 3.1 first, then wiped everything and flashed Beans 23. Phone would not get past the boot animation. I tried to use the restore I had just created and TWRP fails. Tried upgrading TWRP to 2.6.3.2, didn't work, now any rom I try to install or recover from I get errors in TWRP saying too many files open and a second one about data/data/com.contacts. I tried Philz CWM recovery, I even tried downgrading back to TWRP 2.6.3.0 and nothing. I can not get a rom to boot past the boot animation. Please help. I have unlimited data and I can't go use an upgrade.
Click to expand...
Click to collapse
I am using twrp 2.6.3.1. I would reflash the recovery. Then I would wipe everything except your external SD card. I have noticed that if I don't wipe my internal SD for awhile I will start having goofy stuff happen. That usually fixes any issues I have.
Sent from my SCH-I605 using Tapatalk
Yeah, I tried all that as well. Rehashed that version the new version and the older version then tried Phil's, tried wiping internal, external and still had errors. I had to bite the bullet and Odin back to stock 4.1.2 then jailbreak again and after a day lost I finally got it back up. I'm leaving TWRP 2.5 on it
Sent from my SCH-I605 using xda app-developers app