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.
Related
So if we install one ROM, set it up to our liking and then do a Nandroid backup with CWR can we reload that rom later on to exactly how was? I'd like to install UnNamed Rom and the install PhoneBricker Rom, and if I don't like PhoneBricker can I restore to UnNamed Rom and will it restore exactly how I left it?
Yes, exactly as you left it. The only things(I think) a nandroid restore won't touch are the contents of the SD cards, and the modem.
I believe it does everything but your SD content, because every time I swap ROMs back and forth all I have to is restore and I am good to go. No need to install a modem.
Wiping the phone won't wipe the sd card or internal storage would it? So if you flash a rom with bad radios and then install a rom with good radios and restore to the bad one you'll keep the good radios or whatever modem was previously on the phone?
When you are in CWR and do a wipe it doesn't mess with your SD content, just your system file if I am correct. As far as radio/modems go, if that is the problem with the ROM, you should be able to flash a different modem from the list on the sticky just fine.
Yeah, you don't need to worry about modems. Once you have CWM, changing modems isn't much more trouble than changing wallpapers.
mattdm said:
Yeah, you don't need to worry about modems. Once you have CWM, changing modems isn't much more trouble than changing wallpapers.
Click to expand...
Click to collapse
Modems can have problems with cwm and should be done with mobile odin or odin
Sent from my GT-I9100 using Tapatalk 2 Beta-2
I've only flashed roms a couple of times so I'm pretty new to this. Have no plans to flash modems as the roms I want don't have any problems with signal.
rdannar said:
Modems can have problems with cwm and should be done with mobile odin or odin
Sent from my GT-I9100 using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
I've never had issues flashing modems in cwm, FWIW. There is a thread in dev. section with all the i777 modems linked in the OP. There are different CWM flashables depending on whether you are on AOSP base or Samsung base. I have only used these on Sammy based ROMs, but have been through 4 different modems with no issues.
rdannar said:
Modems can have problems with cwm and should be done with mobile odin or odin
Sent from my GT-I9100 using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
Really? I didn't know that. What kind of problems?
Only roms I plan on using are:
http://forum.xda-developers.com/showthread.php?t=1530914
http://forum.xda-developers.com/showthread.php?t=1319955
rdannar said:
Modems can have problems with cwm and should be done with mobile odin or odin
Sent from my GT-I9100 using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
I've used the flashable zips from the earlier post and tried each and every one without a problem flashing with CWM - if you use jivy's kernel cleaning script (or clear cache and dalvik) before each flash, you shouldn't have any problems.
If you don't clear cache and dalvik, you probably would have problems.
So I was mj4 rooted .. then went back to stock .. did OTA kit kat update ... rooted using cf auto root since it was updated for 4.4 base now.. took a few seconds on Odin 3.07 showed up as reset on the screen .. phone will reboot but leave it plugged in til it says pass... Mine took a Lil over 2 mins.. anyway I then went to goo manager installed open recovery but when I clicked reboot to recovery.. my phone bootlooped on recovery screen .. I pulled out the battery an put it back in.. an immediately put it into download mode( before it had a chance to bootloop recovery again ) then clicked down to cancel an restart phone.. my question is is there a link to a 4.4 kit kat compatible twrp recovery version that I can install through Odin ... an if so do I put it in the pda section.. Sorry I'm new to note 3 an Odin. .. coming from HTC lol ... thx in advance !
Sent from my SM-N900P using Tapatalk
chico260 said:
So I was mj4 rooted .. then went back to stock .. did OTA kit kat update ... rooted using cf auto root since it was updated for 4.4 base now.. took a few seconds on Odin 3.07 showed up as reset on the screen .. phone will reboot but leave it plugged in til it says pass... Mine took a Lil over 2 mins.. anyway I then went to goo manager installed open recovery but when I clicked reboot to recovery.. my phone bootlooped on recovery screen .. I pulled out the battery an put it back in.. an immediately put it into download mode( before it had a chance to bootloop recovery again ) then clicked down to cancel an restart phone.. my question is is there a link to a 4.4 kit kat compatible twrp recovery version that I can install through Odin ... an if so do I put it in the pda section.. Sorry I'm new to note 3 an Odin. .. coming from HTC lol ... thx in advance !
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Yes, all TWRP and (I believe Philz, though not certain, as I've never used it) tar files can be flashed with PC Odin. Use the latest for KitKat. Go to the original development forum for answers to this important question, as the preferred recovery should be chosen by you.
If you need help flashing, just ask.
Recovery goes in the PDA slot.
Sent from my SM-N900P using Xparent BlueTapatalk 2
chico260 said:
So I was mj4 rooted .. then went back to stock .. did OTA kit kat update ... rooted using cf auto root since it was updated for 4.4 base now.. took a few seconds on Odin 3.07 showed up as reset on the screen .. phone will reboot but leave it plugged in til it says pass... Mine took a Lil over 2 mins.. anyway I then went to goo manager installed open recovery but when I clicked reboot to recovery.. my phone bootlooped on recovery screen .. I pulled out the battery an put it back in.. an immediately put it into download mode( before it had a chance to bootloop recovery again ) then clicked down to cancel an restart phone.. my question is is there a link to a 4.4 kit kat compatible twrp recovery version that I can install through Odin ... an if so do I put it in the pda section.. Sorry I'm new to note 3 an Odin. .. coming from HTC lol ... thx in advance !
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
The OP of this thread has a link to a 4.4 version of TWRP you can flash through Odin. And yes, you put it in the pda section for flashing.
chico260 said:
So I was mj4 rooted .. then went back to stock .. did OTA kit kat update ... rooted using cf auto root since it was updated for 4.4 base now.. took a few seconds on Odin 3.07 showed up as reset on the screen .. phone will reboot but leave it plugged in til it says pass... Mine took a Lil over 2 mins.. anyway I then went to goo manager installed open recovery but when I clicked reboot to recovery.. my phone bootlooped on recovery screen .. I pulled out the battery an put it back in.. an immediately put it into download mode( before it had a chance to bootloop recovery again ) then clicked down to cancel an restart phone.. my question is is there a link to a 4.4 kit kat compatible twrp recovery version that I can install through Odin ... an if so do I put it in the pda section.. Sorry I'm new to note 3 an Odin. .. coming from HTC lol ... thx in advance !
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Haven't tried it personally but here is the link for it http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltespr ......got this from the http://forum.xda-developers.com/showthread.php?t=2596001 Philz recovery thread says it's for Kitkat. i'm still rockin 4.3 atm
DreamingWolf said:
The OP of this thread has a link to a 4.4 version of TWRP you can flash through Odin. And yes, you put it in the pda section for flashing.
Click to expand...
Click to collapse
Used twrp in the op of this thread in the link an flashed with Odin 3.07 .. Good to go now .. thx everyone .. Also everyone is aware that cf auto root for kit kat 4.4 base was updated correct?
Sent from my SM-N900P using Tapatalk
chico260 said:
Used twrp in the op of this thread in the link an flashed with Odin 3.07 .. Good to go now .. thx everyone .. Also everyone is aware that cf auto root for kit kat 4.4 base was updated correct?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Yup.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Deleted
micmars said:
Yup.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Is the latest twrp still 2.6.3.2 for our kit kat version ?
Sent from my SM-N900P using Tapatalk
chico260 said:
Is the latest twrp still 2.6.3.2 for our kit kat version ?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
The TWRP for KitKat I'm using is 2.6.3.2, and was the first working recovery of which I am aware that was specifically designed for Sprint Note 3 KitKat.
That stated, I'm unclear if it is the latest.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
The TWRP for KitKat I'm using is 2.6.3.2, and was the first working recovery of which I am aware that was specifically designed for Sprint Note 3 KitKat.
That stated, I'm unclear if it is the latest.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Also I was wondering. .. coming from HTC evo 4G lte. . We flashed rom zips from internal but I noticed sacs rom (which I'm on said to wipe internal). .. so on samsung we always flash from external?
Sent from my SM-N900P using Tapatalk
chico260 said:
Also I was wondering. .. coming from HTC evo 4G lte. . We flashed rom zips from internal but I noticed sacs rom (which I'm on said to wipe internal). .. so on samsung we always flash from external?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Uhm, nope. I flash everything from internal, but then I blasted out of Jellybean about a month ago, and at that time, updating to the newer operating system required a repartition of the internal memory, so the internal memory was nuked.
At that time, some very explicit instructions were lain out by me as given to me by the dev whom released the leak NA4. From what I've seen, similar instructions are being used by some roms, most likely for similar reasons.
Thus, it's most likely a one-time event for ya.
Once complete, flash away.
I downloaded a new rom today sitting at my desk at work, installed it in 5 minutes, and had it tamed to my tastes pretty quickly...all from internal memory.
My external is for media, my internal is for flashing. I suspect things will be similar for all.
I hope this helps.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Uhm, nope. I flash everything from internal, but then I blasted out of Jellybean about a month ago, and at that time, updating to the newer operating system required a repartition of the internal memory, so the internal memory was nuked.
At that time, some very explicit instructions were lain out by me as given to me by the dev whom released the leak NA4. From what I've seen, similar instructions are being used by some roms, most likely for similar reasons.
Thus, it's most likely a one-time event for ya.
Once complete, flash away.
I downloaded a new rom today sitting at my desk at work, installed it in 5 minutes, and had it tamed to my tastes pretty quickly...all from internal memory.
My external is for media, my internal is for flashing. I suspect things will be similar for all.
I hope this helps.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
So I'm not going to need to wipe internal to flash other things unless prompt to ?
Sent from my SM-N900P using Tapatalk
I'm Unclear on Your Question...
chico260 said:
So I'm not going to need to wipe internal to flash other things unless prompt to ?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I'm unclear on your question. When I upgraded to KitKat for the first time, I blasted my internal data. That was a month ago. Since that time, I have run at least 3 different KitKat roms, all from internal memory. Each install was a single wipe from within TWRP, the standard flick of the knob, which wipes system, data and dalvik. No internal memory card gets wiped, ever. Just the 3 partitions I referenced.
Gotcha I was thinking I was supposed to wipe entire internal storage every time I flashed a rom, but was thinking if that's where the rom zip is.. I'm going to lose it an twrp back ups lol.. i did wipe everything single thing in internal storage including backups before installing sacs though which sucked.. Sorry I'm a Lil slow to this.. thnx man i really really appreciate your dedication an quick response
Sent from my SM-N900P using Tapatalk
micmars said:
I'm unclear on your question. When I upgraded to KitKat for the first time, I blasted my internal data. That was a month ago. Since that time, I have run at least 3 different KitKat roms, all from internal memory. Each install was a single wipe from within TWRP, the standard flick of the knob, which wipes system, data and dalvik. No internal memory card gets wiped, ever. Just the 3 partitions I referenced.
Click to expand...
Click to collapse
chico260 said:
Gotcha I was thinking I was supposed to wipe entire internal storage every time I flashed a rom, but was thinking if that's where the rom zip is.. I'm going to lose it an twrp back ups lol.. i did wipe everything single thing in internal storage including backups before installing sacs though which sucked.. Sorry I'm a Lil slow to this.. thnx man i really really appreciate your dedication an quick response
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Thnx! Again
Sent from my SM-N900P using Tapatalk
micmars said:
My external is for media, my internal is for flashing. I suspect things will be similar for all.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I think much depends on the size of ExtSDCard the person has. I have a 64Gb SanDisk and I keep everything on it from media to flashing files (ROMs, kernels, mods, recoveries, apps). Internal is only used for day to day accumulations from running apps. When it's time to flash a ROM, I move any data I wish to save from internal to external, then wipe internal. I wipe it every single time I flash a ROM. That way I never have to worry about old data borking the new install.
Just my $.02
DreamingWolf said:
I think much depends on the size of ExtSDCard the person has. I have a 64Gb SanDisk and I keep everything on it from media to flashing files (ROMs, kernels, mods, recoveries, apps). Internal is only used for day to day accumulations from running apps. When it's time to flash a ROM, I move any data I wish to save from internal to external, then wipe internal. I wipe it every single time I flash a ROM. That way I never have to worry about old data borking the new install.
Just my $.02
Click to expand...
Click to collapse
Do you wipe everything including storage
Sent from my SM-N900P using Tapatalk
chico260 said:
Do you wipe everything including storage
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Everything - System, Data, Cache, DalvikCache, Do a Factory reset (which is actually redundant because I wipe all the items included in this individually) and wipe (or format depending on which recovery I'm using) the internal SDCard.
Everything I want to keep and/or flash ROM to ROM sits on my external card.
DreamingWolf said:
Everything - System, Data, Cache, DalvikCache, Do a Factory reset (which is actually redundant because I wipe all the items included in this individually) and wipe (or format depending on which recovery I'm using) the internal SDCard.
Everything I want to keep and/or flash ROM to ROM sits on my external card.
Click to expand...
Click to collapse
OK. . I thought you meant in advanced wipe you wipe internal storage option also
Sent from my SM-N900P using Tapatalk
chico260 said:
OK. . I thought you meant in advanced wipe you wipe internal storage option also
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I did mean that. In TWRP you wipe internal storage under the advanced options, in Philz you format the data/data (internal sdcard) under the mounts option.
I wipe EVERYTHING except bootloader, recovery, and extsdcard every time I flash a ROM.
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Markstache said:
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Click to expand...
Click to collapse
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I've done that so many times.
Markstache said:
I've done that so many times.
Click to expand...
Click to collapse
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yea that's what I said before too but the op said they've done that many times with no luck...
Sent from my SCH-I545 using Tapatalk
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
That's what I would have figured would fix it, because I'm pretty sure that's supposed to wipe /boot, but I found out I cannot flash kernels on my phone for some reason and when having to fix softbricks while experimenting with why it doesn't work and flashing different kernels, I had to do that whole process so many times I can go from softbrick back to where I'm at now in about 20 minutes.
Is your device in factory mode when using touchwiz roms?
jamesd1085 said:
Is your device in factory mode when using touchwiz roms?
Click to expand...
Click to collapse
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
jamesd1085 said:
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
Click to expand...
Click to collapse
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
Definitely don't delete your efs folder. Actually it's good practice to back it up
Sent from my SCH-I545 using Tapatalk
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
No!!!!...you will lose your number and all data capability...just wanted to make sure everything was still mounting properly... I'm at a loss as to what else could be causing your issues
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
I'd find someone like Philz or a TWRP compiler to ask if u haven't already gone that route. I'm sure one of them will know. Hopefully [emoji41]
Sent from my SCH-I545 using Tapatalk
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Markstache said:
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Click to expand...
Click to collapse
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
^^^this should fix you up...but backup everything you can to external SD or computer...when it says full wipe its no joke
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Markstache said:
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Click to expand...
Click to collapse
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As in installing a KT kernel after rooting and having a custom recovery and ROM on my phone. Right now I have three 3/22 nightly cyanogen up and running but as soon as I install kt it trips the Verizon security and on have to flash back to stock kernel to use my phone. Booting into Odin and canceling out to restart does not let me get past the yellow triangle
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
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.