Related
I have an HTC A9 (mid: 2PQ910000 / cid: VODAP001) which is S-ON currently. Up until yesterday it was running OEM HTC Nougat. I attempted to downgrade it to MM so I could run LineageOS using the VodaPhone 1.27.161.6 zip in collection thread (hxxps://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344). Per the instructions in Post #2 I was able to edit partion 28 but when I attempt to actually flash the .zip both via the "SDCARD Method" and via the "rebootRUU Method" I get the cool errors below. Does anyone have any ideas? Or did I hose this real good? I should also mention the bootloader is unlocked and I do have TWRP flashed. I would be happy if I could get back to factory and ideally I'd like to get it so I can get Sunshine and get S-OFF so I can not worry about this kind of thing in the future.
[SDCARD Method Error]
12 RU_ZIP_ERROR
12 RU_ZIP_ERROR
FAIL 12 RU_ZIP_ERROR
[rebootRUU Method Error (Ubuntu Linux using htc_fastboot)]
sending 'zip' (1886913 KB)... FAILED (remote: data too large, 1932198913 > 939151360)
[rebootRUU Method Error (Win10Pro using htc_fastboot)]
load_file: could not allocate 1932198913 bytes
I was able to get this to downgrade to MM (1.27.161.6) but from there I was not able to get LineageOS (lineage-14.1-20170704-nightly-hiaeuhl-signed) to boot. It would keep dropping to the HBOOT screen. In case anyone else ends up with the sweet boot loop I ended up in I have listed what I did below in the unlikely event it helps someone.
1) Grab the 1.27.161.6 zip
2) Grab the RUU decryptor (hxxps://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928)
3) Using the RUU decryptor decrypt the zip file above. Grab the "boot.img" and "system.img" files in the "OUT_2PQ_[version]\system" folder.
4) Flash TWRP to the recovery partition
5) Boot into TWRP and flash the "boot.img" file to the boot partition and the "system.img" to the system partition. For whatever reason, my phone rebooted twice and on the third boot went to safe mode. I was trying to shut it down, so I may have forced it to safe boot. Regardless after one more boot it looks like everything is working with the older MM stock.
Maybe in a few days I will try to get S-OFF using Sunshine. For now I'm just glad to have a working phone again.
I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.
prestonmcafee said:
I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.
Click to expand...
Click to collapse
By a generic system image, you are referring to wanting to install an aosp image (treble ROM), correct?
Yes.
prestonmcafee said:
Yes.
Click to expand...
Click to collapse
And obviously you still have your bootloader unlock code?
Also what Mate 9 version do you have and what exact firmware is it running?
I can help ya out no problem. Just obviously want to make sure you avoid going through that again
Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.
Sorry, MHA-L29 8.0.0.360 (C567)
prestonmcafee said:
Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.
Click to expand...
Click to collapse
Oh...You're already bootloader unlocked that makes it even easier.
I'm using the system.IMG form the thread below this paragraph. Tried a few different aosp ROMs and it seems to be the best so far. Aside from a couple things of course. And the honor 8 Pro is the same CPU, GPU found in the mate 9.
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564.
In the main post of that thread, just follow step 2 and 3 and you'll be good to go for having an aosp ROM.
As for magisk/root... You can follow my guide below that I posted the other day. Just let the aosp ROM boot up once first. Also I can extract the ramdisk.IMG you'll need if you can't once you check it over.
https://forum.xda-developers.com/mate-9/how-to/guide-install-magisk-mate-9-running-t3773878
Basically in a nutshell to get setup on an aosp ROM is as follows
1 Download the ROM from the first thread i posted
2 Extract the system.img to where your adb folder is
3 Run command prompt from there
4 With your phone powered off. Hold the volume up button and connect it to your computer (fastboot screen)
5 Run command fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset
8 Reboot the phone and should be good to go
Need to do first boot on its own before rooting
Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?
prestonmcafee said:
Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?
Click to expand...
Click to collapse
Yeah, fairly happy about it. A few bugs though but nothing major. Get better standby drain and about the same SOT time as EMUI. The only thing that is lacking is the camera in aosp doesn't use both cameras.
There is the stock camera port (works with magisk) but it's lacking a few things like video recording doesn't work... And umm not sure what else.
I needed to install an update, enable developer options and enable OEM unlocking (which was greyed out) before it would install. Here is my earlier post:
Dang, didn't work. Here is what I did.
-reset phone, but did not enable developer options.
-extracted and placed system.img in the minimal fastboot and adb folder. Ran a command prompt with administrative rights (win 10)
-shut off and connected Huawei mate 9 by USB, holding vol up
-vol up brought the EMUI restore screen. Shut off and tried again, same outcome. So shut off and tried vol down, and that brought up the fastboot screen. It reported phone unlocked but FRP locked.
-ran command "fastboot flash system system.img" and get:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 11.167s]
writing 'system' 1/4...
FAILED (remote: Command not allowed)
finished. total time: 11.183s
I suspect this is due to the FRP locked condition.
Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!
prestonmcafee said:
Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!
Click to expand...
Click to collapse
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?
OK, now that I have it up and running, here is the procedure I used, fixing what are either typos or variations because my system was slightly different. I unlocked the bootloader using instructions from:
http://www.teamandroid.com/2017/04/08/huawei-mate-9-unlock-bootloader/
I used Minimal ADB and Fastboot from
https://forum.xda-developers.com/showthread.php?t=2317790
I downloaded and extracted the system image from the link Wirmpolter provided:
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564
Here is a slightly edited set of instructions that worked for me:
a. unlock bootloader
b. reset phone
c. enable developer mode (settings/system/about phone tap on build number until developer mode is enabled), enable OEM unlock and USB debugging
d. check that FRP unlock and bootloader unlock worked by booting into fastboot screen (for me, hold VOL DOWN while booting)
1 Download the ROM from the thread above
2 Extract the system.img to where your adb folder is
3 Run command prompt from there (or use MA&F's desktop icon, which does the same thing)
4 With your phone powered off. Hold the volume DOWN button and connect it to your computer (fastboot screen)
5 Run command: fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset [eRecovery didn't have this option, so I rebooted a couple of times while holding vol up and it eventually gave me the option to factory reset]
8 Reboot the phone and should be good to go
Up and Running!
Wirmpolter said:
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?
Click to expand...
Click to collapse
I'm up and running. Thanks! So far, the only glitches are:
While Android can see and format the SD card (a Samsung 64GB), the SD card is invisible over a USB connection and Google Maps and my music player can't see it. File explorer and copy files to the SD card, so the SD card works.
The camera is terrible, but you have a fix for that.
I'm quite lost about how to install Magisk and a camera module
At the risk of asking too much, I have another request. I'm looking at how to install the stock camera on my Mate 9 with the AOSP, and here is my pathetic understanding of the steps.
First, I looked at your (Wirmpolter) instructions:
1. Install latest Magisk Manager from the Official Thread: https://forum.xda-developers.com/app...mless-t3473445
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img extracted from your Update.app using Huawei Update Extractor.
2. If you are using Mate 9 with model MHA-L29636 running on firmware ending in B362, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
3. Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
Here are some questions:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager -- this is an android app? Do I sideload it?
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Finally, the camera image is here:
https://forum.xda-developers.com/showpost.php?p=75848917&postcount=2
It isn't clear to me how to flash using Magisk, but perhaps that will be obvious once I have magisk operating.
prestonmcafee said:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
Click to expand...
Click to collapse
Firmware Finder (they have Windows desktop and Android apps for it, and there's also http://pro-teammt.ru/firmware-database/ which does the job just as well, though it's all in Russian.)
Find the FullOTA-MF firmware that corresponds to your model, download the 'update.zip' that goes with it - on the website, it's under the link 'update' in the same row. If you do it on your phone in the Firmware Finder app, hit "Download" on the relevant detail screen and it'll prompt you for which files you want.
Once you've got the update.zip, extract it, you'll find a file UPDATE.APP, which is what the extractor wants. If it throws up an error, disable CRC checking of the extracted content. (I don't recall what the label for it is and I don't have it installed on the machine in front of me...); and yes, you'll want RAMDISK.img from it.
prestonmcafee said:
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Click to expand...
Click to collapse
Magisk Manager wants to create a patched ramdisk image. When it updates, it'll want to update the ramdisk image on your device (which it'll be able to do since it's running with root privileges itself anyway), but for the first pass, it needs that image provided and for you to manually flash it.
Thanks!
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.
prestonmcafee said:
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.
Click to expand...
Click to collapse
The magisk manager app apk you just run on your phone to install it, no side loading required.
Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?
That worked
prestonmcafee said:
Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?
Click to expand...
Click to collapse
That seems to have worked.
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
CTSProfile and BasicIntegrity false, any ideas?
Space_Dog said:
CTSProfile and BasicIntegrity false, any ideas?
Click to expand...
Click to collapse
It's probably the version. I have same situation
mingkee said:
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
Click to expand...
Click to collapse
What is this FastbootD? Something new on Android 10, cause the Pixel 4 has it too...
AndroidManager2020 said:
What is this FastbootD? Something new on Android 10, cause the Pixel 4 has it too...
Click to expand...
Click to collapse
It's Android 10 way to flash boot, recovery, dtbo, vbmeta, and super
The interface is more like stock recovery with fastbootd on the top
mingkee said:
It's Android 10 way to flash boot, recovery, dtbo, vbmeta, and super
The interface is more like stock recovery with fastbootd on the top
Click to expand...
Click to collapse
I totally understand the concept but what different between regular fastboot, mfastboot, and fastbootD?
mingkee said:
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
Click to expand...
Click to collapse
For the retail channel on my device, should be LARET which had (2) Builds, the latest being (XT2027-1_DEF_RETLA_10_QPFS30.103-12-5-2_subsidy-DEFAULT_regulatory-XT2027-1-SUTEL-DS_CFC.xml.zip) i'll change to RETAIL after i receie the device. I am worried about getting OTAs later then Brazil/LA Channels.. There are NO RETAIL Firmware Packages for the Retail Channel Device. I guess ill have to see what model it is, Purchased from Amazon, which is where I got my G8+ for a CHEAP $205.83 and as soon as i went to reorder a replacement, price jumped $75, like amazon knew i was going to reorder the same device. Then i came across the one hyper and for a few $$$$ more, specs and chipset are better, same exact specs as the Zoom and the Hyper ran me $314 and the Zoon is like $394.00 I Just need something new to keep me busy until the Edge+ is released....and currently also a Pixel 4 XL (Trying to trade for a LG V60 thinq with the Dual Screen. ) Pixel is 1 month old, 1.5 months at the most, OEM Box, OEM accessories ONLY EVER USED, a couple cases.
Been a Android user since 2010, never had an LG Android. Wait, i had the V40/V50 for under 12 hrs and hated it. it felt cheap and clunky.... But i feel in love with this V60. And i also have (2) Moto G7 aka River. My Moto Def should be here tuesday hopefully. See how quick i can brick this one Moto G8+ was bricked on day one but i pulled out of it using a brand new Levovo Upgrade Tool!
Magisk install
I cannot find on XDA if we can or cannot install Magisk on the XT2027-1 ( One Hyper )
I found a few other sites on the internet that say it can be installed
BUT I tend to err on the side of caution.
I do not want to nuke this phone.
Is this a possibility to install Magisk or not?
I use Viper4 Android and a few other apps like blockada and such
Finally, IF Magsik is installed, I cannot get OTA updates, correct?
Can I uninstall Magisk, update OTA, then reinstall Magisk?
Thank you all
jharkness316 said:
I cannot find on XDA if we can or cannot install Magisk on the XT2027-1 ( One Hyper )
I found a few other sites on the internet that say it can be installed
BUT I tend to err on the side of caution.
I do not want to nuke this phone.
Is this a possibility to install Magisk or not?
I use Viper4 Android and a few other apps like blockada and such
Finally, IF Magsik is installed, I cannot get OTA updates, correct?
Can I uninstall Magisk, update OTA, then reinstall Magisk?
Thank you all
Click to expand...
Click to collapse
Have run into issues......... Damn Windows update restarted computer in middle of night before I was to finish rooting.
I can get into bootloader and when I try to flash I am stuck in bootloop
I get the following errors:
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Sending 'vbmeta_a' (4 KB) OKAY [ 0.016s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 5
OKAY [ 0.000s]
Finished. Total time: 0.016s
Ideas on how to fix? This was flashing back the ORIGINAL stock rom
---------- Post added at 07:57 AM ---------- Previous post was at 07:11 AM ----------
FIXED Rescue and Smart Assistant from Lenovo fixed it
Got it fixed thanks to Rescue and Search program from Motorola
Would like to know since TWRP is not working with the One Hyper, is there a way that I can make a master rom backup via ADB or FASTBOOTD?
If so, can someone make a batch file or list all the things to backup this rom?
I would greatly appreciate it. Thank you
I have my Magisk installed on my Hyper and all is working well. I just got Moto trying to download and update a patch (assuming Google security update). It could not update obviously.
My question is how can I UNinstall magisk , all the modules, and then update my Hyper?
Now if I uninstall magisk I will lose root, correct?
This is the rom I am currently using........DEF_RETAIL_QPFS30.103-47-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC
jharkness316 said:
I have my Magisk installed on my Hyper and all is working well. I just got Moto trying to download and update a patch (assuming Google security update). It could not update obviously.
My question is how can I UNinstall magisk , all the modules, and then update my Hyper?
Now if I uninstall magisk I will lose root, correct?
This is the rom I am currently using........DEF_RETAIL_QPFS30.103-47-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
in order to take updates you would need to restore the stock boot image with fastboot or magisk, and then update your device, then take the new boot image from the downloaded update and patch with magisk and then flash it to regain magisk root, you do not need to uninstall magisk or the modules but you will need to restore stock boot partitions to allow the device to not error out during the install process. This is how it has been in the past for magisk official guides can be found on magisk website here: https://topjohnwu.github.io/Magisk/ota.html
[deleted]
REVIEW THE RISKS
In case you didn't know, bootloader is a little bit of code that tells your device's operating system how to boot up. Motorola has done the work to make sure your device has a fully optimized, certified and tested version of Android. If you are a developer, unlocking the bootloader will allow you to customize your device, but keep the following in mind:
You will lose all media and content on your device and will need to reinstall all applications downloaded from Google Play.
Applications may not work anymore.
You may lose encryption support.
You may lose some key functions like telephone, radio, and audio playback.
You could cause permanent/physical damage to your device.
Unlocking your bootloader will not change your device subsidy lock status
STEP 1 Download Minimal ADB & Fastboot here https://androidfilehost.com/?fid=746010030569952951
[YOUTUBE]uxPEly6EKuk[YOUTUBE]
2. NEXT GET YOUR DEVICE ID
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)
At the prompt, type
$ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
3.Example: On a Windows Desktop, the returned string format would be
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
4.On a Mac OS Desktop, the returned string format would be
INFO0A40040192024205#4C4D3556313230
INFO30373731363031303332323239#BD00
INFO8A672BA4746C2CE02328A2AC0C39F95
INFO1A3E5#1F53280002000000000000000
INFO0000000
5.Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
6.Check if your device can be unlocked by pasting this string in the field below, Like shown in the video below at 9:20 sec and clicking “Can my device be unlocked?”
7.THEN GET YOUR UNLOCK KEY
Heres A step by step video tutorial to also help u get the bootloader unlocked
I achieved to unlock the bootloader but no to root my moto G8 plus.
In the unlock process my phone was formatted and all info was lost.
Now, I can see that can't use my fingerprint in the apps for login, and my phone doesn't update.
My actual rom is QPI30.28-Q3-28-26-3 and it's trying to updated to QPIS30.28-Q3-26-3-2 and does not achieve it. That's why i want to relock the bootloader. Or there is a way to update with the bootloader unlocked and not root?
X4vier said:
I achieved to unlock the bootloader but no to root my moto G8 plus.
In the unlock process my phone was formatted and all info was lost.
Now, I can see that can't use my fingerprint in the apps for login, and my phone doesn't update.
My actual rom is QPI30.28-Q3-28-26-3 and it's trying to updated to QPIS30.28-Q3-26-3-2 and does not achieve it. That's why i want to relock the bootloader. Or there is a way to update with the bootloader unlocked and not root?
Click to expand...
Click to collapse
Come on, it is possible to update the ROM with flash and Magisk, first download the ROM you want
On your mobile in developer options activate OEM UNLOCK
Now with the Magisk Manager installed and the boot.img that has to be copied to the phone Use Magisk to Patch the updated system's boot.img.
Copy the patched img to the PC, and when using the script replace the original boot.img with that of magisk
Flash all ROM images that come along, now you have an updated and rooted system
The biggest problem with updating with root is that we do not know to what extent Android will be able to be tricked on SafetyNet, so I do not recommend always updating, as one hour it will not be possible to install Bank apps or some games.
I need to sit down and do the step-by-step perfectly, but I'm busy all day, so just answer anything and I try to help.
X4vier said:
I achieved to unlock the bootloader but no to root my moto G8 plus.
In the unlock process my phone was formatted and all info was lost.
Now, I can see that can't use my fingerprint in the apps for login, and my phone doesn't update.
My actual rom is QPI30.28-Q3-28-26-3 and it's trying to updated to QPIS30.28-Q3-26-3-2 and does not achieve it. That's why i want to relock the bootloader. Or there is a way to update with the bootloader unlocked and not root?
Click to expand...
Click to collapse
The system does not update with the bootloader unlocked, it is a security system, I recommend updating via flash
Jukmisael said:
Come on, it is possible to update the ROM with flash and Magisk, first download the ROM you want
On your mobile in developer options activate OEM UNLOCK
Now with the Magisk Manager installed and the boot.img that has to be copied to the phone Use Magisk to Patch the updated system's boot.img.
Copy the patched img to the PC, and when using the script replace the original boot.img with that of magisk
Flash all ROM images that come along, now you have an updated and rooted system
The biggest problem with updating with root is that we do not know to what extent Android will be able to be tricked on SafetyNet, so I do not recommend always updating, as one hour it will not be possible to install Bank apps or some games.
I need to sit down and do the step-by-step perfectly, but I'm busy all day, so just answer anything and I try to help.
Click to expand...
Click to collapse
Excuse me.. the process do you discribed here is the same of this video.
X4vier said:
Excuse me.. the process do you discribed here is the same of this video.
Click to expand...
Click to collapse
I really don't understand what you want.
Let's do it like this:
If you have rooted, flash the system that is on the device without root, and now lock the bootloader "Fastboot oem lock" I think the command is this. Go to the system and update your Android, A simple root was not to give so much headache.
X4vier said:
Excuse me.. the process do you discribed here is the same of this video.
Click to expand...
Click to collapse
Dude do things slowly! If you are going to root do it with caution, and put the correct system, as it can brick the phone. If rooted, undo and lock the bootloader, update and then root in 10Q
I rooted xt2019-2 and there were no problems, everything works, activate Magisk Hide and Hide the Magisk package, even SafetyNet Net is now true.
Updating 10Q with Magisk is only possible via FLASH, you are apparently doing it via OTA, in OTA it is not possible to update. With the bootloader unlocked it is possible to do everything, even to place the 10Q with the Magisk without having to revert the root.
If the phone is not rooted, go to developer and disable OEM UNLOCK and fastboot OEM LOCK. Restart the device, and be happy with the OTA.
It is not to give so many problems, there is no secret.
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
ajg32 said:
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
Click to expand...
Click to collapse
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
dcarvil said:
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
Click to expand...
Click to collapse
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
ajg32 said:
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
Click to expand...
Click to collapse
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
dcarvil said:
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
Click to expand...
Click to collapse
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
ajg32 said:
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
Click to expand...
Click to collapse
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
dcarvil said:
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
Click to expand...
Click to collapse
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
ajg32 said:
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
Click to expand...
Click to collapse
"boot_a image size: 100663296" is the wrong size. How are you transferring boot.img and the patched image between your phone and PC? You should be using adb push/pull. If you did use adb push/pull, I'd need to see all the commands you used, and a directory listing of all the files to see if I can spot something wrong. Also, what version of Magisk?
You could try renaming magisk.apk to magisk.zip and installing the zip with TWRP, but I don't know if that method still works on the Pixel 3. I've never tried that method. Make sure you just boot TWRP (fastboot boot twrp.img), and do not install TWRP. If that breaks things, at least you know how to recover now.