Related
Hi everyone,
I'm new to "rooting" android devices, although I have jailbroken all my iPhones and "rooted" my palm pre.
As a newbie, it seems the "root toolkit" is the best way to do this? Is this Windows only, or is there a Mac version?
anything else I should read up on / know before rooting? I basically want to root, initially at least, to get sixaxis support and stickmount working.
Thank you all for your help in advance.
First of all, this is the wrong section. You should post inquiries in the q/a section.
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Sent from my Nexus 7
Take a peek at the nexus root toolkit thread in this forum...quick and easy.
Sent from my Nexus 7 using xda app-developers app
The tool kit is windows only, correct?
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
I would agree with:
evonc said:
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Click to expand...
Click to collapse
Then you know what is happening, and how it works... so if you run into troubles later, you know what to do.
Hard to brick this device.
Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
Click to expand...
Click to collapse
For practice, and maybe the one-click solution is not flexible enough for your means. It's usually dependent on the developer to update it, so do check if it has any limitations.
Also, the ones I've seen are Windows only.
Foxman2k said:
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
As long as you don't mess up the bootloader, it should be possible to reflash stuff via recovery or fastboot. Bear in mind there have been exceptions (though that came about because of a serious kernel bug, rather than due to user error) so this can't be a guarantee.
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
spdecoste said:
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
Click to expand...
Click to collapse
Another recommendation for WUGS rootkit - literally very easy foolproof step by step menus/instructions - only prob I had were the drivers - just manually pointing to driver directory sorted this out.
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
This seems to rely on Windows. Any Mac tools available?
Foxman2k said:
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
Click to expand...
Click to collapse
Unlocking the bootloader allows you to mess with the bootloaders progression at startup, which gives you the ability to install a custom recovery and gives us the method to gain root access. The bootloader can be unlocked by many different methods - some manual and some "one-click". I'd suggest doing it the manual way first, so you understand the process, and are able to fix it manually if anything goes wrong.
To my understanding, it's locked so that people who don't know what they're doing can't mess the device up. It's a safety procedure basically.
To relock the bootloader, you just type (I only know how to do this in windows - Linux and Mac work as well al beit differently)
Code:
fastboot oem lock
and you're all set.
Foxman2k said:
This seems to rely on Windows. Any Mac tools available?
Click to expand...
Click to collapse
The Android SDK and ADB tools are equally available on Linux and Mac. You won't have to do the "Adding to Path" thing. All of the ADB commands will be the same, though.
I didn't know anything about rooting at all too, despite having an android phone for more than 2 years.
I went with the one-click root process.
Download this file, plug your Nexus 7, follow the instructions- which means typing Y, N, Y etc
Done in 5 minutes. There's a youtube video on it too. Go check it out.
I still dont know much about the process.. except I'm unlocked and rooted =)
I have a few naive questions
Do I have to do the OEM unlock to root the device? I would prefer not to wipe it.
Assuming I don't hard brick the device, can I go back to stock for warranty work?
Does rooting the device mean I can't get OTA updates from Google? For now I just want to run the stock kernel/rom and get updates. I just want root to run titanium and certain other apps that require root.
I've seen a thread that suggest that the play store (market) doesn't work on rooted devices. Is that true?
It's done. After almost 2 hours, 3 factory resets, a great deal of anxiety, fears that I'd be stuck with a locked phone that I just upgraded to, and a general desire to repeatedly beat my head against the wall to make it all go away, I finally have my bootloader unlocked.
At first I tried Mofo, but the verify app said my phone was incompatible. I guess Mofo doesn't work with the latest OTA. Oh well, I guessed it saved me a bit of dough, though if I knew I was going to have so many problems with Kingroot, I wouldn't have been celebrating yet.
Kingroot. I just don't trust this app, but it's a necessary evil. Because Kingroot relies on an internet connection to work, a person has absolutely no way of knowing if sensitive data is being sent to lord-knows-where, especially considering the app is headquartered in China. I'm wondering if the "free" part of it isn't just bait. Since the app grants root privileges, there's no way of telling what it's doing in the background. The app is also a pain in the arse. At first it worked, or at least it said it did. Then I decided to to follow a guide I came across (I can't remember the exact guide, so don't ask) to replace Kingroot with SuperSU. This might have been where all my problems started, but I can't be sure. Suddenly, a barrage of FCs. Powered off, rebooted, same thing. Settings FC'ed so no way to uninstall except for the launcher, which was also FCing. The only way was to reboot and uninstall before Kingroot auto launched. Finally, back to square 1, or so I thought.
Just to cover my bases, I did a factory wipe, and started over. I didn't set up anything on the phone, just skipped everything in the wizard. Then I downloaded Kingroot and Sunshine. Installed Kingroot, it didn't work. Tried again several times, rebooted, tried again, no luck. Factory reset again. Repeat. Same results. I once managed to get it working, but by the time I tried to install Sunshine, I got a system error that there wasn't enough space. Strange, since I was coming from a factory wipe.
So it was time to start over. This time, however, the phone became so unstable after running Kingroot that the phone was absolutely unusable. I couldn't get into the settings to do a factory reset. I couldn't get into the launcher or the settings to uninstall Kingroot. I felt absolutely hopeless. I literally felt like I was going to vomit. I thought I had possibly bricked my new phone delivered less than 2 hours ago by FedEx. Then I remembered, "Hey, dumbass, you can do a factory reset through fastboot.
Just in case anyone is curious, the exact fastboot commands are:
./fastboot erase userdata
./fastboot erase cache
(Winblows users, omit the ./)
Powered up the phone, in the setup wizard I got a message that the phone had been reset, which didn't appear the previous 2 times I had factory reset the phone. Very interesting. Skipped through the rest of the steps, opened Chrome, downloaded Sunshine and Kingroot. Wouldn't you know it, the first time I ran Kingroot after that reset using fastboot, it worked! Fingers crossed, I ran Sunshine. Same thing!
My theory is that Kingroot must have preserved files in the cache, which leads me to believe that the app truly isn't trustworthy. Anyhow, now that I'm unlocked, TWRP is installed, and I've got a stock backup of the system partition, it's time to flash SuperSU.
The lesson learned: if you're having problems getting root with Kingroot in order to unlock via Sunshine, you might have to do a hard reset through fastboot. Additionally, I would recommend wiping the data and cache partitions after getting unlocked, just to be sure Kingroot isn't leaving any residual files lurking around and doing lord-knows-what on your phone.
Huge thanks to @jcase for Sunshine, and feigned thanks to Kingroot, after all, I couldn't have done it without them. No thanks, however, for the 2 hour nightmare.
I don't get why so many are having issues I unlocked my wife's turbo few weeks ago. Then today said screw it and unlocked my daughter's. Literally took 10 minutes. Had to do one reboot and try kingroot again and I was rooted. Ran sunshine and bam unlocked.
Sent from my XT1585 using XDA Premium 4 mobile app
pastorbennett said:
It's done. After almost 2 hours, 3 factory resets, a great deal of anxiety, fears that I'd be stuck with a locked phone that I just upgraded to, and a general desire to repeatedly beat my head against the wall to make it all go away, I finally have my bootloader unlocked.
At first I tried Mofo, but the verify app said my phone was incompatible. I guess Mofo doesn't work with the latest OTA. Oh well, I guessed it saved me a bit of dough, though if I knew I was going to have so many problems with Kingroot, I wouldn't have been celebrating yet.
Kingroot. I just don't trust this app, but it's a necessary evil. Because Kingroot relies on an internet connection to work, a person has absolutely no way of knowing if sensitive data is being sent to lord-knows-where, especially considering the app is headquartered in China. I'm wondering if the "free" part of it isn't just bait. Since the app grants root privileges, there's no way of telling what it's doing in the background. The app is also a pain in the arse. At first it worked, or at least it said it did. Then I decided to to follow a guide I came across (I can't remember the exact guide, so don't ask) to replace Kingroot with SuperSU. This might have been where all my problems started, but I can't be sure. Suddenly, a barrage of FCs. Powered off, rebooted, same thing. Settings FC'ed so no way to uninstall except for the launcher, which was also FCing. The only way was to reboot and uninstall before Kingroot auto launched. Finally, back to square 1, or so I thought.
Just to cover my bases, I did a factory wipe, and started over. I didn't set up anything on the phone, just skipped everything in the wizard. Then I downloaded Kingroot and Sunshine. Installed Kingroot, it didn't work. Tried again several times, rebooted, tried again, no luck. Factory reset again. Repeat. Same results. I once managed to get it working, but by the time I tried to install Sunshine, I got a system error that there wasn't enough space. Strange, since I was coming from a factory wipe.
So it was time to start over. This time, however, the phone became so unstable after running Kingroot that the phone was absolutely unusable. I couldn't get into the settings to do a factory reset. I couldn't get into the launcher or the settings to uninstall Kingroot. I felt absolutely hopeless. I literally felt like I was going to vomit. I thought I had possibly bricked my new phone delivered less than 2 hours ago by FedEx. Then I remembered, "Hey, dumbass, you can do a factory reset through fastboot.
Just in case anyone is curious, the exact fastboot commands are:
./fastboot erase userdata
./fastboot erase cache
(Winblows users, omit the ./)
Powered up the phone, in the setup wizard I got a message that the phone had been reset, which didn't appear the previous 2 times I had factory reset the phone. Very interesting. Skipped through the rest of the steps, opened Chrome, downloaded Sunshine and Kingroot. Wouldn't you know it, the first time I ran Kingroot after that reset using fastboot, it worked! Fingers crossed, I ran Sunshine. Same thing!
My theory is that Kingroot must have preserved files in the cache, which leads me to believe that the app truly isn't trustworthy. Anyhow, now that I'm unlocked, TWRP is installed, and I've got a stock backup of the system partition, it's time to flash SuperSU.
The lesson learned: if you're having problems getting root with Kingroot in order to unlock via Sunshine, you might have to do a hard reset through fastboot. Additionally, I would recommend wiping the data and cache partitions after getting unlocked, just to be sure Kingroot isn't leaving any residual files lurking around and doing lord-knows-what on your phone.
Huge thanks to @jcase for Sunshine, and feigned thanks to Kingroot, after all, I couldn't have done it without them. No thanks, however, for the 2 hour nightmare.
Click to expand...
Click to collapse
Jcase has vouched for kingroot in the past after analyzing the data that is sent to their servers. He's a professional security researcher and obviously knows his way around android security, so I trust him. I suspect that your attempt to replace kingroot with supersu is what caused the added headache and instability. Kingroot, when it works, only provides root access temporarily, and it does not disable write protection of the system partition, so attempting to write the supersu files to the system partition was probably not well-received. I'm sure you know this now, but you could have performed a factory reset by booting into recovery mode. Anyway, glad it worked!
For some reason when mine unlocked it rebooted and Kingroot decided to make itself into a /system app or is that normal behavior?
Sounds like the OP didn't read the instructions well. Being kingroot is a temp root before unlock trying to replace it with supersu before unlocking is what caused the vast majority of his problems and force closes. Simply not u derstanding instructions before doing something will always lead to problems.
I used it to get temproot, but I wouldn't trust keeping any trace of it on my system.
TheSt33v said:
Jcase has vouched for kingroot in the past after analyzing the data that is sent to their servers. He's a professional security researcher and obviously knows his way around android security, so I trust him. I suspect that your attempt to replace kingroot with supersu is what caused the added headache and instability. Kingroot, when it works, only provides root access temporarily, and it does not disable write protection of the system partition, so attempting to write the supersu files to the system partition was probably not well-received. I'm sure you know this now, but you could have performed a factory reset by booting into recovery mode. Anyway, glad it worked!
Click to expand...
Click to collapse
That's good to know. I was very hesitant to use Kingroot. Knowing that jcase has vetted it makes me feel a lot more at ease.
And you're right, my problems most likely started when I tried to switch to SuperSU. What boggles my mind is that after doing multiple factory resets, something was still incredibly screwy.
What's even stranger is that once Sunshine unlocked the bootloader, I did a factory reset once again, then flashed TWRP and SuperSU. Guess what? Kingroot was still showing in my app drawer. I tried to use Rom Toolbox to remove it, but it wouldn't. I was successful though in freezing it.
Do you help me unlock bootloader?
pastorbennett said:
What's even stranger is that once Sunshine unlocked the bootloader, I did a factory reset once again, then flashed TWRP and SuperSU. Guess what? Kingroot was still showing in my app drawer. I tried to use Rom Toolbox to remove it, but it wouldn't. I was successful though in freezing it.
Click to expand...
Click to collapse
Kingroot has to be uninstalled from the app's options menu. I learned that one the hard way when I unlocked my Turbo. However, the accompanying Purify app can be removed via the normal uninstall method.
rnwalker7 said:
Kingroot has to be uninstalled from the app's options menu. I learned that one the hard way when I unlocked my Turbo. However, the accompanying Purify app can be removed via the normal uninstall method.
Click to expand...
Click to collapse
Ahh. Thanks for that. It's been well over a year since the last time I had to go through the process of rooting, but it's worth it when I'm getting download speeds of 22Mbps when I live out in the boonies. I'm far enough outside of town that I can't even get DSL.
xuanhac87 said:
Do you help me unlock bootloader?
Click to expand...
Click to collapse
You have to be on the latest OTA.
Download and run Kingroot.
Once Kingroot says that you have root access, download and run Sunshine v3.2 beta.
You will need to cough up the $25 for Sunshine to unlock your bootloader.
And whatever you do, don't try what I did. Once you have Kingroot working, don't attempt to replace Kingroot with SuperSU.
As always, you're doing this at your own peril. If you brick your phone, there's no one to blame but yourself.
Nitefire77 said:
Sounds like the OP didn't read the instructions well. Being kingroot is a temp root before unlock trying to replace it with supersu before unlocking is what caused the vast majority of his problems and force closes. Simply not u derstanding instructions before doing something will always lead to problems.
Click to expand...
Click to collapse
It's not about not understanding instructions. I initially wasn't going to go with unlocking the bootloader because I only wanted root for the purpose of enabling tethering and being able to restore my app backups with Rom Toolbox, but I didn't want Kingroot to be that solution because I was a bit leery about using it. I had wanted to use Mofo, but my phone couldn't be verified as rootable with Mofo. Once everything went to crap with trying to replace Kingroot, that's when I said the heck with it and decided to unlock the bootloader anyway.
GreaterLesser said:
For some reason when mine unlocked it rebooted and Kingroot decided to make itself into a /system app or is that normal behavior?
Click to expand...
Click to collapse
With the exception of the experimental marshmallow method that is floating around, you cannot have root access without modifying /system, so it makes sense that kingroot would make itself a system app.
pastorbennett said:
You have to be on the latest OTA.
Download and run
Once Kingroot says that you have root access, download and run
You will need to cough up the $25 for Sunshine to unlock your bootloader.
And whatever you do, don't try what I did. Once you have Kingroot working, don't attempt to replace Kingroot with SuperSU.
As always, you're doing this at your own peril. If you brick your phone, there's no one to blame but yourself.
Click to expand...
Click to collapse
Thanks you!
But i don't have credit card to pay
Brg
Moforoot only worked on4.4.4 that's why it didn't work
pastorbennett said:
That's good to know. I was very hesitant to use Kingroot. Knowing that jcase has vetted it makes me feel a lot more at ease.
And you're right, my problems most likely started when I tried to switch to SuperSU. What boggles my mind is that after doing multiple factory resets, something was still incredibly screwy.
What's even stranger is that once Sunshine unlocked the bootloader, I did a factory reset once again, then flashed TWRP and SuperSU. Guess what? Kingroot was still showing in my app drawer. I tried to use Rom Toolbox to remove it, but it wouldn't. I was successful though in freezing it.
Click to expand...
Click to collapse
When you do a factory reset, what you're basically doing is just wiping the partition that contains data that is modifiable by the user. All that's left are the apps that are on the /system partition, which by default is not modifiable by the user. However, when you used kingroot and later supersu, both of these apps attempt to place themselves into /system so that they can control root access. It sounds like Kingroot was successful. A factory reset does nothing to /system since Motorola assumes that /system cannot be modified.
If you really want to start fresh and undo whatever damage you might have done with your previous root attempts, do the following:
1. Download the official Verizon SU4TL-44 image here: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Unzip the archive and copy all of the system image sparsechunks somewhere convenient on your computer.
3. Boot into bootloader mode and flash the first sparsechunk using the following command: fastboot flash system <name of first sparsechunk file>
4. Repeat step 3 with the other sparsechunk files until all sparsechunks have been flashed in numerical order
5. Wipe cache and userdata using fastboot as you did before.
6. Boot the phone normally.
7. Boot TWRP and flash supersu.
same here mine worked on the first try... this can easily pass as the next great horror story.
TheSt33v said:
With the exception of the experimental marshmallow method that is floating around, you cannot have root access without modifying /system, so it makes sense that kingroot would make itself a system app.
Click to expand...
Click to collapse
What's this?
Sent from my DROID Turbo using XDA Free mobile app
mrkhigh said:
What's this?
Sent from my DROID Turbo using XDA Free mobile app
Click to expand...
Click to collapse
A forum post.
TheSt33v said:
When you do a factory reset, what you're basically doing is just wiping the partition that contains data that is modifiable by the user. All that's left are the apps that are on the /system partition, which by default is not modifiable by the user. However, when you used kingroot and later supersu, both of these apps attempt to place themselves into /system so that they can control root access. It sounds like Kingroot was successful. A factory reset does nothing to /system since Motorola assumes that /system cannot be modified.
If you really want to start fresh and undo whatever damage you might have done with your previous root attempts, do the following:
1. Download the official Verizon SU4TL-44 image here: http://www.rootjunkysdl.com/getdownload.php?file=Droid Turbo/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Unzip the archive and copy all of the system image sparsechunks somewhere convenient on your computer.
3. Boot into bootloader mode and flash the first sparsechunk using the following command: fastboot flash system <name of first sparsechunk file>
4. Repeat step 3 with the other sparsechunk files until all sparsechunks have been flashed in numerical order
5. Wipe cache and userdata using fastboot as you did before.
6. Boot the phone normally.
7. Boot TWRP and flash supersu.
Click to expand...
Click to collapse
Thanks! I'm wanting as clean a system as possible, and this definitely helps!
I've used the search function and found nothing for this phone. I've used Google and found nothing about rooting this exact model.
I'm looking for the technique to root this phone and I'm finding nothing. Has anybody rooted and flashed a Custom ROM/custom recovery on this device and how did you do it?
I just got this phone as well, and I have been looking and also have found nothing for this exact variant. I have tried the usual one-click methods to no avail. Is there any development in the works? If you need a test dummy, let me know. I have several other phones to use as spares, so I am not afraid of a soft brick.
Rooting ZTE Blade a7 Prime
I too can be a test dummy to root this phone. Since Visible is such a hands off company you really need your phone to be rooted to do things for yourself. Currently for some reason my ZTE BLADE A7 Prime can’t send or receive calls and their techs are telling me 3 to 5 business days... counting yesterday and today that’s a week! Ridiculous! The APN settings look off compared to my wife’s phone but you can’t edit the settings.
ZTE Blade prime A7 Visible
I've been having the exact same problem with making and receiving calls also with losing service(for the service prob. Found great n easy solution- till find permanent one-**go to airplane mode in settings turn it on for 30secs to a minute then turn airplane mode back off TAKES SIGNAL FROM 0-4 BARS EVERYTIME AND I CAN GET/MAKE CALLS INSTANTLY ETC AGAIN ?)
Data saver seems to work for resetting connection as well. I too would be interested in rooting. I kinda like the phone, but it does have its issues.
First glance at unlocking bootloader
I just received the phone today. I was excited to see that I could get into developer mode and move the OEM Unlocking icon to allow bootloader unlock... Unfortunately, that's where the excitement ended. The typical fastboot oem unlock and fastboot flashing unlock yielded no results. I then did some research and it would seem MediaTek only implements two oem commands, and unlock is not one of them...
"The bootloader may implement additional, manufacturer-specific commands. These do not follow the usual protocol command format, and they cannot have a payload. Some manufacturers implement a lot of OEM commands, as can be seen here. MediaTek just implements two: fastboot oem p2u on and fastboot oem p2u off, these enable or disable the redirection of Linux kernel messages to the UART."
Will tinker with it some more later since I'm limited with time. Hope someone figures out how to unlock the bootloader and go from there.
Has anybody tried this?
https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
I don't own this phone (yet), so I can't give it a shot myself.
I'm not very familiar with mediatek processors in general, but that looks rather promising with some restrictions... If I have time over the weekend, I'll give that a whirl and report back whether it works or bricks my device
seems lke ts gonna be a long process before were able to fiddle with roms but im atleast glad this is close to stock android.
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
virx14 said:
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
Click to expand...
Click to collapse
Ditto here too. Couldn't get it working at first. Turned out I miss read the instructions and put all files in the init.d folder instead od the two files in the bin folder. Then your tip on using the 32bit binary got it working. Thanks.
Anybody figured out a way to change build.prop to make it stick after reboot? I am trying to enable APN editing by modifying /system/build.prop, but whenever I reboot I lose the changes.
/system and the root filesystem are mounted as a kind of RAM Disk. You would have to modify the actual image files (varies depending on partition scheme) and reflash to make things stick. Now, to my knowledge, doing so would require an unlocked bootloader, which currently is not possible with this phone.
wunderdrug said:
/system and the root filesystem are mounted as a kind of RAM Disk. You would have to modify the actual image files (varies depending on partition scheme) and reflash to make things stick. Now, to my knowledge, doing so would require an unlocked bootloader, which currently is not possible with this phone.
Click to expand...
Click to collapse
Looks like we can not add an APN even with root then? It's a bummer.
sasuke33 said:
I just received the phone today. I was excited to see that I could get into developer mode and move the OEM Unlocking icon to allow bootloader unlock... Unfortunately, that's where the excitement ended. The typical fastboot oem unlock and fastboot flashing unlock yielded no results. I then did some research and it would seem MediaTek only implements two oem commands, and unlock is not one of them...
"The bootloader may implement additional, manufacturer-specific commands. These do not follow the usual protocol command format, and they cannot have a payload. Some manufacturers implement a lot of OEM commands, as can be seen here. MediaTek just implements two: fastboot oem p2u on and fastboot oem p2u off, these enable or disable the redirection of Linux kernel messages to the UART."
Will tinker with it some more later since I'm limited with time. Hope someone figures out how to unlock the bootloader and go from there.
Click to expand...
Click to collapse
They removed the fastboot command to unlock the bootloader. I found it out by comparing the similar ZTE Blade 10 and Blade 10 Prime. The Blade 10 non-prime has the unlock command and it works whereas the prime version has the command removed but funnily enough the lock command is still there but is useless. I then looked at the bootloader for the a7 prime and same thing the unlock command is removed from the bootloader. So there isn't much hope for it unless a bypass can be found.
virx14 said:
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
Click to expand...
Click to collapse
+1 to another confirmation that the above works. Root is available, but there are limitations. I cannot install many of the modules from magisk, but this is still a great start. Thanks for the links :good:
I installed the magisk, however, it seems no root permission when I installed Titanium to remove stock apps, it never get root permission.
I was able to add new APN easily to make it work on AT&T 4G LTE data network. Are you saying any reboot of phone will make the newly added APN disappear?
ultrasoul said:
I was able to add new APN easily to make it work on AT&T 4G LTE data network. Are you saying any reboot of phone will make the newly added APN disappear?
Click to expand...
Click to collapse
I was also able to add and APN by just clicking on the "+" icon on the top-right corner of the APN configuration screen. When I inserted by MINT SIM Card (T-Mobile MVNO) there were not default populated APNs, but was able to get everything to work after adding an APN -- even after rebooting.
Big Tip: After entering the APN data and before leaving the data entry screen, make sure that you save the APN or it will not be persisted. Click on the "three dots" menu on the top-right corner and hit the Save menu item.
---------- Post added at 05:49 AM ---------- Previous post was at 05:39 AM ----------
AmazerG said:
I installed the magisk, however, it seems no root permission when I installed Titanium to remove stock apps, it never get root permission.
Click to expand...
Click to collapse
After studying the process a bit, I've come to conclude that this isn't really permanent root. All this does is the equivalent of running a script to gain temporary root after after reboot. This is done very late in the boot process, if you can even call it a part of the boot process since it's really just a user-space application auto-starting.
The modules are probably trying to be instantiated well before the root is made available through the pseudo "init.d" scripts.
It's still nice to have root access using this technique, but its usability is pretty limited. For example, I can't even get AFWall+ to start up, even if I configure it with a startup delay (hoping that it kicks in after temporary root).
So what are the odds we can make this a permanent root using a firehose file and QPST/QFIL? Similar to the Visible R2 phone?
Hi!
I've recently unlocked my bootloader as I wanted to root the phone.
However, I'm planning to sell it and want to revert it.
I've tried "fastboot oem lock", but this soft bricked my phone so I had to unlock it again.
Is it possible to relock the bootloader or at least get rid of the booting message "the bootloader is unlocked and software integrity cannot be guaranteed, etc..."...
vessk0 said:
Hi!
I've recently unlocked my bootloader as I wanted to root the phone.
However, I'm planning to sell it and want to revert it.
I've tried "fastboot oem lock", but this soft bricked my phone so I had to unlock it again.
Is it possible to relock the bootloader or at least get rid of the booting message "the bootloader is unlocked and software integrity cannot be guaranteed, etc..."...
Click to expand...
Click to collapse
Ensure that unroot first before locking the bootloader.
The command you used worked for legacy devices. New devices including the OP8 series use the 'fastboot flashing lock' command.
P.S. If you have questions, please post them under the OnePlus 8 Pro Q&A section.
Use MSM tool. This will ensure that the software is 100% clean and in a new state.
Lossyx said:
Use MSM tool. This will ensure that the software is 100% clean and in a new state.
Click to expand...
Click to collapse
+1
Lossyx said:
Use MSM tool. This will ensure that the software is 100% clean and in a new state.
Click to expand...
Click to collapse
It will, but MSM is a low-level flashing utility and thus only recommended for unbricking.
For some very odd reason, I was able to break my phone's proximity sensors after using it the second time.
I wouldn't personally advise it to be a go-to solution for something that could be easily done via a bunch of commands. Just me two cents. ✌
DJBhardwaj said:
It will, but MSM is a low-level flashing utility and thus only recommended for unbricking.
For some very odd reason, I was able to break my phone's proximity sensors after using it the second time.
I wouldn't personally advise it to be a go-to solution for something that could be easily done via a bunch of commands. Just me two cents. ✌
Click to expand...
Click to collapse
I understand what you mean. But if that's the case then you would want to advise somebody to un-root, then run the adb command to remove any and all left over magisk modules, then factory wipe, then lock the bootloader.
Personally have ran the MSM tool 3 times due to poor flashes and it's been perfect.
I think the risk is much much higher if you plan to downgrade your OS. If not then you'll be absolutely fine.
Plus it's quicker
dladz said:
I understand what you mean. But if that's the case then you would want to advise somebody to un-root, then run the adb command to remove any and all left over magisk modules, then factory wipe, then lock the bootloader.
Personally have ran the MSM tool 3 times due to poor flashes and it's been perfect.
I think the risk is much much higher if you plan to downgrade your OS. If not then you'll be absolutely fine.
Plus it's quicker
Click to expand...
Click to collapse
I did mention unrooting first. Magisk will automatically take care of the modules when that's done. But yes, if someone did forcibly mount the system (not sure if it's possible anymore with dynamic partitions) and altered it, then that requires extra care.
As for a factory wipe, that'll be done at the same time when the bootloader is locked. So, that's why I suggested just unrooting and locking the bootloader straightaway.
Anyways, the suggestions you provided are equally valid as well.
DJBhardwaj said:
I did mention unrooting first. Magisk will automatically take care of the modules when that's done. But yes, if someone did forcibly mount the system (not sure if it's possible anymore with dynamic partitions) and altered it, then that requires extra care.
As for a factory wipe, that'll be done at the same time when the bootloader is locked. So, that's why I suggested just unrooting and locking the bootloader straightaway.
Anyways, the suggestions you provided are equally valid as well.
Click to expand...
Click to collapse
No mate you're wrong there im afraid. That is not always the case
Hence the actual requirement for a magisk removal command.
Magisk does not always clear up left overs, that's a well known problem.
But hey that's my advice.
Plus the wipe before hand is to eliminate anything that may have stuck similar to magisk modules.
It can happen.
Tbhi think he'll be fine either way.
dladz said:
No mate you're wrong there im afraid. That is not always the case
Hence the actual requirement for a magisk removal command.
Magisk does not always clear up left overs, that's a well known problem.
But hey that's my advice.
Plus the wipe before hand is to eliminate anything that may have stuck similar to magisk modules.
It can happen.
Tbhi think he'll be fine either way.
Click to expand...
Click to collapse
But sometimes, it is also the module developers to blame. That's why merging the modules into the official repository is difficult.
John has strained on this often. He recently removed EdXposed from the official repo:
https://twitter.com/i/web/status/1350590699113115648
As for wiping, it's all the same if you do it just before the relock command or let the command do it for you. The same thing is gonna happen either way, so it feels redundant to perform a factory reset right before locking the bootloader. This is what I was trying to convey earlier.
And yes, agreed. He'd probably be fine, given that we have provided various points to look out for before locking the bootloader.
DJBhardwaj said:
But sometimes, it is also the module developers to blame. That's why merging the modules into the official repository is difficult.
John has strained on this often. He recently removed EdXposed from the official repo:
https://twitter.com/i/web/status/1350590699113115648
As for wiping, it's all the same if you do it just before the relock command or let the command do it for you. The same thing is gonna happen either way, so it feels redundant to perform a factory reset right before locking the bootloader. This is what I was trying to convey earlier.
And yes, agreed. He'd probably be fine, given that we have provided various points to look out for before locking the bootloader.
Click to expand...
Click to collapse
I think he'll be fine.
An yea R-ice doesn't remove properly especially if you don't remove the theme first
Got a question that I am not sure has a proper answer (and yes I know this is a sus question to begin with).
I have an old s7 and I forgot the pattern to unlock it. Developer mode is enabled but since I can't get through the lock screen I can't whitelist my PC on the phone when I connect it. I need to access my google authenticator app because I want to export it to my new phone (use to have it on my new phone but for other reasons it got wiped). I've tried using the samsung service mode code to put it into service mode from the emergency call dialer but that doesn't work. Is there anything else I might be able to try?
use droidkit or drfone screen unlock? I think dr.fone has a free trial, maybe you can screen unlock with it. Or just look for any other 3rd party free screen unlocker. They usually don't need root, nor adb.
Ive tried both but both don't support the s7. At this point I would pay for one of these apps to get into this damned thing.
Is it's bootloader unlocked?
Yes you may try with - UFED4PC_7.49.0.2.tar
This is supported to remove or read screenshot without lock data For Android & specially working on many SAMSUNG devices
AzimBahar said:
Yes you may try with - UFED4PC_7.49.0.2.tar
This is supported to remove or read screenshot without lock data For Android & specially working on many SAMSUNG devices
Click to expand...
Click to collapse
Is that something you can flash via odin or?
Did some research, looks like a full mobile forensic device suite. I don't have 2000 dollars to drop on trying to open a phone.
NO.
This is a tool which can read your phone lock
I wonder if there is a way to use Odin to flash TWRP for a single boot. It might be enough to push the ADB keyfile to the directory or to delete the sqlite keys for the pattern.
AzimBahar said:
NO.
This is a tool which can cellebrite your phone lock
Click to expand...
Click to collapse
That doesn't mean anything Cellebrite is the name of the company that produces UFED.
metalblaster said:
I wonder if there is a way to use Odin to flash TWRP for a single boot. It might be enough to push the ADB keyfile to the directory or to delete the sqlite keys for the pattern.
Click to expand...
Click to collapse
you use fastboot to boot a twrp image on a device, without actually flashing it, but im not entirely sure if you can do it with a locked bootloader. Google it i guess?
PhotonIce said:
you use fastboot to boot a twrp image on a device, without actually flashing it, but im not entirely sure if you can do it with a locked bootloader. Google it i guess?
Click to expand...
Click to collapse
I wonder if I could mount the system partition that way or not bootloader aside. Unlocking the bootloader would kill all the data too which is a no-no.
It does seem possible to flash TWRP on some devices without unlocking the bootloader. How would I go about booting from it with fastboot without flashing it if I tried it? edit: nevermind I know how to do it.
I assume I would have to use the herolte img to try to get it to work since there isn't one specifically for the sprint variant.
Well I tried but I can't seem to read the phone with fastboot. I tried Odin and it predictably threw out the flash because it wasn't properly authenticated either.
Did you install the correct drivers? You need the samsung usb drivers for odin, and some adb and fastboot drivers for adb.
PhotonIce said:
Did you install the correct drivers? You need the samsung usb drivers for odin, and some adb and fastboot drivers for adb.
Click to expand...
Click to collapse
Yeah, of course. I have the Samsung drivers and I tried working with linux and had the same issue. Feels like my only recourse at this point is to setup a kali nethunter.
You also need to manually install adb and fastboot drivers for your device, which for me is pain, but maybe it'll be easy for you.
PhotonIce said:
You also need to manually install adb and fastboot drivers for your device, which for me is pain, but maybe it'll be easy for you.
Click to expand...
Click to collapse
Yeah I have them both. For some reason though Fastboot just doesn't see the device. I tried pinging it with the linux version and its vendor id but it didn't do any good. Kind of a real pain this is becoming. I may just convert my old nexus 11 into a kali nethunter and try to brute force it.
Still haven't found a solution and now I am feeling the consequences. My Nintendo 2FA is on this damned phone. Going to try to call support and get it removed tomorrow but its a real big pain.
Metablaster,
Is there an update to this?
My wife's S8 is pattern locked, she didn't set up a Samsung account prior, and the Google Find my Phone web tool PIN option has been changed/ deleted. Maybe there's an older html version of this somewhere?
ADB keeps coming back that the device access is "unauthorized" even after reboot, so although I thought I enabled USB Debugging before giving her the phone (it used to be mine), she may have restored to factory without enabling it again.
Kali will delete all of the data like a factory reset so that defeats the purpose except to just get use of the phone at all again.
Is there anyone on here that knows of a professional grade service that can do this?
So frustrating...! Why , upon proof of ownership, can't something be done?
Please pm me, I'd want to try the MD-Next option first.
If I run the risk of losing her data than anything more intrusive probably isn't worth it.
mat68046 said:
Please pm me, I'd want to try the MD-Next option first.
If I run the risk of losing her data than anything more intrusive probably isn't worth it.
Click to expand...
Click to collapse
MetalBlaster,
I did manage to get the S8 to boot into Recovery Mode, please PM me about trying the MD-Next step via USB bridge.
mat68046 said:
MetalBlaster,
I did manage to get the S8 to boot into Recovery Mode, please PM me about trying the MD-Next step via USB bridge.
Click to expand...
Click to collapse
Have you already tried to unlock the device with a locked SIM?