Develop Bugs

(HELP) TMO HTC One- keep wiping and still end up in bootloop

I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!

westonnate said:
I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!
Click to expand...
Click to collapse
If you wanna fix it quick then just do an RUU (t-mobile one) and after you've done that use Sunshine to root, unlock and S-OFF your phone. All though Sunshine costs $25 it is a sure fire to work.
You can find a tutorial for the RUU in the t-mobile forum I believe, not sure as im replying to this before I go to bed but it should have one. If by some chance "TMO" doesn't mean T-Mobile then my bad. Anyways if you get confused take your time and do your research or wait for someone else or me to assist you further.
Also if you used Xposed then that could be the problem, I've had it randomly bootloop me after days of use, just google the Xposed deactivate script zip or Uninstaller script and flash it to remove it. If you don't have it then don't do this part.
Lastly I doubt you'll regret buying an M8 after you get it setup properly, it's a great phone but of course that's just mine and a lot of people's opinion. Anyways good luck and hope one of my solutions fix it! If not then don't be afraid to ask more questions or request further assistance whether from me or someone else.

S1L3nTShaDoWz said:
If by some chance "TMO" doesn't mean T-Mobile then my bad.
Click to expand...
Click to collapse
It does, although T-Mobile is a huge carrier in Europe, and AFAIK only the US T-Mob variant has an RUU (and not immediately clear what version the OP has).

You can flash custom roms without s-off, and have you tried wiping cache and fixing permissions? Idk if that'd solve it or not but worth a try.

So, in 2016, is there still no root for my Samsung Verizon Note 4?

