Develop Bugs

[Q] The first thing to do with an Xplay?

Ok. I would be glad if someone could point me in the right direction here, and answer this question.
I am planning on buying an Xplay, mainly for phoning and gaming. I am very keen on keeping the Xplay "clean" and fast, and therefore wish to remove all bloatware from the beginning.
Could someone point me in a direction to where to start when I first unpack my phone? Should I accept all the updates and so on? What´s the best thing to do if I want to remove the bloatware. I might as well say that I´m pretty much a beginner when it comes to all the terms "rooting" and stuff. But I want to do it a safe way, without taking risks of breaking or bricking anything.
Thanks.

Some of the bloatware can be simply uninstalled, some cannot. For the latter you need to root your phone. I like to use SuperOneClick for rooting. Note that some firmwares (the ones whose version ends with .62 or greater) cannot be rooted, so I wouldn't update to them.
Once rooted, removing the bloatware is pretty simple. The most common way is to use Titanium Backup to uninstall it or you can even do it manually by deleting the relevant .apk files from /system/app.

Root your phone ,this is the first step that you must to do. After rooting ,you can remove bloatware from your phone and gain more free space on you internal memory.
I think that the best rooting way is the (zergRush Method):
http://forum.xda-developers.com/showthread.php?t=1312859
After rooting ,download 'Root Explorer' ,go to system/app and remove all the things you don't need.

If you are getting an AT&T Xplay I would suggest installing the generic north American rom which is 2.3.4 and missing the AT&T bloat. I backed up the games from the stock rom first then installed the NA rom and reinstalled them.

First use pc companion and install the latest update. Then root and remove bloat and get everything set up like your contacts and apps. After that install cwm and make a nandroid backup and start flashing roms! Back-up your info if the rom won't carry it over. Optional: Unlock bootloader before roms. There are plenty of stock based roms to for people with locked bootloaders.

