Hi, here I bring you a small tutorial for upgrading your rooted Realme GT 2 Pro Global Version to latest update (RMX3301_11_A17), as you may know I am not responsible of any damage and I recommend you to back up your data.
First, uninstall all your modules from magisk (technically you could just deactivate them, I prefer uninstall though). Make sure Zygisk is deactivated and turn off all the super user permissions of your apps before the update step. You should deactivate Automatic system updates under developer settings as well.
Here the steps:
1. Go to settings and download the OTA, you´ll get the 200 mb one. Since what we need is the full OTA package, once it's been downloaded when it starts to be extracted force stop the Software Update app in your settings.
2. After previous step go to your file manager (in this case I use Mixplorer, for this you will need the app with root access) and go to the next directory: root/data/ota_package/OTA/ [a folder that starts like .ota], inside you are going to delete the ota file with .zip extension. This first two steps are a way to speed up the process of getting the full OTA.
3. Go again to your software update section in settings, you will see a notification from the app software update app, touch on continue. After that you will see a message of error, and you will see a button that says "Try again", keep clicking on try again several times. You'll see then that full OTA update will start automatically (about 5 gb in size).
4. From here you will have to wait until the "Install" button appears (it'll take a while). Next, you click install.
5. After reboot, transfer the boot.img file attached on this post to your device. Magisk patch it and transfer back to your PC.
6. Open your adb terminal, type the command adb reboot bootloader
7. Test recognition by typing fastboot devices
8. Next type: fastboot boot whatevernameofyourpatchedfile.img (it has to be in the platform tools folder)
9. Your device will boot with a temporary root, check everything is working ok in your device. After that you will go to magisk app, click on install, and in the Method section select "Direct Install", and then Let's go.
10. After reboot you'll have you magisk rooted device updated and working. Now you can install back your modules again.
boot
This method can be done on the phone with root preservation directly via Magisk. No need to copy/patch boot.img files manually, as long as you have restored image in Magisk at least once. This is explained below.
Important notes:
Do not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and patched boot.img must be flashed via fastboot to restore root.
In addition, after installing to inactive partition in Magisk, do not press restart on Magisk's prompt.
The auto-update should be disabled, including the "Auto Download" setting. Otherwise, the updater will attempt to download and install while Magisk is present, and show "Extraction Failed" error, and "Try Again". If that happens, the system will only allow to download a 5GB update instead. To reset it, you can clear Software Updater app data and cache via some root app manager.
When selecting "Restore Images" in Magisk, if a message shows in Magisk "Stock boot image not found", then you need to generate backup stock boot.img on the phone. This is only done once, but you will need a stock boot.img of your current ROM version.
- Copy current ROM version stock boot.img to storage
- Open Magisk and select install -> Patch file -> Select the stock boot.img
- Restart phone.
This will generate Magisk "backup image" folder where it will keep the stock, non-patched boot.img.
This is only done once, on any future update the error will not show.
Click to expand...
Click to collapse
The 300mb OTA update steps:
1. Go to updater and it should show 300-600mb update available. DO NOT press "Download"!
2. Go to Magisk, select to restore image. Do not restart when prompted by Magisk. If you get error, read note on top.
3. Go back to updater and select "Download". It will first download then extract. When it finishes extracting, DO NOT press Install!
4. Go back to Magisk and select install to inactive partition. Once it's done, do not restart via Magisk! Close Magisk.
5. Go back to updater, and press "Install" button
Click to expand...
Click to collapse
Extra notes:
1. If you press Download before removing Magisk, it will fail extracting and show "Try Again". Do not press try again. Go to a root app manager, and clear Data and Cache of com.oplus.ota Software updater. Then repeat the process by restoring images in Magisk first.
2. If you did press "Try Again", it will only allow you to download a 5GB update. Steps are similar as long as you restore Magisk. You might be also able to clear data and cache like in step above to reset it back to smaller update, but I haven't tested this yet.
3. If you restart by Magisk prompt, it will soft-loop. You can hold Vol Up + Power until it boots into non-root partition. Go to updater and press install. It will boot to rooted partition.
4. If you pressed Install in updater before installing Magisk to inactive partition, it will boot to updated partition without root.
5. I have tested the update methods with simply Uninstall -> Restore Images, while I had Magisk modules such as BCR, Shamiko, USF, LSPosed Zygisk. It works fine without the need of removing each module.
Extra side note: Update file is downloaded to: /data/ota_package/OTA/.otaPackage/mymanifest(...).zip
What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
Phone will reboot and updated. Magisk working, All modules intact.
shivrajsingh said:
What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
Phone will reboot and updated. Magisk working, All modules intact.
Click to expand...
Click to collapse
I know what you mean, in fact thank you for telling me that procedure is working well on our device hahaha, since there's no proper flashing tool and no TWRP yet, the idea behind that lengthy process is trying to reduce the risks to minimum n.n
Just confirmed that this works for a 300mb (before restoring images) update file instead of the full 5GB (after restoring images), updated the guide above.
vanya.ag said:
boot
Click to expand...
Click to collapse
now my fingerprint is broken
Quake94 said:
Notes:
When Magisk is removed using Restore Images, the Realme OTA updater will show a full 5GB update. If the Magisk is not removed, the OTA will be around 300mb. Both update files will work OK, there is just small difference in steps. The important part is to not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and a patched boot would need to be flashed via fastboot to restore root.
Click to expand...
Click to collapse
i followed your steps
it was an 5gb OTA update i dovnloaded it and extract it then i go to magisk and install to inactive slot after reboot now im in stock recovery what now?
Terrorigel97 said:
i followed your steps
it was an 5gb OTA update i dovnloaded it and extract it then i go to magisk and install to inactive slot after reboot now im in stock recovery what now?
Click to expand...
Click to collapse
What what? You post in multiple threads. In one of them you want to lock bootloader and keep it stock, but here you say you installed Magisk after OTA. You also talk about stock recovery that has nothing to do with bootloader.
Help yourself and read up, all the information is widely available.
Quake94 said:
What what? You post in multiple threads. In one of them you want to lock bootloader and keep it stock, but here you say you installed Magisk after OTA. You also talk about stock recovery that has nothing to do with bootloader.
Help yourself and read up, all the information is widely available.
Click to expand...
Click to collapse
I never said i will be on stock lol I was just asking if you can lock your bootloader again...
Terrorigel97 said:
I never said i will be on stock lol I was just asking if you can lock your bootloader again...
Click to expand...
Click to collapse
Lock only on clean, stock rom as per guide in the other thread.
Can't lock on rooted, but rooted can be reversed to stock clean.
EDIT: resolved, see bottom note.
A.19 update screwed something up for me.
I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.
Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.
Restarted to fastboot. Fastboot works OK.
When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.
Manually switched active partition via fastboot --set_active to try to boot the A19.
Phone still softloops, again, restarted back to previous slot with A18.
Fastboot indicates unlocked bootloader.
Not sure what got messed up, and why bootloader mode refuses to start.
Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.
Anyone else in a similar situation?
EDIT: LOL I fixed it . I went to software updater, and "Install" button was displayed.
Pressing install restarted the phone into A19 with Magisk installed......
Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.
TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
I confirm you have to reboot via the installer and not via Magisk, since I had to manually flash boot.img multiple times in the past.
Quake94 said:
EDIT: resolved, see bottom note.
A.19 update screwed something up for me.
I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.
Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.
Restarted to fastboot. Fastboot works OK.
When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.
Manually switched active partition via fastboot --set_active to try to boot the A19.
Phone still softloops, again, restarted back to previous slot with A18.
Fastboot indicates unlocked bootloader.
Not sure what got messed up, and why bootloader mode refuses to start.
Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.
Anyone else in a similar situation?
EDIT: LOL I fixed it . I went to software updater, and "Install" button was displayed.
Pressing install restarted the phone into A19 with Magisk installed......
Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.
TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
Click to expand...
Click to collapse
This sounds like what my phone is doing but maybe I am confused because you mention fastboot and the bootloader as two different things. Just to be clear, "adb reboot bootloader" is what you are calling the bootloader and "adb reboot fastboot" which goes into fastbootd mode is what you are calling fastboot?
If so then my phone is doing the exact same thing, I can boot to fastbootd mode but when I attempt to "adb reboot bootloader" then just like you said a little mascot with Chinese writing appears for a split second then it reboots back to the system. Did you get your bootloader working again by doing the install?
GIutton said:
This sounds like what my phone is doing but maybe I am confused because you mention fastboot and the bootloader as two different things. Just to be clear, "adb reboot bootloader" is what you are calling the bootloader and "adb reboot fastboot" which goes into fastbootd mode is what you are calling fastboot?
If so then my phone is doing the exact same thing, I can boot to fastbootd mode but when I attempt to "adb reboot bootloader" then just like you said a little mascot with Chinese writing appears for a split second then it reboots back to the system. Did you get your bootloader working again by doing the install?
Click to expand...
Click to collapse
There are four modes:
bootloader - adb reboot bootloader
fastboot - adb reboot fastboot (or the key combo)
fastbootd - fastboot reboot fastboot (from being already in fastboot)
recovery - adb reboot recovery (or the key combo)
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry
In my case the fastboot mode would start ok, just not the bootloader mode.
I didn't try fastbootd, but it would probably start ok.
I don't understand the fastbootd mode well though. I read somewhere that it is fastboot in Data partition.
I haven't tested rebooting to bootloader after fix, but can let you know.
EDIT: Booting to bootloader from fastboot (fastboot entered with key combo) gives me the mascot again, then it goes immediately back to fastboot. So I think I am in same position as you
Running "adb reboot fastboot" started "Fastbootd" mode (the one with wipe data/reboot/power off)
Running "fastboot reboot fastboot" from the "Fastbootd" would restart to "Fastbootd"
Running "fastboot reboot recovery" from the "Fastbootd" showed success, but 1. phone stayed in "Fastbootd" and 2. The phone deauthorized ADB (but still showed in device manager as "ossi" device)
Running "adb reboot bootloader" from System, showed the mascot and started the regular Fastboot.
Running "fastboot reboot fastboot" while the regular Fastboot was on, started "Fastbootd"
My suspicions are:
1. Regular fastboot mode is the one with green "START" on top. Somehow it is the same as bootloader. This is confirmed by Realme guide for unlocking/locking bootloader - they ask to use adb reboot bootloader, and then run a fastboot command.
2. "Adb reboot fastboot" starts the "userspace" fastboot called "fastbootd" which is isolated from bootloader and kernel.
This would mean the modes are:
bootloader/fastboot -> adb reboot bootloader (or the key combo)
fastbootd - adb reboot fastboot, or fastboot reboot fastboot (from being already in bootloader/fastboot)
recovery - adb reboot recovery (or the key combo)
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry
So you can get into the start menu (fastboot/bootloader) by using the button combo but if you try fastboot reboot bootloader it shows a mascot with chinese letters then goes right back to the start menu and adb reboot bootloader shows the mascot and goes into the start menu as well? I think your phone is fine. . . fastboot and the bootloader should both be the start menu right or is there a difference?
For me I get the realme logo then a screen glitch and boots to the system when I try the button combo. When I try adb reboot bootloader I get a mascot with Chinese letters then a screen glitch then boots into the system.
Added some extra notes in my guide. If Auto download was enabled in About Device -> Software Update, the updater will display "Extraction Failed" since it attempts to download and extract update while Magisk is present. It also locks itself out of "Local install". The updater will download 5GB update instead on a retry, and 5GB method would be used.
With the Auto download disabled, user can Restore Images via Magisk and then download and install the update.
I will test this on the next update rollout.
Revised guide after C.12 to C.13 update and testing the smaller update method. The process is much more straightforward than I initially thought. No need for "Local update".
Related
This is long, but it's nice for noobs because it's detailed. It's honestly kind of fun, I promise. I'm assuming you have WINDOWS. This is based off of the guide by torxx!. It's modified because some of the info is outdated (you don't have to flash the boot.mg separately, for example). If you are NOT a noob you can just look at the "overview" for each step.
UNLOCKING YOUR DEVICE WILL WIPE YOUR DEVICE. THIS IS A SECURITY FEATURE. BACKUP FIRST.
Part 1- gaining unlock token
Overview: go to htcdev.com and unlock bootloader
Be sure you've turned off fast boot option in power menu; usb debugging should be on (settings -> developer options).
Go to http://www.htc.com/www/software/htc-sync-manager/[1] and install HTC SYNC. Alternatively, if you know what you're doing, you can install these drivers:
x86 http://www.mediafire.com/?qabo1tue2v1ky75 x64 http://www.mediafire.com/?8dl8s3l9mr6ggr9
Go on http://www.htcdev.com[4] and create yourself an account on HTCDEV.
Download these adb/fastboot files: http://d-h.st/RvD
Make a new folder anywhere. We'll use C:/fastboot as an example.
Extract the zip downloaded to the new folder
Go Here http://www.htcdev.com/bootloader/[6] and select "All Other Supported Models" and "then begin unlock bootloader" (check the boxes, click proceed, all that good stuff). YOU CAN IGNORE THE DIRECTIONS THAT THEY TELL YOU (and follow this guide instead).
Power off your phone. Power your phone on by holding power and volume down.
Highlight 'Fastboot' the volume buttons then press power to "select".
Plug your phone into your PC and open a Command Prompt. (windows XP - Click Start > Run > type CMD in box then press OK; Windows 7 - Click Start > type CMD in search box then press Enter) Change directory to your folder where we put fastboot files by typing cd c:\fastboot for example.*
*Alternatively, you can just hold down shift and right click in the folder and select "open command window here". Neat huh?
Type this into your command prompt window: fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files
Type this into your command prompt window: fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol+ to accept and power to confirm.
Part 2
Overview: flash your recovery. Boot into recovery. Turn phone off if it boots into OS. Boot into back into recovery. You're done!
Download a recovery:
TWRP (the one I use): http://forum.xda-developers.com/showthread.php?t=2173870
CWM 2: http://forum.xda-developers.com/showthread.php?t=2172979
CWM: http://forum.xda-developers.com/showthread.php?t=2173863
Place the Recovery file to the folder where the fastboot.exe is.
Same thing as above- boot (volume down + power) into the bootloader and highlight 'Fastboot' the volume buttons then press power to "select".
Do the same thing as with the command prompt above. This time, however, you'll be typing:
fastboot flash recovery "name_of_the_recovery.img"
For example:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
then type:
fastboot erase cache
From the menu, boot into recovery (use volume to move up and down, power to select). The phone might boot to the OS instead of recovery, don't worry!
Turn off phone then turn on (while holding volume down) to boot back into the bootloader.
TAMPERED shows up, boot into recovery and now your recovery should be working!
Part 3- obtaining root
Overview: flash a super tool
Download a super user tool for root:
SuperSU (I use this one): http://forum.xda-developers.com/showthread.php?t=1538053
SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Alternatively, download this: http://forum.xda-developers.com/showthread.php?t=2252959. This is a stock rooted rom for ATT. If you download and flash this instead of the super user tool, you're done. (This rom includes super user) Or you can download a custom rom such as this one: http://forum.xda-developers.com/showthread.php?t=2183023
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip super user tool to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead.
I recommend these kernels: http://forum.xda-developers.com/showthread.php?t=2255900 or http://forum.xda-developers.com/showthread.php?t=2233665&highlight=menu
Download it.
Installing custom rom/kernel ("flashing a rom")
Overview: Download Rom, boot into recovery and wipe and then flash.
According to Shenye, even though your device is s-on, you can still flash boot now. So just do this:
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip kernel/cutom rom to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
I feel like this title should be changed to clarify that it's unlocking the bootloader, not the SIM lock.
Just wanted to say this tutorial was 100% dead on and what I used to unlock bootloader and root/rom my One.
Oddity - Did everything, I've got root but I -AM- out of the woods. Was installing bulletproof mod through recovery but it kept failing due to missing a MD5 file or something -- Trying to work that out through that thread atm but anyway, rebooted the phone a couple of times now and I still have root, Tit back up works OR are we talking about things like CPU clocking won't work since it can't rewrite?
Sticking this.
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Does anyone know if this will work on the Rogers HTC One?
Thank you. Followed this last night. Worked flawlessly. The only thing that threw me was rebooting into recovery. It took maybe 3 or 4 reboots for it to say "TAMPERED" at the top. When it didn't say tampered, it would not boot to recovery.
TELUS?
DannySmurf said:
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Click to expand...
Click to collapse
Did you happen do run this tutorial on a TELUS device?
Viceroy_N said:
Does anyone know if this will work on the Rogers HTC One?
Click to expand...
Click to collapse
Yes it does. I have a Rogers phone, and it worked perfectly.
richnanaimo said:
Did you happen do run this tutorial on a TELUS device?
Click to expand...
Click to collapse
No, I have a Rogers device. But the procedure should not be any different.
followed step by step and got an error that says submitted token wrong length
I'm on ubuntu 13.04 and I get stuck at getting the token. I type in fastboot oem get unlock_identifier_token and it says waiting for device. Tried it with sudo and it says error and sudo ./fastboot and it says no such command.
Sent from my HTC One using xda app-developers app
Having a really odd problem. I flash the twrp recovery per instructions. I try to reboot to recovery and it seems to try and then, blam, the att boot.
I have tried this from the bootloader, selecting Recovery, as well as from a booted stated using "adb reboot recovery".
Any hints for me? I originally had a silver One and today got my Black One replacement,. Had no issues on the original one. Hmm. Guess I will try CWM.
FYI: Yes I unlocked the bootloader and it says Unlocked in there
-I also notice that I seem to go right into fastboot, when I boot the bootloader. Now, I believe that is normal if you have the usb cable attached, but this happens regardless.
-flashed stock recovery back and can get into it. trying twrp again, renaming the file to "recovery.img" just because...and it worked on that stock recovery file
-Also, very hard to get into bootloader from powered off state. I may flash RUU_M7_UL_JB_50_Cingular and see if it helps me.
OK, maybe it is the phone or ATT has done something screwy on the latest. I can not even get the RUU install to pass inspection. Wants me to check the connection. I know all my stuff is in order, as I did this all on the previous one. grrr
-Just noticed mine does say Unlocked but it does not say Tampered.
-Crazy. I decided to get a new Unlock token and redo the unlock with it. Now, the bootloader finally says Tampered and I got into TWRP. I have no idea why, since I would think that if the original Unlock token was incorrect, it would not have unlocked the phone.
So, rather than providing worthwhile information for anyone else having problems, I think this post is probably deletable and that is fine by me should the powers so decide.
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
tacotino said:
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
fastboot oem lock
but, it will say relocked. nobody cares or seems to check. also, it will say tampered until you restore a stock ruu to flash. I used RUU_M7_UL_JB_50_Cingular.exe for mine when switching from silver to black. it is the right one for att. sorry, don't have the link to the download anymore.
great writeup! quick comment though, just helped my brother unlock his phone. i had a similar issue to @Barsky above so I decided to try to reflash the recovery. The first time I used the line fastboot erase cache after flashing the recovery and I think that's what caused it to not boot into recovery. The second time I flashed TWRP, I didn't enter that line and voila it worked on the first try!
can anyone post a mirror of the dev host files? devhost seems to be down.
nice...
help please
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
mbroch89 said:
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
Click to expand...
Click to collapse
I think the last bit was your problem. You can't factory reset from bootloader. Try to push twrp again in fastboot then load/flash clean romantic, then boot up. It already has root so you don't need to push su.
Sent from my HTC One X using xda app-developers app
Hi,
I unlocked my Honor 9 bootloader using the "fastboot oem unlock 'unlock key'" method.
After that it did low level reset or something of the sort and booted to Android.
After that I wanted to install TWRP using fastboot, the problem is that every time I do "adb reboot bootloader" I get a message the device cannot be trusted (see pic) and it boots to android.
I tried pressing power button, up button (this gets me to the recovery), but it always gets back to Android and not to fastboot.
What can I do???
Thank you
Return fully stock, then try again
PalakMi said:
Return fully stock, then try again
Click to expand...
Click to collapse
How do I do that, use the original recovery?
OK, I managed to get to the bootloader by turning off the phone, pressing the volume down button and connecting the USB cable.
I flashed twrp and somehow booted to the recovery I wanted to flash the supersu.zip but all the folders and file names in the sdcard were gibberish.
I rebooted and everything was ok (not gibberish) but instead of having twrp I got the original recovery back.
Since then even if I flash using fastboot the twrp recovery I keep getting the original recovery.
In the fastboot screen there's a message "Android reboot reason: bootloader NA reboot_enter_fastboot_common_func" is it normal? (see pic)
And one last question, should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
UPDATE:
I managed to get twrp working.
I did fastboot oem relock, and then unlocked the bootloader again, and it booted to twrp (without re-flashing twrp).
When I tried to flash supersu all the files were gibberish (see pic), what am I missing?
If I wipe data it seems fine, but then I boot to system to copy the supersu file and once I load twrp it is gibberish again.
Also should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
Appreciate any help I can get.
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Midhon58 said:
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Click to expand...
Click to collapse
yeah I figured as much.
Didn't think of using external SD, thanks, was about to try adb sideload, I assume it would have worked too.
Many thanks, the external sd did the trick
I've unlocked the bootloader to my Wileyfox Spark X using "fastboot flashing unlock" from my Ubuntu PC. I've flashed twrp recovery image (twrp-3.2.1-0-porridgek3.img
from https://dl.twrp.me/porridgek3/) having renamed it to twrp.img:
[email protected]:/home/john/Software/WileyfoxSparkX# fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13154 KB)...
OKAY [ 0.378s]
writing 'recovery'...
OKAY [ 0.347s]
finished. total time: 0.726s
But I can't get into SuperSU 2.82 (using SuperSU-v2.82-201705271822.zip) even though I've put it into the root directory of the internal SD card. There's no obvious option from the Android Recovery menu (i.e. Reboot system now, Reboot to bootloader, Apply update from ADB, Apply update from SD card,....). I've tried Apply update from SD Card and selected the SuperSU .zip file but it comes up with ""installation aborted" after "Update verification took 0.2 s (result 1)" with no other help. Any ideas?
I've tried TWRP 3.0.2-0. It gets into TWRP menu. I selected Install but "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. BTW I've emailed TWRP Support (from their web page) asking if they have a working version.
johnaaronrose said:
I've tried TWRP 3.0.2-0. It gets into TWRP menu. I selected Install but "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. BTW I've emailed TWRP Support (from their web page) asking if they have a working version.
Click to expand...
Click to collapse
Don't bug the TWRP developers for a specific version of TWRP which isn't even maintained by them.
Can you mount /system at all? Try pressing the "Mount" button in the main menu and let me know. You aren't supposed to install anything from the Android Recovery menu, you can only install OTA updates through that menu and its functionality is pretty much limited.
Where did you get that version of TWRP from? (I'd appreciate it if you linked me the thread)
AlwaysLivid said:
Don't bug the TWRP developers for a specific version of TWRP which isn't even maintained by them.
Can you mount /system at all? Try pressing the "Mount" button in the main menu and let me know. You aren't supposed to install anything from the Android Recovery menu, you can only install OTA updates through that menu and its functionality is pretty much limited.
Where did you get that version of TWRP from? (I'd appreciate it if you linked me the thread)
Click to expand...
Click to collapse
I assumed that the Wileyfox Spark X (i.e. porridgek3) version is maintained by the TWRP developers because the various versions come from:
https://dl.twrp.me/porridgek3/
Currently, I can't get into TWRP again. It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. sill in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu. Could that be due to needing e.g. 70% battery charged?
At the moment the battery is 50% charged. So I'll fully charge it and post about the mount of /system using TWRP, assuming that I can get into TWRP.
BTW I did find a thread on https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung The interesting comment is #5. It says:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Is this the solution to rooting on the Spark X?
johnaaronrose said:
I assumed that the Wileyfox Spark X (i.e. porridgek3) version is maintained by the TWRP developers because the various versions come from:
https://dl.twrp.me/porridgek3/
Currently, I can't get into TWRP again. It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. sill in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu. Could that be due to needing e.g. 70% battery charged?
At the moment the battery is 50% charged. So I'll fully charge it and post about the mount of /system using TWRP, assuming that I can get into TWRP.
BTW I did find a thread on https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung The interesting comment is #5. It says:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Is this the solution to rooting on the Spark X?
Click to expand...
Click to collapse
Yeah, that's normal. The battery percentage here doesn't really matter, but you could try to boot to TWRP using fastboot. You can also boot to TWRP by executing "fastboot boot recovery.img". You can also flash TWRP *through* TWRP.
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Jonnibravo said:
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Click to expand...
Click to collapse
If you're rooted, give the reboot recovery app you installed after bootloader unlock root privileges.
If not then use the exact same PC ADB commands to boot to TWRP like during bootloader unlock.
I'm confused why you mention flashing TWRP after Boombox. Surely you didn't do that. You already had TWRP.
I am rooted, Recovery reboot just reboots the phone, I have tried to get into twrp by reinstalling but again does the same things just reboots the system after the corruption warning screen. I've also tried to install from the bootloader with the fastboot boot twrp.img command but it simply says waiting for device.
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Jonnibravo said:
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Click to expand...
Click to collapse
Then you didn't follow my bootloader unlock and root guide. I never mention that other TWRP, much less link to it.
You're going to have to load into Download mode and use fastboot commands, but you say you couldn't get past flashing TWRP.
Uninstall the LG Mobile Driver if you have them, then reinstall.
1st, reboot into OS, then open up Device Manager and change view to Show hidden devices. You should see a new category named 'ADB Interface' and underneath that 'Fastboot Interface (Google USB ID)'.
If not, you will also see 'ADB Device' for Other Devices category:
right click that to update driver software ---> Browse my computer for driver software ---> Let me pick from a list... ---> Show all Devices ---> Have Disk ---> Browse ---> C:\Program Files (x86)\LG Electronics\LG Mobile Driver ---> 'lgandbus' ---> 'LGE ADB Mobile Interface'
Download adb/fastboot software, download Joan TWRP 3.2.1 img file and place it in adb/fastboot folder, then send your phone into Download mode:
Open up cmd and type the following after changing directory to Adb/fastboot folder: fastboot devices (see if your device is there), fastboot flash recovery TWRP.img or (whatever file is named).img, then fastboot boot TWRP.img or (whatever file is named).img
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622
Download: https://dl.twrp.me/blueline/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
GitHub: https://github.com/topjohnwu/Magisk/releases
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
Was my misunderstanding. I thought you were implying people should go back to stock recovery to flash ota. You are talking about flashing ota in twrp. You might clear that up a little bit in that section.
Great post.
Unfortunately, if you are writing a process, then writing everything out is a requirement. Especially with item numbers or using an outline format. Not everyone understands shortcuts taken or abbreviated words, unless they are spelled out in the beginning. IMO, wrote and read too many processes. Including software requirement documentation.
Hi,
thanks for the thread :good:
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
Yes, I think so too.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
The boot.img is into "image.zip"
Then I suggest to flash into a and b (or both)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
or
fastboot flash boot --slot all boot.img
Edit
be careful here: Factory reset via ADB sideload (can also do this without wiping data)
bootloader is bootloader, boot is boot, bootloader.img isn't boot.img
so, maybe better to write:
fastboot flash bootloader nameofbootloader.img or if simply renamed fastboot flash bootloader bootloader.img
deleted, bug.
trouble flashing files
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
wangdaning said:
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
Click to expand...
Click to collapse
Thanks, but still no luck.
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
fyrmd said:
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
Click to expand...
Click to collapse
I always buy Anker cables and chargers. All have been good so far.
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
Are you able to get into recovery? If so, download the full ota to your pc and side load it with adb.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
i same issue
rczrider said:
[*]Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Click to expand...
Click to collapse
why not copy all files?
---------- Post added at 11:58 AM ---------- Previous post was at 11:55 AM ----------
fyrmd said:
Thanks, but still no luck.
Click to expand...
Click to collapse
boot to the twrp.img and flash the twrp.zip, unless you are on android 10 you should have no problem unless you are doing it wrong. not exactly hard to do.
How to enable oem unlock in this case?
pedro5148 said:
How to enable oem unlock in this case?
Click to expand...
Click to collapse
There are a few suggestions at https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
However, if the network carrier has locked the bootloader, you cannot unlock it. In the U.S., Verizon and AT&T phones generally cannot be unlocked due to locked bootloaders.