I just managed to get this device from someone the other day. Having been an iphone 5c user for a while, going to a 5c after my last frustrating and horrible android experience with an HTC inspire device, I am back on android for the storage expansion so that I can play emulator games- only to find myself pulling my hair out ONCE AGAIN after all the numerous conflicting advice/ threads/tutorials out here which I have countless wasted hours on already. I don't have time to read through tutorials promising a downgrade from lollipop to kit kat, in hopes of a root so I can pair my ps3 controller wirelessly to my device... constantly stuck on odin failing and what have you, so just give it to me dry and clean. Please help as this is extremely frustrating and annoying.
Can I or can I not root this device? if so How? ( please provide detailed instructions as i don't know what the lingo is around here) If not i'm putting this thing right back on craigslist where I got it from. I am running 5.0.1
All I want to do is pair my ps3 controller wirelessly to my note 4, thought I would be able to do that until sixaxis said it needed 'root access' :silly:
if theres a way to circumvent this, please let me know. I do NOT WANT to use a corded controller with this. Battery life is already kinda sucky on this phone so i'll ened to charge the device as i'm playing

Sunaj1 said:
I just managed to get this device from someone the other day. Having been an iphone 5c user for a while, going to a 5c after my last frustrating and horrible android experience with an HTC inspire device, I am back on android for the storage expansion so that I can play emulator games- only to find myself pulling my hair out ONCE AGAIN after all the numerous conflicting advice/ threads/tutorials out here which I have countless wasted hours on already. I don't have time to read through tutorials promising a downgrade from lollipop to kit kat, in hopes of a root so I can pair my ps3 controller wirelessly to my device... constantly stuck on odin failing and what have you, so just give it to me dry and clean. Please help as this is extremely frustrating and annoying.
Can I or can I not root this device? if so How? ( please provide detailed instructions as i don't know what the lingo is around here) If not i'm putting this thing right back on craigslist where I got it from. I am running 5.0.1
All I want to do is pair my ps3 controller wirelessly to my note 4, thought I would be able to do that until sixaxis said it needed 'root access' :silly:
if theres a way to circumvent this, please let me know. I do NOT WANT to use a corded controller with this. Battery life is already kinda sucky on this phone so i'll ened to charge the device as i'm playing
Click to expand...
Click to collapse
Have not read enough, if you have a Verizon locked bootloader... Recommend to put it right away to Craigslist because no root has been found good luck

If you can deal with root on a temp basis, meaning it is lost every reboot, then go that route. Otherwise as EdrickMg stated, it is not available.

How do I know whether the bootloader is locked or not? I might want to buy an N910V, as its much cheaper than international/Indian version, but I need to make sure whether or not the bootloader is unlocked. Cause I can't even think about not rooting a phone in first one hour of purchase. What could I ask the seller to confirm about the bootloader?

If it's a Verizon Note 4, then the bootloader is locked. There is no permanent rooting method for this phone. People are still hopeful that there might be one coming, but I'm willing to bet that there'll never be a method to root it. This phone has been out since October of 2014, with no root method found. There is a temporary root method that will allow you to root your phone, but the next time you reboot, it's gone and your phone is re-locked. To me, that's a lot of effort for something that you lose whenever you reboot your phone, but that's just my opinion. Also, this temporary root is just root - it doesn't unlock your bootloader.
If you absolutely must have a rootable phone with unlocked bootloader, then look elsewhere.
The only thing that we do have is debloater, which is a method that allows us to turn off and block almost anything we want. For me, that's enough, because the only reason I'd want root is to uninstall all of the crap that comes with this phone. It doesn't get rid of the junk, it just turns it off and keeps it from running.
If you want root to be able to install an ad blocker or to install custom kernels and/or ROMs, you cannot do it on this phone and likely (in my opinion), never will be able to.

Okay, I don't understand all these contract things as we don't have them in our country, but Verizon Note 4 and N910V, they are different? If not, how come there is a custom ROM and kernel for the SM-N910V model? The phone does show a red screen where Verizon is written on it. I am not understanding this!

ithehappy said:
Okay, I don't understand all these contract things as we don't have them in our country, but Verizon Note 4 and N910V, they are different? If not, how come there is a custom ROM and kernel for the SM-N910V model? The phone does show a red screen where Verizon is written on it. I am not understanding this!
Click to expand...
Click to collapse
There is a Verizon Note 4 Developers Edition that comes with an unlocked bootloader and it is rootable. I had to buy it straight from Samsung at full retail price. Totally worth it in my opinion. It is no longer available for sale on the Samsung site though

usmaak said:
If it's a Verizon Note 4, then the bootloader is locked. There is no permanent rooting method for this phone. People are still hopeful that there might be one coming, but I'm willing to bet that there'll never be a method to root it. This phone has been out since October of 2014, with no root method found. There is a temporary root method that will allow you to root your phone, but the next time you reboot, it's gone and your phone is re-locked. To me, that's a lot of effort for something that you lose whenever you reboot your phone, but that's just my opinion. Also, this temporary root is just root - it doesn't unlock your bootloader.
If you absolutely must have a rootable phone with unlocked bootloader, then look elsewhere.
The only thing that we do have is debloater, which is a method that allows us to turn off and block almost anything we want. For me, that's enough, because the only reason I'd want root is to uninstall all of the crap that comes with this phone. It doesn't get rid of the junk, it just turns it off and keeps it from running.
If you want root to be able to install an ad blocker or to install custom kernels and/or ROMs, you cannot do it on this phone and likely (in my opinion), never will be able to.
Click to expand...
Click to collapse
I'm happy with a temp root, itll fit my purposes. Can you point me in that direction? and the debloaters direction?

yes sad, so sad that Permanent root was never fount! I am disappointed with Verizon over this......

DikStarrbuck said:
I'm happy with a temp root, itll fit my purposes. Can you point me in that direction? and the debloaters direction?
Click to expand...
Click to collapse
It's all in topics in the forum. Easy to find if you look.
Sent from my SM-N910V using XDA Free mobile app

RedsonRising said:
It's all in topics in the forum. Easy to find if you look.
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Yea, theres SO much stuff in the forum, I honestly dunno what to look for. I'll keep at it, thanks

So what if u have a bootloader that starts with 15? I got 90% on kingoroot running a crap ton of random apps in the backgroundI thought I had it but bam root failed keep in mind I'm on marshmallow to anyone else get 90% are we really close or is it just a trick lol

custom_roms_epeptic said:
So what if u have a bootloader that starts with 15? I got 90% on kingoroot running a crap ton of random apps in the backgroundI thought I had it but bam root failed keep in mind I'm on marshmallow to anyone else get 90% are we really close or is it just a trick lol
Click to expand...
Click to collapse
So your bootloader is unlocked already, correct? You need to have an unlocked bootloader and be running Lollipop, here's the thread that shows you how/what to do...
https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
I used the instructions in that thread and didn't have any issues.

driguy said:
So your bootloader is unlocked already, correct? You need to have an unlocked bootloader and be running Lollipop, here's the thread that shows you how/what to do...
https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
I used the instructions in that thread and didn't have any issues.
Click to expand...
Click to collapse
Thanks bud I'll try it tonight! I gone like 6 pages into Google trying to find something that works I got a little confused on the baseband version part. This is a silly question but if I have mine on
N910VVRU2CPF3 and use Odin and flash version: N910VVRU1ANJ5 it won't brick my device? And no my bootloader is not unlocked yet

custom_roms_epeptic said:
Thanks bud I'll try it tonight! I gone like 6 pages into Google trying to find something that works I got a little confused on the baseband version part. This is a silly question but if I have mine on
N910VVRU2CPF3 and use Odin and flash version: N910VVRU1ANJ5 it won't brick my device?
Click to expand...
Click to collapse
You'll want to flash the N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar .md5 file in ODIN as that is the firmware that Lollipop expects/works on. I don't know what android version N910VVRU1ANJ5 firmware is for. Flashing N910VVRU1ANJ5 shouldn't brick your phone but you will need to have it on N910VVRU2BPA1 to install Lollipop and root.
Trust me, just follow the instructions in the post I previously linked. It's all laid out for you in what is pretty much the easiest way you can do it. As long as you do it in the order listed, with the files provided, it will work.

driguy said:
You'll want to flash the N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar .md5 file in ODIN as that is the firmware that Lollipop expects/works on. I don't know what android version N910VVRU1ANJ5 firmware is for. Flashing N910VVRU1ANJ5 shouldn't brick your phone but you will need to have it on N910VVRU2BPA1 to install Lollipop and root.
Trust me, just follow the instructions in the post I previously linked. It's all laid out for you in what is pretty much the easiest way you can do it. As long as you do it in the order listed, with the files provided, it will work.
Click to expand...
Click to collapse
Nj5 was kitkat but I will flash the version you said I greatly appreciate it

Wait hold on my bootloader is locked will it still work? Sorry for the annoying questions I'm a little rusty cause I only get a new phone every 2 years so I barely ever root lol

Rooting this phone is pretty tricky and you may have to repeat the process a few times for it to work. Follow the guide custom_roms_epeptic posted, that's the one I used and even though it took me a couple hours to go from stock to Nseven, it did indeed work. I would recommend using the version of kingoroot found in the zip contained in that guide, I tried kingroot and the newest version of kingoroot and both got hung up at 90% or just didn't work at all.

custom_roms_epeptic said:
Wait hold on my bootloader is locked will it still work? Sorry for the annoying questions I'm a little rusty cause I only get a new phone every 2 years so I barely ever root lol
Click to expand...
Click to collapse
Part of the steps you will be doing will be to unlock the bootloader, this is mandatory. If your CID starts with 15, you can change the CID of your device to that of a dev edition device, which can then have its bootloader unlocked. Like I said before, it's all laid out for you in the other thread.

driguy said:
Part of the steps you will be doing will be to unlock the bootloader, this is mandatory. If your CID starts with 15, you can change the CID of your device to that of a dev edition device, which can then have its bootloader unlocked. Like I said before, it's all laid out for you in the other thread.
Click to expand...
Click to collapse
Okay so I FLash the downgrade and then unlock the bootloader
,? Yes?

Looking for PIT files for SM-N910P

I'm looking for the PIT files for Sprint's Note 4. Or does anyone know if the PIT for SM-N910F will work. Is the (F) version compatible in all of the Sprint versions. I.E. when looking for Sprint programs there is no SM-N910(P) but always a SM-N910(F). Is it safe to use the F version? Or is there a safe way to update/redo the bootloaders? I flashed some bad files with Odin right around the BOB7 udate and my device has been spinning in circles around that since. Even if I go full stock and Odin the latest firmware my device is set back to that period from a protected file that is in between bootloaders. I can't touch it. The closest I can get is with a terminal command from TWRP [/sbin/recovery] I can then chmod the files and erase or do whatever with them but they are restored in cold boot. Even after flashing the official firmware it reverts to the files from BOB7. What's really crazy is I'm running stock firmware so can not use xposed but if I mount data and system wipe and then run uberwipe my device will boot with xposed apps functional. It is as if I am running two ROMS one that can not be removed or changed. I can see it happening but not from where exactly. In cold boot it loads the RO biuld from /dev/block/platforms/msm_scc1.by_name/hidden. I can find everything but the hidden. In the stock recovery logs it says the command to fix it is wipe_data_crypto but I can't accomplish it. Any suggestions?

PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk

samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
Yes I'm getting ready to flash bootloaders big AF. I will two the pit files first but if that doesn't work I've got a list. Involves downgrading to kit kat, rooting with auoto root (can't screw me thrice) running triangle away to lose the warranty bit, installing xposed and wanam so as to make it read official. Once samsungs stuff isn't all a scared anymore I delete the /dev/block/platform/msm1_byname/hidden/rape the dumbass that used to trust developers he didn't know until he knew better and the rape was done.
I'm not really looking to flash boot loaders per say. I realized that you can only install a newer version and I TiVo I'm out of updates if I need a new bootloader. Just went to erase the obtrusive piece of poo hidden in between the 2 bootloaders. I'm not even sure theres supposed to be 2 bootladers. I look at samsuny stock firmware it's nothing like the billithera of extra stuff I have on my device. Can't say for sure who caused it because I did some retarded stuff when I was even greener than I am now. But whether it be auto root or srs unlock that super su is obtrusive as it gets. The purpose of root was flee me the user to gain access tip everything. The whole limiting the user and granting permission to every creepy fook on this planet to stock me and my kids is not what I had in mind. These people are so adamant about their creepy stalking not only is my devices esp network cut by 90% they do dangerous stuff like hidden robuilds that has a value of 1 where the radio don't shut off I airplane mode.

samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I appreciate the advice. I hope to avoid allot with the PIT. That's what flashfire back up says it needs. Shutting the phone of is a good idea. The recovery log was actually making fun of me for not. Along with the simple command I needed to open /sbin/recovery then wipe cane and data crypto. The /sbin/recovery was an eye opener (try it from the emulator in twrp to see if root has crippled you. The thing is most of us use a universal supersu update to reinstall and that is not good. That is written to take out the marines if that's what it takes to accomplish root. Remember the food old days when superuser binary was a line compatible with your cu?
Anyways another good command people don't know is if odin fails don't pull the battery. I put am s4 tip sleep forever that way. volumedwn home and power reatart the bootloader and wipe the cache for the software out is rejecting.
Yes I'm getting ready to flash bootloaders big AF. I will two the pit files first but if that doesn't work I've got a list. Involves downgrading to kit kat, rooting with auoto root (can't screw me thrice) running triangle away to lose the warranty bit, installing xposed and wanam so as to make it read official. Once samsungs stuff isn't all a scared anymore I delete the /dev/block/platform/msm1_byname/hidden/rape the dumbass that used to trust developers he didn't know until he knew better and the rape was done.
I'm not really looking to flash boot loaders per say. I realized that you can only install a newer version and I TiVo I'm out of updates if I need a new bootloader. Just went to erase the obtrusive piece of poo hidden in between the 2 bootloaders. I'm not even sure theres supposed to be 2 bootladers. I look at samsuny stock firmware it's nothing like the billithera of extra stuff I have on my device. Can't say for sure who caused it because I did some retarded stuff when I was even greener than I am now. But whether it be auto root or srs unlock that super su is obtrusive as it gets. The purpose of root was flee me the user to gain access tip everything. The whole limiting the user and granting permission to every creepy fook on this planet to stock me and my kids is not what I had in mind. These people are so adamant about their creepy stalking not only is my devices esp network cut by 90% they do dangerous stuff like hidden robuilds that has a value of 1 where the radio don't shut off I airplane mode.

samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man

TheMadScientist420 said:
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man
Click to expand...
Click to collapse
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk

samep said:
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
i dont know the problem seems to have been in a update.. playing with it for a while it started charging and turned on and finished a update....
i got a s6 active did the same thing to me just started working i run it for like 6 months no probs
of coarse its on sprints black list just found out due to non payment of ezpay. but ill deal with that on my own as such talks are downed and frowned upon.
man i got this thing for 20 bucks.... even if nothing else my buddy needs a screen for one in his shop. but most def thank you for responding..
too further your post i do all my own repairs ussually the cheapest route currently behind the wheel of a unrootable verizon note 5 and a lgg4 which is rooted but no twrp method available. each i have very little invested in.

I never could find the files. The link was valid, samep, it just refused to let me have them. It turns out it is easier to get them off your own device and I've zero doubt they are for the 32gb Sprint Note 4. At least mine anyways. I tried the down grade to kitkat which would have worked because it downgrades you boatloader at least according to the page. I got a failed md5. So it wouldn't supirise me if these pit files are different than what the stock one was. Hard to tell what you have, for sure, when you are a flash junk that trusts random people on the inter web. At least I was/did. I gave myself this when it was brand new. It was hard to get it going again. I back up worked with plasma kernel then on the next official it was right again, well almost, I've had this problem almost two years now. I went without root for a while so didn't notice.
I
I hope this fixes it. If not I'll find the right files for the kk downgrade. It would be sweet to go back anyways. I'll leave a link in the next thread for the pit.

