Terms, Conditions, and Background
Please consider the following carefully before even thinking about flashing this ROM:
--I have no idea what I'm doing
--I have never done any dev work before this
--I only did this because no one else has done it
--Installing/flashing this ROM may brick or otherwise destroy/render your device useless
--By downloading, you hold me completely harmless and it's all on you!
ROM building process:
--I rooted the ROM and installed TWRP
--Deodexed the ROM (pulled the files, deodexed, created a .zip of the deodexed files, flashed the files back)
--Nandroid the ROM
--Extracted boot/kernel and system partition
--Renamed all the Knox stuff to .bak
--Built the flashable zip
--Tested flash on TWRP and CWM.
(a lot of search, trial and error on figuring out some of the steps)
This ROM DOES NOT wipe the data partition. So your setup will remain
This ROM already has the SD card write fix flashed to it
I made no other modifications
Credit to jovy23 -- I used his META-INF from Note 4.
If you choose to proceed and use the ROM after warnings above....
1) Do a full nandroid first. In fact, do two! Backup using TWRP or CWM.
2) Download the ROM and compare MD5 just to be sure
3) Flash using TWRP or CWM
4) Wipe cache and dalvik
5) Reboot and enjoy
6) If you get a bootloop, I wouldn't know why. Restore from backup.
Download
This ROM is only for Sprint Note Edge 915P: LINK
MD5 Here: LINK
Afterthoughts
--Please hit/say "Thanks" if you deem appropriate
--Please be nice. I don't know what I'm doing. I'm only sharing in case someone else want the same I do.
--If you can contribute and help improve this, I'm all ears.
--Please do not mirror, repost, or otherwise share without my permission.
--In case you're wondering, I wanted deodexed because it gives way to theming/customization. I also thought I read that Xposed requires deodexed in some cases.
--Did I miss anything?
Well, here goes nothing.... Enjoy.....
Just in case....
Link is up!
snovvman said:
Link is up!
Click to expand...
Click to collapse
As soon as I figure out how to get a working TWRP I will flash this! I early rooted and have no recovery at this time....
Cheers! AND BIG THANKS!
WHOA! I just attempted 3 finger salute and got TWRP to come up! I thought it was broken but it appears to be doing a Nandroid BU as I type. I always do a complete BU with Titanium BU as well so will go do that next and then try your ROM! Cheers!
beejmeister said:
As soon as I figure out how to get a working TWRP I will flash this! I early rooted and have no recovery at this time....
Cheers! AND BIG THANKS!
WHOA! I just attempted 3 finger salute and got TWRP to come up! I thought it was broken but it appears to be doing a Nandroid BU as I type. I always do a complete BU with Titanium BU as well so will go do that next and then try your ROM! Cheers!
Click to expand...
Click to collapse
You have two options:
Fully working CWM for Sprint Edge:
http://forum.xda-developers.com/not...15s-n9150-cwm-based-recovery-6-0-5-1-t2954960
Note 4 TWRP works on Edge (be sure to turn screen brightness down to 10, there will be two white bars on the side)
http://teamw.in/project/twrp2/266
Both work fine to flash zips.
Edit: Just saw your edit. If you use TWRP, disable screen timeout. For me, when the screen times out, I can't get it to turn back on.
Nice. That didn't take long now did it...
Sent from my SPH-L720 using JellyBombed Tapatalk 2
FIRST! I think.....
Well. I finally flashed it, I think. TWRP said that it completed... but it took under a minute to complete.
Also, according the "About" in settings, it indicates a Knox version at the bottom... that might be right... but I don't know.
How can I tell, since there really weren't any significant changes other than deodexing and Knox removal, if I got flashed?
beejmeister said:
FIRST! I think.....
Well. I finally flashed it, I think. TWRP said that it completed... but it took under a minute to complete.
Also, according the "About" in settings, it indicates a Knox version at the bottom... that might be right... but I don't know.
How can I tell, since there really weren't any significant changes other than deodexing and Knox removal, if I got flashed?
Click to expand...
Click to collapse
I can think of a couple of ways to check:
1) Use Root Explorer, look at /system/app, you shouldn't see and .odex files
2) Look at settings/applications/all, you shouldn't see any knox apps listed
Let me know what you find. Thanks.
NK1....
By the way, the Sprint Note Edge is now on NK1 build. I will build an upgrade path and NK1 deodexed if there is enough interest. Let me know.
snovvman said:
By the way, the Sprint Note Edge is now on NK1 build. I will build an upgrade path and NK1 deodexed if there is enough interest. Let me know.
Click to expand...
Click to collapse
I was on NK1 prior to flashing. PLEASE do a upgrade. I know I'm the only one posting here... but I hope you will award my bravery and create the NK1 file. Thanks.
---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------
snovvman said:
I can think of a couple of ways to check:
1) Use Root Explorer, look at /system/app, you shouldn't see and .odex files
2) Look at settings/applications/all, you shouldn't see any knox apps listed
Let me know what you find. Thanks.
Click to expand...
Click to collapse
1) No .odex files
2) No knox apps listed
PROFIT!
Cheers!
I'm uploading a trial of a Nk1 now. Didn't do anything to the rom yet.
I thought about continuing with a full rom with the added goodies, but I'm not sure yet.
I'm a themer not a builder, lol...but I got a great team of guys who would help me with it all.
Guess it depends on how many other devs in sprint are moving over to the edge vs the note 4.
Instead of doing all the extra work, you may want to consider using a kitchen. It will do a lot of that itself that you manually did. Just a thought bro. Good job btw:thumbup:
Sent from my SM-N900T using Tapatalk 2
beejmeister said:
I was on NK1 prior to flashing. PLEASE do a upgrade. I know I'm the only one posting here... but I hope you will award my bravery and create the NK1 file. Thanks.
---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------
1) No .odex files
2) No knox apps listed
PROFIT!
Cheers!
Click to expand...
Click to collapse
I'll need NK1 for my Edge too, so when I get it done, I'll upload it.
Thanks for letting me know that it worked.
cbucz24 said:
I'm uploading a trial of a Nk1 now. Didn't do anything to the rom yet.
I thought about continuing with a full rom with the added goodies, but I'm not sure yet.
I'm a themer not a builder, lol...but I got a great team of guys who would help me with it all.
Guess it depends on how many other devs in sprint are moving over to the edge vs the note 4.
Instead of doing all the extra work, you may want to consider using a kitchen. It will do a lot of that itself that you manually did. Just a thought bro. Good job btw:thumbup:
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
Thanks, it's been awhile since I heard that term "kitchen". I think I used one once to modify some framework. I'll look into it. Thanks.
OK. Update on the install.
No problems with the install. However. I am getting SIGNIFICANT lag across the ROM. In entering text, changing apps, swiping launcher screens, etc. Did cache wipes and such and still it persists. I had to restore my Nandroid BU.
Now. I have previously removed several of the bloatware apps and frozen a couple and I'm wondering that since this ROM is actually "Stock rooted" and those apps would have been reinstalled with the ROM... I don't know. The lag was just so frustrating that I couldn't stay with it.
When you put up NK1 I'll try it though, because MAYBE it was the NJL ROM that I hadn't ever experienced before since I did the NK1 update when I first got the phone....
Anyway. Thanks for your efforts!
beejmeister said:
OK. Update on the install.
No problems with the install. However. I am getting SIGNIFICANT lag across the ROM. In entering text, changing apps, swiping launcher screens, etc. Did cache wipes and such and still it persists. I had to restore my Nandroid BU.
Now. I have previously removed several of the bloatware apps and frozen a couple and I'm wondering that since this ROM is actually "Stock rooted" and those apps would have been reinstalled with the ROM... I don't know. The lag was just so frustrating that I couldn't stay with it.
When you put up NK1 I'll try it though, because MAYBE it was the NJL ROM that I hadn't ever experienced before since I did the NK1 update when I first got the phone....
Anyway. Thanks for your efforts!
Click to expand...
Click to collapse
Thanks for your feedback. So are you saying that your backup (factory/odexed) does not have lag? There are a couple of threads in the Edge forum re lag, take a look at those.
http://forum.xda-developers.com/note-edge/help/sooo-laggy-t2954767
http://forum.xda-developers.com/note-4-tmobile/general/experiencing-lag-t2914618
Try going to Settings/storage/ delete cached data.
I also have a T-Mo Edge that I am seeing lag. If you don't mind, test this: Stock (odexed, as shipped, from your backup), clean (no installed apps, after fresh wipe) VS. deodexed, clean (no installed apps, after fresh wipe). If under these conditions, the deodexed (and only the deodexed) still lags, I would say that something is wrong with the ROM.
Thanks.
I did a quick search:
https://www.google.com/webhp?source...&es_th=1&ie=UTF-8#newwindow=1&q=note edge lag
Take a look at the first page, it seems like Note 4s are seeing various lag too. I am seeing lag in different places on my T-Mo Edge (haven't used Sprint Edge much yet) and would like to find a solution.
NK1 for Sprint is up!
http://forum.xda-developers.com/not...-sprint-note-edge-sm-915p-nk1-rooted-t2962837
Related
I'm gonna go out on a limb here & ask a question that's been on my mind for a while, so bear with me. But first, let me give you some background so there's no confusion & no unnecessary questions asked. I'm by no means a "pro" at modifying my Note 3, I just follow instructions carefully & then implement those directions to achieve results. That's how I rooted my Note 3 but could still care less that I tripped Knox in the end.
I have the 32 GB Sprint Galaxy Note 3 with an 8 GB microSD. It's rooted using Chainfire's method. I also have TWRP for a recovery, but I'm using the stock Sprint ROM that came with it. I have a few root apps installed (Titanium backup, AdAway & Root Explorer) but the rest are what Sprint (& Android) put in there, minus a few that are totally unnecessary for me...(chat apps, picture drawings, step counting & so on) that were removed with Titanuim. It's still on 4.3 Jellybean with PUBMJ4 baseband. I also have the Wi-Fi hotspot fixed through 2 file replacements using Root Explorer.
Now that you know what I have, onto the question...
I see many, many ROMs in other threads that I'd like to try out, but don't know how to go about doing this. Before you jump right in & answer, here's my problem. If I try a ROM but don't like it, or it doesn't suit my needs, how can I go about going back to what I have now in the best (& fewest) steps necessary? In other words, to go back to exactly what ROM I have now, the apps installed, baseband, the whole nine yards. Just like a computer backup, it's a bit-for-bit restore, completely mirroring the hard drive. Understand?
Maybe you could explain to me like I'm seven years old what apps I need, what procedures are taken, the order in which they happen & so on. If I need an app or two to do just this, I have approximately $20 Google Play credit left.
Can a DEV or an experienced person that's done just this help a fellow out? Don't get me wrong, the stock ROM I'm using works for me, but there's ROMs posted that look just awesome! It's all about "personalization", am I right?
Easy, since you have a custom recovery installed (twrp) , you simply do a "nandroid" backup (I personally like to backup to an external SD card, so get a bigger one) before wiping and installing something new. If you like what you got, fine. If you want to go back, wipe and restore! Easy Peasy!
Sorry, being a father means sometimes your time suddenly becomes unavailable. But believe me, it's really easy once you figure out twrp.
I'll let another fine member get more details if you actually need them. ?
Sent from my calculator watch.
So did you figure it all out?
Sent from my SM-N900P using Tapatalk
kingdazy said:
Easy, since you have a custom recovery installed (twrp) , you simply do a "nandroid" backup (I personally like to backup to an external SD card, so get a bigger one) before wiping and installing something new. If you like what you got, fine. If you want to go back, wipe and restore! Easy Peasy!
Sorry, being a father means sometimes your time suddenly becomes unavailable. But believe me, it's really easy once you figure out twrp.
I'll let another fine member get more details if you actually need them. ?
Sent from my calculator watch.
Click to expand...
Click to collapse
Doing a Nandroid backup as we speak! I didn't realize TWRP could do that. (duh! ) I only installed TWRP because I just liked the name of it. TWERP!! (gotta nice sound to it, doesn't it??) Thanks a bunch! :good:
tonyevo52 said:
So did you figure it all out?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I did. I found a Youtube link on how to do a TWRP backup on the Sprint Note 3. Easy Peasy as said above! I'll try some ROMs this weekend (can't promise nuthin' cause it's gonna be 70 degrees this weekend & I'm itchin' to ride my mountainbike along the boardwalk at the Virginia Beach.)
But now that the hard part is outta the way, it's all easy street from here!
Just be sure to Please, oh god Please, read all instructions on any rom you decide to try. Doesn't hurt to read the last 10 pages of each too, get an idea of Current issues that may not be documented in the OP.
And don't get lazy, follow word for word. The only times I f*cked stuff up was when I didn't follow instructions (ie, thought my experience meant I knew best), or just got sloppy.
And, don't forget to wipe! (I wipe 3X, everytime, as a habit. Some people will give you reasons why that's unnecessary, but I can say confidently, if perhaps anecdotally, that I Never have the issues others have with bad flashes, softbricks, FCs, etc.)
Something to get comfortable with, even though you may never need it is ODIN. It's most common use is a utility for flashing stock ROMs and firmwares, great for recovery from bad things. Again, you may never need it, but have it ready in your Pc with a stock ROM file, just in case.
Finally, Titantium Backup can be your best friend, if used properly. It can also be a real pain, so don't become too dependant on it.
FIN
Sent from my calculator watch.
kingdazy said:
Just be sure to Please, oh god Please, read all instructions on any rom you decide to try. Doesn't hurt to read the last 10 pages of each too, get an idea of Current issues that may not be documented in the OP.
And don't get lazy, follow word for word. The only times I f*cked stuff up was when I didn't follow instructions (ie, thought my experience meant I knew best), or just got sloppy.
And, don't forget to wipe! (I wipe 3X, everytime, as a habit. Some people will give you reasons why that's unnecessary, but I can say confidently, if perhaps anecdotally, that I Never have the issues others have with bad flashes, softbricks, FCs, etc.)
Something to get comfortable with, even though you may never need it is ODIN. It's most common use is a utility for flashing stock ROMs and firmwares, great for recovery from bad things. Again, you may never need it, but have it ready in your Pc with a stock ROM file, just in case.
Finally, Titantium Backup can be your best friend, if used properly. It can also be a real pain, so don't become too dependant on it.
FIN
Sent from my calculator watch.
Click to expand...
Click to collapse
No worries! As I said in the OP, I follow directions carefully. I read everything.
Odin is my friend as well. I have it installed on my laptop. That's how I flashed basebands & deodexed stock rooted ROMs on my Galaxy S III. I also have the original stock Sprint ROM for this GN3 "just in case", in a folder sitting on my desktop with a few extra tools. I've never bricked a phone, unless you count using Samsung's online update (can't think of the name at the moment). It said 4.3 was available, so I downloaded it. It flashed, rebooted, but stuck there. Never finished the boot, just gave me an error code. Samsung's own update killed my GS3 & was unrecoverable. Believe me, I tried everything. What was strange, was the ROM was 4.3 but the baseband was the previous version, not the newer one, so the phone just puked. It never updated the baseband so it bricked. Now, I tried (and used) different radios with no problems before the update. Everything worked in harmony. Go figure!
Time for sleep my friend. Gotta work in the morning!
Carrier: Verizon
Device: Samsung Galaxy S4 (MK2)
Custom ROM: Hyperdrive ROM
Phone is rooted, and Safestrap is installed and working flawlessly
I see this question posted all the time, but I'm reading a lot of conflicting information. As I've been searching around the net for a solid (and up-to-date) answer, I was wondering if there was a definitive answer to the following question:
Can I flash a custom ROM to the stock slot using Safestrap, remove the stock ROM from the phone, and keep the backup on my PC for later restoration?
I would assume that I should do the following:
1) Make a backup of the stock ROM (using Safestrap)
2) Wipe the Stock slot
3) Install/Restore custom ROM to the Stock slot
Am I correct in assuming this?
If there are any issues, I'd love to hear why. I'm still trying to figure out all the info. If there are any benefits/drawbacks, I'd also love to hear those. I'd consider myself a "conservative" user. I do nothing with themes and major modifications.
Thank you for any advice!
I apologize if this question has been answered elsewhere.
That works just fine and many people already have. AT&T people are in the same boat and do it too.
Sent from Black<3's I337 running Foxhound ROM
DeadlySin9 said:
That works just fine and many people already have. AT&T people are in the same boat and do it too.
Sent from Black<3's I337 running Foxhound ROM
Click to expand...
Click to collapse
Thank you for the information.
remainnameless said:
Thank you for the information.
Click to expand...
Click to collapse
Just make sure you have the Odin tar file for your phone just in case something goes wrong. Me and a few others ran into some issues messing with the stock slot. Good idea to have that anyways.
Sent from my SCH-I545 using Tapatalk
Just in case someone comes across this in the future:
Everything worked as planned. No issues to report.
But doesn't this entirely contradict what the website says?
On the How-To Safestrap site:
Install: This is for flashing a .zip file to the currently active system. Currently, this is disabled for the stock system. In a future release I will enable flashing to the stock system.
Click to expand...
Click to collapse
And yet people are wiping and flashing to stock fine?
Cool, I will try that
Sent from my SCH-I545 using XDA Premium HD app
DaGamer12345 said:
But doesn't this entirely contradict what the website says?
On the How-To Safestrap site:
And yet people are wiping and flashing to stock fine?
Click to expand...
Click to collapse
Hashcode didn't support flashing to the stock slot when I used SafeStrap. You could do it, but if you ran into problems you were not to expect any help from him.
Now whether or not he disabled that option completely in newer versions of SafeStrap I'm not really sure since I'm on an mdk S4 now.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Hashcode didn't support flashing to the stock slot when I used SafeStrap. You could do it, but if you ran into problems you were not to expect any help from him.
Now whether or not he disabled that option completely in newer versions of SafeStrap I'm not really sure since I'm on an mdk S4 now.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
reason why its called safestrap...and has saved me many times able to get back to my stock rom slot...but we all have our own levels of risk but hashcode made safestrap the way he did for a reason.
I run 3 roms on my S4 and have no issues with memory limitations
So then this is a yes on flashing to stock? Thinking about flashing a SS rom, but not sure how it goes.
I assume I would flash the kernel modules as you have to do that with every custom rom.
If Safestrap lives on the stock system, how does it stay after you wipe? It stays on an unwipe-able area? Because it can't stay on recovery, can it?
If anything goes wrong, I could just flash the MK2 stock with Odin, correct? It wouldn't trip KNOX flag to 0x1?
Out of curiosity, if an OTA was available for stock MK2, and I had it as a custom rom, it would brick the phone or what would happen?
In Titanium Backup, you DON'T restore all the system apps, and only the user apps when migrating roms?
This would be my first time wiping/flashing a rom over the system (and not just over a rom slot), so I'm nervous as almost all people new to this sort of thing.
DaGamer12345 said:
So then this is a yes on flashing to stock? Thinking about flashing a SS rom, but not sure how it goes.
I assume I would flash the kernel modules as you have to do that with every custom rom.
If Safestrap lives on the stock system, how does it stay after you wipe? It stays on an unwipe-able area? Because it can't stay on recovery, can it?
If anything goes wrong, I could just flash the MK2 stock with Odin, correct? It wouldn't trip KNOX flag to 0x1?
Out of curiosity, if an OTA was available for stock MK2, and I had it as a custom rom, it would brick the phone or what would happen?
In Titanium Backup, you DON'T restore all the system apps, and only the user apps when migrating roms?
This would be my first time wiping/flashing a rom over the system (and not just over a rom slot), so I'm nervous as almost all people new to this sort of thing.
Click to expand...
Click to collapse
Well, you're asking a lot of questions that have been already answered, so here's some quick answers.
1. Flashing the modules won't hurt.
2. Safestrap lives in separate directory on your internal storage. As long as you don't wipe the internal storage, it'll still be there. However, if you flash a stock ROM into the stock slot, then Safestrap won't be run during boot and can't be activated.
3. Yes, you can always flash an OEM stock ROM. Factory images from Samsung won't set the Knox Warranty Void flag. This does NOT mean that you can downgrade to an earlier release.
4. OTAs won't brick the phone - they'll fail if you have modified anything that the OTA will be patching.
5. You should only restore user apps and data. You must have the restorecon fix for that to work. Restoring system apps is pretty risky.
None of these are new questions or new answers. Yes, there's a lot to read here, but you really need to spend the time.
k1mu said:
Well, you're asking a lot of questions that have been already answered, so here's some quick answers.
1. Flashing the modules won't hurt.
2. Safestrap lives in separate directory on your internal storage. As long as you don't wipe the internal storage, it'll still be there. However, if you flash a stock ROM into the stock slot, then Safestrap won't be run during boot and can't be activated.
3. Yes, you can always flash an OEM stock ROM. Factory images from Samsung won't set the Knox Warranty Void flag. This does NOT mean that you can downgrade to an earlier release.
4. OTAs won't brick the phone - they'll fail if you have modified anything that the OTA will be patching.
5. You should only restore user apps and data. You must have the restorecon fix for that to work. Restoring system apps is pretty risky.
None of these are new questions or new answers. Yes, there's a lot to read here, but you really need to spend the time.
Click to expand...
Click to collapse
Oh I remember you! You made the Saferoot method I used. Sorry for asking some dumb questions, I just wanted verification for 1, 3, and 4. I'll have to search for the restorecon fix. I'll be flashing Eclipse because I was only looking for an AOSP experience and Hyperdrive has more than I need (leading to larger rom size). The rom is going to go through a big update sometime this weekend so I'll wait for the update.
DaGamer12345 said:
Oh I remember you! You made the Saferoot method I used. Sorry for asking some dumb questions, I just wanted verification for 1, 3, and 4. I'll have to search for the restorecon fix. I'll be flashing Eclipse because I was only looking for an AOSP experience and Hyperdrive has more than I need (leading to larger rom size). The rom is going to go through a big update sometime this weekend so I'll wait for the update.
Click to expand...
Click to collapse
Whew. I thought "Oh I remember you" was going to be followed by ".. you're that jerk that... " :laugh:
Have a good weekend.
remainnameless said:
Carrier: Verizon
Device: Samsung Galaxy S4 (MK2)
Custom ROM: Hyperdrive ROM
Phone is rooted, and Safestrap is installed and working flawlessly
I see this question posted all the time, but I'm reading a lot of conflicting information. As I've been searching around the net for a solid (and up-to-date) answer, I was wondering if there was a definitive answer to the following question:
Can I flash a custom ROM to the stock slot using Safestrap, remove the stock ROM from the phone, and keep the backup on my PC for later restoration?
I would assume that I should do the following:
1) Make a backup of the stock ROM (using Safestrap)
2) Wipe the Stock slot
3) Install/Restore custom ROM to the Stock slot
Am I correct in assuming this?
If there are any issues, I'd love to hear why. I'm still trying to figure out all the info. If there are any benefits/drawbacks, I'd also love to hear those. I'd consider myself a "conservative" user. I do nothing with themes and major modifications.
Thank you for any advice!
I apologize if this question has been answered elsewhere.
Click to expand...
Click to collapse
I just installed hyperdrive to the stock slot and everything works perfect.
I am about at my wits end...Rewind to two days ago...
Order of events:
1. Received my new S4 in the mail a few days ago to replace my old S3. I received the S4 fully updated with the NC5 OTA (yeah, I know, bad juju).
2. So I followed Surge's downgrade thread HERE and am now downgraded to the MK2 build, but with no sound and the telephone/calls app does not work.
3. I then downloaded GooManager and installed the OpenRecovery from TWRP, and it said it installed correctly. However, now I CANNOT GET INTO RECOVERY no matter how I try (via VolUp+Home+Power or via "Reboot into recovery" from the GooManager app). It just goes into Download mode with an error at the top in re that says "Could not do normal boot"
4. At this point the phone just boot loops into Download mode. Cannot go into recovery or the MK2 Rom. I then have to reflash the MK2 downgrade files in order (downgrade, system, cache) in order to get a working phone again and I have now probably done this at least 8 times. It is getting old.
So, I am curious what I need to do now. I have gone through the MK2 downgrade process multiple times and tried again to no avail. I also tried flashing the TWRP .Tar file (directly via Odin) but no luck also --- Is there like a super/clean ODIN file I can use that will also reset the recovery image on the phone? I feel that is my main problem, then I can fix the sound/phone problems after that.
This thing is 10x harder to get on CM than the S3 which I had running CM within 2 hours of ownership. I'd appreciate any help to get me back on path.
FYI - I can install Safestrap 3.71/3.72 and get into those fine, but if I want a chance of running CM I will need a Loki recovery right? If so, I just do not see how I am going to get there.
My ultimate goal is a clean rom, and I was so used to CM on my S3 that I'd hate to part with that, but if there is a Safestrap-friendly ROM that is very clean/similar, then I will take that any day. Ready to be done with this - easiest way out.
--edit--
Found this...can I just follow these steps or is that only for people still on MDK?? http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
There's absolutely no way to get cm, aosp, or twrp on your device .
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
There's absolutely no way to get cm, aosp, or twrp on your device .
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah, pretty sure I am convinced of that now. :crying:
So, should I upgrade to the rooted-NC5 (Surge's method), and THEN put a Safestrap-custom-ROM on, or just do it now running rooted-MK2?
crobs808 said:
Yeah, pretty sure I am convinced of that now. :crying:
So, should I upgrade to the rooted-NC5 (Surge's method), and THEN put a Safestrap-custom-ROM on, or just do it now running rooted-MK2?
Click to expand...
Click to collapse
Well it depends. If you stay on mk2 you can only run 4.3 roms but there's a lot of them. If you upgrade then you can run 4.4 roms but there's only a couple right now.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
Well it depends. If you stay on mk2 you can only run 4.3 roms but there's a lot of them. If you upgrade then you can run 4.4 roms but there's only a couple right now.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I definitely want 4.4.x. I found THIS one called PurifieD (port by gogolie) which is supposed to be clean-ish. We'll see: http://www.androidfilehost.com/?fid=23487008491966540
-edit-
^ hmm, no mirrors may try Fox and Hound instead:
http://www.androidfilehost.com/?fid=23487008491966537
^ and again...no mirrors.
Is there a consolidated link list of SS-compatible ROMs for the S4, or do I have to hunt and peck through the forum?
n/m - found a list of 4.3 roms, but it looks like I will have to hunt for 4.4 roms individually.
Conclusion: Going to try this rom: http://forum.xda-developers.com/showthread.php?t=2596654
I think I will sleep well tonight (crosses fingers)
crobs808 said:
I definitely want 4.4.x. I found THIS one called PurifieD (port by gogolie) which is supposed to be clean-ish. We'll see: http://www.androidfilehost.com/?fid=23487008491966540
-edit-
^ hmm, no mirrors may try Fox and Hound instead:
http://www.androidfilehost.com/?fid=23487008491966537
^ and again...no mirrors.
Is there a consolidated link list of SS-compatible ROMs for the S4, or do I have to hunt and peck through the forum?
n/m - found a list of 4.3 roms, but it looks like I will have to hunt for 4.4 roms individually.
Conclusion: Going to try this rom: http://forum.xda-developers.com/showthread.php?t=2596654
I think I will sleep well tonight (crosses fingers)
Click to expand...
Click to collapse
only a handful, so not that hard to locate in dev forum. Until hashcode comes out with a safestrap for verizon that enables rom slot creation for custom rom installs on 4.4 base phones I know many of us are staying clear of kitkat.
good luck
So I have not used Safestrap since my Moto X days a few years back, and I am having problems installing a new ROM. Here are my steps, please tell me if things have changed because I got unexpected results.
1. While running stock NC5 (rooted+SS installed), copied custom ROM (SS-friendly FoxHound port by gigili) and SU over to my internal sdcard (do not have an external as I never needed one for the S3)
2. Booted into SS and created a ROM slot in rom-slot1
3. Gave it the nickname FoxHound
4. Selected that rom-slot to be active, then went into advanced Wipe, and did Data, Cache, System, Dalvik
5. Went back to the Install menu so I could install the new ROM but there were no files. Actually, I found out it wiped my StockRom slot even though I have made the rom-slot1 active. Why?
Anyway, now I am back to a wiped stock NC5 and have to do this all over again. Am I supposed to not do step 4 (wipe) after I create the ROM slot? and Am I supposed to just install the custom rom in the Stock slot?
Ugg forget it. I now tried flashing the custom ROM on the safe side without doing the WIPE step and just got a rom that looked identical to the stock except that DATA was broken. Forget this - I guess I just have to live with stock rooted, and modify/freeze apps.
I bought a note 3 thats rooted already and ive rooted a device before but this root or maybe the kitkat version does not give me 4glte i currently have lidroid official v1.5.1 it has a lot of features i like anything similar that comes with kitkat 4.4.4? i tried the freze rom and its not letting me load it to the phone for some reason any help or input is appreciated thanx
P.Dub said:
I bought a note 3 thats rooted already and ive rooted a device before but this root or maybe the kitkat version does not give me 4glte i currently have lidroid official v1.5.1 it has a lot of features i like anything similar that comes with kitkat 4.4.4? i tried the freze rom and its not letting me load it to the phone for some reason any help or input is appreciated thanx
Click to expand...
Click to collapse
It appears you are running an outdated version of this rom here http://forum.xda-developers.com/showthread.php?t=2485607 if you like the rom down load the latest version and flash with odin. Who is your carrier ? This rom is for SM-N9005 which is AT&T ? As far as 4G LTE go settings/general/system update/update PRL then power down and reboot the device.
If your on a Sprint carrier I would get back to stock NC5 rooted, this thread will answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
jimzweb1 said:
It appears you are running an outdated version of this rom here http://forum.xda-developers.com/showthread.php?t=2485607 if you like the rom down load the latest version and flash with odin. Who is your carrier ? This rom is for SM-N9005 which is AT&T ? As far as 4G LTE go settings/general/system update/update PRL then power down and reboot the device.
If your on a Sprint carrier I would get back to stock NC5 rooted, this thread will answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
Click to expand...
Click to collapse
yea i have sprint and already tried to update the prl i tried another rom with kitkat4.4.4 and it gave me 4glte but it kept crashing on me so switched back im going to take a look at the link you suggested thanx
P.Dub said:
yea i have sprint and already tried to update the prl i tried another rom with kitkat4.4.4 and it gave me 4glte but it kept crashing on me so switched back im going to take a look at the link you suggested thanx
Click to expand...
Click to collapse
This is what I would do. First odin flash back to NC5 stock unrooted. Then boot into stock recovery and do a factory reset. Next odin flash NC5 stock unrooted .tar again, then boot into download mode it should look like this
with official on both lines, sometimes it shows official on one line and custom on the other. That will give you headaches later. Now go ahead root, and install a recovery, beloat the stock rooted rom, for use as a daily driver, and make sure nothing crashes. Next make a backup so you have base to work from. Follow the instructions on the thread I listed above. I know this seems like a pain, but somewhere part of that AOSP rom is being left behind and causing your install of a stock rom to crash.
So I searched and found a ROM its nice and simple but now WiFi doesn't work ?
Sent from my SM-N900P using XDA Free mobile app
P.Dub said:
So I searched and found a ROM its nice and simple but now WiFi doesn't work ��
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Well thats no good!!! What are you looking for in a rom functionality for customization? Touch wiz or some like CyanogenMod? Can you upload a screenshot of what your device is running? Like 4.4.2 or 4.4.4? Do you have custom recovery?
Goat1378 said:
Well thats no good!!! What are you looking for in a rom functionality for customization? Touch wiz or some like CyanogenMod?
Click to expand...
Click to collapse
I want something similar to what I have. The rom I just tried was the cyanogen and wifi didn't work with it and it kept rebooting after an 1 hr of trying it on my phone.... main reason I want to switch is to get the 4glte I like the ability of not holding down the buttons to go into recovery
Sent from my SM-N900P using xda app-developers app
P.Dub said:
I want something similar to what I have. The rom I just tried was the cyanogen and wifi didn't work with it and it kept rebooting after an 1 hr of trying it on my phone.... main reason I want to switch is to get the 4glte I like the ability of not holding down the buttons to go into recovery
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
So you like aosp roms? Ok are you on NC5 or NH7? The screenshots in my last post will show you what you look for under setting/general/about device
Yes custom recovery I believe. And 4.4.2
Sent from my SM-N900P using xda app-developers app
P.Dub said:
Yes custom recovery I believe. And 4.4.2
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Do you have a pc with odin?
Yes sir I do
Sent from my SM-N900P using xda app-developers app
P.Dub said:
Yes custom recovery I believe. And 4.4.2
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Do you want update your firmware to NH7 or stay NC5?
Would like to update. I would need a new rom correct?
Sent from my SM-N900P using xda app-developers app
P.Dub said:
Would like to update. I would need a new rom correct?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Hey Pedro,
I put together this post when helping another person out on another thread. I think it'll work as a step-by-step guide for you:
I'll explain how to install a custom ROM and some common things to think about/check prior to installing anything:
Installing a Custom ROM
Step 1 - Gather Information
First off, you need to know what version of Android your phone currently is running. This is easily done by looking in the Settings Menu -> General -> About Device.
The Main things we are looking at on this screen are Software Version, Model Number, Android Version, and Baseband Version. I'll explain these (to the best of my knowledge) below:
Software Version:
This is the "type" of Android that you're running. Rather than quoting the entire name, we typically only refer to the last 3 characters (MJ4, NAB, NC5, etc.). Stock Note 3 devices will (most-likely) be running one of 3 different versions of TouchWiz (TW):
MJ4 - This is the last Jellybean version of TW for the Sprint Note 3NAB - This is the first KitKat TW version for the Sprint Note 3NC5 - This is the second KitKat TW version for the Sprint Note 3NH7 - This is the latest KitKat TW version for the Sprint Note 3
The reason that we are concerned with the Software Version is that between the MJ4 and NAB versions, there were major changes. So if you're running MJ4, you will have to do additional steps before flashing a custom ROM based on a newer version. And if you're on NAB or NC5, you will not be able to go back to MJ4, so beware what you're flashing.
For the most part, if you're on NH7, you can flash either a NH7 or NC5 custom ROM, but just read the ROM's FAQ to see if there are any issues with doing so.
Model Number:
Most people don't worry about this, but I always do when looking at a new ROM. The Sprint Note 3 is different from the Verizon Note 3, which is also different from the International Note 3. It's always best to double-check that the ROM you're trying to install is truly meant for your device. This simple check will prevent a LOT of potential issues you'll get when installing a ROM.
Android Version:
This is just an additional check to the Software Version. Always best to know.
Baseband Version:
The Baseband is, unless I'm mistaken, the "kernal" for the phone's cellular and 4G radios. Sometimes upgrading (or downgrading) the Baseband can help with signal strength and reception. Some users have noted that they got better reception on older Baseband versions. I haven't personally looked into it and the reports from other users seem somewhat anecdotal, but it's good to know which Baseband you're on.
The Baseband is independent from the ROM version, so you can run an older Baseband (MJ4 or NAB) on a newer ROM (NC5), and vice-versa.
The last bit of information you need to know is the Bootloader Version. The way to find this information is to reboot your device. When you see the text on the screen, you should look for the Bootloader Version. It'll be a long string of characters, but you're only looking for the last 3 (MJ4, NAB, or NC5).
Once you have all the above information, you should be ready to start the fun process of preparing your phone to flash your first ROM.
Step 2 - Backup your Media
First thing: Backup all of your media to your computer. If there's pictures/music/videos/recordings you don't want to lose, back them up. It's just good practice. Don't lose all your cat pictures because you flashed something and it somehow erased your internal storage. I tend to keep everything of importance on the External Storage, but there are times where even external storage can be wiped, so it's best to back up everything to a PC.
Step 3 - Upgrade your Phone to the latest Stock ROM (NH7)
This only is a MUST applies if you're running an older version and want to install a NH7 ROM. Most continually-developed ROMs are either NC5 or NH7 now, so the first things first: Update your phone to NH7.
Go over to micmar's thread and download the One-Click File. It will remove Root, but don't worry, because when you install a new ROM, it will automatically include root access.
Follow the instructions in his thread and your phone will now be fully upgraded.
At this point, your "About Device" should show the following:
Software Version: N900PVPUCNH7
Android Version: 4.4.4
Baseband Version: N900PVPUCNH7
Reboot your phone and let it sit for a minute so it can get it's bearings.
Step 4 - Install a Custom Recovery
So far, we've been flashing everything in ODIN. Now, we're going to use ODIN one last time to flash a custom recovery, so that you can flash custom ROMs without the need of a computer.
The most-commonly used Custom Recovery is TWRP (XDA Link). You'll want to use the latest version, 2.8.0.
Flash this in ODIN. You should use the "PDA" or the "AP" Slot.
Reboot your phone to make sure it works correctly.
Step 5 - Make a Nandroid Backup of your device
If you don't know what a Nandroid backup is, don't worry. It's basically just taking your phone as is and making a backup of it. In case you make a mistake or flash a bad download of a ROM, this allows you to restore your system. I always keep my backups on the External Storage (microSD Card), so in case I have to wipe my internal storage, it's not a big deal. You can also copy the files over to your PC, just to be more paranoind about your nandroid backups (rhyming is fun!).
You do this by restarting into Recovery (power down device, hold down home button and volume up while powering on phone).
Once in TWRP, go to "backup." Make sure the storage selected is "external storage." This screen will have various options of what to backup. I typically choose everything except external storage. Typically, backups range from 1-2 Gigs.
For me, backups typically take 5-10 minutes to do. In my opinion, this is totally worth it, since I can always restore a backup with no issues.
Step 6 - Install a Custom ROM
Once you choose your custom ROM from the Development Section, follow the instructions on the original post to install it. I'll give a general outline of what I do whenever installing a new ROM, but sometimes a custom ROM will have specific instructions, so you want to make sure to read the posts carefully.
Generic Instructions for Installing a ROM:
Download ROM and check the md5
Internet being spotty in my area, I always check the md5 to make sure that the file downloaded correctly. You can check the md5 using this windows program or using a file explorer on your phone like ES File Explorer. I always copy the ROM zip file to my external SDcard.
Reboot to Recovery
Wipe Data, System, Cache, and Dalvik Cache
This is called a "Clean Wipe," meaning it will wipe out your installed Apps and the data associated with them. Some people will claim that "Dirty Flashing" (i.e. not wiping the above) is OK, but I've seen too many apps Force Closing (FC-ing) when dirty flashing. Also, if you dirty-flash and encounter an issue with a ROM, the first piece of advice is to do a clean install. Might as well do that initially and hopefully not run into any issues.
Install the Custom ROM
Pretty straight-forward on how to do this... just click "Install" and then browse to the place your copied the ROM zip file.
Reboot your phone and run through the typical initial start-up information (google account, etc).
Once you get your phone set up the way you like (apps, accounts, wifi passwords, etc), I'd make another Nandroid backup, just so you have one where it's setup with everything you need. This will make any issues less painful, since you'd restore a backup that's already setup.
Step 7 - Further Considerations
If you ever want to try a new ROM, all you have to do is repeat step 6. Beware, though, people easily become flashaholics when they first figure this stuff out.
If you were paying attention to my "Generic Instructions" when installing a ROM, you'd notice that every time you do a Clean Install of a ROM, you lose all your apps... All of your Angry Birds 3-Star levels are gone!
Well, there are ways to get prevent losing that data... One is by "Dirty Flashing" (Not wiping the "system" or "data" partitions before flashing a ROM in TWRP). This is common practice among users here on XDA, but is typically frowned upon by ROM devs. I've noticed that a good number of issues on ROM threads stem from people Dirty Flashing. It typically causes more problems than it solves.
The other way of backup up and restoring app data (prior to wiping) is by using Titanium Backup. I could write up a long post on how to use Titanium Backup (TiBu), but the main things to remember are the following:
White line items are fine to be restored (both Data and Apps).
Restoring Yellow line items is typically OK (Data only).
Restoring system apps or data (red line items in TiBu) is typically a bad idea.
I've been using TiBu for the past 2-3 years and it's typically worked like a charm. Sometimes, when there's a major Android Update (like from JellyBean to KitKat), it can become broken, but the Developer is really responsive and gets it to work within a few weeks. If you upgrade to PRO, you can schedule automatic app backups (I backup all my user apps every night at 3am). You can also restore apps/data from Nandroid Backups (which is great if you do a Nandroid backup but had forgotten to update your TiBu backups).
In Summary
Whew, that was a lot to write... I'm a Structural Engineer, not a Software Engineer, so I don't know the technical side of things like bootloaders or basebands, but hopefully none of the information I provided was false.
Anyways, let me know if you have any problems with the install. I appreciate any feedback!
Click to expand...
Click to collapse
Since you're looking for AOSP ROMs, I'd recommend looking into this section of the forums. You need to make sure whichever ROM you are looking into works for the Sprint version of the phone (HLTESPR).
Alright so I used the last posts links and upgraded to 4.4.4 but now my data doesn't work
This is a Backup of the PH1 ROM's system and modem partitions. This is a Pre-Rooted ROM with the SD Card write permissions fix. This is different from my other post in those two differences.
You will need a custom recovery to install this ROM. (http://forum.xda-developers.com/note...lipop-t3089382)
Always perform the appropriate backups and other steps just in case something messes up. If you are on Lollipop, you should be able to just flash and go without any data loss (except custom system apps), but no promises.
Extract the folder (ES File Explorer or 7 Zipper) to "extsdcard/TWRP/backups/[serial number]" then boot into recovery and restore the image. The easiest way to get this folder is to simply perform a backup first, then unzip this folder next to the one for the backup you just created.
I didn't factory reset prior to this backup because it's just system partitions, so let me know if there's anything weird.
https://drive.google.com/open?id=0B2iEgzRTFjrQa2JEbE1DSE9qNHM
Here's the Odin ROM:
http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178/page1
Here's my non-rooted TWRP ROM:
http://forum.xda-developers.com/not...stom-recovery-rom-stock-rooted-t3449321/page1
Still 5.0 this is probably just a security update
RDF
http://device.sprintpcs.com/Samsung/SM-N900P-SPRINT/PH1.rdf
evilvoice said:
Still 5.0 this is probably just a security update
RDF
http://device.sprintpcs.com/Samsung/SM-N900P-SPRINT/PH1.rdf
Click to expand...
Click to collapse
Yep, just a security update most likely. Looks like some of the stock (Sprint) apps may have been updated as well . The update file was only about 190 megabytes if I remember correctly.
Quick question on updating modem & firmware.. I'm stock rooted ok2, and i dont have this update yet. I am working toward flashing the newly released and highly anticipated DL Modded N5N7 v4 which requires the PH1 updated firmware.
Do I need to ODIN flash the update files from the other PHI ROM thread or can I just do a full wipe and flash this backup with TWRP?
Thanks in advance.
Sent from my SM-N900P using XDA Labs
MeAtKeRtN said:
Quick question on updating modem & firmware.. I'm stock rooted ok2, and i dont have this update yet. I am working toward flashing the newly released and highly anticipated DL Modded N5N7 v4 which requires the PH1 updated firmware.
Do I need to ODIN flash the update files from the other PHI ROM thread or can I just do a full wipe and flash this backup with TWRP?
Thanks in advance.
Sent from my SM-N900P using XDA Labs
Click to expand...
Click to collapse
You can just flash the rom you want and keep your current bootloader/modem. But it's always suggested to keep current with any bootloader/modem, that the OP mentioned. That way if there is a issue with the install, it wouldn't be that.
Sent from my Nexus s using XDA-Developers mobile app
jhunt75 said:
You can just flash the rom you want and keep your current bootloader/modem. But it's always suggested to keep current with any bootloader/modem, that the OP mentioned. That way if there is a issue with the install, it wouldn't be that.
Sent from my Nexus s using XDA-Developers mobile app
Click to expand...
Click to collapse
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
MeAtKeRtN said:
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
Click to expand...
Click to collapse
Hey, I've seen you in a few threads and figured I ask before I made the same mistake. I'm looking to upgrade to DL Modded N5N7 v4 like yourself. I have a exploding Note 7 still and I'm anticipating being blacklisted at some point. As crazy as it sounds I like my Note 3's snappiness and everything else over the 7. My issue is my Note 7 radio gets 4g in my job and my Note 3 radio is 3g or spotty. I'm sure my modem and baseband is outdated and may help being updated
I'm on a older Moars Rom Baseband Nk4 android version 4.4.2. Did you figure out where things went bad. I was thinking of following these instructions http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178 don't want to mess this up.
What did you use and what should you have used?
Thanks
Lyvewire said:
Hey, I've seen you in a few threads and figured I ask before I made the same mistake. I'm looking to upgrade to DL Modded N5N7 v4 like yourself. I have a exploding Note 7 still and I'm anticipating being blacklisted at some point. As crazy as it sounds I like my Note 3's snappiness and everything else over the 7. My issue is my Note 7 radio gets 4g in my job and my Note 3 radio is 3g or spotty. I'm sure my modem and baseband is outdated and may help being updated
I'm on a older Moars Rom Baseband Nk4 android version 4.4.2. Did you figure out where things went bad. I was thinking of following these instructions http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178 don't want to mess this up.
What did you use and what should you have used?
Thanks
Click to expand...
Click to collapse
My mistake was following bad advice and flashing the TWRP Backup of PH1 in the OP of this thread instead of ODIN flashing the full ROM-ODIN-PH1- Update- t3463178.
I was able to get TWRP to restore my backup to OK2. From there I did a full wipe 3x and ODIN flashed the full PH1 update, immediately rooted with CFautoroot and reinstalled TWRP 2.8.7.0.
From there I followed the OP instructions in the DL Modded N5N7 thread which require the ROM, Kernel Cleaner, MVNO Buzbee2, Sprint VVM, and I installed the DL MM UIX Kernel.
The ROM and kernel are both really well put together except my mobile network connection to Sprint has been intermittent... the phone was stuck roaming and was connecting in spurts with Verizon, sprint, or the network was unavailable.
I just dirty flashed the Rom, Kernel, and MVNO fix an hour or so ago and the APNs seem to be sticking now. We'll see.
I have three Note 3's and each has its own quirky 'personality'- not especially playing nicely with most of the Port ROMs available these days. Hope this answers your questions and helps someone else trying to keep their Note 3 thriving.
MeAtKeRtN said:
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
Click to expand...
Click to collapse
I am not trying to start any trouble, but from reading your comment it seems you are suggesting I gave you bad or wrong advice. So I want to explain myself just in case it was a misunderstanding. All roms are capable of being flashed with older bootloaders and modems. But the proper thing to do, is to always be up to date with all bootloader/modem files. This way you will not run into any problems. Now I didn't mention anything about flashing the OP'S twrp backup method. I figured you may have been experienced enough to flash these BL/modem files from a source like sammobile. Then proceed to flash your rom of choice. As you experienced you lost your signal. It may have been a few reasons why this happen. 1. The way the OP mentioned to flash wasn't meant for your phone. Every phone response differently. 2. The rom for whatever reason can only be used if you dirty flashed over your current system. This will not be the only time you may have to do it this way. So instead of being sarcastic with your reply, maybe try and ask the one who is helping you to explain themselves more. We are all here to help each other, and by no means was my response to your question was meant to harm your phone.
Sent from my SM-N920C using XDA-Developers mobile app
jhunt75 said:
I am not trying to start any trouble, but from reading your comment it seems you are suggesting I gave you bad or wrong advice. So I want to explain myself just in case it was a misunderstanding. All roms are capable of being flashed with older bootloaders and modems. But the proper thing to do, is to always be up to date with all bootloader/modem files. This way you will not run into any problems. Now I didn't mention anything about flashing the OP'S twrp backup method. I figured you may have been experienced enough to flash these BL/modem files from a source like sammobile. Then proceed to flash your rom of choice. As you experienced you lost your signal. It may have been a few reasons why this happen. 1. The way the OP mentioned to flash wasn't meant for your phone. Every phone response differently. 2. The rom for whatever reason can only be used if you dirty flashed over your current system. This will not be the only time you may have to do it this way. So instead of being sarcastic with your reply, maybe try and ask the one who is helping you to explain themselves more. We are all here to help each other, and by no means was my response to your question was meant to harm your phone.
Click to expand...
Click to collapse
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
MeAtKeRtN said:
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
Click to expand...
Click to collapse
I never knew giving someone detailed information was a problem. It's funny how I never had an issue with the install, but you did. It seems you lack enough experience to realize a few things. But I will make it a point to never help you again. Whether that's to long-winded or not for you, oh well.
Sent from my SM-N920S using XDA-Developers mobile app
MeAtKeRtN said:
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
Click to expand...
Click to collapse
Did you get it all figured out?
I did get it figured out. Wasn't much more than an unnecessary inconvenience that someone else might be able to avoid.
Ok, so something weird...
Im running KK4.4.2 with the NC5 baseband on Sprint.
I upgraded my TWRP to 2.780 to flash the recovery both first time 'dirty flashing' and the 2nd time doing a facory wipe.
I removed the battery after the flash.
When I reboot, the phone stays on the Yellow Sprint screen and the LED pusles blue slowly. So far been doing it for 15 mintues.
What am I missing?
Dave
Unidave199 said:
Ok, so something weird...
Im running KK4.4.2 with the NC5 baseband on Sprint.
I upgraded my TWRP to 2.780 to flash the recovery both first time 'dirty flashing' and the 2nd time doing a facory wipe.
I removed the battery after the flash.
When I reboot, the phone stays on the Yellow Sprint screen and the LED pusles blue slowly. So far been doing it for 15 mintues.
What am I missing?
Dave
Click to expand...
Click to collapse
Give it 30 minutes? It seriously takes a long time. Are you sure you want to upgrade to lollipop? In just asking because you've been on Kit Kat long after support for lollipop or this phone has long stopped. I'd suggest downloading the latest Odin and flashing that instead, unless there is something here you wanted? I'm rooted on PL1 and have no issues other than my phone being as old as it is and how many times it's been flashed.
evilvoice said:
Give it 30 minutes? It seriously takes a long time. Are you sure you want to upgrade to lollipop? In just asking because you've been on Kit Kat long after support for lollipop or this phone has long stopped. I'd suggest downloading the latest Odin and flashing that instead, unless there is something here you wanted? I'm rooted on PL1 and have no issues other than my phone being as old as it is and how many times it's been flashed.
Click to expand...
Click to collapse
30 minutes? Woah that is a long time. Ok I will give it a try sometime when I go to bed.
I am mainly trying to get the PL1 update and not mess with Odin if I can get around it. I would like to try and port the Darklord Marshmellow ROM and take advantage of built in google assistant
So I thought I would try them. And always get back if I need to but wanted to keep the PL1 modem updates.
I only have one problem with one other phone user... She doesnt always get my texts and I dont always get hers. I dont know if others arent getting them and just dont know but my 1 friend I text a lot so she notices when there is a gap.
Anyways. Just feeling out how I can maximize this phone's performance. NO plans on changing phones anytime soon.
Unidave199 said:
30 minutes? Woah that is a long time. Ok I will give it a try sometime when I go to bed.
I am mainly trying to get the PL1 update and not mess with Odin if I can get around it. I would like to try and port the Darklord Marshmellow ROM and take advantage of built in google assistant
So I thought I would try them. And always get back if I need to but wanted to keep the PL1 modem updates.
I only have one problem with one other phone user... She doesnt always get my texts and I dont always get hers. I dont know if others arent getting them and just dont know but my 1 friend I text a lot so she notices when there is a gap.
Anyways. Just feeling out how I can maximize this phone's performance. NO plans on changing phones anytime soon.
Click to expand...
Click to collapse
I still use my note 3. Granted not for main phone as I switched to iPhone, but I use it every day. I don't really know the hesitation of using Odin, but to each their own. If you did decide to use Odin, I'd flash the ROM, boot it, go to download mode again, flash TWRP, boot recovery (so it sticks and doesn't go back to stock recovery), flash SuperSU, done. You're rooted on PL1. Hopefully you have already backed up your text messages and other various things to either SDCard or something else. I'm not sure if that survives whether you wipe and flash clean or Odin. Depending on provider, that could be your issue with text messages. If you're with Sprint, check that you are on latest PRL. If not, make sure APN settings are correct.
If you're only looking for Assistant, I had it running on stock PL1. XDA did a blog post about enabling it in Lollipop, so once you upgrade, check it out. I couldn't stay on Marshmallow. Being that these are ports and not specifically built for our phone, I ran into issue with every single ROM either not being able to place calls, text (MMS actually), or wireless/data not working. No matter what I changed APN to, I would always have issues. Some do not. I just can't recommend a port when they haven't worked for me. Some roms have been abandoned, which meant if I found one that I could at least handle, it was so outdated that it was unusable (issues had arisen and the developer had moved on so they weren't being fixed). By handling a rom, I mean that after I upgraded to iPhone, I only needed wireless to work (to connect to hotspot) and it not go into a boot loop or crash all the time (some do). Those roms I have no idea if calls or text work because I wasn't using that. A lot have issues with wireless working.
One more thing you can try is to do a flash, wait about 30 minutes. If it still doesn't boot, pull the battery and reboot into recovery. Wipe data and cache and reboot again. It should boot. It'll still take a long time. Make sure you wait the 30 minutes before pulling the battery (it should have finished upgrading your system by then). Do note that first boot from now on will take forever no matter if it's a port or stock. Lollipop and higher take a long time to upgrade. I've only had 1 or 2 roms take around 5 minutes and that's because they were minimalist and without Google apps. The phone does get a little warm and uses a lot of battery, so I'd keep it plugged in.
Please report back if you got it to work and how. Like I said, I still use mine. I still visit this forum every day even though I've had an s5 and an s7 edge. I love this phone. I need to get mine replaced because I've worn it out: broken charger port so I have to make sure the cable is plugged in a certain way and I can't touch the phone while charging, side molding is broken off in places, some of my partitions can't be changed which means the memory is failing (not even Odin flashes correctly anymore let alone custom roms). But, it still keeps on ticking.
evilvoice said:
I still use my note 3. Granted not for main phone as I switched to iPhone, but I use it every day. I don't really know the hesitation of using Odin, but to each their own. If you did decide to use Odin, I'd flash the ROM, boot it, go to download mode again, flash TWRP, boot recovery (so it sticks and doesn't go back to stock recovery), flash SuperSU, done. You're rooted on PL1. Hopefully you have already backed up your text messages and other various things to either SDCard or something else. I'm not sure if that survives whether you wipe and flash clean or Odin. Depending on provider, that could be your issue with text messages. If you're with Sprint, check that you are on latest PRL. If not, make sure APN settings are correct.
If you're only looking for Assistant, I had it running on stock PL1. XDA did a blog post about enabling it in Lollipop, so once you upgrade, check it out. I couldn't stay on Marshmallow. Being that these are ports and not specifically built for our phone, I ran into issue with every single ROM either not being able to place calls, text (MMS actually), or wireless/data not working. No matter what I changed APN to, I would always have issues. Some do not. I just can't recommend a port when they haven't worked for me. Some roms have been abandoned, which meant if I found one that I could at least handle, it was so outdated that it was unusable (issues had arisen and the developer had moved on so they weren't being fixed). By handling a rom, I mean that after I upgraded to iPhone, I only needed wireless to work (to connect to hotspot) and it not go into a boot loop or crash all the time (some do). Those roms I have no idea if calls or text work because I wasn't using that. A lot have issues with wireless working.
One more thing you can try is to do a flash, wait about 30 minutes. If it still doesn't boot, pull the battery and reboot into recovery. Wipe data and cache and reboot again. It should boot. It'll still take a long time. Make sure you wait the 30 minutes before pulling the battery (it should have finished upgrading your system by then). Do note that first boot from now on will take forever no matter if it's a port or stock. Lollipop and higher take a long time to upgrade. I've only had 1 or 2 roms take around 5 minutes and that's because they were minimalist and without Google apps. The phone does get a little warm and uses a lot of battery, so I'd keep it plugged in.
Please report back if you got it to work and how. Like I said, I still use mine. I still visit this forum every day even though I've had an s5 and an s7 edge. I love this phone. I need to get mine replaced because I've worn it out: broken charger port so I have to make sure the cable is plugged in a certain way and I can't touch the phone while charging, side molding is broken off in places, some of my partitions can't be changed which means the memory is failing (not even Odin flashes correctly anymore let alone custom roms). But, it still keeps on ticking.
Click to expand...
Click to collapse
Come back to Android! We miss you!!!!
Yes I am backed up and also have a Titanium Backup of everything so I am pretty much covered... I have even backed up the backups to my PC!
You have much wisdom in what you are saying. I thought I would play around with some other ROM's and see what the potential is.
I hear good things about the Darklord Reborn by Midevil and JCorderno so thought I would investigate.
I am not opposed to using Odin, but I was at work, and no access to a computer so wanted to see if I could do the upgrade 'on the fly' since I am already rooted and with recovery.
Man, waiting 30 minutes for a phone to boot sounds like a anxiety attack waiting to happen! But still wanna give it a try.
As to your USB port. Have you thought of going wireless charging? I did and haven't looked back! You can get a wireless charging back and a case that will fit at...
for the charging back
https://smile.amazon.com/Samsung-Ga...=8-2&keywords=samsung+note+3+wireless+charger
for the case
https://smile.amazon.com/gp/product/B00F3KP156/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
Clone Wars....
Just wanted to put out a big THANKS for this.. I broke my Note 3 after 2,433 days (long story) but had bought a stock spare on Ebay last year... Making the switch now, but your PH1 Flashable update is making it super easy!
To let everyone who needs to use this nowdays... you will need to Flash an older TWRP (I used 2.7.8) in order to allow the Modem partition to be overwritten. Then you can flash up to 3.x to load a Android 10 based rom.