Develop Bugs

[GUIDE][WIFI ONLY]Android 3.1 on Xoom WiFi, Root, via ClockworkMod Recovery

This guide may be obsolesced shortly, but it's still good reading for the curious. See [UPDATE][HC3.1] Wifi and 3G! Completely Flashable! No Fastboot Needed! No Data Loss. (thanks, bigrushdog)
WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.
COMPATIBILITY NOTE: I have personally tested this procedure ONLY ON THE US XOOM WIFI MZ604. If other devices (i.e., Euro Xoom WiFi) implement the same Android 3.1 update file, then this procedure *should* work; some users have reported success with UK and Canadian models (see this post for more info). Know, however, that you proceed at your own risk.
AWESOMENESS NOTE: Instead of copying files which you're going to adb push to the platform-tools directory every time, why not just add the directory to your PATH environment variable ("How to update your PATH")? That way, you can run adb from any directory you want.
3G GUINEA PIGS: I've edited the 3G version of the updater_script in the same way as the WiFi, but I don't have a 3G Xoom with which to test. IF YOU ARE FLASHING AND TROUBLESHOOTING SUPASTAH, please try the attached updater-script_UNTESTED_Xoom3G_Android3.1_Root_v03.zip(Updated!) with the MZ600 HRI66 stock images and Xoom 3G 3.1 Update ZIP. If it works, I'll update the guide to cover both devices. Please PM me your feedback, since a post might be easily buried in this thread. Thanks!
[size=+1]SUMMARY[/size]
Here's a run-down on the current procedure:
Updates the Xoom WiFi to Android 3.1 using ClockworkMod Recovery (update.zip)
Resolves issue in updater-script: get_prop ro.product.device wingray
Sets correct permission on su to enable functioning root
Flashes the recovery (version 03 persists CWM Recovery), boot (kernel), and system partitions to stock (required at this time)
Stock kernel means no SD Card in Honeycomb (still available in recovery), no overclocking until devs release 3.1 compatible kernels
Updates bootloader to include Recovery in the boot menu
Leaves user data intact
Outstanding Issues:
(FIXED in updater_script version 03) Recovery partition gets overwritten to stock on reboot: Edit updater-script to leave recovery partition intact
Too many steps: Include the edited updater-script, su, Superuser.apk in the update.zip
Now, without further ado...
[size=+1]ASSUMPTIONS[/size]
You've downloaded the Xoom WiFi Android 3.1 update from Google (thanks, pof)
You've downloaded and unzipped the stock Xoom WiFi MZ604 HWI69 images from Motorola
You've downloaded su and Superuser.apk (see WiFi Xoom Root Zip link at Xoom WiFi (MZ604) Root!!)
You've flashed a boot.img that enables adb remount (Xoom WiFi (MZ604) Root!!, custom kernels, etc.)
You've flashed ClockworkMod Recovery (thanks, bigrushdog, koush, et al)
You've installed a physical SDCard in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
You've configured the Android SDK on your PC, with adb functioning properly
You've downloaded fastboot and have it functioning properly (usually alongside adb in platform-tools)
You've installed an archive program that lets you edit the contents of an existing ZIP file (7-Zip, WinRAR, etc.)
You've downloaded and unzipped the edited updater_script file attached to this post
[size=+1]PROCEDURE[/size]
Prepare the Android 3.1 Update file
The update file as-provided is not ready for use in ClockworkMod Recovery. This fixes it. I could just include a link to a prepared update.zip file, but this is safer than trusting some dude with less than 20 posts on XDA. I'll upload one when I hit 25.
Rename the Android 3.1 Update file to update.zip
Open the zip file in an archive program for editing
Navigate to the following directory: META-INF/com/google/android
Delete the following file: updater-script
Copy the updater-script file from the ZIP file attached to this post to META-INF/com/google/android
Flash stock system.img
Prior to performing the actual update, the update script checks a number of files (including bcm4329.ko, which is usually built with the kernel) in /system. If any file doesn't match what's expected, the update halts. Flashing the stock system.img ensures a smooth update.
Code:
adb reboot bootloader
fastboot flash system system.img
fastboot reboot
Reconfigure superuser
After flashing stock, we no longer have superuser/root access on our Xoom. By pushing and configuring these files, we restore our root capability without interfering with the pre-update checks. (thanks, Berzerker for catching missing symlink)
Code:
adb remount
adb push su /system/bin/
adb shell chown root.shell /system/bin/su
adb shell chmod 4755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
adb push Superuser.apk /system/app/
adb shell chmod 644 /system/app/Superuser.apk
Flash stock boot.img
The pre-update checks also include the boot partition. We wait until now to flash the boot partition to stock because we need to perform adb remount earlier in the procedure, which we can't do with the stock boot.img. The actual update flashes this partition with a new kernel that implements the new 3.1 features.
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Perform update
Code:
adb reboot recovery
Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select.
In ClockworkMod Recovery, select "mounts and storage"
Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
On your PC, copy update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
In the "Mounts and Storage Menu" screen, if the option "unmount /sdcard" is present, continue to the next step; if "mount /sdcard" is present, select it then continue
Select "+++++Go Back+++++"
Select "apply update from sdcard"
Select "Yes - Install /sdcard/update.zip"
"Install from sdcard complete." will indicate that the update is completed.
.
Select "reboot system now"
New bootloader will install. The message, "Congratulation! Your bootloader was successfully upgraded" will be immediately followed by an automatic reboot.
Enjoy your rooted Xoom WiFi, running on Android 3.1!
[size=+1]POST-UPDATE NOTES[/size]
Custom kernels: As of 0730 11 May 2011, there are no kernels/boot.img that are compatible with the Android 3.1 update, though the devs are undoubtedly on it. Do not flash a custom kernel after performing this procedure unless you know that it's compatible with the 3.1 update.
Recovery: updater_script v03 no longer flashes stock recovery. If you ran a previous version of the update, please see this post by Berzerker on getting ClockworkMod Recovery to persist (thanks, Berzerker)

