Database Info

Hopes & Dreams

Is it silly to hope this update will provide a pathway to re-unlocking the boot loader?
If so, I'll update, if not, I'll hold off. *le sigh*

It has been stated over and over again that the security hole was patched. 4.4 is even more secure. People need to stop asking about unlocking, it's getting old.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
It has been stated over and over again that the security hole was patched. 4.4 is even more secure. People need to stop asking about unlocking, it's getting old.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So, thanks for your asinine, non responsive reply. The question was whether the update could provide a pathway to unlocking. I assure you I am more familiar with the situation of the boot loader than you are. Acceptable answers would include
1. Yes
2. Yes because blah blah blah
3. No
4. No because blah blah blah
It has already been debated that the update could possibly include a change to the boot loader that could be exploited. Since there are those that are more knowledgeable than me and are able to give actual answers, I shall ask you to have a good day, sir.

brownrt said:
So, thanks for your asinine, non responsive reply. The question was whether the update could provide a pathway to unlocking. I assure you I am more familiar with the situation of the boot loader than you are. Acceptable answers would include
1. Yes
2. Yes because blah blah blah
3. No
4. No because blah blah blah
It has already been debated that the update could possibly include a change to the boot loader that could be exploited. Since there are those that are more knowledgeable than me and are able to give actual answers, I shall ask you to have a good day, sir.
Click to expand...
Click to collapse
It's just because this question gets asked over and over and over again. A little bit of searching will pretty much explain how this was an exploit, not an actual path to unlocking the bootloader. Once this was patched and fixed, the hopes of finding another exploit to unlock the bootloader on a phone that was not meant to have it's bootloader unlocked, were pretty much gone. Dan, who found the exploit, had done a LOT of exploring that took a lot of time, trial and error, etc. It wasn't an easy exploit that just showed up all of a sudden. The same goes for getting root. It's not an easy thing to get. As each patch comes out for Android, more and more exploits are patched. it's just part of the business to make the OS more secure.
Going to KK, as explained in the previous posters comments, pretty much makes it possible only if pigs fly. KK is more secure than JB and as each iteration of Android comes to being, it means it becomes more and more secure, which means less exploits to find to gain root. This also means, unless they reintroduce a new exploit (highly unlikely), then don't hold your breath for an unlocked bootloader as well.

If you're more aware of the situation than I, why did you ask about it? I meant no disrespect, but it has been frustrating seeing many people come in and asking about the BL, almost a year after the OTA was released to lock it back up. If you think KK will offer you a path to unlocking, then I invite you to go through the Moto X and S5 forums and see how much trouble they're having even attaining root.

iBolski said:
It's just because this question gets asked over and over and over again. A little bit of searching will pretty much explain how this was an exploit, not an actual path to unlocking the bootloader. Once this was patched and fixed, the hopes of finding another exploit to unlock the bootloader on a phone that was not meant to have it's bootloader unlocked, were pretty much gone. Dan, who found the exploit, had done a LOT of exploring that took a lot of time, trial and error, etc. It wasn't an easy exploit that just showed up all of a sudden. The same goes for getting root. It's not an easy thing to get. As each patch comes out for Android, more and more exploits are patched. it's just part of the business to make the OS more secure.
Going to KK, as explained in the previous posters comments, pretty much makes it possible only if pigs fly. KK is more secure than JB and as each iteration of Android comes to being, it means it becomes more and more secure, which means less exploits to find to gain root. This also means, unless they reintroduce a new exploit (highly unlikely), then don't hold your breath for an unlocked bootloader as well.
Click to expand...
Click to collapse
I don't see no pigs flying.

RikRong said:
It has been stated over and over again that the security hole was patched. 4.4 is even more secure. People need to stop asking about unlocking, it's getting old.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
See how asinine you were now?

brownrt said:
See how asinine you were now?
Click to expand...
Click to collapse
just run and do it they were helping you to the best of there knowledge at the time

billycar11 said:
just run and do it they were helping you to the best of there knowledge at the time
Click to expand...
Click to collapse
Feel free to explain to me what was helpful about their replies to the OP?