TheMadScientist420 said:
i dont know the problem seems to have been in a update.. playing with it for a while it started charging and turned on and finished a update....
i got a s6 active did the same thing to me just started working i run it for like 6 months no probs
of coarse its on sprints black list just found out due to non payment of ezpay. but ill deal with that on my own as such talks are downed and frowned upon.
man i got this thing for 20 bucks.... even if nothing else my buddy needs a screen for one in his shop. but most def thank you for responding..
too further your post i do all my own repairs ussually the cheapest route currently behind the wheel of a unrootable verizon note 5 and a lgg4 which is rooted but no twrp method available. each i have very little invested in.
Click to expand...
Click to collapse
Did you fix it? Your right totally worth it for the screen. You can unlock the imei. I only did it once just because some people are so adamant you can't. I like to believe anything is possible. I don't feel bad about getting those non paid because the phone companies are the thieves. Especially in the US. They bury a lot of people locking you down to have a phone and the policy on being to stupid to fix anything is raw. With two kids I paid out a lot of dead phones. It takes rooting one phone to have bested the entire knowledge of tech at sprint. That's the hard part. If they sold parts it would be nothing.
TheMadScientist420 said:
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man
Click to expand...
Click to collapse
Sent from my SM-N910P using XDA-Developers mobile app

PIT_SM_N910P
https://mega.nz/#!cJREFYqS
Sent from my SM-N910P using XDA-Developers mobile app

planb234 said:
Did you fix it? Your right totally worth it for the screen. You can unlock the imei. I only did it once just because some people are so adamant you can't. I like to believe anything is possible. I don't feel bad about getting those non paid because the phone companies are the thieves. Especially in the US. They bury a lot of people locking you down to have a phone and the policy on being to stupid to fix anything is raw. With two kids I paid out a lot of dead phones. It takes rooting one phone to have bested the entire knowledge of tech at sprint. That's the hard part. If they sold parts it would be nothing.
Sent from my SM-N910P using XDA-Developers mobile app
Click to expand...
Click to collapse
Y3a it just decided it was gonna start workin heck yea.
The battery is trashed on it. Im gonna order one here soon
Ive flashed a few roms on it. Rooted. But everytime i restart it the bat percentage is totally diffrent.. thank you. I got a s6 once same way
Wouldnt do nothing. Plyin with it and decided to boot up.
Again i know talks of bad imeis are not good conversation. But i use cdma workshop and basicly took a old sammy i had that was junk and destroyed it. Took the sticker and rewrite a new iemi. Havent done it yet but. When i get there i know i can.
Ofcoarse now i cant unlock it even if i follow all the guides. Ive tried and tried.

