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.
Related
I have one S3 that's stock and another that's rooted, so I decided to try CM9 first on rooted S3 because CM10 didn't seem quite ready for daily use. Flashed ROM and Gapps, and things were fine until wi-fi ceased functioning. Worked, then didn't ever again. Nothing I found in searching this helped. And I couldn't get to PlayStore because there was no connection. Tried many things to reset wi-fi, but despite excellent signal, the phone wasn't connected to Internet. I reflashed CM9 (same most current release) but it didn't help.
So, having not actually done anything other than adding ROM Manager, I decided to flash latest CM10 nightly with CWM recovery via ROM Manager. Everything was fine, except of course I forgot I needed to install newer Gapps. However, when I went to do so, ROM Manager was no longer there and manually trying to get recovery only resulted in download mode, which meant I couldn't install Gapps or do much of anything.
I spent time trying to figure out how to get recovery, but having run out of options, I thought it perhaps best to flash back to stock using desktop Odin. I have the MD5 for 4.1.1 LK3. So I did this, but now once past the Samsung and AT&T animations, the phone stops with a Samsung logo. And that's where I'm at.
I know I've seen threads on fixing this, but I can't find them and I would like rectify the softbrick circumstance. What to do.
eduardo_b said:
I have one S3 that's stock and another that's rooted, so I decided to try CM9 first on rooted S3 because CM10 didn't seem quite ready for daily use. Flashed ROM and Gapps, and things were fine until wi-fi ceased functioning. Worked, then didn't ever again. Nothing I found in searching this helped. And I couldn't get to PlayStore because there was no connection. Tried many things to reset wi-fi, but despite excellent signal, the phone wasn't connected to Internet. I reflashed CM9 (same most current release) but it didn't help.
So, having not actually done anything other than adding ROM Manager, I decided to flash latest CM10 nightly with CWM recovery via ROM Manager. Everything was fine, except of course I forgot I needed to install newer Gapps. However, when I went to do so, ROM Manager was no longer there and manually trying to get recovery only resulted in download mode, which meant I couldn't install Gapps or do much of anything.
I spent time trying to figure out how to get recovery, but having run out of options, I thought it perhaps best to flash back to stock using desktop Odin. I have the MD5 for 4.1.1 LK3. So I did this, but now once past the Samsung and AT&T animations, the phone stops with a Samsung logo. And that's where I'm at.
I know I've seen threads on fixing this, but I can't find them and I would like rectify the softbrick circumstance. What to do.
Click to expand...
Click to collapse
Did you remember to factory reset (wipe /data) when flashing the stock ROM? That's the most common cause of soft-bricking in this scenario.
If not, boot into recovery (Vol Up + Home + Power) and do so, then try booting the phone again.
Do I do factory reset from desktop Odin in download mode?
That's one possibility, but if you don't want to go through the Odin process again, you can just do the reset from recovery as I outlined above.
smelenchuk said:
That's one possibility, but if you don't want to go through the Odin process again, you can just do the reset from recovery as I outlined above.
Click to expand...
Click to collapse
Ah...volume UP. But wipe data/factory reset didn't help. If I select update from external storage, would that be MD5 or...?
Okay, I wiped cache partition and I'm in business. No more softbrick. Thanks!
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 wiped the dust off my old S2 in hopes to get it running again. The last ROM I had on it was Jedi Mind Trick JB 4. I flashed sultanxda's CM11 ROM and it booted up fine(logged into google, installed some apps). I did a soft reboot and the phone never wanted to boot back up. It flashed the Samsung logo and then just sat at a black screen. I flashed CM11 again just to make sure it didn't get corrupted the first time, but it still did not want to come up after a reboot. Then I thought maybe it's the ROM/ZIP so I flashed ParanoidAndroid 4.6-beta5. Same issue, it boots up fine after the flash, but will not start up after a reboot.
I'm on CWM Recovery 6.0.2.7, and I wipe/format the usual before the flash. Also on radio UVMC6. Any ideas?
I'm having the same problem, did you find a fix ?
Rushaan™ said:
I'm having the same problem, did you find a fix ?
Click to expand...
Click to collapse
same issue, different roms .
You. Guys are using an out of date recovery. Get the newest version of twrp and you should. Be fine.
CWM: http://www.teamchopsticks.org/p/cm110-release-notes.html
TWRP: http://forum.xda-developers.com/showthread.php?t=1768742
Hi, new to flashing roms and this might be a noobie question, however, I can't find an answer online. Over this week I have tried to flash cyanogenmod to note 3 the tmobile variant. I have it rooted (thanks to CF-Auto-Root) and it has twrp 2.8 the newest version. I downloaded the newest cyanogenmod rom and gapps into my flash drive and used an adaptar when I tried to flash it to my phone. It successfully flashed and I was excited for the new rom. However, when my phone rebooted into the Samsung Galaxy note 3 boot up screen; the top left of the screen showed Kernel is not seandroid enforcing set warranty bit: kernel. And it just starts bootlooping. I've tried waiting for 30 minutes and that just kept happening. So i decided to boot into recovery and and restore my original rom with twrp. That went fine and now I have all my data back. However, how do I end the bootloop? I watch youtube videos and they all work fine, however, they dont get the bootloop. They even have the same phone with the same carrier. I know its not the bootloader because tmobile doesnt have locked boot loaders. Right now I'm running on 4.4.2 Kit Kat on my note 3. Also I have already went back into twrp after flashing the rom and wiping dalvik and cache. It still didnt work. After I went back in and formated system memory and it still didnt work, so I gave up and did a little research. However, I cant anything relavant online to help me.
Links that I already read: http://forum.xda-developers.com/showthread.php?t=2470599
http://forum.xda-developers.com/showthread.php?t=2609767
http://forum.xda-developers.com/showthread.php?t=2614787
Hi,
I will have your thread moved to your device section.
Good luck!
Superbia Thema said:
Hi, new to flashing roms and this might be a noobie question, however, I can't find an answer online. Over this week I have tried to flash cyanogenmod to note 3 the tmobile variant. I have it rooted (thanks to CF-Auto-Root) and it has twrp 2.8 the newest version. I downloaded the newest cyanogenmod rom and gapps into my flash drive and used an adaptar when I tried to flash it to my phone. It successfully flashed and I was excited for the new rom. However, when my phone rebooted into the Samsung Galaxy note 3 boot up screen; the top left of the screen showed Kernel is not seandroid enforcing set warranty bit: kernel. And it just starts bootlooping. I've tried waiting for 30 minutes and that just kept happening. So i decided to boot into recovery and and restore my original rom with twrp. That went fine and now I have all my data back. However, how do I end the bootloop? I watch youtube videos and they all work fine, however, they dont get the bootloop. They even have the same phone with the same carrier. I know its not the bootloader because tmobile doesnt have locked boot loaders. Right now I'm running on 4.4.2 Kit Kat on my note 3. Also I have already went back into twrp after flashing the rom and wiping dalvik and cache. It still didnt work. After I went back in and formated system memory and it still didnt work, so I gave up and did a little research. However, I cant anything relavant online to help me.
Links that I already read: http://forum.xda-developers.com/showthread.php?t=2470599
http://forum.xda-developers.com/showthread.php?t=2609767
http://forum.xda-developers.com/showthread.php?t=2614787
Click to expand...
Click to collapse
Make sure your getting the ROM from here: http://download.cyanogenmod.org/?device=hlte
Latest TWRP recovery is 2.8.4: http://www.techerrata.com/browse/twrp2/hlte
Gapps: http://wiki.cyanogenmod.org/w/Google_Apps
When in recovery do a factory reset as step 1. Then go into Advanced Wipe, and only leave SD card unchecked. Wipe everything else. Then Format the system. After all that Flash the ROM, then Gapps, and them reboot. If you want you can try CM12. It's been very stable even as a new nightly.
http://forum.xda-developers.com/note-3-tmobile/general/official-cm12-released-t2995099
Seeing: Kernel is not seandroid enforcing set warranty bit: kernel is normal for CM. Don't worry about that.
Hope it works for ya. Enjoy.
I downloaded cyanogenmod and gapps from those websites, but I'll flash twrp again to give it another try. Yea I was goanna install android lollipop but the bootloop gets me every time...
Sent from my SM-N900T using XDA Free mobile app
bobbyphoenix said:
Make sure your getting the ROM from here: http://download.cyanogenmod.org/?device=hlte
Latest TWRP recovery is 2.8.4: http://www.techerrata.com/browse/twrp2/hlte
Gapps: http://wiki.cyanogenmod.org/w/Google_Apps
When in recovery do a factory reset as step 1. Then go into Advanced Wipe, and only leave SD card unchecked. Wipe everything else. Then Format the system. After all that Flash the ROM, then Gapps, and them reboot. If you want you can try CM12. It's been very stable even as a new nightly.
http://forum.xda-developers.com/note-3-tmobile/general/official-cm12-released-t2995099
Seeing: Kernel is not seandroid enforcing set warranty bit: kernel is normal for CM. Don't worry about that.
Hope it works for ya. Enjoy.
Click to expand...
Click to collapse
Welp I went ahead and flash another rom and it worked so I'm guessing I either have the wrong files or something is wrong with my phone. However, dompop works amazingly to thanks for the help!!!
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.