brownrt said:
Feel free to explain to me what was helpful about their replies to the OP?
Click to expand...
Click to collapse
they were right at the time and now things have changed the community as a whole was just really annoyed about getting the same question so much so they were frustrated and i know users who missed out were even more frustrated with not being able to do what they want with there phones so don't take your frustration out on people who were trying to tell you the right answer at the time , take it out on your boot loader and unlock it yayayayay

brownrt said:
Feel free to explain to me what was helpful about their replies to the OP?
Click to expand...
Click to collapse
Feel free to explain to me what was helpful about your posts?

brownrt said:
I don't see no pigs flying.
Click to expand...
Click to collapse
brownrt said:
See how asinine you were now?
Click to expand...
Click to collapse
Past has shown that as old as these phones are, a new root exploit, when all others have been patched, never occurs.
What just happened was luck:
Someone was working on a root exploit not specific to this phone AND you got lucky that it worked for the RAZR HD/MAXX/M.
You got REAL lucky with Motorola basically screwing up and re-introducing the bootloader unlock exploit. This was patched with version 9.18 last year and has been unavailable since then. THIS was dumb luck, period. Well, dumb on the part of Motorola for somehow falling back to the old code that is located on a protected zone of the phone. This was the ONLY way it could have be re-introduced and this RARELY happens, so again, dumb luck.
However, there is another OTA coming (I was just emailed asking to participate in it yesterday). I'm pretty sure it will fix the Towelroot exploit (all 2013 phones running 4.4.2 as well as any 4.4.2 kernel whose date is >= 6/3/2014 disallow the Towelroot exploit) as well as the bootloader exploit.
So, now is your chance to root and unlock the bootloader and it's high time everyone takes advantage of this because we will get the same questions, over and over again when the next OTA comes out.
Our main point, as has been stated, was if people would just search and read, rather than being lazy and just asking the same question that has already been asked a hundred times before, they would find their answer a lot quicker and the rest of us who have been helping so many other people would not feel we would have to rehash the same answer again. It's like being in class, the teacher explains something, and then 10 other people raise their hand and ask the teacher about the exact thing the teacher just went over, so now the teacher has to stop class, explain it again, and then 10 more kids raise their hands and ask the same, exact question. It pollutes the forums with the same questions and then the same answers.
We weren't being mean about saying no root, but what just happened was pure luck, especially with the bootloader unlock.
BTW, I think I did see a pig fly in Minecraft yesterday, so I guess they did fly which makes sense. :laugh:
In the end, we are all very happy for those that have locked bootloaders because now, they can root and then unlock this phone. But, they need to do it NOW before the next OTA comes out. And I can guarantee you that those who fail to do it will be back on here asking the same question over and over again. So, let's spread the word and beg and plead that these people root their phones now and unlock the bootloader so that when the next OTA comes out in the next couple of weeks, they won't have to worry about another root exploit, if at all.
Again, those with locked bootloaders got real lucky.
As far as warranty goes, who cares. The phone is old (18+ months) and most people who have turned in their locked phones for warranty have gotten their replacement without having to pay anything, so the company will accept them and they don't charge for it. Besides, would you rather have an unlocked phone knowing you can have root no matter what the next OTA does or do you want to wait and have to do an exploit? Sideloading is SO much easier and just requires a reboot into a custom recovery (like TWRP) and then you do an "adb sideload" and you reboot and your done. Pretty easy, no muss, no fuss.

billycar11 said:
they were right at the time and now things have changed the community as a whole was just really annoyed about getting the same question so much so they were frustrated and i know users who missed out were even more frustrated with not being able to do what they want with there phones so don't take your frustration out on people who were trying to tell you the right answer at the time , take it out on your boot loader and unlock it yayayayay
Click to expand...
Click to collapse
Being annoyed by the question is not the same as the quest. In fact the question had not been asked before.

killrhythm09 said:
Feel free to explain to me what was helpful about your posts?
Click to expand...
Click to collapse
It wasn't a post. It was a question. Questions are not meant to help anyone but the asker. Being that I was the asker and people that had no idea about actual development decided to answer, I am in fact the best person do judge whether or not they were helpful.