TheMadScientist420 said:
Y3a it just decided it was gonna start workin heck yea.
The battery is trashed on it. Im gonna order one here soon
Ive flashed a few roms on it. Rooted. But everytime i restart it the bat percentage is totally diffrent.. thank you. I got a s6 once same way
Wouldnt do nothing. Plyin with it and decided to boot up.
Again i know talks of bad imeis are not good conversation. But i use cdma workshop and basicly took a old sammy i had that was junk and destroyed it. Took the sticker and rewrite a new iemi. Havent done it yet but. When i get there i know i can.
Ofcoarse now i cant unlock it even if i follow all the guides. Ive tried and tried.
Click to expand...
Click to collapse
There's a couple of ways to calibrate the battery. the easiest is a root app in Play "Battery Calibrator" it resets the stats at 100% Another is *#0228# I believe you calibrate it then let it run all the way dry then charge it to full with the system off. Not too hard to find if you want to give it a shot. It's hard to say what the problem is. I just got a new one because the old was dying at 30%. I use both and they take turns on which one is weak. Neither is a problem with out root. I probably have too much working Or to much stuff in the background.
I've heard that about changing the sticker. i only change the sticker if I used another phone for the screen. It matches what is in the board that way, If you take it in the store to get it activated they may be a little less confused.
I took an S4 that was compiled of 3 previous ones and my daughters that just stoppede working to get activated at sprint. Of course he couldn't. His story the same "When you work on them .. . He was pretty adamant that as it. I couldn't figure out how that affected both of them. So i took it home and activated it myself. Turns out the S4 is a dual band so he generally has a 50% succes rate it will turn on in the mode.
The sticker definitly won't get it activated. I've got an LG3 that was given to me by some who did't care about sprint anymoe that was Imei locked out activated. It was $100 bucks for the server. The server was. It unlocked a s5 also that a jerk sold me was clean. It unlocked it too. It was through verizon so i never activated it. I was trying to flop it to sprint when it disappeard .I unloced my note 4 with it to. The SIM so the APNs aere never locked altough I'm not positve it could have been GTidonetehapp that did it. I did' know what I ws doing, I just like plaing with them. No real reason to unlock a phone you own. Well ther is the hotspot. I'm pretty sure that's how I crumbed up my note and my puter to. I dropped exec files in my win 32 folder and flashed in something with a crazy odin to get my phone unlocked. But again not positive, thier stuff workied so it was just to give my equiment herepes.

planb234 said:
PIT_SM_N910P
https://mega.nz/#!cJREFYqS
My bad. I did not know that there has to be a key for mega. This one should do better.
Fwd: https://www.dropbox.com/sh/b0b3ywj5rbiec7h/AAAUM9TvOLUCDPJXXZTZBd_Ea?dl=0
Click to expand...
Click to collapse

planb234 said:
There's a couple of ways to calibrate the battery. the easiest is a root app in Play "Battery Calibrator" it resets the stats at 100% Another is *#0228# I believe you calibrate it then let it run all the way dry then charge it to full with the system off. Not too hard to find if you want to give it a shot. It's hard to say what the problem is. I just got a new one because the old was dying at 30%. I use both and they take turns on which one is weak. Neither is a problem with out root. I probably have too much working Or to much stuff in the background.
I've heard that about changing the sticker. i only change the sticker if I used another phone for the screen. It matches what is in the board that way, If you take it in the store to get it activated they may be a little less confused.
I took an S4 that was compiled of 3 previous ones and my daughters that just stoppede working to get activated at sprint. Of course he couldn't. His story the same "When you work on them .. . He was pretty adamant that as it. I couldn't figure out how that affected both of them. So i took it home and activated it myself. Turns out the S4 is a dual band so he generally has a 50% succes rate it will turn on in the mode.
The sticker definitly won't get it activated. I've got an LG3 that was given to me by some who did't care about sprint anymoe that was Imei locked out activated. It was $100 bucks for the server. The server was. It unlocked a s5 also that a jerk sold me was clean. It unlocked it too. It was through verizon so i never activated it. I was trying to flop it to sprint when it disappeard .I unloced my note 4 with it to. The SIM so the APNs aere never locked altough I'm not positve it could have been GTidonetehapp that did it. I did' know what I ws doing, I just like plaing with them. No real reason to unlock a phone you own. Well ther is the hotspot. I'm pretty sure that's how I crumbed up my note and my puter to. I dropped exec files in my win 32 folder and flashed in something with a crazy odin to get my phone unlocked. But again not positive, thier stuff workied so it was just to give my equiment herepes.
Click to expand...
Click to collapse
I do my own i jusf activate sim cards the sticker is basicly for my refrance i sell a lot of phones but i keep ones like this for myself. So theres no issues i just swap sims all the time so no need for activations

planb234 said:
I never could find the files. The link was valid, samep, it just refused to let me have them. It turns out it is easier to get them off your own device and I've zero doubt they are for the 32gb Sprint Note 4. At least mine anyways. I tried the down grade to kitkat which would have worked because it downgrades you boatloader at least according to the page. I got a failed md5. So it wouldn't supirise me if these pit files are different than what the stock one was. Hard to tell what you have, for sure, when you are a flash junk that trusts random people on the inter web. At least I was/did. I gave myself this when it was brand new. It was hard to get it going again. I back up worked with plasma kernel then on the next official it was right again, well almost, I've had this problem almost two years now. I went without root for a while so didn't notice.
I
I hope this fixes it. If not I'll find the right files for the kk downgrade. It would be sweet to go back anyways. I'll leave a link in the next thread for the pit.
Click to expand...
Click to collapse
I do believe you have to sign into Sammobile to download files.
The PIT can also be found in the first stock tar for each OS update; the developer I linked says that the PIT hasn't changed. I've seen methods to extract PIT from phone but they don't match md5 when checked. I checked your linked PIT in the post above and it doesn't match either. I wouldn't recommend using that one.
If your phone has ever updated beyond OB7, you can't Odin full stock KitKat tars or OB7 stock tar. The bootloader will block the Odin flash.
Not looking at your phone, it's hard to say what's going on. But I hope the feedback helps. Ask if you have further questions; I'll try to reply, but I haven't experienced what you've having issues with. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk

samep said:
I do believe you have to sign into Sammobile to download files.
The PIT can also be found in the first stock tar for each OS update; the developer I linked says that the PIT hasn't changed. I've seen methods to extract PIT from phone but they don't match md5 when checked. I checked your linked PIT in the post above and it doesn't match either. I wouldn't recommend using that one.
If your phone has ever updated beyond OB7, you can't Odin full stock KitKat tars or OB7 stock tar. The bootloader will block the Odin flash.
Not looking at your phone, it's hard to say what's going on. But I hope the feedback helps. Ask if you have further questions; I'll try to reply, but I haven't experienced what you've having issues with. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yeah it didn't work . It just shut down . I'll explain what has going on. Thank you for this post. It's good to know there's more options.
I actually did take a note 4 and s4 back. It dependes on how they upgraded. The bootloader doesn't change in an fota. I could do the s4 again now.
Thanks again for the awesome info.

TheMadScientist420 said:
I do my own i jusf activate sim cards the sticker is basicly for my refrance i sell a lot of phones but i keep ones like this for myself. So theres no issues i just swap sims all the time so no need for activations
Click to expand...
Click to collapse
You don't have to unlock the SIM or anything? Even if you do that's a lot less than getting the imei forgot about. Don't you have to get an msl from a comany. I know it's very possible send easy in free countries but i live in murica. You pay and pay here and the still put a cap on the data. If we're not careful we may use up all that data and then there would be no way to watch us 24-7 just we might go rogue.
A sticker that changes the sim? Details please.

samep said:
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I've been trying to reply to this for 2 days. You see it's not the way my phone runs that is the issue it is my network that is completely raped. I can't lose my parasite. I screwed up my bootloader petty bad when I was learning about Samsung. If you ask how to unlock a bootloader the most common answer you get is "you don't, you use auto root". Auto root is as amazing for sure but I can tell there is a lot of people who don't read anything and just do. The the disclaimer is "don't use this with a locked boot loader, you will likely brick your device." As i mentioned I'm a flash junky. I didn't know once you blew the hole in thy boot you only needed a custom recovery forever. I like changing roms so i rooted with it a couple more times. Things for real bad after I ran the kitkat auto root on lollipop. I could use one of my back ups and add plasma kernel for a few months until the next update. Worse than that i flashed a something from an unlock sight with a special version of Odin. I didn't even need to because i had all ready changed the csc to xas so my apns were open. The effects were scary but cool. I got locked out of my phone for awhile except for virtual access on my puter screen. My home network for straight raped after that. I had everything set to home and share because i didn't think there would be even more bored than me so as to waste there life watching my life. There is and they are smart as #. I go in intervals of being angry to amazed. I thought they were gone but no. I was not keen on interweb when i got on here. Now that i could protect myself I can't keep the evil at bay because it lurks in the dark spaces I can't reach. FlashFire says it can remove the seemles. It is incredible to but I don't think so. It definitely can't mine. What's crazy is I've had a couple new bootloaderers since then but it remains. I'm with out root at the moment and am able to look at some of the data and dev were files. I can see the usb files that block adb is in but still no. Even though auto root totally changes the way and where from the device boots, I'm needing to extract or other wise terminate what is probably one card a ftp or smb. I can see in my win logs that if uses a machine to confuse the system in a barrage of security log ins while opening a door for daddy. I had the xml explaing how it's done but then a brand new 125gb card magically went to sleep forever. Some script out there is beyond amazing to me. Virtual net adapters that aren't on top of actual hardware blow my mind. It would have never crossed my mind in a million years they there is going to be a need for antivirus software on hardware like a Bluetooth keyboard.

planb234 said:
You don't have to unlock the SIM or anything? Even if you do that's a lot less than getting the imei forgot about. Don't you have to get an msl from a comany. I know it's very possible send easy in free countries but i live in murica. You pay and pay here and the still put a cap on the data. If we're not careful we may use up all that data and then there would be no way to watch us 24-7 just we might go rogue.
A sticker that changes the sim? Details please.
Click to expand...
Click to collapse
this device had a bad iemi person i got it from said they didnt pay for it on the sprint ezpay.
i checked and that was the truth. so i changed the iemi with another old sammy i had and put the sticker in for my records. so i know what the new iemi is without the device being turned on.
im trying to sim unlock it so i can use it on domestic gsm but no go sofar always invalid sim.
i guess i need to take this dissussion to another thread as so i dont get to far off the orig topic here

