Related
I've been rooting since OG Evo days, but only played with that, the s2, and s3. Rooting was easy as pie. But with all this knox stuff I'm wary.
I recently read reports of people sending in their phones to both Samsung and tmobile and getting it back with knox restored but still maintaining sim unlocks. So obviously it's a well kept firmware they flash or perhaps signatures.
This in mind I used kingoapp, and root was easy. Just decline the recovery install and you'll maintain 0x0. But after this new information I'm still worried to trip knox for fear those restores we're just a fluke.
Anybody have luck with safestrap? I heard/read it doesn't replace recovery so it also won't trip knox? Also, as long as I don't flash kernels or recovery I'll be good right? Like i can delete bloat or install at root level to /system and I'll be fine?
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
I've been rooting since OG Evo days, but only played with that, the s2, and s3. Rooting was easy as pie. But with all this knox stuff I'm wary.
I recently read reports of people sending in their phones to both Samsung and tmobile and getting it back with knox restored but still maintaining sim unlocks. So obviously it's a well kept firmware they flash or perhaps signatures.
This in mind I used kingoapp, and root was easy. Just decline the recovery install and you'll maintain 0x0. But after this new information I'm still worried to trip knox for fear those restores we're just a fluke.
Anybody have luck with safestrap? Also, as long as I don't flash kernels or recovery I'll be good right? Like i can delete bloat or install at root level to /system and I'll be fine?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As long as you just root it nothing happens system will be fine .... Plssss hit thanksss.....
Sent from my HTC Desire C using XDA Premium 4 mobile app
pvinayraju2k4 said:
As long as you just root it nothing happens system will be fine .... Plssss hit thanksss.....
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the info. However in the future there's no need to request we thank. I've learned most people here on xda thank quite often, myself included.
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
Thanks for the info. However in the future there's no need to request we thank. I've learned most people here on xda thank quite often, myself included.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First off, the above poster is wrong... can't believe he asks for a thank. When you install a custom recovery, that is when you trip Knox. There a method to install a custom ROM w/o a recovery using Mobile Odin Pro. I know nothing about that but have read here that it works. You just can't flash custom kernel. I went ahead and flash a custom recovery because I don't care about Knox and will never send this phone to Samsung for warranty repair.
asianflavor said:
First off, the above poster is wrong... can't believe he asks for a thank. When you install a custom recovery, that is when you trip Knox. There a method to install a custom ROM w/o a recovery using Mobile Odin Pro. I know nothing about that but have read here that it works. You just can't flash custom kernel. I went ahead and flash a custom recovery because I don't care about Knox and will never send this phone to Samsung for warranty repair.
Click to expand...
Click to collapse
Just the fact most of us have insurance plans; if we discover a problem such as faulty gps or screen displacement, etc, tmobile fixes it for us anyway, right?
So it really doesn't matter if we trip knox, correct???
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
Just the fact most of us have insurance plans; if we discover a problem such as faulty gps or screen displacement, etc, tmobile fixes it for us anyway, right?
So it really doesn't matter if we trip knox, correct???
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
From everything I read, yes.
Sent from my SM-N900T using Tapatalk
asianflavor said:
First off, the above poster is wrong...
Click to expand...
Click to collapse
He's not wrong. There are a couple different methods of rooting that don't require a custom recovery, therefore don't trip Knox.
Sent from my SM-N900T using Tapatalk
asianflavor said:
From everything I read, yes.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I guess I shouldn't bother with safestrap then. Was planning on trying to pay off the note 3 and keep it anyway instead of jumping again this year.
Either way it won't matter...until I do eventually get a new handset but even then I know enough about rooting I shouldn't need to repair this one once paid off and detached from my account.
my next question is then should I TWRP or cwm? I tried CWM for the first time since gingerbread on my s3 and fell in love with it
Sent from my SM-N900T using XDA Premium 4 mobile app
Hey Nature! just wanted to add my 0.02, ok theres a difference between rooting, and a difference between flashing recoveries,kernels,roms,and what have you.
ill give a brief explanation in the differences. The Colors of the titles indicate how safe/dangerous it is to modify one of these things and wether it will void your warranty, Green=Wont void your warranty, and easily reversible. Orange=Void Warranty, Reversible, But starting to get Dangerous, Red=Definitely VVoids Warranty, and if screwed up, could ruin/brick your devvice Definitely Voids Warranty, and if screwed up, could ruin/brick your devvice
Rooting: When you are rooting your device, you are basically forcing your stock version of android to allow you (the user) root access, therefore allowing you to bypass/allow signature verification for apps, now this could be anything from homebrew apps that you are making yourself...to the naughty pirated apps, and i dont encourage the latter. By giving yourself root access to your phone, your allowing the next to happen:
Flashing a Custom Recovery: Ok ill explain this as simple as i can...Mostly all if not ALL android phones have a stock recovery, this is a safeguard in case some kind of software fault happened in the phone(stock software fault or what have you). Flashing a custom recovery would be your next step after Rooting a device (IF) you want to go further than apps, meaning Kernels, Roms etc. Now the reason you must Root your device in order to install a custom recovery, is because like explained above signature verification....Now this is when you begin to tread in warranty territory, once flashing a custom recovery...your warranty has become VOID, however what the custom recovery allows you to do is a multitude of things, but the most major is Flashing .ZIP files, which most roms are in the form of, now not only Roms are in ZIP files, so are kernels,mods,baseband firmwares, etc, with that being said, different phones/devices use different methods of flashing roms, lets say for example you somehow screwed something up on a samsung really bad, and it wont boot, however, you can still get into download mode...then you're safe, because samsung uses Odin to flash the entire phone back to stock meaning Recovery/aBoot/Data/System and bring you right back, but if you hard brick it, theres only 3 ways out from that...and they all suck....number one, is call me and send it to me to Jtag it for you ..but it takes long and its not that cheap, #2, Desolder the chip (whichever it is on the device that has caused the problem) and replace it...and thats not an easy task at all, ive done it once to an S3 successfully, after that i never wanted to do it again, and this was back when they were really expensive, and lastly....#3.....and this one is the worse....go buy a new one SO BE CAREFUL!
ROMS: So now that we have a custom recovery, a rom is basically a heavily modified version of Android! and let me tell ya, i love them...i love so many of them, there are sooo many different things that you can do with roms, but the most desired from what ive gathered, is so people can remove the bloatware that comes with their phone when they buy it from the carrier/manufacturer. Thats not all tho, there is way too much to get into, but some roms allow you to Overclock your phones CPU/GPU, and change the Behaviors of the phones hardware, and the major component in roms that allows that is the Kernel.
Kernel: Now dont totally quote me here, im still learning kernels, but a kernel is basically the binary software in the phone, almost like a bios that when modified from stock, changes the behavior of the MOST of the hardware, not all. Now i could be wrong and anyone please feel free to correct me, now i do want to give you a shot of my own advice here...if you dont know what you are doing, kernels are dangerous to a noobie..before i started messing with roms and kernels, i tried to get the best understanding i could, and ill be honest with you, i blew up a couple S3's doing so. but im still learning. so if you're unweary or still not educated enough in the hobby to get too it, please read more up on it, because as none of these guys here that are devs nor people like myself that are trying to help intend to destroy your device on you, so please be careful for your own device's safety, and to save yourself money and a broken heart.
Knox: Ok now correct me if im wrong here, because im still learning as this is new to me, i only saw it on the MJA bootloader on the S4 on Jellybean from Sprint when they first OTA'd it, but knox looks to be Samsungs pathetic try of not lettings us Access the devices binary software, like an encryption, or to only let us access and modify certain things, also samsung has added a flash counter, which will tell them how many times you have flashed a new rom, however there are ways around these things, google and the search bar are you best friends to start, and we can help too.
I Hope this helped and shed some light on some information, and please if anyone has anything to add or to correct me if im wrong anywhere please do so ^_^
P.S. To be totally honest, theres always a way to restore your device and even get the flash counter back to 0 again and put everything back to normal, if an experienced tech looks at it and puts it in download mode unless all is restored, hell be able to see everything, but honestly, if you pay off the phone, you havve nothing to worry about, but then again, i dont care much for warranties, so it all depends on how savvy with fixing problems when they go wrong, but if you ever need i can help you, im pretty experienced when it comes to everything but developing atm, i was a microelectronics major in college, so my expertise is mainly in hardware i.e. if you hard/soft brick the devvice i can usually get it out of that.
please excuse my typing, i type extremely fast, and i have a mechanical keyboard and i think some lettings are startings to give way such as the V key.
---------- Post added at 01:45 AM ---------- Previous post was at 01:29 AM ----------
Naturesretard said:
I guess I shouldn't bother with safestrap then. Was planning on trying to pay off the note 3 and keep it anyway instead of jumping again this year.
Either way it won't matter...until I do eventually get a new handset but even then I know enough about rooting I shouldn't need to repair this one once paid off and detached from my account.
my next question is then should I TWRP or cwm? I tried CWM for the first time since gingerbread on my s3 and fell in love with it
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh and please i Highly suggest using Philz Touch!
Code:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltetmo
Thats for the HLTETMO version, which is our versions in this forum, all credit to phil ofcourse, it is basically CWM, but so much more user friendly and advanced with much more options, there are two files there, you obviously want the latest version, and there are two ways to do it, if you download the tar.md5 you must use Odin, and put your phone in download/odin mode, very easily done (turn it off unplug usb and press Home+Vol Dwn+Pwr) then once the screen pops up press Vol Up and then plug the USB in, and follow the instructions of w/e tutorial you are ready, but be very careful in odin mode, if you disturb the phone while its flashing you will most likely brick it, and the .zip is considering you already have a custom recovery and you can just flash it through there.
MasterSe7en said:
Hey Nature! just wanted to add my 0.02, ok theres a difference between rooting, and a difference between flashing recoveries,kernels,roms,and what have you.
ill give a brief explanation in the differences. The Colors of the titles indicate how safe/dangerous it is to modify one of these things and wether it will void your warranty, Green=Wont void your warranty, and easily reversible. Orange=Void Warranty, Reversible, But starting to get Dangerous, Red=Definitely VVoids Warranty, and if screwed up, could ruin/brick your devvice Definitely Voids Warranty, and if screwed up, could ruin/brick your devvice
Rooting: When you are rooting your device, you are basically forcing your stock version of android to allow you (the user) root access, therefore allowing you to bypass/allow signature verification for apps, now this could be anything from homebrew apps that you are making yourself...to the naughty pirated apps, and i dont encourage the latter. By giving yourself root access to your phone, your allowing the next to happen:
Flashing a Custom Recovery: Ok ill explain this as simple as i can...Mostly all if not ALL android phones have a stock recovery, this is a safeguard in case some kind of software fault happened in the phone(stock software fault or what have you). Flashing a custom recovery would be your next step after Rooting a device (IF) you want to go further than apps, meaning Kernels, Roms etc. Now the reason you must Root your device in order to install a custom recovery, is because like explained above signature verification....Now this is when you begin to tread in warranty territory, once flashing a custom recovery...your warranty has become VOID, however what the custom recovery allows you to do is a multitude of things, but the most major is Flashing .ZIP files, which most roms are in the form of, now not only Roms are in ZIP files, so are kernels,mods,baseband firmwares, etc, with that being said, different phones/devices use different methods of flashing roms, lets say for example you somehow screwed something up on a samsung really bad, and it wont boot, however, you can still get into download mode...then you're safe, because samsung uses Odin to flash the entire phone back to stock meaning Recovery/aBoot/Data/System and bring you right back, but if you hard brick it, theres only 3 ways out from that...and they all suck....number one, is call me and send it to me to Jtag it for you ..but it takes long and its not that cheap, #2, Desolder the chip (whichever it is on the device that has caused the problem) and replace it...and thats not an easy task at all, ive done it once to an S3 successfully, after that i never wanted to do it again, and this was back when they were really expensive, and lastly....#3.....and this one is the worse....go buy a new one SO BE CAREFUL!
ROMS: So now that we have a custom recovery, a rom is basically a heavily modified version of Android! and let me tell ya, i love them...i love so many of them, there are sooo many different things that you can do with roms, but the most desired from what ive gathered, is so people can remove the bloatware that comes with their phone when they buy it from the carrier/manufacturer. Thats not all tho, there is way too much to get into, but some roms allow you to Overclock your phones CPU/GPU, and change the Behaviors of the phones hardware, and the major component in roms that allows that is the Kernel.
Kernel: Now dont totally quote me here, im still learning kernels, but a kernel is basically the binary software in the phone, almost like a bios that when modified from stock, changes the behavior of the MOST of the hardware, not all. Now i could be wrong and anyone please feel free to correct me, now i do want to give you a shot of my own advice here...if you dont know what you are doing, kernels are dangerous to a noobie..before i started messing with roms and kernels, i tried to get the best understanding i could, and ill be honest with you, i blew up a couple S3's doing so. but im still learning. so if you're unweary or still not educated enough in the hobby to get too it, please read more up on it, because as none of these guys here that are devs nor people like myself that are trying to help intend to destroy your device on you, so please be careful for your own device's safety, and to save yourself money and a broken heart.
Knox: Ok now correct me if im wrong here, because im still learning as this is new to me, i only saw it on the MJA bootloader on the S4 on Jellybean from Sprint when they first OTA'd it, but knox looks to be Samsungs pathetic try of not lettings us Access the devices binary software, like an encryption, or to only let us access and modify certain things, also samsung has added a flash counter, which will tell them how many times you have flashed a new rom, however there are ways around these things, google and the search bar are you best friends to start, and we can help too.
I Hope this helped and shed some light on some information, and please if anyone has anything to add or to correct me if im wrong anywhere please do so ^_^
P.S. To be totally honest, theres always a way to restore your device and even get the flash counter back to 0 again and put everything back to normal, if an experienced tech looks at it and puts it in download mode unless all is restored, hell be able to see everything, but honestly, if you pay off the phone, you havve nothing to worry about, but then again, i dont care much for warranties, so it all depends on how savvy with fixing problems when they go wrong, but if you ever need i can help you, im pretty experienced when it comes to everything but developing atm, i was a microelectronics major in college, so my expertise is mainly in hardware i.e. if you hard/soft brick the devvice i can usually get it out of that.
please excuse my typing, i type extremely fast, and i have a mechanical keyboard and i think some lettings are startings to give way such as the V key.
---------- Post added at 01:45 AM ---------- Previous post was at 01:29 AM ----------
Oh and please i Highly suggest using Philz Touch!
Code:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltetmo
Thats for the HLTETMO version, which is our versions in this forum, all credit to phil ofcourse, it is basically CWM, but so much more user friendly and advanced with much more options, there are two files there, you obviously want the latest version, and there are two ways to do it, if you download the tar.md5 you must use Odin, and put your phone in download/odin mode, very easily done (turn it off unplug usb and press Home+Vol Dwn+Pwr) then once the screen pops up press Vol Up and then plug the USB in, and follow the instructions of w/e tutorial you are ready, but be very careful in odin mode, if you disturb the phone while its flashing you will most likely brick it, and the .zip is considering you already have a custom recovery and you can just flash it through there.
Click to expand...
Click to collapse
Ty for the explanation. Unfortunately, that is if you took the time to write that or just copied, I knew most if not all of the risks. As I said earlier I've been rooting since gingerbread.
However, it's quite informative and anybody else who is new to rooting shall find it helpful.
Kernels are more or less a bios, if you will. But they are specific to builds. You can't use aosp on tw and vice versa. There are other key features but I can't remember off the top of my head. Basically no kernel =/= no phone or no features such as camera.
You're right about the s4, but if I'm not mistaken it was believed to be an eFuse, as was for the note 3 too. Although other members have said they got it back reset, 0x0, and sim unlocks intact to fix other issues like broken gps. Therefore it is believed to be software at a signature level.
And I'll look into philz, loved it on the s3. If you ever have q's about root feel free to pm me
Sent from my SM-N900T using XDA Premium 4 mobile app
Towle said:
He's not wrong. There are a couple different methods of rooting that don't require a custom recovery, therefore don't trip Knox.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Wow... must have read that post wrong. Been working way too much. Sorry about that but looks like we have some great info added here.
Naturesretard said:
Ty for the explanation. Unfortunately, that is if you took the time to write that or just copied, I knew most if not all of the risks. As I said earlier I've been rooting since gingerbread.
However, it's quite informative and anybody else who is new to rooting shall find it helpful.
Kernels are more or less a bios, if you will. But they are specific to builds. You can't use aosp on tw and vice versa. There are other key features but I can't remember off the top of my head. Basically no kernel =/= no phone or no features such as camera.
You're right about the s4, but if I'm not mistaken it was believed to be an eFuse, as was for the note 3 too. Although other members have said they got it back reset, 0x0, and sim unlocks intact to fix other issues like broken gps. Therefore it is believed to be software at a signature level.
And I'll look into philz, loved it on the s3. If you ever have q's about root feel free to pm me
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ahh nate, i misunderstood, i thought you were new to rooting but just knew some of the basics, but were unclear of some others, but yeh, i typed that all up, no copy and paste here otherwise i would've credited the Author ^_^ but i hope it was Helpful, im sure its plastered and posted evverywhere around here, but maybe ill make a Write up somewhere to clarify things, because when i was learning, everything was scattered and i had to collect all the information.
MasterSe7en said:
ahh nate, i misunderstood, i thought you were new to rooting but just knew some of the basics, but were unclear of some others, but yeh, i typed that all up, no copy and paste here otherwise i would've credited the Author ^_^ but i hope it was Helpful, im sure its plastered and posted evverywhere around here, but maybe ill make a Write up somewhere to clarify things, because when i was learning, everything was scattered and i had to collect all the information.
Click to expand...
Click to collapse
You Be Surprised How Often that happens. I'd sticky if I could
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
You Be Surprised How Often that happens. I'd sticky if I could
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey Nate! **WAVE**
lol well i posted a new thread on it, so i hope it helps the newer guys and it'd be nice if it was stickied, like i said tho, its plastered everywhere around here and on google even, but its nice to try to help my Fellow note 3'ers
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?
I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
notedroidbrokedroid said:
I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
Click to expand...
Click to collapse
The processes were easy enough...and some like me had temp root on first or second try. If you've spent weeks and weeks trying to figure this all out, I'm not sure anyone can help you. There are people in these threads that have answered every question you've brought up, and helped people get through. I know you must be some kind of troll with your "one post" and claiming you've been rooting blah blah blah....engineer...blah blah blah, you should be embarrassed by your lack of understanding and ability to root and unlock. Go read some of the dopey posts by people who can't follow instructions or put a sentence together, yet were successful! I guess what I'm saying is stfu and go away.
Sent from my SM-N910V using XDA-Developers mobile app
gcounts said:
The processes were easy enough...and some like me had temp root on first or second try.
Click to expand...
Click to collapse
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
gcounts said:
you should be embarrassed by your lack of understanding and ability to root and unlock.
Click to expand...
Click to collapse
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
notedroidbrokedroid said:
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
Click to expand...
Click to collapse
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
douger1957 said:
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
Click to expand...
Click to collapse
- Has anybody bothered to state that 40% of the battery charge disappears every time you run Kingoroot? Nope. Nowhere in the guides.
- Has anybody mentioned that the CPD1 VZW bootloader firmware is also locked and will not boot a ROM flagged as custom? Nope! Nowhere. You heard it here first!
- Has anyone examined the content of the BPA1-CPD1 hybrid 5.1.1 ROM to determine whether it contains OEM VZW firmware or a custom firmware revision developed by someone on this forum? No. Nobody has done that.
You don't have to "write full-time" to have good written communication skills. I could write a very respectable COMPREHENSIVE guide on the process involved, but do you know what would happen to it? The admins would never sticky it and it would get buried under a thousand other threads. Somebody decided that there can be ONLY ONE ["Official"] guide, even though the current one is a stupid, incoherent mess that's maintained by an OP who refuses to amend or add anything to it.
And lazy? At least I perused the source code before I blindly copied a script claiming to unlock my bootloader. I doubt you have the slightest clue on either how to look at it or what malicious code looks like.
Lastly and most importantly, you're a fool for being content with giving your money to a phone manufacturer that rails you in the ass for wanting more control over it. After I brought my Note 4 back from the grave, I bought a Nexus. You think donating your change to the Devs is going to fix this problem long-term when you give Samsung $800 to continue doing this to you? I don't have enough crayons to further explain to you what an idiot you are.
Ok as this really is nothing more then a rant I will close this up with a few passing thoughts.
Things like this are not meant to be done by the average guy. This is a developers site. So yes you are expected to do lots of research before you do anything.
Next. No one in their right mind uses that root process. The battery drain is it connecting to the internet and downloading what ever it is they use to root the device after then get your imei and store it.
Also lets leave the name calling for the playground or the next name that will be called is banned.
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
Hey guys i preordered my s9 and was super excited because my s8 was not able to be rooted due to knox and so was looking forward to trying out some xposed mods and roms..unfortunately ive yet to see anything on how to root the sm-G960U1 variant? Seems odd because its the u.s unlocked which i thought would be more common than carrier locked ones in xda community
The odds are nearly zero. Unless there's an engineering firmware that leaks out. The Snapdragon is locked up tight.
waylo said:
The odds are nearly zero. Unless there's an engineering firmware that leaks out. The Snapdragon is locked up tight.
Click to expand...
Click to collapse
True
The engineering firmware for sm-g960u has been leaked... should work on ur or be easy to tweak...
jflow36 said:
The engineering firmware for sm-g960u has been leaked... should work on ur or be easy to tweak...
Click to expand...
Click to collapse
I know this is old, but I've been trying today to get root on a new sm-g960u1, with no luck at all.
I couldn't even get twrp installed... Would you be able to help me or point me in the right direction?
[
I couldn't even get twrp installed... Would you be able to help me or point me in the right direction?[/QUOTE]
PrashannaGP said:
There is no twrp your bootloader is locked. And cannot be unlocked. If you look in the snap dragon dev section you can obtain a system mode root only.
No custom ROMs.
And what is your problem??
I just helped him to install TWRP in custom rom. He was saying that he counldn't install TWRP in his rom.
Don't disturb me without reading the whole problem.
Click to expand...
Click to collapse
Well the thread clearly states for g960u1 which is the US model so and your answering with twrp and custom ROMs so if this thread is for g960u1 I'd like to know how you helped him install twrp and or custom rom.
Read the whole problem
I couldn't even get twrp installed... Would you be able to help me or point me in the right direction?
Pretty self explanatory. Unless he thread jacked and has another model
So your telling em your flashing twrp on g960u1 models? That are locked bootloader. No oem unlock. And must only boot signed imgs. Ok I want proof
If this is the case your rich mate.
Ok so I can flash twrp but the device still only boots signed images. WTH. What device are you doing this to
---------- Post added at 08:36 AM ---------- Previous post was at 08:34 AM ----------
Again we need pics of this it didn't happen. After the community reads your posts on claims of twrp on g960u1 their gonna be all over you
What model do you have
---------- Post added at 08:50 AM ---------- Previous post was at 08:46 AM ----------
You use sp flash tool mate? I thought sp flash tool was for media tek. Lol. Some one got a knock off s9 off wish
You must be stuck in 2012. It's not so simple anymore. Bootloader lock means it's locked regardless of twrp or SuperSU.
Did you truthfully use this method to flash my twrp to your locked bootloader device that is an s9 or s9+?
I'm gonna need some real proof before I believe that from a guy that just created his account 2 days ago and calls himself an Android app developer without a link to his github or gitlab.
I have very serious doubts about your so called method. If it really works as you claim them proof shouldn't be an issue at all to present to everyone.
Sent from my Pixel 2 XL using Tapatalk
Again sp flash tool is for mediatek devices samsung does not have media tek but the crappy clones or knockoffs do. So again where's the proof mate. So your saying you've managed to do what every developer has been trying to do since the s6 maybe further. The u u1 and w devices are fully bootloader locked. There is no flashing twrp. No safe strap you are completely full of crap and Im sure I can speak for many people on xda not wanting your mis information thrown about. You would be a millionaire if you did what you claim as in bypassing a 256 bit encryption signed device.
You need to just quit before some one without knowledge attempts what you claim and bricks their device. It isn't fair to the community that you don't know what your doing making false claims on obviously a device you most definitely do not own. I have all my devices listed in my profile. Why don't you?
You know 45% of android lol.
Just a couple days ago your asking if you can extract a file with 7zip and how many files where in it. Now your a bootloader unlock expert . My hat is off to you good sir
TheMadScientist said:
Again sp flash tool is for mediatek devices samsung does not have media tek but the crappy clones or knockoffs do. So again where's the proof mate. So your saying you've managed to do what every developer has been trying to do since the s6 maybe further. The u u1 and w devices are fully bootloader locked. There is no flashing twrp. No safe strap you are completely full of crap and Im sure I can speak for many people on xda not wanting your mis information thrown about. You would be a millionaire if you did what you claim as in bypassing a 256 bit encryption signed device.
You need to just quit before some one without knowledge attempts what you claim and bricks their device. It isn't fair to the community that you don't know what your doing making false claims on obviously a device you most definitely do not own. I have all my devices listed in my profile. Why don't you?
You know 45% of android lol.
Just a couple days ago your asking if you can extract a file with 7zip and how many files where in it. Now your a bootloader unlock expert . My hat is off to you good sir
Click to expand...
Click to collapse
He's just a quick study and hasn't updated his profile to knowing 100% of Android yet.
Sent from my Pixel 2 XL using Tapatalk
Thread Cleaned
Hey folks, Just wanted to remind everyone that always ensure you do your research for what you choose to do to your device and also make sure as best you can that whatever modifications you attempt to make are backed up by evidence of success or proof of concept and there is some type of documentation. The last thing we want to see is a new help thread because someone flashed something and damaged their device. Always do your homework and always check for credibility too of said files and members.
If you see anything that looks off, please report it and avoid any conflict or confrontations out here. Good job folks and stay safe and stay home if you can!
-Negan