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.
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?
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
BigBoy275 said:
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
Click to expand...
Click to collapse
First time installing CyanogenMod 10.2 to your Galaxy Note 2 I605, or coming from another ROM:
- Read known issues ans FAQs
- Flash the latest official ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
read the OP for CM 10.2 next time....
First - clockworkmod not twrp for 4.3 usually fixes things
Second - do a factory reset AFTER installing
Third - Dont restore apps with TiBu going to 4.3
Next time be truthful when you say you read and searched.
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
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Hi,
I rooted my phone back in August. I made a backup of the rooted device. I have reset it numerous times. This time it will not work. I started without gapps the first time. I re-did the backup and did gapps but my phone is stuck on android is upgrading after it optimizes apps. I have Philz touch Clock work. I also have liquid smooth but it doesn't appear when I reboot. I have the liquid smooth file on my sd so i can install ls zip and then gapps and the phone will boot up so my phone is on on. The setup wizard fails and I cant access anything. I've tried different gapps 5.1 4.4.2(orignal one), 4.4.3 not compatible. I'm assuming i didn't brick it because it does start and go to myregular phone display.I don't know if something was updated with samsung which made my backup or gapps not work correctly. Any help would be greatly appreciated. I have wiped rom, davlik, cache, installed backup...same process install liquid smooth first. Ive done my backup without gapps and it starts but all apps fail because no gapps.