NICE! Will be trying this out shortly.

trying it now.... will give feedback

Can someone confirm the filesize and md5 of the update zip file? (the actual update.zip, not the updater-script)

Do I need to be using the stock kernal before I start?

good post.... cant wait to try this when I get home.

here's the official update link for wifi xoom:
http://android.clients.google.com/p...signed-tervigon-HMJ37-from-HWI69.e379f0b9.zip

just one quick question why is it US only ? don't you think it should work on wifi only euro too ?

pof said:
here's the official update link for wifi xoom:
http://android.clients.google.com/p...signed-tervigon-HMJ37-from-HWI69.e379f0b9.zip
Click to expand...
Click to collapse
Yes, but the official update won't flash in ClockwordMod Recovery unless it is modified, like the one in the OP of this thread. Posting the official version on this thread just adds to the confusion.

publicanimal said:
Yes, but the official update won't flash in ClockwordMod Recovery unless it is modified, like the one in the OP of this thread. Posting the official version on this thread just adds to the confusion.
Click to expand...
Click to collapse
All he posted in the OP was a modified script, you still need to get the update.zip from Google.
The Google server is much much faster than the 3rd party download sites too.

le_pere_noel said:
just one quick question why is it US only ? don't you think it should work on wifi only euro too ?
Click to expand...
Click to collapse
Only because I don't have a test device. I'll update the post.

Just got done with this procedure, and it works perfectly.
I'm rooted on 3.1 on my WiFi Xoom.
Thanks OP!

stachre said:
[*]Flash stock system.img
Code:
adb reboot bootloader
fastboot flash system.img
fastboot reboot
Click to expand...
Click to collapse
fastboot flash system system.img

tony710 said:
All he posted in the OP was a modified script, you still need to get the update.zip from Google.
The Google server is much much faster than the 3rd party download sites too.
Click to expand...
Click to collapse
Ah my bad, I only saw the .zip at the end of the filename

Anyone know if this works in Canada?

tony710 said:
Just got done with this procedure, and it works perfectly.
I'm rooted on 3.1 on my WiFi Xoom.
Thanks OP!
Click to expand...
Click to collapse
So, maybe a stupid question, but did you have Tiamat kernel installed? Just wondering if that makes a difference. Thanks!
-edit- plus, will this wipe all userdata??

were do we find a boot.img that enables adb remount?

Thanks man! Can't wait to give this a try when I get home!
One general question though, what program do you guys use to edit the update.zip?
Thanks in advance for the help fellas!
Peace
Dan

mbroeders said:
So, maybe a stupid question, but did you have Tiamat kernel installed? Just wondering if that makes a difference. Thanks!
-edit- plus, will this wipe all userdata??
Click to expand...
Click to collapse
Yeah, I had Tiamat installed and all my userdata stayed.
I'm currently trying to see if I can flash the latest Tiamet back to see what happens.

dowenprs said:
Thanks man! Can't wait to give this a try when I get home!
One general question though, what program do you guys use to edit the update.zip?
Thanks in advance for the help fellas!
Peace
Dan
Click to expand...
Click to collapse
I used 7z to edit the zip file

cant update to 7.1.1

Hello, i am running full stock and trying to update to 7.1.1 via sideload, i have had no issues in the past when i done my monthly update.
i get the following error:
C:\Users\*\AppData\Local\Android\Sdk\platform-tools>adb sideload bullhead-ota-nmf26f-27b4075c.zip
loading: 'bullhead-ota-nmf26f-27b4075c.zip'
* cannot read 'bullhead-ota-nmf26f-27b4075c.zip' *
i can open the zip file with winrar and have no issues extracting it, i have downloaded android studio and am using the latest adb and running cmd as admin, also the sha-256 match

Are you certain the zip file is in "C:\Users\*\AppData\Local\Android\Sdk\platform-tools>" ??
Make sure the zip is in the same folder as adb.exe

kirkgbr said:
Are you certain the zip file is in "C:\Users\*\AppData\Local\Android\Sdk\platform-tools>" ??
Make sure the zip is in the same folder as adb.exe
Click to expand...
Click to collapse
I have also problem updating to 7.1.1 final version from DP2. It says updating aborted. Can't update over newer build. But I'm in Developer Preview 2 of 7.1.1, how is this possible. Finally in order to update to android 7.1.1 official I had to opt out of beta to get Android 7.0 and then I sideloaded the update with success!Now I have the latest update of our beloved Nougat with December 5 security patch!