@planb234
I'm not following well what you've tried since getting a PIT file. Did you get the PIT file from Sammobile yet? Did you try the latest stock tar? If older ones, which ones fail?
If Odin fails, can you post the log and text on screen?
I believe what you're talking about is not needing to root if flashing a custom ROM. After a stock tar, you could Odin TWRP and flash a custom ROM. Custom ROMs include root and su. If using Chainfire Auto Root for Note 4, make sure to use the right one and latest for Lollipop and Marshmallow. KitKat had its own Auto Root. But the auto root uses a modified stock recovery which may make its use redundant if flashing a custom or even wanting just TWRP for backups if stock rooted.
Some fun facts for you:
The bootloader on Sprint Note 4 is unlocked. Flashing a stock tar will un-root it. Factory reset will cause you to lose systemless root. But flashing a full stock tar successfully will replace the bootloader. If you're trying to flash OB7 or older KitKat stock tar, your bootloader won't be replaced. As far as OTA, it patches existing baseband, bootloader and effected system files and partitions that need patched. Even if it's just a revision number in the update, it gets rolled up to match the update revision. While I feel stock tar updates are full and need no patching, the patching is sequential and should match the Odin'd bootloader and baseband once sequentially rolled up accordingly. So IMO, a patched bootloader is same as newly Odin'd bootloader. I could be wrong about the patching so not necessarily a fact.
I think your problem is unsuccessful flash of full stock tar. A blown eFuse may cause that but from what I've read in past posts of others that had issues back then is that flashing the correct stock tar after full wipe in stock recovery overcomes the flash. It leads me to believe it's only activating reset protection to try to roll the bootloader back to OB7 or KitKat. Maybe I'm wrong but if your phone isn't suffering a hardware issue, you should be able to recover it.
Other bootloaders between OB7 and OG5 like OE1 and OF5 were also exhibiting an inability to downgrade but bootloaders OG5 and up can so far can be downgraded to OG5. I haven't tried downgrading bootloader to OE1 or OF5 though.
I've seen phone info from posters claiming to roll their bootloader back to OB7 or older and they've actually reported a newer bootloader, post OB7.
As far as I know, the only true way to get KitKat ROM to flash and boot is to flash a newer kernel after ROM flash, but prior to initial boot attempt. Currently, I'm only aware of Android 5.1.1 kernel and post OB7 bootloader booting a KitKat ROM after bootloader is updated beyond OB7.
If you're capable of doing otherwise, I'd like to see legit screenshot of phone info or galaxy tools application.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Sent from my SM-N910P using Tapatalk

Help Installing Custom Recovery on LG G Pad 8.3

So i just got this tablet out of the blue, didnt realy expect it and its not something thats really needed but it could come in handy. I figured id mod the hell out of it so it would be ready to go when i did decide to use it. I figured it being a name brand that doing all this would be easy. I havnt even looked into ROMs yet id figured id start with some custom recovery TWRP. Everything has been a complete disaster tho.
I had the thing for less than a few hours and done had it bricked and then about 10 more times after that. Ive been able to unbrick each time using the LG Flash Tool 2014 and a stock android 4.2.2 rom. I have the newer stock roms up to 5.?.? whitch is what i think was oroginal on it when i got it, but i figured downgrading would make everything easier. I still cant get anything to work right ive watched dozens of videos and posted and there so much crap out there its kinda hard to know what to use and to try, Were my particular tablet works into this time line.
Ive tried simple one click stuff that i think was the original tools. Ive tried the apps on the device. Ive tried hooking up to the pc. Using the command line on pc and on phone. Ive tried a million and one diffrent tools, programs, and files. My whole desktop is filled up with crap. The one thing i am able to do is root the drvice using kingroot but i beleave thats the one app you guys dont realy aprove of, but its so easy to use. I tried using some other root methods to see if that would help, but it didnt.
I read some were about the bootloader being locked and that being the problem, So i tried different things to unlock that but no luck. Then there was something about needing to downgrade the bootloader to the 4.?.? version or something, IDK. I am so lost any more idk were to go from here. I only get a new android device every few years because as long as it makes call i dont care and i dont tend on modding it all that much because theres the possibility i could be with out a phone for a few days. ive always been pretty good at modding stuff over the years but it just seems like android stuff just gets harder and harder over the years. Its starting to be more trouble then its worth but i guess thats the point. Ive always love doing this stuff but i just dont have the time like i use to spend all day looking this stuff up and getting stuff done but i just dont have the time to do that anymore. My eyes and back cant handle the hours starring down the keybored like they use to. Sometimes taking brakes screws up my concentration and it takes me a minute to get back on track.
Anywase like i said im kinda lost not sure were to go from here and i just figured id post and see if anybody would through me a line. If not well its cool ill figure it out eventually or just use it the way it is.
Dont have original info - I know I should have wrote everyhting down before diving in, but i didnt. This info is from the current stock ROM installed
Model # VK810 4G
Hardware Version # Rev.1.0
Android Version # 4.2.2
Baseband Version # M9615A-CEFWTAZM-4.0.10353
Kernal Version # 3.4.0
Build # JDQ39B
Software Version # VK81011A
Any other needed info please ask.
O its from Verizon

Did i post this in the wrong place.

I encountered the same problem but i've solved it by downgrading the stock ROM because the recovery is locked with last version of stock ROM.

BololFR said:
I encountered the same problem but i've solved it by downgrading the stock ROM because the recovery is locked with last version of stock ROM.
Click to expand...
Click to collapse
I downgraded the stock rom still couldn't get it to do anything.

telcar said:
I downgraded the stock rom still couldn't get it to do anything.
Click to expand...
Click to collapse
Which version do you have ?
Have you root your device ?
Have you try Official TWRP App for flashing recovery ?

BololFR said:
Which version do you have ?
Have you root your device ?
Have you try Official TWRP App for flashing recovery ?
Click to expand...
Click to collapse
All that info was given in my original post at top

Updating question