iBolski said:
Past has shown that as old as these phones are, a new root exploit, when all others have been patched, never occurs.
What just happened was luck:
Someone was working on a root exploit not specific to this phone AND you got lucky that it worked for the RAZR HD/MAXX/M.
You got REAL lucky with Motorola basically screwing up and re-introducing the bootloader unlock exploit. This was patched with version 9.18 last year and has been unavailable since then. THIS was dumb luck, period. Well, dumb on the part of Motorola for somehow falling back to the old code that is located on a protected zone of the phone. This was the ONLY way it could have be re-introduced and this RARELY happens, so again, dumb luck.
However, there is another OTA coming (I was just emailed asking to participate in it yesterday). I'm pretty sure it will fix the Towelroot exploit (all 2013 phones running 4.4.2 as well as any 4.4.2 kernel whose date is >= 6/3/2014 disallow the Towelroot exploit) as well as the bootloader exploit.
So, now is your chance to root and unlock the bootloader and it's high time everyone takes advantage of this because we will get the same questions, over and over again when the next OTA comes out.
Our main point, as has been stated, was if people would just search and read, rather than being lazy and just asking the same question that has already been asked a hundred times before, they would find their answer a lot quicker and the rest of us who have been helping so many other people would not feel we would have to rehash the same answer again. It's like being in class, the teacher explains something, and then 10 other people raise their hand and ask the teacher about the exact thing the teacher just went over, so now the teacher has to stop class, explain it again, and then 10 more kids raise their hands and ask the same, exact question. It pollutes the forums with the same questions and then the same answers.
We weren't being mean about saying no root, but what just happened was pure luck, especially with the bootloader unlock.
BTW, I think I did see a pig fly in Minecraft yesterday, so I guess they did fly which makes sense. :laugh:
In the end, we are all very happy for those that have locked bootloaders because now, they can root and then unlock this phone. But, they need to do it NOW before the next OTA comes out. And I can guarantee you that those who fail to do it will be back on here asking the same question over and over again. So, let's spread the word and beg and plead that these people root their phones now and unlock the bootloader so that when the next OTA comes out in the next couple of weeks, they won't have to worry about another root exploit, if at all.
Again, those with locked bootloaders got real lucky.
As far as warranty goes, who cares. The phone is old (18+ months) and most people who have turned in their locked phones for warranty have gotten their replacement without having to pay anything, so the company will accept them and they don't charge for it. Besides, would you rather have an unlocked phone knowing you can have root no matter what the next OTA does or do you want to wait and have to do an exploit? Sideloading is SO much easier and just requires a reboot into a custom recovery (like TWRP) and then you do an "adb sideload" and you reboot and your done. Pretty easy, no muss, no fuss.
Click to expand...
Click to collapse
First off, my phone was an insurance replacement, not a **** up "oops I accidentally updated"
But I have to ask you, when you decided to answer originally, did you actual contemplate the question? Or did you assume that it was the same that had been asked before? I assure you that if you had thought about it, you would have considered the plausibility of an answer other than no. (yes and maybe being the alternatives). The post didn't ask you how to do it. And also, EXACTLY what would the OP search for to find an answer. KitKat was still in Soak Test at the time of the OP, but the all knowing non developers seemed to have the answer (this seems unacceptable). I think if the question had been pondered by the respondents they would have realized the question had not been asked before.
1. Historically, new root an boot loader exploits have been found AFTER an update has been released.
2. Historically there has not been a phone that jumped an entire cycle of updates to a new release. And that is hundreds of phones over many OSs over many iterations.
3. The idea that it was plausible should have been at the forefront of peoples minds, because the boot loader was required to be changed. There have been many posts about the nature of root being changed in kitkat. So the jump would absolutely open up risk to exploit.
4. Google wants devices to be open. Did no one think it was plausible that the exploit would be reintroduced after the hand off to Lenovo?
So I ask again, the present situation not withstanding, do you honestly think that anyone answered my question? A bunch of people tired of reading a similar question, giving the answer to a different question. As a member and contributor to the xda community for quite a while now, I've learned that it's important to actually answer the question that's actually asked and not assume the OP is not fully aware of the question they are asking. Especially if the qualify the question in the first place to differentiate it from the question he knows responders are going to assume the OP is asking. Cheers.
P.S. The idea that any of you were actually being "helpful" is cockypop.

