Correct Twrp recovery for Sgp611 MM - Xperia Z3 Tablet Compact Q&A, Help & Troubleshooti

Hi, what is the correct version of Twrp recovery for 6.0.1 stock, since Nuts dualrecovery is not compatible? Thanks

https://eu.dl.twrp.me/scorpion_windy/

Please Help
So I am a total noob. Never rooted a device before. The only reason I'm doing it is cos my kid wants to do gps spoofing with pokemon go. I have already made a mistake as I have unlocked the bootloader without backing up the DRM keys. Now Im tyring to install twrp. On most tutorials it looks straight forward but on the TWRP official site it says....
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:
I really don't know what any of this means. Ive downloaded the utility but have no idea how to use it.
Oh and I also have a xperia z3 tablet sgp611.

Related

Encryption on custom ROMs?

I was able to enable Android encryption (/user partition) under a stock ROM, but I've tried several ROMs that where encryption fails. Specifically, when enabling encryption on AICP 4.4.4, the system reboots (as usual), then completely forgets that I asked it to get encrypted.
Semi-related, I'm having trouble installing TWRP onto the Xperia Z2. AFAIK it's the only recovery that supports encrypted partitions, and XZDualRecovery bundles a version of TWRP that may be too old to use the KK4.4 encryption.
(After installing TWRP based on directions from the site, booting into recovery via power + volume up buttons just hangs on a black screen.)
My phone is a Sony Xperia Z2 D6503, with unlocked bootloader.
Has anyone gotten this to work?
I have gotten this to work (sort of) with a two-kernel solution.
This post contains a stock kernel that has been modified to include TWRP 2.8.1.0 as its recovery (17.1.2.A.0.314-based, by Desperanto86). In combination with the TWRP image, encrypted partitions can be backed up:
Code:
fastboot flash boot boot.img
fastboot flash recovery openrecovery-twrp-2.8.1.0-sirius.img
If you enable encryption on top of this, the system no longer boots (I used custom ROM cm-11-20141206-NIGHTLY-sirius.zip). Flashing the CM boot.img allows the device to boot, but TWRP is no longer accessible.
It's probably possible to integrate TWRP into CyanogenMod's boot.img, but for now, I'm okay with just re-flashing the kernel at times when I need to back up my device (hopefully I don't burn through the flash memory with all the writes). So the process looks like this:
flash FTF firmware with Flashtool
enable developer options, then enable ADB in settings
install XZDualRecovery for root + recovery
copy custom ROM to /sdcard
boot into recovery, factory reset and install custom ROM
boot custom ROM, enable passcode, enable encryption
And when making backups:
power off phone
flash modded kernel + TWRP
take backup
flash original kernel boot.img from ROM (to restore boot ability)
Update for CM12/Lollipop: AOSP seems to enable hardware encryption for Qualcomm-based platforms, but this is not supported with TWRP (GitHub issue). Since hardware support is needed to decrypt storage, TWRP needs to load proprietary Qualcomm binaries to talk to the hardware (which are undocumented).
It seems like there will be no support for encrypted Lollipop backups, so I'll be sticking with 4.4.4.

[Q] Ways to get new bootloader

As some of You may know, Sony gives as opportunity to use /recovery partition.
My question is if I still need to use EMMA or some update (.270, .283 for Tmo) has this bootloader built in?
I ask, coz I read (maybe its just gossip) the M2 with 18.3.1.C.1.17 got new bootloader (ofc it still needs unlocked bootloader to flash recovery).
Additionally i would like to ask someone who use it, how to flash recovery to this partition.
And what when i flash stock rom. Is it overwritten? Or recovery is always there?
I think recovery isn't flashed unless you flash it, because even flashtool doesn't do it.
Recovery can be flashed through fastboot using "flash recovery xyz.img", where xyz.img is your recovery but you have to compile one yourself as I haven't seen any already compiled.
Sadly, none update has integrated this bootloader update so far, maybe sony will surprise us with the 5.1.1 update and include it so yes, you have to use Emma.
EDIT: You can download AOSP package from freexperia, they have build an AOSP recovery that you can boot into with the new bootloader but the menu is missing, however I can be wrong because I have tried it a month ago, maybe some changes were made

