I tried flashing a nightly of CM12 on my M919 after no problems for almost 2 weeks. After flashing, my phone was stuck in boot with the CM logo. I tried flashing previous versions of the rom wiping and clearing each time. All I got was the CM logo. I finally decided to start from scratch and reinstalled stock(4.4.4) with ODIN 3.07. Phone booted right up. Rooted the phone with CF-Auto-Root (KTU84P.M919UVUFNH7) with no problems. Ran it for the day to make sure no issues. After feeling comfortable, I downloaded and tried flashing CM11 Snapshot M12 since it's based off 4.4.4. Boot loop again. I tried CM12 with the same results. I'm using CWMR 6.0.4.7. I've tried newer versions of both CWMR and TWRP(I don't remember what versions they were). I'd like to go back to using 5.0, if possible. I'm not sure if I've missed a step in rooting, since it's been so long that I rooted/flashed this phone. Right now it's running stock 4.4.4/M919UVUFNK2 and rooted. Any suggestions as to what I could try?
That nightly may have borked some files causing a problem, the nightlies are usually full of warnings about possibly causing boot loops or lockups and always recommend a nandroid b/u before flashing.
A nightly is a way of trying something out on other people's phones to see if it works well enough to add it as an update to the regular rom build.
If your that desperate for a nightly you need to follow the thread for a couple of days and see how others do with it.
If all you see is "I flashed the nightly and boot loops all over the place, don't bother, otherwise you find yourself in this thread.
Try a factory reset and flashing again,
also get a newer CWM recovery 6051 (if not mistaken) but stay away from the nightlies.
If you really need a reliable phone that works all the time and doesn't windup dead, just keep your stock rooted rom. And lollipop will be here soon as an update, probably by mid-march, the you'll have all the lollipops you want.
Pp.
Related
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
chirantan.f said:
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
Click to expand...
Click to collapse
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
i would also like to note here that i tried installing AOSP based ROMs also, and AOKP didnt work, got stuck at nexus like boot animation forever, but when i tried installing CM10.1.2 (which is what i was running when i tried to get back to TW based ROM) it worked perfectly, so for now i am back to CM, but i would really get back to flashing different ROMs and trying them out. just makes me wonder if CM is the reason i am not able to install anything else, just a thought...
has anybody else tried going to any other ROMs from CM 10.1.2?
your help is appreciated!
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
Click to expand...
Click to collapse
thanks for your reply, but i have tried doing that, i also wipe data and system along with cache and dalvik before installing any new ROM.
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
Click to expand...
Click to collapse
i have latest recovery , TWRP 2.6.0.0 and i have given more than an hour to boot up and still nothing. i have been flashing ROMs like an addict since i got this phone last year, but when CM 10.1 stable was released i stayed on it till today, but now i cannot install any other ROM, i can odin to stock 4.1.1 ROM or install cm 10.1.2 which i did just now, but no other ROM, either TW based on AOSP based is working...which is very weird for me.
Were you able to fix this issue at all? I am facing the same issue, in my case, the phone was encrypted on stock TW. I roooted and put in CM 10.1.2 and now when I try installing Dandroid, the install itself would work but I am struck at the "type password to unlock the screen". If I reflash CM10.1.2, I can login fine. Any pointers?
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
captican said:
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
Click to expand...
Click to collapse
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
I had the same problem since 4.3 came out. It has to do with partition tables... What i've done to correct the problem:
- Odin back to stock
- Format entire phone. (Complete wipe) + Dalvik and cache
- Odin stock with root
- Replaced TWRP recovery for CWM
- Flashed 4.3 ROM and VOILA
- I have tried every 4.3 rom ever since with no problems
Don't (Complete wipe) with Twrp recovery, it seems to mess up the partitions.
Hope this works for you
Cheers
danielhep said:
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
Click to expand...
Click to collapse
It loaded the first time and then rebooted, freezing on the kernel screen. I could get into recovery, and restore a previous ROM but it would hang up on 4.3. I described the steps I had taken when someone suggested reformatting data. I tried again and it is working now.
The method described in the other post may also solve your problem. I say that because I cannot update twrp to 2.6.1, at least via goo manager. I have not tried using Odin to update (yet).
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
I managed to load a stock rom back to the phone but again, it hung on the SAMSUNG screen. Took it to "a guy" and he did a
key sequence and got it to boot. Woulnd't tell me what it was........
ANy one know???
Apocalypse487 said:
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This happened to me after I flashed back but formatting data got it to work (but I have had more problems with apps not installing properly but I learned how to deal with that...still cannot update TWRP via goo manager; waiting on trying it with Odin).
Bought a Nexus 7 about a month ago, updated it to KitKat, rooted it and flashed the latest stable CM. No problems at all. Today I decided to try some other ROM's. Flashed one and the root access was acting funny so I flashed my CM recovery. Tried to flash Paranoid Android and can't even get that one to boot up. It's something to do with my root access, but I don't know what else to do. I've flashed different versions of SU and nothing is working. Everything is great as long as I stay on my CM backup but if I do anything involving updating SU or flashing a ROM it's screwed. Anybody got any ideas?
BeeBiteBoy said:
Bought a Nexus 7 about a month ago, updated it to KitKat, rooted it and flashed the latest stable CM. No problems at all. Today I decided to try some other ROM's. Flashed one and the root access was acting funny so I flashed my CM recovery. Tried to flash Paranoid Android and can't even get that one to boot up. It's something to do with my root access, but I don't know what else to do. I've flashed different versions of SU and nothing is working. Everything is great as long as I stay on my CM backup but if I do anything involving updating SU or flashing a ROM it's screwed. Anybody got any ideas?
Click to expand...
Click to collapse
I haven't flashed CM in a couple years, other than mods I stay on stock roms but I'm thinking your problem has something to do with the kernel you have with CM and maybe changes to the partitions if any. Personally... I would flash the factory image without flashing the userdata.img so you don't lose your data. Then you can try PA or whatever.
Hi All
I've been having such trouble flashing custom ROMs on my Samsung Galaxy Tab Pro 10.1 WiFi SM-T520. I was sucessfully able to flash TWRP 2.8.7 via odin on the device. However, I've tried several ROMs (CM11, 12, 12.1, Unofficial Liquidsmooth) each with their own issues but whichever is able to be flashed always ends up with random startup reboots. I cannot for the life of me figure out why or what is the reason. If I flash back to stock Samsung firmware, everything is fine, works perfectly but no custom firmware.
CM12.1 out right hangs during install in TWRP. The only way I was able to install it is via Cyanogen Recovery which I flashed via odin then attempted to install the rom but even still ends up in random reboots during first bootup and a few times during optimizing apps.
Just a note, I have been doing full wipes (cache, data, system) prior to flashing the ROMs. I don't know what else to do. CM12.1 works really great and smooth but cannot use it because of these random reboots. Can anyone shed some light so I can have a successful flash?
ALSO, I would like to note one suspicion I have and that is my tablet came preloaded with KOT49H.T520UEUAOD1 (T520UEUAOD1_T520XARAOD1_XAR) Samsung Firmware Build. I wonder if perhaps something with this latest build shipped is causing my troubles but am not sure.
Thanks in advanced!
Try booting back to recovery immediatly after new rom flash and perform factory reset and it ahould fix it in most cases.
Sent from my LG-D800 using XDA Free mobile app
I tried the factory reset suggestion but unfortunately did not make a difference.
Are you restoring any backups after flashing? I have been having the same issue, since flashing back to stock. I didn't like stock so I went back to CWM 12.1, which worked flawlessly before. now having random reboots, and the longer I leave it on my system, it's takes longer and longer to wake each time. The only difference between now and the first time I flashed, is, this time I restored a backup! I to, wipe before and after flashing!
Mossey said:
Are you restoring any backups after flashing? I have been having the same issue, since flashing back to stock. I didn't like stock so I went back to CWM 12.1, which worked flawlessly before. now having random reboots, and the longer I leave it on my system, it's takes longer and longer to wake each time. The only difference between now and the first time I flashed, is, this time I restored a backup! I to, wipe before and after flashing!
Click to expand...
Click to collapse
No backup/restores involved for me. Are you still experiencing this issue with CM12.1 or was restoring the backup the problem in your situation?
I am wondering if perhaps the bootloader version that is based off of the latest official stock ROM that was released in April/May 2015 has something to do with my issues. Is there anyone that was on the latest stock Samsung ROM that has been able to successfully flash a custom ROM and use it in a stable way (short of minor CM bugs)?
Do anyone know what to do here. I got a note 2 from my aunt for fixing her S6, I figured I would use this as an extra device to play around with but I absolutely HATE TouchWiz so I wanted to put CM12.1 on it, now I've done this probably thousands of times before, this phone is screwed, I can't figure out why. Even on my old Note 2 it worked, can't get this working, no idea why.
My aunt has done all the OTA updates since she bought it brand new so it was running 4.2.2 DNF4, I did a system restore to get rid of all her stuff, once it booted to the welcome screen to set it up I rebooted into download mode, used odin to flash the latest twrp, all good, wiped the phone, flash the latest cm12.1 nightly and latest opengapps, wipe dalvik, reboot, reboots back into twrp, nothing I can do, I tried this a few times with different builds and even different roms, nothing works, twrp is screwed and will not let me leave once it boots, I have to pull the battery.
So I flashed back to stock touchwiz 4.4.2, rebooted back to download, flashed CMR, figured it must work better since it's right on the download page for CM12.1, wipe it, flash the files, reboot, stuck in a boot loop at the cyanogenmod face, sits there for hours, nothing happens.
Tried the exact process using cwm and philz, nothing works, I literally can't flash anything AOSP, I've tried other roms and only stock touchwiz will boot past the boot screen, and stock touchwiz has no problem running if I run CMR, CWM, or Philz, but TWRP doesn't work on anything, it will not let me leave if I boot into recovery unless I pull the battery and let it boot normal.
Any ideas at all? I'm getting completely fed up with this phone and I'm going to throw it in the garbage if I can't figure this out, I've wasted the same amount of time that if I spent this much time at work, I could have bought a used Nexus 5 by now lol
I used DN3, U HAVE TO WIPE 3X WITH OLDER TWRP, FLASH PHILZ, dont WIPE , THEN INSTALL ROM.ITS ALL REALLY A PAIN.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
How old are we talking for TWRP? As in a different version of 2.8.x or like 2.7.x or maybe even 2.6.x?
EDIT:
I followed your instructions and that actually worked.. I used the latest TWRP for 2.7 which was 2.7.1, I'm going to play with this a little more tomorrow and see what the latest version of twrp is that I can use without getting stuck in a boot loop, thanks a lot for that info.
The only issue I've run into now is I got Error 12 while trying to flash GAPPS so currently there are no GAPPS installed.
Glad you're running. GAPPS very touchy on some roms, Go to ROM thread for that stuff.
I'm just running regular untouched CM12.1 nightlies, any GAPPS should work but the recovery is telling me it's out of date and can't use it stbin or something like that?
However, I found out that once CM12.1 is installed, and before it's set up, I can reboot back into download, flash with odin TWRP 2.8.5 which is the newest I've found that works. and it will let me flash the latest GAPPS, the phone still boots back to the setup/welcome screen, and then I can set it all up as if everything was fine.
It's quite the work around but at least I was able to get it all working.
I also tested this again using DNF4 and it also works using this twrp to wipe and philz to flash method.
Thanks again.