Okay, so I've been trying to install CM11 on my friend's Sprint Note 3 on the NAB firmware,
Each time I try, I get it rooted and TWRP installed fine, however, as soon as I attempt to install CM11 on it, I get:
Kernel is not Seandroid Enforcing
Set Warranty Bit: Kernel
Then boot loop.
Reflash to stock through Odin and try again.
Am I missing something? Because I haven't seen anything that solves this issue. Thoughts?
Andowsdan said:
Okay, so I've been trying to install CM11 on my friend's Sprint Note 3 on the NAB firmware,
Each time I try, I get it rooted and TWRP installed fine, however, as soon as I attempt to install CM11 on it, I get:
Kernel is not Seandroid Enforcing
Set Warranty Bit: Kernel
Then boot loop.
Reflash to stock through Odin and try again.
Am I missing something? Because I haven't seen anything that solves this issue. Thoughts?
Click to expand...
Click to collapse
Are you completely wiping not just a factory reset .... advanced wipe system dalvik cache data .... And I usually move what I want to sd and wipe internal and flash from external
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Are you completely wiping not just a factory reset .... advanced wipe system dalvik cache data .... And I usually move what I want to sd and wipe internal and flash from external
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yep. I've tried Standard factory, I've tried advanced wiping everything but external, and wiping cache/Dalvik multiple times.
Andowsdan said:
Yep. I've tried Standard factory, I've tried advanced wiping everything but external, and wiping cache/Dalvik multiple times.
Click to expand...
Click to collapse
Did you see if md5 is correct and re download ... Try pacman and don't forget to flash gapps
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Did you see if md5 is correct and re download ... Try pacman and don't forget to flash gapps
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
MD5 was good, but I'm gonna go ahead and check pacman and see if that works.
Pacman worked. Thanks for the tip on trying that ROM.
CM is usually my go-to, but since that won't work right now, this will do just fine.
Andowsdan said:
Pacman worked. Thanks for the tip on trying that ROM.
CM is usually my go-to, but since that won't work right now, this will do just fine.
Click to expand...
Click to collapse
Maybe it was just a bad cm try a different day also ...
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Maybe it was just a bad cm try a different day also ...
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
It's possible. I'll try a different day a little bit further down the road. Let him see if he likes that one, first.
Thanks again for the help, bud.
Related
I've tried to get back to Com Rom several times. All I ever get is bootloops or it just freezes on Samsung.
Anybody care to give me the play by play on how to get there?
Thanks
Sent from my SCH-I500 using Tapatalk
........I happened to do it successfully. I don't know what could be your problem...
Which recovery are you on?
Currently on the one packaged with Nameless.
Sent from my SCH-I500 using Tapatalk
I also Odin'd timesinfinity's recovery from 4.22.11, booted straight into recovery, then flashed ComRom 2.0. Bootloop.
I must be missing something.
Sent from my SCH-I500 using Tapatalk
I have been having problems also since Nameless V4
http://forum.xda-developers.com/showthread.php?t=1138145
I may be wrong, but I was always under the impression when going backward in OS, you have to use ODIN. So you would need to ODIN the full EB01 package, then build your way up from there. Or ODIN to DL09, then OTA to ED04, then flash Comm ROM
Thanks Landshark, I'll give it a try when I get home.
Sent from my SCH-I500 using Tapatalk
Steps I took going from nameless to evil.
reboot recovery
Wipe data, cache, dalvik 3 times. Flashed evil and kernel. Boot to os. Reboot recovery. Enable voodoo. Done. Zero problems
ahh thats my issue.......i forgot to enable voodoo in Recovery....did that the robot ladie did her thing and now bam im all good no more kernel panic issues
Dalamar1320 said:
Steps I took going from nameless to evil.
reboot recovery
Wipe data, cache, dalvik 3 times. Flashed evil and kernel. Boot to os. Reboot recovery. Enable voodoo. Done. Zero problems
Click to expand...
Click to collapse
No Odin?
Sent from my SCH-I500 using Tapatalk
bgoodwin said:
No Odin?
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
try his method first...if a no go still then odin back down to DL09(make sure re-partition is checked) and ota or flash to current ED04....then odin recovery and then flash your rom and kernel of choice
bgoodwin said:
No Odin?
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
No. No Odin.
Dalamar1320 said:
Steps I took going from nameless to evil.
reboot recovery
Wipe data, cache, dalvik 3 times. Flashed evil and kernel. Boot to os. Reboot recovery. Enable voodoo. Done. Zero problems
Click to expand...
Click to collapse
^^This^^
Worked great, I escaped Nameless with my sd card intact.
Thanks, y'all
Sent from my SCH-I500 using Tapatalk
So i was going to flash a rom I made a back up, I hit fixed permissions. and now all I have is Samsung Galaxy S4 logo and is just stuck there. I can get into twrp and have tried wiping and starting from a clean slate and restoring the back up but still get the galaxy logo? any suggestions ?
**have just tried to use odin and fails also*** How do I get back to stock please? Anyone please help
bump
Imprezive13 said:
bump
Click to expand...
Click to collapse
Have you tried flashing a stock ROM from TWRP?
-------edit----------
I just remembered. This used to happen on the Note 2 at times. If you're booting and get the Samsung splash screen, try going to TWRP and doing a Factory Reset a couple times. No idea if it will work, but with the Note that would usually clear whatever block existed and allow the ROM to boot past the splash screen. Good luck.
eakeller said:
Have you tried flashing a stock ROM from TWRP?
Click to expand...
Click to collapse
what do you mean ? first time ever having a problem with this. are you talking about the SCH-I545_MDK_562219_Stock_Restore.tar file ?
Imprezive13 said:
what do you mean ? first time ever having a problem with this. are you talking about the SCH-I545_MDK_562219_Stock_Restore.tar file ?
Click to expand...
Click to collapse
If it exists, it would basically be that ROM stuck into a .zip file which could be flashed from TWRP. I'm not sure it exists, was just browsing the Dev thread for you to see if anyone posted it. There is a version here http://forum.xda-developers.com/showthread.php?t=2292707 , but I'm not familiar with Loki enough to say whether or not you have it.
eakeller said:
If it exists, it would basically be that ROM stuck into a .zip file which could be flashed from TWRP. I'm not sure it exists, was just browsing the Dev thread for you to see if anyone posted it. There is a version here http://forum.xda-developers.com/showthread.php?t=2292707 , but I'm not familiar with Loki enough to say whether or not you have it.
Click to expand...
Click to collapse
Well for right now im trying to just get the phone back to its working condition. trying to using odin, but fails every time. and not sure what i should do.
Imprezive13 said:
Well for right now im trying to just get the phone back to its working condition. trying to using odin, but fails every time. and not sure what i should do.
Click to expand...
Click to collapse
If Odin isn't working for you, a solution might be had via TWRP since you can still get into the recovery. If you flash your ROM or try your backup, does the install complete or does it crash? Have you wiped cache, dalvik, system, and data before the flash?
-edit-
Sorry, just saw your OP where you said you wiped and tried. If I were you my next step would be trying a different ROM just to see if you can get something booting.
eakeller said:
If Odin isn't working for you, a solution might be had via TWRP since you can still get into the recovery. If you flash your ROM or try your backup, does the install complete or does it crash? Have you wiped cache, dalvik, system, and data before the flash?
Click to expand...
Click to collapse
Trying again. First wiping wiped cache, dalvik, system, and data , then restoring back up. I've tried this multiple times before hopefully it works this time. But generally when i hit reboot system afterward it just hangs at the Samsung Galaxy IV boot screen and does nothing.
Imprezive13 said:
Trying again. First wiping wiped cache, dalvik, system, and data , then restoring back up. I've tried this multiple times before hopefully it works this time. But generally when i hit reboot system afterward it just hangs at the Samsung Galaxy IV boot screen and does nothing.
Click to expand...
Click to collapse
After your backup restores, try using TWRP to do a Factory Reset a couple times before rebooting. Also wipe cache/dalvik again before the boot.
Failed again stuck at Samsung Galaxy S4 boot screen
eakeller said:
After your backup restores, try using TWRP to do a Factory Reset a couple times before rebooting. Also wipe cache/dalvik again before the boot.
Click to expand...
Click to collapse
Stuck again
Imprezive13 said:
Stuck again
Click to expand...
Click to collapse
Sorry to hear that, man. I'm out of ideas and hopefully someone with more know-how can give the solution.
Sent from my SCH-I545 using Tapatalk 2
I would try downloading a ROM to your computer then copying it to a microsd, put the card in your phone and then try to flash the fresh ROM from TWRP. (After wiping everything again.)
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
I would try downloading a ROM to your computer then copying it to a microsd, put the card in your phone and then try to flash the fresh ROM from TWRP. (After wiping everything again.)
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Ive been looking for the stock rom files no luck at the moment.
Maybe this one?
http://forum.xda-developers.com/showthread.php?t=2292707
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
Maybe this one?
http://forum.xda-developers.com/showthread.php?t=2292707
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
downloading now wish me luck
Good luck to you.
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
Good luck to you.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
got it working. on a deoxed rom. but is there a way to go completely back to stock using odin ?
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Well went to restart the phone and now its stuck on a Samsung logo with a unlocked icon thats says custom underneath it and just sits there.
I'm trying to clean up my S4 to sell, and so I wiped data/factory reset and did format data. I then reflashed HyperDriver 14 and now I get stuck at the Galaxy S4 splash screen. I do still have access to get into TWRP however. Is there something I can do from TWRP to fix this? I have tried to fix permissions and it says FAILED. Do I need to do an ODIN flash at this point? I don't know what baseband I have, but since I have TWRP that was functional does that imply that I have the MDK baseband?
Thanks for any help!
jst07 said:
I'm trying to clean up my S4 to sell, and so I wiped data/factory reset and did format data. I then reflashed HyperDriver 14 and now I get stuck at the Galaxy S4 splash screen. I do still have access to get into TWRP however. Is there something I can do from TWRP to fix this? I have tried to fix permissions and it says FAILED. Do I need to do an ODIN flash at this point? I don't know what baseband I have, but since I have TWRP that was functional does that imply that I have the MDK baseband?
Thanks for any help!
Click to expand...
Click to collapse
Try another factory data reset and wipe /cache and /dalvik. If that doesn't work I would double the check the md5 of the HD rom file to make sure it's not corrupted. If the file is still good then you need to reflash the rom but this time do a factory data reset, wipe /system, wipe /cache, wipe /dalvik, and then install the rom, and it SHOULD boot.
hexitnow said:
Try another factory data reset and wipe /cache and /dalvik. If that doesn't work I would double the check the md5 of the HD rom file to make sure it's not corrupted. If the file is still good then you need to reflash the rom but this time do a factory data reset, wipe /system, wipe /cache, wipe /dalvik, and then install the rom, and it SHOULD boot.
Click to expand...
Click to collapse
Yeah I tried that again and have done that a few times, still no luck. The MD5 checks out OK. I could try another ROM tomorrow.
I'm on TWRP 2.5.0.2, is there any benefit to upgrading to 2.6.x.x? Would that help me possibly?
jst07 said:
Yeah I tried that again and have done that a few times, still no luck. The MD5 checks out OK. I could try another ROM tomorrow.
I'm on TWRP 2.5.0.2, is there any benefit to upgrading to 2.6.x.x? Would that help me possibly?
Click to expand...
Click to collapse
No, stick with 2.5, it works better on these phones than 2.6.
If your going to sell it then it doesn't get much better than just Odin mdk and re reroot it . probably take 10 minutes. Just my two cents lol
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
If your going to sell it then it doesn't get much better than just Odin mdk and re reroot it . probably take 10 minutes. Just my two cents lol
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I would suggest the same. 30 or 40 minutes and you are done
Mistertac said:
If your going to sell it then it doesn't get much better than just Odin mdk and re reroot it . probably take 10 minutes. Just my two cents lol
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
decaturbob said:
I would suggest the same. 30 or 40 minutes and you are done
Click to expand...
Click to collapse
Anyone have a link to the best MDK image? I've seen a few so far.
jst07 said:
Anyone have a link to the best MDK image? I've seen a few so far.
Click to expand...
Click to collapse
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
That's the one I used and it worked perfectly.
Sent from my SCH-I545 using Tapatalk
thesoldier said:
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
That's the one I used and it worked perfectly.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Is that one a no wipe or full wipe? I tried downloading it but the link is slow.
I did try to flash a no wipe MDK image and it seems I'm still stuck at the same spot.
jst07 said:
Is that one a no wipe or full wipe? I tried downloading it but the link is slow.
I did try to flash a no wipe MDK image and it seems I'm still stuck at the same spot.
Click to expand...
Click to collapse
I believe that one is a complete wipe.
If you have no luck with the no wipe tar, you may want to try the one that does wipe and back up all your internal storage.
Sent from my SCH-I545 using Tapatalk
thesoldier said:
I believe that one is a complete wipe.
If you have no luck with the no wipe tar, you may want to try the one that does wipe and back up all your internal storage.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah I'll try the one you linked. Just gotta wait 5 hours for it to download. At least I don't have anything to back up, its all wiped already.
jst07 said:
Yeah I'll try the one you linked. Just gotta wait 5 hours for it to download. At least I don't have anything to back up, its all wiped already.
Click to expand...
Click to collapse
It's that slow? Took me maybe 20 minutes to download. :what:
Sent from my SCH-I545 using Tapatalk
thesoldier said:
It's that slow? Took me maybe 20 minutes to download. :what:
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah I've been averaging like 80-100kB/s. Only 15 mins left
jst07 said:
Is that one a no wipe or full wipe? I tried downloading it but the link is slow.
I did try to flash a no wipe MDK image and it seems I'm still stuck at the same spot.
Click to expand...
Click to collapse
Finally downloaded, flashed, and worked like a charm. Thank you!
first...upgraded to kitkat 4.4.2 and....sd not working anymore, cant download anything, some apps say sd is required...and on computer i cant write to it either. And gps is crap....so any fixes?
i saw that upgrading to 4.4 fixes all of it but only at&t has it at the moment. What would happen if i installed at&t via odin on a sprinit phone and selected nand erase all option? and why cant u downgrade....with nand erase all, i mean i was not 4.4.2 and the way i upgraded was by installing the recovery rom that was 4.4.2
And I tried editing xml file was not able to open, I tried sd fix from store and a zip via twrp, sd still no work. Am on vision X stock rom, software cn5
Try a different sd ... Maybe you have a bad one ... folder Mount in store works I know ...
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Try a different sd ... Maybe you have a bad one ... folder Mount in store works I know ...
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
not bad, just after update. I put sd in another phone and works. 8 read this is a kitkat problem
That actually worked said faulty and patch sucess. What about gps...it's working but it's not following along or saying turn
djhulk2 said:
That actually worked said faulty and patch sucess. What about gps...it's working but it's not following along or saying turn
Click to expand...
Click to collapse
Gps is working fine for me ...I would go back to complete stock using Odin and tar file ...mj4 if your on jelly bean or nab nc5 if you're on kit Kat and then check Gps .... Maybe a hardware problem with your phone ...Gps wasn't great on aosp but was fine on stock
Sent from my SM-N900P using Xparent BlueTapatalk 2
I did start with stock mc5, but it did not want to load it...would stay stuck on Samsung logo. So I rooted it and installed that rom and it loaded, but stock doesn't want to anymore
and everything worked before this kitkat update, and here is proof its 100% kitkat
gps problem: http://www.gottabemobile.com/2014/0...e-3-android-4-4-kitkat-release-5-key-details/
sd problem:http://www.androidpit.com/how-to-fix-android-4-4-2-kitkat-problems-galaxy-note-3
djhulk2 said:
I did start with stock mc5, but it did not want to load it...would stay stuck on Samsung logo. So I rooted it and installed that rom and it loaded, but stock doesn't want to anymore
and everything worked before this kitkat update, and here is proof its 100% kitkat
gps problem: http://www.gottabemobile.com/2014/0...e-3-android-4-4-kitkat-release-5-key-details/
sd problem:http://www.androidpit.com/how-to-fix-android-4-4-2-kitkat-problems-galaxy-note-3
Click to expand...
Click to collapse
It will stay on Samsung screen if you don't wipe right when installing a rom .... I always wipe data davlik cache and system .... If I am going to aosp of any kind ....I wipe internal and flash from external sd ...I always wipe internal going from aosp to touch wiz also .... There are to many file differences for me
Sent from my SM-N900P using Xparent BlueTapatalk 2
I did do those wipes but was still stuck. This flash was also via odin
djhulk2 said:
I did do those wipes but was still stuck. This flash was also via odin
Click to expand...
Click to collapse
After flashing in Odin if it passed sometimes you may have to boot into stock recovery and wipe .... If your trying to get it to say official in software for ota it may be necessary to remove sd card prior to flashing with Odin. ..
Sent from my SM-N900P using Xparent BlueTapatalk 2
It's interesting that u say u have no problems, the sd got fixed thanks ti that app mentioned above, but gps works but it does not giude u. The fix for all these problems are said to be in the upgrade 4.4 which only at&t has at the moment
djhulk2 said:
It's interesting that u say u have no problems, the sd got fixed thanks ti that app mentioned above, but gps works but it does not giude u. The fix for all these problems are said to be in the upgrade 4.4 which only at&t has at the moment
Click to expand...
Click to collapse
I use gps every day in Phoenix .... You milage may vary but it works. .. If it don't work for you that is why I would advise you go back to stock to try but if you just want to say no or don't work. ..I tried I have no reason to steer you wrong but oh well
Sent from my SM-N900P using Xparent BlueTapatalk 2
Thanks but, flashing stock is not the solution.
Bump
I am trying to flash a Sprint Samsung Note 3 with Cyanogenmod 11. I downloaded the imaged, checked the hash, and put it on the external sdcard. When I use TWRD to flash it, after wiping / factory default, I get the following message : Unable to mount '/usbstorage along with a Success message from TWRD. But when I reboot the phone it gets caught in a recovery loop. I have tried older releases of Cyanogenmod 11 also. Is there something I am missing? I looked online, and found some comments about wiping the data before flashing. But I had done that.
sansari123 said:
I am trying to flash a Sprint Samsung Note 3 with Cyanogenmod 11. I downloaded the imaged, checked the hash, and put it on the external sdcard. When I use TWRD to flash it, after wiping / factory default, I get the following message : Unable to mount '/usbstorage along with a Success message from TWRD. But when I reboot the phone it gets caught in a recovery loop. I have tried older releases of Cyanogenmod 11 also. Is there something I am missing? I looked online, and found some comments about wiping the data before flashing. But I had done that.
Click to expand...
Click to collapse
You flash gapps too ? And wipe data and system before flashing . The unable to mount error means nothing
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
You flash gapps too ? And wipe data and system before flashing . The unable to mount error means nothing
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I found this link about the error. http://forum.xda-developers.com/showthread.php?t=2507403 but the link to the script provided to fix this issue does not work. I have made a comment about it. Hope they can fix it.
Just to double check, I am putting my zip files for Cyanogenmod and Gapps on the sdcard. That is what we are supposed to do right?
sansari123 said:
Yes I did. For some reason it keeps getting stuck in boot loop. So you are saying I should look into something else? The unable to mount message does not mean much?
Click to expand...
Click to collapse
When going from stock to any aosp always wipe system that is what most do wrong
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
When going from stock to any aosp always wipe system that is what most do wrong
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Epix,
I'm not familiar with AOSP Roms on the Note 3, but I know that people were having major issues when upgrading from JellyBean to KitKat TW Roms. They had to Odin flash the stock NAB update first, then they were able to flash NAB (KitKat) Roms. Is this the same procedure for AOSP KitKat Roms?
I haven't seen anything on the various AOSP threads about having to be on NAB or newer (i.e. KitKat) in order to flash their Roms.
topherk said:
Epix,
I'm not familiar with AOSP Roms on the Note 3, but I know that people were having major issues when upgrading from JellyBean to KitKat TW Roms. They had to Odin flash the stock NAB update first, then they were able to flash NAB (KitKat) Roms. Is this the same procedure for AOSP KitKat Roms?
I haven't seen anything on the various AOSP threads about having to be on NAB or newer (i.e. KitKat) in order to flash their Roms.
Click to expand...
Click to collapse
It did not matter what bootloader you were on when flashing aosp roms .... as they were not built to need that .... you could have mj4 and flash 4.4.2 aosp roms just fine ... most times it is not wiping system as touch wiz was on system and it needs wiped to install aosp ....I personally wipe all but external and flash from there .... I hit advanced wipe and wipe data cache davlik system and internal. .. but that is just me
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
It did not matter what bootloader you were on when flashing aosp roms .... as they were not built to need that .... you could have mj4 and flash 4.4.2 aosp roms just fine ... most times it is not wiping system as touch wiz was on system and it needs wiped to install aosp ....I personally wipe all but external and flash from there .... I hit advanced wipe and wipe data cache davlik system and internal. .. but that is just me
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Ah, that's good to know. I wasn't sure if AOSP Roms needed the updated bootloader.
I also do a full wipe in TWRP before flashing a new Rom. I find it prevents a lot of the various issues I've seen with dirty flashers on here.
Thanks for the input!
Epix4G said:
When going from stock to any aosp always wipe system that is what most do wrong
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yea I did a complete wipe of everything. Still got the error. I am now trying another microsd.