brownrt said:
P.S. The idea that any of you were actually being "helpful" is cockypop.
Click to expand...
Click to collapse
I apologize if it came off gruff, but we have been helpful before, it just gets aggravating when it appears as if someone didn't do their due diligence in doing actual research, especially if when we've answered the same question numerous times.
In the future, I'll work at being more helpful and if it's the same question that I've already answered, maybe instead of going off, I can just wait for someone else to answer, especially if I've already typed the same answer numerous times to other people.
In any case, whether you think it's poppycock or not, we are genuinely happy for everyone that has now had a second chance at unlocking the bootloader with this "mistake" from Motorola. I just hope everyone takes advantage of it.

^^^I won't apologize for appearing "gruff."
brownrt said:
See how asinine you were now?
Click to expand...
Click to collapse
I don't feel asinine, in the least bit. What happened was pure, dumb luck (or someone at Moto "accidentally" putting the TZ back into the KK update). You all also got lucky when someone decided to try out Motopocalypse just for the hell of it. At the time, there was no "path" to the unlock and every experienced dev (I'm no dev) was under the notion this would never happen. Thanks for bringing this up, I always enjoy a good discussion. I was wrong, the devs were wrong, the experts were wrong.

ill just leave this here
im not getting involved in this bickering, ill just say this:
-it took Dan (a security expert by trade) a long time to find the BL unlock. so when he says "it will never happen again", i tend to belive him. therefore "the never going to happen" post by others.
-i highly doubt moto forgot on purpose to apply the known exploit patches, or let us have it back on purpose, so someone over there is probably fired right about now.
-had geohot not found a blanket root, something that is quite rare, there still would be no root as no one is actively trying.
so, however it may have not been worded in the best manner, the assumptions at the time of the op were accurate.
that will be all, as you were....

Does Developer support exist for Huawei Phones? In particular the Mate 7.

I know the phone is barely released, but what is the likelihood of seeing a root tool and a base AOSP Android L rom when it releases? In general do Huawei phones even see developer support on XDA or any other forums?
I really want the Mate 7, but only if i'll be able to get vanilla Android L running on it in the near future. I searched the Huawei forums and it doesn't look very promising. I was wondering since this is a pretty big departure from what Huawei usually releases, if it changes anything.

I am very tempted to get this device too, but only if it can be tinkered with.
I would love to get this running stock android L

bboylito said:
I know the phone is barely released, but what is the likelihood of seeing a root tool and a base AOSP Android L rom when it releases? In general do Huawei phones even see developer support on XDA or any other forums?
I really want the Mate 7, but only if i'll be able to get vanilla Android L running on it in the near future. I searched the Huawei forums and it doesn't look very promising. I was wondering since this is a pretty big departure from what Huawei usually releases, if it changes anything.
Click to expand...
Click to collapse
Usually when there is very little developer interest in a device we have end up getting a bounty going. I started a bounty for root for the Galaxy Mega last year and it ended up working.

Techngro said:
Usually when there is very little developer interest in a device we have end up getting a bounty going. I started a bounty for root for the Galaxy Mega last year and it ended up working.
Click to expand...
Click to collapse
Root and recovery is out.
http://pan.baidu.com/s/1pJ2qx3l password is fuwq
To prep phone : http://cn.club.vmall.com/thread-1241100-1-1.html do this. Google translate the page.
viola root. Caveat is only from a PC... no mac support. Cannot personally verify, but reading comments translated in multiple threads seems successful. Will have to manually save and update phone to upgrade as updates come out via this method. Wish it were a simple as other chinese roms, like miui or flyme.

