Related
I've been messing with root on my G965F and, after a few ROM changes a decided to return to One UI, but my camera simply doesn't work. I'de flashed the CSB3 vendor image in order to install pixel experience ROM.
At the time I did my One UI backup, but I didn't save the original vendor Image, and now I can't completely restore it. Therfor my camera refuses to function.
I've tried restoring my device using odin, but becouse I've TWRP installed it gave me an error (a very scary one), "an error has occurred while updating the device software s9+...". It prompet me to use Smart switch emergency recovery which failed to recognise my device. My solution was to flash TWRP again (Fortunately it worked, and I was back to TWRP).
I restored my one UI backup without the vendor image, and the camera still doesn't work.
If I understood this corectly, if I restore my vendor image the camera will fuction back again. But I'am open to sugestions.
Thanks
RichNoob said:
I've been messing with root on my G965F and, after a few ROM changes a decided to return to One UI, but my camera simply doesn't work. I'de flashed the CSB3 vendor image in order to install pixel experience ROM.
At the time I did my One UI backup, but I didn't save the original vendor Image, and now I can't completely restore it. Therfor my camera refuses to function.
I've tried restoring my device using odin, but becouse I've TWRP installed it gave me an error (a very scary one), "an error has occurred while updating the device software s9+...". It prompet me to use Smart switch emergency recovery which failed to recognise my device. My solution was to flash TWRP again (Fortunately it worked, and I was back to TWRP).
I restored my one UI backup without the vendor image, and the camera still doesn't work.
If I understood this corectly, if I restore my vendor image the camera will fuction back again. But I'am open to sugestions.
Thanks
Click to expand...
Click to collapse
Simply, copy your data and download the official pie from samfirm or where you want and flash it with the latest odin.. have a thread about latest pie for s9 plus you can chek it..
forkatar12 said:
Simply, copy your data and download the official pie from samfirm or where you want and flash it with the latest odin.. have a thread about latest pie for s9 plus you can chek it..
Click to expand...
Click to collapse
I already tried that. But when I attempt to flash it using odin it gives me an error on my phone "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 4 BINARY: 3".
I might be wrong, but to my understanding from your last post you tried to install an original firmware image with bootloader v3 while your phone already has a bootloader v4. If I understand everything correctly you need to use a firmware version (for your region) containing a bootloader v4 for it to install correctly - otherwise it won't install since bootloaders aren't backwards compatible.
If you've flashed a non-stock recovery like TWRP*, you can not use the OTA update feature. You need to flash the full ROM via TWRP.
* TWRP is now officially supported, make sure you flash that version if you're using an older, unofficial TWRP.
1. Obtain the ROM you want to install. Make sure the download is from miui.com if you want stock
Official site -> My phone is the EEA version, so I use the 'Mi 9T EEA' tab. The website does not update links immediately after a ROM update is released, so you may have to do a bit of digging if you want a very recent update.
You can also check ROM links on third party sites like ezbox.idv.tw, again, make sure the actual download links are from miui.com and not somewhere else.
Latest EEA ROM(Android 10) as of 2020-10-24 -
V12.0.3.0.QFJEUXM
Nightly official LineageOS builds
2. Get into TWRP
Either run 'adb reboot recovery'
Or power phone off and boot into TWRP by holding PWR+VOL_UP during boot
3. Upload the ROM to the phone
Code:
adb push ~/Downloads/[B]miui_DAVINCIEEAGlobal_V12.0.3.0.QFJEUXM_12b99693bc_10.0.zip[/B] /sdcard/
4. Flash the ROM via TWRP
5. Flash Magisk if you use it, because flashing the ROM deletes it.
6. Remove the update file:
Code:
adb shell rm /sdcard/[B]miui_DAVINCIEEAGlobal_V12.0.3.0.QFJEUXM_12b99693bc_10.0.zip[/B]
That's it! Reboot your phone into your new ROM!
Also check out my debloat list and my detailed phone settings.
Additional note - formatting /system will brick your phone and you'll have to recover using a fastboot ROM.
Please can I get the 10.3.15 ota zip for the official recovery I cant get the update and my phone is now on 10.3.12 it always say no update available even though I have done the update before and returned to 10.3.12 but it does show it to me again and also my otg doesn't work . please help me
Benfatica said:
Please can I get the 10.3.15 ota zip for the official recovery I cant get the update and my phone is now on 10.3.12 it always say no update available even though I have done the update before and returned to 10.3.12 but it does show it to me again and also my otg doesn't work . please help me
Click to expand...
Click to collapse
OTA zip is here => https://bigota.d.miui.com/V10.3.15....PFJEUXM-V10.3.15.0.PFJEUXM-14bc6a5788-9.0.zip
Micdu70 said:
OTA zip is here => https://bigota.d.miui.com/V10.3.15....PFJEUXM-V10.3.15.0.PFJEUXM-14bc6a5788-9.0.zip
Click to expand...
Click to collapse
Thanks,I was able to get it over ota but it doesn't come now has xiaomi removed it or something
I also get this message if I try to download the latest package. Is something wrong with my phone
It looks like the 10.3.15.0 update was pulled and 10.3.12.0 is now latest.
C0rn3j said:
It looks like the 10.3.15.0 update was pulled and 10.3.12.0 is now latest.
Click to expand...
Click to collapse
Ok thanks, but why though ??
My last update is 10.3.11.0 July security patch
C0rn3j said:
If you've flashed a non-stock recovery like TWRP, you can not use the OTA update feature. You need to flash the full ROM via TWRP.
So how to get around this when the updater is telling you there is an incremental update?
Simple, we tell the updater to download the full image instead, move the update from the original folder so MIUI won't attempt to upgrade from it on next reboot, boot into TWRP and flash the image there.
1. Settings -> About Phone -> System update -> three dots -> Download latest package
2. Get filename of the update:
3. You now have the filename of the update. I got miui_DAVINCIEEAGlobal_V10.3.15.0.PFJEUXM_b6738621e2_9.0.zip and will be using this name throughout the rest of this how-to, replace the examples accordingly based on what name you got.
4. (optional) Backup the latest ROM file to your PC:
5. Prevent MIUI from seeing the update file and trying to update from it on accident by moving the file a folder higher:
6. Power phone off
7. Boot into TWRP by holding PWR+VOL_UP during boot
8. Flash the ROM via TWRP
9. Flash Magisk if you use it, flashing the ROM deletes it.
10. Boot back into Android and remove the update file:
That's it!
You can also download the full ROM directly through miui.com, but keep in mind the website does not instantly update the link there after a ROM update is released.
https://en.miui.com/download-361.html#619 -> My phone is the EEA version, so I use the 'Mi 9T EEA' tab.
Page best viewed in Firefox, clicking on the lock icon -> Arrow icon in the security tab -> Disable protection, since Xiaomi can't even set their website up properly.
In my case the ROM download through phone was corrupted and I had to edit the site URL from the filename I got to get a proper update file:
Click to expand...
Click to collapse
Redmi K20 Open Beta File Link?
Wrong thread.
Don't quote the OP, it clutters the thread.
For people who want the 10.3.15.0 update. I uploaded it to mega. Link is here:
https://mega.nz/#!pddQUaBL!s5En8LWaxWciUyNowU8_rYYMk2D48Dj8J7_PbJwv0kc
C0rn3j said:
...
https://en.miui.com/download-361.html#619 -> My phone is the EEA version, so I use the 'Mi 9T EEA' tab.
Page best viewed in Firefox, clicking on the lock icon -> Arrow icon in the security tab -> Disable protection, since Xiaomi can't even set their website up properly.
...
Click to expand...
Click to collapse
The most accurate, updated and actual site for Mi 9t/K20 (davinci) firmware/rom - https://mirom.ezbox.idv.tw/en/phone/davinci/
10.3.15 ota is back online, just received it
Hey @C0rn3j
I am on stock 10.3.12.0 PFJEUXM and TWRP 4PDA 3.3.1.-2 fix and Magisk.
My questions:
1. Is it worth the upgrade to MIUI 11 as it is still Android 9
2. If I flash it through TWRP, did you loose any dual app settings? (as I lost dual apps while backing up the phone with TWRP and Titanium backup)
3. as you said I have to flash the Magisk again, did you choose the latest or the same as was installed on the phone before the upgrade?
Thanks in advance for reply
rastip said:
Hey @C0rn3j
I am on stock 10.3.12.0 PFJEUXM and TWRP 4PDA 3.3.1.-2 fix and Magisk.
My questions:
1. Is it worth the upgrade to MIUI 11 as it is still Android 9
2. If I flash it through TWRP, did you loose any dual app settings? (as I lost dual apps while backing up the phone with TWRP and Titanium backup)
3. as you said I have to flash the Magisk again, did you choose the latest or the same as was installed on the phone before the upgrade?
Thanks in advance for reply
Click to expand...
Click to collapse
1. Security updates.
2. I don't use dual apps so I wouldn't know. AFAIK people had issues with using the backup/restore functionality of TWRP on that version. You should probably update it as I believe latest is -4
3. Latest.
C0rn3j said:
1. Security updates.
2. I don't use dual apps so I wouldn't know. AFAIK people had issues with using the backup/restore functionality of TWRP on that version. You should probably update it as I believe latest is -4
3. Latest.
Click to expand...
Click to collapse
I have Nova Launcher, do you use default or as well external one?
Do you think Nova will stay untouched with this upgrade?
rastip said:
I have Nova Launcher, do you use default or as well external one?
Do you think Nova will stay untouched with this upgrade?
Click to expand...
Click to collapse
Nothing will happen to it
If the Magisk have to be flashed again, does it mean all the hide settings which were there before has to be set again or stay there from the old version? I have few apps in Magisk hide root, so just wondering how this will be affected with rom update
A second question:
I am on 10.3.12.0 not upgraded yet to 10.3.15.0.
Can I upgrade straight to V11.0.2.0 or first to 10.3.15.0 and then to V11?
---------- Post added at 05:27 PM ---------- Previous post was at 05:09 PM ----------
C0rn3j said:
1. Security updates.
2. I don't use dual apps so I wouldn't know. AFAIK people had issues with using the backup/restore functionality of TWRP on that version. You should probably update it as I believe latest is -4
3. Latest.
Click to expand...
Click to collapse
While flashing did you untick Recovery in the TWRP as I believe the whole 2,2GB ZIP has recovery image and could be flashed and overwrite the TWRP?
Your guide not working, twrp failed to install the update "file corrupted".
I've downloaded the OTA package from "http://c.mi.com//miuidownload/detail?device=1700361" and twrp very happy to install this file, my Mi_9T at the latest update 11.
Unfortunately the archive downloaded through the Updater cannot be flashed as is through TWRP (message: file corrupted)
miui_RAPHAELEEAGlobal_V11.0.3.0.QFKEUXM_153f9511ae_10.0.zip
Hello everyone,
so I have been playing around with my HTC U11. I unlocked the bootloader and installed the newst TWRP version. Then I flashed it to Lineage 16. However I could not install the HTC Edge Sense App and since I couldnt find any answers to that problem decided to flash back to stock rom and then update to Android 9.0 and get my Edge Sense back.
So I checked for my device CID which is HTC_034 and downloaded myself the stock rom from the getdroidtips stock firmware collection (cant post link because I am new)
I did the MD5 Checksum and everything was fine. However when I try to sideload it via adb i get a zip file corrupt error and TWRP stops it. Then I tried pushing it and installing it through the install function of TWRP. I can push it onto the device but when I want to install it I get the same error again. Things I tried so far:
1. used an older version of TWRP
2. all the 4 stockroms available for the HTC_034 on said link
3. load the .zip onto an sd card, enter it and tell TWRP to install from there - didnt work either.
4. rename the .zip to package.zip (read it somewhere)
Everytime I get the Error that the .zip is corrupt. Checksums of all the files are ok...
Has anyone an idea what else I can do? I would actually be fine with lineage 16 if I could just get my HTC Edge Sense back (
Thanks in advance for your help
Headcannon: what if the problem ia for some reason the twrp? Could i somehow flash the stock rom without going through the TWRP?
I am not talking about removing it. I am talking about somehow flashing without using it. Maybe via adb or odin?
Then the stockrom should be able to install. If something goes wrong I can still boot into recovery and use TWRP to get LOS16 back.
Ok so since I read somewhere that on the pixels root access was necessary to get HTC Edge Sense running I installed Lineage 16, added GAPPS and then used Magisk to get root access.
I still can't install HTC Edge Sense. I even downloaded the apk and pushed it onto the phone but the install always stops and tells me it can't finish
So for now I can neither have stock rom nor Edge Sense - any suggestions because I am slowly running out of ideas
when manually updating is full OTA or factory image better or safer?
what are the pros and cons of each?
if you are rooted will it make a difference?
custom kernel issues people should know about before updating?
If you're rooted, download the factory image, extract the boot.img from the zip, patch it in magisk and move the patched image to your PC.
Sideload the OTS, reboot to bootloader, flash the patched boot.img and pretty much that's it.
This is how i do it
Basically what Svid said. However, you can also use Payload Dumper to extract the boot.img from the payload.bin in the OTA.zip - saves you the download of the full factory image. Nowadays mostly a preference kinda thing since downloading speed is rarely an issue.
Custom kernels will get wiped upon updating anyway, so make sure the kernel is updated for 12.1/L before flashing again. I know bluspark is not yet compatible, so you have to wait for that one. Also, the Pixel Addon Features Magisk module causes a bootloop for now.
Hi all.
I updated to the latest version last night, but I lost my root in the process.
I tired to re-root my GP6 yet unsuccessful. Anybody manage to do it?
Thanks.
Tried how? Assuming your bootloader is unlocked, the easiest way is probably:
Unhide Magisk on your phone for now (so PixelFlasher can find it to easily automatically patch your boot.img)
Enable USB debugging if you haven't already
Grab the T2B1 beta factory image (as by T2B1 it sounds like you're on the beta), and PixelFlasher
Use PixelFlasher to extract the boot.img from the factory image (red rocket icon right of the browse bar)
With your phone connected, hit Scan in the top right of PixelFlasher, and select your Pixel in the dropdown
With the extracted boot image extracted, hit "Patch" in PixelFlasher and let it do its thing
With the patched (band-aid icon) boot image selected, hit "Flash Boot" on the right, then let it do its thing again
You can hide Magisk again at this point.
You should have root back after doing all of that. Let me know if I missed anything or if it gets stuck anywhere.
Jaitsu said:
Tried how? Assuming your bootloader is unlocked, the easiest way is probably:
Unhide Magisk on your phone for now (so PixelFlasher can find it to easily automatically patch your boot.img)
Enable USB debugging if you haven't already
Grab the T2B1 beta factory image (as by T2B1 it sounds like you're on the beta), and PixelFlasher
Use PixelFlasher to extract the boot.img from the factory image (red rocket icon right of the browse bar)
With your phone connected, hit Scan in the top right of PixelFlasher, and select your Pixel in the dropdown
With the extracted boot image extracted, hit "Patch" in PixelFlasher and let it do its thing
With the patched (band-aid icon) boot image selected, hit "Flash Boot" on the right, then let it do its thing again
You can hide Magisk again at this point.
You should have root back after doing all of that. Let me know if I missed anything or if it gets stuck anywhere.
Click to expand...
Click to collapse
Have the same Problem, no root on latest Beta,
although following the above steps ( used them in the pasta for wach beta)
Anyone with root on newest Beta?
To be fair, I'm not rooting on the latest beta, I'm still on the standard TQ1A December release - the instructions I gave should apply to any version, but it's possible T2B1 has broken something. When you open the Magisk app, does it show that Magisk isn't installed, even after flashing the patched boot image?
Jaitsu said:
To be fair, I'm not rooting on the latest beta, I'm still on the standard TQ1A December release - the instructions I gave should apply to any version, but it's possible T2B1 has broken something. When you open the Magisk app, does it show that Magisk isn't installed, even after flashing the patched boot image?
Click to expand...
Click to collapse
Yes, same thing happened to me this morning after doing the common steps to retain root after applying an OTA. I then proceeded to patch the boot image using adb but stil no root access.
Edit. It appears that no one is able to root on T2B1, as someone said in the official guide rooting pixel 6 here on XDA
Same issue, tried with PixelFlasher, manual commands, diffrent Magisk versions, but still can't get it work
Strange, and interesting. May be worth filing a bug at the official Magisk github page if anyone is willing to go through the steps necessary to help troubleshoot the problem (doing all of the above with the latest debug version of Magisk, for starters; if you report a bug using any other version the bot will automatically close your issue). I would if I were running the beta or if we had working TWRP so I could backup and restore, but I juuust got my Pixel back to the way I like it on the non-beta after a factory reset.
Jaitsu said:
Strange, and interesting. May be worth filing a bug at the official Magisk github page if anyone is willing to go through the steps necessary to help troubleshoot the problem (doing all of the above with the latest debug version of Magisk, for starters; if you report a bug using any other version the bot will automatically close your issue). I would if I were running the beta or if we had working TWRP so I could backup and restore, but I juuust got my Pixel back to the way I like it on the non-beta after a factory reset.
Click to expand...
Click to collapse
I've already posted on Reddit r\Magisk [Help] Flashed magisk pathed pathed boot image T2B1.221118.006 don't works, but maybe submitting bug would be better. Yea, TWRP would be best but still nothing for A13 (and A12 I think). I remember that there was similar issue in older updates, but Canary made it work, but... not this time
Tried all the possible ways to root the phone, either using fastboot or Pixel Flasher, but no avail. Perhaps someone could successfully do it and tell all of us how
Same issue in Pixel 6a
Guys, see https://github.com/topjohnwu/Magisk/issues/6441.
It looks like Google released corrupted boot image.
To make it work, You need to patch and flash boot image from Pixel 7.
Pixel 6 -> Pixel 7 boot image.
Pixel 6 Pro -> Pixel 7 Pro boot image.
I don't know what about Pixel 6a.
So, should we download the same latest beta for pixel 7 and extract and patch the boot image inside of it?
BAlex9601 said:
So, should we download the same latest beta for pixel 7 and extract and patch the boot image inside of it?
Click to expand...
Click to collapse
Yea, everything else stays the same. Just after upgrade, instead of patching Pixel 6 boot.img, patch the one from Pixel 7 and flash it.
I've used Pixel Flasher for factory update and then in Magisk app I've patched image and then flashed it with fastboot flash boot <patched_boot.img>.
https://twitter.com/i/web/status/1602774339224367104
Yup broken.. should have read the thread.
m_pastuszek said:
Guys, see https://github.com/topjohnwu/Magisk/issues/6441.
It looks like Google released corrupted boot image.
To make it work, You need to patch and flash boot image from Pixel 7.
Pixel 6 -> Pixel 7 boot image.
Pixel 6 Pro -> Pixel 7 Pro boot image.
I don't know what about Pixel 6a.
Click to expand...
Click to collapse
Is this true? I'm downloading it now to test it. Will update later.
UPDATE:
Apparently, flashing Pixel 7 boot.img into Pixel 6 worked like a charm. I get the root back. Thanks guy!
Thanks for the hint regarding boot.img
I'm facing aslo this issue while updating
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.2-9152140'.
Update requires 'slider-1.2-9228550'.
Actually I'm on T1B3.221003.008
Any idea? -> flashed bootloader manually -> solved