Develop Bugs

Rooting non-standard Android

Model number: GM_DSTL1
Firmware version: 1.5
Baseband version: 20/05/09,st32,x2a.m1
Kernel version: 2.6.28-svn1368
Build number: CUPCAKE.eng.long.20090720.210535.r1368
Trying to figure out how this could be rooted because I can't seem to use traditional methods like downgrading and 1-click rooting.
If I understand correctly this is possible for me due to CVE-2009-2692
In an effort to try and cover my butt I have backed up all that "adb shell" permission would let me.
Zinx's "Recovery partition flasher for Android" has not been helpful.
Getting my device to use FastBoot seems to be my first step.
Constructive comments?

still no luck
Ruled out the telnetd hack, bummer:
I run telnetd in terminal and it gives me no errors but a port scan doesn't return anything besides port 110(pop3), 25(smtp), and 21(ftp) - none of which have proved useful thus far. Must have been patched with cupcake... or something I'm missing.
Also ran cat /proc/cpuinfo for fun
--------------------------------
Processor : XScale-V3 based processor rev 2 (v5l)
BogoMIPS : 103.58
Features : swp half thumb fastmult edsp iwmmxt
CPU implementer : 0x69
CPU architecture: 5TE
CPU variant : 0x0
CPU part : 0x689
CPU revision : 2
Hardware : yuhua X2_V4 on Marvell (Littleton)
Revision : 0004
Serial : 0000000000000000
-----------------------------------------------------
103.58 is weak sauce... but apparently that is the minimum for the Marvell PXA310 RISC Microprocessor
I wonder if anyone else on this board is bumpin the DSTL1? I may be the lone fish out here

Following this guide to get Fastboot aka Engineering Bootloader
I skipped flashing the radio because I figured it had to do with the OTA stuff which doesn't affect my model...
So I downloaded spl-signed.zip and renamed it to update.zip, placed it on my sdcard in the folder "update" (these instructions are specific to my model). In recovery mode I tried to update it but it FAIL.

