Related
What's the best way to root my so I can use setcpu? I only want to do that and keep everything I currently have the same. Is this possible and if so how?
Believers b3ar fruit with their Nexus S.....
B3arfruit said:
What's the best way to root my so I can use setcpu? I only want to do that and keep everything I currently have the same. Is this possible and if so how?
Believers b3ar fruit with their Nexus S.....
Click to expand...
Click to collapse
CAUTION: experimental/theoretical until someone tries it on a virgin phone, but...
Shrivelfig's found a method that might let you root without unlocking your bootloader and erasing the phone.
Download these two files:
clockwork recovery
su-2.3.6.1-ef-signed.zip
Place the su zip one in your sdcard.
Place the other on your computer.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the instructions that Allgamer gives in this thread, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps from this thread:
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
Reboot.
If it works, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
Please let me know if that works; I've not seen anyone who wasn't already rooted report back on the success or failure of this method.
distortedloop said:
CAUTION: experimental/theoretical until someone tries it on a virgin phone, but...
Shrivelfig's found a method that might let you root without unlocking your bootloader and erasing the phone.
Download these two files:
clockwork recovery
su-2.3.6.1-ef-signed.zip
Place the su zip one in your sdcard.
Place the other on your computer.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the instructions that Allgamer gives in this thread, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps from this thread:
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
Reboot.
If it works, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
Please let me know if that works; I've not seen anyone who wasn't already rooted report back on the success or failure of this method.
Click to expand...
Click to collapse
If I do a full root does it delete everything that I have? I have never tried it an I now looking Ratbags site that has a full outline on how to do it. All I want to do is use setcpu without deleting my stuff
Believers b3ar fruit with their Nexus S.....
B3arfruit said:
If I do a full root does it delete everything that I have? I have never tried it an I now looking Ratbags site that has a full outline on how to do it. All I want to do is use setcpu without deleting my stuff
Believers b3ar fruit with their Nexus S.....
Click to expand...
Click to collapse
Most of the root methods involve unlocking the bootloader with the "fastboot oem unlock" command as the first step.
That's the command that erases your phone.
Any method that has you do that command will erase your phone.
If the method above works as expected, it will root you without erasing your phone. Shrivelfig did it without harm to his phone, but he had already been rooted the old-fashioned way.
I would certainly backup my data that I could before doing any root method, but this one seems like it's 99% safe.
Use at own risk, of course, but that's true of all the methods.
OK last question what is the easiest way to backup your phone? How?
Believers b3ar fruit with their Nexus S.....
B3arfruit said:
OK last question what is the easiest way to backup your phone? How?
Believers b3ar fruit with their Nexus S.....
Click to expand...
Click to collapse
Without root, your options are limited and incomplete.
The only stuff you'll be able to backup are items that are stored on the sdcard. Some apps put their data there, some don't, some mix it up.
To backup the sdcard is as easy as usb mounting the phone and dragging/dropping the stuff you want to save.
distortedloop said:
Without root, your options are limited and incomplete.
The only stuff you'll be able to backup are items that are stored on the sdcard. Some apps put their data there, some don't, some mix it up.
To backup the sdcard is as easy as usb mounting the phone and dragging/dropping the stuff you want to save.
Click to expand...
Click to collapse
Your the man thanks bro I'll let you know if it works. Hope my phone doesn't crash on me
Man I suck I followed a lot of different direction and still can get my computer to recognize my phone when trying to root....
B3arfruit said:
Man I suck I followed a lot of different direction and still can get my computer to recognize my phone when trying to root....
Click to expand...
Click to collapse
You're putting the phone in fastboot mode? It's got the white screen?
You're using the proper commands fastboot? What message does your computer show? Are you Win, Mac, or Linux?
distortedloop said:
CAUTION: experimental/theoretical until someone tries it on a virgin phone, but...
Shrivelfig's found a method that might let you root without unlocking your bootloader and erasing the phone.
Download these two files:
clockwork recovery
su-2.3.6.1-ef-signed.zip
Place the su zip one in your sdcard.
Place the other on your computer.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the instructions that Allgamer gives in this thread, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps from this thread:
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
Reboot.
If it works, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
Please let me know if that works; I've not seen anyone who wasn't already rooted report back on the success or failure of this method.
Click to expand...
Click to collapse
Just tried it on a new Nexus S, worked perfectly
I rooted using this method last night. From start to finish, 10 minutes. I have full root capabilities.
Sent from my Nexus S using XDA App
I've been somewhat discouraged from rooting my Nexus S because of the apparent hurdles to rooting. When I rooted my Vibrant it never erased any data or stopped me from getting a firmware upgrade. Sure I lost root after upgrading, but all I had to do was run it again.
With the NS, when I hear people talk about root methods erasing their phones and preventing them from upgrading, it worries me. Sure I can back up all the data I really care about, but why should the NS have these difficulties when the Vibrant didn't?
zorak950 said:
I've been somewhat discouraged from rooting my Nexus S because of the apparent hurdles to rooting. When I rooted my Vibrant it never erased any data or stopped me from getting a firmware upgrade. Sure I lost root after upgrading, but all I had to do was run it again.
With the NS, when I hear people talk about root methods erasing their phones and preventing them from upgrading, it worries me. Sure I can back up all the data I really care about, but why should the NS have these difficulties when the Vibrant didn't?
Click to expand...
Click to collapse
Actually, you haven't been keeping up with the rooting methods. A few weeks back someone figured out how to push a recovery and install Superuser without unlocking the bootloader which is the part that wipes your phone.
The reason it is so easy to root most phones is that they use an exploit in the Android system to grant Superuser priveleges while on the Nexus S we do it the legitimate way. I've not heard of root preventing people from updating nor does it really bother me. I run custom roms and therefore wait for the updates to be integrated in my custom ROM. I'm sort of confused why someone would buy a Nexus S, a phone Google has said was designed to be hacked to pieces, and leave it stock.
kenvan19 said:
Actually, you haven't been keeping up with the rooting methods. A few weeks back someone figured out how to push a recovery and install Superuser without unlocking the bootloader which is the part that wipes your phone.
The reason it is so easy to root most phones is that they use an exploit in the Android system to grant Superuser priveleges while on the Nexus S we do it the legitimate way. I've not heard of root preventing people from updating nor does it really bother me. I run custom roms and therefore wait for the updates to be integrated in my custom ROM. I'm sort of confused why someone would buy a Nexus S, a phone Google has said was designed to be hacked to pieces, and leave it stock.
Click to expand...
Click to collapse
Because it's the fastest, cleanest, most up-to-date Android device of its class on the market. Custom ROMS are all well and good, but they're hardly the only reason to get the phone. Indeed, there are a ton of phones out there with arguably equal or better third-party ROM options at present. Anyway, to say Google designed the NS to be hacked to pieces is perhaps a bit of an overstatement; to my knowledge all they said is that they deliberately left open a way to root the phone, and even at that, it wasn't exactly a consumer marketing point.
Not that I'm badmouthing rooting, installing custom ROMS, or whatever else people do to their phones. On the contrary, I think it's fantastic. But ultimately, I object to the idea that there's a "wrong" choice when it comes to making those modifications. Different people have different priorities, concerns, and levels of comfort with various procedures, and the NS is a great phone no matter what you choose to run on it. I'm probably on the low end of the spectrum with respect to my interest and comfort in modding as far as people who post with any regularity on these forums go, but bear in mind I'm also probably a great deal more engaged with it than the majority of users, many of which may not even make full use of their phone's basic features, let alone think to try making their phone do anything that the top-layer UI doesn't facilitate.
Clockwork link not working
suhas_sm said:
Clockwork link not working
Click to expand...
Click to collapse
Try this one: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.5-crespo.img
or go straight to koush's blog: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
worked for me as well, on 2.3.2 without erasing anything.
thanks!
I concurr, the nowipe method works here (UK SNS fro Carphone Warehouse on 2.3.2).
All we need now is google to fix the issues (rebooting in particular).
Hey, thanks ... if this works without unlocking the bootloader, I'm trying it
Two things before that though:
a) Please let us know if you can update to 2.3.3 after this or if you have to wait for a new image.
b) Can I rewind and get my phone back to the unrooted version as it was when I bought it? If yes, can someone write the steps for that too?
Thanks
Paparasee said:
Hey, thanks ... if this works without unlocking the bootloader, I'm trying it
Click to expand...
Click to collapse
It works. Try it. Full thread on it that I'll update as things change here.
Paparasee said:
Two things before that though:
a) Please let us know if you can update to 2.3.3 after this or if you have to wait for a new image.
Click to expand...
Click to collapse
We won't know for sure until the 2.3.3 update comes out and we can examine its contents and what it does. There's no reason to expect that Google will do much differently in terms of the bootloader or recovery than they have in the last two updates, especially since they've said in the Google blog that the NS was designed to be easily unlocked and rooted.
In the prior two OTA updates, you could update with no issues other than your root being broken, but it was as easy as just rebooting into clockwork and reinstalling the su update zip.
The only people who had issues updating prior OTAs after this kind of root were folks who had messed around with applications in the /system folder (such as replacing the Market or Gmail apps with some modded one). That can be worked around easily and is discussed numerous times in a couple of threads.
Paparasee said:
b) Can I rewind and get my phone back to the unrooted version as it was when I bought it? If yes, can someone write the steps for that too?
Thanks
Click to expand...
Click to collapse
All rooting with this method does is add the su binary to /system/bin, the superuser.apk file to /data/app and change permissions on /system/bin. If you install busybox (which you really need to do for root to be most effective) it will add it's own files and some symlinks.
Several easy ways to reverse the process:
Restore/flash a nandroid or stock rom image that's not rooted. (Try making one after getting into Clockwork and before flashing su-update.zip.)
Use terminal/adb, the Settings/Applications app or the Market to rm and/or uninstall the su binary, the busybox install, and the superuser.apk as well as any root-enabled apps you installed.
There's more details if you need them in another thread here or Q&A section. You should be able to find them with a search on the terms "rm /system/bin/ root".
Okay, I'll explain what I've done from getting the phone, up until now.
When I first got my N6P, I've managed to add my card (unsupported) into Pay with no problems. I was able to make NFC payments and whatnot.
Flash forward to the November security patch. I couldn't wait for the OTA, so I unlocked the bootloader, installed TWRP and did a full wipe, flashed the image (with userdata wipe), and booted into the system (bootloader still unlocked). I was still able to add my unsupported card and use it to make payments with no problems with an unlocked bootloader.
Yesterday, I decided to flash a custom ROM (install TWRP, full wipe, the whole deal). After a while, I decided to revert back to full stock. Went to TWRP, full wipe, then went and flashed the image via ADB commands. When I went to add my card again, it gave me a "Request Failed. Please verify your card information and try again."
Here's what I've done to attempt to fix it:
1. Went to payments.google.com, removed the card from there, re-add it from there, then add it on Pay. Nothing
2. Flashed the image again, then locked the bootloader. Nothing
3. Tried three other cards (unsupported). Nothing
I'm guessing that there are three possibilities:
1. Problem on Google's end
2. Custom ROM might've tripped something (qFuse hasn't been tripped)
3. I can't grandfather my cards onto Pay any more.
Any solutions or explanations would be greatly appreciated
Android Pay does not work with root or with custom roms even if it is not rooted for security reasons.
unixasaurusrex said:
Android Pay does not work with root or with custom roms even if it is not rooted for security reasons.
Click to expand...
Click to collapse
I know, but I went back to stock via factory image straight from Google.
ak47nerd said:
I know, but I went back to stock via factory image straight from Google.
Click to expand...
Click to collapse
Have you checked that SE Linux is enforcing?
unixasaurusrex said:
Have you checked that SE Linux is enforcing?
Click to expand...
Click to collapse
Well, I did a full wipe on TWRP, then installed the factory image again. I went to add my card, and now it isn't supported any more.
I'm guessing that I can't grandfather my old cards again.
ak47nerd said:
I know, but I went back to stock via factory image straight from Google.
Click to expand...
Click to collapse
ak47nerd said:
Well, I did a full wipe on TWRP, then installed the factory image again. I went to add my card, and now it isn't supported any more.
I'm guessing that I can't grandfather my old cards again.
Click to expand...
Click to collapse
That's odd I have added my card many times. Make sure SE is enforcing, other than that I don't know what to tell you im out of knowledge on this. Sorry.
This guide is for those of us that have devices that have been updated to the new bootloader 4 firmware which prevents downgrading to a firmware compatable with most sim unlocking tools. Firmware versions that suffer this include PH7, PJ2 or PK1 for s7 and s7e (s7e=edge for purpose of this guide, s7=g930x, s7e=g935x).
This method was used personally and tested using a sprint s7 g930p on PJ2 firmware. Your mileage may vary
This involves rooting and will trip warranty status flag. If you have another rooting method different from this thread that wont void warranty or trip KNOX please use that instead.
After this guide you can use a unlocking method of your choice a few that work will be outlined later and also a few to avoid. I also recommend having a copy of your stock rom in case anything goes wrong.
Part A: Setup
1.) Download Root_S7.zip from the bottom of this post, extract the files so that you have the folder Root_S7 with files inside it.
Copy this folder to the root of your phones internal storage and leave a copy on your PC also so you can run(double click) Root_S7.bat in the later step.
2.) Download and setup Package Disabler and use it to disable the following: (should be about 5 apps total. This step not 100 percent necessary but I found it made things easier)
Anything that says Knox
Anything DM (all of them)
SecurityLogAgent
3.) Go to Settings>About Device> and tap "Build Number" 7 times to enable "Developer Menu" then enable "USB Debugging" and "OEM unlock" in the Developer Menu.
4.) Power off the phone completely, now hold Home and Volume-(down), keep them pressed and power the phone on.
5.) Press Volume+(up) when prompted to enter "Downloading Mode"
6.) Connect USB and wait for all drivers to finish installing on PC.
7.) Download SM-G930x_Engineering_BOOT.tar.md5 or SM-G935x_Engineering_BOOT.tar.md5 (choose correct file for S7 or S7e).
8.) Open Odin3 (Run as administrator), then select the above file in "AP" slot, then press START on Odin3, the file will be flashed.
9.) keep phone connected to PC as soon as the system identifies the device Double click "Root_S7.bat that is inside Root_S7 folder that you extracted on your PC. After the phone reboots automatically it is rooted. (it may take a couple tries due to the phone bootlooping, once successful SuperSU will be installed)
10.) Open SuperSU app and go to its settings>Access> and change it from "Prompt" to "Grant". After you have changed this setting the phone should only reboot 1 more time.
11.) Proceed to unlocking
NOTE: If SuperSU prompts "update su binary" you need to run the Root_S7.bat again, and/also check that you have copied Root_S7 folder with exact same name and location as the picture below. Do not use the SuperSU from playstore use the one included in the zip.
You can now unlock using idoneapps or you can PM grsjohn.
After unlock I suggest reflashing stock rom to remove root and restore functionality.
Part B: If you decide to pm Mr. grsjohn.
1.) On a windows machine download and install TeamViewer 11 and Usb redirector
2.)In Teamviewer click extras>options>advanced>show advanced>install VPN driver (its close to the bottom)
3.)Contact Mr. grsjohn. Prepare to donate because Mr. grsjohn is awesome and is doing this with his own resources and free time. :fingers-crossed:
Thanks to and beers for
colormedroid For Root Thread here.
grsjohn for sim unlocking. :highfive: And gets my endorsement.
idoneapps for guide and root zip here.
Note: I Bulletbeef am in no way associated with idoneapps.com or any other entity. I was in the situation that this guide addresses and thought it a nice thing if everyone could have the information consolidated and in an easy to follow guide. I WILL NOT BE HELD RESPONSIBLE FOR PHONE BRICKS, LIMBS STUCK IN TOASTERS OR THE DELAY OF HALF LIFE 3.
Downloads: (Mirrors welcomed)
Mega
Useful Links
Useful links will be posted here:
Samsung Galaxy S7 (SM-G930P) Root & Xposed Framework install Without Voiding Warranty
SM-G930P Root - Updated 10/25/2016
Unlocking methods and services suggestions.
Unlocking suggestions will go here:
Unlockbase Cable - Confirmed works up to bootloader 3 on s7, great refund policy.
idoneapps - Should work
Sammobile - should work on bootloader 4 with root, great refund policy.
s7 tmobile not supported ..
This process doesn’t always work first time.
grsjohn said:
T-mobile phones usually have unlock app, this models can be unlocked by code wity this app, only if phone is eligible for unlock
Click to expand...
Click to collapse
if it is not eligible then how to unlock..?
grsjohn said:
T-mobile phones usually have unlock app, this models can be unlocked by code wity this app, only if phone is eligible for unlock
Click to expand...
Click to collapse
If I load some other carriers firmware will it be possible?
grsjohn said:
bad idea, on t-mobile phones you must flash only firmwares made for it
Click to expand...
Click to collapse
right now i m have u firmware
Will this unlock a straight talk s7, I think firmware is ph4?
Help me
I have SM-G930T and even with the unlocking password I got from the simdoctor site, I can not unlock. Can someone help me?
tmobile need to be unlocked via app..!!
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
diegosantospt said:
I have SM-G930T and even with the unlocking password I got from the simdoctor site, I can not unlock. Can someone help me?
Click to expand...
Click to collapse
tmobile need to be unlocked via app..!!
Will this method work for Sprint locked SM-G935P?
Please someone get back to me asap
Anyone try it to get a free unlock codefrom askunlock.net....is not exactly free, is a win win situation, but I dont know what to say...
hi.
I have galaxy S7 locked to unknown canadian network.
can i use this guide to unlock it ?
Bump
daveyaz said:
hi.
I have galaxy S7 locked to unknown canadian network.
can i use this guide to unlock it ?
Click to expand...
Click to collapse
Any idea [email protected]#$#@!
hello, iam owner of SG7 (SM-G930F), i followed the steps described above and my phone now is dead, i can't enter into download mode (odin Mode) it only display the
message "Exception: do_handler_sync: UNKNOWN (0x2000000) pc: 0x88144000 Ir: 0x8f0009318 sp: 0x0f10ff50".
justhyno_ said:
hello, iam owner of SG7 (SM-G930F), i followed the steps described above and my phone now is dead, i can't enter into download mode (odin Mode) it only display the
message "Exception: do_handler_sync: UNKNOWN (0x2000000) pc: 0x88144000 Ir: 0x8f0009318 sp: 0x0f10ff50".
Click to expand...
Click to collapse
i fixed my trouble using an older odin.
I have use SM-G935x_Engineering_BOOT.tar.md5 this file ,after reboot it will none stop to reboot
what should I do?
i use G935V
930AZ running 930U (ATT), sent my phone into bootloop.
Mr William
Hi i have a Samsung S7 edge and when i phone out it said that you not register on network had replace the sim and did factory reset and update and clear cashme but still the same had use the phone for 6 months and when i woke up and want to phone i got that???
I bought a used Essential (love it!). It came with the bootloader unlocked, so every reboot I get the "your device software can't be checked for corruption. Please lock the bootloader."
I am not really concerned about that (should I be?), but when I try to set up Google Pay I get this:
"Couldn't finish setup to pay in stores. This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
I'm not sure that the Pay issue is because of the unlocked bootloader, but I don't need it rooted/unlocked, so I might as well re-lock to eliminate it as an issue.
There's a lot of info on the forums about *not* relocking when you have a custom rom, but I'm pure Pie.
So - is there a straightforward way to relock? I have things backed up/etc.
back to official rom, before that
First of all make sure you are pure stock
Then boot into fastboot by holding vol- and power button together.
Download android platform tools https:REMOVEME//developer.android.com/studio/releases/platform-tools?hl=th, unzip it, go into the folder, open cmd there, and type
Code:
fastboot flashing lock
And it's finished!
r_w said:
I bought a used Essential (love it!). It came with the bootloader unlocked, so every reboot I get the "your device software can't be checked for corruption. Please lock the bootloader."
I am not really concerned about that (should I be?), but when I try to set up Google Pay I get this:
"Couldn't finish setup to pay in stores. This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
I'm not sure that the Pay issue is because of the unlocked bootloader, but I don't need it rooted/unlocked, so I might as well re-lock to eliminate it as an issue.
There's a lot of info on the forums about *not* relocking when you have a custom rom, but I'm pure Pie.
So - is there a straightforward way to relock? I have things backed up/etc.
Click to expand...
Click to collapse
Look at the other threads about rooting.
You can do a couple of things to solve the issue:
Install ElementalX kernel
Install Magisk
VoidWalkerAlpha said:
First of all make sure you are pure stock
Then boot into fastboot by holding vol- and power button together.
Download android platform tools https:REMOVEME//developer.android.com/studio/releases/platform-tools?hl=th, unzip it, go into the folder, open cmd there, and type
Code:
fastboot flashing lock
And it's finished!
Click to expand...
Click to collapse
Perfect! Flashed the latest original from Essential per HapRow's comment, pulling from Essentials current build website.
Had to wait a long time to restore everything. Then the "fastboot flashing lock" erases everything, so I had to restore again.
Took a while, but was thankfully uneventful.
And now Google Pay works!
Thank!
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?