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!!!
Related
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
Hey guys all my restores are failing half way through. It also fails if I try to factory reset or wipe dalvik but wipe cache works fine It fails if i try flash any ROM.. And if I try to boot to system it shows SG logo then black screen I'm really kind of lost here. I've already tried flashing 4 different versions of Twrp/clockworkmod and I get the same result every time. The roms I'm trying to flash were running fine on my device before this happened. Never seen this before please help thank you.
Sent from RootBox infected sensation or my PacMan e739
djwuh said:
Hey guys all my restores are failing half way through. It also fails if I try to factory reset or wipe dalvik but wipe cache works fine It fails if i try flash any ROM.. And if I try to boot to system it shows SG logo then black screen I'm really kind of lost here. I've already tried flashing 4 different versions of Twrp/clockworkmod and I get the same result every time. The roms I'm trying to flash were running fine on my device before this happened. Never seen this before please help thank you.
Sent from RootBox infected sensation or my PacMan e739
Click to expand...
Click to collapse
is this an i747 or i747m (carrier?)? what was the last thing you did to the device/had you just modified or flashed something? were you using recovery or odin to flash the 4 different recoveries?
xBeerdroiDx said:
is this an i747 or i747m (carrier?)? what was the last thing you did to the device/had you just modified or flashed something? were you using recovery or odin to flash the 4 different recoveries?
Click to expand...
Click to collapse
I have sgh i747 at&t us model. Unlocked Sim for Tmobile use. Before having problems. I flashed vanilla rootbox att nightly. it was running fine then I flashed acid audio mod. And it worked but not well with my player of choice. So i flashed a restore from fright before the sound mod. And all I got was 2 different Samsung logos then black screen. At this point Twrp started asking for a password. I tried an older backup. (rootbox stable) and it booted fine. Everything seemed to be working. But when I rebooted again I got the 1St SG logo then black screen. Now recovery doesn't read anything on the internal card as well as the other problems I stated. I used mskips toolkit to flash Twrp originally and now I've been flashing back and forth between recoveries using recovery flashable zips. Also every time I flash roms or restore I did factory wipe/cache/dalvik and after I started having these issues I tried wiping system and that didn't help either. Thanks for trying to help
Sent from RootBox infected sensation or my PacMan e739
what recovery are you currently sitting on?
Twrp 2.4.4.0 is what I started with and now I'm back on it but from a flashable zip this time instead of whatever mskips toolkit used
Sent from RootBox infected sensation or my PacMan e739
here is the link to an odin flashable twrp 2.5.0.0 tar: http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.5.0.0-d2att.tar
and here's a recovery flashable twrp 2.5.0.0 zip link: http://forum.xda-developers.com/attachment.php?attachmentid=1917517&d=1367104589
if you flash in recovery, be sure to reboot recovery in order to boot into the new version. i'm sure you know most of this but i'm just trying to cover all the bases.
is twrp still asking for the password or were you able to get passed that?
if you have a micro sd card, you could place a ROM/gapps on it, flash this latest twrp recovery from odin or recovery, perform a full wipe (cache, dalvik, data, system) and flash the ROM/gapps. see if that remedies your situation.
if you dont have a micro sd card, and it appears you've wiped the system so there's no OS, you may have to odin back to rooted stock and start over. keep me posted
Still no luck. i flashed twrp2.5 through recovery and after rebooting back to recovery it still asked for a password so I hit cancel at which point it lets me continue and after full wipe as you described above and a fresh flash of stable rootbox 3.9.1 (md5 matched) im still in the same situation. also factory wipe says failed still
I think at this point if it were me, I would Odin flash back to stock then start from scratch. Pain in the butt I know, and no guarantee, but usually flash back to stock is a safe bet.
Another option is to grab the Odin flashable cwm tar in the "root from recovery" method in the general section. Flash the tar, boot into recovery and flash the 6.0.3.1 zip in post #2 of my signature link. Reboot recovery and try wiping/flashing again.
Since you're not entering the password in TWRP, I think that's why you're not getting successful wipes and flashes.
now I used the power+home+vol down button combo to see if bootloader would start. it gave me a choice to download a custom rom or cancel so I canceled and the phone rebooted and i was blessed with the beautifull rootbox animation. my rootbox 3.9.1 nandroid booted and seems to be running fine. Now Im afraid to reboot in fear it will start the whole process over again. any suggestions? or should I just leave it powered on for the rest of its life lol
edit: well I got up the guff to reboot and everything came back fine again WTH. this is so weird, I wish I had a clue what happened. anyways I just wanted to thank you guys one more time for you help. hopefully we wont have to come back to this thread. Peace ;-]
Man that is strange. If that ever happens again it would be interesting to see the log if you can get it. I wonder if there were issues mounting a partition and/or your SD card. If TWRP and CWM were both having an error and the files were on your SD card that would probably be the only thing in common that could cause something like this. Some Transformers seemed to have the password issue, but doesn't seem related to your experience. Glad you got it sorted.
Hello,
I can not flash any ROM to my GT-P5210 Tab anymore.
I was on BinDroid ONE P5210 LITE V3.0.0, but since it is discontinued
and 2 other ROMs rolled out over the past days I wanted to give it a try.
- went back to stock with official firmware from "sammobile" for my device,
- flashed TWRP with Odin 3.07
- flashed ROOT with Odin
- went to recovery did factory reset + dalvik/cache (
- flashed new ROM (neither ROM Pimpdroid or Grievous is working)
after flashing Tab goes into a bootloop to recovery. First boot after flash takes some time in the Galaxy Tab3 Logo but in the end it reboots into TWRP. I have tried CWM too with the same results.
I am not totaly new to flashing, did it with my I9000 and now with my I9300 int. but with this Tab3 now I am lost.
Any ideas are much appreciated.
regards and sorry for my english its not my native tongue
zerodv8 said:
Hello,
I can not flash any ROM to my GT-P5210 Tab anymore.
I was on BinDroid ONE P5210 LITE V3.0.0, but since it is discontinued
and 2 other ROMs rolled out over the past days I wanted to give it a try.
- went back to stock with official firmware from "sammobile" for my device,
- flashed TWRP with Odin 3.07
- flashed ROOT with Odin
- went to recovery did factory reset + dalvik/cache (
- flashed new ROM (neither ROM Pimpdroid or Grievous is working)
after flashing Tab goes into a bootloop to recovery. First boot after flash takes some time in the Galaxy Tab3 Logo but in the end it reboots into TWRP. I have tried CWM too with the same results.
I am not totaly new to flashing, did it with my I9000 and now with my I9300 int. but with this Tab3 now I am lost.
Any ideas are much appreciated.
regards and sorry for my english its not my native tongue
Click to expand...
Click to collapse
did u try root check app to c if u r truly rooted? is ur su updated? if so try reflashing the recovery...n the root file. do u have the stock kernel?
THink I Got a fix
This worked for me. The TWRP does NOT actually wipe anything. go to settings in whatever rom you are running, and do a factory data reset from there. Let it wipe all app data and EVERYTHING. Then go through the steps to install whichever ROM you want. It worked for me!! Post back and let me know if it worked for you too. I tried for 3 days to install anything, and this is the only thing that worked.:victory:
Tquarter said:
This worked for me. The TWRP does NOT actually wipe anything. go to settings in whatever rom you are running, and do a factory data reset from there. Let it wipe all app data and EVERYTHING. Then go through the steps to install whichever ROM you want. It worked for me!! Post back and let me know if it worked for you too. I tried for 3 days to install anything, and this is the only thing that worked.:victory:
Click to expand...
Click to collapse
ok did read your post before trying to flash. i lost my back up and as well as my emmc. so i need a stock firmware only problem I now have is downloading one. Three quarter of links r dead and the three i have tried have had errors. Can you help me anyone with a google drive or box download of an unknown region stock firmware so I can breathe light in t o my brick please
https://db.tt/63atdfRZ Here ya go!
I'm uploading a stock firmware that can be flashed using ODEN. I have not tried this file, I just downloaded it, before I flashed anything, in case something went wrong. I'll post the link when it finishes uploading. Good luck! Post back and let us know how it went.
solved
Tquarter said:
This worked for me. The TWRP does NOT actually wipe anything. go to settings in whatever rom you are running, and do a factory data reset from there. Let it wipe all app data and EVERYTHING. Then go through the steps to install whichever ROM you want. It worked for me!! Post back and let me know if it worked for you too. I tried for 3 days to install anything, and this is the only thing that worked.:victory:
Click to expand...
Click to collapse
I tried your method and it worked. Another thing that works is first thing when you enter TWRP check if system is mounted, if not tick mount and then wipe the way installation of the rom suggests. This worked for me too. Thanks for ur time and the fish
Oh cool, I'm glad to help. I also tried to manually mount system, but untill I got that first ROM installed, it just un-mounted itself again. I hope these problems will be sorted out. Both recoveries act choked down somehow. (TERP, CWM) Looks like "source manifest CM 10.2 "thread is making exciting progress. I can't stop watching it. Most of it is over my head, but google helps me, in trying to grasp what they are saying.
Tquarter said:
Oh cool, I'm glad to help. I also tried to manually mount system, but untill I got that first ROM installed, it just un-mounted itself again. I hope these problems will be sorted out. Both recoveries act choked down somehow. (TERP, CWM) Looks like "source manifest CM 10.2 "thread is making exciting progress. I can't stop watching it. Most of it is over my head, but google helps me, in trying to grasp what they are saying.
Click to expand...
Click to collapse
can someone recommend a clean rom for gt-p5210
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
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.