I have an unlocked boot loader and I know how to flash Graphene OS, Calyx OS, and unofficial Lineage build but have problems with flashing Evolution X(as it's only an OTA update), Satix OS and Stag os. Those others I'm having trouble with. I also put sdk platform tools as path. What am I doing wrong? And I could go back and install December and January stock firmware and still get errors.
UltimateGamer83 said:
I have an unlocked boot loader and I know how to flash Graphene OS, Calyx OS, and unofficial Lineage build but have problems with flashing Evolution X(as it's only an OTA update), Satix OS and Stag os. Those others I'm having trouble with. I also put sdk platform tools as path. What am I doing wrong? And I could go back and install December and January stock firmware and still get errors.
Click to expand...
Click to collapse
Assume you are installing EvoX via ADB sideload & not fastboot (per the instructions), so maybe try the previous platform tools prior to Feb.
Yes. Do I set them to path? As I already know how to do that.
UltimateGamer83 said:
Yes. Do I set them to path? As I already know how to do that.
Click to expand...
Click to collapse
Yes, If you are using Platform-tools 34.0.0 downgrade to V33.0.3. There is a bug on the latest platform-tools. There is a thread on this issue with information.
schmeggy929 said:
Yes, If you are using Platform-tools 34.0.0 downgrade to V33.0.3. There is a bug on the latest platform-tools. There is a thread on this issue with information.
Click to expand...
Click to collapse
Could you link the thread here please? I was about to update my platform-tools later today
xunholyx said:
Could you link the thread here please? I was about to update my platform-tools later today
Click to expand...
Click to collapse
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Related
Using
Code:
adb logcat
I was able to grab the url and download each OTA. I have uploaded to my Android File Host account here.
I own the Android One Moto X4 XT1900-1 purchased from Project Fi and these only work on stock via stock recovery adb sideload. This is the same as taking the official OTA from the notification.
Dec - Blur_Version.27.21.2.payton_fi.google_fi.en.US (initial upgrade to Oreo)
Jan - Blur_Version.27.221.3.payton_fi.google_fi.en.US
Feb - Blur_Version.27.231.6.payton_fi.google_fi.en.US
Mar - Blur_Version.27.251.10.payton_fi.google_fi.en.US
Apr - Blur_Version.28.11.15.payton_fi.google_fi.en.US (upgrade to Oreo 8.1)
How can I install these files on my Moto X4, do you know?
Awesome you rock bro
Thanx a lot bro
abrfilho said:
How can I install these files on my Moto X4, do you know?
Click to expand...
Click to collapse
Try to ADB sideload with stock recovery
Neffy27 said:
Try to ADB sideload with stock recovery
Click to expand...
Click to collapse
I tried, and no success. I done this :
"adb sideload nameoftheupdate.zip" and i've had this message : "E: failed to unmount /"
I tried to set "mount /System" and redid the previous command but with no success again... any help ?
My moto X4 is on Project Fi Oreo (previously on Stock Moto, XT1900-7) and the bootloader is unlocked of course.
That is unfortunate. I'm not sure what advice to give next. I uploaded them in hopes to that it may help towards more customizations. Seems Lenovo really doesn't want to be like Google.
I plan to stay stock till development gets further.
THANK YOU for uploading this!! I am on a completely stock, locked, Project Fi moto x4 and was stuck on the 7.1.1 November update. Flashing the Oreo update via adb sideload worked perfectly
skmpowdjy said:
THANK YOU for uploading this!! I am on a completely stock, locked, Project Fi moto x4 and was stuck on the 7.1.1 November update. Flashing the Oreo update via adb sideload worked perfectly
Click to expand...
Click to collapse
Glad this worked for you. :good: plan to do the same whenever I get March notification.
On my 5th attempt to sideload the 8.0 update. Tried different downloads, file paths, and PC. Same results.
Step 1/2Error applying update: 20 (ErrorCode: : kDownloadState InitializationError)E: Error in / sideload/package.zip ( Status 1)
Any ideas?
Downloaded the full 8.0 firmware file and flashed in fastboot. While setting up the phone, got prompt for Jan security update. Installed it and check for Feb update. Also downloaded and installed. Guess I had some kind of glitch in 7.1.1 that prevented me from receiving OTA's or sideloading with ADB. Figures.
Glad you got it working ?
jfalls63 said:
Downloaded the full 8.0 firmware file and flashed in fastboot. While setting up the phone, got prompt for Jan security update. Installed it and check for Feb update. Also downloaded and installed. Guess I had some kind of glitch in 7.1.1 that prevented me from receiving OTA's or sideloading with ADB. Figures.
Click to expand...
Click to collapse
I just saw your post in the other thread and was about to direct you here. I was in the same boat. My only guess is that the Oreo update isn't being sent to devices on Verizon's network, but security patches are? There's someone else who posted on these forums a while back with the same issue on Verizon.
I had even tried removing the Sim, rebooting, and checking over WiFi before manual flash. Still don't know what caused ADB sideload to fail.
Official March OTA added!
Official April OTA added!
I can't get adb sideload to work. Strange.... Anyone with an unlocked bootloader have success? TWRP won't do it either.
Unlocked BL
Slickademo said:
I can't get adb sideload to work. Strange.... Anyone with an unlocked bootloader have success? TWRP won't do it either.
Click to expand...
Click to collapse
Also can't get sideload to work with unlocked bootloader. TWRP didn't work for me either. Can't tell why exactly it isn't working. My next thought was to try with a MicroSD Card.
Nick1801 said:
Also can't get sideload to work with unlocked bootloader. TWRP didn't work for me either. Can't tell why exactly it isn't working. My next thought was to try with a MicroSD Card.
Click to expand...
Click to collapse
I tried micro SD card with stock recovery and it did not mount. I just read that the newest update kills USB connectivity (besides charging) so it's probably best not to update until they fix that
So has the OTA files actually helped anybody? I thought I had at least one verified successful adb sideload done on a previous OTA.
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Thank you :fingers-crossed:
I'm still on Android 8.1 and waiting stable Android 10
a1291762 said:
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Click to expand...
Click to collapse
can i use this patch update is 10.0.20.0. with new magisk without ubl n twrp, it just install magisk manager 2.04 and select this image for root acces thanks before.
ony89 said:
can i use this patch update is 10.0.20.0. with new magisk without ubl n twrp, it just install magisk manager 2.04 and select this image for root acces thanks before.
Click to expand...
Click to collapse
If you have a locked bootloader, you can't do anything.
Magisk and root is separate to TWRP on this phone. This image will help you get Magisk installed.
Instructions here
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
a1291762 said:
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Click to expand...
Click to collapse
Hi a1291762, as a noob could I ask you a few questions please?
Wanting to downgrade from Q to Pie, could I used your 10.0.20.0 vanilla boot with the Mi Flash Tool using the steps here, and then if I wanted to add root I could use the 10.0.20.0 patched boot with the guide here?
Thank you!
wassupjg said:
Hi a1291762, as a noob could I ask you a few questions please?
Wanting to downgrade from Q to Pie, could I used your 10.0.20.0 vanilla boot with the Mi Flash Tool using the steps here, and then if I wanted to add root I could use the 10.0.20.0 patched boot with the guide here?
Click to expand...
Click to collapse
You might want to check that people have been able to downgrade. I know that pie-oreo caused a modem issue.
You need a fastboot image to downgrade. Unless MiFlash has magic (I have never used it).
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Looks like you'll have to downgrade to 10.0.18.0 and then apply the 10.0.20.0 update, since I do not see a fastboot for 10.0.20.0.
You won't need the vanilla boot image because it is in the fastboot image.
One you have 10.0.20.0 installed you can use the 10.0.20.0 patched boot to install Magisk.
a1291762 said:
You might want to check that people have been able to downgrade. I know that pie-oreo caused a modem issue.
You need a fastboot image to downgrade. Unless MiFlash has magic (I have never used it).
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Looks like you'll have to downgrade to 10.0.18.0 and then apply the 10.0.20.0 update, since I do not see a fastboot for 10.0.20.0.
You won't need the vanilla boot image because it is in the fastboot image.
One you have 10.0.20.0 installed you can use the 10.0.20.0 patched boot to install Magisk.
Click to expand...
Click to collapse
Much appreciated, I had thought your vanilla boot and the fastboot images were the same things, once I downgrade to 10.0.18.0, how would I apply the 10.0.20.0 update as I assume the next xiaomi system update would skip straight to the latest Q build?
wassupjg said:
Much appreciated, I had thought your vanilla boot and the fastboot images were the same things, once I downgrade to 10.0.18.0, how would I apply the 10.0.20.0 update as I assume the next xiaomi system update would skip straight to the latest Q build?
Click to expand...
Click to collapse
I'm not totally sure...
There are links to the OTA zips around. A thread about Android 10 showed how to install one using the stock recovery... I guess the same works for 10.0.20.0?
As a Linux user I would be inclined to try and use command line tools to install the OTA zip... But I don't even know if that's a thing
wassupjg said:
...
Click to expand...
Click to collapse
Apparently there was a 10.0.20.0 fastboot, but it's not on the fastboot thread
I don't know where I got this URL from but 10.0.20.0 is http://bigota.d.miui.com/V10.0.20.0...0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
a1291762 said:
Apparently there was a 10.0.20.0 fastboot, but it's not on the fastboot thread
I don't know where I got this URL from but 10.0.20.0 is http://bigota.d.miui.com/V10.0.20.0...0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
Click to expand...
Click to collapse
Thanks dude, I did find it here in the posts, I guess the OP isn't updated anymore, I've just had too many problems with Q, it sucks imo, once I back up everything I'll give it a go, by any chance do you know any good app and general backup apps that make things easy?
wassupjg said:
by any chance do you know any good app and general backup apps that make things easy?
Click to expand...
Click to collapse
I bought titanium backup pro a long time ago and still use it. Back in the day, the free version was annoying for whole device restore. But it's let me move across 5 devices and saved me from losing data on many occasions so I consider it money well spent.
I backup and then rsync /sdcard to a computer daily (CLI tools from cron). For restore I copy the files back (if needed) and then restore.
I only backup user apps, call history and SMS. System apps don't restore properly these days.
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
The May update is 11.0.5.0. I have a patched boot with Magisk 20.4
https://yasmar.net/xda/patched_boot_11.0.5.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.5.0.img.gz
Did you update from 9.0? or from previous 10.0 ROM?
smicas said:
Did you update from 9.0? or from previous 10.0 ROM?
Click to expand...
Click to collapse
I went from Pie 10.0.20.0 to Q 11.0.4.0 to 11.0.5.0.
I wasn't offered 11.0.2.0.
a1291762 said:
I went from Pie 10.0.20.0 to Q 11.0.4.0 to 11.0.5.0.
I wasn't offered 11.0.2.0.
Click to expand...
Click to collapse
Thanks,
And from 10.0.2.0 to 11.0.4.0 - did you also update the same way, or did you clean flash from fastboot?
smicas said:
And from 10.0.2.0 to 11.0.4.0 - did you also update the same way, or did you clean flash from fastboot?
Click to expand...
Click to collapse
I've been using the same process for every OTA since 10.0.4.0.
Only a few updates caused issues.
10.0.9.0 needed a newer TWRP.
Magisk 20 broke TWRP.
When I did the android 10 upgrade I had an issue with some Magisk modules that I had not upgraded. It would have been fine if I'd upgraded them first. I disabled them to boot and then installed the upgraded modules.
Does anyone have the boot img from version 11.0.10.0?
abracadabra02099 said:
Does anyone have the boot img from version 11.0.10.0?
Click to expand...
Click to collapse
There is no such version for Mi A2 Lite.
11.0.5.0 is the newest release (Android 10 with May security patches).
Hi @a1291762,
I'd like to know if
. it is possible to downgrade from 11.0.5 to latest Android 9
. it is possible to use a full working Gcam on 11.0.5 and how to install it.
Thank you!
I'm currently on v. 10.0.18 (I stopped the latest update for Pie) and I have a CSOT screen.
DekiS3 said:
Hi @a1291762,
I'd like to know if
. it is possible to downgrade from 11.0.5 to latest Android 9
. it is possible to use a full working Gcam on 11.0.5 and how to install it.
Thank you!
I'm currently on v. 10.0.18 (I stopped the latest update for Pie) and I have a CSOT screen.
Click to expand...
Click to collapse
It was only the first Android 10 (11.0.2.0) that had issues with screens. The 2 followups (11.0.4.0 and 11.0.5.0) work on all phones.
In theory, it is possible to downgrade back to 10.0.18.0 using a fastboot image.
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
To get to 10.0.20.0 you'll need to get the OTA zip and install that. I'm not sure how to do that, but this process seems like it should work: https://forum.xda-developers.com/mi-a2-lite/how-to/how-to-manual-update-v11-0-4-0-users-t4082815
It might be worth checking if people have done the downgrade successfully. For example, the Pie-Oreo downgrade caused modem issues.
There's heaps of threads where people discuss gcams, but I do not know what the state is because I use the stock camera app.
DekiS3 said:
...
Click to expand...
Click to collapse
Apparently there was a 10.0.20.0 fastboot, but it's not on the fastboot thread
I don't know where I got this URL from but 10.0.20.0 is http://bigota.d.miui.com/V10.0.20.0...0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
a1291762 said:
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
The May update is 11.0.5.0. I have a patched boot with Magisk 20.4
https://yasmar.net/xda/patched_boot_11.0.5.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.5.0.img.gz
Click to expand...
Click to collapse
First of all, i never had magisk on android 8-9 before,then i want to install it on android 10 , i'm quiet understand with the fastboot step, but i don't know if its ok to do it right on a10, i mean if i just boot with your android 10 patched_boot then install magisk, did i just rooted my phone ?
I just wanted to install GCam btw
Thank you.
I installed LineageOS 18.1 (Android 11) on my OP7P and want to boot (or flash) TWRP.
There is a lot of different information about the state of TWRP on Android 11.
I hope someone could clearify the following questions:
1. Does TWRP [3.5.2] support Android 11?
the release notes of 3.5.1 state that they "prepared a mini release before Android-11 support."
The release notes of 3.5.2 don't mention android 11 at all.
There are various people in the LOS18.1 thread that can boot twrp, so I assume there is some kind of (partial) support.
2. What if 'fastboot boot twrp.img' doesn't work?
For me I can't boot (or flash) TWRP (on LOS18.1).
So as the twrp/lineage os guide says I do:
fastboot boot twrp.img
Click to expand...
Click to collapse
It finished succesfull, but my phone stays in fastboot and doesn't reboot.
The TWRP guide says the following:
If fastboot boot command doesn't work you need to root your device and flash the TWRP installer (remember that flashing the TWRP installer you will lose the root).
Click to expand...
Click to collapse
I find this a very vague description; what do they mean with "doesn't work"?
(when I flash twrp it results in an unbootable phone, might be related to a/b partitions, but I have not enough knowledge of that)
3. Does TWRP work on encrypted phones?
I found various posts that suggest that TWRP doesn't work on encrypted phones.
I can't find any reliable source that supports that statement.
Twrp says this, but that doesn't clearify things at all.
I hope someone could give me some answers, or guide me to some reliable source so I can find it myself.
I find the documentation of LineageOS and TWRP lacking in that perspective.
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
lenigma1too said:
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
Click to expand...
Click to collapse
I also think there is no official TWRP for android 11, but twrp doesn't make this very clear in their docs.
Multiple people are claiming they are able to (at least) boot twrp on Android 11.
LineageOS 18.1 is Android 11 (but I will clearify the post).
Thank you for your reply
there is now a working TWRP version for Android 11.
Nebrassy version: https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
worked for me with 'fastboot boot TWRP-3.5.1-guacamole-Nebrassy-3.img'
Hi, today i flash the december update in my pixel 6a, now i can´t root, magisk patch the image but when i flash it (fastboot flash boot magisk-patched.img) the phone join in a bootloop and need to reinstall the rom, any help?
I have seen below another thread with the same problem but they talk about the QPR2 beta and I don't know if the same procedure applies with the December update.
Thanks!
What do you mean? If bootloader is unlocked and you run 'fastboot flash boot "file" ' will it work fine.
You can also check the magic managers logs on /cache.
dannyzamora said:
Hi, today i flash the december update in my pixel 6a, now i can´t root, magisk patch the image but when i flash it (fastboot flash boot magisk-patched.img) the phone join in a bootloop and need to reinstall the rom, any help?
I have seen below another thread with the same problem but they talk about the QPR2 beta and I don't know if the same procedure applies with the December update.
Thanks!
Click to expand...
Click to collapse
Make sure you don't have any Magisk mods that may need disabling and updating.
And no, the same procedure does not apply for the stable December update as it does for QPR2 Beta 1.
JonasHS said:
What do you mean? If bootloader is unlocked and you run 'fastboot flash boot "file" ' will it work fine.
You can also check the magic managers logs on /cache.
Click to expand...
Click to collapse
Yes, that is the procedure I am referring to, the one I have always used, it is strange, as I said, I have followed the same steps as always:
1. Download Factory image of december for Pixel 6a (the last one available in the web).
2. Extract boot.img
3. Patch it with latest magisk app (25.2)
4. Reboot to fastboot
5. Use command "fastboot flash boot magisk-patched.img"
The command is applied correctly but when rebooting the terminal stays in the "Google" logo and after a while it reboots and returns to the same "Google" screen, so in a loop.
Lughnasadh said:
Make sure you don't have any Magisk mods that may need disabling and updating.
An no, the same procedure does not apply for the stable December update as it does for QPR2 Beta 1.
Click to expand...
Click to collapse
I don't have any modules installed, it's a clean install of everything.
It will sound stupid but... I did the steps indicated in the other thread and I have solved the problem, I have root.
I downloaded the december image of the Pixel 7 Pro, extracted the boot.img, patched it with magisk and flashed it with the usual command "fastboot flash boot magisk-patched.img" and it let me boot without problems and working root.
thats crazy, Im on december update A13 and I had no issues whatsoever.
booted the image and then flashed through magisk instead of flashing it directly but still... if it were broken that wouldnthave worked
G5-User7080 said:
thats crazy, Im on december update A13 and I had no issues whatsoever.
booted the image and then flashed through magisk instead of flashing it directly but still... if it were broken that wouldnthave worked
Click to expand...
Click to collapse
I know, the truth is that it makes no sense that I have given me this problem because I did not see anyone else with the December update talking about this particular problem, the closest thing was the post I mentioned with the beta, the phone had just arrived from the SAT but I do not think this influenced the problem, it came with the November update and I updated it to the December update.
You mentionned you downloaded the image for the Pixel 7 pro. I assume you made a type and are not flashing a pixel 7 pro image to a pixel 6a? If not then get the right image file.
Otherwise I suggest using the Pixel Flasher software posted in this forum. It's a really good piece of software.
No hassle with manual flashing anymore.
With Pixel Flasher I even update to new security patches with keeping root in like 4-10 minutes, by just downloading the image and then clicking a couple buttons