Re-flashing OPX ROM via fastboot

Hi
First a little history...
I recently got an OPX with the intention of installing Sailfish OS on it. So first I need to get CM 12.1 installed. Following the instructions here I flashed TWRP using fastboot, but the version of TWRP provided at the link would not find any system partitions on my device and therefore could not be used to flash any images. Newer versions of TWRP would simply not load.
Eventually, using the stock OPX recovery, I managed to upgrade Oxygen OS to the latest version. I then flashed the latest version of TWRP (3.1.1-1) again and it worked! It found my devices partitions and I could flash ROMs with it. But, it wouldn't flash CM 12.1. Something about a trustzone incompatibility...
So I got the idea to try and downgrade Oxygen OS, which I did via TWRP. But then TWRP stopped working... and here is my problem.
I'm now stuck in a situation where:
- I can access fastboot
- The only versions of TWRP which work (e.g. 3.0.2-0) fail to find my system partitions, and therefore can't be used to flash ROMs
- The stock recovery also seems to fail to find the system partitions (clicking on "install locally" does nothing), so I can't use that to flash ROMs either
So I really need to get a working image on my phone somehow... but how?? Is it possible to do this via fastboot only?
Cheers!
Is your bootloader unlocked? TWRP cannot see system partitions if so.
I unlocked it originally... but since then I have installed a new ROM (Oxygen OS 2.x). Would this overwrite the bootloader? Do I need to unlock again? I think I must be using the old OOS bootloader now...
I think you can see if it's unlocked if you boot into bootloader, connect to pc and write on cmd "fastboot devices".
Whenever you switch between android 5.0 roms and 6.0 and further you have to first use the correct recovery from oneplus, only then you can flash the correct twrp and the adequate roms
My bootloader is unlocked. I cannot flash a new ROM via recovery, because none of the recovery images (stock, TWRP) can see my system partitions (I don't know why). At this stage I would just like to know if there is a way to flash a stock ROM/recovery/bootloader via some other method (fastboot, or a special tool), so I can restore my phone back to factory state. I don't care about losing data. Thanks.
EDIT: Just to clarify, I believe this is my current situation (please correct me if something doesn't make sense):
- OOS has two different bootloaders, 2.x and 3.x.
- The phone originally had OOS 2.x on it. None of the TWRP images I installed recognized my system partitions, so I couldn't flash with TWRP.
- After re-installing the stock recovery (which happened automatically when I booted to the stock ROM), I was able to upgrade to OOS 3.x via stock recovery. Now recent TWRP versions were working (I assume because upgrading to OOS 3.x updated the bootloader too), and were recognizing my system partitions.
- Using a new version of TWRP (3.1.1-1), I re-flashed an older version of OOS 2.x again. I think this was my mistake, because I think this downgraded the bootloader to 2.x again. Now none of the TWRP versions recognize my system partitions, so I cannot flash ROMs.
- I have re-flashed the stock recovery from the OnePlus website, but not even this allows me to flash ROMs. The symptoms look like in TWRP, i.e. that it fails to recognize my system partitions. So I am stuck with no way to flash ROMs, or upgrade the bootloader.

Unofficial TWRP now available

Was searching in preparation of my K30 arriving, and found an unofficial version of TWRP is now available.
https://www.google.com/amp/s/unofficialtwrp.com/unofficial-twrp-3-3-1-xiaomi-redmi-k30/amp/
Note: I've not tried it myself, as I don't have the phone yet.
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
ddaggebi said:
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
Click to expand...
Click to collapse
please give instalation guide also
ddaggebi said:
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
Click to expand...
Click to collapse
Thanks for the info @ddaggebi
I used the K30 TWRP from https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914 to fastboot boot to TWRP and dump stock boot, recovery and misc (using e.g. `dd=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img`). Then I patched the boot.img with Magisk Manager Canary. :good:
Any idea why that TWRP recovery installer .bat overwrites the misc partition? Temp booting the .img directly with fastboot boot seemed to work fine without their patched misc, so I'm sticking with that for now.
Again, be sure to fastboot boot recovery and then dump your ROM's misc first if you plan on flashing the recovery using that batch script, since you might need to flash it back along with the ROM's recovery for OTAs to succeed.
I can understand rooting here but is twrp installed permanently here? I mean to flash any rom do we always need fastboot command to boot twrp or its staying always and working normally??
Hard_Rock83 said:
I can understand rooting here but is twrp installed permanently here? I mean to flash any rom do we always need fastboot command to boot twrp or its staying always and working normally??
Click to expand...
Click to collapse
Yes. But some features are limited for now.
btw I installed eu rom in case stock rom replaces TWRP to stock recovery.
osm0sis said:
I used the K30 TWRP from https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914 to fastboot boot to TWRP and dump stock boot, recovery and misc. Then I patched the boot.img with Magisk Manager Canary. :good:
Any idea why that TWRP recovery installer .bat overwrites the misc partition? Temp booting the .img directly with fastboot boot seemed to work fine without their patched misc, so I'm sticking with that for now.
Also here is the latest Magisk Canary (20308) patched stock boot.img to simplify rooting for those just getting started on this device. Simply fastboot flash boot it..
Click to expand...
Click to collapse
Ok so the question is can we reboot to recovery normally or we need to manually type fastboot command to boot to recovery..
I am still searching for twrp , which can normally appears while rebooting to recovery
LR.Team twrp-3.4.0-0209 will be installed by default when you install Eu rom.
I can reboot into recovery as normal (by pressing "vol up" & "power" button). To install root, I can simply go to "Advanced" -> "Install Root" or by using boot.img method. One thing which I can't do is deleting (or changing file name) to system file to remove some of the unwanted app.
It works very well
https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914

Question How to install TWRP permanently for Redmi Note 10 (sunny)?

I am having a tough time installing TWRP on (sunny) as I am not used to A/B partitioned devices. The stock recovery is replaced every time once I boot back to system. I have been using fastboot to get the custom recovery. It would be helpful if someone could tell how to get it installed permanently as there is no recovery partition in A/B devices. There was no option for Recovery Ramdisk in TWRP.
Thank You
If you change the boot.img, the recovery is automatically changed. There is no other way.
The boot.img includes the recovery. This is the reason.
So is there no way to get recovery without altering the boot?
Once you install the ROM via TWRP, I believe you need to go to Advanced > Install Recovery Ramdisk > flash the TWRP image file from microSD.
I haven't gotten to test this myself since I am still waiting for the bootloader unlock, others can confirm if it is the case or if I said something false.
Alternatively, I think crDroid dev for this phone bundles it with TWRP... actually, I think dev dropped it in latest release.
syntheticdingo said:
Once you install the ROM via TWRP, I believe you need to go to Advanced > Install Recovery Ramdisk > flash the TWRP image file from microSD.
I haven't gotten to test this myself since I am still waiting for the bootloader unlock, others can confirm if it is the case or if I said something false.
Alternatively, I think crDroid dev for this phone bundles it with TWRP... actually, I think dev dropped it in latest release.
Click to expand...
Click to collapse
I am using an unofficial twrp and it is not having Install ramdisk option.
Unofficial Twrp 3.5.1 Sunny
1) Installing boot.img changes the recovery to the one it contains.
2) You can change the recovery by subsequently installing recovery on the ramdisk.
But whenever I flash the boot.img again, the recovery changes again.
Even version 3.5.1 of TWRP includes a ramdisk installation feature. Look for it in "Advanced".
StaryMuz said:
1) Installing boot.img changes the recovery to the one it contains.
2) You can change the recovery by subsequently installing recovery on the ramdisk.
But whenever I flash the boot.img again, the recovery changes again.
Even version 3.5.1 of TWRP includes a ramdisk installation feature. Look for it in "Advanced".
Click to expand...
Click to collapse
As I said before that option isn't available in the Advanced option despite me looking for it.
EDIT: I used a different recovery.img TWRP 3.5.2 for sunny, and it had the option. I am linking it here so you can use it.

Categories

Resources