Related
I have rooted my Xperia L stock ROM 15.3.A.1.17 and unlocked the bootloader. Now I wish to install TWRP recovery on a separate partition. As indicated on official TWRP page on Xperia L,
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily. Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility. The source for this utility is here.
This setup means that you must have a kernel or boot image installed that will use the FOTAKernel method. This utility is designed to work in conjunction with the current methods that most AOSP ROMs, like OmniROM or CyanogenMod, will support. Some rare stock kernels may also support the FOTAKernel method.
What does all this mean? It means that TWRP may not work on your device unless you install other custom software as well. Check with your ROM developer to see what they support.
Click to expand...
Click to collapse
However, the stock kernel does not support FOTAkernel method a.ka. extract_elf_ramdisk feature. The webpage does not address the issue of running TWRP on stock kernel. It's like a chicken and egg problem. To have TWRP running, one needs a custom kernel. To flash a custom ROM, one needs TWRP (or other custom recovery).
I can think of two possible ways of breaking this deadlock.
Possible method #1:
Flash TWRP using Recovery Installer Toolkit for Xperia L
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
Possible method #2:
Use a stock ROM image with TWRP integrated:
Code:
adb flash boot boot_twrp2.img
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
Possible method #3:
Boot into fastboot mode
Flash the TWRP image directly onto the boot partition
Code:
fastboot flash boot twrp.img
Reboot the phone which now should boot directly to TWRP recovery
The screen flickers when you are in recovery menu. However, flashing a custom ROM will fix the problem
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
As of now, I installed TWRP on FOTAkernel partition using official TWRP app. As expected, when I issue,
Code:
adb reboot recovery[/CODEL] the phone boots to stock recovery instead of TWRP. This behavior is expected as stock kernel knows nothing about TWRP being located on FOTAkernel.
I don't even know if any of the proposed methods work. However, before embarking down any one of those routes, I want to ask the community if I am overlooking any straightforward, less cumbersome alternative(s).
[B]Credits:[/B]
[LIST]
[*] Dees_Troy
[*] Kungfu73
[/LIST]
Holmes.Sherlock said:
I have rooted my Xperia L stock ROM 15.3.A.1.17 and unlocked the bootloader. Now I wish to install TWRP recovery on a separate partition. As indicated on official TWRP page on Xperia L,
However, the stock kernel does not support FOTAkernel method a.ka. extract_elf_ramdisk feature. The webpage does not address the issue of running TWRP on stock kernel. It's like a chicken and egg problem. To have TWRP running, one needs a custom kernel. To flash a custom ROM, one needs TWRP (or other custom recovery).
I can think of two possible ways of breaking this deadlock.
Possible method #1:
Flash TWRP using Recovery Installer Toolkit for Xperia L
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
Possible method #2:
Use a stock ROM image with TWRP integrated:
Code:
adb flash boot boot_twrp2.img
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
As of now, I installed TWRP on FOTAkernel partition using official TWRP app. As expected, when I issue,
Code:
adb reboot recovery[/CODEL] the phone boots to stock recovery instead of TWRP. This behavior is expected as stock kernel knows nothing about TWRP being located on FOTAkernel.
I don't even know if any of the proposed methods work. However, before embarking down any one of those routes, I want to ask the community if I am overlooking any straightforward, less cumbersome alternative(s).[/QUOTE]
Well, I think installing latest TWRP directly from stock XL ROM for first time is hard for everyone :D
I myself exactly used first method and worked fine. Also please note that in step 2 of method 1, you should install some Lollipop or KitKat versions of custom ROM (because current recovery is old)
I've not tested 2nd method, but it should work too.
I think these methods are the most simple ones if you want to jump from stock to latest TWRP ;)[COLOR="Silver"]
[SIZE=1]---------- Post added at 12:06 PM ---------- Previous post was at 11:53 AM ----------[/SIZE]
[/COLOR]Oh I forgot to mention that there is another (a little risky) way to use latest TWRP.
Using adb&fastboot run this command:
[B]fastboot flash boot twrp.img[/B]
[I](twrp.img is your recovery image name)[/I]
This command flashes recovery image directly to boot partition and because of that, when you power on the phone, you jump directly to TWRP recovery!
[B] Please note that in this method, the screen flickers when you are in recovery menu, but it's normal and gets fixed by flashing custom ROM
Note 2: immediately after booting to recovery, flash your custom ROM to avoid any problems![/B]
If there were any problems, simply flash stock ROM to get back to normal state.
Click to expand...
Click to collapse
Kungfu73 said:
Also please note that in step 2 of method 1, you should install some Lollipop or KitKat versions of custom ROM (because current recovery is old)
Click to expand...
Click to collapse
I don't get the point why I need a KitKat/Lollipop based custom ROM. What do you mean by current recovery being old?
Oh I forgot to mention that there is another (a little risky) way to use latest TWRP.
Using adb&fastboot run this command:
fastboot flash boot twrp.img
(twrp.img is your recovery image name)
This command flashes recovery image directly to boot partition and because of that, when you power on the phone, you jump directly to TWRP recovery!
.
Click to expand...
Click to collapse
I talked to @Dees_Troy on IRC about the issue and he suggested the same to me.
.
Please note that in this method, the screen flickers when you are in recovery menu, but it's normal and gets fixed by flashing custom ROM
Note 2: immediately after booting to recovery, flash your custom ROM to avoid any problems!
If there were any problems, simply flash stock ROM to get back to normal state.
Click to expand...
Click to collapse
I am also experiencing flickering. It's surprising to hear that the problem is supposed to go away with custom ROM. Do you have any idea how does having a custom ROM make any difference at all?
Holmes.Sherlock said:
I don't get the point why I need a KitKat/Lollipop based custom ROM. What do you mean by current recovery being old?
Click to expand...
Click to collapse
Well, the version of twrp that recovery installer app flashes, is 2.7 or something like that (not 3.0.2) and it may fail to flash MM or N ROMs (it's mentioned in some official custom ROMs download page to use latest TWRP)
Holmes.Sherlock said:
I am also experiencing flickering. It's surprising to hear that the problem is supposed to go away with custom ROM. Do you have any idea how does having a custom ROM make any difference at all?
Click to expand...
Click to collapse
If you mean by difference, fixing the flickering, well it wipes boot partition while flashing ROM, and (some of ROMs) flash latest TWRP to fota agian, and it fixes that
But if you mean difference between stock and custom ROM, well... it depends on your using. The most obvious ones are the improved security and more space for apps and tons of customizable and useful features, etc.
(And also sorry if I had mistakes in English!)
Kungfu73 said:
Well, the version of twrp that recovery installer app flashes, is 2.7 or something like that (not 3.0.2) and it may fail to flash MM or N ROMs (it's mentioned in some official custom ROMs download page to use latest TWRP).
Click to expand...
Click to collapse
The installer app lets you choose the version to flash. You can very well flash any version (of twrp.img) downloaded on your phone.
Holmes.Sherlock said:
The installer app lets you choose the version to flash. You can very well flash any version (of twrp.img) downloaded on your phone.
Click to expand...
Click to collapse
Oh this is what that makes difference!
On stock ROM, you can only use old TWRP's that are compatible with stock ROMs that don't support fota !
And also you should use the recovery that the app gives to you
Kungfu73 said:
On stock ROM, you can only use old TWRP's that are compatible with stock ROMs that don't support fota !
And also you should use the recovery that the app gives to you
Click to expand...
Click to collapse
The app gives a list of all recovery versions available on the official website for category `taoshan`. Are you sure that there is some TWRP version that does not support FOTA and works with stock ROM?
Holmes.Sherlock said:
The app gives a list of all recovery versions available on the official website for category `taoshan`. Are you sure that there is some TWRP version that does not support FOTA and works with stock ROM?
Click to expand...
Click to collapse
Well, if you check the official twrp website, there is no version before 2.8 for XL , and lol those removed ones are compatible!
Kungfu73 said:
Well, if you check the official twrp website, there is no version before 2.8 for XL , and lol those removed ones are compatible!
Click to expand...
Click to collapse
I am curious to know how come any TWRP version be compatible with stock ROM unless the recovery ramdisk is integrated with the boot image than being written onto FOTAkernel.
Holmes.Sherlock said:
I am curious to know how come any TWRP version be compatible with stock ROM unless the recovery ramdisk is integrated with the boot image than being written onto FOTAkernel.
Click to expand...
Click to collapse
I don't have much detailed information about that.
You can get help from experts
And could you finally flash and boot any version of twrp using that 3 methods?
Kungfu73 said:
And could you finally flash and boot any version of twrp using that 3 methods?
Click to expand...
Click to collapse
I tried method #2 and #3. Both works
android oreo 8.1 firmware leak for alldocube power m3 ,guys who own the pad have a try!and give a bug reply post.
alldocube power me oreo 8.1 firmware(0621)
a offical oreo 8.1 firmware with google play for power m3:http://www.mediafire.com/file/qev79...2B32.Neutral.8.1.V01.01.20190118user.zip/file
The firmware is working. One problem: after installation in TWRP package OpenGapps the system crashes. I couldn't find the replacement option (arm64, 8.1). Energy saving is good. Root access - Magisk.
P.S.: Build OpenGapps UNOFFICIAL is suitable for installation and works after components are updated (for example, with Yalp Store or Aurora App Store, F-Droid & etc.)
P.P.S.: If someone decides to install the firmware - must first make a backup of the NVRAM!!! Because the firmware will have to be installed with formatting and the nvram section will die. After flashing the firmware, it must be restored from the saved backup.
For me I got Problems with the display.. Its kinda over saturated.
If someone can explain the rights step to flash this rom would be nice. I cant install twrp over the Flash tool i used this for flashing twrp:
https://forum.xda-developers.com/android/general/cube-power-m3-tablet-twrp-img-t3772179
Hai_Duong said:
For me I got Problems with the display.. Its kinda over saturated.
If someone can explain the rights step to flash this rom would be nice. I cant install twrp over the Flash tool i used this for flashing twrp:
https://forum.xda-developers.com/android/general/cube-power-m3-tablet-twrp-img-t3772179
Click to expand...
Click to collapse
Take my version TWRP specifically for Oreo (the same in Russian how to install and patched Magisk boot.img to obtain root-rights): hire.
The saturation of the screen is comfortable for me, Occasionally settings of installed programs fly off.
TWRP Oreo
patched boot
config.gz in /proc fs
wangyiling said:
android oreo 8.1 firmware leak for alldocube power m3 ,guys who own the pad have a try!and give a bug reply post.
alldocube power me oreo 8.1 firmware(0621)
Click to expand...
Click to collapse
running linux kernel was configured to have /proc/config.gz. The configuration for this is found in
General setup
[*] Kernel .config support
[*] Enable access to .config through /proc/config.gz
with oreo 8.1...
treble checker reports device to be supported by Project - only with A-partition.
did anyone tried out to switch to GSI image?
cmarxmeier said:
tried out to switch to GSI image
Click to expand...
Click to collapse
Theoretically, should be suitable all the firmware from this theme and some of this. But we need TWRP support Treble, if I understand correctly (I tried the project on another device, everything was already done).
Treble works. As an experiment, I launched Omni 8.1. Started, but gives error 'com.android.phone has stopped'. The system image installed through fastboot (my TWRP isn't able to install to the system partition). The bootloader must be unlocked.
AOSiP Pizza Alpha [EXPERIMENTAL] - wi-fi, sound work, phone don't.
[9.0.0] ArrowOS (Android 9) - very quite good, but again the phone module. Need a system.img way to rebuild, or looking for a fix. In the firmware theme this is the main question. And in general, I liked the firmware, fast response and fast touch interface.
https://megaup.net/6u3i/Y5352.CUBE.T1001.MID.2+32.Neutral.8.1.V01.01.20181210user.zip
also some one can try this new power m3 8.1 firmware .
it's not beta .
wangyiling said:
also some one can try this new power m3 8.1 firmware
Click to expand...
Click to collapse
I already have this version installed. The work of the Treble Project checked on it. Firmware international, Google applications available, fixed some bugs. The installation also requires restoring the nvram partition.
Here's an updated TWRP 3.2.1-0 x64 for Oreo with support for the Treble Project (my port from Infinix X571): AFH
ViAlexSt said:
Theoretically, should be suitable all the firmware from this theme and some of this. But we need TWRP support Treble, if I understand correctly (I tried the project on another device, everything was already done).
Treble works. As an experiment, I launched Omni 8.1. Started, but gives error 'com.android.phone has stopped'. The system image installed through fastboot (my TWRP isn't able to install to the system partition). The bootloader must be unlocked.
AOSiP Pizza Alpha [EXPERIMENTAL] - wi-fi, sound work, phone don't.
[9.0.0] ArrowOS (Android 9) - very quite good, but again the phone module. Need a system.img way to rebuild, or looking for a fix. In the firmware theme this is the main question. And in general, I liked the firmware, fast response and fast touch interface.
Click to expand...
Click to collapse
ViAlexSt said:
I already have this version installed. The work of the Treble Project checked on it. Firmware international, Google applications available, fixed some bugs. The installation also requires restoring the nvram partition.
Here's an updated TWRP 3.2.1-0 x64 for Oreo with support for the Treble Project (my port from Infinix X571): AFH
Click to expand...
Click to collapse
nice
wangyiling said:
https://megaup.net/6u3i/Y5352.CUBE.T1001.MID.2+32.Neutral.8.1.V01.01.20181210user.zip
also some one can try this new power m3 8.1 firmware .
it's not beta .
Click to expand...
Click to collapse
Firmware brings up DualWifi again - 5GHz stopped working in former version.
EngineerMode.apk seems to be removed from priv-app's in this release - restoring manually from old image did not help - app crashes.
No easy way to set IMEI on device without MTK EngineeringMode.
cmarxmeier said:
Firmware brings up DualWifi again - 5GHz stopped working in former version.
EngineerMode.apk seems to be removed from priv-app's in this release - restoring manually from old image did not help - app crashes.
No easy way to set IMEI on device without MTK EngineeringMode.
Click to expand...
Click to collapse
for imei restore ,i think mtk sn write tool will do some help
wangyiling said:
for imei restore ,i think mtk sn write tool will do some help
Click to expand...
Click to collapse
mtk sn write tool did the job. - shows up with correct IMEI and VoLTE 4G.
patched boot.img with magisk
- works like a charm so far.
Looking forward to check USB-C Port with Icy Box to get Ethernet/HDMI device listed on USB-Bus.
wangyiling said:
https://megaup.net/6u3i/Y5352.CUBE.T1001.MID.2+32.Neutral.8.1.V01.01.20181210user.zip
also some one can try this new power m3 8.1 firmware .
it's not beta .
Click to expand...
Click to collapse
Someone does have TWRP recovery for this one? Trying to port old one, but getting buggy rotated recovery...
fraddy91 said:
Someone does have TWRP recovery for this one? Trying to port old one, but getting buggy rotated recovery...
Click to expand...
Click to collapse
Compile yourself by adding the lines:
# TWRP
......
RECOVERY_TOUCHSCREEN_SWAP_XY := true
RECOVERY_TOUCHSCREEN_FLIP_Y := true
Or Phils recovery.
Ultimate Guide for Flashing GENRIC SYSTEM IMAGE.
Contents:
Intro
how to flash gsi.
how to get rooted.
gapps issues
how to get back to non treble rom from gsi or treble enabled builds.
Introduction and basic information:
GSI means Generic System Image, which can be flashed over any Treble Device.
So, in simple words : same System.img can be flashed over multiple devices having Treble Support.
This happens as we now have a separate /vendor partition where all the vendor hals are stored.
Now, this will help to do easy bring ups, Treble builds are smooth af y'all know that and you'll get to flash aosp treble rom
Also, if you own 2-3 treble devices, now you'll just have to download one system.img xD it'll work for all of em ( if treble supported )
How to get Treble Support?
Flashing Treble TWRP won't give you treble support. Keep that in Mind. It'll just mount the partition in the recovery, so that vendor img can be flashed.
To get Treble Support, you'll need to flash a latest ROM which has vendor image compiled with the latest changes by mikeNG, once you flash such a ROM, you'll get the vendor stored in the vendor partition, and after that you can flash any GSI ( as it's just System.img, and all our device specifics are in /vendor so it won't mess with that)
Instructions:
Download Official LineageOS-15.1 treble enabled build from here
Download treble enabled twrp from here
Move both the downloaded files to external sd card (recommended)(optional)
boot in twrp
move to wipe option from twrp.
advanced wipe.
select data and then check if its in ext4 if not format it to ext4 ( do this from official twrp by @celoxocis )
then go to install and install the recovery provided above.
reboot to recovery.
wipe system, data, dalvik, cache & internal storage recommended.
install the lineage os zip and reboot.
download GSI of any rom of your choice. if it is in zipped format extract it and make sure you have a *.img
boot into twrp
wipe anything other than boot, micro sd & vendor
go to install option and then select install image button on bottom right corner
select the gsi of your choice which you have downloaded and install it on system partition.
reboot to recovery (important)
flash mind the gapps if you are going to use gapps in your rom. ( important open gapps have a few issues on treble like many of times gapps dont get flashed or shows some error)
reboot
Kudos you have now flashed a Genric System Image on your Lenovo P2.
for how to get rooted with magisk refer to next post.
and List Of GSI is available here
if you have any doubts even after reading this ultimate guide feel free to post it i will try to answer it and help you with that.
after following instruction as mentioned above
* download the magisk from here
* flash it normally.
A list of GSI and download links can be found here.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Only A arm64 gsi are supported well on our device and based on arch of our device
how to get back to non treble rom?
* Download the non treble rom your choice
* boot into twrp do wipes as suggested on rom's thread and then flash the rom package no need to mess with vendor partition.
I have managed to flash Dirty Unicorns Rom and its working pretty much well.
Here are some screen shots.
Volte working on GSI?
Volte working on any gsi?
advaithbhat said:
Volte working on any gsi?
Click to expand...
Click to collapse
My network provider don't use volte you can try and tell me
Sent from my Phh-Treble vanilla using Tapatalk
I'm on codeexilir's twrp, can't I use that twrp to flash official los 15.1 to get vendor image and then flash any GSI. Or it is mandatory to use los twrp?
abdal2006 said:
I'm on codeexilir's twrp, can't I use that twrp to flash official los 15.1 to get vendor image and then flash any GSI. Or it is mandatory to use los twrp?
Click to expand...
Click to collapse
I believe You can but I haven't tested that.
Sent from my Phh-Treble vanilla using Tapatalk
If i want to change the gsi img then should i clean flash the los 15.1 again?
imPro01 said:
If i want to change the gsi img then should i clean flash the los 15.1 again?
Click to expand...
Click to collapse
No. Just don't wipe vendor & boot just change GSI
Sent from my Phh-Treble vanilla using Tapatalk
abhayruparel said:
No. Just don't wipe vendor & boot just change GSI
Click to expand...
Click to collapse
Thank you for reply
1) If i go to recovery and flash the new GSI img without anything wipe then it'll work?
2) If i want to go back to Los then how to do it?
Thx abhayruparel.
There is not an aosp p beta yet, no?
After flashing GSI NFC is not working
I can't make any gsi work.Always returns password and reset phone screens on reboot.Entering password says password accepted but decryption unsuccessful.Reset phone takes to TWRP but does nothing and reboots to the same password screen.What to do?
rexit1979 said:
I can't make any gsi work.Always returns password and reset phone screens on reboot.Entering password says password accepted but decryption unsuccessful.Reset phone takes to TWRP but does nothing and reboots to the same password screen.What to do?
Click to expand...
Click to collapse
Changing system and data to ext4 will do the trick probably
Miltonbaidya88 said:
Changing system and data to ext4 will do the trick probably
Click to expand...
Click to collapse
Both are already on ext4.
After flashing gsi got decryption unsuccessful error. How to solve that?
something is very wrong......
First if I flash lineage then any other gsi like pixel experience, it gives me decryption unsuccessful error.... I'm not even able to format the storage to remove encryption. I did format the encryption using an older version of twrp as the twrp provided for treble gives an error like ''
Unable to format data. Unble to remove encryption
-Now When I formatted data using earlier twrp and hen flashed the treble one and then flashed lineage. Booted and it still encrypted my phone. So the loop goes on again.
I dont know whats wrong. Treble flashing should be easy... been awake since last night trying to make it ork by using different combinations but no luck.
can anyone help?
Is there any way to enable volte in GSI?
Hi all.
So, as we know with recent MIUI update Xiaomi screwed our whyred. And this gave birth to many questions which is like a struggle for many users to find all those answers. So, I tried to answer all your questions. If you think your question isn't included please feel free to ask.
Q1: What is this "Anti-Rollback" thing?
A: Its a security measure that Google brought with the release of Android Oreo. It makes sure that your data is secure even when phone is stolen or if any attacker tries to downgrade the software and wants to gain control over your data.
Q2: How is this harmful to my device?
A: Well, as a security measure it should never give you a hard-brick. When someone tries to downgrade, it should display a warning and get turned off but there's difference between how things should work and how Xiaomi does. As Google has stated, "Anti-Rollback" should get automatically turn off when the user unlocks the bootloader but in case of MIUI even unlocked users are getting hard-bricks. Hopefully the developers of MIUI should push an update soon and if they don't, our beloved devs will find a way for sure
Q4: So, what now? Will Xiaomi solve this issue?
A: We do not know. But our beloved developers in the XDA-Forum will find a way for sure
Q5: How to know if my device is affected by it?
A: Run fastboot command :
Code:
fastboot getvar anti
The displayed output : 3 shall mean you're fine while 4 shall mean you're in the Anti-Rollback squad.
Q6: I'm in the Anti-Rollback squad what now?
A: Don't worry you can still flash custom recovery and roam around custom ROMs but avoid flashing any firmware or any MIUI ROM which is older than what you're using now otherwise you'll brick your device.
Q7: Which MIUI builds include "Anti-Rollback"?
A: All the MIUI builds which are released after Stable MIUI V9.5.17.0 and Beta MIUI V8.7.5 include "Anti-Rollback". And yes the Chinese versions are affected as well.
Q8: Do MIUI Stable V9.5.17.0 and Beta V8.7.5 have "Anti-Rollback" enabled?
A: NO. If you're on either of these builds you are safe to downgrade and use any older version.
Q9: How to flash custom recovery and custom ROMs on "Anti-Rollback" enabled devices?
A: On "Anti-Rollback" enabled ROMs you cann't flash custom recovery permanently. You'll have to boot into recovery first by running fastboot command:
Code:
fastboot boot xyz.img
(where xyz is name of your recovery file). Once you're booted into the custom recovery, copy the recovery image file in the internal storage and flash that recovery from recovery itself. Now you've successfully flashed custom recovery and you're good to go with custom ROMs. WARNING: Avoid flashing any firmware.
Q10: Can I migrate from Stable to Beta and vice-versa?
A: You can install Beta from Stable, make sure you flash latest Beta build same is the case with Stable. If you're on anti-4 firmware, whether its Beta or Stable you can switch to any anti-4 MIUI ROM Beta or Stable but remember you must flash latest version available while switching. (anti-4 means "Anti-Rollback" enabled firmware)
Q11: Can I unlock bootloader and flash custom ROMs on an "Anti-Rollback" enabled device?
A: Yes. Again to flash custom ROMs and recovery refer to Q9.
Q12Can I flash "Anti-Rollback" enabled ROM via TWRP?
AWell, in some cases it did work, just flash lazy flasher zip file after flashing MIUI ROM via TWRP. But while switching to MIUI from AOSP based ROMs on an "Anti-Rollback " enabled device I recommend you to go with fastboot method to avoid chances of brick.
For active discussion join whyred telegram group: https://t.me/redminote5proofficial
Hit thanks if helped.
Saabu said:
Q9: How to flash custom recovery and custom ROMs on "Anti-Rollback" enabled devices?
A: On "Anti-Rollback" enabled ROMs you cann't flash custom recovery permanently. You'll have to boot into recovery first
by running fastboot command:
Code:
fastboot boot xyz.img
(where xyz is name of your recovery file). Once
you're booted into the custom recovery, copy the recovery image file in the internal storage and flash that recovery
from recovery itself. Now you've successfully flashed custom recovery and you're good to go with custom ROMs.
WARNING: Avoid flashing any firmware.
Click to expand...
Click to collapse
Thanks for the above, but I believe that #9 is true. All MIUI roms regardless of version and anti roll back protection willl reflash the default MIUI recovery when you boot the OS. The only way to get it to stay is by flashing a custom ROM after TWRP, or by obtaining root and removing the "/system/bin/install-recovery.sh" file. If you're on anti-rollback you won't even be able to flash the recovery - you'll get an anti-rollback protection error.
This only concerns the "Xiaomi Redmi Note 5"?
For the Fastboot Command : fastboot getvar anti , I have : Anti:1 .. What does means ?
When you says "avoid flashing any firmware or any MIUI ROM which is older than what you're using now." , So Imagine if I have MIUI 10 Official with Android 8.1 and I Would like to flash like Xiaomi.eu or Lineage OS with Android 8.0 , The phone will brick ?
If I want to Flash Mod with TWRP Flashable Zip , the phone will brick or not ?
Thanks for your FAQ !
For me when i type fastboot devices it shows my device number but when i type this command fastboot getvar anti it shows nothing please help and im using Redmi note 5 vince version and miui version is 9.6.2.0 global stable.
kunal bro said:
For me when i type fastboot devices it shows my device number but when i type this command fastboot getvar anti it shows nothing please help and im using Redmi note 5 vince version and miui version is 9.6.2.0 global stable.
Click to expand...
Click to collapse
You answered yourself... It is ONLY for Redmi Note 5 (Pro) aka whyred! You are even in wrong device forum!
One doubt..... I am on AOSP right now. If I flash global beta 8.7.12 in twrp and then flash lazyflasher, will my twrp be removed !! Will I be able to go back to AOSP ?? @Saabu
DEBASISH said:
One doubt..... I am on AOSP right now. If I flash global beta 8.7.12 in twrp and then flash lazyflasher, will my twrp be removed !! Will I be able to go back to AOSP ?? @Saabu
Click to expand...
Click to collapse
After you flash a ROM that has Anti-Rollback enabled, you can still switch to AOSP anytime as I discussed in Q9. And yes, flashing lazy flasher simultaneously after MIUI will keep your TWRP.
Happy flashing
Saabu said:
Q5: How to know if my device is affected by it?
A: Run fastboot command :
Code:
fastboot getvar anti
The displayed output : 3 shall mean you're fine while 4 shall mean you're in the Anti-Rollback squad.
Click to expand...
Click to collapse
Hi, @Saabu,
Many thanks for the clarification.
However to enter the code through the fastboot, it has to be with the equipment turned off in fastboot mode, right?
Best regards,
Jorge
Jorge Moreira said:
Hi, @Saabu,
Many thanks for the clarification.
However to enter the code through the fastboot, it has to be with the equipment turned off in fastboot mode, right?
Best regards,
Jorge
Click to expand...
Click to collapse
Ofc.
Fastboot commands work only in fastboot mode?
Saabu said:
Ofc.
Fastboot commands work only in fastboot mode
Click to expand...
Click to collapse
It was a silly question, I know ...
Just to confirm....
Thanks,
I am a little concern about all this anti rollback matter...
well, the point is i am in xiaomi.eu rom, 8.6.28 (miui 10). I have checked the "anti" variable via the "fastboot getvar anti", and return 3.
Now, I would like to downgrade to miui 9 via twrp, and since I have "the 3 value" I understand that I can downgrade without any trouble, rigth?
However, I have found this https://xiaomi.eu/community/threads/antiroll-back.44975/
Here a guy have tried somehing similar and...briked phone.
What do I do now? Flash? i stay in a rom version that i dont like?
Thanks for your answers
nolohedecidido1 said:
I am a little concern about all this anti rollback matter...
well, the point is i am in xiaomi.eu rom, 8.6.28 (miui 10). I have checked the "anti" variable via the "fastboot getvar anti", and return 3.
Now, I would like to downgrade to miui 9 via twrp, and since I have "the 3 value" I understand that I can downgrade without any trouble, rigth?
However, I have found this https://xiaomi.eu/community/threads/antiroll-back.44975/
Here a guy have tried somehing similar and...briked phone.
What do I do now? Flash? i stay in a rom version that i dont like?
Thanks for your answers
Click to expand...
Click to collapse
You can flash any MIUI 9 with anti 3 via TWRP. Dont flash the ROMs with anti 4 via TWRP. Last MIUI ROMs with anti-3 were: Stable MIUI V9.5.17.0 and Beta MIUI V8.7.5.
Saabu said:
Hi all.
So, as we know with recent MIUI update Xiaomi screwed our whyred. And this gave birth to many questions which is like a struggle for many users to find all those answers. So, I tried to answer all your questions. If you think your question isn't included please feel free to ask.
Q1: What is this "Anti-Rollback" thing?
A: Its a security measure that Google brought with the release of Android Oreo. It makes sure that your data is secure even when phone is stolen or if any attacker tries to downgrade the software and wants to gain control over your data.
Q2: How is this harmful to my device?
A: Well, as a security measure it should never give you a hard-brick. When someone tries to downgrade, it should display a warning and get turned off but there's difference between how things should work and how Xiaomi does. As Google has stated, "Anti-Rollback" should automatically turn off when the user unlocks the bootloader but in case of MIUI even unlocked users are getting hard-bricks. Hopefully the developers of MIUI should push an update soon and if they don't, our beloved devs will find a way for sure
Q4: So, what now? Will Xiaomi solve this issue?
A: We do not know. But our beloved developers in the XDA-Forum will find a way for sure
Q5: How to know if my device is affected by it?
A: Run fastboot command : The displayed output : 3 shall mean you're fine while 4 shall mean you're in the Anti-Rollback squad.
Q6: I'm in the Anti-Rollback squad what now?
A: Don't worry you can still flash custom recovery and roam around custom ROMs but avoid flashing any firmware or any MIUI ROM which is older than what you're using now. Remember you cann't flash MIUI Stable over Beta otherwise you'll brick your device.
Q7: Which MIUI builds include "Anti-Rollback"?
A: All the MIUI builds which are released after Stable MIUI V9.5.17.0 and Beta MIUI V8.7.5 include "Anti-Rollback". And yes the Chinese versions are affected as well.
Q8: Do MIUI Stable V9.5.17.0 and Beta V8.7.5 have "Anti-Rollback" enabled?
A: NO. If you're on either of these builds you are safe to downgrade and use any older version.
Q9: How to flash custom recovery and custom ROMs on "Anti-Rollback" enabled devices?
A: On "Anti-Rollback" enabled ROMs you cann't flash custom recovery permanently. You'll have to boot into recovery first by running fastboot command: (where xyz is name of your recovery file). Once you're booted into the custom recovery, copy the recovery image file in the internal storage and flash that recovery from recovery itself. Now you've successfully flashed custom recovery and you're good to go with custom ROMs. WARNING: Avoid flashing any firmware.
Q10: Can I migrate from Stable to Beta and vice-versa?
A: You can install Beta from Stable and make sure you flash latest Beta build but installing Stable over Beta isn't possible yet.
Q11: Can I unlock bootloader and flash custom ROMs on an "Anti-Rollback" enabled device?
A: Yes. Again to flash custom ROMs and recovery refer to Q9.
For active discussion join whyred telegram group: https://t.me/redminote5proofficial
Hit thanks if helped.
Click to expand...
Click to collapse
Deleted
i have a question for my understanding. for example i want to install LOS 15.1. Where do i know if LOS uses ARB 3 or 4 ?
TM147 said:
i have a question for my understanding. for example i want to install LOS 15.1. Where do i know if LOS uses ARB 3 or 4 ?
Click to expand...
Click to collapse
When updating to LOS/AOSP based rom, its installer does not include firmware update. So you gonna have the same anti value after flashing it. Btw, check their official thread, they have clear installation instructions now.
what about my warranty if my phone is bricked?
will they do for free of cost
as my phone got bricked today 3 months old phone
If I delete firmware update folder in any rom ( with ARB4 ,ARB4,any older ROM) and flashing that will brick my phone ?
hargitomi said:
When updating to LOS/AOSP based rom, its installer does not include firmware update. So you gonna have the same anti value after flashing it. Btw, check their official thread, they have clear installation instructions now.
Click to expand...
Click to collapse
Thanks. but now i have some more question. Sorry this ARB Think is
Which official thread did you mean ? I found the official installation guide but i can't read anythink about devices with ARB4
... sorry can't post the link to LOS
Another thing that makes me thoughtful is Q2 in the beginning. "As Google has stated, "Anti-Rollback" should automatically turn off when the user unlocks the bootloader but in case of MIUI even unlocked users are getting hard-bricks."
So unlocking the bootloader is essential for flashing a custom recovery. What can/ must i do if i have a ARB4 Device to install TWRP ? On the TWRP side i can't read anything about this problem
.. sory can't post the link to TWRP
So please help me because i don't want to brick my device
iam on 8.7.5 with unlocked bootloader can i flash custom roms like los and rr rom by using twrp
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
RockstarLover said:
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
Click to expand...
Click to collapse
OK, so I am not sure what exists in the OnePlus forums but lets start with:
1. You are aware there are two sets of partitions on this device correct? If not, please read here: https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
2. What are you running now?
3. You need to update your TWRP to blu_spark but I am not sure if the latest (v9.91) works with Oreo... I know that v9.86 works with Oreo for sure. Read and download from here: https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
4. Get the appropriate OOS zip file from this thread: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Specifically OOS 5.1.11: https://www.androidfilehost.com/?fid=1322778262903980680
The basic steps should be like this (all assumes you have and unlocked bootloader):
1. If you are running OOS 5.1.11, reboot to fastboot
2. Boot blu_spark TWRP.img - fastboot boot twrp.xxx.img
3. Flash OOS 5.1.11
4. Flash blu_spark TWRP.zip to get it on both slots
5. Reboot to RECOVERY
6. Flash OOS 5.1.11
7. Flash blu_spark TWRP.zip
8. Factory reset in TWRP
9. Flash Havoc Oreo zip
10. Flash blu_spark TWRP.zip
11. Reboot to RECOVERY
12. Flash GApps
13. Flash Magisk (optional if you want root)
14. Flash no-verity if you plan to run unencrypted. (optional)
My advice is to READ READ READ before going forward with anything. The A/B partition layout is far from the traditional days of a single partition layout with a recovery partition. Educate yourself or risk bricking your device and opening up a whole different set of problems.
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
RockstarLover said:
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
Click to expand...
Click to collapse
It does sound like you READ READ READ before proceeding... My steps were not intended as a step-by-step guide, which is why I said the steps "should look like this". You didn't answer any of my questions, so I have no idea where you started from or where things went wrong to get you into this state...
Can you get into fastboot mode?
If so, try this thread first: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
The fastboot restore method will ONLY work if you know which OOS you were running before you got bricked...
If you can't restore from fastboot images, try this thread: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
I cannot stress enough, you MUST read all the steps and understand what you are doing before doing anything. If you have any questions, ASK before proceeding... Good luck.
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
1. You are aware there are two sets of partitions on this device correct?
Click to expand...
Click to collapse
I know it
2. What are you running now?
Click to expand...
Click to collapse
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
RockstarLover said:
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
I know it
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
Click to expand...
Click to collapse
You are back up and running, good work! Congrats!
When you say the device is 'locked', you mean the bootloader is locked again? It shows 'Locked' in fastboot? Obviously you need to unlock the bootloader again before proceeding if this is the case...
And 'Yes', it is normal for 'bootloader version' and 'baseband' to be blank. It shows the same on my device anyway, and I can flash custom ROMs with no issues, and everything works.
At this point, you should be able to follow the steps in my post, making sure you first unlock the bootloader (which will wipe all of your data). You might want to format data (not just wipe as well) to start fresh. I would also confirm that there are no issues running Havoc Oreo with encryption (I'd recommend asking the question in the Havoc OnePlus telegram channel, https://t.me/havoconeplus). After people ask to "Why are you running Oreo?!?!", you just might get an answer... I dumped being encrypted after about a week of having this device because it made moving between ROMs more difficult.
In step 14, I mention the no-verity file to remove force encryption. I have attached it to this post. Again, you may want to have /data encrypted (necessity, personal preference etc.) so this isn't mandatory but I found it made flashing different ROM's much easier (personal preference really).
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
RockstarLover said:
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
Click to expand...
Click to collapse
Looks like they removed Oreo builds, you might be out of luck. Check out XenonHD 8.1 thread if your set on running Oreo, was updated to Dec. Security patch.
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
RockstarLover said:
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
Click to expand...
Click to collapse
Did you flash OOS 5.1.11 on both slots? I know you said you were on OOS 5.1.5 when you did the MSM tool restore.
Unsure if the Havoc build you are running requires a certain FW. Usually the devs update the blobs on customer ROMs based on the latest releases of OOS. In this case, 5.1.11 was the last version of OOS Oreo.
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
RockstarLover said:
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
Click to expand...
Click to collapse
I'd recommend just going to Pie. I haven't run Havoc in over a month but the latest AEX is solid and battery life is excellent. The Pie ROMs have stabilized significantly in the last month.
i just flashed the latest havoc rom now. Really really thanks brother. ur a good boy.
have a good year