Ok, I start this off with the fact that this is my first phone with the whole slot A&B thing. I've done a ton of reading but it's still very confusing to me. I'm very confused on what exactly to do when it comes to updates. I'm stock rooted with TWRP installed on slot A. I'm also on the December build. I would like to update but I don't know what the easiest way to go about it is to be honest. I feel like an idiot but I guess that's because I'm really old school when it comes to this stuff. My rooting/roming goes back to the Samsung Captivate and countless other phones up until it got to be too much of a hassle to get a phone from a carrier that could be messed with. Now that I have rambled on, I thought it would be different getting a Pixel but this whole slot thing has me all confused. I basically want to stay stock rooted for now and possibly try a kernel down the line but I'm very happy with stock for now. Any advice would be greatly appreciated.
Thanks

pside15 said:
Ok, I start this off with the fact that this is my first phone with the whole slot A&B thing. I've done a ton of reading but it's still very confusing to me. I'm very confused on what exactly to do when it comes to updates. I'm stock rooted with TWRP installed on slot A. I'm also on the December build. I would like to update but I don't know what the easiest way to go about it is to be honest. I feel like an idiot but I guess that's because I'm really old school when it comes to this stuff. My rooting/roming goes back to the Samsung Captivate and countless other phones up until it got to be too much of a hassle to get a phone from a carrier that could be messed with. Now that I have rambled on, I thought it would be different getting a Pixel but this whole slot thing has me all confused. I basically want to stay stock rooted for now and possibly try a kernel down the line but I'm very happy with stock for now. Any advice would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
@Homeboy76 will get you squared away :good:
https://forum.xda-developers.com/pi...-android-9-0-pie-unlock-t3857195/post77944292

Badger50 said:
@Homeboy76 will get you squared away :good:
https://forum.xda-developers.com/pi...-android-9-0-pie-unlock-t3857195/post77944292
Click to expand...
Click to collapse
Thanks for the reply. I've read throughout that thread numerous times and I still can't determine the easiest way to update my phone and the necessary steps to take to get there. I just want to be stock rooted like I am now but don't know what steps to take to get there. Like do I need to unroot first, relock bootloader? I'm sure all those answers are in that thread but I'm probably just too dense to see them. I haven't really had a solid rooted phone in like 3 years so I'm used to things being done way different. Some times I miss my old HTC Inspire/Desire HD. There was so much development for that phone and it was all very straightforward.

pside15 said:
Thanks for the reply. I've read throughout that thread numerous times and I still can't determine the easiest way to update my phone and the necessary steps to take to get there. I just want to be stock rooted like I am now but don't know what steps to take to get there. Like do I need to unroot first, relock bootloader? I'm sure all those answers are in that thread but I'm probably just too dense to see them. I haven't really had a solid rooted phone in like 3 years so I'm used to things being done way different. Some times I miss my old HTC Inspire/Desire HD. There was so much development for that phone and it was all very straightforward.
Click to expand...
Click to collapse
This guide is how I update the monthly security patches. It is predicated on the notion that you have the latest platform-tools (28.0.1) and that your computer and phone are communicating well. It doesn't not require you to switch slots, and it will not wipe your data, and, you do not have to unroot before you begin. Happy flashing, and good luck
And never ever ever relock the bootloader! :crying:

Badger50 said:
This guide is how I update the monthly security patches. It is predicated on the notion that you have the latest platform-tools (28.0.1) and that your computer and phone are communicating well. It doesn't not require you to switch slots, and it will not wipe your data, and, you do not have to unroot before you begin. Happy flashing, and good luck
And never ever ever relock the bootloader! :crying:
Click to expand...
Click to collapse
Awesome, thank you very much for that. Yeah, I figured that about the bootloader. Does it matter if I have TWRP installed? That's the one main confusing thing to me. How you can have TWRP installed or not installed. I'm used to absolutely having to have TWRP or some other kind of custom recovery installed. But like I said it's been quite a while since I was really able to root/ROM a phone. I was basically forced to move to AT&T and opted for the Active line of Galaxy phones since I have little kids plus even the phones that were rootable and such seemed like more of a hassle than it was worth. The last phone I had that had some good development was probably the LG G3 on T-MOBILE. For some reason the T-MOBILE version had an unlocked bootloader or could be unlocked, don't remember exactly. But then a coworker got a Pixel 2XL and I got the itch again, not knowing how much had really changed though. Ok, I think I've rambled on enough now. Thanks again for the help.

pside15 said:
Awesome, thank you very much for that. Yeah, I figured that about the bootloader. Does it matter if I have TWRP installed? That's the one main confusing thing to me. How you can have TWRP installed or not installed. I'm used to absolutely having to have TWRP or some other kind of custom recovery installed. But like I said it's been quite a while since I was really able to root/ROM a phone. I was basically forced to move to AT&T and opted for the Active line of Galaxy phones since I have little kids plus even the phones that were rootable and such seemed like more of a hassle than it was worth. The last phone I had that had some good development was probably the LG G3 on T-MOBILE. For some reason the T-MOBILE version had an unlocked bootloader or could be unlocked, don't remember exactly. But then a coworker got a Pixel 2XL and I got the itch again, not knowing how much had really changed though. Ok, I think I've rambled on enough now. Thanks again for the help.
Click to expand...
Click to collapse
Doesn't matter if you have twrp installed or not. When you fastboot the update, it'll wipe it out anyway :good: