Related
Hi all,
After owning the TF700 for a few years I thought I would try installing a Custom ROM... I've used Android for years but never attempted this.
Anyway, I've copied the ASUS Unlock Tool (both the V7 and V8 versions) to my device and attempted to installed. The installer loads, shows me what changes will be made, then I tap Next and after a few seconds the text "app not installed" appears with the only option to select is "Done."
I've done a complete factory reset but still no use. Same error.
Any ideas?
Apologies if this has been asked and solved before. I did some searching but couldn't really find anything.
AB
Settings >Security
Allow unknown sources
You may want to read my guide in the General section... ?
berndblb said:
Settings >Security
Allow unknown sources
You may want to read my guide in the General section... ?
Click to expand...
Click to collapse
Sorry... I should have mentioned that I had already done this. I've read through the guides with no luck.
Same problem here....
ablundon said:
Sorry... I should have mentioned that I had already done this. I've read through the guides with no luck.
Click to expand...
Click to collapse
I have the same issue and have tried things. Did you ever get yours unlocked? If so, how?
Thanks!
Mystery Solved....
tmhofmann said:
I have the same issue and have tried things. Did you ever get yours unlocked? If so, how?
Thanks!
Click to expand...
Click to collapse
Looks like I solved my problem. I ran V7 of the unlock tool (for ICS) even though I am on JB. My tablet is now unlocked
Unlock T700T
I am on 4.2.1 Android Firmware version 10.6.1.14.10-20130801. I have security set to allow unknown sources and have gone through all the normal reset to factory, blah, blah... Tried version 8 of the unlocker tool. result "app not installed". Tried version 7 "app installed" reboot. Not unlocked. Or at least it doesn't show it up in the corner at shutdown or boot up. Annoying as hell. Any suggestions?
e.powell said:
I am on 4.2.1 Android Firmware version 10.6.1.14.10-20130801. I have security set to allow unknown sources and have gone through all the normal reset to factory, blah, blah... Tried version 8 of the unlocker tool. result "app not installed". Tried version 7 "app installed" reboot. Not unlocked. Or at least it doesn't show it up in the corner at shutdown or boot up. Annoying as hell. Any suggestions?
Click to expand...
Click to collapse
You have to open the app and follow the steps outlined there. Couple of confirmations that you kiss the warranty goodbye etc... THEN it will unlock it.
Did that. It goes throught the either next, next, (to scroll down) or just scroll check box. Then click install. Then shows installed. I reboot and not unlocked.
e.powell said:
Did that. It goes throught the either next, next, (to scroll down) or just scroll check box. Then click install. Then shows installed. I reboot and not unlocked.
Click to expand...
Click to collapse
No - after installing the app you have to open it like any other app from your app drawer and RUN it.
Installing it does not unlock the device. Running it does :cyclops:
After you used it to unlock you can trash it. It's done all it can do....
Did that. Just hadn't mentioned it in this post. Installed, went into apps. Scrolled through all the crap. Checked agree and press to unlock device. Says "an unknown error occurs which may be a network connection issue please wait and try again later". Made sure unknown sources was allowed in settings and it was registered on ANUS site. Yea, that misspelling was on purpose... WTF!!!!!! Got a tablet that is slow and sucks and can't do anything with it! Wish I would have never gotten rid of my Tab 2. Gonna put this POS on ebay soon.
Has anyone managed to solve this one? I just got a TF700T from woot.com and am having a HELL of a time unlocking it.
It's on 4.2.1 - V7 just seems to time out, V8 won't install in the first place.
rprussell said:
Has anyone managed to solve this one? I just got a TF700T from woot.com and am having a HELL of a time unlocking it.
It's on 4.2.1 - V7 just seems to time out, V8 won't install in the first place.
Click to expand...
Click to collapse
If you have Google's 2-step verification enabled you need to disable it or create an app specific password for the unlock app.
You could also be a victim of Google's "less secure app" feature and need to enable/disable that in your G-account.
berndblb said:
If you have Google's 2-step verification enabled you need to disable it or create an app specific password for the unlock app.
You could also be a victim of Google's "less secure app" feature and need to enable/disable that in your G-account.
Click to expand...
Click to collapse
Hah! You got me in both threads!
I did have the 2-step verification on (I couldn't figure out which bloody password it wanted!) and even with that turned off - and "less secure apps" allowed - it was still timing out.
I tried again this morning, got a message about not having a google account ONCE, I said "don't care," and it sat for a couple minutes and came back and said "Failed."
Now I'm just getting the unknown error again.
Growf.
---------- Post added at 09:05 AM ---------- Previous post was at 08:26 AM ----------
OKAY.
Persistance pays off.
Note: This is on a clean wiped tablet, on stock 4.2.1, using V7 of the tool, and no Google account installed.
I did send a support question to Asus, and they had me send in my Wifi/Bluetooth mac addresses and build info. (There was no mucking about with "we don't support unlocking..." WHEW)
That was about an hour ago - and I've been sitting here pressing the "unlock me" button over, and over, and over, and over... just in case.
Eventually I got the "You don't have a Google account installed.. unlock anyway?" and I said yes - but it would just wait a bit and say "FAILED."
After three or four successful "unlock anyway?" clicks (out of dozens of "unlock me" clicks) it finally rebooted and unlocked.
It's possible that John_Lu at asus just got my MAC info into support and they fixed me up. I dunno.
IN any case, chalk another up for the good guys. Now, off to install Zombi!
I had the same problem installing V8.
Figuring there might be an issue with the file currently posted on the Asus support site, I went looking around for a different source/repost.
I found one here: https://github.com/hackdefendr/TF700T-ADB-Tool
-seems to be for TF700T, unlock tool v8.
Since my tablet is going to be wiped soon anyways and not connecting to any other devices, the malware risk is pretty low, so I went ahead.
The file is slightly larger, 630kb instead of 600kb; and behold, this one installed fine.
I have android v 4.4 what can i use to unlock bootloader. seems i've been trying to hard but the unlock aplication from asus site says for v 4.2 or ics 4.0. so as i assumed when i tried runing the unlock app i got the app not installed message. PLS help.
psilocybinmeth3 said:
I have android v 4.4 what can i use to unlock bootloader.
Click to expand...
Click to collapse
There is no official Android 4.4 for the TF700, so either your bootloader is already unlocked or you have some other version of Android.
i apologize i wasnt specific, i have an asus memo pad 7 i have desperately been trying to root and it runs kitkat 4.4. i read i could unlock bootloader to flash custom rooted rom so this is what i was attempting but i get the application njot installed when i use the tool. Is it not really compatable with my device? if not, what is my best chance at root, as i have already tried towelroot and kingo and framaroot.
You're asking in the wrong device thread.
That aside, the JB unlock tool usually works fine on later versions. That error sounds like the common "less secure apps" problem. Read the thread, google the term.
App not installed v7
Hi I need some help. I downloaded the unlocker tool v7, ran the apk file, but it won't install....
(I have the TF700T (10.6.1.14.10), developer settings on, usb debugging on and unknown sources allowed)
I've searched around and not found people with exactly the same problem.
I don't know what to do anymore ....
Go into your Google account settings on the web and allow "less secure apps". Then the apk will install
I bought new xperia z5 dual and for some unknown reasons I am unable to find a single working thread for rootin Xperia Z5 Dual running the build 32.0.A.6.152. Please I had been an xperia user for 2 years now and I know a lot of stuff about rooting sony phones but this one is getting on my nerves now as I have many important apps that require rooting but I am unable to find any solution. Kindly help me out.
Thanks in advance
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
this worked for me and i have a E6653 instead of the usual E6603
Envious_Data said:
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
this worked for me and i have a E6653 instead of the usual E6603
Click to expand...
Click to collapse
I am following this thread before you even suggested me, but its very confusing. I have made my TA Partition Backup. Now there are few steps which are totally out of sync by the writer of this thread himself. For example.
7.Unlock your bootloader now.request keys from here.follow the guide
http://developer.sonymobile.com/unlo...r-boot-loader/
He did not even mention how to unlock the bootloader, but nontheless I found out the steps to unlock my bootloader. But there is one problem with me. When I run that fastbood unlocker command, my pc gives error. I am pasting a screenshot of that error. Kindly follow it up and suggest me the fix for it.
noob_coder said:
I am following this thread before you even suggested me, but its very confusing. I have made my TA Partition Backup. Now there are few steps which are totally out of sync by the writer of this thread himself. For example.
7.Unlock your bootloader now.request keys from here.follow the guide
http://developer.sonymobile.com/unlo...r-boot-loader/
He did not even mention how to unlock the bootloader, but nontheless I found out the steps to unlock my bootloader. But there is one problem with me. When I run that fastbood unlocker command, my pc gives error. I am pasting a screenshot of that error. Kindly follow it up and suggest me the fix for it.
Click to expand...
Click to collapse
you have to go into your developer settings of the device and click "enable oem unlock" (an odd decision to have this if you ask me)
i tried this and had to enable that open aswell for me to unlock my bootloader
Envious_Data said:
you have to go into your developer settings of the device and click "enable oem unlock" (an odd decision to have this if you ask me)
i tried this and had to enable that open aswell for me to unlock my bootloader
Click to expand...
Click to collapse
Thanks buddy. It worked like charm :good: . But you know with greater possibilities comes greater mysteries. Now since I am rooted with my phone, there are strange things happening. For example Greenify is now acting like that it doesnt have full root access even though I have allowed it through SU and it will show Greenify - No Auto Hibernation, then it mentions Pending Manual Hibernation, when I click on manual hibernation it starts to Force Stop the apps using the Apps Module of the Android OS, a thing which never happened with me on any of my rooted android phones. :silly::crying:
Second problem is that the guide which made me root the one which you also suggested me, installed TWRP recovery on my device. :crying:For some funny reasons I never liked TWRP Recoveries and wouldn't stand a chance to use it. I tried to flash XZDual Recovery, but to of no avail. Is there any workaround to remove TWRP or Flash XZDual Recovery on top of TWRP and make XZ Dual Recovery as Default Recovery.?:silly::silly:
noob_coder said:
Thanks buddy. It worked like charm :good: . But you know with greater possibilities comes greater mysteries. Now since I am rooted with my phone, there are strange things happening. For example Greenify is now acting like that it doesnt have full root access even though I have allowed it through SU and it will show Greenify - No Auto Hibernation, then it mentions Pending Manual Hibernation, when I click on manual hibernation it starts to Force Stop the apps using the Apps Module of the Android OS, a thing which never happened with me on any of my rooted android phones. :silly::crying:
Second problem is that the guide which made me root the one which you also suggested me, installed TWRP recovery on my device. :crying:For some funny reasons I never liked TWRP Recoveries and wouldn't stand a chance to use it. I tried to flash XZDual Recovery, but to of no avail. Is there any workaround to remove TWRP or Flash XZDual Recovery on top of TWRP and make XZ Dual Recovery as Default Recovery.?:silly::silly:
Click to expand...
Click to collapse
Not that I know of and given the support and useful things in twrp i'd suggest you use it although you may not like it
Reinstalling apps usually works for me half the time if they are acting odd.
Sent from my E6653 using XDA-Developers mobile app
Envious_Data said:
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
this worked for me and i have a E6653 instead of the usual E6603
Click to expand...
Click to collapse
Envious_Data said:
Not that I know of and given the support and useful things in twrp i'd suggest you use it although you may not like it
Reinstalling apps usually works for me half the time if they are acting odd.
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
Buddy I think through this tutorial either root access is not properly allowed or maybe this whole tutorial had some kind of step which made partial rooting. Strange things are happeing with some applications. For example SD MAID PRO and ROOT UNINSTALLER PRO are working with root access without any problems. But GREENIFY and now CLEAN MASTER's AUTO START UP feature (requires root access) is not working even it says CLEAN MASTER has been given root access on my device. But then it fails to toggle enable/disable STARTUP ADDS which are around 34+. Second this Greenify is not even AUTO HIBERNATING the apps which are user apps. If I run it on NON ROOT MODE it says MANUAL HIBERNATION PENDING. If I run it on ROOT MODE it says on the top "No Auto-Hibernation" and down again written "Pending Manual Hibernation".
I have tried multiple SU packages like 2.71 Beta 2.65 but same ****s going on again and again. Can you figure it out :good::fingers-crossed::fingers-crossed:
noob_coder said:
Buddy I think through this tutorial either root access is not properly allowed or maybe this whole tutorial had some kind of step which made partial rooting. Strange things are happeing with some applications. For example SD MAID PRO and ROOT UNINSTALLER PRO are working with root access without any problems. But GREENIFY and now CLEAN MASTER's AUTO START UP feature (requires root access) is not working even it says CLEAN MASTER has been given root access on my device. But then it fails to toggle enable/disable STARTUP ADDS which are around 34+. Second this Greenify is not even AUTO HIBERNATING the apps which are user apps. If I run it on NON ROOT MODE it says MANUAL HIBERNATION PENDING. If I run it on ROOT MODE it says on the top "No Auto-Hibernation" and down again written "Pending Manual Hibernation".
I have tried multiple SU packages like 2.71 Beta 2.65 but same ****s going on again and again. Can you figure it out :good::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Open the SuperSU app and check if greenify and other apps have been denied root access.
Envious_Data said:
Open the SuperSU app and check if greenify and other apps have been denied root access.
Click to expand...
Click to collapse
No way MAN. They are all allowed. I know how to check SU for Denied & Allowed Apps in its list. This is really pissing me off. Any other ideas?
noob_coder said:
No way MAN. They are all allowed. I know how to check SU for Denied & Allowed Apps in its list. This is really pissing me off. Any other ideas?
Click to expand...
Click to collapse
not sure, it doesnt make Any sense that some apps work and some dont because i followed the same tutorial and ive not had any root related issues so im out of ideas really
but first make sure that if you flash a stock kernel then use the rootkernel tool to drm patch and well obviously allow root.
Envious_Data said:
Open the SuperSU app and check if greenify and other apps have been denied root access.
Click to expand...
Click to collapse
Envious_Data said:
not sure, it doesnt make Any sense that some apps work and some dont because i followed the same tutorial and ive not had any root related issues so im out of ideas really
but first make sure that if you flash a stock kernel then use the rootkernel tool to drm patch and well obviously allow root.
Click to expand...
Click to collapse
Greenify latest version is 2.8.1 . I removed it and installed an older version 2.7.1 and it is now working automatically hibernating the unncessary apps. Now remains only CLEAN MASTER. Its working with root only I cant use toggle enabling/disabling startup adds.:silly::silly::cyclops:
Envious_Data said:
Not that I know of and given the support and useful things in twrp i'd suggest you use it although you may not like it
Reinstalling apps usually works for me half the time if they are acting odd.
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
If you are following the thread. In the android folder of the downloaded folder there are folders of twrp recovery. Replace them with your desired recovery and then make rooted kernel with rootkernel oldkernel.img newkernel.img
And then flash it
Sent from my E6633 using XDA-Developers mobile app
Does rooting void the warranty of the device? And if yes, can we get the warranty back somehow?
Yes it will surely void the warranty
You can get back only if you unroot, re flash original Rom and update via OTA
Sent from my E6633 using XDA-Developers mobile app
Rooted, bootloader unlocked, latest magisk and edxposed.
Security for a really good game is tripped and force closes randomly during play, not saving what you did.
Core only mode, no go
Magisk hide no go
Edxposed modules and blacklist, no go.
Read that Google checks if bl is unlocked now so impossible to truly hide, I think this app may also use that info.
Can I keep root and relock bl?
Better app at hiding root from other apps?
Anything I'm just not seeing?
Not good at root without twrp, so weird lol.
Any advice would be much appreciated
Idk if you've figured your problem out but I was having the same issue with a couple of games. Do like you were doing by enabling core mode, magisk hide any app on your phone that requires root, and also hide magisk manager. After all that restart your phone and you should be good to go
bobbyp1086 said:
Rooted, bootloader unlocked, latest magisk and edxposed.
Security for a really good game is tripped and force closes randomly during play, not saving what you did.
Core only mode, no go
Magisk hide no go
Edxposed modules and blacklist, no go.
Read that Google checks if bl is unlocked now so impossible to truly hide, I think this app may also use that info.
Can I keep root and relock bl?
Better app at hiding root from other apps?
Anything I'm just not seeing?
Not good at root without twrp, so weird lol.
Any advice would be much appreciated
Click to expand...
Click to collapse
Where did you get exposed module
For some reason I cannot find it for my Moto g stylus
Or how to install it.
Ljw4884 said:
Where did you get exposed module
For some reason I cannot find it for my Moto g stylus
Or how to install it.
Click to expand...
Click to collapse
It's gotten trickier, but it's been tricky ever since Lolipop; the trickiness just changes, and it JUST CHANGED AGAIN as a matter of fact... If you don't see a thread by me on how to get it going in the Guides section in the next few days, please remind me. I've got bigger fish to fry right now, though. I just got this phone and I tried Omni and Havoc so far on it. I came to see if there's a fix for the screen record issue in Havoc. I thought it said a new kernel had fixed it. Remind me and I'll probably make a YouTube video tutorial about Xposed (actually Edxposed) in Android 10 to celebrate getting my screen recording to work.
arkansawdave74 said:
It's gotten trickier, but it's been tricky ever since Lolipop; the trickiness just changes, and it JUST CHANGED AGAIN as a matter of fact... If you don't see a thread by me on how to get it going in the Guides section in the next few days, please remind me. I've got bigger fish to fry right now, though. I just got this phone and I tried Omni and Havoc so far on it. I came to see if there's a fix for the screen record issue in Havoc. I thought it said a new kernel had fixed it. Remind me and I'll probably make a YouTube video tutorial about Xposed (actually Edxposed) in Android 10 to celebrate getting my screen recording to work.
Click to expand...
Click to collapse
Please let me know when you do. I'll definitely check it out and thumbs up the video
Thank you
Ljw4884 said:
Please let me know when you do. I'll definitely check it out and thumbs up the video
Thank you
Click to expand...
Click to collapse
Have you ever used edxposed? The way you install with Magisk?
Anyone have the original build.prop ? I have everything done except CTS profile. But I think that's because I had gcam and in there it has me as pixel 2. Can flash, twrp, no screen issues, RR remix latest, going to go stock tho because CTS and my game, it's too much fun
With the pixel 4a finally arriving for some (like me), figured I'd make a quick guide
Note that unlocking your bootloader breaks safetynet. There's a workaround in this guide but no guarantee that it won't get patched out in the future.
Also note that this only works with the unlocked carrier model. Cell providers typically lock you out from this unlock process.
Unlocking Bootloader (this is for the unlocked mode, can't speak for other models)
Go to system settings -> About phone -> tap on 'Build number' several times until Developer Options is enabled
Back out into settings and go to System -> Advanced -> Developer Options -> Enabled 'OEM Unlocking'
Unplug your phone if it's plugged into anything and power it off
Boot into fastboot by holding Power + Vol Down
Plug into pc -> open terminal/shell/whatever
Type 'fastboot flashing unlock' -> Follow prompt on device to unlock bootloader (Note that this will FACTORY RESET device)
The bootloader is now unlocked!
Rooting
Grab the boot img for your rom. If it's stock, get it from the official zip
Copy the boot.img to your device
Install Magisk manager (grab it from the release zip on github - it's in the common folder)
Open Magisk Manager -> select 'Beta'
Back on the main page of Magisk Manager, Select 'Install' -> 'Select and Patch File' -> select your boot.img file -> it'll output the patched boot img to your Downloads folder
Copy the magisk_patched.img to your pc
Reboot your device back into fastboot (see Unlock section above)
Open a terminal in the directory your patched boot img file is and type 'fastboot flash boot magisk_patched.img'
You're now rooted!
Disable "Automatic System Updates" in Developer Options so you aren't surprised with an OTA on boot and end up unrooted (see the OTA section below on proper way of updating)
Passing SafetyNet
As was discovered some time ago, google is switching to a hardware attestation method for safetynet. Fortunately, at the time of writing, there is a workaround thanks to @Didgeridoohan. As of January 2021, this fix no longer works. A new module by @kdrag0n now fixes the hardware attestation issue:
Enable MagiskHide in magisk manager
Download/Install his Safetynet-fix module from this xda thread
Reboot and verify you should hopefully pass safetynet!
Taking an OTA While Rooted
Note: Installing to Inactive slot has been disabled temporarily meaning that if you take an ota, you'll need to do the patch boot img method like you did initially. See here for more details.
Note that you can download the rom from google's site here and extra the boot img from there for patching.
TopJohnWu has a great guide on how to do this here along with some nice screen shots that complement this quick guide. I'll summarize the applicable stuff here:
When an OTA is available, ignore it at first
Open Magisk Manager and go to Uninstall -> Restore Images
Now go back to Settings -> System -> Advanced -> System Update and install the OTA but DO NOT REBOOT
Once the install is done (but before rebooting), go back into Magisk Manager -> Install -> Install to Inactive Slot
Once the install is done, choose the reboot option IN MAGISK MANAGER. It works some voodoo magic to switch to updated slot and skip post-ota verifications
Having issues?
Try magisk canary instead
Note that this isn't a support thread but just a guide. You're welcome to post your tips/experiences/questions here but don't expect me to answer or reply to them.
I'll try to keep this updated with other useful guides such as TWRP when/if it is released for this device :good:
So this won't work with a Verizon pixel 4a?
Steve One said:
So this won't work with a Verizon pixel 4a?
Click to expand...
Click to collapse
Yes, the 3A's fingerprint will work for the 4A. This will satisfy SafetyNet, thus re-enable Google Pay.... For now!!!
I followed these instructions, and also enabled Magisk Hide. I'm failing both items in SafetyNet. However, I'm also running EdXposed. I'm assuming that is the reason and that there is no workaround for that?
Thank you for this guide. I only needed root to restore old app settings with Swift Backup and this worked great. I just used fastboot to boot the modified image instead of flashing it and then used that session to run Swift Backup with root. When it rebooted, all was back to stock.
neph81 said:
Thank you for this guide. I only needed root to restore old app settings with Swift Backup and this worked great. I just used fastboot to boot the modified image instead of flashing it and then used that session to run Swift Backup with root. When it rebooted, all was back to stock.
Click to expand...
Click to collapse
I would think, in this case, you'll still fail SafetyNet b/c of the unlocked bootloader. Is this the case?
digger16309 said:
I followed these instructions, and also enabled Magisk Hide. I'm failing both items in SafetyNet. However, I'm also running EdXposed. I'm assuming that is the reason and that there is no workaround for that?
Click to expand...
Click to collapse
Xposed can break safety net, I haven't tried it on this device. I have been able to pass safety net with it on some older devices though
cmstlist said:
I would think, in this case, you'll still fail SafetyNet b/c of the unlocked bootloader. Is this the case?
Click to expand...
Click to collapse
Yup but without Xposed, I was able to get safetynet to pass thanks to the module and magiskhide
cmstlist said:
I would think, in this case, you'll still fail SafetyNet b/c of the unlocked bootloader. Is this the case?
Click to expand...
Click to collapse
So, I reinstalled the magisk apk and confirmed that cts does fail. However, it does not appear to be affecting any apps. My games that normally trigger on root being available all work and Google Pay does not appear to be giving me any issues. This will bear some additional testing though anyone else goes that route.
Do I need to keep my Verizon sim card out until this is done? Is there a way to skip the initial setup so I can get to Developer Options?
it looks like there is now a pixel 4a fingerprint available in magiskhide props config
MaxPower742 said:
Is there a way to skip the initial setup so I can get to Developer Options?
Click to expand...
Click to collapse
Yes, but there are several different things you have to skip or back out of. Also, you have to have a Wi-Fi connection before it will enable the OEM unlocking setting in Developer options. You don't need to actually do any setup or enter an account or anything, though, before unlocking.
the_chrononaut said:
it looks like there is now a pixel 4a fingerprint available in magiskhide props config
Click to expand...
Click to collapse
Ya but we don't want that (we have the 4a fingerprint by default). The point of the fingerprint hack is to change the fingerprint to a device that does not use hardware attestation so magiskhide will be enough to pass safety net (like the 3a)
Zackptg5 said:
Ya but we don't want that (we have the 4a fingerprint by default). The point of the fingerprint hack is to change the fingerprint to a device that does not use hardware attestation so magiskhide will be enough to pass safety net (like the 3a)
Click to expand...
Click to collapse
Oh cool. Learn something new everyday
CSX321 said:
Yes, but there are several different things you have to skip or back out of. Also, you have to have a Wi-Fi connection before it will enable the OEM unlocking setting in Developer options. You don't need to actually do any setup or enter an account or anything, though, before unlocking.
Click to expand...
Click to collapse
Awesome thanks for your help. Got it all going including the safetynet thing. Only stumbling block so far has been it didn't seem to recognize my sim card, even waiting till it prompted me to pop it in. I just had to disable wifi and it just became my phone, didn't even ask me to activate with VZ or anything. I just did it though so I guess something could come up later where I have to go through the portal or their support to switch off my old device and turn this one on like I had to do with my last one. Maybe they improved the process though, we'll see.
Should we turn off automatic updates in dev options? I've been on roms so long I don't remember how it works with stock rooted. I imagine it'd be fine as long as it's not an android version upgrade which would not be automatic anyway.
MaxPower742 said:
Should we turn off automatic updates in dev options? I've been on roms so long I don't remember how it works with stock rooted. I imagine it'd be fine as long as it's not an android version upgrade which would not be automatic anyway.
Click to expand...
Click to collapse
I always turn it off, but I'm not sure if it's required.
Zackptg5 said:
Ya but we don't want that (we have the 4a fingerprint by default). The point of the fingerprint hack is to change the fingerprint to a device that does not use hardware attestation so magiskhide will be enough to pass safety net (like the 3a)
Click to expand...
Click to collapse
i don't think that's right there's no problem with using the pixel 4a fingerprint. personally tested. use the module to change the fingerprint and then the next option for basic key attestation. checked cts profile with magisk no problems.
Yeah I switched to the 4a fingerprint then actually did reset to default and still pass safetynet. Ampere thinks my phone is a 3a even after reinstall which is driving me ocd crazy but maybe it's just that app that needs to be updated.
MaxPower742 said:
Ampere thinks my phone is a 3a even after reinstall which is driving me ocd crazy but maybe it's just that app that needs to be updated.
Click to expand...
Click to collapse
Same thing here. I couldn't stand to look at my car showing my phone as a 3a on the screen all the time so I changed it back.
CSX321 said:
I always turn it off, but I'm not sure if it's required.
Click to expand...
Click to collapse
Turning it off is recommended if rooting
Seems like with the magisk module for props config active, it'll continue to self identify as a 3a even if you tell it to reset the fingerprint to default. I assume that's why it keeps working, cause when I disabled it, Ampere did properly see it as a 4a, but safetynet failed.
I haven't been able to disable signature verification
I root my phone before and I found out the most of the app I used doesnt work with rooted phone. I did flashed the original firmware but I am always getting an error prompt every time I restart my phone or turning my phone off. I also found out that all my banking apps doesnt work if the bootloader is open.
So, I am hoping if by any chance I can have my bootloader relocked?
phaw16 said:
I root my phone before and I found out the most of the app I used doesnt work with rooted phone. I did flashed the original firmware but I am always getting an error prompt every time I restart my phone or turning my phone off. I also found out that all my banking apps doesnt work if the bootloader is open.
So, I am hoping if by any chance I can have my bootloader relocked?
Click to expand...
Click to collapse
You can't change your mind later. Are you sure you can't use one of the safetynet fixes to use the apps?
Beyond that, I believe the locking command was never found. There was a post stating the ones for the ROG 3 didn't work, but I'm not sure if that was ever resolved.
You can make your banking apps work with magisk hide - that's an option to hide your root state for certain selected apps.
Anubarak16 said:
You can make your banking apps work with magisk hide - that's an option to hide your root state for certain selected apps.
Click to expand...
Click to collapse
From where I am at its not the root state that's causing the issue, my phone is not rooted at the moment its running on stock ROG5 firmware the latest one still it doesn't work. Its the unlocked boot loader that's causing the issue.
twistedumbrella said:
You can't change your mind later. Are you sure you can't use one of the safetynet fixes to use the apps?
Beyond that, I believe the locking command was never found. There was a post stating the ones for the ROG 3 didn't work, but I'm not sure if that was ever resolved.
Click to expand...
Click to collapse
I tried the safetynet fixes it doesn't work for me for as long as the boot loader is tampered it wont work. The ROG 2 relocking bootloader worked for me before using tool in one but now I'm not sure how to fix it. I may need the latest boot loader IMG it might fix the issue.
Whenever that I boot into fastboot it's showing fastbootd and not fastboot.
phaw16 said:
I tried the safetynet fixes it doesn't work for me for as long as the boot loader is tampered it wont work. The ROG 2 relocking bootloader worked for me before using tool in one but now I'm not sure how to fix it. I may need the latest boot loader IMG it might fix the issue.
Click to expand...
Click to collapse
You're correct about Safetynet fixes and this device. Some (or all?) apps seem to be able to detect the open bootloader on ROG 5 somehow if they want, even if you get a visual pass on Safetynet with fixes. Don't know how and not sure if there are fixes out there that may work - I didn't find one. I use another device for banking apps.
phaw16 said:
Whenever that I boot into fastboot it's showing fastbootd and not fastboot.
Click to expand...
Click to collapse
Try Fastbooting with the physical buttons (Vol Up + Power) instead.
phaw16 said:
From where I am at its not the root state that's causing the issue, my phone is not rooted at the moment its running on stock ROG5 firmware the latest one still it doesn't work. Its the unlocked boot loader that's causing the issue.
Click to expand...
Click to collapse
Continued at https://forum.xda-developers.com/t/how-re-lock-bootloader-asus-rog-5.4285013/
You can continue discussion in the existing thread here
Thread closed
Thanks