Related
This thread was previous titled "How To Brick Your Phone" but because of confusion over the intent of the thread I decided to change the title.
I'm not sure if this would be helpful for everyone but I know some would benefit from knowing how one can brick their phone*. It may help early explorers to know what areas of their phone are for more seasoned SU's and what areas they can explore safely. So, if you know of a way to brick your device, please list it and give some detail leading up to the point of bricking**.
And if you have bricked your phone, please share your experience so that others do not follow in your steps.
* Please list ways to brick your phone other than using physical materials and not ways that are malicious in nature.
** Keep in mind, this thread is not intended for anyone to use as a way to defraud your carrier. The methods outlined are to serve as a warning on certain parts of the device to steer clear from (as a young learner) and to help people feel more comfortable exploring their phone's SU side.
-------------------------------------
Sent via the XDA Tapatalk App
Most commonly talked about way; flash a GSM radio to the CDMA Hero.
Austin3600 said:
Most commonly talked about way; flash a GSM radio to the CDMA Hero.
Click to expand...
Click to collapse
+1 for this. It's the only way I've ever heard of someone truly "bricking" their phone.
Re: How to brick your phone.
This is the most common way I've heard of as well. Can a radio baseband be included in a custom ROM or is this something that has to always be flashed OVER a ROM?
The xda-wiki has a great section listing various radios that are for CDMA Heros. Anyone have the link? I'm on my phone at the moment.
-------------------------------------
Sent via the XDA Tapatalk App
run over it with a truck then pay the 100 bucks to get a new one.
gunnyman said:
run over it with a truck then pay the 100 bucks to get a new one.
Click to expand...
Click to collapse
Indeed. I would say even a medium-size car could do the trick. Unless you have Ghost Armor.
This thread is offensive
There are plenty of ways to render your phone useless, but why?
Unless you're trying to defraud Asurion into getting a new device...
ridiculous
nebenezer said:
This thread is offensive
There are plenty of ways to render your phone useless, but why?
Unless you're trying to defraud Asurion into getting a new device...
ridiculous
Click to expand...
Click to collapse
I believe the intention was to make a list of things to avoid, rather than a list of things to try.
ethereal45 said:
I believe the intention was to make a list of things to avoid, rather than a list of things to try.
Click to expand...
Click to collapse
Ahhh, that makes sense.
In that case I would suggest the OP change the thread title to "How to NOT brick your phone"
A list of things to avoid is simply another way of saying "a list of things to do."
The right information in the wrong persons hands.
nebenezer said:
Ahhh, that makes sense.
In that case I would suggest the OP change the thread title to "How to NOT brick your phone"
Click to expand...
Click to collapse
I'm not going to change the thread title. The intention was to pose the question so people could STAY AWAY from those areas (ethereal45 hit the nail on the head). I'm not sure if there is anyone out there sincerely looking to brick their device. This idea is a bit ridiculous and if you're reading that into this thread you're clearly not seeing the ironic nature of the title Gunnyman's comment was completely sarcastic and funny (at least that's the way I took it in my reply...we're not trying to defraud anyone). But in all reality, no one is going to intentionally brick their phone. If they do, they've got issues larger than this forum can fix.
The intention is the opposite of what you're thinking. Just wanting to know what roads to avoid so that we don't brick our devices. I'm very fresh to this world and it can seem intimidating, so I thought this thread could help ease some of that anxiety.
joshuaharp said:
I'm not going to change the thread title. The intention was to pose the question so people could STAY AWAY from those areas (ethereal45 hit the nail on the head). I'm not sure if there is anyone out there sincerely looking to brick their device. This idea is a bit ridiculous and if you're reading that into this thread you're clearly not seeing the ironic nature of the title Gunnyman's comment was completely sarcastic and funny (at least that's the way I took it in my reply...we're not trying to defraud anyone). But in all reality, no one is going to intentionally brick their phone. If they do, they've got issues larger than this forum can fix.
The intention is the opposite of what you're thinking. Just wanting to know what roads to avoid so that we don't brick our devices. I'm very fresh to this world and it can seem intimidating, so I thought this thread could help ease some of that anxiety.
Click to expand...
Click to collapse
This is like posting a very detailed guide on how to break into a computer, and then saying it's so people can prevent.
Sure, some people will use it for what it's intended, but there are people who will misuse it because there's something they don't like about their Hero, and want to get a refurb or new phone or something.
abcdfv said:
This is like posting a very detailed guide on how to break into a computer, and then saying it's so people can prevent.
Sure, some people will use it for what it's intended, but there are people who will misuse it because there's something they don't like about their Hero, and want to get a refurb or new phone or something.
Click to expand...
Click to collapse
I find this VERY hard to believe. If someone is wanting to defraud their carrier and get a refurbished phone, do you think they will look online for how to 'brick' their root device? I doubt it. Why not just throw it in a pool or run over it with their car?
It's more like a help to not overheat your car. What are ways that you can overheat your car. No radiator fluid, running A/C through the mountains, etc. This is to give people a help on things to avoid. Sure, if someone has a desperate desire to overheat their car, they can follow the instructions and overheat it. But that's up to them.
I find that as I'm exploring the deeper side of my device, I'm constantly thinking thoughts like "wonder if doing this will brick my phone" and so I don't usually explore very far, because of this fear (and my wife and my conscience won't allow me to defraud Sprint, run over my phone and get a replacement). I'm just trying to be cautious that's all and wondering if there are any other ways (non-physical and non-malicious) to brick your device other than flashing a GSM Radio on a CDMA phone.
joshuaharp said:
I'm not sure if there is anyone out there sincerely looking to brick their device. This idea is a bit ridiculous and if you're reading that into this thread you're clearly not seeing the ironic nature of the title Gunnyman's comment was completely sarcastic and funny (at least that's the way I took it in my reply...we're not trying to defraud anyone). But in all reality, no one is going to intentionally brick their phone. If they do, they've got issues larger than this forum can fix.
Click to expand...
Click to collapse
If thats's how I read it? That's what you said... "How to brick your phone".
You might be surprised how many people do intentionally brick their phones. You might also be surprised (if you did just a LITTLE bit of searching) how many threads have been closed because people are openly trying to find out how to brick their phones with the intention of avoiding the $100 replacement charge.
joshuaharp said:
The intention is the opposite of what you're thinking. Just wanting to know what roads to avoid so that we don't brick our devices. I'm very fresh to this world and it can seem intimidating, so I thought this thread could help ease some of that anxiety.
Click to expand...
Click to collapse
If that's the intention then I don't understand why you mislabeled the thread.
There are only 2 ways I know of to brick a CDMA Hero. They are very, very easily avoidable. You almost have to go out of your way to brick a CDMA Hero and if you READ about what you are doing to your phone before you do it you will easily avoid it. And for that matter, as long as you make nandroid backups, forget bricking, it's hard even just to lose whatever info might be important to you.
That's fine though, whatever floats yer boat. I am well aware of how to AVOID bricking my phone so I'll leave your thread alone now.
http://forum.xda-developers.com/showthread.php?t=672131&highlight=brick
http://forum.xda-developers.com/showthread.php?t=663949&highlight=brick
Just to list two.
nebenezer said:
If thats's how I read it? That's what you said... "How to brick your phone".
You might be surprised how many people do intentionally brick their phones. You might also be surprised (if you did just a LITTLE bit of searching) how many threads have been closed because people are openly trying to find out how to brick their phones with the intention of avoiding the $100 replacement charge.
Click to expand...
Click to collapse
First of all, how am I going to find closed threads? Don't they remove them? I really didn't know people search on how to brick their phones with this intention. It seems asinine to me. I hope the mods don't think that's my intention, because I've described it pretty clearly and have even updated the description to be extra clear.
If that's the intention then I don't understand why you mislabeled the thread.
Click to expand...
Click to collapse
Because a thread that says "How to not brick your phone" is a complete waste of time (which this thread is quickly becoming). There are way more ways to NOT brick your phone than to brick it.
There are only 2 ways I know of to brick a CDMA Hero. They are very, very easily avoidable. You almost have to go out of your way to brick a CDMA Hero and if you READ about what you are doing to your phone before you do it you will easily avoid it. And for that matter, as long as you make nandroid backups, forget bricking, it's hard even just to lose whatever info might be important to you.
Click to expand...
Click to collapse
What are the two ways?! I only know of one for the CDMA Hero (GSM Radio flashing to CDMA phone). This is what I'm talking about. You have information that I've been unable to find. Please share.
When you're learning about rooting your device and someone says "this procedure may brick your phone" your mind wonders, what is it about this procedure that may cause my phone to become an invaluable paperweight? That's what I'm after. From a previous forum, I learned that radios are something to be extra careful with. So, that got my mind wondering, what other areas should I be looking out for.
While I agree with the purpose of this thread, the title is a little confusing.
However, On a different phone (HTC Kaiser) there was an android port that I was interested in. I managed to brick that phone by running the sudo rm code in Terminal Emulator. While I don't know if it will brick a Hero it did brick the poor Kaiser. As it was an AT&T phone I had no use for it anymore and thought I'd give the command a try just to see the consequences.
mbobino said:
While I agree with the purpose of this thread, the title is a little confusing.
However, On a different phone (HTC Kaiser) there was an android port that I was interested in. I managed to brick that phone by running the sudo rm code in Terminal Emulator. While I don't know if it will brick a Hero it did brick the poor Kaiser. As it was an AT&T phone I had no use for it anymore and thought I'd give the command a try just to see the consequences.
Click to expand...
Click to collapse
I don't think that would brick it, as we could still access the recovery partition to nandroid back.
Re: How to brick your phone.
While I agree with the purpose of this thread, the title is a little confusing.
However, On a different phone (HTC Kaiser) there was an android port that I was interested in. I managed to brick that phone by running the sudo rm code in Terminal Emulator. While I don't know if it will brick a Hero it did brick the poor Kaiser. As it was an AT&T phone I had no use for it anymore and thought I'd give the command a try just to see the consequences.
Click to expand...
Click to collapse
This is good to know. What would I be doing to have to use this command?
Thread name: Will probably change when I have computer access. I honestly didn't realize people search forums to intentionally brick their devices. I've been proven wrong on that one
-------------------------------------
Sent via the XDA Tapatalk App
mbobino said:
while i agree with the purpose of this thread, the title is a little confusing.
However, on a different phone (htc kaiser) there was an android port that i was interested in. I managed to brick that phone by running the sudo rm code in terminal emulator. While i don't know if it will brick a hero it did brick the poor kaiser. As it was an at&t phone i had no use for it anymore and thought i'd give the command a try just to see the consequences.
Click to expand...
Click to collapse
Code:
sudo rm ~/
lol
Just so everyone is aware, the kernel and the recovery partition signatures are checked on each boot, changing those will leave you with a brick, until we have proper firmware to recovery with.
I found out the hard way.
On my second Atrix now.
Casualty of war
Taking one for the team
Well that sucks..
any free partitions that we can "steal"? and basically pull a haret where it loads partially from legit bootloader and kernel, then shuffles off to a different partition we CAN write for the real kernel, unloads all that other stuff and then launches the new kernel partiion we've modified?
designgears said:
Just so everyone is aware, the kernel and the recovery partition signatures are checked on each boot, changing those will leave you with a brick, until we have proper firmware to recovery with.
I found out the hard way.
On my second Atrix now.
Click to expand...
Click to collapse
I guess that when we told you this, you just had to find out for yourself. The recovery should only be checked when you attempt to access it, but the kernel is checked on every boot. I hope you did not return to store as defective.
DG, thank you for putting yourself out there, and putting together roms along with the dev work.
Its nice to see some progress being done along side all the people on here saying what we shouldnt be doing/trying with our phones.
Athailias said:
DG, thank you for putting yourself out there, and putting together roms along with the dev work.
Its nice to see some progress being done along side all the people on here saying what we shouldnt be doing/trying with our phones.
Click to expand...
Click to collapse
Don't thank him for repeating something which had been confirmed.
jimmydafish said:
I guess that when we told you this, you just had to find out for yourself. The recovery should only be checked when you attempt to access it, but the kernel is checked on every boot. I hope you did not return to store as defective.
Click to expand...
Click to collapse
So you told me it was checked every boot (first bold), but it should only be checked when you access it (second bold)? Confused, on drugs or what?
I just found out the hard way for you, it's checked every boot accessed or not.
If you want to be elitist and not post up a FAQ about what you know (do you even have an atrix), please stop posting in here, you've done nothing but spout off what you know about other moto devices, it is clear they tightened things down a bit more.
jimmypopulous said:
Don't thank him for repeating something which had been confirmed.
Click to expand...
Click to collapse
everything you guys say, along with others says it SHOULD be checked when accessed, which means I should have been able to boot normally and fail when I boot recovery.
You guys keep saying its CONFIRMED, where is it documented for the atrix. Tests performed with document results as proof.
designgears said:
So you told me it was checked every boot (first bold), but it should only be checked when you access it (second bold)? Confused, on drugs or what?
I just found out the hard way for you, it's checked every boot accessed or not.
If you want to be elitist and not post up a FAQ about what you know (do you even have an atrix), please stop posting in here, you've done nothing but spout off what you know about other moto devices, it is clear they tightened things down a bit more.
everything you guys say, along with others says it SHOULD be checked when accessed, which means I should have been able to boot normally and fail when I boot recovery.
You guys keep saying its CONFIRMED, where is it documented for the atrix. Tests performed with document results as proof.
Click to expand...
Click to collapse
What is being elitist by my statement? That before you started playing with your shiny new toy, we advised that doing certain things with your phone without proper firmware to restore your phone, WOULD result in a "soft brick".
I do not have a motorola ATRIX, never said I did, but I can read the firmware pretty well. If your offended by my post I assume it is because offered up my standard line of "hope you did not return it as defective", because nothing else in that statement should lead you behave like a child.
Here how about this for a Facts, my rom was the first to safely remove Blur from the Droid series of phones safely, after reading the firmware from your phone, and your deodexed version of the firmware there are many portions you could remove safely.
If you have questions you could ask and get the answers, but as it stands right now, we are just trying to help you save yourselves. Many people will enter these forums, and while each person is responsible for their own device, they will try to follow what you have done and they too will soft brick their phone. I'm not sure of your ethical and moral makeup but too many people return their manipulated device to the provider as defective causing every to pay for their mistake.
I just hope you bought another Atrix outright and did not scam ATT/Motorola.
designgears said:
So you told me it was checked every boot (first bold), but it should only be checked when you access it (second bold)? Confused, on drugs or what?
I just found out the hard way for you, it's checked every boot accessed or not.
If you want to be elitist and not post up a FAQ about what you know (do you even have an atrix), please stop posting in here, you've done nothing but spout off what you know about other moto devices, it is clear they tightened things down a bit more.
everything you guys say, along with others says it SHOULD be checked when accessed, which means I should have been able to boot normally and fail when I boot recovery.
Click to expand...
Click to collapse
DesignGears,
Please don't let a claim-to-know-it-all self-righteous Prick like jimmydafish discourage your efforts.
As far as I'm concerned (and probably the majority of people who mash the refresh button on this subforum multiple times a day would agree) it's people like you (people who have actively contributed to the users here at XDA in the past (all your captivate work)), that make me feel lucky to own the same type of device that you and other dedicated devs like yourself own.
Its hard to imagine how someone who probably played a very small part on a team -- a team that, as far as I can tell, has never managed to actually produce any real results on the DX -- can know so much about a device he doesn't even own.
And if reading this post encourages members of any such team to get their panties in a wad and start talking about how they are not going to contribute here now, well then to that I say: good riddance. For every one small tip you may provide it seams like you offer two holier-than-thou-doughe-bag-comments that frankly this section of this forum could do without.
But again, thank you DesginGears and Devs like you
mburris said:
DesignGears,
Please don't let a claim-to-know-it-all self-righteous Prick like jimmydafish discourage your efforts.
As far as I'm concerned (and probably the majority of people who mash the refresh button on this subforum multiple times a day would agree) it's people like you (people who have actively contributed to the users here at XDA in the past (all your captivate work)), that make me feel lucky to own the same type of device that you and other dedicated devs like yourself own.
Its hard to imagine how someone who probably played a very small part on a team -- a team that, as far as I can tell, has never managed to actually produce any real results on the DX -- can know so much about a device he doesn't even own.
And if reading this post encourages members of any such team to get their panties in a wad and start talking about how they are not going to contribute here now, well then to that I say: good riddance. For every one small tip you may provide it seams like you offer two holier-than-thou-doughe-bag-comments that frankly this section of this forum could do without.
But again, thank you DesginGears and Devs like you
Click to expand...
Click to collapse
I can assure you I am not, glad to have support.
--
Jimmy, no hard feelins, sorry I wanted try something and learn from it, sorry you told me two opposing things in the same post(this is what I am *****ing about if you would read you would know that), sorry I act like a child, I guess calling it how I see it is childish. From all the PM's about you I just got and mburris reply, you have made my block list, have fun in there with rafy.
jimmydafish said:
I just hope you bought another Atrix outright and did not scam ATT/Motorola.
Click to expand...
Click to collapse
Maybe if more people softbricked and returned phones that have locked down bootloaders, oems and carriers might finally realize that when someone buys a piece of technology, they own it, and would like to use it as such.
That includes:
1. Not having some POS skin on top of stock android (Blur)
2. Not being locked into paying twice for the data we already pay for (tethering)
3. Not being allowed to easily install non-market apps that we develop without jumping through hoops (slide loading)
4. Not having to wait for the carrier or oem mfg to release an update before we can have a current version of Android.
Call it a Brick-n-Return Protest
mburris said:
Maybe if more people softbricked and returned phones that have locked down bootloaders, oems and carriers might finally realize that when someone buys a piece of technology, they own it, and would like to use it as such.
That includes:
1. Not having some POS skin on top of stock android (Blur)
2. Not being locked into paying twice for the data we already pay for (tethering)
3. Not being allowed to easily install non-market apps that we develop without jumping through hoops (slide loading)
4. Not having to wait for the carrier or oem mfg to release an update before we can have a current version of Android.
Call it a Brick-n-Return Protest
Click to expand...
Click to collapse
LOL, that would surely cause some grief over at at&t, and a good laugh.
They would probably start leasing the phones so you can't say you own them.
Closed by OP request as this is an informational thread stating results of testing.
Does it have, got my Note 8 a week ago but just wondering has I have not seen anykind of movement for the US variant.
all sorts of threads and posts answer your questions..
Just search, do not be lazy
Oh wow, thanks before posting I searched and found nothing only for older versions using SamFail. Thanks anyways loooool glad to see a gooood comunity
PLUS I said that I didn't saw any kind of movement
@atrix_noob What firmware are you running ?
Alek7 said:
@atrix_noob What firmware are you running ?
Click to expand...
Click to collapse
It's on 8.0 May 1 security patch.
atrix_noob said:
It's on 8.0 May 1 security patch.
Click to expand...
Click to collapse
For the US 950U and 950U1 snapdragon there is no root for the May update. That is bootloader revision 4 and has no root at this time. Your best bet is to keep a eye on the samfail thread for updates.
If your past U3 were sol for now. I think theres only one guy working on a possible partial root. There are lots of apps for theming. Substranium and Good lock are great.
atrix_noob said:
Oh wow, thanks before posting I searched and found nothing only for older versions using SamFail. Thanks anyways loooool glad to see a gooood comunity
Click to expand...
Click to collapse
Dude.
Just search around.
Don't give us the 'lmao such a good community, how about you go and suck it because I don't want to research' attitude.
It's not our fault you couldn't be bothered to check for any activity and read around.
Plus people are tired of having others ask the same question hundreds of others have asked related to root, it's all about searching or reading.
Don't you think if someone found a way to root the newest firmware there would be a lot more sites talking about it?
Sarcasm aside, no, there is no root for Oreo Bootloaders (U4). Only Nougat with U3 or below.
luisramon17 said:
Dude.
Just search around.
Don't give us the 'lmao such a good community, how about you go and suck it because I don't want to research' attitude.
It's not our fault you couldn't be bothered to check for any activity and read around.
Plus people are tired of having others ask the same question hundreds of others have asked related to root, it's all about searching or reading.
Don't you think if someone found a way to root the newest firmware there would be a lot more sites talking about it?
Sarcasm aside, no, there is no root for Oreo Bootloaders (U4). Only Nougat with U3 or below.
Click to expand...
Click to collapse
Before posting I always use the search feature cause it's very usefull. Has you know there are multiple threads and forums and specifically a T-Mobile Model one and its pretty much dead. If YOU read above I said that I didn't see any kind of activity. Another one is that if you read more down below, I stated that all I could find is a SamFail one but it's pretty outdated. So I came here to the Questions & Answers area and posted this thread here to see if anyone had an idea of whats happening with the US models
I don't need for someone to come here and tell me
"Oh don't be lazy and use the search funtion"
Already stated on the first post. Sheesh
And yeah, thanks for the bootloader part.
atrix_noob said:
Before posting I always use the search feature cause it's very usefull. Has you know there are multiple threads and forums and specifically a T-Mobile Model one. If YOU read above I said that I didn't see any kind of activity. Another one is that if you read more down below, I stated that all I could find is a SamFail one but it's pretty outdated. So I came here to the Questions & Answers area and posted this thread here to see if anyone had an idea of whats happenind with the US models
I don't need for someone to come here and tell me " Oh don't be lazy and use the search funtion"
Alrready stated on the first post. Sheesh
And yeah, thanks for the bootloader part.
Click to expand...
Click to collapse
The thing is theres not much firmware differences between models. They might have slight baseband changes but they're all based on the same thing. So root that would work on a Verizon Note8 would work on a T-Mobile Note8.
And yes, the only one we have is sadly the V3 for those unlucky to update.
And I imagine people would check the last section of the thread to be on standby since apparently theres a new exploit that might (or might not) help.
This is why I assumed you didn't check first, but since you did (I didn't see that part), I apologize.
Amos420en said:
If your past U3 were sol for now. I think theres only one guy working on a possible partial root. There are lots of apps for theming. Substranium and Good lock are great.
Click to expand...
Click to collapse
Thanks for the heads up, I really like the root and all that stuff. Especially for getting rid of all T-Mobile crap on the phone. I'm a person that chages phone alot but I think I'll be giving this guy an exchange for another phone lol. I literally don't last a month with a phone has I like to test other brands and models
luisramon17 said:
The thing is theres not much firmware differences between models. They might have slight baseband changes but they're all based on the same thing. So root that would work on a Verizon Note8 would work on a T-Mobile Note8.
And yes, the only one we have is sadly the V3 for those unlucky to update.
And I imagine people would check the last section of the thread to be on standby since apparently theres a new exploit that might (or might not) help.
This is why I assumed you didn't check first, but since you did (I didn't see that part), I apologize.
Click to expand...
Click to collapse
Don't worry, I searched everywhere but nothing found. Sometimes you know, people spread rumors or someone may know of something that's been on progress but it doesn't come up on public threads.
I been rooting my phones literally ever since I had an Android phone and always do my reaserch before posting on forums, cause you know there's always the people that come and say "Use the search feature" and always try to avoid that.
And yeah, all I read about was on Nougat. So I'll just asume it's dead.
atrix_noob said:
Don't worry, I searched everywhere but nothing found. Sometimes you know, people spread rumors or someone may know of something that's been on progress but it doesn't come up on public threads.
I been rooting my phones literally ever since I had an Android phone and always do my reaserch before posting on forums, cause you know there's always the people that come and say "Use the search feature" and always try to avoid that.
And yeah, all I read about was on Nougat. So I'll just asume it's dead.
Click to expand...
Click to collapse
You switch phones a lot too? Same, heh. Went from having a Note 4 to iPhone 8 Plus, then Note 8, then iPX, then back to Note 8 (cause drawing), but to be fair, I do miss a little of Apple.
To be fair, it's not dead (yet) since the Oreo update landed pretty recently, plus the only tool we had for making it possible got executed pretty much, so I'd give it a little time.
And that search feature situation is a fair point.
Misterxtc said:
For the US 950U and 950U1 snapdragon there is no root for the May update. That is bootloader revision 4 and has no root at this time. Your best bet is to keep a eye on the samfail thread for updates.
Click to expand...
Click to collapse
Thanks for the tip. I'll keep an eye on it
luisramon17 said:
You switch phones a lot too? Same, heh. Went from having a Note 4 to iPhone 8 Plus, then Note 8, then iPX, then back to Note 8 (cause drawing), but to be fair, I do miss a little of Apple.
To be fair, it's not dead (yet) since the Oreo update landed pretty recently, plus the only tool we had for making it possible got executed pretty much, so I'd give it a little time.
And that search feature situation is a fair point.
Click to expand...
Click to collapse
Yeah, I have had literally all flagship phones by now except for the Huawei P20.
Last Apple Device I had was the iPX, very good device but the atmosphere of the OS makes it pretty boring to me and get bored at it pretty quickly has you can't make any changes to the look of it.
I got this Note 8, exchanged it for my iPX. The guy that maked the deal with me gave me around 200 bucks and the Note for the iPhone lol.
I love the Note 8, super fast and love the big screen.
Do not ask for an ETA
Once the mods start getting onto people for asking, I'll take my dev work off site. I don't want to upset mods and admin over people being impatient.
I've been looking and root isn't available yet for the Snapdragon version. I've created root access for a few devices so far, be it years ago. I want root, so I've decided to start dev work on my own. Can't say how long it will take, or if I will be able to, but anyone that is willing to test or help, feel free to comment and say so, since help would be greatly appreciated. Testers are needed.
First off though, what advancements have been made so far? Several posts I've seen have dead links to data, so to start, I'll need to know what's been done already. No need to reproduce failed outcomes.
Reserved for future links.
drakaina said:
Do not ask for an ETA
Once the mods start getting onto people for asking, I'll take my dev work off site. I don't want to upset mods and admin over people being impatient.
I've been looking and root isn't available yet for the Snapdragon version. I've created root access for a few devices so far, be it years ago. I want root, so I've decided to start dev work on my own. Can't say how long it will take, or if I will be able to, but anyone that is willing to test or help, feel free to comment and say so, since help would be greatly appreciated. Testers are needed.
First off though, what advancements have been made so far? Several posts I've seen have dead links to data, so to start, I'll need to know what's been done already. No need to reproduce failed outcomes.
Click to expand...
Click to collapse
One guy flashed a combination version of the firmware and got the OEM unlock toggle to show on a SM-G960U. It switched on and off but I am not sure if it actually unlocked the bootloader or not. There is a TWRP already ported to the Snapdragon version as well, although only for the Chinese and Hong Kong version, it should work on our device if you can get the bootloader unlocked first. I have been scouring online and in the forums since the phone came out and that's all I nave found thus far. Im sure you already know these things, but I figured I would say it just in case you weren't aware. Hope you get it figured out! Good luck! ?
The only development I've heard of is one user claiming he got a diagnostic boot with SElinux permissive. (In the S9 root dev forum/thread) I also have a source who is NOT trying to be identified publicly because he works for google, but he informed me that "the android O build for SAMSUNG DEVICES, was developed with special instructions in it to automatically kick a KERNEL PANIC , if ANY app NOT on some internal White List attempts to access, modify, or send SU commands through any NOT LISTED app with those permissions granted already." ... now I'm not an Android level programmer, but I'm an old Linux dev/ penetration systems tester (lol) and from what I am gathering is that the patches or whatever that Samsung added to the O.S. also included an encrypted or hidden white list, which he says is VERY small, (as in number of items actually in the list) , but even he said they do not have any access nor knowledge of where they stored this. He did tell me that they delivered an incomplete or infant code for Samsung Snapdragon Model Note 8,9 and s8,9, and it was so crude that not only would it not compile because of missing crap Samsung deliberately did not supply them with... but he said that it was NOT lockable in that state, so Samsung either inserted their own locked kernel and whatever to create this B.S. broke down version of Android that is Root crippled. BUT the only clue he could give me was that "On no level can an E-fuse provide an unbreakable chain of trust, and that if an extreme modded were to actually break down the system board of an S9, they could in theory remove or add some sort of device that would bypass the Qualcomm Secure boot completely!" ... now this ain't a best friend or nothing so truthfully I'm surprised I got this much from him... but I've known who he was and that hes worked for Google nearly 12 years as a developer and software engineer. So I dont know if any of that info helps... but my contribution is that I can get my device (s9+ from Sprint USA Sm-g965U) replaced with little to no hassle, so I'm 100% willing to do any tests u need, providing that you give me at least a basic level of instruction, as to each set of commands or package u want me to flash. I'm pretty android savvy considering it's just a linux derivative... and I know Samsung 100% .. I've had every S - galaxy since day 1 . BUT throwing blind commands at my device that I have 0 understanding of their impact, makes me feel like a squirrel running across the freeway during rush hour! Plz Do me a favor and shoot me a private message and I'll give you my cell number and email so u can reach me quicker when you have something u need tested! Now please people don't berate me if something he said to me was not correct or you have different data to disprove what he said. I literally took notes by hand and had him confirm them, so I'm just the messenger/informant and u gotta realize that as a google employee, he #1 is partially not knowledgeable of ways to exploit the O.S. which is what the hackers come into play for. And make the developers work **** tons harder to FIX the hole the ****ed up in the 1st place! ? Lol... and #2. I did ask about the possibility of a $$$$ number he would take in order to provide an actual Eng-boot like that of the S8, and he said that "Those are developed by each individual corporation after they are provided the build source code", and that "google has no interest in possessing or archiving any such file because the O.S. does not need it to provide a developers version of the O.S., which is as far as Google goes in providing a new system to the companies.... so for something like that, reach out to one of the underpaid factories full of workers and I'm sure they would happily give you what you want for much cheaper than you imagine!" Ok that was very long winded but I wanted to cover all I could because I prob wont check this thread anymore.... plz PM me bro so I can get you my info ... and let's put this Flashing Guinea Pig (me) to work in getting this ***** at least hack rooted or maybe full!!!
Hello, i've just finished reading all above and from what I've read I can tell that not all hopes are lost as well I'm offering my help to be a (TESTER) for any attempts you wanna try, however, please note that I'm NO DEV just a user who would like to his phone rooted ASAP that's all, so please explain the commands that you would give me and the steps. plz PM me so I can get you my contact info
It ain't happening with the known exploits.
Ok, so far I have a few routes I plan to take that have worked on other devices. Working on the first, but not at the moment. The rude comment compelled me to post my own. Devs don't follow old ways of doing things so get that out of your head if you want to think forward, not backwards. I have found what could be an exploit in the rom itself that "might" be the starting point to get root access. This is NOT an ETA but hopefully we can start testing in the next few weeks.
I'll say it now, don't get overly excited a possible exploit has been found. I make no guarantee on it being THE exploit needed. Just be patient, and if you have insight on a way to attack this or another possible exploit, do say so.
If anyone knows of the bootloader partition already having been copied, post a link. I share mine at the moment so I don't always have it around, so any of the bootloader data would help greatly.
drakaina said:
Ok, so far I have a few routes I plan to take that have worked on other devices. Working on the first, but not at the moment. The rude comment compelled me to post my own.
Click to expand...
Click to collapse
I saw no rude comment, just a dose of reality for you, a little thin skinned are we?
You're continuing to be rude and attempting to derail the point of the thread. Meh, I'm getting back to work since it not good to feed trolls.
Pretty sure placeholder threads are not allowed on XDA...
I am making presence known now. I will be watching this closely
Technicly this thread don't even need to exist right now.
drakaina said:
Do not ask for an ETA
First off though, what advancements have been made so far? Several posts I've seen have dead links to data, so to start, I'll need to know what's been done already. No need to reproduce failed outcomes.
Click to expand...
Click to collapse
Myself and a handful of other people involved in us snapdragon s8/s8+/n8+ took a brief crack at it a little while ago to no avail. I don't want to go into too many details on here as 1) Samsung is watching surely and 2) the contents from the peanut gallery get old quick but here are the cliff notes. Feel free to pm me here or on telegram for more details. (Backstory on me, I created samfail which was the first/only n8 root method and the second for the s8/s8+ and the only published one beyond bootloader v1.
- samfail is 100% patched. No known way to modify system
- you can't mix combo boot with stock images anymore. Samsung got wise to that. Figured out how to track it if we can force write a system image
- there is a ton of new system level security because they had to move out of the boot image due to treble. Probably the first big nail in the coffin I'm.
- don't waste your time on the oem unlock toggle in the combo/factory rom. No it doesn't unlock the bootloader. The us snapdragons don't respect it's value outside of turning off frp, but that was with the s8 idk if it is still true on the s9.
- the other poster is right about the anti root thing. It's in the open source kernel code. If anything being exexuted under uid 0 matches a list of common/known root mods/not stuff that is supposed to be there, instant kernel panic. Things like "binary is called BusyBox" are on that list.
This was the point I gave up. Partially because I don't have the device so testing is extremely difficult (I wised up this year and purchased a intl. Snapdragon sm-g9650 which has full oem unlock just like the exy).
In sure there's things in forgetting right now and again, being too transparent here results in root method bring patched faster, hit me up if you want more brain dump
drakaina said:
You're continuing to be rude and attempting to derail the point of the thread. Meh, I'm getting back to work since it not good to feed trolls.
Click to expand...
Click to collapse
Although I have seen a lot worse on these threads, his comment was pretty negative, which is what we do not need in this thread. I wish people would just keep their thoughts to themselves if they have nothing to add to the discussion. I also will test so let me know if there is anything I can do to help.
i also have a g965u and have been trying various mwthods to no avail at this point.. we need new exploits to be found.. all the obvious stuff will not work
It is because of this is why I will never buy another Galaxy phone. I need root.
zzEvilGeniuszz said:
It is because of this is why I will never buy another Galaxy phone. I need root.
Click to expand...
Click to collapse
Just don't buy snapdragon, the Exynos S9s are unlocked
*Detection* said:
Just don't buy snapdragon, the Exynos S9s are unlocked
Click to expand...
Click to collapse
You cannot buy Exynos from a carrier. You have to buy directly from Samsung for that. I know because I requested a Exynos variant. Sprint said they couldn't (or wouldn't) give me one.
edit: nvm not worth it.
zzEvilGeniuszz said:
You cannot buy Exynos from a carrier. You have to buy directly from Samsung for that. I know because I requested a Exynos variant. Sprint said they couldn't (or wouldn't) give me one.
Click to expand...
Click to collapse
i talked to samsung a couple months ago before i got my s9 and they told me they wont sell you one directly with the Exynos. I was going to get the s8 with the exynos if they would of sold me one. They wouldn'ty so i bought a tmobile s9 with my carrier.
has anyone been able to reboot phone into edl mode?
Title says all. i REALLY need to use the spay or atleast get past "Rooting detected. Use another payment method" also, if i went back to stock rom, will spay work or is it gone forever ?
Chappi3 said:
Title says all. i REALLY need to use the spay or atleast get past "Rooting detected. Use another payment method" also, if i went back to stock rom, will spay work or is it gone forever ?
Click to expand...
Click to collapse
Search, this question has been asked and answered 100's of time so search before posting.
To answer your question its gone forever, you obviously did not do your research before rooting, people get sick of answering these sorts of questions when they have been asked and answered before because people do not do a search first..
Even going back to stock it will not work.
Cheers
samorgs said:
Search, this question has been asked and answered 100's of time so search before posting.
To answer your question its gone forever, you obviously did not do your research before rooting, people get sick of answering these sorts of questions when they have been asked and answered before because people do not do a search first..
Even going back to stock it will not work.
Cheers
Click to expand...
Click to collapse
your answer is incorrect and then you went on to chastise a member for not researching. SPay has worked for folks who have rooted via Magisk modules. There is also work going on in the S10 forum about making it work more easily.
Ive personally used SPay on my Gear S3 thru a rooted phone, which was also supposed to be impossible due to tripping knox. Just to put your idea down before it even pops up, the watches knox wasnt tripped which is what non-believers used as their scapegoat justifying why it worked. SPay doesnt live on the watch, it lives on the phone. Which was VERY rooted and knox tripped.
Dont chastise members for "not researching before asking" when you cant even give accurate information in your scathing replies
Also, you had better get used to the idea that more and more repetitive questions are going to get asked because more and more people now have smartphones than ever before. And they arent forum veterans like some of us. Also also, the search results are usually quite swampy, so sometimes asking a question that has indeed been asked tons of times before is necessary to avoid 4 hours of reading to get an answer that could have been resolved in 15 min
---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------
Chappi3 said:
Title says all. i REALLY need to use the spay or atleast get past "Rooting detected. Use another payment method" also, if i went back to stock rom, will spay work or is it gone forever ?
Click to expand...
Click to collapse
going back to stock wont fix it. Check into the Magisk developments as they have had some success masking root. Do you use it on the phone or do you have a watch?
samorgs said:
Search, this question has been asked and answered 100's of time so search before posting.
To answer your question its gone forever, you obviously did not do your research before rooting, people get sick of answering these sorts of questions when they have been asked and answered before because people do not do a search first..
Even going back to stock it will not work.
Cheers
Click to expand...
Click to collapse
Instead of being a dickhead for no reason, simply answer the question, you got sick of answering ? then dont answer and just move on. people already can use spay thru their sgear but i dont have one. i've searched alot before posting this and haven't found an up-to-date thread about this.
youdoofus said:
your answer is incorrect and then you went on to chastise a member for not researching. SPay has worked for folks who have rooted via Magisk modules. There is also work going on in the S10 forum about making it work more easily.
Ive personally used SPay on my Gear S3 thru a rooted phone, which was also supposed to be impossible due to tripping knox. Just to put your idea down before it even pops up, the watches knox wasnt tripped which is what non-believers used as their scapegoat justifying why it worked. SPay doesnt live on the watch, it lives on the phone. Which was VERY rooted and knox tripped.
Dont chastise members for "not researching before asking" when you cant even give accurate information in your scathing replies
Also, you had better get used to the idea that more and more repetitive questions are going to get asked because more and more people now have smartphones than ever before. And they arent forum veterans like some of us. Also also, the search results are usually quite swampy, so sometimes asking a question that has indeed been asked tons of times before is necessary to avoid 4 hours of reading to get an answer that could have been resolved in 15 min
---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------
going back to stock wont fix it. Check into the Magisk developments as they have had some success masking root. Do you use it on the phone or do you have a watch?
Click to expand...
Click to collapse
THANK YOU so much for your detailed answer, i was just lookin' for good answer like yours but couldn't, is there anyway to use the spay without the gear ? i've rooted my phone and have Magisk installed everything works fine but not the spay when i try to purchase something off the galaxy store. is there a way to fix that or hide something inside the magisk that gives me access to purchasing via spay ?
Chappi3 said:
THANK YOU so much for your detailed answer, i was just lookin' for good answer like yours but couldn't, is there anyway to use the spay without the gear ? i've rooted my phone and have Magisk installed everything works fine but not the spay when i try to purchase something off the galaxy store. is there a way to fix that or hide something inside the magisk that gives me access to purchasing via spay ?
Click to expand...
Click to collapse
i would have to go poke around in the S10 forum to find it. But thats one thing ive learned over the decade or so that ive been on XDA, especially as of late with mfg's releasing new phones every 5.25 days. If the subforum youre diving into isnt of much or any help, i guarantee you that there are other subforums that very well might have the conversation youre looking for already going. And very especially when talking about the new blood Samsung phones. They are all SUPER similar these days and the devs are spread out across 73 different device subforums. Dont be afraid to look in subforums of phones similar to yours for stuff.
ill see if i can find that thread for ya, but i completely disregarded it as i dont plan on rooting any time soon due to the finagling you hafta do to get SPay working again.
youdoofus said:
your answer is incorrect and then you went on to chastise a member for not researching. SPay has worked for folks who have rooted via Magisk modules. There is also work going on in the S10 forum about making it work more easily.
Ive personally used SPay on my Gear S3 thru a rooted phone, which was also supposed to be impossible due to tripping knox. Just to put your idea down before it even pops up, the watches knox wasnt tripped which is what non-believers used as their scapegoat justifying why it worked. SPay doesnt live on the watch, it lives on the phone. Which was VERY rooted and knox tripped.
Dont chastise members for "not researching before asking" when you cant even give accurate information in your scathing replies
Also, you had better get used to the idea that more and more repetitive questions are going to get asked because more and more people now have smartphones than ever before. And they arent forum veterans like some of us. Also also, the search results are usually quite swampy, so sometimes asking a question that has indeed been asked tons of times before is necessary to avoid 4 hours of reading to get an answer that could have been resolved in 15 min
---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------
going back to stock wont fix it. Check into the Magisk developments as they have had some success masking root. Do you use it on the phone or do you have a watch?
Click to expand...
Click to collapse
spay on the actual phone itself?
i think not.
please enlighten us because saying it works without proof or a means to do so is just as bad.
bober10113 said:
spay on the actual phone itself?
i think not.
please enlighten us because saying it works without proof or a means to do so is just as bad.
Click to expand...
Click to collapse
all i can say is that there are people in other forums who state that they have had success with it. SPay isnt relegated to the note. The issue youre experiencing is caused by there being a TON more than just last years irrelevant galaxy phones. There used to be 1 a year, then 2 with the addition of the note series. Back then it wasnt hard to keep all the relevant information on one page and everybody with a sammy phone was in the same group. Not anymore.
Think what you like, but when it comes right down to it, the e-fuse is merely a software controller. There isnt anything that the e-fuse physically interrupts to stop SPay or anything else for that matter. Its all coding. Coding that CAN be circumvented. SPay being broken by knox being tripped is a 2 year old problem, the minds that the old galaxy devices used to have laser focused on one device are now scattered to the wind, but that doesnt mean that the answer isnt out there.
youdoofus said:
all i can say is that there are people in other forums who state that they have had success with it. SPay isnt relegated to the note. The issue youre experiencing is caused by there being a TON more than just last years irrelevant galaxy phones. There used to be 1 a year, then 2 with the addition of the note series. Back then it wasnt hard to keep all the relevant information on one page and everybody with a sammy phone was in the same group. Not anymore.
Think what you like, but when it comes right down to it, the e-fuse is merely a software controller. There isnt anything that the e-fuse physically interrupts to stop SPay or anything else for that matter. Its all coding. Coding that CAN be circumvented. SPay being broken by knox being tripped is a 2 year old problem, the minds that the old galaxy devices used to have laser focused on one device are now scattered to the wind, but that doesnt mean that the answer isnt out there.
Click to expand...
Click to collapse
please take a few minutes to point where we can find information on using samsung pay on rooted/knox tripped device.spay for the phone not the watch.( s8,s8+,s9,s9+,note8,note9,s10,s10+,s10+5g,n10,n10+,n10+5g)
you've stated your opinion. now i need to see where this information of yours comes from.( aka show proof.)
regards
bober10113 said:
please take a few minutes to point where we can find information on using samsung pay on rooted/knox tripped device.spay for the phone not the watch.( s8,s8+,s9,s9+,note8,note9,s10,s10+,s10+5g,n10,n10+,n10+5g)
you've stated your opinion. now i need to see where this information of yours comes from.( aka show proof.)
regards
Click to expand...
Click to collapse
i pop around so much between pages that it would be virtually impossible to find it again and honestly it isnt worth my time. its just like everyone has always said, research before you post. at this point, just go ahead with your thought that nobody has figured out a way to get around the knox issue and probably arent wanting the fix to spread like wildfire which would alert samsung to the vulnerability and patch it. youre right, im wrong. technically not true, but if it makes you feel better, fine....
youdoofus said:
i pop around so much between pages that it would be virtually impossible to find it again and honestly it isnt worth my time. its just like everyone has always said, research before you post. at this point, just go ahead with your thought that nobody has figured out a way to get around the knox issue and probably arent wanting the fix to spread like wildfire which would alert samsung to the vulnerability and patch it. youre right, im wrong. technically not true, but if it makes you feel better, fine....
Click to expand...
Click to collapse
i think ure mixing up google pay and samsung pay.
if something as groundbreaking as having spay work as mentionned, even with you popping up everywhere, a simple search would make it also "pop up" as well in the results.
annnyways... talk about the blind leading the blind.
OP is not much more better off by you than by the user you chastised about chastising.
bober10113 said:
i think ure mixing up google pay and samsung pay.
if something as groundbreaking as having spay work as mentionned, even with you popping up everywhere, a simple search would make it also "pop up" as well in the results.
annnyways... talk about the blind leading the blind.
OP is not much more better off by you than by the user you chastised about chastising.
Click to expand...
Click to collapse
nope. the posts i refer to specifically spoke to g-pay not being much of a problem to get working with root. It even went into the process of pulling the SPay app from the firmware and adb installing it after root is done and magisk has hidden root. Im not going to argue about this anymore as your opinion of me doesnt concern me in the slightest. The OP might find the solution with patience and perseverance as some have reported success with it and it is still definitely being worked on. SHealth has been made to work with root and SPay likely uses a similar code to disable it when it detects root. Devs arent dumb. Devs also know that once samsung knows of a security hole, they do the opposite of Sony and patch it. It wouldnt even begin to shock me if the posts got pulled to prevent this from happening to those who figured it out. Im not sure how long youve been arounf xda, but entire threads just disappear from time to time. Mods arent dumb either, they know a lucky penny when they turn up and getting something to sneak by knox is about as lucky of a penny as there even possibly could be.
Like i said, youre right man. Nobody has figured it out. Nobody will. SPay and SHealth are lost causes.
Oh, and for the op not being any better off with any of my comments vs being chastised, whenever i see a$$holes talking down to people for no conceivable reason whatsoever, they will hear about it from me