Like the title says. I've heard that previous motorola phones used eFuse to brick the phones if you did the rooting process incorrectly. Now I've also heard that because of the Tegra 2 chip that the Atrix may not have eFuse. Has anyone heard either way?
squassss said:
Like the title says. I've heard that previous motorola phones used eFuse to brick the phones if you did the rooting process incorrectly. Now I've also heard that because of the Tegra 2 chip that the Atrix may not have eFuse. Has anyone heard either way?
Click to expand...
Click to collapse
eFuse is an encryption scheme that is built into the TI OMAP series of processors and therefore not on the Atrix since it uses Tegra 2. Because of this, the Bootloader is not encrypted, although it is signed which is still very difficult to get by.
That said all you needed to do was search to find the answer.
Thank you, I did a search for "efuse" with no luck. I just followed briefmobiles step by step which was literally painless. My biggest concern was checking out all the failsafes before attempting this. I just switched from the iPhone and I do not want to have to go back because I bricked my Android like a noob lol. Thank you for your help.
Related
From what I know, bootloader loads kernel then gives control to it. So why we have to modify the bootloader? Can we just modify the kernel?
My understanding is: "signed bootloader + bootloader checking kernel's integrity" is a problem. Signed bootloader itself is not a problem.
Please educate me.
If I understand correctly:
The signed bootloader checks the signature of the kernel.
If you modify the kernel the bootloader won't recognize it.
This whole situation has me wondering "so what?" People talk about a signed bootloader like it's a permanent state. Uncrackable. Well of course it's crackable! Software encryptions are cracked all the time, what makes the Atrix any different?
jwhited said:
This whole situation has me wondering "so what?" People talk about a signed bootloader like it's a permanent state. Uncrackable. Well of course it's crackable! Software encryptions are cracked all the time, what makes the Atrix any different?
Click to expand...
Click to collapse
Yes everything is crackable but it takes time for computers to crack them. Some encryptions can take 3 seconds to crack on a super computer while the more hardcore encryptions can take months to crack on that same super computer.
Squadfer said:
Yes everything is crackable but it takes time for computers to crack them. Some encryptions can take 3 seconds to crack on a super computer while the more hardcore encryptions can take months to crack on that same super computer.
Click to expand...
Click to collapse
So I guess the question is, "Is anyone working on this?" If not, what needs to happen in order to get the ball rolling, so to speak?
jwhited said:
So I guess the question is, "Is anyone working on this?" If not, what needs to happen in order to get the ball rolling, so to speak?
Click to expand...
Click to collapse
About 20 thousand dollars. Just for the support computer.
jwhited said:
This whole situation has me wondering "so what?" People talk about a signed bootloader like it's a permanent state. Uncrackable. Well of course it's crackable! Software encryptions are cracked all the time, what makes the Atrix any different?
Click to expand...
Click to collapse
What makes the difference is the Atrix possibly has encryption/sighned bootloader going all the way to the hardware on the chip. Meaning you'd need to actually replace the chip on the main board with a non signed one
Clienterror said:
What makes the difference is the Atrix possibly has encryption/sighned bootloader going all the way to the hardware on the chip. Meaning you'd need to actually replace the chip on the main board with a non signed one
Click to expand...
Click to collapse
Or perhaps it's possible to sandbox that part of the bootloader to its own region, and have an alternate loader that doesn't do a signature check?
I mean, I know this is all based on speculation, but I can imagine numerous possibilities.
So I need to send my Atrix back to Motorola and need to flash a .sbf file in order to relock it (running CM7 for now).
I've read tutorials so I'm not concerned about the procedure but more about which .sbf file I need. My Atrix was bought from ibood.de so it's probably coming from Belgium or The Nertherlands.
Any idea of the version that is used ?
Here's a screenshot of the box for some info : http://i.imgur.com/8j7DP.jpg
Thanks !
DannyBiker said:
So I need to send my Atrix back to Motorola and need to flash a .sbf file in order to relock it (running CM7 for now).
I've read tutorials so I'm not concerned about the procedure but more about which .sbf file I need. My Atrix was bought from ibood.de so it's probably coming from Belgium or The Nertherlands.
Any idea of the version that is used ?
Here's a screenshot of the box for some info : http://i.imgur.com/8j7DP.jpg
Thanks !
Click to expand...
Click to collapse
////////////////////////////////////////////////////////////////////////////
you dont need to reload original (i sent mine with just a 2.3.6 fruitcake rom)
they will lock your phone forever with new stock rom (no way to unlock it with current procedures)
hope it help[s
Do they always lock it ? Don't you think it has to do with the fact that you send it unlocked ?
Sometimes they don't permalock it, but most of the time they do. Just assume it is going to get locked.
That's super ****ty. And there's nothing that can be done to unlock it ?
I mean, I don't even think that is legal, they just can't change my product if they want it. It's mine now and I want them to fix it not to change it.
Not only do they cancel ICS but they would now stuck me with stock rom !
DannyBiker said:
That's super ****ty. And there's nothing that can be done to unlock it ?
I mean, I don't even think that is legal, they just can't change my product if they want it. It's mine now and I want them to fix it not to change it.
Not only do they cancel ICS but they would now stuck me with stock rom !
Click to expand...
Click to collapse
You can blame all the media corps and their desire to control media consumption for that. The primary reason for locked bootloaders has a lot to do with companies and groups like Netflix, the cable industry, MPAA/RIAA, etc. not being willing to allow their services if certain protectionist measures aren't put in place.
As for locking it and it being legal? They can simply give you a replacement and it be locked and claim it was cheaper to swap it than fix it. What's worse is that there is a growing debate over who owns devices once purchased and devices purchased on subsidy could be used as being considered owned by the carrier or manufacturer and only 'leased' to the customer. Now that's what I'd call pretty s****y because if they get away with that then we'd own nothing which is ideal for any company on the ownership side of the deal.
And sorry for being a little off topic but it's definitely something that will only get worse before it gets better.
Sent from my Nexus 7
There ulis nothing illegal with them permalocking the bootloader on your device.
AnotherBill said:
The primary reason for locked bootloaders has a lot to do with companies and groups like Netflix, the cable industry, MPAA/RIAA, etc. not being willing to allow their services if certain protectionist measures aren't put in place.
Click to expand...
Click to collapse
That may be true for the US but I'm European (so is my Atrix) where Netflix and cables companies don't have any kind of power on that level (for now) + the UE tend to make laws to prevent those situations.
So can I hope that lock issue is US-only ? Did it happen to non-US users ?
DannyBiker said:
That may be true for the US but I'm European (so is my Atrix) where Netflix and cables companies don't have any kind of power on that level (for now) + the UE tend to make laws to prevent those situations.
So can I hope that lock issue is US-only ? Did it happen to non-US users ?
Click to expand...
Click to collapse
I'm not really sure but I'd be willing to bet if it goes to a US facility it'll get locked regardless.
Also, looking at the type number it appears it's the UK version but don't take my word on it.
Sent from my MB860 using xda app-developers app
I really doubt it will cross the Atlantic...
Okay, I'll see if I can get a confirmation on that UK suggestion. Thanks for that !
Ok guys come on this is driving me absolutely insane. Beautiful phone, no root all these work arounds because there is no root is driving me insane. Spent many many hours scouring xda and google for a solution. Maybe we need to think outside the box on this one remember Gingerbreak? I realize on a software level we have only standard user access, but its just an OS theres gotta be something we can do. Who needs what to get this going? Im brave enough to do what needs to be done/tested on my i527. Im comftorable using any tools you need me to will provide promptly. My device is ATT Branded but it is unlocked and currently being used on MetroPCS with working lte and usb tethering
Downgrading
What is seriously stopping us from odin'ing or heimdalling this thing back to stock 4.2.2? Never in my life have a seen a device (phone pc etc) that could not be drastically changed by going to the hardware level. Thats the point of download mode right? bypassing the need for a sucessful initialization. This thing is just a Krait 300 cpu with a Qualcomm Snapdragon 400 soc, seriously nothing new or special about it. (yes i understand the bootloader is locked and encrypted)
Ive been doing alot of thinking about this device and it honestly reminds me of the old days when we ran embedded systems, with alot of those embedded systems theres was no hardware level access what so ever, but there was always a way. Ive done numerous GPS's, Car stereos etc. All running windows embedded with no hardware level access and were able to bypass system software with ease. i realize yes it was windows embedded but the principal is still the same, not much has really changed since then. (yes i know ALOT has changed but not really all the same rules/principals apply) What we are dealing with seems to be software based encryption in the firmware of the device. With a computer I think of a couple things 1. with a bios password you screwed up on what do you do? reset the cmos...this is obiviously out for obvious reasons. 2. update/restore/bypass that bios Got a problem with the bios or screwed up restore it, done. (once again I realize these are not like a standard pc just comparison thinking outside the box remember?) Id really like to see this device flashed back to 4.2.2 then twrp'd or cwm to whatever we want from there.
Whats the real problem here?
Been asking myself what is the REAL problem? I dont mean, root or locked bootloader. What is really stopping us? Answer is super simple yet complicated. User Account Permissions We need rw access to that system folder. Via terminal on the device im able to mount /system as rw but any further changes are useless usually result in a bad mode error. Maybe we need to call in a black hat boy and give us an account exploit for at least software level (os root is better than no root right?)? Ive got some friends in high places in security working for that wonderful DoD, ive been in the game a long time can keep up with most of em but i went networking not security.
Come on people Ive never seen this community give up on something like this before! Yall got me started on all this with my ppc6700, and this bump in the road just makes me wanna lift the civic up a bit so we dont scrape and hit it at 30mph.
In the words of Young Jeezy:
If you grind hard enough
You could stack a few mil' nigga make it out the streets like me
If you grind strong enough
You could be a trap star nigga be on TV and keep it G
If you grind long enough
You could take care of your nephews and your nieces and your moms and your girl
If you grind hard enough
You could stand on top, tell these hatin a** niggas It's Tha World
Its all you man, knock yourself out. I was optimistic for a year. Longest year of my life. I got parolled and then liberated from Samsung.
It was malnourished from the get go, designed as an affordable big screen device. But very average.
Get out now my friend.
Sent from my Nexus 6 using XDA Free mobile app
Hey!
Does anybody know if this phone has a hardware fuse (or an internal counter), which blows after eg. unlocking the bootloader or something like this?
I'm pretty sure it does not because I am have switched from bootloader unlocked to locked and root to unroot with no lasting effects for anything such as android pay or snapchat
Yeah, I think you are right. I'm just asking because I found mention of a fuse inside the Project Menu (*#*#2846579#*#*), but in a different regard. Also I know that Huawei did this at least once with the Nexus 6P.
Let's ignore the Chinese SnapDragon variant that has BL unlock and root.
For all the other SnapDragon versions, is it possible that they will never get bootloader unlock and root? I'm looking at the S8+ which has been released well over a year now and the SnapDragon variants also seem to not have root or BL unlock.
EDIT: Wow, even looking back at the S7, LineageOS is only supported on the Exynos models and none of the SnapDragons:
https://wiki.lineageos.org/devices/herolte
https://wiki.lineageos.org/devices/hero2lte
fuzzybabybunny said:
Let's ignore the Chinese SnapDragon variant that has BL unlock and root.
For all the other SnapDragon versions, is it possible that they will never get bootloader unlock and root? I'm looking at the S8+ which has been released well over a year now and the SnapDragon variants also seem to
Click to expand...
Click to collapse
It's unlikely. It takes finding an actual exploit to unlock the bootloader which comes with tradeoffs. You will trip Knox which will permanently void your warrenty, as well as make it so Samsung Pay never works again. In the S8 it also cripples the battery to never charge over 85% I believe.
It's possible that someone may find an exploit to achieve root / unlock bootloader. I wouldn't hold out hope though. If you really have to have root / custom roms, don't get the US Snapdragon device. Or get another phone altogether.
todd3835 said:
It's unlikely. It takes finding an actual exploit to unlock the bootloader which comes with tradeoffs. You will trip Knox which will permanently void your warrenty, as well as make it so Samsung Pay never works again. In the S8 it also cripples the battery to never charge over 85% I believe.
It's possible that someone may find an exploit to achieve root / unlock bootloader. I wouldn't hold out hope though. If you really have to have root / custom roms, don't get the US Snapdragon device. Or get another phone altogether.
Click to expand...
Click to collapse
Thanks. For me root is necessary. I've used Samsung ever since the S2. Besides being very very slow to release OS updates, they are notorious for no longer supporting and updating a phone that hardware-wise still has a TON of life left in it. When this happens, instead of being forced to upgrade I simply install something like LineageOS on it and get years of extra use out of it.
So for me root is very very important and I'm pretty mad that they stopped it for SnapDragon since at least the S7. Sound reasonable?
fuzzybabybunny said:
Thanks. For me root is necessary. I've used Samsung ever since the S2. Besides being very very slow to release OS updates, they are notorious for no longer supporting and updating a phone that hardware-wise still has a TON of life left in it. When this happens, instead of being forced to upgrade I simply install something like LineageOS on it and get years of extra use out of it.
So for me root is very very important and I'm pretty mad that they stopped it for SnapDragon since at least the S7. Sound reasonable?
Click to expand...
Click to collapse
it's a kind of "in the eye of the beholder" thing really.
Your not forced to upgrade phones. You don't have to actually root the phone to get use out of it once Samsung decides to stop issuing major OS updates, you can easily use the same OS for a long while. I know some brand new phones that are still being sold with older android OS's on them, and I know quite a few people who are getting a lot of use out of them.
Also it's not that they stopped it for the snapdragon phones as much as it is Samsung made the phone to be secure. If there is no exploit that can be found to install root on the phone then it means Samsung did what they were supposed to do when designing, creating and updating the phone. While I would also like the ability to root the phone at some point in time and customize it as I wish, I also do prefer to maintain the ability to keep my phone secure. Rooting the phone strips away some/most of that security by allowing full admin access to the phone's software (something that it was not originally intended to be sold with).
So like I said, it's an eye of the beholder thing....
fuzzybabybunny said:
Thanks. For me root is necessary. I've used Samsung ever since the S2. Besides being very very slow to release OS updates, they are notorious for no longer supporting and updating a phone that hardware-wise still has a TON of life left in it. When this happens, instead of being forced to upgrade I simply install something like LineageOS on it and get years of extra use out of it.
So for me root is very very important and I'm pretty mad that they stopped it for SnapDragon since at least the S7. Sound reasonable?
Click to expand...
Click to collapse
As the other person said, there's nothing wrong with running an older OS. I typically upgrade every year or two, so I'm not too worried.
I used to always root and usually run something custom. The S9 Plus is the 2nd phone I haven't rooted,the LG v20 being the other. Honestly, the only thing I was missing was Titanium Backup. Google has gotten better about backing up app data. It isn't perfect, but it's a lot better. Samsung also included a decent backup app for restoring.
As for OS updates, we are already seeing Treble pay off. Sure, being able to use a GSI image would be nice but the alpha builds are further along than in previous years at the time from what I've read.
If you truly care about root / custom roms, you should probably get a pixel. They are the easiest to unlock, have the fastest updates, and will play so nicely with GSI images.
I wish I had researched this aspect of the 9/S9+ more before buying one.
I came from the S5, and the Galaxy S before, and didn't realize that the phone hadn't had root for a while (and was looking so doubtful)
Titanium Backup *was* a favorite root-enabled program, as well as a few others, and I liked LineageOS.
But I will probably stay with this phone for a while, now that I own it. It has been a good phone -- I just liked the freedom of a rooted phone.
fuzzybabybunny said:
Let's ignore the Chinese SnapDragon variant that has BL unlock and root.
For all the other SnapDragon versions, is it possible that they will never get bootloader unlock and root? I'm looking at the S8+ which has been released well over a year now and the SnapDragon variants also seem to not have root or BL unlock.
EDIT: Wow, even looking back at the S7, LineageOS is only supported on the Exynos models and none of the SnapDragons:
https://wiki.lineageos.org/devices/herolte
https://wiki.lineageos.org/devices/hero2lte
Click to expand...
Click to collapse
Due to nobody trying to work on it actively I don't think more than likely not. We'd have to try to bring in somebody