Related
Making defy miui patchrom JB4.2，and it has finished.
But can‘t reboot into system. and can't adb logcat :crying:
===============
$ adb devices
List of devices attached
0123456789ABCDEF unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device
===============
In system, I know how to Allow USB debugging
but It can not enter into SYSTEM now， how to solve the adb devices unauthorized?
Android Debug Bridge version is 1.0.31
Help me~
YouthTeam said:
Making defy miui patchrom JB4.2，and it has finished.
But can‘t reboot into system. and can't adb logcat :crying:
===============
$ adb devices
List of devices attached
0123456789ABCDEF unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device
===============
In system, I know how to Allow USB debugging
but It can not enter into SYSTEM now， how to solve the adb devices unauthorized?
Android Debug Bridge version is 1.0.31
Help me~
Click to expand...
Click to collapse
First Ensure that your cell phone is rooted. after that...
On the same window option in System Settings - Find an option called "Root Access" and select "Apps and ADB" option.
I hope its help you
also check for developer->usb debugging notify...
Anarkista7 said:
First Ensure that your cell phone is rooted. after that...
On the same window option in System Settings - Find an option called "Root Access" and select "Apps and ADB" option.
I hope its help you
Click to expand...
Click to collapse
I was having the same problem. I also had a box that said 'USB debugging notify' checked and didn't notice the device asking for permission to run adb right after I did the kill-server and start-server. As soon as I hit 'ok' the unauthorized problem went away.
Thanks to all on the thread.
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
problem
I am having a similar problem as well. My old Samsung Galaxy S is stuck on bootloop. Home button is dead so I cannot acces download mode/recovery mode manually and in adb device is unfortunately unauthorized
Any way to go around this ?
unauthorized device, unable to adb anything
[email protected]:~$ adb reboot bootloader
error: device unauthorized. Please check the confirmation dialog on your device.
[email protected]:~$
[email protected]:~$ adb devices
List of devices attached
FA2BDS501095 unauthorized
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.
Same Problem! Phone stuck on Samsung logo
So guys,
I am stuck with this really bad problem : http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867/page4
and essentially my phone is unable to start up and gets stuck at the Samsung Logo.
So I am faced with the same error message of phone being detected by adb but unauthorized. Is there any way to access the root of the device overriding the authorization?
I had done adb before so it has to be checked within the settings.
Thanks a lot! Any help is appreciated!
are that problem was solved?
how?
What do you do if the RSA key dialog never comes up?
I have root, I have usb debugging enabled.
I've tried revoking authorizations.
I've tried adb kill-server followed by adb start-server
I've tried changing from MTP to MSC (those are the only two options I have)
I've tried on both an Xperia Z2 and an Xperia Z3 Tablet compact.
Both have the same problem.
No RSA key dialoge either
I have seen some RSA key apps but they are for creating keys. How can I get the dialoge to come up. I have a HTC One M8 831c ROOTED twrp recovery BadSeeds Stock Rooted ROM SuperSU PRO updated. Its on a Harman Kardon Edition which seems to be a little off from the other versions.
emko7 said:
What do you do if the RSA key dialog never comes up?
I have root, I have usb debugging enabled.
I've tried revoking authorizations.
I've tried adb kill-server followed by adb start-server
I've tried changing from MTP to MSC (those are the only two options I have)
I've tried on both an Xperia Z2 and an Xperia Z3 Tablet compact.
Both have the same problem.
Click to expand...
Click to collapse
I have the same exact problem as you. Have you found a solution?
same problem
I have root
have deleted critical system files via titanium backup
i have USB debugging enabled
have revoked authorizations
i have systemui error which loops every time I boot
no home button functionality
no actual phone application any longer
no drop-down notification available, however banner notifications do present themselves only to disappear out of reach above the screen edge.
I have done everything the previous poster mentioned, and my problem is virtually identical to theirs.
Due to these particular circumstances, I am unable to receive the RSA prompt menu and authorize ADB.
I have root access but cannot enter ADB into root mode due to unauthorized device errors.
i am unable to do anything with shell functions as well
my phone is practically disabled at this point, to do anything useful is a daunting task of escaping and passing by the looping systemui error in order to slip into subsequent menus/functions.
The only solution I have found is to rebuild the boot.img file such that it excludes the RSA protocol or over-rides it.
factory restore does not remount vendor partition files no luck restoring from SD or cache.
I am sure I could rebuild the file but I would be pushing my boundaries, something I don't have particular time for at this moment. Being too busy with academics that currently dont encompass coding, I have no time to study on this one...
I will be happy to do my due diligence whatever the case may be, however...I need some answers. My phone is out of commission.
Same problem, did u get the solution?
jleonardol said:
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
Click to expand...
Click to collapse
Please help me. I rooted my phone with the procedure given at:
wiki.cyanogenmod.org/w/Install_CM_for_nicki
Now , after doing
fastboot flash boot boot.img
fastboot reboot
i did -> wipe data/factory reset.
after that when i tried -> adb sideload <my cm12.1 package name>.zip
i am getting this msg.
error: device unauthorized. Please check the confirmation dialog on your device.
when i typed -> adb devices
i got my device unauthorised.
Please help me, i am desperate.
for some reason I dont get the adb authorize box on my watch anymore (to adb reboot bootloader) its says "error: device unauthorized. Please check the confirmation dialog on your device." but there is no way to enable the authorisation anymore.
I also face this problem with pop 2 4.5 5042d; unauthorized and phone in bootloop with no fastboot
No OS installed so not able to Allow USB debugging.
I accidentally Wipe all data using TWRP. Now no OS is installed so not able to allow USB debugging. and adb showing unauthorised device error. Because of it not able to push anything into my phone.
Can somebody help me with this???
---------- Post added at 10:03 AM ---------- Previous post was at 09:10 AM ----------
Im_Rohit said:
I accidentally Wipe all data using TWRP. Now no OS is installed so not able to allow USB debugging. and adb showing unauthorised device error. Because of it not able to push anything into my phone.
Can somebody help me with this???
Click to expand...
Click to collapse
I used OTG instead of internal storage and it works.
jleonardol said:
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
Click to expand...
Click to collapse
same problem--- any idea to solve my problem???
thanks
abhi26 said:
So guys,
I am stuck with this really bad problem : http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867/page4
and essentially my phone is unable to start up and gets stuck at the Samsung Logo.
So I am faced with the same error message of phone being detected by adb but unauthorized. Is there any way to access the root of the device overriding the authorization?
I had done adb before so it has to be checked within the settings.
Thanks a lot! Any help is appreciated!
Click to expand...
Click to collapse
Your phone might be bricked. Did you recently try to root it?
bit late to the party, but this worked for me
I had RSA ADB fingerprint issues, worked for ages then stopped working, went through every forum post and nothing worked, then found this post.... stackoverflow.com/questions/31638582/android-adb-devices-unauthorized[/url]
opening a cmd prompt in this location C:\Users\<your user name>\AppData\Local\Android\sdk\platform-tools and running adb from here and it worked straight from the off.
i've spent 2 nights working on this, so if it helps anyone
my screen broke and picture is completely ****ed and useless.
is it possible to enable USB debugging without using the touch screen? i want to mirror the phone to a laptop and pull my work hour sheet
Gonna try and cover as much as possible but dont be afraid to comment or correct me as I might forget to mention something
ZUK Z1 Specs:
5.5 inch IPS Screen
Snapdragon 801 @ 2.5GHz
3GB RAM
64GB Storage
Dual sim - 2G/3G/4G (doesnt have LTE band 20 unfortunately)
13MP camera with OIS and 8MP front
USB-C charging/data connector
Fingerprint reader
Wifi A/B/G/N/AC
GPS Glonass
Bluetooth 4.1
4100mAh battery
Activate developer settings and ADB + OEM unlock (needed for bootloader unlock among other things)
1. Open settings and scroll to bottom and press "About phone"
2. Scroll to bottom again and press 5 times on "Version" (the one above "SElinux-status") and it should say "developer settings now activated"
3. Press back button once and you should now have a new option "Developer Settings" above "About Phone"
4. Press "Developer Settings" and scroll down to USB debugging and activate it.
5. You can also find the OEM-unlock which unlocks bootloader. If nothing happens when you try to unlock the bootloader then you can use adb command to unlock instead.
Download "Android debug bridge", can recommend minimal ADB by shimp208
http://forum.xda-developers.com/showthread.php?t=2317790 and install it.
You also need adb driver for the phone
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B7YilDjZatvLqGBi_R4vVUYVdkrsUL_Ve9k
or from the chinese site
http://bbs.zuk.cn/z1/t16224/
When driver and adb is installed then type "adb devices" to check if phone is detected. If its detected then you can type "adb reboot bootloader" and after that you might wanna check device manager that your phone driver is installed and working then type "fastboot -i 0x2b4c oem device-info" to see the bootloader lock status and type "fastboot -i 0x2b4c oem unlock" to unlock it, doublecheck with "fastboot -i 0x2b4c oem device-info" again to see if its actually says unlocked before you reboot. Either type "fastboot -i 0x2b4c reboot" or hold power button til it restarts.
Ps. If you are running windows 10 and have issues with adb not detecting any devices, then download updated binary (credits goes to mrcoldbird) and replace the three files in your adb installation https://www.androidfilehost.com/?w=...164e5e9c078239797e768e69027c4effaf26930b8050b
After you´ve replaced the files, type "adb kill-server" and then try "adb devices" again and it should hopefully work. Dont forget to authorize your computer on the phone when the dialog pops up or else you wont be able to perform any commands.
How to enter recovery mode, flash mode
To enter recovery mode you need to make sure phone is turned off.
Then you press and hold vol - and + (both yes) and push the power button and release as soon as the screen is lit (still hold vol+ and vol- until you see the recovery screen).
To enter flash mode you need to make sure phone is turned off.
Then you press and hold vol+ and insert the usb data cable and your computer should have found new hardware. The iffy part here is that the phone is only in flashmode for like 5sec or so, so you need to be quick. Flash mode is currently used for when you wanna unbrick phone or factory reset to the chinese android version called ZUI
How to enter diagnostic mode
There are 2 ways of doing this, the first way is making sure no cable is inserted into phone and turning the phone off. Then hold vol+ and insert usb cable and it will be in diag mode for a brief moment (which can be quite annoying)
The second way (which requires root) makes it easier to fiddle around in diag mode. Activate ADB in developer settings and plug in your phone and authorize it, then type
Code:
adb shell
su
setprop sys.usb.config rndis,diag,adb
and voila you got diag mode activated
Flash TWRP (recovery) onto your phone
Download a twrp file for this phone (credits to JoaoPaulo)
https://www.androidfilehost.com/?fid=24269982087019837
1. Make sure you have adb on pc, driver installed, phone developer settings activated and bootloader is unlocked. Just use the above guide where I explain how to "Activate developer settings and ADB + OEM unlock"
2. Plug in cable if it isnt already and type "adb devices" to check if phone is detected, if not then try "adb kill-server" and try "adb devices" again. If detected then type "adb reboot bootloader".
3. Again make sure phone still has connection with pc by typing "fastboot -i 0x2b4c oem device-info" (since "adb devices" mostly dont work in bootloader mode we use oem device-info command instead to check communication)
4. You can then type "fastboot -i 0x2b4c flash recovery TWRP-2.8.7.0-ham-fixSystem-fixADB.img" to flash the recovery onto phone.
5. If all good and no error messages then reboot phone by typing "fastboot -i 0x2b4c reboot" or hold power button til it restarts.
6. Check that recovery is there and works by shutting down phone, then press and hold vol+ and vol- and press power button til screen goes on then you can release it (still keep hold vol+ and vol- til recovery screen is up)
Flash ZUI, Unbrick phone or fix wierd issues such as problem with activating Wifi or bluetooth
First you need to download the QPST flash program
https://mega.nz/#!4tom3DqL!4a-rRcLef1yS6HJSrBfne_-r9atg6yF3kI_HW8lDaPY
And then you also need the ZUI rom file
https://mega.nz/#!chQkEAwR!IHeYRxWx38QdML6VxjPdVz08BgbZD-Z-xVuSG150qPU
And if you havent already fixed the driver then that aswell
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B...UYVdkrsUL_Ve9k
After you installed QPST, you will get a bunch of programs associated to it, start QFIL from the QPST folder
Click browse on the programmer path row and select "prog_emmc_firehose_8974.mbn" from the directory where you unzipped the QPST ZUI ROM and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone, you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default. On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings), scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option to change language to english incase you cant make out the chinese and you should be good to go
Download and install Gapps
Open http://opengapps.org/
and for first column select "ARM"
Second column, if you are running CM12 or the ZUI 1.2.x for example it is 5.1 you want
If you are running CM13 or ZUI 1.5.x it is 6.0 you want.
Then last column is just how many of the google apps you want to have installed, you can press the link "Version Information" in red text at the bottom left to see the what each package contains.
I usually go with nano since you get the necessary apps to sync your account and then ill just download the rest I want/need from play store. Its also a smaller download so goes quicker to flash aswell
Activate Root on Cyanogenmod
First you need to activate developer settings if you havent already (tap version 5 times in "about phone"), then enter developer settings menu and there you´ll have an option called "Root access" which you can set to either "only apps" and "only ADB" or both. "Only apps" is preferred and thats it, you can now run root priveliged apps (after you have confirmed each apps authorisation).
Convert from ZUI to cyanogenOS/mod
Check the guide from Paul on Modaco for this
http://www.modaco.com/forums/topic/375804-convert-z1-from-zukui-to-cyanogen-os/
Troubleshooting
If you are having usb connectivety issues, please try using another PC. Can also be a bit iffy getting connection going with windows 10 so try windows 7 if possible. You could also run windows 7 in a virtual machine and get it working that way as an example.
Also when troubleshooting connectivety issues working with adb, dont forget to try and "adb kill-server" to reset the connection before you try adb commands again if phone isnt detected in the first place between any changes you may have made.
If you have issues with rom then its good to start fresh with a factory reset and if that doesnt help then flash zui through QPST and any issues should now be resolved unless there is a hardware issue ofc.
Keep in mind that you should almost always do a factory reset when doing a large update, like if you update from kitkat to lollipop then factory reset or from lollipop to marshmallow also factory reset but this also applies when you change from cyanogen to Zui for example regardless of it its lollipop or marshmallow. Only time when its ok to "dirty flash" (in my opinion) is when you do smaller updates such as updating nightly to nightly on CM12 or nightly to milestone/rc or final. Also applies on modified roms which uses CM12 as base, as long as you are staying on the same rom its fine but if you swap from modified cm12 to vanilla/stock cm12 then you might experience issues.
CM12 Nightly -> CM12 newer Nightly OK
CM12 Nightly -> CM12 Milestone OK
CM12 Nightly -> ZUI any version definately NOT OK
CM12 Nightly -> CM13 NOT OK
CM13 Nightly -> CM13 newer Nightly OK
CM12 MOKEE -> CM12 nightly NOT OK
CM12 MOKEE -> CM13 NOT OK
Stuff "might" work if you update from CM12 to CM13 and also going from a modified CM12 to vanilla or the other way around but it might also cause wierd issues which you might not think of, batterydrain, slow phone, force close etc etc
Downloads and links:
Driver Zuk Z1 Win Vista/7/8/10
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B7YilDjZatvLqGBi_R4vVUYVdkrsUL_Ve9k
Flash program QPST
https://mega.nz/#!4tom3DqL!4a-rRcLef1yS6HJSrBfne_-r9atg6yF3kI_HW8lDaPY
Password: bbs.zuk.cn
Kernel
Chromakernel http://forum.xda-developers.com/zuk-z1/development/kernel-chroma-kernel-r1-tester-t3254724
Minimal ADB
http://forum.xda-developers.com/showthread.php?t=2317790
ROMS (mostly TWRP)
CyanogenOS 12.1 http://forum.xda-developers.com/zuk-z1/development/official-ota-update-links-ota-updating-t3226990 and http://forum.xda-developers.com/zuk-z1/development/rom-cyanogen-os-12-1-yog4pas3oh-t3248820
Cyanogenmod 12.1 http://forum.xda-developers.com/zuk...om-cyanogenmod-12-1-nightlies-lenovo-t3249009
Cyanogenmod 13 http://forum.xda-developers.com/zuk-z1/orig-development/unofficial-cm13-t3277885
Zui QPST version https://mega.nz/#!chQkEAwR!IHeYRxWx38QdML6VxjPdVz08BgbZD-Z-xVuSG150qPU
Zui 1.2.070 (Lollipop) http://bbs.zuk.cn/zui/t53638/
Zui 1.5.x (Marshmallow) http://forum.xda-developers.com/zuk-z1/development/android-6-0-official-zui-1-5-077-beta-t3270587
Exodus http://forum.xda-developers.com/zuk-z1/orig-development/rom-exodus-android-zuk-z1-t3244026
Mokee http://forum.xda-developers.com/zuk...om-mokee-opensource-project-official-t3254984
Toolkit
http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964
Unlock Bootloader without wiping data
http://forum.xda-developers.com/zuk-z1/help/guide-unlock-bootloader-zuk-z1-wiping-t3251801
TWRP (Recovery) by JoaoPaulo
https://www.androidfilehost.com/?fid=24269982087019837
Thanks to everyone involved in helping making this a better device
Thanks to Breadcrust for the initial developing and help
Thanks to javirenart for porting a Toolkit to our device
Thanks to Paulobrien at Modaco for the guide on converting ZUI to CM
And whomever else I have forgotten to mention (shout at me and ill update)
Special thanks to @MrColdbird for fixing a working CM13 with Wifi/Data/GPS/DT2W/bugs and @JoaoPaulo for helping out and giving us an updated and fixed TWRP, kernel stuff and hopefully fingerprint reader!
Some recommended apps
Check hardware sensors
Sensor box for android https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
Check hardware and some sensors
CPUZ https://play.google.com/store/apps/details?id=com.cpuid.cpu_z
Underclock to gain more batterytime
Kernel Auditor https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
(Personally ive used 1497MHz on cpu keeping interactive governor and put GPU on 200MHz with great result, phone still feels snappy on CM13)
Reserved 2
Great job man....It's really helpful for everyone, instead of searching every where.
You forget how to unlock to boot loader without wiping the device
Tengo10 said:
You forget how to unlock to boot loader without wiping the device
Click to expand...
Click to collapse
Not sure how you would do that? Looked quickly if anyone had written any guides already about it but didnt see any and search function is temporary disabled or unavailable :/
@Titokhan and I tested it and it workes perfect... link: http://forum.xda-developers.com/zuk-z1/help/guide-unlock-bootloader-zuk-z1-wiping-t3251801
@Tengo10
which version you used to kingroot? the latest 4.6.5 b2?
Inviato dal mio Z1 utilizzando Tapatalk
Thanks for your work but some downloads needs password,also to unzip downloads is asked for password.
Can you provide them
---------- Post added at 12:29 PM ---------- Previous post was at 11:51 AM ----------
Thanks for your work but some downloads are asking for password,also in the downloads witch are not asking for password ,the zip files are asking for it.
Can you provide them please ?
fr4nkr0c said:
@Tengo10
which version you used to kingroot? the latest 4.6.5 b2?
Inviato dal mio Z1 utilizzando Tapatalk
Click to expand...
Click to collapse
Oh sry didn't get a message, the kingroot version was the newest but that's not interesting cause it loads the scripts from the web
Reserved
Enviado desde mi Z1 mediante Tapatalk
While trying to unlock band 20 on another phone I tried it on the zuk z1 aswell but didnt work, anyway found out how to enter diagnostic mode in a more permanent matter instead of the brief 5sec you get when using vol+ and inserting usb cable before the phone boots.
Ive added it in first post but the magic is
Code:
adb shell
su
setprop sys.usb.config rndis,diag,adb
unbrick phone method didnt work for me, fails when downloading through QFIL
Driver Zuk Z1 Win Vista/7/8/10
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B...UYVdkrsUL_Ve9k
Could you please insert the correct link of MEGA?
Thanks a lot
Need the drivers for Win 7 @tndb
the mega link u posted needs a decryption key, please post the same
satsmagic said:
Need the drivers for Win 7 @tndb
the mega link u posted needs a decryption key, please post the same
Click to expand...
Click to collapse
Sorry about that, link is updated
tndb said:
Sorry about that, link is updated
Click to expand...
Click to collapse
thanks for posting the link. I am using the International version of Zuk Z1
However, even after installing the drivers you posted my device is not connecting properly to my Win 7 laptop, I tried on a XP machine too.
When i connect the device, by default, it connnects in charging mode and I get a popup saying device not recognised.
If i switch to MTP mode, nothing happens. I wait till the screen turns off, when i turn on the screen again, it again shows in charging mode. I have to disconnect and then reconnect, then it connects in MTP mode. This should not happen, I should be able to swap between the modes without disconnecting and reconnecting the device
If i select Mass storage mode, then it shows an addtional drive in My computer as removable disk, but does'nt show its capacity. If i click on it, it says please insert a disk. so Mass storage mode doesnt work. I have to select MTP again, disconnect and then reconnect to get in MTP mode.
Anyone else facing this issue, what can be a solution for this.
I am on 12.1-YOG4PAS7DF
Also, i found these C-apps on this link https://cyngn.com/c-apps
Should i flash these, would these update anything on my ROM version
please help me !!!!!
Let me know how i can turn off Zuk Z1 as my touch is not working, i tried to root is using Farmaroot and when i restarted it the touch stopped working. Hardware keys are working fine.
I am using zui version 1.2.070 in India, how to upgrade this ??,, I am a simple user, don't have much tech knowledge about this ,kindly guide me
25.11.2017 - Update: I've just used same tutorial to unlock Z5 6653 and it was success ! Good luck to everyone!
23.09.2021 - Files shared again by request. If any questions occur - write me.
This is solution that i used to unlock found device Xperia Z5 Premium, which was locked with fingerprint, bootloader is locked and FRP (google account security) is activated.
Dear friends, as everyone here, i must say USE THIS GUIDE ON YOUR OWN RISK ! ! !
I'm not responsible for bricked devices, if your dog unplug the cable or you lost electricity durring flashing!
First i want to say HUGE thanks to @YasuHamed !!! He knows why !
*to get in flash mode: press volume down and connect device to PC; - green notification LED
*to get in Fastboot mode: press volume up and connect device to PC; - blue notification LED
DOWNLOADS:
Xperia E6853 - Google Drive
drive.google.com
Xperia E6853 - Google Drive
drive.google.com
*I'm trying to share folder with unattended access, but google asks me everytime. Usually i respond fast, but do not hesitate to PM me if you have no access.
GUIDE:
1st you need Sony flashtool and drivers, and ADB fastboot.
-Download Sony Companion to have all sony drivers.
-Download Flashtool (flashtool-0.9.23.1-windows.exe) and install it.
-I updated Flashtool from 0.9.23.1 to 0.9.23.2. Simply download (x10flasher.jar) and replace existing file in C:/Flashtool/.
-Next download ADB fastboot (minimal_adb_fastboot_v1.4_setup.exe) and install it.
2nd i flashing another Android using Flashtool thru flash mode, for clean start of the device.
-Open Flashtool (C:/Flashtool/Flashtool.exe)
-Connect your device in flash mode.
-Click on the black XE button on the right end of the toolbar in FlashTool.
-Choose your device, choose region and customization and on the right side, bellow the picture of the phone you can see "Available Firmware:"
Here i've choose 1300-1579 Internal Promoter 32.0.A.6.170 / R2B. This is old 5.1.1 Android which allow you to get in to the phone menu itself and do the FRP Unlock.
-Click on the firmware , bellow phone picture, and download it.
-After it is downloaded, close that windows and on main window, will see in console that firmware is prapairing for flashing.
-Phone is still connected in flash mode, and flashing will start automaticly when firmware is ready.
Have patience! Prepairing and flashing took around 10 mins for my PC.
3rd Bypass FRP ( google account security lock)
-check FlashTool console if flashing status is DONE, and if it is, unplug your device and power it up.
-now download the video file ( Bypass Google Account SONY Xperia Z5 - How to Remove FRP Lock.mp4 ) and follow the steps as it is shown.
On the last step when you have to switch from GUEST to Owner user, my device just frozen on waiting screen, and after 5-6 minutes screen went disturbingly black, like it is dead and went OFF.
I power it up and voila, there was 2 steps to complete setting up of the new phone.
4. If you want you can unlock your bootloader now (if it is available by SONY) and use custom roms, root and etc.
-go to dialer and dial *#*#7378423#*#*
-tap Service info” go to “Configuration ” go to ” Rooting Status.
-if Boot loader unlock allowed says ” Yes” then you can follow below guide. If it says NO - sorry, you can't unlock your bootloader.
-you need your IMEI number, You can check it in settings menu or dial *#06#.
-turn on OEM Unlocking and USB debugging options in Settings > Developer options. (To enable Developer options menu, go to Settings > About phone , and tap several times on Build number.)
-switch off your Sony Xperia Z5 Premium by pressing power button.
-now connect phone in fastboot mode. To do so, you must hold Volume UP and plug device to PC.
-next go to https://developer.sonymobile.com/unlockbootloader/ and finish the steps using your IMEI to get unlock KEY from Sony.
When you have the key, you will see instructions on the same site, what command you have to use in fastboot ADB. To get in Fastboot ADB:
-on your PC go to the folder (C:/adb/) where you installed minimal ADB and fastboot, hold shift + Right click, choose Open command window here.
-check if device is propperly connected. Write in CMD : fastboot devices . Your device should be listed there if it is connected in fastboot mode.
-now you have to write the command, same as on Sony site with the key: fastboot -i 0x0fce oem unlock 0x“your unlock code”.
example : – fastboot -i 0x0fce oem unlock 0x87eb234h6212g5646
-If it says OK [time] finished , you are done well.
After bypass FRP you can flash Android 7.0, there is no problem or security issues.
I've used those guides:
https://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614
http://www.gogorapid.com/unlock-bootloader-sony-xperia-z5-premium/
this is very well xplained tutorial.
i have book marked it and will be referencing it in future
best of luck
FRM Bypass Not Working with Nougat
YasuHamed said:
this is very well xplained tutorial.
i have book marked it and will be referencing it in future
best of luck
Click to expand...
Click to collapse
Guide is awesome. Only problem now, bypassing the Google account video does not work with Nougat which is what the flashtool downloaded by default for me.
Is there any other way please?
EDIT UPDATE: I found a way with another video on YouTube. Maybe could use this one also to update your guide. It worked for me. I thank you once again for this awesome guide, helping me to reset this phone.
https://www.youtube.com/watch?v=PdSo5hkB7SI
KayCee-Kepz said:
Guide is awesome. Only problem now, bypassing the Google account video does not work with Nougat which is what the flashtool downloaded by default for me.
Is there any other way please?
EDIT UPDATE: I found a way with another video on YouTube. Maybe could use this one also to update your guide. It worked for me. I thank you once again for this awesome guide, helping me to reset this phone.
https://www.youtube.com/watch?v=PdSo5hkB7SI
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=A5ok_s8zxKc
Not working
I bought a phone that was damaged and I repaired it. It has the google frp lock all the guides so far dont work. It is on android 7 and I am stumped how to get passed this can you help?
mintminty59 said:
I bought a phone that was damaged and I repaired it. It has the google frp lock all the guides so far dont work. It is on android 7 and I am stumped how to get passed this can you help?
Click to expand...
Click to collapse
Read 2nd step in instructions! First of all you have to downgrade the Android version !
thanks for bootloader unlocking method. For frp bypass you can follow this guide ~ http://www.frpghost.com/2017/03/sony-xperia-frp-unlock.html
My bootloader cannot be unlocked via Sony as my rooting status says NO. (Phone has Android 7.1.1) so even with your instructions I cannot root the phone and or downgrade to Android v7.0. Is this correct?
---------- Post added at 03:33 AM ---------- Previous post was at 03:31 AM ----------
grosseader said:
25.11.2017 - Update: I've just used same tutorial to unlock Z5 6653 and is was success ! Good luck to everyone!
This is solution that i used to unlock found device Xperia Z5 Premium, which was locked with fingerprint, bootloader is locked and FRP (google account security) is activated.
Dear friends, as everyone here, i must say USE THIS GUIDE ON YOUR OWN RISK ! ! !
I'm not responsible for bricked devices, if your dog unplug the cable or you lost electricity durring flashing!
First i want to say HUGE thanks to @YasuHamed !!! He knows why !
*to get in flash mode: press volume down and connect device to PC; - green notification LED
*to get in Fastboot mode: press volume up and connect device to PC; - blue notification LED
DOWNLOADS:
https://drive.google.com/open?id=0ByQNHZjTS8SNWDdDTkpCUDFfSGM
GUIDE:
1st you need Sony flashtool and drivers, and ADB fastboot.
-Download Sony Companion to have all sony drivers.
-Download Flashtool (flashtool-0.9.23.1-windows.exe) and install it.
-I updated Flashtool from 0.9.23.1 to 0.9.23.2. Simply download (x10flasher.jar) and replace existing file in C:/Flashtool/.
-Next download ADB fastboot (minimal_adb_fastboot_v1.4_setup.exe) and install it.
2nd i flashing another Android using Flashtool thru flash mode, for clean start of the device.
-Open Flashtool (C:/Flashtool/Flashtool.exe)
-Connect your device in flash mode.
-Click on the black XE button on the right end of the toolbar in FlashTool.
-Choose your device, choose region and customization and on the right side, bellow the picture of the phone you can see "Available Firmware:"
Here i've choose 1300-1579 Internal Promoter 32.0.A.6.170 / R2B. This is old 5.1.1 Android which allow you to get in to the phone menu itself and do the FRP Unlock.
-Click on the firmware , bellow phone picture, and download it.
-After it is downloaded, close that windows and on main window, will see in console that firmware is prapairing for flashing.
-Phone is still connected in flash mode, and flashing will start automaticly when firmware is ready.
Have patience! Prepairing and flashing took around 10 mins for my PC.
3rd Bypass FRP ( google account security lock)
-check FlashTool console if flashing status is DONE, and if it is, unplug your device and power it up.
-now download the video file ( Bypass Google Account SONY Xperia Z5 - How to Remove FRP Lock.mp4 ) and follow the steps as it is shown.
On the last step when you have to switch from GUEST to Owner user, my device just frozen on waiting screen, and after 5-6 minutes screen went disturbingly black, like it is dead and went OFF.
I power it up and voila, there was 2 steps to complete setting up of the new phone.
4. If you want you can unlock your bootloader now (if it is available by SONY) and use custom roms, root and etc.
-go to dialer and dial *#*#7378423#*#*
-tap Service info” go to “Configuration ” go to ” Rooting Status.
-if Boot loader unlock allowed says ” Yes” then you can follow below guide. If it says NO - sorry, you can't unlock your bootloader.
-you need your IMEI number, You can check it in settings menu or dial *#06#.
-turn on OEM Unlocking and USB debugging options in Settings > Developer options. (To enable Developer options menu, go to Settings > About phone , and tap several times on Build number.)
-switch off your Sony Xperia Z5 Premium by pressing power button.
-now connect phone in fastboot mode. To do so, you must hold Volume UP and plug device to PC.
-next go to https://developer.sonymobile.com/unlockbootloader/ and finish the steps using your IMEI to get unlock KEY from Sony.
When you have the key, you will see instructions on the same site, what command you have to use in fastboot ADB. To get in Fastboot ADB:
-on your PC go to the folder (C:/adb/) where you installed minimal ADB and fastboot, hold shift + Right click, choose Open command window here.
-check if device is propperly connected. Write in CMD : fastboot devices . Your device should be listed there if it is connected in fastboot mode.
-now you have to write the command, same as on Sony site with the key: fastboot -i 0x0fce oem unlock 0x“your unlock code”.
example : – fastboot -i 0x0fce oem unlock 0x87eb234h6212g5646
-If it says OK [time] finished , you are done well.
After bypass FRP you can flash Android 7.0, there is no problem or security issues.
I've used those guides:
https://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614
https://www.youtube.com/watch?v=GmaK1bfiaTo
http://www.gogorapid.com/unlock-bootloader-sony-xperia-z5-premium/
Click to expand...
Click to collapse
My bootloader cannot be unlocked via Sony as my rooting status says NO. (Phone has Android 7.1.1) so even with your instructions I cannot root the phone and or downgrade to Android v7.0. Is this correct?
xectis said:
My bootloader cannot be unlocked via Sony as my rooting status says NO. (Phone has Android 7.1.1) so even with your instructions I cannot root the phone and or downgrade to Android v7.0. Is this correct?
Click to expand...
Click to collapse
You should be able to flash OE rom and downgrade using 2nd step!
What you want to to ? Bypass FRP ? root? or ?
4. If you want you can unlock your bootloader now (if it is available by SONY) and use custom roms, root and etc.
-go to dialer and dial *#*#7378423#*#*
-tap Service info” go to “Configuration ” go to ” Rooting Status.
-if Boot loader unlock allowed says ” Yes” then you can follow below guide. If it says NO - sorry, you can't unlock your bootloader.
Click to expand...
Click to collapse
This is what I don't get it, my Z5P says NO in bootloader, so even so, can I do this process to unlock? or definitely i can't unlock it in any way
I haven't started the process yet, because first I would like to know if I can still unlock it with this process even if it says no in the configuration menu.... I'm still on 7.1
Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!
ZSparda said:
Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!
Click to expand...
Click to collapse
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?
Wolfcity said:
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?
Click to expand...
Click to collapse
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.
ZSparda said:
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.
Click to expand...
Click to collapse
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?
PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.
Wolfcity said:
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?
Click to expand...
Click to collapse
I tried to attach a couple of screenshots but I get the "bad request" message here. Anyways, when we do a normal boot we get the validation error message and we are sent directly to fastboot menu, but there we cannot choose any options because all of them lead to the error message again.
It's been a couple of weeks now but the last time we tried doing something, the device wasn't showing up in device administrator nor being recognized by adb.
As regards to the battery, we've left it charge up for some hours, so I guess that's not a problem, although we cannot see the percentage.
[email protected] said:
PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.
Click to expand...
Click to collapse
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?
ZSparda said:
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?
Click to expand...
Click to collapse
This thread is long, but alot of good info on hard bricked Moto G5 plus devices.
Code:
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
To get PC in test mode
Code:
Here is how to turn on or off the Test Mode feature in Windows 10.
IMPORTANT: Please remember that turning off the Test Mode feature may force the program/driver which is not digitally signed stop working.
Step 1: Open Command Prompt as administrator. To do so, type CMD in Start menu search to see Command Prompt in the search result. Right-click on Command Prompt entry and then click Run as administrator option. Click Yes button when you see the User Account Control screen.
Step 2: At the Command Prompt window, execute the following commands:
To enable the Test Mode:
Bcdedit.exe -set TESTSIGNING ON
To disable the Test Mode:
Bcdedit.exe -set TESTSIGNING OFF
If the above command didn’t work, this one must work:
Bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
Bcdedit.exe -set TESTSIGNING OFF
You may exit the Command Prompt now.
[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Thanks! I'll send him all these so he can try. I'll update as soon as possible.
[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.
ZSparda said:
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.
Click to expand...
Click to collapse
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about
Code:
fastboot devices
? It should show the device #. ADB doesn't always show devices.
[email protected] said:
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about ? It should show the device #. ADB doesn't always show devices.
Click to expand...
Click to collapse
Yes! Fastboot devices shows the device! So now we have to procede with the flashblank.zip and all that from the other post right? Also sorry for the late reply, I've been pretty busy these past days so I left him with all the work.
I'll be making a video for this with the 7 inch tablet on Nov. 29th or 30th (depending on the time I have)
General Disclaimer: I'm not responsible if you brick your tablet. This is how I did it personally as other methods here didn't work for me. I have yet to test this method on a 7 inch, also do not have access to the Surf variants. This has only been tested on the 10.1 inch with the keyboard. Will update when I test with the 7 inch.
What's Needed:
MTK Fastboot Drivers: https://online.mediatek.com/Public Documents/MTK_Android_USB_Driver.zip
Magisk Manager Canary: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Stock Boot Image: https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
ADB and Fastboot: https://www.xda-developers.com/what-is-adb/
Prerequisites:
Personally, I had issues getting my PC to recognize the tablets in Fastboot mode. The drivers wouldn't install. This might be optional for some of you, but I thought I'd include it just in case.
Installing MTK Fastboot Drivers from the link above
If you plugin your device in fastboot mode and your PC doesn't recognize it, follow these steps. If it did, skip this part.
1.) Download the drivers above and unzip the Zip file somewhere on your PC (desktop or My Documents is easiest)
2.) Boot your Tablet into Fastboot Mode by holding Vol + and Power, then select Fastboot from the Menu
*NOTE* There is a bug with these tablet's that the volume buttons are mislabeled. Really dumb, but I guess that's why they were 55 bucks for the 10 inch on black friday
3.) Plug the device into your PC and open Device Manager by pressing WinKey+R and typing devmgmt.msc, hit Enter
4.) If there's an Other Device listed called Android, follow these steps. If it isn't there, follow the next set of steps
5.) Open a Command Prompt window as Admin and type the following command
Code:
bcdedit.exe /set nointegritychecks on
6.) Hit enter, then restart your PC
7.) Once the PC is restarted, make sure your tablet is connected in Fastboot mode and open Device Manager again
8.) Right click Android under Other Devices and select Update Drivers
9.) Click the Browse my Computer for driver software button and select the MTK Folder you extracted from the download link above
10.) From there, you can open command prompt, type fastboot devices and see if your tablet shows up and move on to root!
Unlocking your Bootloader
From here, you can unlock your bootloader very easily to Root your device
This will wipe all data off the tablet!
0.) Enable OEM Unlock and USB Debugging on the tablet by going to Settings->About and tap Build Number 7 times. From here, enter the new Developer Options that unlock and turn on OEM Unlock and USB Debugging.
1.) Boot your tablet into Fastboot mode and connect it to your PC
2.) Open a Command Prompt window and type the following command, then hit enter
Code:
fastboot flashing unlock
3.) Follow the instructions on screen to unlock your bootloader
4.) Now Boot your device and we'll move on to making a rooted Boot Image
Creating a Rooted Boot Image with Magisk Manager
0.) Make sure you already have Wifi setup and connected before the first time you open Magisk Manager on your device! Make sure it auto connects as well
1.) Download Magisk Manager Canary from the link above
2.) Install it to your device
3.) Download boot Image from the Stock Boot Image part of the Prerequisites above and put the boot.img on your devices internal memory
4.) Open Magisk Manager and select Install Magisk
5.) Select Patch File and select the boot.img from your internal storage
6.) Once its done patching the image, take magisk_patched.img from the downloads folder of your device and move it onto your PC
7.) Boot your tablet into Fastboot mode and plug it into your PC
8.) Open Command Prompt and type the following command and hit enter (make sure you know your magisk_patched.img file location)
Code:
fastboot flash boot magisk_patched.img
9.) Reboot the device and you'll be Rooted!
Optional Steps like Modules and Debloating
My basic debloat script: https://forum.xda-developers.com/wa...s-general/root-walmart-bloat-remover-t4011639
Will be testing GSI roms on the spare 7 inch and will list those here
Recommended Magisk Modules:
Viper4Android Legacy
FDE.AI
MagiskHide Props Config
Systemless Hosts
Youtube Vanced Black
Magisk Setting to Enable:
Magisk Hide
Rename Magisk Manager App (keeps app from detecting magisk root)
Credits:
Myself for this root method @byproxy for reminding me to add the steps for OEM Unlock and enabling wifi before opening Magisk Manager for the first time
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Are you online? I had the same problem.
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Sorry, been a busy few days, but make sure you're connected to Wifi, close Magisk Manager, then reopen it and you'll be good to go!
Onn 8" walmart tablet
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
CoachDad said:
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
Click to expand...
Click to collapse
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
mrmazak said:
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
Click to expand...
Click to collapse
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
This is an mtk device not Samsung. So there is no Odin or download mode. There is spflash tool, and preloader.
And if you flash firmware (with default frp partition) then frp lock is cleared.
But you will have to find that file. It maybe in the stock firmwares that are shared, I do not know.
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
byproxy said:
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
Click to expand...
Click to collapse
I did not realize I didn't include that step. Total noob mistake when typing a tutorial up for android. I do this almost daily at work, so I forget to include it
CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot.
no worries! i didn't think about it either until i was having issues. thanks for the tutorial... it was super helpful!! btw it definitely works on the 8" tablet.
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
'Quis said:
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
Click to expand...
Click to collapse
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
KaptinBoxxi said:
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
Click to expand...
Click to collapse
Ok, thank you! This is a shot in the dark, but in order for ADB to work, USB debugging has to be enabled. I can't do that as the tablet is locked by FRP and I have looked countless times on Google and MSN to see if it's possible. Do you have any tips for that?
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
will this root onn 8 inch tablet running android 9
soateufel said:
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
Click to expand...
Click to collapse
Sorry for late reply. Been away from home with work. When fastboot mode indicates "waiting for device," it generally means that your device is not properly communicating with your PC or laptop. This is nearly always due to missing or incorrect drivers 9n your computer. There are several comprehensive guides here on XDA for installing necessary ADB & Fastboot drivers.
installed magisk manager on onn 8 and also have img zip but win i go to patch it magisk manager crashes
when you mean patch boot img do mean to unzip file on onn 8