update.log from failed update
Starting recovery on Thu Oct 8 01:22:51 2009
framebuffer: fd 4 (240 x 400)
I:text_cols 24 text_rows 22
E:Can't open /cache/recovery/command
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=CUPCAKE
ro.build.display.id=CUPCAKE.eng.long.20090710.190105.r1322
ro.build.version.incremental=eng.long.20090710.190105.r1322
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Fri Jul 10 19:15:42 CST 2009
ro.build.date.utc=1247224542
ro.build.type=user
ro.build.user=long
ro.build.host=long-desktop
ro.build.tags=ota-rel-keys,test-keys
ro.product.model=GM_DSTL1
ro.product.brand=generic
ro.product.name=gm_x2
ro.product.device=x2
ro.product.board=x2a_v4
ro.product.manufacturer=yh
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=
ro.build.product=x2
ro.build.description=gm_x2-user 1.5 CUPCAKE eng.long.20090710.190105.r1322 ota-rel-keys,test-keys
rild.libpath=/system/lib/libyh-ril.so
rild.libargs=-d /dev/ttyp1
persist.gsm.dual.mode.phone=1
persist.gsm.sim.active.phone=GSM1
sms.supports.national.lang=1
wifi.interface=eth0
ro.config.sm_notification_snd=notf_gm_02.ogg
ro.config.sm_notification_snd_2=notf_gm_02.ogg
ro.config.notification_sound=F1_New_SMS.ogg
ro.config.ringtone=GM_01.ogg
ro.config.ringtone_2=GM_01.ogg
ro.config.sync=yes
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=yuhua
ro.revision=4
init.svc.recovery=running
init.svc.adbd=running
init.svc.yuhua-board-init=stopped
ro.kernel.android.qemud=0
ro.radio.use-ppp=no
ro.com.google.locationfeatures=1
RecVer:Fri Jul 10 19:15:42 CST 2009
Recovery tools:
HOME: Sd-card update
CALL: Board test
BACK: Factory reset
POWER: Reboot system
I:Key 102 pressed, alt 0
Search /sdcard/update/*
I:Find file . in /sdcard/update/
I:Find file .. in /sdcard/update/
I:Find file update.log in /sdcard/update/
I:Find file update.zip in /sdcard/update/
Find update.zip, Home to update
I:Update package /sdcard/update/update.zip
Installing /sdcard/update/update.zip
Installation failed.

Another Fastboot attempt
http://android-dls.com/wiki/index.php?title=Engineering_Bootloader
Downloaded update.xxx, renamed it to update.zip, placed it on my sdcard in the folder "update" (these instructions are specific to my model). In recovery mode I tried to update it but it FAIL... again.
From the log files it seems this stock recovery system SUCKS...

Another FAIL
Revisiting http://forum.xda-developers.com/showthread.php?t=532719 from my earlier post (#3). Tried to do the Radio Update... Downloaded ota-radio-2_22_19_26I.zip and renamed it to update.zip... yada yada yada, you know the rest.

Visit "http://www.generalmobile.com/index.asp?action=Android_Phones/DSTL1_support", and you can find how the update system work(it is not a G1). Also take some time to see the install package and hack it.
1. Unzip the package.
unzip Android_20090826_r1502.zip
2. Copy some missed property app(http://www.sendspace.com/file/dii80c get from adp1.5) to /system/app/ after diff it with the ADP image.
3. zip the new package.
zip Android_20090826_r1502_hack.zip -ry system boot.img
4. update package and wait it bootup.

Very cool!
@wineleven
THANKS!
That was very cool! Finally some progress
So I was not too off from that path, I had already downloaded the update from General Mobile and had been inspecting the zip file they were trying to shove in my face as a quick fix to their buggy ROM. I was asking the support some very hard questions, which is probably why it has taken them more than their 48 hours to reply to me. (its been 5 days now)
General Mobile's update is Android_20090826_r1502.zip
containing the following particularly interesting (to me) files:
/system/build.prop
/system/system-update-post-script
/boot.img
/update-validate-script
Attempt 1
Here I tried to zip up their unmodified package with the suggested -ry arguments and hope that stock recovery takes it and runs with it.
FAIL
I reviewed wineleven's suggestions noticed he omitted the file update-validate-script
This was probably my problem
Attempt 2
Here I omitted update-validate-script
SUCCESS!
Attempt 3
Spirits high I go for the gusto:
I downloaded superuser.zip from this forum and embedded it in the location /system/app
Flash SUCCESS, functionality FAIL
I got too excited and put Superuser.apk and su both in the same directory... silly mistake
Attempt 4
This time I put Superuser.apk in /system/app and su in /system/bin
Flash SUCCESS, functionality FAIL
running su in terminal gave me "permission denied" with the following carriage return:
here1here2here3here4$
obviously I'm missing something here... but have made progress and feel more confident about this.
More attempts to come. Suggestions and advice is welcome!
Question to those knowledgeable
Why are certain files in the /system/bin included as "links" and not actual files? save space in zip?
Can boot.img be modified? Replaced with a better (more useful) one?
Any ideas on obtaining root?

Root idea and shortcommings
After reviewing http://android-dls.com/wiki/index.php?title=Magic_Root_Access
I may have bin (lol) too hasty with slapping su in /system/bin
But logic tells me it shouldn't matter... bin or xbin
And I feel like permissions are my real issue because my current su (residing in /system/bin)
command
ls -l /system/bin/su
returns
-rwxr-xr-x root shell 34612 2008-08-01 08:00 su
command
chmod 6755 /system/bin/su
returns
Unable to chmod su: Read-only file system
^--- in hindsight I see that as a DUH, because I can't remount the /system partition as read/write
More questions
I have always understood chmod to use three digits, why are there four digits now?
Also, what is 's' in terms of permission... is that to see? like hidden files?

Main task accomplished!
After reviewing Cyanogen's experimental ROM I can see where and how he sets permission for su
Trying to emulate his method for myself has been plenty of trial and error, but I have finally done it.
system-update-post-script was the key file that set permissions.
One MUST keep the carriage return at the end of the file - I have a neatfreak habit of cleaning them up.
Also, using the su and Superuser.apk in Cyanogen's latest build kept restarting my device, must be because his kernel is newer than mine.
RapidShare is hosting for 90 days Android_20090826_r1502_rooted.zip - NEW BUILD HERE
MD5: F1DE9A270CDDF01ADEE708B6660B7AFA
PM me if not avail.
NOTE:
I am not responsible for your new paper-weight mode...
This has worked fine on my device, but I guarantee nothing for yours...
My device is General Mobile's DSTL1 - details in post #1
What you get:
Root access via su and Superuser.apk - procured from XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060
To use:
Your sdcard must contain "update" folder, this is where you will place the zip file after you have renamed it to "update.zip"
Happy ROOT
------------------------------------------
My next task will be to get Cyanogen's ROM to work on my device... seeing as how Cyanogen codes for the popular HTC models, I am left out - and I don't like being left out.
Side quests will be to play with the boot.img, flash the SPL, and maybe get a nice recovery
Particularly I would love to try out nandroid.
@wineleven THANK YOU for the nudge in the right direction!
Thank you:
Google for the open source Android OS - without the free SDK wouldn't have been possible for me
General Mobile for the nifty device
Remote Exploit for BackTrack3/4 - I did most of my work on this Live CD distro
XDA-Developers Forum for info and resources: superuser files and Cyanogen's ROM for info

congratulation to you.
Some notice:
As this devices is deeply modified based on Android open source and hardware different to G1. So you can not rebuild any system framework APK from open source unless you can get the DSTL1 source code. As i now, one thing we can do is to add some external APK file (API compatible to device, now SDK 1.5) to system. Like the Superuser.apk you do.

crzyruski said:
After reviewing Cyanogen's experimental ROM I can see where and how he sets permission for su
Trying to emulate his method for myself has been plenty of trial and error, but I have finally done it.
system-update-post-script was the key file that set permissions.
One MUST keep the carriage return at the end of the file - I have a neatfreak habit of cleaning them up.
Also, using the su and Superuser.apk in Cyanogen's latest build kept restarting my device, must be because his kernel is newer than mine.
RapidShare is hosting for 90 days Android_20090826_r1502_rooted.zip
MD5: C3C13F6DC75BF6F86E5C9E41D7FB4C59
PM me if not avail.
NOTE:
I am not responsible for your new paper-weight mode...
This has worked fine on my device, but I guarantee nothing for yours...
My device is General Mobile's DSTL1 - details in post #1
What you get:
Root access via su and Superuser.apk - procured from XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060
To use:
Your sdcard must contain "update" folder, this is where you will place the zip file after you have renamed it to "update.zip"
Happy ROOT
------------------------------------------
My next task will be to get Cyanogen's ROM to work on my device... seeing as how Cyanogen codes for the popular HTC models, I am left out - and I don't like being left out.
Side quests will be to play with the boot.img, flash the SPL, and maybe get a nice recovery
Particularly I would love to try out nandroid.
Click to expand...
Click to collapse
Hi crzyruski
I'm a new android and DSTL1 user and this information is cool
it's easy to do for a newbie as I?

What do you mean easy? What would you like to do?
I took General Mobile's only update: http://www.generalmobile.com/index.asp?action=Android_Phones/DSTL1_support and gave it ROOT. If this is all you want to do, I have compiled the package already for you in my post above. If you want to do it manually then read the whole thread to see how I did it.
If you want to use my compiled package, it is easy.
Then again, I don't know if anyone else has tried it. It worked for me.
You are only the second individual to inquire about it, I am not sure if the other fellow had any luck - he hasn't replied to me.
Hope this helps.
Keep in touch!

I only have 3 days with Android, but I think that I want to get root access. The only thing I have to do is a second "update" with your package, isn't it?
I'm going to look for a backup system program first...
Can I have problems to update from General Mobile support web in a future? (i.e Android 2.0)

It does not need to be second. That is your choice. You can use it in any order. This is not a patch so order is no relevant.
My package is basically the original General Mobile update + 2 files.
These two files are su and Superuser.apk - nothing special (except that you will obtain root access on demand)
I currently only utilize root access to run Advanced Task Manager.
And in the future I want to overclock because I feel the DSTL1 is greatly underclocked though it should max out at ~600Mhz.
Good luck with a backup program as I have not found any free versions and NAndroid is ideal but not not yet possible as you have to flash the SPL and I am not aware how to do this for DSTL1 though I am sure it is possible.
Please let me know what you end up using to backup, if you do.
I would like to note that I am not all knowing and if something goes wrong I am sorry, but can't take responsibility.
There is no reason you should not be able to update from my package to another like: original 1.5 or new 1.6 or future 2.0 (whenever it comes out).
Hopefully when those come out I will be able to modify them similarly and make them available.
But you mentioned you will only have the device for 3 days, do you suppose 2.0 will be released within this time?
-crzyruski

crzyruski said:
Please let me know what you end up using to backup, if you do.
But you mentioned you will only have the device for 3 days, do you suppose 2.0 will be released within this time?
-crzyruski
Click to expand...
Click to collapse
I'm going to try with My Backup Pro
And about 2.0 this all I know...
http://www.boygeniusreport.com/2009/10/16/android-2-0-screenshot-walkthrough/

Good luck to you.
I think I may begin working on some more DSTL1 hacks.
Please keep me updated with your progress

I only have to do ALL this process with your zip, isn't it?
How to Install the Product Update:
Create a folder at the top-level of your memory card called 'update' , and copy file '*.zip' into your phone's memory card.
Make sure your phone is off, and press the Home key together with the Power & End key to enter the recovery mode, do the operations following the UI indication:
1- Press the Home key to search the zip file from your memory card, and press the Home key again to update the software.
2- Press the Call key to do board test.
3- Press the Back key to restore the factory settings.
4- Press the Power & End key to reboot your phone after update finishes.
Click to expand...
Click to collapse

Looks correct to me. Tell me how it works out.

crzyruski said:
Looks correct to me. Tell me how it works out.
Click to expand...
Click to collapse
I've done it! and all seems to be ok...
Thank you crzyruski.
I'll be waitng for your future DSTL1 hacks.

Rooting and Installing Chinese 2.2 ROM

Wow... The process rather elaborate so I think maybe someone needs a pointer...
1. Download the files...
Root: http://ifile.it/38fdvi0/SuperOneClickFor2.1.zip
Recovery: http://ifile.it/g8adtem/com.kb7sqi.defy.bootstrap.apk
ROM: http://ifile.it/yfrx7mv/droid22.zip superceded, see below
Boot: http://ifile.it/6ozr825/defy_2.2_boot_only.zip superceded, see below
Gapps: http://ifile.it/p2y3xt9/update (1).zip superceded, see below
3G 850/900/1900/2100 fix: http://forum.xda-developers.com/showthread.php?t=944258
RSD Lite: http://ifile.it/hx7c6gk/( uploadMB.com ) RSD Lite 4.9.zip
USB drivers: 64-bit 4.9 http://ifile.it/bsg731q/Handset_USB_Driver_64_v4.9.0.msi
32-bit 4.9 http://ifile.it/jlexou4/Handset_USB_Driver_32_v4.9.0.msi
Click to expand...
Click to collapse
2. Root the device
Plug in in Portal mode. Activate Usb Debugging. Execute Superoneclick with Adminrights and then click on root, restart your phone.
Click to expand...
Click to collapse
3. Install custom recovery
Fairly straight forward, if you're struck at this you should stop now and enjoy the stock ROM.
Click to expand...
Click to collapse
4. Install ROM
* Extract ROM files to...
/sdcard/clockworkmod/backup/droid2.2/system.img
/sdcard/clockworkmod/backup/droid2.2/nandroid.md5
* Put update (1).zip at sd card root folder
* Reboot into recovery via Recovery System. (make sure usb debugging is disabled)
* Wipe data/factory reset
* Restore from nandroid backup
* Flash gapps
* Reboot into recovery (volume up + power)
* Flash boot_only.sbf via RSD Lite
Click to expand...
Click to collapse
5. Done
Respective threads...
Root: http://forum.xda-developers.com/showthread.php?t=913709
Recovery: http://forum.xda-developers.com/showthread.php?t=944543
ROM: http://forum.xda-developers.com/showthread.php?t=899450
Gapps: http://forum.xda-developers.com/showthread.php?t=896312

BTW, I like the Chinese ROM more because it has a call recorder.
Ooops.. The original gapps didn't work for me, so I grabbed the one from Cyanogen...
Afterwards, you may proceed to remove the crap from the stock ROM... Just use the adb included in the SuperOneClick root utility.
A pointer: http://forum.xda-developers.com/showthread.php?t=856104
After all these the Defy flies compare to stock.
FWIW, the ROM version is Version.0.26.0.ME525.ChinaRetail.en.CN and the radio is EPU93ST2_U_03.09.00

root
i try to root it..
as i need to over copy some file in the system
like fonts.
but it all time say canot as the file is protected.
so the root proccess is for what?
not to unlock the system files to me??

You can root with z4root:
http://forum.xda-developers.com/showthread.php?t=833953
For me it worked.

Could you check please which languages are included in this version?
Thanks

English and Simplified Chinese.

isa.ahmed said:
i try to root it..
as i need to over copy some file in the system
like fonts.
but it all time say canot as the file is protected.
so the root proccess is for what?
not to unlock the system files to me??
Click to expand...
Click to collapse
Once rooted, goto terminal (either on phone or by adb), enter...
Code:
mount -o remount,rw -t yaffs2 /dev/block/mmcblk1p21 /system
Then you can edit the files under /system.
BECAREFUL! IT MAY DAMAGE YOUR PHONE! USE WITH CAUTION!

update: changed gapps. cyanogenmod one cannot enable agps.

oh yeah, i installed new versions of busybox (and super user) from market, otherwise titanium backup won't work 100%.
also added new clockwork recovery (remember disable usb debugging otherwise only blank screen after reboot recovery)
and an app called system app remover from chinese (http://www.yingyonghui.com/soft_detail_1884_0_10.html)
d/l here
http://ifile.it/c97j4pb/com.danesh.system.app.remover.1297658941450.apk

Newer version 1.11: (system.img + boot_only.sbf)
http://ifile.it/63okl95/me525.1.11.7z
Gapps:
Either this...
http://forum.xda-developers.com/showthread.php?p=11624878#post116248780
or
http://forum.xda-developers.com/showthread.php?t=899704
Beware some people have experienced dead LED flash after flashing a Chinese ROM. Please come and vote if you've flashed one...
http://forum.xda-developers.com/showthread.php?t=990326

[TOOL] [v3.2] [09NOV] Ubuntu Touch "system-image" Installer // w/o computers

[TOOL] [v3.2] [09NOV] Ubuntu Touch "system-image" Installer // w/o computers
# All credit goes to Ubuntu and contributors
ut-system-installer
I wanted to install Ubuntu Touch system-image (official, ro, OTA-enabled, for-sale-in-the-future) on my Galaxy Nexus, but there were some limitations and disadvantages to do so. It requires Ubuntu on my computer and completely wipes my device. Compared to cdimage-touch, which one can install easily with his/her phone, system-image is hard for some people to try, so I made a simple recovery-flashable zip with shell scripts to install it without computer and losing data. It downloads and installs system-image on your device(officially supported ones only).
What is does:
The same thing as doing
Code:
phablet-flash ubuntu-system --channel devel --no-backup
but without wiping the device, so
-Download files for installing Ubuntu Touch system-image (half-automatically)
-Install it on your device (supported ones by Canonical)
Supported Devices:
-Galaxy Nexus (maguro, toro, toroplus)
-Nexus 7 (grouper, tilapia)
-Nexus 4 (mako)
-Nexus 10 (manta)
Downloads:
http://d-h.st/users/zittoro/ut
Do not use anything in wip folder.
* This will install a CWM-based recovery from Ubuntu, and your device could brick but will not be compensated. *
How-to:
1. Download the zip.
2. Unzip it in /sdcard/Download/ut
3. Move or copy ut-system-dl(read "Arguments for "ut-system-dl"" in second post for options) to /data. Then run the script with root(su). You can just type these in terminal instead of doing this step manually (You need busybox and su installed)
Code:
su
cp -a /storage/emulated/0/Download/ut/ut-system-dl /data
sh /data/ut-system-dl
4. Zip everything in /sdcard/Download/ut
5. Flash it in recovery and reboot recovery (Just use the default install menu at home if you are using special recoveries like MultiROM)
6. Enjoy Ubuntu Touch
Bug reports: post your /sdcard/Download/ut/ut-system.log, /cache/recovery/last_log, and copy of the error if possible

Changelogs:
Code:
[b]09NOV2013[/b]
v3.2
-Added official UT disclaimer link
-Cleaner code
[b]07NOV2013[/b]
v3.1
-Support for "generic customization" channels
[b]03NOV2013[/b]
v3
-Support for "*-customized" channels
-More consistent and easier way of configuring files names to download
v2.2
-Download the recovery image properly as saucy-named doesn't exist in the path anymore. --Thanks to @pildoc for reporting.
[b]21OCT2013[/b]
v2.1
-Log file support to the installation script; still need recovery log because of "system-image-installer"
-Support for trusty-related channels
-Workaround for delta images when device files are the same
-Dropped support for old-channel device images
-Workaround for non-patched recoveries
-Show the actual device names rather than codenames to avoid confusion
[b]19OCT2013[/b]
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files
[b]18OCT2013[/b]
v1.2
-Fix for script error
-Aborts installation if script fails
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad:(
-Added log file: ut-system.log
[b]16OCT2013[/b]
v1
-Initial
Arguments for "ut-system-dl":
-$1: -auto: default for script, automatically detects the device's codename using the value for "ro.build.product"
-DEVICE_NAME: images for DEVICE_NAME devices
-$2: -full: default for script, full images used for initial installation
-delta: delta images used for updates(OTA)
-$3: -CHANNEL: use CHANNEL channel to download images, default "devel"
-$4: -BUILD_NUMBER: build number of image

I dont get it
Sent from my Nexus 4 using xda app-developers app

gazhead said:
I dont get it
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It basically installs the recommended version of ubuntu touch

Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl

hockeyadc said:
Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl
Click to expand...
Click to collapse
Dang I made a mistake

Zittoro said:
Dang I made a mistake
Click to expand...
Click to collapse
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?

hockeyadc said:
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?
Click to expand...
Click to collapse
Can you get a screenshot for me?

Zittoro said:
Can you get a screenshot for me?
Click to expand...
Click to collapse
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?

hockeyadc said:
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?
Click to expand...
Click to collapse
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.

Zittoro said:
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.
Click to expand...
Click to collapse
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?

hockeyadc said:
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?
Click to expand...
Click to collapse
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery

Zittoro said:
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery
Click to expand...
Click to collapse
Awesome!

hockeyadc said:
Awesome!
Click to expand...
Click to collapse
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?

Zittoro said:
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?
Click to expand...
Click to collapse
I haven't tried yet. I realized how many apps I need and use on a daily basis, so I would rather not install it yet. Just gonna wait it out until Ubuntu is more complete.

Changelogs:
18OCT2013
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad
-Added log file: ut-system.log
v1.2
-Fix for script error
-Aborts installation if script fails

Blur
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..

subaash said:
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..
Click to expand...
Click to collapse
1. Download the zip from the link
2. Unzip it to the specified directory on your phone (you can do this with a file explorer app)
3. Download a terminal app and copy and paste the "code" into it.
4. If you get an error, post your /sdcard/Download/ut-system.log. If you don't, zip everything in the specified folder and flash it in recovery
5. Reboot recovery right after the installation

Changelogs:
19OCT2013
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files

Will this work with kulturom(nexus7) AS secondary ROM?
Wysłane z mojego Nexus 7 przy użyciu Tapatalk

[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

Development [ROM][13][UNOFFICIAL][alioth] PixelExperience for Redmi K40/Poco F3/Mi 11X [AOSP]

Hello,
After a lot of work done by lzgmc, jayanthk and after some tests, I have built an unofficial continuation of PE for alioth.
Motivation:
- I have the device and wanted to have last security patches
- I want to have Netflix, Google Wallet, McDonald app working
- because of lzgmc's and JayanthKandula's hard work, needed changes were reduced to minimum
Changes:
- Updated binaries from the most recent global alioth image
- All updates from PixelExperience, including security updates
- Share the same kernel as munch
Changelog:
05.2023
- small kernel updates
- small performance and ui tweaks
04.2023
- use updated drivers from the most recent version of MIUI Global 14.0.4.0
- use current 4.19 kernel instead of old one
- performance and ui tweaks
Images:
PE - Alioth - Google Drive
drive.google.com
Sources:
https://gitlab.com/lukasz1992-pe/
Instruction:
- you have to flash 05.2023 full image first, if you were on different image
For every next incremental update:
- allow system to boot after flashing
- then reboot to recovery
- flash incremental update
FAQ:
Q: Do you have the device?
A: Yes, I use my ROM on my device
Q: How to report bugs?
A: Write about them here
Q: I do not trust your builds
A: No problem, build image yourself from source or just do not use this rom
Q: What about official support?
A: My ROM is not official (depsite OFFICIAL in name of images). There is already an official maintaner, but has not released images yet.
Q: Why automatic updates are not working?
A: Because alioth is not officially supported, I support it unoficially. Maybe I add updates to my repo.
Q: Why do you publish incremental updates
A: They take less space on my Google Drive and are easier to flash
Q: I want to install 05.2023 (and newer) images directly
A: Flash 04.2023 version first, then install incremental updates one by one (as described in description above)
Q: Incremental update does not work
A: Make sure you are on the correct image, follow the order and allow to boot system after each flash (do not try to flash >1 image without reboot)
Q: Is this a vendor-boot ROM?
A: No
Q: Is there any guarantee?
A: xD

You accidentally used the Question-tag for this thread

Hi, I'm on the 20230420-1753 build but when I try to adb sideload the from-20230420-1753-to-20230516-2127 update I'm getting this error, I'm using the provided recovery image:
Code:
Supported API: 3
Finding update package...
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1.
Installation aborted.
I also tried with OrangeFox Recovery, I didn't get this error there but upon reboot I noticed that my version number didn't change.
Also, thanks a lot for keeping PE on the Poco F3 alive, I briefly tried MIU14 but I found it too bloated for my taste.

Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?
Please also confirm you do not have magisk etc.?

lukasz_m said:
Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?
Please also confirm you do not have magisk etc.?
Click to expand...
Click to collapse
Sure, here they are: https://pastebin.com/M5kvav40 https://pastebin.com/VRkbgbvh
I also don't have magisk or anything like that installed.

[DELETED]

Okay, released a new, fixed update - I tested it, it should work

I flashed the new update and its been working fine, thanks for you work!

I flashed the full image on GDrive linked above - thanks very much, works really well. But I think I'm being a blind and can't see the May update? Where do I find that...

Everything okay with your eys. We have some defects with may update again Currently not repaired yet, will publish it when I am sure everything works.

lukasz_m said:
Everything okay with your eys. We have some defects with may update again Currently not repaired yet, will publish it when I am sure everything works.
Click to expand...
Click to collapse
Ah great, thought I was asking a stupid question
Thanks for all your work - had semi-retired my F3 and just bumped it from 12 to 13, its really fast and smooth.

Update - 2023.05 image was reuploaded

Sorry if this is a noob question. Is it possible to dirty flash to this 2023.05 from the latest official build?
And thx for keeping this device updated, really appreciate what you're doing here.

hi, yes - you can do it

Hey Lukasz,
thanks for this work you are doing for all of us.
I I'm on last OFFICIAL PE build from lzgmc and I'm tying to dirty flash with ADB your ROM.
I receive this error whenever I run the ADB sideload comand but Maybe I did something wrong...can you help me ?
Thanks in advance
My version is:
PixelExperience_alioth-13.0-20230119-0644-OFFICIAL
Enabled ADB.
Now send the package you want to apply to the device with "adb sideload <filename Supported API: 3
Finding update package...
Installing update... Step 1/2
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1. Installation aborted.
@lukasz_m

It happens when update was interrupted. I do not remember exact names, but please do from ADB:
mount /dev/block/by-name/metadata /metadata
rm -rf /metadata/ota*
reboot to recovery and try again

lukasz_m said:
mount /dev/block/by-name/metadata /metadata
rm -rf /metadata/ota*
Click to expand...
Click to collapse
Sry Lukasz but I don't understand how to run these commands.
I'm surely missing somethig, so it's my ingorance.
I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.
I get this so ADB is running properly:
List of devices attached
506a3bf9 device
Than what I have to do ?
thanks in advance for your time.

ciottaciotta said:
Sry Lukasz but I don't understand how to run these commands.
I'm surely missing somethig, so it's my ingorance.
I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.
I get this so ADB is running properly:
List of devices attached
506a3bf9 device
Than what I have to do ?
thanks in advance for your time.
Click to expand...
Click to collapse
First open a shell on your device by entering on your PC: adb shell
Then then you can give shell commands like in the posting above

blonderulez said:
First open a shell on your device by entering on your PC: adb shell
Then then you can give shell commands like in the posting above
Click to expand...
Click to collapse
OK thnaks for the explanation...
After giving "mount /dev/block/by-name/metadata /metadata" command i get:
"mount: bad /etc/fstab: No such file or directory"
When I try to browse it with "cd" and "ls" commands i can browse till /dev/block/by-name/ and I see metadata folder with "ls" than when i go for "cd metadata" i get this "/dev/block/by-name/metadata: Not a directory"

Does this work?
Code:
mkdir /tmp/metadata
mount /dev/block/by-name/metadata /tmp/metadata
rm -rf /tmp/metadata/ota*