Related
Well... Here it is.
I also have some script files i found and all the info you need to create your own pre-rooted rom using your current system files if you like that option better. I am currently working on a custom 5.0.1 rom.
READ THE WHOLE POST BEFORE YOU DO THIS!!!
I am only giving you a step by step process put into a easy to use reference guide to help you obtain "root" on your device. I am providing this "As-Is". If you read the whole guide and decide to try it on your own device just know that It may/will void any product warranty that you may have on the device if any. Any time you do anything to your tablet via fastboot or any other means you run the risk of "bricking" your device, or loosing all of your data. I am not responsible for any damage to your device, and i will not be responsible for any damage or loss that you may have as a result of this post, or any instructions that i give here. If you have any questions feel free to send me a message and I will try to help you out, if i can....
I looked and looked and looked through many forums without much luck, and I finally found out how to root the U.S. version ASUS MEMO FHD 10 that has been updated to 4.3 - V5.0.21 by using a pre rooted system rom. If you are not running that version you can go to” Settings - About Tablet - System Update” to update it to 5.0.21
First things first...
Fully charge your tablet, and make a backup of your system!!!
1. Make sure the tablet has a good charge. It will not charge while you are doing this, and who knows what will happen if it dies halfway through the process.
2. Turn USB debugging mode on in the "Developer Options" menu under settings on your tablet.
If you do not have the "Developer Options" menu just go down to "About Tablet" and click the "Build Number" button six or seven times and it will say "developer mode enabled", or something to that effect, and it will unlock the "Developer Options" menu for you.
3. Turn off your tablet.
4. Hold down the volume up button , and press the power button until your tablet turns on. It will boot into fastboot for you.
Connect your tablet via USB cable to your computer, and set it aside.
Now your tablet is ready to go and it is time to set up your computer.
1. To get your computer to recognize your tablet in usb debugging mode you need to install the intel drivers.
2. Download and install minimal adb fastboot.
3. Download the pre-rooted system rom, and then put that rom into the folder that you installed fastboot in on your computers hard drive.
4. I used minimal_adb_fastboot_v1.1.3_setup.exe to do this next part with no problems whatsoever. the only thing was I needed to type the .exe from the command prompt for it to work on my laptop. You might not need to.
Now you have your computer all set up, your tablet is all ready, and it is time to finally do some rooting.
1. On your computer, open up a command prompt, and navigate to the folder that you installed fastboot to.
2. Enter the following commands one line at a time into your fastboot window. (See transcript below)
fastboot.exe devices (Just to make sure your device is connected properly.)
fastboot.exe erase system (Optional I think? I didn't use it and mine works great)
fastboot.exe flash system us_me302c-v5.0.21-jb_4.3-system.gz (Replace with your image file name if you are using a different one)
If done right it should look something like this.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe devices
1111111111111111 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe flash system us_me302c-v5.0.21-jb_4.3-system.gz
sending 'system' (771129 KB)...
OKAY [ 95.862s]
writing 'system'...
OKAY [ 74.116s]
finished. total time: 169.978s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
And guess what. You're all done…
Now just sit back and let it reboot a few times.
You are going to want to make sure you have a superuser app and enjoy…
Im not an expert but after a few weeks of hunting for it i finally found out how to do it.
Many thanks go out to everyone who worked on this for all of us, and if you found this post helpful please feel free to add some thanks.
WARNING: UNLOCKING THE DEVICE WILL VOID YOUR WARRANTY WITH ASUS, ALSO, I AM NOT RESPONSIBLE FOR ANY DAMAGES TO ANY TABLET, EVEN THOUGH I HAD NO TROUBLE OR PROBLEMS WHATSOEVER.
Am currently run windows 8.1 professional. I have plainly ran around trying to fastboot a used ASUSTF700T i bought.
Before beginning head to the ASUS web site and download version(V7) (source for the apk file to unlock bootloader)
http://support.asus.com/download.as...Infinity+TF700T&os=&hashedid=fq2B3oq64av1O95u
select android and the utilities, which is an apk file save on an SD card before installing. under security in settings all ow installation from
unknown sources
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings.
Press back and go into Developer Options and enable USB debugging.
Install the the latest Android studio(http://developer.android.com/sdk/index.html) for your windows pc follow all the prompt as required.
after installation open file explorer > click view tab > click option > click view > check show hidden files > click apply and then Ok.
Look at the Screenshot.
In file explorer right click on This PC an click on properties > Click advance system settings > click Environmental Variables
scrol down on system variables until path and click edit and delete "/" and put ";" all without quotes
now type in or paste C:\Users\YOUR\AppData\Local\Android\sdk\platform-tools (YOUR is the name of the user account)
Double click on the drive C: ( or wherever you have installed the android studio software) navigate to users and then to the account
to which under the installation of android studio was installed navigate to
AppData(C:\Users\YOUR\AppData)
then C:\Users\YOUR\AppData\Local -> C:\Users\YOUR\AppData\Local\Android -> C:\Users\YOUR\AppData\Local\Android
-> C:\Users\YOUR\AppData\Local\Android\sdk\platform-tools
Now download the latest openrecovery-twrp from(http://techerrata.com/browse) http://techerrata.com/browse/twrp2/tf700t
eg openrecovery-twrp-2.8.5.0-tf700t.blob rename ( right click on the file and click rename( type over only the highlighted letter not after the "dot"
the file(openrecovery-twrp-2.8.5.0-tf700t.blob) to twrp.blob and place the file into the folder
C:\Users\YOUR\AppData\Local\Android\sdk\platform-tools
http://www.teamw.in/project/twrp2/105/
"adb" and "fastboot" are installed from the android studio
Open a comand prompt( with administrator privileges) by using the search pane and right click and run as administrator
Now boot your device into fastboot mode Turn off your device.
Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
If you have an old bootloader select USB icon, press Volume up button
If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is Unlocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
on the cmd prompt enter fast boot devices ( lower case letters only) if the device is found you will see the
some unique name associated with your device.
C:\Windows\system32>fastboot devices
015d29955e441c12 fastboot
Now continue to change the directory till you get to platform-tools
C:\Windows\system32>cd..
C:\Windows>cd..
C:\>cd users
( your is the current user account)
C:\Users>cd your
C:\Users\YOUR>cd appdata
C:\Users\YOUR\AppData>cd local
C:\Users\YOUR\AppData\Local>cd android
C:\Users\YOUR\AppData\Local\Android>cd sdk
C:\Users\YOUR\AppData\Local\Android\sdk>cd platform-tools
(Type in fastboot -i 0x0b05 flash staging twrp.img or fastboot -i 0x0B05 flash recovery twrp.blob)
C:\Users\YOUR\AppData\Local\Android\sdk\platform-tools> fastboot -i 0x0B05 flash
recovery twrp.blob
sending 'recovery' (7276 KB)...
OKAY [ 2.793s]
writing 'recovery'...
OKAY [ 7.432s]
finished. total time: 10.241s
TWRP recovery is now installed on your device
check that enter recovery mode :Boot with "power + vol down" then after the splash screen put "vol up".
credit for this explanation and information (http://forum.xda-developers.com/member.php?u=5422278) from the forum and from different other websites and gathered them together for my own case, but I think this may help others
Thanks to all the guys here.
I recently purchased a used Pixel 4a, and I now understand why the seller was offering such good price for it and why he refused to respond to me now I have it. This phone has ArcanseOS 10 installed, which has only 3 apps installed... Setting, Clock and Calculator. There is no Play Store app, no Phone app, nothing.
The only useful reference to ArcaneOS I can find in the Googleverse is this one... https://translate.google.com.au/tra...rueck-flashen.973774.html&prev=search&pto=aue where the OP describes his troubles with a Pixel 3. Through the rough translation, I see similar issues... can't enable developer mode, can't unlock bootloader, can't sideload apps.
Some random observations about this phone/OS...
- The phone is in good condition. I used the supplied pin code to unlock it and did a factory reset. Have done basic config with my Google Account, etc.
- In Settings > About Phone - the build number is not shown. I cannot tap on the build number 7 times to enable Developer Mode. I have tried tapping everything in About Phone 7+ times, but I have not been able to enable Developer Mode.
- When the phone powers on, the first thing shown is a message like "Your device is loading a differennt operating system".
- The installed OS is ArcaneOS 10. The system updater says that ArcaneOS 11 is available for download (but I don't want to do that in case it makes this thing even harder to fix).
- I tried sideloading open_gapps and a random developer shortcut app I found, but I can't seem to get them to load.
I'm no expert at this, so I've tried various commands that I found and got some of these results...
(note: some details, esp path names, have been edit for brevity)
>adb devices
List of devices attached
09241JEC228869 sideload
>adb shell
error: closed
>adb sideload open_gapps-arm64-10.0-stock-20210518.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
>adb sideload "by4a.setedit22_2018.10.31-18_minAPI11(arm64-v8a,armeabi-v7a,x86,x86_64)(nodpi)_apkmirror.com.apk"
serving: 'by4a.setedit22_2018.10.31-18_minAPI11(arm64-v8a,armeabi-v7a,x86,x86_64)(nodpi)_apkmirror.com.apk' (~47%) adb: failed to read command: No error
>adb shell settings put global development_settings_enabled 1
error: closed
>adb root
adb: unable to connect for root: closed
>adb shell
error: closed
>fastboot --version
fastboot version 31.0.2-7242960
>fastboot devices
09241JEC228869 fastboot
>fastboot flash bootloader sunfish-rq2a.210505.002\bootloader-sunfish-s5-0.3-7062598.img
Sending 'bootloader' (8357 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Any suggestions on how to unlock this device? Then I can flash it and restore it back to stock.
Thanks
PS. Please do not say "tap build number 7 times to enable Developer Mode/options". If you believe this is the solution, please re-read this post, and the linked/German post, then describe a different way of doing that task that doesn't rely on the build number being visible.
mayday175 said:
I recently purchased a used Pixel 4a, and I now understand why the seller was offering such good price for it and why he refused to respond to me now I have it. This phone has ArcanseOS 10 installed, which has only 3 apps installed... Setting, Clock and Calculator. There is no Play Store app, no Phone app, nothing.
The only useful reference to ArcaneOS I can find in the Googleverse is this one... https://translate.google.com.au/tra...rueck-flashen.973774.html&prev=search&pto=aue where the OP describes his troubles with a Pixel 3. Through the rough translation, I see similar issues... can't enable developer mode, can't unlock bootloader, can't sideload apps.
Some random observations about this phone/OS...
- The phone is in good condition. I used the supplied pin code to unlock it and did a factory reset. Have done basic config with my Google Account, etc.
- In Settings > About Phone - the build number is not shown. I cannot tap on the build number 7 times to enable Developer Mode. I have tried tapping everything in About Phone 7+ times, but I have not been able to enable Developer Mode.
- When the phone powers on, the first thing shown is a message like "Your device is loading a differennt operating system".
- The installed OS is ArcaneOS 10. The system updater says that ArcaneOS 11 is available for download (but I don't want to do that in case it makes this thing even harder to fix).
- I tried sideloading open_gapps and a random developer shortcut app I found, but I can't seem to get them to load.
I'm no expert at this, so I've tried various commands that I found and got some of these results...
(note: some details, esp path names, have been edit for brevity)
>adb devices
List of devices attached
09241JEC228869 sideload
>adb shell
error: closed
>adb sideload open_gapps-arm64-10.0-stock-20210518.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
>adb sideload "by4a.setedit22_2018.10.31-18_minAPI11(arm64-v8a,armeabi-v7a,x86,x86_64)(nodpi)_apkmirror.com.apk"
serving: 'by4a.setedit22_2018.10.31-18_minAPI11(arm64-v8a,armeabi-v7a,x86,x86_64)(nodpi)_apkmirror.com.apk' (~47%) adb: failed to read command: No error
>adb shell settings put global development_settings_enabled 1
error: closed
>adb root
adb: unable to connect for root: closed
>adb shell
error: closed
>fastboot --version
fastboot version 31.0.2-7242960
>fastboot devices
09241JEC228869 fastboot
>fastboot flash bootloader sunfish-rq2a.210505.002\bootloader-sunfish-s5-0.3-7062598.img
Sending 'bootloader' (8357 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Any suggestions on how to unlock this device? Then I can flash it and restore it back to stock.
Thanks
PS. Please do not say "tap build number 7 times to enable Developer Mode/options". If you believe this is the solution, please re-read this post, and the linked/German post, then describe a different way of doing that task that doesn't rely on the build number being visible.
Click to expand...
Click to collapse
Bro try using the online flash tool to flash both partitions... Directly go to the bootloader screen and plug in the device... If the firmware not getting detected go to official firmware page of google and copy the version number and paste it.... Make sure you installed minimal adb, 15sec adb installer & Universal adb driver (if using a windows machine)....
https://androiddatahost.com/7uvfn (15 sec adb installer)
https://androiddatahost.com/uq6us (adb minimal installer)
https://github.com/koush/adb.clockworkmod.com/releases/latest/download/UniversalAdbDriverSetup.msi (Universal adb driver)
https://flash.android.com/welcome (flash tool online)
https://developers.google.com/android/images#sunfish (for checking version if device not recognizing the model)
May be I'm silly but try it...
That's strange... You have the boot screen saying that the phone has been modified, yet you seem to have a locked bootloader... Doesn't make any sense to me :/
I saw your adb/fastboot attempts, but I didn't saw "fastboot oem unlock"... I doubt it'll work, but can you give it a try ?
@g0t.milkk - thanks for the feedback... I did try that, must have missed it when I was copy/pasting different text. Basically i get:
>fastboot.exe oem unlock
FAILED (remote: 'Invalid oem command unlock')
fastboot: error: Command failed
(looks to me like someone has modified the boot loader/recovery/fastboot environment so it no longer recognises/supports various commands. I see similar with some adb commands. Looks like this ArcaneOS was not designed to be removed)
@Raj Pandiyan - thanks for that. I'll give it a go. I believe I started with the online tools first, but that was a while ago before I started digging into command based stuff. I don't think this is gunna work, cos the boot loader is lockec... but I'll follow the links you give and give it a try.
After some further testing... @Raj Pandiyan - I already have the latest platform tools from developer.android.com. I looked at the installer links you provided, however I think I already have the ADB tools I need (and from a source that I recognise). The Universal ADB Driver I have already installed. The online flash tool starts by asking for Developer mode to enable usb debugging and OEM unlock. As mentioned, developer mode is not accessible, so enabling these other options is not possible thru the GUI, and therefore flashing this device is not possible... regardless of the tool used to do it.
If anyone knows of another way to crack this one open, I'm willing to give it a go. This device is little more than a fancy paperweight that I'm about to sell for spare parts...
Some more details, if anyone is interested in looking at them... I have placed a number of photos of this phone and a text file with the output from a list of fastboot commands here
EDIT: I've removed the original Google Drive link that I used here (information/privacy leakage)... instead, I have attached some of the same photos directly on this post.
The photos show the phone starting up, the lock screen, the grand total of only 2 apps installed, the setting app, the settings > About Phone (note, thats everything shown there; there is no ability to scroll up or down), some additional details about the phone and OS, the bootloader/fastboot screen, recovery mode and recovery menu and finally the fastboot menu (selected from the recovery menu).
Does anyone know of a more advanced way to force the bootloader unlocked? I have not been able to do it with the methods/commands that I currently know of.
I'm tossing an idea, I don't know if it's even feasable, but can you try "fastboot boot bootloader-sunfish-s5-0.3-7062598.img" ?
Like not flashing, just one time boot with this image ?
@g0t.milkk ... nice idea, thanks for that. However, I got this:
>fastboot.exe boot bootloader-sunfish-s5-0.3-7062598.img
creating boot image...
creating boot image - 8560640 bytes
Sending 'boot.img' (8360 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
(I've added this output to the text file in my GoogleDrive link above)
Does anyone know how to unlock a device that refuses to be unlocked? (or, more accurately, does not recognise the commands telling it to unlock)
Did you try reaching out to Google directly? That URL it points you to (g.co/ABH) expands to https://support.google.com/android/answer/6185381.
What I really don't understand is how you can have a custom OS on a locked device. I didn't think that was even possible? (As in, if you lock the bootloader with a custom OS installed, you get a brick, not ... what you have)
Your bootloader is the oldest released bootloader you can get from Google (eg. factory image): s5-0.2-6281315. Same for the baseband.
The recovery seems to be a bit newer (based on the third released update: 10.0.0 (QD4A.200805.003, Aug 2020) - Not the "JP or Verizon" version.
I guess you can't find anything that resembles "developer mode" (clicking on all those things in the About screen)? And I guess you'd need that to even think about unlocking the bootloader. Maybe Google's got some magic way around that? (hence the first link)
So odd that there's no mention of ArcaneOS on the internet... maybe the guy who sold you the phone was trying to make the next great custom ROM and ... failed?
Maybe this is a longshot... but the recovery lets you install an OTA. Maybe you can grab a Pixel 4a full ota (https://developers.google.com/android/ota) and load that through the recovery? You'd need to get it onto the device though... hopefully USB transfers are working, since there's no apps to let you pull it down over wifi.
I have the same thing.
A friend got a used pixel 4a and it's running arcaneos with the same issues described by the OP
Nothing works when attempting to flash.
No idea how it has some broken custom rom with a locked bootloader...
mayday175 said:
mayday175 said:
I recently purchased a used Pixel 4a, and I now understand why the seller was offering such good price for it and why he refused to respond to me now I have it. This phone has ArcanseOS 10 installed, which has only 3 apps installed... Setting, Clock and Calculator. There is no Play Store app, no Phone app, nothing.
The only useful reference to ArcaneOS I can find in the Googleverse is this one... https://translate.google.com.au/tra...rueck-flashen.973774.html&prev=search&pto=aue where the OP describes his troubles with a Pixel 3. Through the rough translation, I see similar issues... can't enable developer mode, can't unlock bootloader, can't sideload apps.
Some random observations about this phone/OS...
- The phone is in good condition. I used the supplied pin code to unlock it and did a factory reset. Have done basic config with my Google Account, etc.
- In Settings > About Phone - the build number is not shown. I cannot tap on the build number 7 times to enable Developer Mode. I have tried tapping everything in About Phone 7+ times, but I have not been able to enable Developer Mode.
- When the phone powers on, the first thing shown is a message like "Your device is loading a differennt operating system".
- The installed OS is ArcaneOS 10. The system updater says that ArcaneOS 11 is available for download (but I don't want to do that in case it makes this thing even harder to fix).
- I tried sideloading open_gapps and a random developer shortcut app I found, but I can't seem to get them to load.
I'm no expert at this, so I've tried various commands that I found and got some of these results...
(note: some details, esp path names, have been edit for brevity)
>adb devices
List of devices attached
09241JEC228869 sideload
>adb shell
error: closed
>adb sideload open_gapps-arm64-10.0-stock-20210518.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
>adb sideload "by4a.setedit22_2018.10.31-18_minAPI11(arm64-v8a,armeabi-v7a,x86,x86_64)(nodpi)_apkmirror.com.apk"
serving: 'by4a.setedit22_2018.10.31-18_minAPI11(arm64-v8a,armeabi-v7a,x86,x86_64)(nodpi)_apkmirror.com.apk' (~47%) adb: failed to read command: No error
>adb shell settings put global development_settings_enabled 1
error: closed
>adb root
adb: unable to connect for root: closed
>adb shell
error: closed
>fastboot --version
fastboot version 31.0.2-7242960
>fastboot devices
09241JEC228869 fastboot
>fastboot flash bootloader sunfish-rq2a.210505.002\bootloader-sunfish-s5-0.3-7062598.img
Sending 'bootloader' (8357 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Any suggestions on how to unlock this device? Then I can flash it and restore it back to stock.
Thanks
PS. Please do not say "tap build number 7 times to enable Developer Mode/options". If you believe this is the solution, please re-read this post, and the linked/German post, then describe a different way of doing that task that doesn't rely on the build number being visible.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I got mine working.
You'll need to use the GrapheneOS Web Installer to fix it up.
GrapheneOS web installer
Web-based installer for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
Get your device into fastboot/bootloader mode, and use the unlock bootloader option.
Then run through the rest of the installation steps up until the relock bootloader option. Don't relock the bootloader.
Then boot into the OS.
Once I did this, I was then able to boot back to bootloader and flash the factory image.
Device works just fine now.
ArcaneOS must have been a short-lived custom rom - originally recovery said ArcaneOS Recovery, then after GrapheneOS flashed, recovery was called GrapheneOS recovery.
I had a same problem but I solved it with unlocking bootloader and flashing Factory Image.
put device in bootloader mode
run fastboot flashing unlock
downloaded sunfish-rq3a.210605.005-factory-be541467.zip and unzip
run flash-all.bat
make sure you have Minimal fastboot and adb
done
Thanks for the feedback everyone... I was about to give up until this recent rush of comments. Let me respond to some of them...
@a1291762 - Yes, I saw and followed that link. However, I have not yet reached out to Google support or their forums. I will need to try that next.
@shaitan667 - thanks for that suggestion. However, the GrapheneOS instructions say to first enable OEM unlocking, which requires access to Developer options, which (as mentioned) there is no entry point within the GUI. Equivalent fastboot commands fail... see the text file located at my GoogleDrive link provided above. That said, I tried this anyway and got the message "Error: Bootloader was not unlocked, please try again!" when clickingn in the "unlock bootloader" button. I can only assume you were lucky enough to have your phone already OEM unlocked.
@Kubanac - As mentioned, unlocking commands do not work... see the text file located at my GoogleDrive link.
Further on this last point... the command and response is:
>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
The interesting part is the "remote" feedback... this is confirmation that the phone has received the fastboot command while in fastboot mode, and explicitly says (ie. the phone itself says) that is does not recognise the command. Similarly...
>fastboot oem unlock
FAILED (remote: 'Unknown OEM command')
fastboot: error: Command failed
I believe this is for older Google phones... here my phone is telling me it does not recognise the "oem" command and, in turn, does not recognise any of the oem sub-commands (like "unlock").
How do you unlock a phone that does not recognise the unlock command?
How do you access developer options where there is no GUI access to them?
How do you sideload an alternate app to access developer options when you can't sideload apps?
Maybe the answer to that last question might provide a possible solution... however, when I try to sideload an app, I see...
>adb.exe sideload "Developer Options Shortcut_v2.7.0_apkpure.com.apk"
serving: 'Developer Options Shortcut_v2.7.0_apkpure.com.apk' (~2%) adb: failed to read command: No error
and on the phone it says (edited for brevity)...
E: footer is wrong
E: Signature verification failed
E: error: 21
I have tried a few apps and always seem the same. Maybe I need to try another app?
I have added to my GoogleDrive some more photos and an "adb commands.txt" of this issue.
Edit: Also, what about the "Rescue" mode? I've tried many things in fastboot and recovery mode, but I don't know much about the rescue mode. Could it be useful in this situation?
Edit 2: Google Support was of no assistance. They advised to do what I have already done, then repeatedly said their "assistance is limited due to this device being rooted". (ha! pardon the pun... depending on your local language, "rooted" may have multiple meanings... in my Aussie slang, that also means its stuffed, buggered... and other translations inappropriate for this forum).
mayday175 said:
Thanks for the feedback everyone... I was about to give up until this recent rush of comments. Let me respond to some of them...
@a1291762 - Yes, I saw and followed that link. However, I have not yet reached out to Google support or their forums. I will need to try that next.
@shaitan667 - thanks for that suggestion. However, the GrapheneOS instructions say to first enable OEM unlocking, which requires access to Developer options, which (as mentioned) there is no entry point within the GUI. Equivalent fastboot commands fail... see the text file located at my GoogleDrive link provided above. That said, I tried this anyway and got the message "Error: Bootloader was not unlocked, please try again!" when clickingn in the "unlock bootloader" button. I can only assume you were lucky enough to have your phone already OEM unlocked.
@Kubanac - As mentioned, unlocking commands do not work... see the text file located at my GoogleDrive link.
Further on this last point... the command and response is:
>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
The interesting part is the "remote" feedback... this is confirmation that the phone has received the fastboot command while in fastboot mode, and explicitly says (ie. the phone itself says) that is does not recognise the command. Similarly...
>fastboot oem unlock
FAILED (remote: 'Unknown OEM command')
fastboot: error: Command failed
I believe this is for older Google phones... here my phone is telling me it does not recognise the "oem" command and, in turn, does not recognise any of the oem sub-commands (like "unlock").
How do you unlock a phone that does not recognise the unlock command?
How do you access developer options where there is no GUI access to them?
How do you sideload an alternate app to access developer options when you can't sideload apps?
Maybe the answer to that last question might provide a possible solution... however, when I try to sideload an app, I see...
>adb.exe sideload "Developer Options Shortcut_v2.7.0_apkpure.com.apk"
serving: 'Developer Options Shortcut_v2.7.0_apkpure.com.apk' (~2%) adb: failed to read command: No error
and on the phone it says (edited for brevity)...
E: footer is wrong
E: Signature verification failed
E: error: 21
I have tried a few apps and always seem the same. Maybe I need to try another app?
I have added to my GoogleDrive some more photos and an "adb commands.txt" of this issue.
Edit: Also, what about the "Rescue" mode? I've tried many things in fastboot and recovery mode, but I don't know much about the rescue mode. Could it be useful in this situation?
Edit 2: Google Support was of no assistance. They advised to do what I have already done, then repeatedly said their "assistance is limited due to this device being rooted". (ha! pardon the pun... depending on your local language, "rooted" may have multiple meanings... in my Aussie slang, that also means its stuffed, buggered... and other translations inappropriate for this forum).
Click to expand...
Click to collapse
Try fastboot from this toolkit https://androiddatahost.com/hhetd
@Kubanac - I do not understand how that will help. I have already downloaded, and have been using, the latest developer tools from developer.android.com... release 31.0.2. Plus, the version of the fastboot executable on my local pc is not the issue here... reviewing the information provided, you will see that the phone itself is sending a command denied or unrecognised response to may of the commands I send to it. A different fastboot executable will not change the commands that this phone does or does not recognise.
However, is there a useful command that I have not yet tried? (see the text files in my Google Drive link for most commands that I have tried).
Is there anything I could do while in Recovery or Rescue mode? (my understanding is that Rescue mode is a relatively new feature... I don't know what access or commands are available there). Any help from anyone is greatly apreciated.
Bro I'm telling you, I was in the same situation as you. That GrapheneOS web installer *WILL* unlock the bootloader if you are unable to enable OEM unlocking .
@shaitan667 - I tried the GrapheneOS web installer again... I got the same response as last time... "Error: Bootloader was not unlocked, please try again!" while using the current version of Google Chrome, and same for the current version of MS Edge. The instructions on the web installer page clearly say "OEM unlocking needs to be enabled from within the operating system."... which I can't do from within the GUI. I can only assume you were fortunate for this to work, while I am not.
Try to flash stock images from linux. Someone relocked bootloaer after installing custom ROM. Also try from linux to unlock bootloader..
follow the instructions on the Google site. I wouldn't try any other instructions until you get a phone back to the factory condition using Google's instructions.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Hi there. We want to install f-droid on HTC U11 on Android 9. Function to enabling 'Unknown Sources' or 'Install Unknown Apps' isn’t available in dev mode!
We reckon you have to unlock the device to install f-droid. Unless spending already many hours we get stucked. Situation: Dev mode enabled + OEM unlocked
Installed Android File Transfer on Linux Mint 19.2 https://www.omgubuntu.co.uk/2017/11/android-file-transfer-app-linux device is shown on pc.
Made account on HTC website. https://www.htcdev.com/bootloader/unlock-instructions
Used Android_File_Transfer-cce42ee-x86_64.AppImage + executed
Started mobile in "download mode" went to ‘fastboot mode”
PC doesn’t show U11 in cli lsblk
Fastboot oem get_identifier_token - FAILED (remote: unknown command)
How on earth can one unlock this device?
[GUIDE] [LINUX] Installing ADB and Fastboot on Linux & Device Detection "Drivers"
[GUIDE] [LINUX] Installing ADB and Fastboot on Linux & Device Detection "Drivers" Installing ADB and Fastboot on Linux & ADB Drivers Tutorial For Debian-based distributions (Debian Ubuntu Mint etc.) Installing ADB CLI tool ( Android Debug Bridge...
forum.xda-developers.com
Hi Golv, we followed instructions in the link given. Now 1 step further we are stucked again. Could you please have a look on our comment here:
https://forum.xda-developers.com/t/...linux-device-detection-drivers.3478678/page-2
Well I bought this Calypso U318AA from a friend for cheap. It was his sons he got new phone. I bought it to root it. I was just going to do the magical root.. I've rooted several other phones in past. The world wide web has very little info well, no info on this thing. It's a Android 10. I'm not sure of even the best way to unlock the bootloader. I know it doesn't have nothing in developers options. On recovery reboot you can do a recovery boot and a fastboot as well as normal boot. Can't find anything but factory at&t stuff. So any info would be great. Thank you
dorkxperience said:
Well I bought this Calypso U318AA from a friend for cheap. It was his sons he got new phone. I bought it to root it. I was just going to do the magical root.. I've rooted several other phones in past. The world wide web has very little info well, no info on this thing. It's a Android 10. I'm not sure of even the best way to unlock the bootloader. I know it doesn't have nothing in developers options. On recovery reboot you can do a recovery boot and a fastboot as well as normal boot. Can't find anything but factory at&t stuff. So any info would be great. Thank you
Click to expand...
Click to collapse
I just received this phone from at&t. Found out mtk_client will unlock bootloader. so magisk root "should be" available after this unlock. I have not tried yet , i only unlocked bootloader earlier today. will keep looking for anyone else trying this and update as i find any info.
Twrp is working (mostly) for TINNO U318AA. (ATT&T Calypso)
still need to work out data decryption, and FatsbootD mode.
Device Tree: https://github.com/mrmazakblu/twrp-device-att_u318aa/tree/twrp-11
Device Dump: https://github.com/mrmazakblu/att_u318aa_dump
mrmazak said:
Twrp is working (mostly) for TINNO U318AA. (ATT&T Calypso)
still need to work out data decryption, and FatsbootD mode.
Device Tree: https://github.com/mrmazakblu/twrp-device-att_u318aa/tree/twrp-11
Device Dump: https://github.com/mrmazakblu/att_u318aa_dump
Click to expand...
Click to collapse
Phh aoap gsi a11 installs and runs good
mrmazak said:
Phh aoap gsi a11 installs and runs good
Click to expand...
Click to collapse
To clarify, let me tel you all which build version i have installed and outline the steps to get it loaded.
THIS IS NOT INTENDED TO BE STEP BY STEP GUIDE ONLY AN OVERVIEW
WHATEVER YOU DO ON YOUR DEVICE IS AT YOUR OWN RISK
system-squeak-arm32_binder64-ab-vndklite-vanilla
downloaded from :
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
!. Bootloader must be unlocked.
AT&T removed the enable OEM unlock from developer menu, but there is an excellent work around 'tool' to get around this.
MTK CLIENT will allow you to read (pull) stock firmware off from phone, much like spflash tool does, except with this phone and many other newer phones the manufacture has enabled security and authorization files to block sp flash tool , SOOOO, tools like mtk client try to stay a step ahead.
I only used the GUI options with the client, it was very user friendly , the tool has way more options than i needed to mess with.
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
2. Before flashing gsi, make sure you have pulled firmware from phone, so you have stock super.img. If you don't you will not be able to restore device when / if you mess up the vendor partition.
3. I disabled vbmeta verification .
will need stock vbmeta from pulled firmware.
boot into bootloader, (adb reboot bootloader , or reboot while holding the volume up button. You should get a boot menu)
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(the last part need to point to you file location where ever it is)
4. Now we need to move from bootloader to fastboot. fastboot reboot command didn't work for me so needed to boot recovery first, then fastboot.
Code:
fastboot reboot
hold volume up button to get boot menu, select recovery
from recovery select reboot fastboot
in the fastbootd connection you will be able to flash gsi
the system area is not large enough to fit gsi , so you will need to remove the /product partition.
Code:
fastboot delete-logical-partition product
fastboot flash system system-squeak-arm32_binder64-ab-vndklite-vanilla.img
once completed use the screen menu to reboot back to recovery and perform factory reset.
With the exception of needing to use mtk client, the rest of these steps are standard android process. documented in many locations. I go to the android source first for information. \
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Thanks a lot mrmazak, I'm working on a step by step guide for newbies like me to expand on your steps to unblock and reflash the phone.
I was able to use MRK Client, unlock bootloader and put the phone in fastboot.
The problem I have is to find the right MediaTek driver for the device USB\VID_0E8D&PID_201C
Where did you find them? I tried Google USB driver from ADP but they use different Device ID and all MediaTek driver with same VendorID 08ED have old ProductID instead of 201C.
Any help on MediaTek driver so I can finish the guide and post the link here?
Specifically, I was able to connect via ADB but Fastboot requires a different driver which I'm not able to find
Thanks a lot for your help!
mrmazak said:
I just received this phone from at&t. Found out mtk_client will unlock bootloader. so magisk root "should be" available after this unlock. I have not tried yet , i only unlocked bootloader earlier today. will keep looking for anyone else trying this and update as i find any info.
Click to expand...
Click to collapse
Thats awesome thanks
inglele said:
Thanks a lot mrmazak, I'm working on a step by step guide for newbies like me to expand on your steps to unblock and reflash the phone.
I was able to use MRK Client, unlock bootloader and put the phone in fastboot.
The problem I have is to find the right MediaTek driver for the device USB\VID_0E8D&PID_201C
Where did you find them? I tried Google USB driver from ADP but they use different Device ID and all MediaTek driver with same VendorID 08ED have old ProductID instead of 201C.
Any help on MediaTek driver so I can finish the guide and post the link here?
Specifically, I was able to connect via ADB but Fastboot requires a different driver which I'm not able to find
Thanks a lot for your help!
Click to expand...
Click to collapse
Did not have to install any drivers special.
mrmazak said:
Did not have to install any drivers special.
Click to expand...
Click to collapse
Yes, I had Other \ Android device listed in Device Manager, so I tried disable signed driver and force install of these drivers: https://forum.xda-developers.com/t/...32-64-bit-driver-install-tutorial-m2.3267033/
Now, I have it visible as MediaTek PreLoader USB VCOM Port but if I type "fastboot devices" is not listed.
ADB is able to see it correctly:
adb devices
List of devices attached
AYMB5PKZCUEUUOSC device
When I restart in fastboot with "adb reboot bootloader" the phone restart correctly in fastboot.
I'm not able to unblock the connection between fastboot tool and phone in fastboot mode, I suspect due to missing / wrong driver.
If you have any idea, it would be great!
Found the correct driver. I needed to force Google ADB Driver -> "Android Bootloader Interface" and it works!
They are available here: https://developer.android.com/studio/run/win-usb
Thanks for the help and sorry for confusion, newbie questions
Mod Edit: Quote removed since post deleted.
I received 'not enough space" error when flashed gsi, this is why i delete product partition.
I recall there are fastboot commands to list super.img size, but not sure for super sub-partiton size. there are tools to extract the sub-partitons and it will show individual size.
there must be commands for it in fastboot i think, But i do not know them.\
They deleted the previous post, so I'm copy paste the steps from the blog post.
Pre-requirements
Tested on Windows 11, it should work on any previous Windows versions
Install MTK Client to unlock bootloader: Inofficial MTK reverse engineering and flash tool – which requires Python 3.9 and Git – Downloading Package (git-scm.com) and UsbDk
Download phone image system-squeak-arm32_binder64-ab-vndklite-vanilla.img.gz from Release AOSP 12.1 v410 · phhusson/treble_experimentations
Download Android DevelopersSDK Platform Tools | Android Developers
Download Google USB Driver | Android Developers
Unlock phone bootloaderBootloader must be unlocked to install the new firmware.
MTK CLIENT will allow you to read stock firmware off from phone, except with this phone the manufacture has enabled security and authorization files to block sp flash tool.
Install Python 3.9 from Microsoft Store and Git – Downloading Package and daynix/UsbDk · GitHub, then open a CMD:
mkdir C:\test
cd C:\test
git clone https://github.com/bkerler/mtkclient
cd mtkclient
pip3 install -r requirements.txt
Once installation in complete, start MTK Client with
c:\Test\mtkclient
python mtk_gui
To activate BRUM mode for the phone and connect it to MKT Client
Turn off the phone if it’s on.
Press Volume UP + Volume DOWN and plug the USB cable.
Do not press power button and MKT Client will detect it.
Backup:
In the Read partition tab,
Select all of them and Save to C:\Test\Firmware\Original
It will take about 40min to complete all the operation
Unlock Bootloader
In Flash Tools tab,
Click on Unlock bootloader button
Debug log will show Bootloader: unlock and python windows list
sej - HACC init
sej - HACC run
sej - HACC terminate
sej - HACC init
sej - HACC run
sej - HACC terminate
Progress: |██████████████████████████████████████████████████| 100.0% Write (Sector 0x1 of 0x1, ) 0.03 MB/s
If you restart the phone, you will see a warning that bootloader is unlocked and it will ask you to factory reset the phone.
Install the new firmwareYou need to have Android DevelopersSDK Platform Tools | Android Developers installed to be able to flash the new firmware.
Enable USB Debugging in the phone and connect ADB
Start the phone
Perform a Factory Reset
Restart the phone and complete the initial wizard
Open Settings -> “About Phone” -> Tap the “Build Number” item seven times.
You should get a message saying you are now a developer.
Settings -> “System” -> “Advanced” -> “Developer Options.”
Open the menu and enable “USB Debugging.”
To verify that ADB in installed correctly and is able to connect to the device:
CD C:\Test\Tools
adb version
Android Debug Bridge version 1.0.41
Version 33.0.1-8253317
Installed as C:\Test\Tools\adb.exe
adb devices
List of devices attached
AYMB5PKZCUEUUOSC device
Boot into fastboot with the following command adb reboot bootloader
or reboot while holding the volume up button and select fastboot.
Install Google ADB FastBoot driver in Windows 11Download Google USB Driver | Android Developers as they will be needed to connect the device via fastboot. To install the driver, we need to force the installation in Device Manager with these steps:
Open Device Manager
Right click on Other Devices \ Android device
Select “Update Driver” -> “Browse my computer for drivers” -> “Let me pick from the list of available driver“
Select “Show All Devices” -> “Have Disk“
Navigate to “C:\Test\Tools\usb_driver_r13-windows” and let Windows load the drivers
Select “Android Bootloader Interface” as driver name
Test that Fastboot tool is able to interact with the phone
CD C:\Test\Tools
fastboot devices
AYMB5PKZCUEUUOSC fastboot
Next step is to disable vbmeta verification with the following steps:
Firmware update via Fastboot
While the phone is in the FastBoot mode, type the following:
CD C:\Test\Tools
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta "C:\Test\Firmware\Original\vbmeta.bin"
target reported max download size of 134217728 bytes
sending 'vbmeta' (8192 KB)... OKAY [ 0.204s]
writing 'vbmeta'... OKAY [ 0.189s]
finished. total time: 0.393s
After vbmeta image is flashed, perform:
fastboot reboot fastboot to restart the phone and enter fastbootd
Check the phone is connecting correctly with fastboot devices
and force the installation of Android Bootloader Interface in Device Manager if needed.
The following step delete product partition so system partition has enough space:
fastboot delete-logical-partition product
Deleting 'product' OKAY [ 0.016s]
Finished. Total time: 0.016s
This command flash the custom rom on system partition:
fastboot flash system "C:\Test\Firmware\system-squeak-arm32_binder64-ab-vndklite-vanilla.img"
Invalid sparse file format at header magic
Resizing 'system' OKAY [ 0.016s]
Sending sparse 'system' 1/5 (255489 KB) OKAY [ 14.939s]
Writing 'system' OKAY [ 7.651s]
Sending sparse 'system' 2/5 (262100 KB) OKAY [ 15.141s]
Writing 'system' OKAY [ 7.705s]
Sending sparse 'system' 3/5 (262104 KB) OKAY [ 15.001s]
Writing 'system' OKAY [ 7.595s]
Sending sparse 'system' 4/5 (261825 KB) OKAY [ 14.752s]
Writing 'system' OKAY [ 7.711s]
Sending sparse 'system' 5/5 (183741 KB) OKAY [ 10.421s]
Writing 'system' OKAY [ 5.832s]
Finished. Total time: 107.885s
Once flash of new rom is completed, you can restart the phone and it will boot using the new rom.
Original post suggested to perform a factory reset.
WARNING: In my case, a factory reset caused a reboot loop and was not able to
If you want to proceed, in the menu on the screen:
Select “Enter recovery” and
Select “Wipe data/factory reset“
Screen on the phone will show
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /metadata...
Data wipe completed.
If you missed the previous screen, or clicked the wrong button/option:
restart the phone holding Volume UP,
Select fastboot on the phone
Type fastboot reboot fastboot to reenter fastbootd screen
And repeat the factory reset
Restart the phone and you are up and running.
Restore original firmwareIf you need to restore original rom, use MKT Client tool to write:
vbmeta.bin
super.bin
then close the tool and restart the phone. It will be like new
hi! hope i can get some help. this is my first time using mtkclient but i can't seem to get it to detect the phone. i'm making sure to follow the steps listed of having the phone off first, then press both volume buttons and plug in the usb. on the phone it eventually pulls up a "select boot mode" where i can use the volume buttons to select recovery mode fastboot mode or normal mode boot. i've tried recovery and fast boot modes as well as just leaving it on that select screen but nothing is detected in mtkclient
thanks!
New to the world of droid but am familiar with modding stuff so I'm a semi-noob I suppose. Found myself getting one of these things from the local dollar general and followed this guide to get rid of all the google crap and hopefully speed it up a bit. Bootloader is unlocked, .img posted above is flashed, and it boots up and seemingly works. Can't figure out how to sideload apps nor can I find any type of write up explaining what to do with the tree and dump file posted above. Any help and/or clarification, greatly appreciated. MTKClient, ADB, and Fastboot are all installed and functional. Using Linux Manjaro.
--chuckles b
ltk6260 said:
hi! hope i can get some help. this is my first time using mtkclient but i can't seem to get it to detect the phone. i'm making sure to follow the steps listed of having the phone off first, then press both volume buttons and plug in the usb. on the phone it eventually pulls up a "select boot mode" where i can use the volume buttons to select recovery mode fastboot mode or normal mode boot. i've tried recovery and fast boot modes as well as just leaving it on that select screen but nothing is detected in mtkclient
thanks!
Click to expand...
Click to collapse
Run mtkclient. With the phone already off, hold down both volume buttons and connect the phone to your computer. You should hear the "usb connected" notification sound on your computer and mtkclient will pick up it. As soon as you hear that chime, release the buttons, set the phone down, and don't touch it. The screen shouldn't come on during this step.
Make sure you're ONLY holding down the volume buttons and plugging it in. Don't touch the power button.
If you're still having issues with it not picking up your phone, go through the standard troubleshooting steps: Recheck you followed every step, restart your computer, try other USB ports, try other cables.
*********
FYI this isn't applicable to this process, but should be noted: This phone has a weird way to get into the recovery menu. You have to hold Vol+ and Power, then select Recovery from the menu, THEN immediately press and hold the Vol+ (or Vol- I don't recall at the moment) and Power buttons again until the recovery menu comes up
veryspecialagent said:
Run mtkclient. With the phone already off, hold down both volume buttons and connect the phone to your computer. You should hear the "usb connected" notification sound on your computer and mtkclient will pick up it. As soon as you hear that chime, release the buttons, set the phone down, and don't touch it. The screen shouldn't come on during this step.
Make sure you're ONLY holding down the volume buttons and plugging it in. Don't touch the power button.
If you're still having issues with it not picking up your phone, go through the standard troubleshooting steps: Recheck you followed every step, restart your computer, try other USB ports, try other cables.
*********
FYI this isn't applicable to this process, but should be noted: This phone has a weird way to get into the recovery menu. You have to hold Vol+ and Power, then select Recovery from the menu, THEN immediately press and hold the Vol+ (or Vol- I don't recall at the moment) and Power buttons again until the recovery menu comes up
Click to expand...
Click to collapse
Thanks! that did help.
i was able to get all the way through up to flashing the new rom. I'm getting this error:
fastboot flash system system-squeak-arm32_binder64-ab-vndklite-vanilla.img
Invalid sparse file format at header magic
Resizing 'system' OKAY [ 0.013s]
error: write_sparse_skip_chunk: don't care size 201668900 is not a multiple of the block size 4096
Sending sparse 'system' 1/2 (262140 KB) error: write_sparse_skip_chunk: don't care size 201668900 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 201668900 is not a multiple of the block size 4096
OKAY [ 12.568s]
Writing 'system' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
still can't get past this error. i've confirmed my filename, file extensions, and file location. even checked file permissions. the img file is in the same folder as the fastboot command itself.
i also tried the command using the full c:\ path to the img file but it fails the same.
i then restored the phone to the original super.bin and the phone worked like normal. so i went all the way back through the steps starting from the top but failed at the same final step flashing the system.
ltk6260 said:
still can't get past this error. i've confirmed my filename, file extensions, and file location. even checked file permissions. the img file is in the same folder as the fastboot command itself.
i also tried the command using the full c:\ path to the img file but it fails the same.
i then restored the phone to the original super.bin and the phone worked like normal. so i went all the way back through the steps starting from the top but failed at the same final step flashing the system.
Click to expand...
Click to collapse
What are you trying to do? What is the purpose or end result you're hoping to achieve?
I ask because this thread is a bit convoluted and "noobs" looking to just root and tinker might come in thinking they have to do all the steps in this thread to get there.
Like someone wanting an oil change overhearing two mechanics rebuilding a transmission, taking notes, especially where they mentioned "oil," then walking away thinking that's what they need to do.
The tools linked above are great. The mtk one, once I was able to get it running, was how I got past the FRP. For anyone wondering, there's an FRP partition that you can just delete with the tool.
If you're just wanting root, see above for unlocking the bootloader, then stop. I'm 90% certain I achieved root by just following the process outlined the official Magisk page on GitHub.
Can I get some OP/MOD thoughts on breaking this thread up into specific guides with the purpose clearly written in the title?
veryspecialagent said:
What are you trying to do? What is the purpose or end result you're hoping to achieve?
I ask because this thread is a bit convoluted and "noobs" looking to just root and tinker might come in thinking they have to do all the steps in this thread to get there.
Like someone wanting an oil change overhearing two mechanics rebuilding a transmission, taking notes, especially where they mentioned "oil," then walking away thinking that's what they need to do.
The tools linked above are great. The mtk one, once I was able to get it running, was how I got past the FRP. For anyone wondering, there's an FRP partition that you can just delete with the tool.
If you're just wanting root, see above for unlocking the bootloader, then stop. I'm 90% certain I achieved root by just following the process outlined the official Magisk page on GitHub.
Can I get some OP/MOD thoughts on breaking this thread up into specific guides with the purpose clearly written in the title?
Click to expand...
Click to collapse
I understand your questioning. I'm trying to unlock and load aosp firmware, or frankly, anything other than what this device is loaded with since it's horribly bloated, slow and periodically unstable. this is a play phone, i have two of these phones actually.
ltk6260 said:
I understand your questioning. I'm trying to unlock and load aosp firmware, or frankly, anything other than what this device is loaded with since it's horribly bloated, slow and periodically unstable. this is a play phone, i have two of these phones actually.
Click to expand...
Click to collapse
So is mine. I agree with the bloat, which I thought was weird considering the Android 10 version it comes with (Go) is supposed to be a more streamlined version for lower end phones that lack the processing power.
I tend to not do new ROMs unless it's something with a track record and support like Lineage, but after playing around with it and testing some of the functions with things like WIGL, Termux, LSposed, etc, I'm thinking it might be a good Nethunter phone.
After some extensive Googling, and since I doubt this falls under the "you're flashing the wrong build/version" because there's only one variant of this phone, I'd say it might be possible you're not running the right SDK platform package.
Start Android Studio, go to Settings > Appearance & Behavior > System Settings > Android SDK and make sure you have the right platform packages installed (i.e. Android 10, API 29) and updated.