gn0s1s said:
Root and recovery is out.
http://pan.baidu.com/s/1pJ2qx3l password is fuwq
To prep phone : http://cn.club.vmall.com/thread-1241100-1-1.html do this. Google translate the page.
viola root. Caveat is only from a PC... no mac support. Cannot personally verify, but reading comments translated in multiple threads seems successful. Will have to manually save and update phone to upgrade as updates come out via this method. Wish it were a simple as other chinese roms, like miui or flyme.
Click to expand...
Click to collapse
So does this mean you can have stock android? Sorry Im new to android. Looking at making this my first device.

10pmStalker said:
So does this mean you can have stock android? Sorry Im new to android. Looking at making this my first device.
Click to expand...
Click to collapse
Yes, technically that means you can install various ROMs or recoveries on your device, but you'll have to wait until someone actually makes some for the device. Judging by the other Huawei devices on XDA, there doesn't seem like there will be very much development for this device either. That's why I suggested a bounty. I've had Android phones where there was not much development (T-Mobile Galaxy Note, Moto Cliq). It sucked watching other devices get all the attention. Now the AM7 may be just popular enough to get some attention from devs, but ultimately, I am preparing myself for the possibility that development for the AM7 will be very slow, just so I won't be dissapointed.
But I may be wrong.

How do bounty's work? Paypal? How do you know if the Dev is even qualified or going to complete the work once the bounty is paid? I'd be willing to throw in a few bucks.