Billys20 said:
I have also problem updating to 7.1.1 final version from DP2. It says updating aborted. Can't update over newer build. But I'm in Developer Preview 2 of 7.1.1, how is this possible. Finally in order to update to android 7.1.1 official I had to opt out of beta to get Android 7.0 and then I sideloaded the update with success!Now I have the latest update of our beloved Nougat with December 5 security patch!
Click to expand...
Click to collapse
The final release version appears to have been made before the developer preview 2 build. Developer Preview 1 was very stable in my opinion and they went ahead and made a final version based on developer preview 1 soon after releasing it. You can just flash the factory image to get to the final version

yep its in there
https://img42.com/VcsxN

kenpachizero said:
Hello, i am running full stock and trying to update to 7.1.1 via sideload, i have had no issues in the past when i done my monthly update.
i get the following error:
C:\Users\*\AppData\Local\Android\Sdk\platform-tools>adb sideload bullhead-ota-nmf26f-27b4075c.zip
loading: 'bullhead-ota-nmf26f-27b4075c.zip'
* cannot read 'bullhead-ota-nmf26f-27b4075c.zip' *
i can open the zip file with winrar and have no issues extracting it, i have downloaded android studio and am using the latest adb and running cmd as admin, also the sha-256 match
Click to expand...
Click to collapse
I am having exactly the same thing. ADB reboot to recovery detects and reboots the phone. But from ADB SIDELOAD, same thing.
Already tried USB troubleshooting (having only the phone connected), and multiple downloads of the OTA file that matches the SHA-256. Tried everything from the net, doesn't fix/work.
anyone encountered and fixed this issue?
I got Windows 10 Pro x64, tried both USB 2.0 and USB3.0 sockets, and still the same.

run command prompt as admin?

Primal1031 said:
run command prompt as admin?
Click to expand...
Click to collapse
yes, i did run as admin in my first post

Same issue here: I firstly tried with Nexus Root Toolkit but with no fortune (some missing stock files), then tried with ADB Sideload. Always KO with error * cannot read 'bullhead-ota-nmf26f-27b4075c.zip' *

Same Issue here on 5x. Just spent a few hours trying to figure this one out to no avail.
Windows 10 64bit
Latest ADB Drivers
multiple downloads of OTA update file
matching SHA-256 checksum
cmd as admin
plenty of space on device
same setup as every other sideload I've done
Always getting "cannot read 'bullhead-ota-nmf26f-27b4075c.zip"
And if you try to put the update file on the SDCard and issue the "Apply update from SD Card" you get:
"E:unknown volume for path [/sdcard]
-- Couldn't mount /sdcard
Installation aborted."
Trying to find any solution before having to flash a full factory image.

Billys20 said:
I have also problem updating to 7.1.1 final version from DP2. It says updating aborted. Can't update over newer build. But I'm in Developer Preview 2 of 7.1.1, how is this possible. Finally in order to update to android 7.1.1 official I had to opt out of beta to get Android 7.0 and then I sideloaded the update with success!Now I have the latest update of our beloved Nougat with December 5 security patch!
Click to expand...
Click to collapse
hi guys just info, you can't install nmf26f ota file just because its older than npf26f, so in this case you downgrade the rom via sideload and you can't do that. I know because I doing same thing like you do before

adytprayoga said:
hi guys just info, you can't install nmf26f ota file just because its older than npf26f, so in this case you downgrade the rom via sideload and you can't do that. I know because I doing same thing like you do before
Click to expand...
Click to collapse
I can't speak for everyone else, but I was trying to go from n5d91l TO nmf26f which should work just fine going from the 7.0.0 to 7.1.1 version.

USB debugging enabled in developer settings?
I just side loaded ota from 7.0 to 7.1.1 in under 20 minutes. Following directions only on ota Google developers instructions. https://developers.google.com/android/ota
Using minimal adb and fastboot only, no SDK, did it for you. http://forum.xda-developers.com/showthread.php?t=2317790

scariola said:
USB debugging enabled in developer settings?
I just side loaded ota from 7.0 to 7.1.1 in under 20 minutes. Following directions only on ota Google developers instructions. https://developers.google.com/android/ota
Using minimal adb and fastboot only, no SDK, did it for you. http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
i have downloaded the one in that thread but no success, same result, i confirm usb debugging via settings and going adb devices before i start

