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!
Hi. I bought a near-mint S4 on Swappa from a seller who had already rooted it and installed a custom ROM (one similar to Samsung stock). After verifying that it worked I did a factory wipe, deleted the caches and used the existing TW recovery to install CM11, which so far I just love -- it's extremely close to the stock Android on my Nexus tablet, only with other great options like running Titanium backup and a firewall, etc. The lack of VZW and Samsung bloat is also great, of course.
However, do I need to worry that the phone could still be infected with or vulnerable to malware, perhaps because of something left over from whatever process the seller used to root the phone and install recovery? Would using the Avast firewall protect me, or would I be wiser to unroot the phone, take it back to stock and start all over again? (I'm reluctant to do that because it has the MK2 baseband and I'm afraid of not being able to get back to having a custom recovery.) Am I worrying needlessly, because the willing and installation of CM would have deleted any dangerous stuff that may have been lurking?)
This is my first time dealing with a rooted phone or a custom ROM. I really like the idea of having more control over what I run on my own phone (similar to running Linux on my computers, which I've been doing for years), but want to make sure I'm not being foolish somehow.
Aquifer122 said:
Hi. I bought a near-mint S4 on Swappa from a seller who had already rooted it and installed a custom ROM (one similar to Samsung stock). After verifying that it worked I did a factory wipe, deleted the caches and used the existing TW recovery to install CM11, which so far I just love -- it's extremely close to the stock Android on my Nexus tablet, only with other great options like running Titanium backup and a firewall, etc. The lack of VZW and Samsung bloat is also great, of course.
However, do I need to worry that the phone could still be infected with or vulnerable to malware, perhaps because of something left over from whatever process the seller used to root the phone and install recovery? Would using the Avast firewall protect me, or would I be wiser to unroot the phone, take it back to stock and start all over again? (I'm reluctant to do that because it has the MK2 baseband and I'm afraid of not being able to get back to having a custom recovery.) Am I worrying needlessly, because the willing and installation of CM would have deleted any dangerous stuff that may have been lurking?)
This is my first time dealing with a rooted phone or a custom ROM. I really like the idea of having more control over what I run on my own phone (similar to running Linux on my computers, which I've been doing for years), but want to make sure I'm not being foolish somehow.
Click to expand...
Click to collapse
Since you're able to run CM11, it must be running the MDK build, which is pretty amazing as you can run what you want with the Loki exploit allowing you to bypass the locked bootloader.
If you really are concerned about what's on the phone, you can always flash a full-wipe factory MDK ROM image and start over.
DO NOT - Don't - no - never- take any factory updates. Or flash anything past MDK from Verizon. Ever.
Thank you -- I do indeed feel fortunate about having the MDK build and don't want to do anything to mess it up.
How reasonable are my concerns about some vulnerability being left on the phone by the prior owner? I did two wipes of the phone (system, data, cache and dalvik cache each time) before installing CM.
Aquifer122 said:
Thank you -- I do indeed feel fortunate about having the MDK build and don't want to do anything to mess it up.
How reasonable are my concerns about some vulnerability being left on the phone by the prior owner? I did two wipes of the phone (system, data, cache and dalvik cache each time) before installing CM.
Click to expand...
Click to collapse
You'll be fine if you hop into recovery and do a Factory Reset where it includes the Internal Card.
Most likely your all set though with what you've done. Enjoy that MDK phone! I also have one and being able to run non Touchwiz Roms is the only way to go if you ask me.
If you have anymore questions regarding MDK feel free to hit me up or ask here... Were all here to help
Sent from my SCH-I545 using Tapatalk
Hi guys I want to post my experience for future reference. Bought this phone (in Athens, Greece) because it's crazy value for money. After a week or so I was really satisfied with it. Just wanted some more Marshmallow features, like multiwindow. So I did my research and ended up following a related guide : steps-to-root-moto-e-2nd ge n. Everything went well, I unlocked the bootloader, flashed twrp, the phone rebooted and I chose to flash SD card as internal, and I was able to install my apps and settings. Then again following the guide steps I tried to flash SuperSU. This resulted to an endless bootloop, where the message " YOU HAVE UNLOCKED THE PHONE S BOOTLOADER....." kept showing up. So I started reading related post from many forums, most of them reproducing the same solutions, like "find your phone's official firmware and reflash". I downloaded many firmwares, all of them appeared (to me at least) suitable for my phone, but none of them had any result. The bootloop continued. I couldn't even flash ROMS from SD card, obviously because of the internal memory format I had done the first and only time the phone booted. Two days had passed and I was really frustrated, ready to take it to service ( or throw it against the wall). Until now I didn't want anything else but the official firmware. But what the heck, after so much efforts, anger and disappointment there is nothing wrong in trying new things. So when I came across the guide about installing cyanogen 13 on my phone, I decided to give it a try. TOTAL SUCCESS!!!! Now my phone is really "flying", is really fast and the most important: is really working again. Although I went through a second flashing of cyanogen 13 because I had the lame persisting idea to flash SuperSU again, with the same frustrating results. So the bottom line, and the reason for this post is : do not flash SuperSU on this phone because you will soft brick it, and don't get caught up with a "hunt" for the right firmware, you will only loose time and some sanity. This is my advice: Go ahead and install cyanogen, it is really great and has insane features. Big thanks to all the guys developing and contributing, you really saved me big time!!!!
vagfyt said:
Hi guys I want to post my experience for future reference. Bought this phone (in Athens, Greece) because it's crazy value for money. After a week or so I was really satisfied with it. Just wanted some more Marshmallow features, like multiwindow. So I did my research and ended up following a related guide : steps-to-root-moto-e-2nd ge n. Everything went well, I unlocked the bootloader, flashed twrp, the phone rebooted and I chose to flash SD card as internal, and I was able to install my apps and settings. Then again following the guide steps I tried to flash SuperSU. This resulted to an endless bootloop, where the message " YOU HAVE UNLOCKED THE PHONE S BOOTLOADER....." kept showing up. So I started reading related post from many forums, most of them reproducing the same solutions, like "find your phone's official firmware and reflash". I downloaded many firmwares, all of them appeared (to me at least) suitable for my phone, but none of them had any result. The bootloop continued. I couldn't even flash ROMS from SD card, obviously because of the internal memory format I had done the first and only time the phone booted. Two days had passed and I was really frustrated, ready to take it to service ( or throw it against the wall). Until now I didn't want anything else but the official firmware. But what the heck, after so much efforts, anger and disappointment there is nothing wrong in trying new things. So when I came across the guide about installing cyanogen 13 on my phone, I decided to give it a try. TOTAL SUCCESS!!!! Now my phone is really "flying", is really fast and the most important: is really working again. Although I went through a second flashing of cyanogen 13 because I had the lame persisting idea to flash SuperSU again, with the same frustrating results. So the bottom line, and the reason for this post is : do not flash SuperSU on this phone because you will soft brick it, and don't get caught up with a "hunt" for the right firmware, you will only loose time and some sanity. This is my advice: Go ahead and install cyanogen, it is really great and has insane features. Big thanks to all the guys developing and contributing, you really saved me big time!!!!
Click to expand...
Click to collapse
There's an issue with SuperSU when it tries to install in systemless mode.
Flashing it this way seems to do the trick, and has been confirmed by multiple users on this board: http://androiding.how/root-moto-g-2014-marshmallow/
If you're using CM13, there is no need to flash SuperSU. CM13 has its own root pre-installed, you can turn it on in Developer Options.
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.
I love my KF HD 6 and use it daily, but after almost two years I've grown tired of the UI and was thinking about switching over to a custom ROM. That, and the fact that Amazon seems to have abandoned development for my device since it's a couple generations behind so it's not likely to get updated past its current 5.1.1 lollipop.
I did some digging, but the only official ROM I could find for my device is CM11. A bit disappointing since it's not only an incomplete port (not all features work), but it would be a downgrade to 4.X KitKat. Not really what i'm looking for. I did find a video showing how to put CM13 Marshmallow onto a KF 7. https://www.youtube.com/watch?v=W0GwGthOfh8 and I thought this may work for the 6 as well. I know they're not the same device, but I've seen it mentioned several places that the HD 6 and HD 7 that were released in 2014 are identical under the hood with the only difference being the screen size.
Anyway, I have a working TWRP recovery for my device, along with properly installed ADB and fastboot drivers. So if I use ADB to pull my partitions and copy them to my PC just in case, then make a Nandriod backup in TWRP and transfer it to my PC (again, just in case) then do a cache wipe and a system wipe, then flash CM13 along with the appropriate Gapps, then another cache wipe to avoid bootloops, then reboot I should be good right?
Either it will work, or it won't. In case it doesn't work I should be able to boot back into TWRP and restore from my Nandroid. If for some reason I can't get back into TWRP, I do have a fastboot cable that can at least get me access to fastboot mode where I can push all my partitions back manually. Either way I should be good in the event that it all goes pear shaped?
Sorry if these are basic questions, but I am still new to all this and I just want to make sure I have all my bases covered before I start anything. I feel it's better to ask for clarification and advice first, than to jump the gun and come here afterward with a bricked device asking for help trying to fix it because of my own stupidity.
For all you who are pros at this sort of thing, did I miss anything or should I be good to go? Thanks.
Necro bump - so what did you end up doing? I have a KF 6HD gathering dust and I'm getting an itch to ROM