EDIT: Don't do the below, just read you don't want risk!
1. Unlock the bootloader
2. Use flashtool to install a generic ROM .FTF file (.368 has CRT animation but is old, .42 is good, .62 is good)
3. Install a kernel (DooM's is great). This will allow you to overclock, and give automatic ROOT (no need to exploit or install anything else)
4. Buy/acquire an app called "Titanium Backup" (it needs ROOT to run), and check the guide in these forums for which apps are safe to remove

The first thing to do? Here's a list:
1. READ everything you can find related to your model version of the Play. There are different versions depending on where you are in the world and who your service provider is. If you have a GSM capable phone (Europe, Canada, ATT in US just to name a few), you will have a lot more modification options available. If you have a CDMA capable phone (Verizon), you have fewer choices but there are more coming almost every day.
2. READ again - you know you only understood maybe a 10th of what you just read!
3. POST specific questions AFTER you have searched the forums. Don't be afraid to try Google - that's what it's there for.
4. THINK !!! - what is it that you expect to get from modifying your phone that it doesn't do now? If you just want to remove bloatware, you can simply root, install a custom recovery, make a backup and then go to town. No need for unlocking the bootloader or loading a custom rom.
5. SLOW DOWN !!! - don't be in such a hurry to modify your phone that you leap before you look. Most bricked phones could be avoided in the first place by taking time to understand the steps involved before making changes.
6. DON'T PANIC !!! - There are very few things you can do to your phone that the experienced folks here on the forums can't help you resolved.
7. HAVE FUN !!!
---------- Post added at 01:16 AM ---------- Previous post was at 01:14 AM ----------
Potato13 said:
First use pc companion and install the latest update. Then root and remove bloat and get everything set up like your contacts and apps. After that install cwm and make a nandroid backup and start flashing roms! Back-up your info if the rom won't carry it over. Optional: Unlock bootloader before roms. There are plenty of stock based roms to for people with locked bootloaders.
Click to expand...
Click to collapse
Not necessarily. If you install some of the latest updates, you no longer can root. That's why some research needs to be done first.

Search google and read xda forums on a daily basis. That's the shortest route lol
1. Root using zergrush or use flashtool rooting feature
2. Unlock bootloader (this will void your warranty)
3. Install clockworkmod 5.0.2.7 for xperia phones (get it free on play store fka android market)
4. Install titanium backup and perform batch backup of your apps to your sd card
5. Get doomlord's kernel v11 (link is on my signature) and wifi modules
6. Reboot into recovery and hold down or tap volume down to enter CWM recovery
7. Flash the kernel, then reboot and flash the wifi module
8. Flash your custom rom
9. There your phone is bricked! Haha

netizenmt said:
4. THINK !!! - what is it that you expect to get from modifying your phone that it doesn't do now? If you just want to remove bloatware, you can simply root, install a custom recovery, make a backup and then go to town. No need for unlocking the bootloader or loading a custom rom.
Click to expand...
Click to collapse
Thanks for the input.
The only thing that I plan to do, is probably just remove bloatware and nothing more. So I guess it´s just down to rooting the phone then, and delete the things that I don´t want? No need for unlocking bootloaders etc.?
Is there a list of what stuff that can be deleted? Or other things that can be achieved by only rooting the phone?
And the last question. Is it totally ok to accept android updates after the rooting and removing of bloatware?

silmes said:
Thanks for the input.
The only thing that I plan to do, is probably just remove bloatware and nothing more. So I guess it´s just down to rooting the phone then, and delete the things that I don´t want? No need for unlocking bootloaders etc.?
Is there a list of what stuff that can be deleted? Or other things that can be achieved by only rooting the phone?
And the last question. Is it totally ok to accept android updates after the rooting and removing of bloatware?
Click to expand...
Click to collapse
If you aren't going to get into custom kernels and overclocking, then no, you can do what you want without unlocking the bootloader.
There are some links in General and here in Q & A that make suggestions of what can be removed safely.
If you only rooted and didn't remove anything, you could accept updates. If you remove bloatware, the update won't even install. That's why I suggest installing CWM (ClockWorkMod) Recovery and doing a Nandroid Backup after you root but before you debloat.
Here are some useful links for you:
Rooted (Locked Bootloader) Phone - App Removal (Safe List)
[GUIDE] R800x owners - You got Custom ROM questions? I've got Answers!
The second one there was one I posted up for R800x users with locked bootloaders. It was all the stuff I had to glean for myself when mine was locked.
Hope this helps.

Sigh...hope this isn't too late.
http://forum.xda-developers.com/showthread.php?p=23845116#post23845116

First thing: Root right away with Flashtool (http://androxyde.github.com/) and don't listen to the others, the Flashtool nowdays contains the Exploit that you need and it works perfect to root on 2.3.4 (I did it myself when I root'd mine the first time).
I am planning on buying an Xplay, mainly for phoning and gaming. I am very keen on keeping the Xplay "clean" and fast, and therefore wish to remove all bloatware from the beginning.
I recommend the Titanium Backup as all the others, and you can use this list as help: http://forum.xda-developers.com/showthread.php?t=1046699&highlight=remove+app+list
Could someone point me in a direction to where to start when I first unpack my phone? Should I accept all the updates and so on?
Yes, do that first of all before you go ahead and root your device.

Q: Could someone point me in a direction to where to start when I first unpack my phone? Should I accept all the updates and so on?
A: Yes, do that first of all before you go ahead and root your device.
The interesting thing is that the answer to this seems to differ on who you ask. Further back in this thread, someone advised me NOT to update, as it might lead to problems when trying to root my phone. What´s the deal here?

silmes said:
Q: Could someone point me in a direction to where to start when I first unpack my phone? Should I accept all the updates and so on?
A: Yes, do that first of all before you go ahead and root your device.
The interesting thing is that the answer to this seems to differ on who you ask. Further back in this thread, someone advised me NOT to update, as it might lead to problems when trying to root my phone. What´s the deal here?
Click to expand...
Click to collapse
If you update to the .62 firmware you can't root.
Sent from my LT26i using Tapatalk

silmes said:
Q: Could someone point me in a direction to where to start when I first unpack my phone? Should I accept all the updates and so on?
A: Yes, do that first of all before you go ahead and root your device.
The interesting thing is that the answer to this seems to differ on who you ask. Further back in this thread, someone advised me NOT to update, as it might lead to problems when trying to root my phone. What´s the deal here?
Click to expand...
Click to collapse
That's because it differs between models and some people aren't aware of that, while others like to be argumentative!
If you have a Verizon R800x Play, our firmware only goes up to Version 2.3.3 (3.0.1.E.0.88). If yours comes with 2.3.2, you're safe to update. You will be able to root with no problem.
If you have one of the other phones, you can apply updates below 4.0.2.A.0.62 and still root. .62 and higher, no root.
Check out this thread [HOW-TO] Root Phones w/ Android v2.2.x-2.3.x (zergRush Method) for additional information.

Stock rom in case be Hose the Note 8?

how about if i were to hose my note 8 and need to recover to complete stock. is there anything out yet for the US WIFI version? just wondering as i might wait untill i root, install recovery etc...

I am downloading the UK version as per the suggestions in a post on the first page to this thread. I was told it is the same.I hosed mine trying the multi boot option on one of the dev threads, Cant get to my recovery so I'm kinda screwed.

dvigue said:
how about if i were to hose my note 8 and need to recover to complete stock. is there anything out yet for the US WIFI version? just wondering as i might wait untill i root, install recovery etc...
Click to expand...
Click to collapse
Now the only way you can hose your stock firmware is to mess up a flash, or purposefully delete system files in the root.
With that said, you can safely root with Saferoot.zip. It does not flash our change your counter. So a OTA or Kies update will work as if you never touched the device.
Now that you have rooted safely, you can install Xposed framework and it's modules... they will not hose your device as they are boot only system options.
I recommend Ti backup pro, and Solid Explorer but be careful about doing anything in root, as their may be irreparable consequences without a proper ROM.
Now for recovery with a replacement ROM. There will be a new ROM release soon, so when it does come out, it will be available to download. That will be your best option to recover if needed. Note... The only way you will hose a device is through a bad flash. So I would stay away from flashing any custom bootloaders, recoverys, kernels or ROM. Until you read up and are well educated on proper flashing techniques. All I can say is stick with developers threads on the specific model and have given plenty of info on the subject. Never blindly take chances.
As for recovery after saferoot.zip... as long as you never flash afterwards, you will never need triangle away, which is a plus... all you need to do is do a factory restore. Yep, no need to run any un-rooting tools, though you can use Supersu's clean up for reinstall and reboot if you want before doing the factory reset.
I know, I have done plenty of testing with custom and factory ROMs. I have personally found no need for customized bootloaders or roms, once I have found where and what to tweak. What little benefit from the customized options that are available, were too little for the trouble involved.

I actually posted about how to mod your device using Xposed installer and 2 to 3 modules and thats all you need to get that really cool custom look if thats what you are going for. With Gravity Box and HK Themer you can mod away semi safely. You still need to be careful with any mod that makes changes in system.
Sent from my GT-N5110 using XDA Premium HD app

Noob ROM user - help with 1st ROM install, please

Hope this the right place to post - please let me know if not.
I have the Sprint G3. I rooted (being a first time rooter at that time) within a few weeks of getting the phone. Frankly, I don't recall how I rooted it, but I think it was using Stump'd. In any case, root went fine, installed, SU, and been using some of the Framework apps like tweaksbox.
Okay, here's what I need some help with:
I think I need to unroot the phone, return it to factory stock, and then reroot before flashing a ROM to it. Is that correct?
I've seen a couple of threads here with instructions, but I don't follow/understand much of the terminology. Hence, is this page good to use to help me - http://lgg3root.com/lg-g3-root/how-t...nbrick-lg-g3/?
Secondly, once returned to factory srock ROM, will I have to OTA update to the most current version for Sprint before rerooting? I think I've read that the current stock ROM is not yet rootable?
Third, I really want to flash a ROM because I think it will result in a lighter weight ROM to conserve battery power and because I really want to theme the phone beyond what I can do now rotted with icon packs and tweaksbox. Is the CM ROM lighter weight and will I realize better battery performance?
Lastly, I'm hesitant to install a custom ROM because I'm afraid of losing phone, data, sms, gps services. I think this after reading the custome ROM threads and see complaints regarding users not having services available or connectivity issues. Is this a legit concern or am I overthinking this?
Thanks in advance for your suggestions, tips, and feedback.

JMak00 said:
Hope this the right place to post - please let me know if not.
I have the Sprint G3. I rooted (being a first time rooter at that time) within a few weeks of getting the phone. Frankly, I don't recall how I rooted it, but I think it was using Stump'd. In any case, root went fine, installed, SU, and been using some of the Framework apps like tweaksbox.
Okay, here's what I need some help with:
I think I need to unroot the phone, return it to factory stock, and then reroot before flashing a ROM to it. Is that correct?
I've seen a couple of threads here with instructions, but I don't follow/understand much of the terminology. Hence, is this page good to use to help me - http://lgg3root.com/lg-g3-root/how-t...nbrick-lg-g3/?
Secondly, once returned to factory srock ROM, will I have to OTA update to the most current version for Sprint before rerooting? I think I've read that the current stock ROM is not yet rootable?
Third, I really want to flash a ROM because I think it will result in a lighter weight ROM to conserve battery power and because I really want to theme the phone beyond what I can do now rotted with icon packs and tweaksbox. Is the CM ROM lighter weight and will I realize better battery performance?
Lastly, I'm hesitant to install a custom ROM because I'm afraid of losing phone, data, sms, gps services. I think this after reading the custome ROM threads and see complaints regarding users not having services available or connectivity issues. Is this a legit concern or am I overthinking this?
Thanks in advance for your suggestions, tips, and feedback.
Click to expand...
Click to collapse
First lets start with returning to Stock ROM. No, no you definitely do not need to return to stock factory ROM to flash a new one. Since you already are rooted all you need is a TWRP recovery.
To flash TWRP recovery to your device (Sprint G3) use this thread:
http://forum.xda-developers.com/sprint-lg-g3/orig-development/bump-unlock-lg-g3-twrp-sprint-t2900588
It's very easy for a begginer to achive this. If you don't want to use adb, fell free to download flashify and flash the downloaded TWRP image from thread above with it.
It's even easier with flashify.
Yes CM ROM is lighter, closer to stock android, not the LG one. If you really want better battery experience you should also look up different kernels, different governors, more adavanced stuff, nothing too much.
You don't need to be scared of flashing ROMs. It's a very basic task these days.
Losing data, calling ability or other thing is very unlikely. Of course mistakes happen so be careful. First thing to do before flashing anything on your device after instaling your TWRP recovery is to do a backup.
ALWAYS DO A BACKUP OF ALL IMPORTANT PARTITIONS ON YOUR DEVICE.
To get your custom ROMs, including CM look up these:
http://forum.xda-developers.com/sprint-lg-g3/orig-development
http://forum.xda-developers.com/lg-g3/development
Also be careful to flash things made only for your device (Sprint LG G3).

Very helpful and thanks.
To show off my noobness... Do custom ROMs have customer kernels or do I install a customer kernel as well as a custom ROM?

Yes, they do come with custom kernels.
But you could change kernel for some other one if you wish for.
I personally use Blisspop 3.7 on my LG G3 D855 with kernel that came with it 777 by 777jon.

Thanks, now to twrp, flash new rom and install cm 12 theme. Fingers crossed I dont go ham and brick the device.

Can you root the latest update and use xposed? Pros and Cons?

Cant make much sense of all these threads. Always used a highly customized and unlocked international Nexus. But this US Verizon phone seems to be difficult to customize.

usern ameisval idandnot said:
Cant make much sense of all these threads. Always used a highly customized and unlocked international Nexus. But this US Verizon phone seems to be difficult to customize.
Click to expand...
Click to collapse
You definitely can root this phone and install exposed. The biggest issue is that the bootloader is locked and doesn't look like it's going to be unlocked anytime soon. So for the most part, no custom roms. Another downside if that of something goes wrong on root, your options to get your phone back up and running are limited to using a KDZ file if one is available for the specific version your trying to root, or push a stock system image if you made a back up. Sf today the latest 13b software has a KDZ thanks to autoprime. I haven't done much customization, so I can't shall to that.

Where can find a step by step guide how to flash a rooted image? What precautions are necessary to get back to stock in case something goes wrong? I need to costumize my phone.

usern ameisval idandnot said:
Where can find a step by step guide how to flash a rooted image? What precautions are necessary to get back to stock in case something goes wrong? I need to costumize my phone.
Click to expand...
Click to collapse
I used this guide: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
Following this guide will allow you to make a backup of your stock system image and root your own image. It's easy and straightforward.

Google lg g4 root xda
From there, you'll see a link to a low effort root, that teaches you how to flash system image.
I tried KDZ method but the KDZ image I loaded wasn't rooted...

It is super easy to do. I will say the low effort root page should be updated with a * or something to say hey, the latest version for the verizon lg g4 is 13b. Also the flashfire method to install xposed takes 15 minutes. I also like using g4 tweaksbox.
This is my first few days with the g4. I have had the g3 since release. Much faster. Familiar. Liking it so far. Battery life seems great. But I am delaying greenify, amplify, etc, to see if I even need it.
Kinda shocked there isnt more activity around here tho!

I have successfully rooted my G4 and Xposed is up and running. I do have a kinda dumb question. Can i move my rooted.img & system.img to my external SDcard to save some space? Just want to make sure. Thank you in advance.
NVM found my answer.

Can't get root twice for bootloader unlock. Got it once, can't do it again.

I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)

Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Where are you getting the firmware you're trying to use to downgrade?

douger1957 said:
Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
Click to expand...
Click to collapse
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
douger1957 said:
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Click to expand...
Click to collapse
I actually tried a PC version of kingoroot. It also failed numerous times.
douger1957 said:
Where are you getting the firmware you're trying to use to downgrade?
Click to expand...
Click to collapse
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.

nertskull said:
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
I actually tried a PC version of kingoroot. It also failed numerous times.
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.
Click to expand...
Click to collapse
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.

douger1957 said:
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.
Click to expand...
Click to collapse
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?

nertskull said:
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?
Click to expand...
Click to collapse
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?

douger1957 said:
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?
Click to expand...
Click to collapse
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.

nertskull said:
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.
Click to expand...
Click to collapse
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.

douger1957 said:
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.
Click to expand...
Click to collapse
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks

nertskull said:
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks
Click to expand...
Click to collapse
That's a difficult question to answer and for me would boil down to whether I wanted features available in Marshmallow based ROMs or not.
Wifi calling is a nice to have feature for me but it's not really a dealbreaker. There's a bit more security baked into Marshmallow which is always nice to have.
The development atmosphere is more active over at the generic Note 4 forum. You can now get one of the super ROMs (Note/S7 combo ports) in either flavor. You'll want to stick with ROMs developed for the N910F or G models. They're international phones with fewer integration headaches for our N910V phones. To use those ROMs on our phone, you'll need a data fix most kindly provided by @louforgiveno.
My suggestion in picking a ROM is to zero in on one that seems to have the features you'd like to have and read the entire thread. Look for threads in either the General or Q&A subforums that are dedicated to answering questions about the ROM and read those, too. Some of those threads are upwards to 1,000 posts or more, you say? You'll discover what problems people have had with the ROM and the solutions or workarounds needed to overcome them. You'll also discover just how lazy many posters are either not reading thoroughly or failing to use the search function.
Final suggestions? Do a full nandroid backup before you flash anything. In TWRP, check off all of the boxes. In many of today's ROMs, you'll have a 8 to 10 gig backup file. If you can't keep that on the phone, move it to your PC. There will be far fewer tears if something goes wrong. When you flash a ROM, do a full wipe. I check off Dalvik/ART cache, system, data, and cache. For your first ROM, I would move anything that you have on internal storage off the phone and wipe internal storage too. If you have any Kingroot/Kingoroot cooties, that should clear them off the phone. When you're done flashing a ROM there's an option to wipe the cache. Do it. If you've installed a bunch or apps or deleted them, wipe the Dalvik and cache. It'll help bring the Android stars into alignment as that forces the system to optimize.
Good luck and happy flashing.

You need to go to 5.1.1 use kingOroot and then do it again. Cid will remain that's what I did. Its different for everyone these root methods are pulled from the internet and it will usually take a few time and it will try dufrrent methods of rooting
nertskull said:
I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)
Click to expand...
Click to collapse

For me, I had to run Kingoroot from my laptop, and Kingroot never worked.