Just out of curiosity, are the successful sideloaders using Linux? I set ADB_TRACE=1 and got a memory allocation message (when I get to my PC, I'll post the message). It seems that the adb that is in the sdk has issues with large OTA files.
EDIT: While I **thought** I tried this, I just tried to install the OTA using an admin mode command prompt, no error message, and I see the update coming over on my phone... I also see FAR too many trace messages in my command prompt window, but that's not all that important... Just have to wait for the update to finish "patching system image unconditionally"...
Sent from my Nexus 5X using Tapatalk

I'm having problems with the update too. I haven't tried adb sideload yet.
I tried only the built-in option. The update is downloaded and verified. After pressing the button for reboot and installation the phone starts into the recovery and then doesn't do anything anymore.
Anyone an idea what might be the problem?
EDIT: Now i tried the method stated in https://developers.google.com/android/ota but all i get is the error message "error:closed". I tried it with adb devices and with adb usb before but nothing works.

found my issue, BitDefender was stopping it, something as simple as antivirus....

Can anyone tell me how to do a manual update without loosing my personal app data?

@flattervieh: save them with TitaniumBackup.

Bootloop after flashing gapps to any 64bit rom

Model Device: XT1676
Yesterday I unlocked the bootloader, the message "ID: bad key" appeared when the phone was started. I ignored this, I flashed the 64bit twrp and here the problems start - I've tried many roms:
- FireHound v4.5,
- AospExtended v5.4,
- BootleggersROM 2.2,
- dotOS 2.1 and 2.2,
On all roms (except for dotOS 2.1) the same problem appears - the system itself works and starts correctly, but when I flash any version of Open Gapps the phone falls into the bootloop, the exception is dotOS 2.1, it works fine, but there are not many functions has dotOS 2.2, interestingly - when I flash dotOS 2.1, gapps, run the phone and then I do flash update to 2.2, everything works fine, but I would like to use another rom, but all have the same problem, does anyone know how I fix it?
And as for "ID: bad key" - I can not even relock the bootloader and unlock again (I read that helps), because the phone has a bootloader with the NPPS25.137-93-8 stock version, which even can not be downloaded anywhere, and the flash attempt of the older stock is canceled due to the older security patch.

The message bad key is normal - you can replace the splash screen if you want
Make sure you have formatted data
Some roms require a certain type of gapps - if it's a 64bit rom make sure you are using 64bit gapps
Check thread 1st post and user comments for any information on this
Some users have reported booting the rom first without gapps then Data wipe only then flash rom & gapps again
You can also try disabling the welcome screen on first launch
In twrp, mount /system, go to advanced, terminal and type
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop

TheFixItMan said:
The message bad key is normal - you can replace the splash screen if you want
Make sure you have formatted data
Some roms require a certain type of gapps - if it's a 64bit rom make sure you are using 64bit gapps
Check thread 1st post and user comments for any information on this
Some users have reported booting the rom first without gapps then Data wipe only then flash rom & gapps again
You can also try disabling the welcome screen on first launch
In twrp, mount /system, go to advanced, terminal and type
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
Click to expand...
Click to collapse
Booting the rom first without gapps then Data wipe only then flash rom & gapps again didn't help, I use the latest arm64 gapps but I still have a bootloop on almost all the latest roms, disabling setupwizard didn't work - The only roms that work for me are those from before April.
EDIT
I downloaded the build.prop through ADB, edited it over the computer and sent it back to the phone - it helped, thanks for the advice.
Thread to close.

Wanted_X2 said:
Booting the rom first without gapps then Data wipe only then flash rom & gapps again didn't help, I use the latest arm64 gapps but I still have a bootloop on almost all the latest roms, disabling setupwizard didn't work - The only roms that work for me are those from before April.
EDIT
I downloaded the build.prop through ADB, edited it over the computer and sent it back to the phone - it helped, thanks for the advice.
Thread to close.
Click to expand...
Click to collapse
how did you get build.prop by adb? in twrp? what commands? thanks

durc12 said:
how did you get build.prop by adb? in twrp? what commands? thanks
Click to expand...
Click to collapse
Yes, I used ADB, commands:
to download build.prop - adb pull /system/build.prop
after edit, to push file into device:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
There is full tutorial: www.ultimatetech.org/edit-build-prop-file-android-withwithout-root/

Wanted_X2 said:
Yes, I used ADB, commands:
to download build.prop - adb pull /system/build.prop
after edit, to push file into device:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
There is full tutorial: www.ultimatetech.org/edit-build-prop-file-android-withwithout-root/
Click to expand...
Click to collapse
I install the rom, then the gapps, but it says to me that no build.prop is ther with the pull command, I don´t know why
EDIT: finally I did it, but it was neccesary to mount /system in twrp, to check the box in "mount". Thaks for all

[RECOVERY][Android 10/11][Stock/SODP][XZ2/C/P/3] TWRP 3.4.0-0 [UNofficial]

The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
FAQ:
Just wiping your phone in TWRP lead into an encrypted & not readable userdata in the stock system.
You need to open advanced wiping and check the entries data and internal storage.
Of course clear the dalvik, too.
If you backed up system and/or vendor partitions and you want to restore them, make sure that TWRP setting "Use rm -rf instead of formatting" is set!.
If after the usage of NewFlasher or the OTA Updater or something else, which installs stock firmware parts you get stuck into the TWRP or SONY Logo, you need again to disable the verification with the vbmeta.img file and its parameters in fastboot.
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Weird problems not easily to reproduce by other users require that you make sure, that you
Use the newest platform tools (adb & fastboot)
Downloaded the newest firmware via Xperifirm from XDA and installed the newest firmware via Newflasher from XDA
Newflasher from XDA
Xperifirm from XDA
Removing the stock bloat apps via titanium backup may result in a boot loop. Use a file explorer to remove them, disable them or try to use my unfinished bloat removal script at github.
Your phone reboots into recovery, instead of system? Maybe it crashed too often due to a wrong installation or whatever?
In TWRP:
Code:
cat /dev/block/bootdevice/by-name/misc
shows you the reason.
TWRP -> [WIPE] -> [Advanced Wipe] -> Tick only the misc -> [Swipe to Wipe]
Known Bugs:
The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
You can also "fastboot reboot bootloader" in the blue fastboot mode.
This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
If "fastboot boot twrp.img" results into a blackscreen and reboot of the phone, take a look if you modified the DTBO partition.
It requires a special TWRP for every modified kernel/dtbo until I find some way to unify the twrp kernel with the DTBO (if the bootloader supports it).
Bugtracker:
TWRP Bugtracker -> If you think the problem is in TWRP
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs your device name, dmesg, the /tmp/recovery.log and a way to reproduce the issue.
If possible use
Code:
logcat -b all
instead of just a dmesg.
If ADB is not working to provide logs
VOLUP+POWER for 1 Seconds -> Forced crash to create a pstore
Boot the normal system.
Give me the files in
Code:
/sys/fs/pstore/
If the TWRP is stuck at the TWRP logo, the chances are high, that the decryption didn't succeed.
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@dees_troy and his team of volunteers for the TWRP code
@dhacke thank your for providing a download server
Shame on me if I forgot someone after searching through the thread and my PM's!
And many thanks to the few donators!
A telegram group for technical SODP stuff:
https://t.me/xda_tv
XDA:DevDB Information
TWRP, ROM for the Xperia XZ2
Contributors
MartinX3, Sony
Source Code: https://github.com/MartinX3-AndroidDevelopment
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Newest recommended
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 3.4.0-0
Stable Release Date: 2020-06-13
Created 2020-03-29
Last Updated 2020-06-20

Download & Installation
Download:
https://androidfilehost.com/?w=devices&uid=11410963190603893035
https://www.dhsfileserver.de/ftp/martinx3/ Thank you @dhacke for the second download server
Installation:
Update to newest stock firmware before unlocking!!!
Unzip the *.gz files with https://7-zip.org/ or Linux.
Enter fastboot via software, not hardware buttons. See "Known Bugs".
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot boot twrp.img
Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img
Reboot into installed TWRP
Want Root? -> Magisk
(Only if your phone doesn't boot to system anymore) Advanced menu -> "Fix recovery bootloop"
(Optional; Security degradation; Only if you know what you're doing) Switch SELinux to permissive (with my permissive.zip)

News
02.03.2021
Reuploaded the SODP TWRP with a workaround for Android 11 compatibility.
Click to expand...
Click to collapse
15.06.2020
reuploaded the stock twrp for the xz2 premium with a completely fixed touch.
Click to expand...
Click to collapse
14.06.2020
reuploaded the stock twrp with a later touch kernel modules initialization.
Hopefully fixing the randomly happening not working touch.
Click to expand...
Click to collapse
13.06.2020
thanks to the fixes in 3.4.0 we got now a twrp with the following enhancements for stock and sodp:
- this twrp will work with future 10.0 roms, you don't need a new build matching the security patch level of your rom.
- you can install this twrp again with the buildin ramdisk patcher. Please follow the installation instructions.
Click to expand...
Click to collapse
11.06.2020
switch to twrp 3.4.0
sodp twrp 2020-06 security patch level
stock twrp 2020-05 security patch level for firmware 52.1.a.2.1
now both twrp should work without a rom being installed (empty system/vendor/oem partitions) and still be able to decrypt your userdata.
Also the stock twrp touch should now always work instead of playing russian roulette.
Click to expand...
Click to collapse
11.05.2020
reuploaded sodp twrp for 2020-05 security patch level.
It didn't boot with the newest aosp.
Click to expand...
Click to collapse
07.05.2020
sodp twrp for 2020-05 security patch level.
Click to expand...
Click to collapse
14.04.2020
removed stock twrp for firmware 52.1.a.0.672 until sony releases the kernel sources of the new security patch level.
Otherwise the keymaster won't decrypt the userdata for twrp and twrp gets stuck on the twrp logo.
Click to expand...
Click to collapse
13.04.2020
stock twrp for firmware 52.1.a.0.672
sodp twrp for 2020-04 security patch level
hopefully fixed the touch problems of the stock twrp
fixed the forced read only partition mountings of system, vendor, odm
Click to expand...
Click to collapse
31.03.2020
stock twrp for firmware 52.1.a.0.618
Click to expand...
Click to collapse
30.03.2020
sodp twrp for 2020-03 security patch level
installing in ramdisk (to make it persistent) is impossible at the moment, because it is a 9.0 twrp which makes its ramdisk incompatible to the rom.
Of course monthly twrp releases in sync with the current patch level need to be released or i would need to remove the userdata decryption completely.
The stock twrp will follow, after it became ready.
Click to expand...
Click to collapse

30.03.2020
SODP TWRP for 2020-03 security patch level
Installing in Ramdisk (to make it persistent) is impossible at the moment, because it is a 9.0 TWRP which makes its ramdisk incompatible to the ROM.
Of course monthly TWRP releases in sync with the current patch level need to be released or I would need to remove the userdata decryption completely.
The Stock TWRP will follow, after it became ready.
Click to expand...
Click to collapse
PS: AndroidFileHost blocked me for doing too many actions at the same time.
Maybe I can upload it there tomorrow.
Done

can't wait for possibility to install in ramdisk
but now there is a working recovery :highfive:

31.03.2020
Stock TWRP for firmware 52.1.A.0.618
Click to expand...
Click to collapse

xz3 twrp
MartinX3 said:
31.03.2020
Click to expand...
Click to collapse
xz3 twrp won't boot, sodp version is good but there's no install on ramdisk?

hafiidh said:
xz3 twrp won't boot, sodp version is good but there's no install on ramdisk?
Click to expand...
Click to collapse
You mean SODP TWRP works, but not the stock TWRP on your XZ3?
You are stuck on sony logo?
Or on TWRP logo?
I need a bugreport with "logcat -b all" via adb.
Install ramdisk doesn't work at the moment, because it is a TWRP 9.0 hack, since TWRP 10.0 is ready.
But I wrote it in the news
Edit:
Reworked the thread a bit for more clarification

First! Wonderful job!
---EDIT------
Everything works fine! So nice!

@MartinX3 Great job as always bro! :good:
I ran it on my XZ2 (stock 52.1.A.0.618).
Phone has booted to the twrp screen (till the unlock pattern), but the touch is not working (log).
I didn't start from scratch (fresh install), for the record.
Tia!

serajr said:
@MartinX3 Great job as always bro! :good:
I ran it on my XZ2 (stock 52.1.A.0.618).
Phone has booted to the twrp screen (till the unlock pattern), but the touch is not working (log).
I didn't start from scratch (fresh install), for the record.
Tia!
Click to expand...
Click to collapse
Thank you
Are you sure the touch doesn't work?
I tested this release on the same firmware on my XZ2 in stock.
This confuses me now.
You booted stock .618 before and you tried to deactivate & activate the display?
Here it worked right out of the box.
And if it happens again, could you execute "start preptouch"
And if that not works, could you execute "/sbin/preptouch.sh"?

Sjll said:
First! Wonderful job!
---EDIT------
Everything works fine! So nice!
Click to expand...
Click to collapse
Thank you

MartinX3 said:
[...] Are you sure the touch doesn't work?
And if it happens again, could you execute "start preptouch"
And if that not works, could you execute "/sbin/preptouch.sh"?
Click to expand...
Click to collapse
I am. I have tried at least three times so far. Tried turning off and on the screen, but the slide to unlock didn't work, too.
"start preptouch", no response, no working touch
"/sbin/preptouch.sh"...
Code:
insmod: failed to load /sbin/clearpad_rmi_dev.ko: File exists
insmod: failed to load /sbin/clearpad_core.ko: File exists
insmod: failed to load /sbin/clearpad_i2c.ko: File exists
akari:/sbin # ls -l
Tia again

serajr said:
I am. I have tried at least three times so far. Tried turning off and on the screen, but the slide to unlock didn't work, too.
"start preptouch", no response, no working touch
"/sbin/preptouch.sh"...
Code:
insmod: failed to load /sbin/clearpad_rmi_dev.ko: File exists
insmod: failed to load /sbin/clearpad_core.ko: File exists
insmod: failed to load /sbin/clearpad_i2c.ko: File exists
akari:/sbin # ls -l
Tia again
Click to expand...
Click to collapse
And the service menu of android should also say that you use the clearpad driver.
And I assume the 9.0 stock twrp did always touch fine?
The script say that the kernel modules for the touch driver got loaded and I assume the sys path in the script file got executed too, after loading the .ko files.
And you have a normal European firmware?
That's now a mystery for me why it works for me and others, but not in your phone
Especially if you have the clearpad touch hardware

MartinX3 said:
And the service menu of android should also say that you use the clearpad driver.
And I assume the 9.0 stock twrp did always touch fine?
The script say that the kernel modules for the touch driver got loaded and I assume the sys path in the script file got executed too, after loading the .ko files.
And you have a normal European firmware?
That's now a mystery for me why it works for me and others, but not in your phone
Especially if you have the clearpad touch hardware
Click to expand...
Click to collapse
I got the touch working after copying the three .ko libs to the ramdisk /sbin folder, and a small editing (below) in the permissive.sh (also removed "$touch_id" == "3" from preptouch.sh).
Code:
setenforce 0
insmod /sbin/clearpad_rmi_dev.ko
insmod /sbin/clearpad_core.ko
insmod /sbin/clearpad_i2c.ko
echo 1 > /sys/devices/virtual/input/clearpad/post_probe_start
I know this is an awful workaround, but maybe this give you some hint (or sets you more confusing yet )
I'm with the sony stock customized_br fw, as always!

serajr said:
I got the touch working after copying the three .ko libs to the ramdisk /sbin folder, and a small editing (below) in the permissive.sh (also removed "$touch_id" == "3" from preptouch.sh).
Code:
setenforce 0
insmod /sbin/clearpad_rmi_dev.ko
insmod /sbin/clearpad_core.ko
insmod /sbin/clearpad_i2c.ko
echo 1 > /sys/devices/virtual/input/clearpad/post_probe_start
I know this is an awful workaround, but maybe this give you some hint (or sets you more confusing yet )
I'm with the sony stock customized_br fw, as always!
Click to expand...
Click to collapse
Ah you have a XZ2C, not a XZ2?
Because the removed ID 3 is for the XZ2 with clearpad touch.
But the script did already copy the .ko files into your /sbin before and executed the same code, you did now manually.
And according to your logs the setenforce 0 was already executed earlier.
So you just did the same the script did.
Well, yes you confuse me more
Could you try to just execute "echo 1 > /sys/devices/virtual/input/clearpad/post_probe_start" if the touch doesn't work again?
I wonder if the initialization is too early on your device.
Then I could try to delay the preptouch service to a later stage of the device boot.

MartinX3 said:
Ah you have a XZ2C, not a XZ2?
Because the removed ID 3 is for the XZ2 with clearpad touch.
But the script did already copy the .ko files into your /sbin before and executed the same code, you did now manually.
And according to your logs the setenforce 0 was already executed earlier.
So you just did the same the script did.
Well, yes you confuse me more
Could you try to just execute "echo 1 > /sys/devices/virtual/input/clearpad/post_probe_start" if the touch doesn't work again?
I wonder if the initialization is too early on your device.
Then I could try to delay the preptouch service to a later stage of the device boot.
Click to expand...
Click to collapse
I have a regular XZ2 (H8216), and its touch_id is 3 (customized_br fw), so I removed the Id 3.
"Could you try to just execute..." I've already tried that, with no success.
"Then I could try to delay the preptouch..." Cool... As you could notice, it worked here with that awful way I did it, so why not?
:good:

serajr said:
I have a regular XZ2 (H8216), and its touch_id is 3 (customized_br fw), so I removed the Id 3.
"Could you try to just execute..." I've already tried that, with no success.
"Then I could try to delay the preptouch..." Cool... As you could notice, it worked here with that awful way I did it, so why not?
:good:
Click to expand...
Click to collapse
But you tried it also yourself later.
You executed the script again without success at a later stage.
And adding it to the permissive.sh is like executing the script, just earlier.
I assume `cat /sys/devices/dsi_panel_driver/panel_id` gives you the "3" as result?

MartinX3 said:
But you tried it also yourself later.
You executed the script again without success at a later stage.
And adding it to the permissive.sh is like executing the script, just earlier.
I assume `cat /sys/devices/dsi_panel_driver/panel_id` gives you the "3" as result?
Click to expand...
Click to collapse
I ran the scripts/codes manually in the trwp root shell (with the no working touch screen).
Yep, running the script earlier (permissive.sh) did the trick (*.ko files in the ramdisk).
And 3 is the output of the panel_id (that's why I removed the 3 from the preptouch.sh).
Edit: I've noticed this...
The permissions of the libs copied from vendor to sbin (preptouch), as you could see here
Code:
-rw------- 1 root root 1070630 1972-01-22 17:46 clearpad_core.ko
-rw------- 1 root root 251702 1972-01-22 17:46 clearpad_i2c.ko
-rw------- 1 root root 296934 1972-01-22 17:46 clearpad_rmi_dev.ko
Patched twrp
Code:
-rwxrwxrwx 1 root root 1070902 2020-04-02 21:48 clearpad_core.ko
-rwxrwxrwx 1 root root 251830 2020-04-02 21:48 clearpad_i2c.ko
-rwxrwxrwx 1 root root 297054 2020-04-02 21:48 clearpad_rmi_dev.ko
Edit 2: chmod on copied files did the trick (preptouch.sh) - but sometimes still not working (need to boot twice, three times...):
Code:
#XZ2 "3" XZ2C "4" Clearpad
if [[ "$touch_id" == "3" ]] || [[ "$touch_id" == "4" ]]; then
cp /v/lib/modules/clearpad_rmi_dev.ko /sbin/
cp /v/lib/modules/clearpad_core.ko /sbin/
cp /v/lib/modules/clearpad_i2c.ko /sbin/
[B]chmod 777 /sbin/clearpad_rmi_dev.ko
chmod 777 /sbin/clearpad_core.ko
chmod 777 /sbin/clearpad_i2c.ko[/B]
insmod /sbin/clearpad_rmi_dev.ko
insmod /sbin/clearpad_core.ko
insmod /sbin/clearpad_i2c.ko
echo 1 > /sys/devices/virtual/input/clearpad/post_probe_start
fi
Maybe you find out a more elegant way to handle with that!
Edit 3:
I also got it permanently installed on kernel (combo keys does work, too), it's a bit tricky I gotta say, but it works.
You know, twrp's ramdisk.cpio kernel hack (old install procedure).

Hi Martin,
just wanted to let you know that your latest version for Sony stock (0.618 fw) does also not work for me (touch does not respond). Even 'fastboot reboot bootloader' before 'fastboot boot twrp-xz2.img' doesn't change anything.
Device:
Xperia XZ2 (H8216) running Android 10 stock (52.1.A.0.618)
Customized CH
Clearpad Touch version: 3

MICRO-G LineageOS 17.1 - Xiaomi A2 Lite - Development Only

Hello,
Its me reujea0/packmaan7144/hukad,
I have been asked by many to build a microG version of lineageOS. I do not plan to run this build, as I prefer gapps, so all the testing/features/fixes will depend on you and your logs. This build should behave exactly the same as my other (standart) los build. This thread is for developement only, meaning that it will be used until I feel that the rom is stable enough and make a propper thread for it. Of course i am not accountable if this blows up your device.
Here is the link to the first version: https://github.com/a-huk/otaserver/...ge-17.1-20200917-UNOFFICIAL-daisy_micro-g.zip
Second version with actual microG: https://github.com/a-huk/otaserver/...ge-17.1-20201012-UNOFFICIAL-daisy_migro-g.zip
Always latest version: https://github.com/a-huk/otaserver/releases/download/09/lineage-17.1-20201124-UNOFFICIAL-daisy_micro-g.zip
Here are the sources:
Device: https://github.com/a-huk/device_xiaomi_daisy
Kernel: https://github.com/a-huk/kernel_xiaomi_daisy
Vendor: https://github.com/a-huk/vendor_daisy

Not quite microG LineageOS, just signature spoofing enabled.

celrau said:
Not quite microG LineageOS, just signature spoofing enabled.
Click to expand...
Click to collapse
OK my bad, I did not fully understand how to bake in micro-g. I'll make sure it is present in the next build/OTA

reujea0 said:
OK my bad, I did not fully understand how to bake in micro-g. I'll make sure it is present in the next build/OTA
Click to expand...
Click to collapse
I think the easiest would be to integrate the minimal or minimalAP configuration from these guys. It works really good for me

New version and OTA is out, hopefully this is fully working with proper microG and what you have been asking for

reujea0 said:
New version and OTA is out, hopefully this is fully working with proper microG and what you have been asking for
Click to expand...
Click to collapse
Hey, I just flashed it and Phonesky was not properly initialized for sig spoofing, I achieved that by this command:
Code:
pm grant --user 0 com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
And thanks for adding microG.

Ok, so normally the november ota is out, let me know if it all works and if you have the right security patch

reujea0 said:
Ok, so normally the november ota is out, let me know if it all works and if you have the right security patch
Click to expand...
Click to collapse
All is good with the new ota.

Out of interest, what are the exact differences between this rom and the other version? Like what parts of microG are installed, in addition to the signature spoofing?

julianfairfax said:
Out of interest, what are the exact differences between this rom and the other version? Like what parts of microG are installed, in addition to the signature spoofing?
Click to expand...
Click to collapse
If my memory serves me right :
GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend com.google.android.maps.jar FDroid FDroidPrivilegedExtension

reujea0 said:
If my memory serves me right :
GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend com.google.android.maps.jar FDroid FDroidPrivilegedExtension
Click to expand...
Click to collapse
Does this mean Google Maps is installed by default or is it some kind of system component required to use it, that would be otherwise uninstallable as a user app? It seems to be this: https://github.com/microg/android_frameworks_mapsv1?

The ROM is working great and I feel better without Google (well, their closed source apps, still need to connect to their servers ofc). Thanks for developing this!

I've tried installing the latest version of this rom on my Xiaomi Mi A2 Lite. Besides following the standard LineageOS instructions, I've also installed TWRP (just in case). After running "adb sideload" I got this error:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch)
Updater process ended with ERROR: 1.
Any clue about what should I do?

mirluin said:
I've tried installing the latest version of this rom on my Xiaomi Mi A2 Lite. Besides following the standard LineageOS instructions, I've also installed TWRP (just in case). After running "adb sideload" I got this error:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch)
Updater process ended with ERROR: 1.
Any clue about what should I do?
Click to expand...
Click to collapse
Which TWRP are you using? It is also better to flash directly than to sideload. Try this TWRP https://github.com/LinkBoi00/twrp_d...rc6_2/twrp-3.4.0_9-rc6_2-unofficial-daisy.img

reujea0 said:
Which TWRP are you using? It is also better to flash directly than to sideload. Try this TWRP https://github.com/LinkBoi00/twrp_d...rc6_2/twrp-3.4.0_9-rc6_2-unofficial-daisy.img
Click to expand...
Click to collapse
I tried with twrp-3.5.0_9-dees_troy-daisy.img
I'll try again with your suggested version.
What do you mean by flash directly? Adb pushing the image to the sdcard and install from TWRP?
Sorry for the question but I'm pretty new to flashing and stuff. Thanks.

mirluin said:
I tried with twrp-3.5.0_9-dees_troy-daisy.img
I'll try again with your suggested version.
What do you mean by flash directly? Adb pushing the image to the sdcard and install from TWRP?
Sorry for the question but I'm pretty new to flashing and stuff. Thanks.
Click to expand...
Click to collapse
Deestroy twrp is broken, so use the one linked. You can either adb push it or it should simply show up in This Pc as storage on your computer so just drag it in there. Ans then flash directly from inside twrp and your phon'es or sdcard storage.

reujea0 said:
Deestroy twrp is broken, so use the one linked. You can either adb push it or it should simply show up in This Pc as storage on your computer so just drag it in there. Ans then flash directly from inside twrp and your phon'es or sdcard storage.
Click to expand...
Click to collapse
Tried again with twrp-3.5.0_9-1-daisy-unofficial.img and it failed with a different error:
Zip signature verification failed! Error installing zip file '...
Retrying removing the zip signature verification from TWRP installation lead to flashing... and apparently it worked.
Should I be concerned about the missing signature verification?

mirluin said:
Tried again with twrp-3.5.0_9-1-daisy-unofficial.img and it failed with a different error:
Zip signature verification failed! Error installing zip file '...
Retrying removing the zip signature verification from TWRP installation lead to flashing... and apparently it worked.
Should I be concerned about the missing signature verification?
Click to expand...
Click to collapse
Not at all

reujea0 said:
Not at all
Click to expand...
Click to collapse
Thank you for the support!

These are probably unrelated issues but I'm just wondering if there's anything I can do to fix them: I have dark mode set to turn on/off automatically but most of the time it doesn't actually work, and when I used the regular version of this rom I was able to swipe on the keyboard to type, but it seems that doesn't work on this version?