bboylito said:
How do bounty's work? Paypal? How do you know if the Dev is even qualified or going to complete the work once the bounty is paid? I'd be willing to throw in a few bucks.
Click to expand...
Click to collapse
The person who creates the bounty sets the goal (root, recovery, ROM, AOSP, etc.) that will satisfy the bounty. People pledge an amount of their choosing. Once the goal is completed and verified (by making it available to test), then the money is collected via Paypal and given to the first person to reach the goal.
Here's a good example of what a bounty thread looks like: http://forum.xda-developers.com/showthread.php?t=2728051
(Don't expect our bounty to get that expensive lol.)

Hopefully if root works and we can get the device tree sorted then its all good. Be interesting to see if kernel sources will be released

Tab E T560nu/LineageOS/NetHunter

this is the first device I've had success modding, and i was blown away when i was able to install NetHunter as well I started this crazy business about a year and a half ago when i got an S6 for my wife and an S6 Edge+ for my daughter, needless to say I was not successful modding those devices I was almost discouraged to the point that i was going to pursue a different hobby when i came across some dude selling a samsung Tab E (probably hot) that was locked, and, go figure, the dude didn't have the password. i gave him $50 and decided to give it a go.
as the process dragged on i realized, and no offense to the almighty devs, that i needed to stop adhering to all the "rules". it's quoted like scripture here that one should NEVER try to flash components that don't match... lol
https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/
https://forum.xda-developers.com/showthread.php?t=3534545
https://github.com/jcadduono/lazyflasher
https://github.com/offensive-security/kali-nethunter/tree/master/nethunter-installer
https://build.nethunter.com/
HAVE FUN!!
no great mind has ever existed without a touch of madness - Aristotle

Curiosity
First off I have to say the first link is likely a phishing link. It pops up some reward for 5 billionth search and if you back out wrong another rewards page pops up. Mods please remove the link for security issues.
Second the github nethunter installer is no longer a valid repository.
Ok I'm really curious about putting nethunter on this device. I've had it rooted since I bought it. Twrp on it with a stock rom (oreo) but far outdated security updates. I see in this post I can throw lineage os on it which I never knew was possible before seeing this post. I couldnt find any custom roms. I'm going to flash that reguardless. I did several times in this device flash different versions of this stock rom and never had a problem. Atm I've got a nook device haha. So I know this device is versatile with or without the patching link.
The only place I can find nethunter is on kali site. But obviously this device is not on their page for downloads. I see theyve got a couple different generic android kernel downloads but I'm unsure of they will setup correctly. I cant see any assuring information that I wont damage the device flashing. I can deal with any brick, I just dont want to damage any chip.
This person really didnt layout how he went about it and just posted some useful links of repositories or tools. I really want nethunter and being I cant have it on my newer bootloader locked samsungs, and I dont have the funds for the one plus 7 pro atm, I'm hoping someone can assist me or give me a little more information on how to get nethunter. I have several kali builds on pc and laptops and VMS dating back to 2015 but as far as a useful handheld os I dont have and am unfamiliar with, yet i want it sooo bad. Thanks

ACT now for bootloader unlock | Official Whatsapp and Telegram groups Realme1

Hello folks,
So i've recently bought realmeone recently primarily due to its hardware. Am not a big fan of color os tbh and in my limited research found some stuff from the internet
First, the bad bit :
Realme1's twin brother oppo F7 still has no way of unlocking bootloader.
Oppo seems to have disabled (deleted?) fastboot binaries.
Expecting GPL compliance from mediatek SOC is asking a bit too much.
Now the good bit :
Realme1 is project treble ready.
We've had examples treble doing wonders for even obscure mediatek devices like this one.
Root and twrp and custom roms are only possible once we have a working way to unlock the phone. And with the issues like messed up multi tasking atleast on the 3gb variant (which i have by the way) it becomes all the more important to have a good custom rom scene to fall back to if color os becomes too unbearable.
I'd assume anyone whose come looking for realmone here on xda, like me, would want to see some dev support for this awesome device. So I am hoping all you folks would take some time and mail oppo at [email protected] asking to make the device's boot loader unlockable.
For those of us who are laziest here's a draft that you can copy paste but i urge people who have time to make their own mail body so that every mail wont look same
Dear oppo,
First of all, as a user of realmeone, thanks for this great value for money smartphone. Many of us power users in the realmeone community would love to have the option to unlock the boot loader so as to be able to root the device. Rooting is essential to some of us who've been used to some nifty root tools like system wide ad blocker etc. We hope oppo will help us exploit full potential of its hardware by allowing boot loader unlock at the earliest.
Thanks
Click to expand...
Click to collapse
We've also have whatsapp and telegram group for realme1 running to better co ordinate these things and help each other out, find links below:
PS : If anyone knows any other mail id to contact them, feel free to point out I'll add that too here.

Done, email sent! Though I've just ordered my phone and yet to receive it. :laugh:

We can backup and flash images using miracle box. I mean I haven't personally tried because I don't have miracle box but have seen in the forums that ppl are backing up invidiual images n flashing the firmware back into the device.
I don't know how miracle box works but if some genius can help us then maybe we can make some easy fastboot/sp Tools based tools to flash images..
I'm talking about Oppo f7..

I've already mailed and got response that there's no way I can unlock bootloader and they also told me that it voids warranty and crap so they don't provide that. Regarding kernel sources, they simply ignored it.
I'm going to return the phone back to Amazon. No wonder why XDA opened a forum for OPPO phones which is not developer friendly.

1manshow said:
Done, email sent! Though I've just ordered my phone and yet to receive it. :laugh:
Click to expand...
Click to collapse
Sorry but had to cancel the order due to stubborn policy of Oppo not allowing bootloader unlock and fastboot binaries. There won't be any development for this phone despite being such a good phone. Heck, I need root for few of my favorite apps and thus can't miss them due to this stupid policy by OEM. No thanks, will wait for Mi A2 or buy Asus zenfone max pro

I think we can plead them through change.org

1manshow said:
Sorry but had to cancel the order due to stubborn policy of Oppo not allowing bootloader unlock and fastboot binaries. There won't be any development for this phone despite being such a good phone. Heck, I need root for few of my favorite apps and thus can't miss them due to this stupid policy by OEM. No thanks, will wait for Mi A2 or buy Asus zenfone max pro
Click to expand...
Click to collapse
Asus Zenfone Max Pro M1 having Resurrection Remix OFFICIAL already

mail sent

Finally Amazon agreed to take away the phone. Today the guy took the phone back and hopefully the refund will be processed soon. Screw you OPPO for your ****ty policies. I shouldn't have bought your phone at first place. No bootloader unlock=go to hell.
Now, search for another phone begins.

Daruwalla said:
Finally Amazon agreed to take away the phone. Today the guy took the phone back and hopefully the refund will be processed soon. Screw you OPPO for your ****ty policies. I shouldn't have bought your phone at first place. No bootloader unlock=go to hell.
Now, search for another phone begins.
Click to expand...
Click to collapse
On what ground did you returned the phone to Amazon? I am planning to return. Just wanted to confirm......

apat26 said:
On what ground did you returned the phone to Amazon? I am planning to return. Just wanted to confirm......
Click to expand...
Click to collapse
I just chatted with cc and told him the phone has ram management issues and ask him to check the reviews, everyone is complaining about it. He asked if I need a replacement or return, I politely told him to refund/return, he processed the return request.
This is the first time I ever returned something to Amazon so may be that's why the cc agreed easily. Your mileage will vary. Good luck.

Daruwalla said:
I just chatted with cc and told him the phone has ram management issues and ask him to check the reviews, everyone is complaining about it. He asked if I need a replacement or return, I politely told him to refund/return, he processed the return request.
This is the first time I ever returned something to Amazon so may be that's why the cc agreed easily. Your mileage will vary. Good luck.
Click to expand...
Click to collapse
Thanks dear. Even I will be doing so for the first time.
Lets see.

Dear Sravan,
We are glad to see your interest towards RealMe 1 and deeply regret the inconvenience caused.
As per your inquiry regarding Rooting of the device, we would like to bring to your notice that we have taken your feedback and shared the same with the relevant team so that they can look into your suggestions.
In case of any further suggestion/inquiry, you can also contact us by calling on our toll-free number 1800-102-2777 from Monday to Sunday, 0900 AM to 0700 PM or you can also reply back to us on the same email.
Regards,
Palak
RealMe Mobiles

sankarsravz said:
Dear Sravan,
We are glad to see your interest towards RealMe 1 and deeply regret the inconvenience caused.
As per your inquiry regarding Rooting of the device, we would like to bring to your notice that we have taken your feedback and shared the same with the relevant team so that they can look into your suggestions.
In case of any further suggestion/inquiry, you can also contact us by calling on our toll-free number 1800-102-2777 from Monday to Sunday, 0900 AM to 0700 PM or you can also reply back to us on the same email.
Regards,
Palak
RealMe Mobiles
Click to expand...
Click to collapse
Hi Palak,
Please count my vote in for unlocking bootloader. I'm sure the realme line up will enjoy more popularity if this happens.

Mail got replay
Their response shown below
"We understand that you want to give root access to the device and we apologize for the inconvenience caused. As per the policy, it is not suggestible to root the device. However, if you want to root the device, you can root it using any third party boot-loader on your risk. We won't be able to assist you with any information regarding the rooting of device."

nisanthu said:
Their response shown below
"We understand that you want to give root access to the device and we apologize for the inconvenience caused. As per the policy, it is not suggestible to root the device. However, if you want to root the device, you can root it using any third party boot-loader on your risk. We won't be able to assist you with any information regarding the rooting of device."
Click to expand...
Click to collapse
Which means root is possible
Third party boot-loader
Sent from my MotoG3 using XDA Labs

What third party are they even talking about? The bootloader has to be unlockable to do anything, unless they find some exploits.
Has anyone tried the oem fastboot unlock command?

A Request to RealMe Officials
Hi, The RealMe Team
This device really has got the attention of the people with it's specifications, just like how Xiaomi redmi phones did but unfortunately this Locked Bootloader thing is really making me feel as if i am using an Apple, please let the people enjoy their freedom of using an Android. Perhaps in return company will gain more customers.
Thank You.
Regards
Avneet

Has anyone tried the Kingoroot app on the phone? I know MediaTek phones can be difficult to root but I was able to root MTK6737 devices with Kingoroot. It does not unlock the bootloader or anything but it gives you root privileges.

I use Oppo F7 and it won't work on the phone...

Skyuniverse Devices Rooting Assistance Requested

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.