I've seen plenty of topics about unlocking or 'jailbreaking' Windows Phone 7.
I was just wondering if anybody could explain specifically any disadvantages to unlocking? I know it risks voiding your warranty and things like that.
One of my major concerns is whether this risks making the phone ineligible for future updates from Microsoft/Carriers or even bricked by updates (such as some early jailbroken iPhones were). I'd also like to know if this restricts access to the marketplace or anything like that.
I know I've heard that the phones can often re-lock themselves. That's fine with me as long as it doesn't retain any negative side effects.
Any information anyone can provide would be much appreciated. Thanks in advance.
Xuanlong said:
I've seen plenty of topics about unlocking or 'jailbreaking' Windows Phone 7.
I was just wondering if anybody could explain specifically any disadvantages to unlocking? I know it risks voiding your warranty and things like that.
One of my major concerns is whether this risks making the phone ineligible for future updates from Microsoft/Carriers or even bricked by updates (such as some early jailbroken iPhones were). I'd also like to know if this restricts access to the marketplace or anything like that.
I know I've heard that the phones can often re-lock themselves. That's fine with me as long as it doesn't retain any negative side effects.
Any information anyone can provide would be much appreciated. Thanks in advance.
Click to expand...
Click to collapse
Hi, What do you mean "unlocking" unlock to all networks or unlock to use third party software? Unlock mobile by code is easy and safe. This is permanent unlock and after that you can use any sim card. You can loose warranty but I did it a few times and newer had problems with it. After using jailbreak you can install third party software. This is a temporary solution because after hard reset you loose everything and you need to use jailbreak once again.
Regards
Regarding Jail-breaking, if I rolledback the updates I installed in order to use CheveronWP7, is there any contact loss? Also will I be able to update it without relockng it?
Does WP7 has it's own unofficial marketplace like Cydia?
If not, then I don't see any point in jailbreaking this not-so-evolved OS.
Wait for a while, let it get popular, let more developers get interested and then finally you will have pirated apps for which you will need to jailbreak your phone
Hi
I know that this will sound like another hacked story but I know what to do.
My phone got hacked couple of months back.i didnt know it was untill the hacker started to leave clues. It was then that i started really payibg attention to everything going on. but keeping quiet abort it so that he or she thinks i didn't know
I know of 3 incidents that may have conpronised my security coupled by the fact that I did not practice password hygiene or unique ones for all accounts. I know that its totally my fault and i am not goings to blane Android os. So please dont think of this as one of tjose posts
What i now need is help in understanding what tondo next.
Little details on what happens, lets say i get search for some one on Facebook. The same is Charles smith, I Finish off my search and open Instagram boom i see a pictures where recommended shows a google search page where Charles is written and the Google auto complete is giving options .
Happened twice
I tumlr and I don't really post anything in fact My blog is totally blank. Suddenly i have people followings me and they tend of hame my nick name as their user id .the id displays my WhatsApp status updates.
These and just two examples i have more but i think everyone gets whats going on.
things i have done to prevent such occurences factory formatting the phones mac abd router. Gotten new routers and ready to flash a custom firmware for them.
Password changes .everything.wps2 aes wifi password with random numbers upper case lower case n symbols
Passwords are written on paper without a electronic backup and under lock and key.
I thought that maybe its a key logger but i took my moto x2 n moto e2 to the service center and got them to re load official software.
Two days later bam the same thing.
Any suggestion on where the weakness is ?
The problem is that I am kind of tired if thi
Sent from my XT1092 using XDA Forums
Check account sync settings if it is on more applications can use various private data.
Sent from my A0001 using XDA Free mobile app
i dont understand?
can u explain , i have sync on should I not have it
on different note does anyone suggest rooting and installing something that can isolate and restrict data from being accessed. now i know that exposed does that and marshmallow will work that out. but any other guidance ?
Did you use a virus or malware scanner?
Are there any apps you didn't install on your phone?
If i were you, i would start with doing the following steps by their exact order to get rid of the hacker and operate on a "safe" system.
1- Backup personal files to pc and deep scan them with virus scanner, make sure they're clean.
2- Unlock the bootloader of device and flash every image manually with fastboot from stock factory image.
3- After flashing the images, go to stock recovery and wipe data / factory reset and wipe cache for a complete, untouched system.
4- Change account passwords with stuff that are unrelated to you. I mean if you made a google search for firedance, don't include dance or fire in any your passwords.
* also change the " forgot my password " questions and their answers.
5- Once you boot the system, download any ota packages from the manufacturer to be sure you'd be on a safer and patched software for security.
For future securtity, be sure to check apps permissions before installing anything from google play or external places. Don't root your device and don't enable USB Debugging in developer options. Hope it helps.
Semseddin said:
If i were you, i would start with doing the following steps by their exact order to get rid of the hacker and operate on a "safe" system.
1- Backup personal files to pc and deep scan them with virus scanner, make sure they're clean.
2- Unlock the bootloader of device and flash every image manually with fastboot from stock factory image.
3- After flashing the images, go to stock recovery and wipe data / factory reset and wipe cache for a complete, untouched system.
4- Change account passwords with stuff that are unrelated to you. I mean if you made a google search for firedance, don't include dance or fire in any your passwords.
* also change the " forgot my password " questions and their answers.
5- Once you boot the system, download any ota packages from the manufacturer to be sure you'd be on a safer and patched software for security.
For future securtity, be sure to check apps permissions before installing anything from google play or external places. Don't root your device and don't enable USB Debugging in developer options. Hope it helps.
Click to expand...
Click to collapse
Don't Root your device? Don't check USB debugging? Seriously? That is your answer? Wow, do you work for Verizon or AT&T by some chance? Sorry, but with Root and some nicely placed Xposed modules, this persons phone or tablet would be more safe than anything g Verizon or AT &THE could conjure up. You are a dope! Lol! Seriously, go away. Bother another community. ?
Sent from my SM-N910V using Tapatalk
Jaytronics said:
Don't Root your device? Don't check USB debugging? Seriously? That is your answer? Wow, do you work for Verizon or AT&T by some chance? Sorry, but with Root and some nicely placed Xposed modules, this persons phone or tablet would be more safe than anything g Verizon or AT &THE could conjure up. You are a dope! Lol! Seriously, go away. Bother another community. ?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Pardon me but where does that come from ? Made me laugh. Since this is security forum, the first priority is security not your "nicely put xposed modules whatever that means". It is said many times by security experts rooting an android device removes a big portion of layer of security. I unfortunately don't work for AT&T or Verizon but i wish i worked for them for a nice salary.
This one is coming from the recognized developer and moderator of XDA Android Security forum. Someone who have exploited devices and found vulrenabiliies that you can't even dream of. Lets say i am a "dope" and you're the smart guy. Are jcase, steve kondik dopes as well ?
http://securitywatch.pcmag.com/secu...-have-android-settings-from-a-security-expert
http://www.dailytech.com/CyanogenMod+Creator+Tells+Android+Users+to+Rethink+Rooting/article33058.htm ( yeah, even steve kondik doesn't approve rooting for general users.
https://blog.kaspersky.com/rooting-and-jailbreaking/1979/ " Kasperksky a security platform well known for years are also against rooting.
Think again if you can who is the dope, now, go bother in your nicely put xposed modules forums for the sake of security. :good:
Semseddin said:
Pardon me but where does that come from ? Made me laugh. Since this is security forum, the first priority is security not your "nicely put xposed modules whatever that means". It is said many times by security experts rooting an android device removes a big portion of layer of security. I unfortunately don't work for AT&T or Verizon but i wish i worked for them for a nice salary.
This one is coming from the recognized developer and moderator of XDA Android Security forum. Someone who have exploited devices and found vulrenabiliies that you can't even dream of. Lets say i am a "dope" and you're the smart guy. Are jcase, steve kondik dopes as well ?
http://securitywatch.pcmag.com/secu...-have-android-settings-from-a-security-expert
http://www.dailytech.com/CyanogenMod+Creator+Tells+Android+Users+to+Rethink+Rooting/article33058.htm ( yeah, even steve kondik doesn't approve rooting for general users.
https://blog.kaspersky.com/rooting-and-jailbreaking/1979/ " Kasperksky a security platform well known for years are also against rooting.
Think again if you can who is the dope, now, go bother in your nicely put xposed modules forums for the sake of security. :good:
Click to expand...
Click to collapse
For a dope, I suppose that Root is a security risk. But, just because a device is not Rooted, does not mean it is secure by any stretch of the imagination. Truthfully, they are more unsecured if locked out from the user. That is, if the person is not a dope. What I am saying is that your advice, for the OP to take every update and not Root, was not really that helpful. If the OP installed an app that was a risk, then all the updates and non Root, will not help them. Now, if you were to show them, that if they were to Root, and use certain apps and modules on their device. Then they could keep a better eye out for potential problems. But, even if they did as I just said. If the OP is being a dope, and installing apps that, let's say, they obtained from a torrent site. Then, well, dope would be a fitting title for them as well.
And, if those recognized developers stated that Root was not good at all. Then yes, dope would be a fitting application of the word. Root is only bad for those that are dopes.
I believe that you inadvertently called the OP a dope. You did not help them all that well. What you did was help them to get rid of the problem temporarily. Do we know who apps are on their device? It would be a good idea to know these things. Also, where did they get these apps from? Kind of a big deal there.
But, if you were wondering what it is that I am talking about in regards to xposed. Look it up.
http://repo.xposed.info/module/de.robv.android.xposed.installer
I suggest the OP do the same. As well as anyone else who is having g issues. Now, knowing about xposed and the modules that can accompany it. Will not fully protect anyone from blatant stupidity. Read, read, read. And practice safe device use. There are so many avenues to protecting g ones self. But a big one that anyone can do. Don't download from shady places. Though, it is even very possible to get in trouble from apps from the Play store. Knowing what apps are asking for what permissions is important. What bothered me about your post is that you in the same post, stated for them to unlock the bootloader and then, to not root. Verizon and AT&T are advocates of the no Root behavior. And that sickens me. As well as many others. Instead of helping g people to see the dangers. They are told to do the most simplest of tasks, not to Root. And that they would be fine. Absolutely and completely false and misleading. Now, and again, for a dope. I suppose this would be fine. Though, it is not helpful. Education into matters are. One needs to seek out the underlying issue first. Then attempt to educate. As far as calling you a dope, I do humbly apologize for my Choi e of words. You did not deserve that. It would have been just fine for me to build onto what you suggested. Which was good advice. So, I am sorry. And yes, I am very much a dope at times .
Sent from my SM-N910V using Tapatalk
Jaytronics said:
For a dope, I suppose that Root is a security risk. But, just because a device is not Rooted, does not mean it is secure by any stretch of the imagination. Truthfully, they are more unsecured if locked out from the user. That is, if the person is not a dope. What I am saying is that your advice, for the OP to take every update and not Root, was not really that helpful. If the OP installed an app that was a risk, then all the updates and non Root, will not help them. Now, if you were to show them, that if they were to Root, and use certain apps and modules on their device. Then they could keep a better eye out for potential problems. But, even if they did as I just said. If the OP is being a dope, and installing apps that, let's say, they obtained from a torrent site. Then, well, dope would be a fitting title for them as well.
And, if those recognized developers stated that Root was not good at all. Then yes, dope would be a fitting application of the word. Root is only bad for those that are dopes.
I believe that you inadvertently called the OP a dope. You did not help them all that well. What you did was help them to get rid of the problem temporarily. Do we know who apps are on their device? It would be a good idea to know these things. Also, where did they get these apps from? Kind of a big deal there.
But, if you were wondering what it is that I am talking about in regards to xposed. Look it up.
http://repo.xposed.info/module/de.robv.android.xposed.installer
I suggest the OP do the same. As well as anyone else who is having g issues. Now, knowing about xposed and the modules that can accompany it. Will not fully protect anyone from blatant stupidity. Read, read, read. And practice safe device use. There are so many avenues to protecting g ones self. But a big one that anyone can do. Don't download from shady places. Though, it is even very possible to get in trouble from apps from the Play store. Knowing what apps are asking for what permissions is important. What bothered me about your post is that you in the same post, stated for them to unlock the bootloader and then, to not root. Verizon and AT&T are advocates of the no Root behavior. And that sickens me. As well as many others. Instead of helping g people to see the dangers. They are told to do the most simplest of tasks, not to Root. And that they would be fine. Absolutely and completely false and misleading. Now, and again, for a dope. I suppose this would be fine. Though, it is not helpful. Education into matters are. One needs to seek out the underlying issue first. Then attempt to educate. As far as calling you a dope, I do humbly apologize for my Choi e of words. You did not deserve that. It would have been just fine for me to build onto what you suggested. Which was good advice. So, I am sorry. And yes, I am very much a dope at times .
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Humble apology accepted.
You may not like AT&T and Verizon for their tight stance against rooting.I don't like that as well. They're filling their devices with their bloatware and excluding some very useful features from their customers like hotspot for free. However, Anyone who owns an operator variant of a specific device have already signed a contract with his operator already accepted their terms and that's why they get their bloated and controlled devices for cheaper prices in long term instead of paying full in cash. That said, i see nothing wrong with AT&T or Verizon's policy of keeping their devices locked to death since rooting would take a stake from their business and that was not their agreement with their customers. This is not the subject of this thread for sure. Should add, i see nothing wrong if a contracted owner a device wants to take full potencial out of it by rooting since it is the only way for them to get rid of bs in their devices. This is another discussion, not related to this thread.
I will use the word " regular user " instead of "dope" since nobody have to be knowledgeful about android security. Being someone without a clue of android security wouldn't make them a "dope". I currently sport a Moto Maxx, a bootloader unlockable variant of Verizon Droid Turbo sold in Brazil. I paid about 150$ more just to be free of Verizon Bloatware for the exact same hardware. I could have paid 150$ less and bought a Verizon Droid Turbo but i didn't just because i knew i would have Verizons' bs running in my phone every second. There used to be a time for me when rooting was a must with android because i used to own devices bloated with Motoblur, having low amount of ram and storage as well as unavailbility of disabling/deleting of unwanted apps. Now, i have 3gb of ram and 64gb storage with near Vanilla Android experience with my phone. I asked myself, what the heck do i need rooting for ? The answer was easy : nothing.
Lets say, android is an apartment, the root is the key to its door, xposed is the "watchdog" and hacker is the "thief". Would you keep the door unlocked and rely on a dog for its security ? I personally wouldn't do that cause the dogs can be fooled easily by a piece of meat and most importantly they have no responsibility at all. After all, It is just a dog serving for free without any responsibility. I couldn't ask for insurance as well cause i was the one who kept the door unlocked. I am also aware that any door can be opened without a key and the dog can be bypassed easily and the hacker can get whatever he wants. Things will happen if they're destined to be happen, we can't avoid some. Still, it is always our responsibility to keep the door locked in the first place and take counter measurements against. That was what i was pointing in my post.
Disabling USB debugging is the first thing one should do if there're concerns about security and this is not coming from a "dope" but security experts of android. :good:
Semseddin said:
Lets say, android is an apartment, the root is the key to its door, xposed is the "watchdog" and hacker is the "thief". Would you keep the door unlocked and rely on a dog for its security ? I personally wouldn't do that cause the dogs can be fooled easily by a piece of meat and most importantly they have no responsibility at all. After all, It is just a dog serving for free without any responsibility. I couldn't ask for insurance as well cause i was the one who kept the door unlocked. I am also aware that any door can be opened without a key and the dog can be bypassed easily and the hacker can get whatever he wants. Things will happen if they're destined to be happen, we can't avoid some. Still, it is always our responsibility to keep the door locked in the first place and take counter measurements against. That was what i was pointing in my post.
Disabling USB debugging is the first thing one should do if there're concerns about security and this is not coming from a "dope" but security experts of android. :good:
Click to expand...
Click to collapse
To show how ridiculously and persistently wrong you are, I am going to use your above example. If root is your key, then what you are doing is giving that key to Google and device manufacturer, while throwing your own copy away. In your own apartment, you are only allowed to go where google and verizon let you. This makes no sense whatsoever, unless the apartment owner is a real dope (no personal offence meant).
Disabling usb debugging also sounds like an aria from the same opera. If the device is on your person, this provides no additional security at all, as usb debugging is only relevant when your phone is connected to computer. If someone physically takes your device, it would take 10 seconds to enable debugging.
Root provides you an opportunity to control your device and restrict system apps, thereby reducing possibilities for hackers to take over your phone... As I have already mentioned before, every operating system provides root access to users. The only reason it is not done on smart phones is becase manufacturers, carriers and OS providers want to turn users into walking advertising beacon-dopes. Again, no offence meant...
optimumpro said:
To show how ridiculously and persistently wrong you are, I am going to use your above example. If root is your key, then what you are doing is giving that key to Google and device manufacturer, while throwing your own copy away. In your own apartment, you are only allowed to go where google and verizon let you. This makes no sense whatsoever, unless the apartment owner is a real dope (no personal offence meant).
Disabling usb debugging also sounds like an aria from the same opera. If the device is on your person, this provides no additional security at all, as usb debugging is only relevant when your phone is connected to computer. If someone physically takes your device, it would take 10 seconds to enable debugging.
Root provides you an opportunity to control your device and restrict system apps, thereby reducing possibilities for hackers to take over your phone... As I have already mentioned before, every operating system provides root access to users. The only reason it is not done on smart phones is becase manufacturers, carriers and OS providers want to turn users into walking advertising beacon-dopes. Again, no offence meant...
Click to expand...
Click to collapse
I see your point, respect it but disagree. Your example doesn't really work with my logic since you're putting players like Google/Verizon in the same league with an hacker. Yes, they for sure have control over their software since they're the one who created Android and offered the hardware along with an oem in the first place. These big companies are not like 3rd party devs who are irresponsible for any their actions.. If you happen to have sensetive privacy trust issues with Google, leave any android device out, you wouldn't even use google search in your pc.
A hacker having pyshical access to a device who would enable USB debugging in 5 seconds. is this what we're really talking about ? Anyone who have a device in hand doesn't need to be a hacker to get data from it. Have a coffee with the target sitting next to to him, memorize his passcode Done. Another way is to flash twrp and give some adb shell commands to bypass any lockscreen code. Done. USB debugging ON help with apk rooters and computer based root exploits as well.They rely on usb debugging to be on. You're hacked in no time.
I just can't trust any 3rd party dev more than my device manufacturer / operating system provider and network provider. I think the same for you like you're persistently and ridiciolusly wrong by giving too much credit to some unknown sources instead of those who have an actual business address. :good:
Just kiss each other already or dont say anything.
This thread is made by someone who needs help and you two both are taking it off topic instead of helping him. Now out of respect for that user, stop this endless conversation.
Semseddin said:
I see your point, respect it but disagree. Your example doesn't really work with my logic since you're putting players like Google/Verizon in the same league with an hacker. Yes, they for sure have control over their software since they're the one who created Android and offered the hardware along with an oem in the first place. These big companies are not like 3rd party devs who are irresponsible for any their actions.. If you happen to have sensetive privacy trust issues with Google, leave any android device out, you wouldn't even use google search in your pc.
A hacker having pyshical access to a device who would enable USB debugging in 5 seconds. is this what we're really talking about ? Anyone who have a device in hand doesn't need to be a hacker to get data from it. Have a coffee with the target sitting next to to him, memorize his passcode Done. Another way is to flash twrp and give some adb shell commands to bypass any lockscreen code. Done. USB debugging ON help with apk rooters and computer based root exploits as well.They rely on usb debugging to be on. You're hacked in no time.
I just can't trust any 3rd party dev more than my device manufacturer / operating system provider and network provider. I think the same for you like you're persistently and ridiciolusly wrong by giving too much credit to some unknown sources instead of those who have an actual business address. :good:
Click to expand...
Click to collapse
This is not about respect, disrespect or disagreements. The facts (not opinions) remain: every operating system on Earth provides root or administrative privileges to users. However, it is not given to the same user when he turns to a smartphone. There is no security reason whatsoever why a user has root on computer and no root on a smartphone.
As I have already said, there are plenty of non-security reasons for the above: the main one being to prevent the user from removing advertising junk and spying malware inserted there by manufacturers, carriers and software providers. Kids love it (above three) and Mother (NSA) approves...
Every argument against root invalidates itself when applied to computer OS: remember the user is the same.
@its the peanut
Please stop patronizing. This is a security discussion thread and we discuss security, which is beneficial to the poor guy, the OP... :silly:
Semseddin, what do you do to stop fastboot?
rooting and knowledge go hand in hand, the OP states device is rooted, but sounds like hasn't got the interest to know what's behind the process. that is why we don't have the slightest piece of evidence that his device has been compromised. just the users opinion that it has.
having su and adb debugging at least allows them to logcat.
I have a Skyuniverse Elite A5 that i want to root. I've reached out to manufacturer several times with no luck on instructions to unlock boot-loader. its running android 9 (go edition) currently. Id like to root with magisk so i would need the stock boot.img however there is very, very minimal information on this device. where to begin on a device that has this many speed bumps? i need instructions on how to unlock my boot loader, clone my stock firmware to acquire necessary files, and rooting a ARM Cortex-A53 device with build ID: Elite_A5_1700_V1.0_202000618 Kernel Version 4.4.147 (24414) kernel architecture armv71. Thanks in advance
nonamemaddox5446 said:
I have a Skyuniverse Elite A5 that i want to root. I've reached out to manufacturer several times with no luck on instructions to unlock boot-loader. its running android 9 (go edition) currently. Id like to root with magisk so i would need the stock boot.img however there is very, very minimal information on this device. where to begin on a device that has this many speed bumps? i need instructions on how to unlock my boot loader, clone my stock firmware to acquire necessary files, and rooting a ARM Cortex-A53 device with build ID: Elite_A5_1700_V1.0_202000618 Kernel Version 4.4.147 (24414) kernel architecture armv71. Thanks in advance
Click to expand...
Click to collapse
You have to get the bootloader unlocked first, there is nothing you can do until that happens. There is no "other way".
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You have to get the bootloader unlocked first, there is nothing you can do until that happens. There is no "other way".
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
What would you recomend I try if manufacturer, carrier, and OS proprietary owner's all are not willing to provide any assistance? I've tried every fastboot command I could find, not even a specific code is given like some devices and even if I did acquire some special code there is no avenue to request unlocking from anyone. I'm finding it hard to believe that they are legally allowed to control how i use my device that i paid for. I can't stand not being in control of my phone. i feel like im being left in the dark about all the processes that are running because i literally am. i cant even view logs of anything. just what is running; not what exactly they are doing. this isnt right
nonamemaddox5446 said:
What would you recomend I try if manufacturer, carrier, and OS proprietary owner's all are not willing to provide any assistance? I've tried every fastboot command I could find, not even a specific code is given like some devices and even if I did acquire some special code there is no avenue to request unlocking from anyone. I'm finding it hard to believe that they are legally allowed to control how i use my device that i paid for. I can't stand not being in control of my phone. i feel like im being left in the dark about all the processes that are running because i literally am. i cant even view logs of anything. just what is running; not what exactly they are doing. this isnt right
Click to expand...
Click to collapse
You have no choice but to do what we all do here when we have a device that has no valid bootloader unlock method, that is to just accept the fact that you are not going to unlock the bootloader without an unlock code from the manufacturer/carrier or paying for a bootloader unlock service from a shop/website that is not guaranteed to successfully unlock the bootloader.
The manufacturer and the carrier don't "have" to provide us with bootloader unlock information if they don't want to.
As a matter of fact, not giving us the bootloader unlock information actually protects their interests as far as network security and their warranty on the device is concerned.
Manufacturers lose a lot of money repairing/replacing devices that have been hardbricked due to user error/ignorance during the user's attempt to unlock and modify the device. When I device has been hardbricked, the manufacturer has no way to know that the device has been modified and that the warranty is now no longer valid due to the device being modified. Therefore, they end up paying to repair/replace devices that have technically had their warranty voided by the users modifications.
Sent from my SM-S767VL using Tapatalk
Well I completely understand where you're coming from and also understand that that is the normal methods that most users must abide by however I will do everything in my power to ensure that I can do what I want with my device. Of course manufacturers and cell phone carriers do not want users to unlock the bootloader and acquire root privileges. They hide behind the facade that they are limiting a devices use to prevent improper user operations in which could malfunction the device. That's the official statement, however if one were to acquire root privileges one would be able to view and stop all the data acquisition processes that are running in the background and everyone's device currently without their knowledge or permission. Every single application has a main objective and a more important secondary function, "capture any information that they can sell". I'm beginning the process of litigation in this matter. Manufacturer's, cell phone carrier's, and all of Google's various Android Operations cannot provide any legal documentation regarding terms and conditions and policies on rooting or installing custom operating systems. Now is the time to force them to update their policies while they do not have any currently implemented. They are no rules written about this matter they are just going with the flow essentially, mostly because nobody is aware of this. It's time you and everyone else take ownership of their devices and prevent others from profiting without your knowledge, permission, and stipulations if you choose to share your information. It's important to remember that it is okay to share information as long as you are compensated for it and are aware of its intentions. Imagine buying a pair of shoes and when you begin lacing them how you wish you are somehow unable to do so. The holes are there, the strings are in your hands, but the manufacturer doesn't want you to lace them up how you wish because if you did they wouldn't be able to make any more money off of the shoes. They have already sold the shoes, they are not in possession of them anymore; you are, however they are still trying to tell you what to do with your shoes. If you can't graspe the audacity of all this I suggest you begin researching. I used you as a framing device to convey my message so if you are offended by any of my statements please know that I was also referring to the general public as well as you. Nothing I said was intended to hurt or bother you.
People are hacking things left and right to effortlessly gain root or remove pattern locks on their Androids and thanks to devs of this wonderful resource they're not spending a dime in the process, but for some reason unlocking a hardlocked bootloader, an age-old problem, has no other method but the one costing $30. I'd love if someone could explain to me what makes it such a conundrum to figure out and why aren't more people trying to come up with a free solution for everyone.
Hi @4qx.
For devices that have OEM Unlocking grayed out (so you can't unlock the bootloader), there can never be a single solution that would work for every device. Different device manufacturers have their own ideas about security and contain proprietory code specific to that manufacturer, and it's further refined as new models from the same manufacturer come out.
Sometimes a device-specific vulnerability is found and can be taken advantage of to gain root. Sometimes the manufacturer makes a very specific but easy-to-find mistake on one particular version of Android on a single device that lets users officially unlock their bootloader, but that mistake is corrected with the next update for the device.
Even though you might not hear of someone working to root particular devices, it doesn't mean that no one is trying. It's common and expected that attempts that involve vulnerabilities would be kept as secret as possible so that a manufacturer can't patch them before developers can take advantage of what they found.
So the combination of different manufacturers, different models, different variations of models, different Android versions, and different manufacturer or device-specific security makes it near impossible to find a way to root all devices without exception.
Lastly, the easiest and universal method to start the path to being rooted is to have a device that lets you unlock the bootloader officially - preferably with no penalties like some manufacturers do. Anyone who buys devices that you can unlock the bootloader officially probably has no interest in finding a way to root other ways since it's so easy to do with an unlocked bootloader.
Edit: Also, regarding "free for everyone", it takes developers time to achieve what they do, so finding a way to root a device usually isn't a way to make money to live, so they do what they can when they can.
give it a try
https://github.com/bkerler/edl#for-generic-unlocking
If you're citizien of EU and bought an Android device in the territory of EU you never will have troubles with unlocking a phone's bootloader and rooting phone's Android.
Huawei will stop providing bootloader unlocking for all new devices
Earlier this month, we wrote about Huawei and Honor users not being unable to access the page for generating bootloader unlock codes. Now, they will stop providing unlock codes completely.
www.xda-developers.com
You shouldn't post here if you've NO knowledge about current legal situation in EU.
I am from germany too and can tell you Vodafone still sells Huawei devices. There are other brands with non-unlockable bootloader (Google, Samsung, Vivo, Oppo). OEMs tend to lock down their devices entirely for reason
aIecxs said:
give it a try
https://github.com/bkerler/edl#for-generic-unlocking
Click to expand...
Click to collapse
Unless I misinterpret what it says, it seems to be for enabling OEM unlocking. I was referring to unlocking a hardlocked bootloader.
Sorry maybe I didn't get you right. kindly share definition / example or at least descripe what you mean with "hardlocked bootloader"?
roirraW edor ehT said:
For devices that have OEM Unlocking grayed out
Click to expand...
Click to collapse
Was talking about something different, though I appreciate the info.
@aIecxs check this out. Some Xperia models, mostly Japanese ones, have unlockable OEM but are not allowed to have their bootloader unlocked.
Fairly enough there exist quit few devices where manufacturer provides official unlock code, but carrier locked down bootloader by ignoring, disabling or hiding OEM unlock toggle or other device specific methods. I feel "hardlocked bootloader" is a good way to differ from "non-unlockable bootloader" where bootloader is locked from manufacturer entirely (like Huawei)
If you can have it unlocked for £23 obviously XZ1C is unlockable, so if you can find sony leaked prog_ufs_firehose_8998_ddr.elf I would give it a try at least. Björn Kerler is a leading reverse engineer in scene and did good job to oppo rooting.
(you can check /dev/block/bootdevice/by-name/* if devinfo or config exist and decide if it's worth a try)