Database Develop

[ROM] MM M1D63X ext 4 Rooted + Frankenlenok Kernel

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, thermonuclear war,
* or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if you point
* the finger at me for messing up your device, I will laugh at you.
*/
I've made a very fast rom, without a lot of stupid apk and with ext4 system for modifing /system.
You must say thanks to other people, I'm only a stupid "aggregator"....
But thanks also to @Cameo164, after his experience i've made a more little system.img, changing the partions size.
- Download my rom, unzip
http://www.mediafire.com/file/ke5h46vy86o23tl/DF0.1.zip
- Reboot into fastboot
- Install this Recovery (you'll find also here: http://forum.xda-developers.com/g-watch-r/development/getting-ext4-instead-squashfs-6-0-1-t3341166 )
fastboot flash recovery path/to/twrp-3.0.0.img
- Reboot into recovery and Make a backup of your Rom/data/system with this recovery!!!! It's very important!
- Wipe cache and data via recovery, reboot into bootloader
- Install my boot.img
fastboot flash boot boot.img
- Go to this thred ( http://forum.xda-developers.com/g-watch-r/development/getting-ext4-instead-squashfs-6-0-1-t3341166 ) and follow the steps 4-15 and then come back here
- Then:
fastboot flash system systemimageresized.img
- Reboot recovery and install supersu: Wear-SuperSU-v2.67.zip (you'll find in my zip)
- Restart system and wait..........
- Don't care for the google play error on your smartwatch, if you have
- Enable adb debug under dev options on your watch, you can also enable before paring, pushing the hardware button for about 2 seconds
- Pair with your phone
- Install busybox (you'll find in my zip)
adb install busybox.apk
- Install advanced settings for wear http://forum.xda-developers.com/android/apps-games/advanced-settings-t3341722
adb install com.sssemil.advancedsettings.apk
It's very usefull for change the screensaver brightness and other things
- Install Kernel Auditor http://forum.xda-developers.com/android-wear/development/app-kernel-audiutor-4-wear-t3126122
adb install KernelAudiutor4Wear.apk
For enable/disable cores and other things
- on your smartwatch if you have issue, reboot and clear data to google.play. framework (with advanced settings), reboot again
This rom is without a lot of things (like lg wathfaces, tutorial.apk and other things that i don't remeber, i'm sorry).
I use other watchfaces (with facer, this is mine: https://www.facer.io/watchface/hLzCJbTR3Z?draft=true )
Don't ask for add apks, or other things, thank you!
I suggest disable with advanced settings under apps also Bug report sender com.google...wearable.bugreportsender
Remember:
Don't change kernel or rom because you'll corrupt the new ext4 partition and you'll lose your data.
In any case before make a backup,
So, when you'll change rom/kernel you must install again the right kernel and the right rom.
If you have adb error ($ADB_VENDOR_KEYS is not set; try 'adb kill-server'), from recovery:
On your pc search adbkey.pub
cd user/.android
adb push adbkey.pub /data/misc/adb/adb_keys
You must say thanks to:
For stock Image thanks to @intersectRaven and also @vt0r http://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
For This great Kernel thanks to @dirtyhank http://forum.xda-developers.com/g-watch-r/development/kernel-frankenlenok-t3342054 (look at the last page)
windroid toolkit http://forum.xda-developers.com/showthread.php?t=2499926
@Chainfire
@suleymanovemil8
@Xmaster24
@Grarak
@dirtyhank
@Cameo164

Changelog
I've uploaded my things.

Hi, thanks for your work, but for me restoring your system in twrp fails. It show's me an "ERROR: 255" close to the end. I re-downloaded the backup files, so that I can be sure that the files aren't damaged, but still no luck. I'm using the twrp.img you provided and did it like you described.
And btw. When I'm right, it should be called "adb push" not "adb pull".

http://forum.xda-developers.com/showthread.php?t=2236620&page=48
Did you format your system, cache and data?
Did you mount system in recovery?
Or try installing before leedroid rom.
Yes... is push! I'm sorry!

dettofatto said:
http://forum.xda-developers.com/showthread.php?t=2236620&page=48
Did you format your system, cache and data?
Or try installing before leedroid rom.
Click to expand...
Click to collapse
Yes I did. But it's not important if I did it, because TWRP does it before restoring anyways.
What difference would it make if install leedroid rom before restoring, when TWRP formats /system before restoring your backup ?

If you read the link that I've posted you'll see that the issue is in some files on your phone (probably).
Leedroid use ext4, mm only f2fs (I don't remember name exactly) on system. So, probably, if you install leedroid rom, you'll format your system partition to ext4.

dettofatto said:
If you read the link that I've posted you'll see that the issue is in some files on your phone (probably).
Leedroid use ext4, mm only f2fs (I don't remember name exactly) on system. So, probably, if you install leedroid rom, you'll format your system partition to ext4.
Click to expand...
Click to collapse
To have ext4 I don't need to install a non-mm rom like leedroid's. I can just format /system to ext4 in TWRP.
Yes I have read it. The file that causes problems is "/system/usr/icu/icudt55l.dat". I removed it from the backup file and pushed the new file to the watch. And now the restoring works. But I ended up with a bootloop (tried with SuperSu flashed & without SuperSu). I don't know if it's because I removed the file or if it has any other reason.
Thanks for trying to help me.

Did you wait about 5 mins? Because the first time is very long!
Try also with several reboot!
Which boot animation you see?
After I'll see that file!!
But I don't understand... in your log which error is it?
Did you correct permission? In any case you can't remove I file from backup and restore.
Because if you format system and data you don't have any files, restoring stops for an error rewriting your files?
I've restored full m1d63x stock and then I've checked my backup and steps and I didn't find any stop...

dettofatto said:
Did you wait about 5 mins? Because the first time is very long!
Try also with several reboot!
Which boot animation you see?
After I'll see that file!!
But I don't understand... in your log which error is it?
Did you correct permission? In any case you can't remove I file from backup and restore.
Because if you format system and data you don't have any files, restoring stops for an error rewriting your files?
I've restored full m1d63x stock and then I've checked my backup and steps and I didn't find any stop...
Click to expand...
Click to collapse
Yeah I waited 30 minutes, rebooted, waited another 30 minutes and again, again...
The bootanimation I see on watch is in the attachments but because the watch screen is too small there's only "ndroi" instead of "android" visible. And there's that darker font shadow, like a fade-out animation which is going through continuously.
I know that I can't just delete one file, but with that file I can't even restore the backup.
Then I get this error :
Code:
tar_extract_all(): calling th_get_pathname()
tar_extract_all(): calling tar_extract_file(t, "/system//usr/icu/")
item name: '/usr/icu/'
dir
==> extracting: /system//usr/icu/ (mode 40755, directory)
==> setting perms: /system//usr/icu/ (mode 40755, uid 0, gid 0)
Restoring SELinux context u:object_r:system_file:s0 to file /system//usr/icu/
tar_extract_all(): calling th_get_pathname()
tar_extract_all(): calling tar_extract_file(t, "/system//usr/icu/icudt55l.dat")
item name: '/usr/icu/icudt55l.dat'
reg
==> tar_extract_regfile(t=0xb56a9300, realname="/system//usr/icu/icudt55l.dat")
==> extracting: /system//usr/icu/icudt55l.dat (file size 23068784 bytes)
FAILED RESTORE OF FILE i: /system//usr/icu/icudt55l.dat
I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/411KPFX0122123/DF/system.ext4.win'
Fehler während der Wiederherstellung. *should be "Error during restore process" in english
Prozess extractTarFork() endete mit FEHLER: 255 *should be "Prozess extractTarFork() ends with ERROR:255" in english
I:Failed to reset capabilities of /system/bin/run-as binary.
Can you send me the file icudt55l.dat from your running watch and then I can try replacing the file in the backup?

I'll send you icudt55l.da after, when I come back at home. But is very strange...
Anyone has this issue?

icudt55l.dat rw-r-r-
http://www.mediafire.com/file/kjge1s3ox561s5g/icudt55l.dat

dettofatto said:
icudt55l.dat rw-r-r-
http://www.mediafire.com/file/kjge1s3ox561s5g/icudt55l.dat
Click to expand...
Click to collapse
I tried everything I'm able to do : First pasting your new icudt55l.dat file into the backup, just gives me the same error as before. Then I tried restoring the backup without the icudt55l.dat file and push the file with adb push to /system/usr/icu, just gives me a "no space left on device error" and at last I tried to extract the system.ext4.win file on the watch with adb shell instead of twrp, this gives me a "no space left on device" error too, but it seams that I does it anyways. But still stuck on bootanimation. I just can't get this rom to work on my watch :|

After I'll try tu upload another backup...

Ok i've created a system.img_sparsechunk1 flashable via fastboot
Backup everything.
Then download: http://www.mediafire.com/file/d3yo1opb4i7j7at/system.img_sparsechunk1
Reboot into bootloader and:
fastboot erase system
fastboot erase data
fastboot erase cache
fastboot flash system system.img_sparsechunk1
Flash also (I don't know if is necessary for you, but you must use mine boot.img) boot.img http://www.mediafire.com/file/w11byay60nwy5xb/boot.img
fastboot flash boot boot.img
Reboot into recovery and
Wipe data, davlink and cache
Reboot
How I've obtained this system.img_sparsechunk1?
I've extracted my system.img with: dd if=/dev/block/mmcblk0p19 of=/sdcard/system.img
but when i reflashed via fastboot I had an error because was bigger than system partition.
So i've compressed with SparseConverter v1.0.1 http://forum.xda-developers.com/showthread.php?t=2749797
to correct size: sparseconverter /compress system.img .\ 2684354560
and I've obtained the righht system.img
I hope...
In any case i've reflashed on mine and is ok

Thanks a lot for your hard work but my watch still refuses to flash the system -.-
Code:
fastboot.exe flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.288s]
sending sparse 'system' 1/2 (252175 KB)...
OKAY [ 8.280s]
writing 'system' 1/2...
FAILED (remote: size too large)
finished. total time: 8.651s
I have tried it with the latest fastboot version for windows and linux too, but both fail on "size too large". I have even downloaded SparseConverter myself, decompressed the "system.img_sparsechunk1" to "system.img" and then compressed it back into two 100MB and one 61MB sparsechunk files. Still fastboot gives me the "size too large" error.
I can flash the stock "M1D63X_system.img" successfully and it boots too.

I have this
Code:
D:\Hack\Android\LG\extracted>fastboot flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.375s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.551s]
writing 'system'...
OKAY [ 81.913s]
sending sparse 'system' (15336 KB)...
OKAY [ 0.632s]
writing 'system'...
OKAY [ 31.335s]
finished. total time: 122.806s
try with this fastboot http://www.mediafire.com/file/rbz0qqlbb0hty9r/fastboot.exe

dettofatto said:
I have this
Code:
D:\Hack\Android\LG\extracted>fastboot flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.375s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.551s]
writing 'system'...
OKAY [ 81.913s]
sending sparse 'system' (15336 KB)...
OKAY [ 0.632s]
writing 'system'...
OKAY [ 31.335s]
finished. total time: 122.806s
try with this fastboot http://www.mediafire.com/file/rbz0qqlbb0hty9r/fastboot.exe
Click to expand...
Click to collapse
I tried your fastboot version, but it happens the same :
Code:
fastboot.exe flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.300s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.332s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 8.711s

Ok... I don't have any idea for this.
I'm uploading another backup, and another system.img extracted (this is more big, because is uncompressed)

dettofatto said:
Ok... I don't have any idea for this.
I'm uploading another backup, and another system.img extracted (this is more big, because is uncompressed)
Click to expand...
Click to collapse
I don't have any ideas too, I would be very good if anyone else could try your rom and tell if installing and booting works. Then we would know if it's my watch's or my' fault or the rom's fault.

System uncompressed extracted: http://www.mediafire.com/file/g481ae7m3ayrjmb/systemuncompressed.zip
New Backup from System:
http://www.mediafire.com/file/4jc5a31xe2insc6/TWRP.7z
May be is my rom

how to unlock bootloader on bricked mobile?

Hello
my mobile is blocked on the HUAWEI logo
when I press VOL- and POWER I go to FASTBOOT & RESCUE MODE (mobile connected to the PC)
PHONE Locked
FRP Lock
my questions:
* if the bootloader is blocked, it is not possible to flash the BOOT, RECOVERY, SYSTEM, etc. with ADB?
* If the mobile is bricked, it is not possible then to unlock the bootloader?
* why, when I introduce an SD card with a LOAD folder, containing UPDATE.APP the mobile does not perform the firmware installation?
I try I do not know how many firmware and I have not yet managed to unblock.
if someone has had the same problem, I want their help.
otherwise, tell me clearly that it is not possible to unlock and the mobile will end up in the trash ...
it will save me from tearing off the rest of hair on my head

iblda said:
Hello
my mobile is blocked on the HUAWEI logo
when I press VOL- and POWER I go to FASTBOOT & RESCUE MODE (mobile connected to the PC)
PHONE Locked
FRP Lock
my questions:
* if the bootloader is blocked, it is not possible to flash the BOOT, RECOVERY, SYSTEM, etc. with ADB?
* If the mobile is bricked, it is not possible then to unlock the bootloader?
* why, when I introduce an SD card with a LOAD folder, containing UPDATE.APP the mobile does not perform the firmware installation?
I try I do not know how many firmware and I have not yet managed to unblock.
if someone has had the same problem, I want their help.
otherwise, tell me clearly that it is not possible to unlock and the mobile will end up in the trash ...
it will save me from tearing off the rest of hair on my head
Click to expand...
Click to collapse
You are totally bricked.. Must have luck to unbrick this but try with DC-Phoenix unlocker, but It"s paid.. I was have same problem and this one help to me

cxyqqz said:
You are totally bricked.. Must have luck to unbrick this but try with DC-Phoenix unlocker, but It"s paid.. I was have same problem and this one help to me
Click to expand...
Click to collapse
I paid 15 € !!
I have this message on DC phoenix
Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
and the mobile is on fastboot & rescue mode ..
if i try to pass the mobile with flight + & power, it shows me the same screen as the departure:
Error!
Func NO: 10 (boot image)
Error NO: 1 (security verify failed)

this morning another test with DC phoenix
error 10
error 1

iblda said:
this morning another test with DC phoenix
error 10
error 1
Click to expand...
Click to collapse
try : https://www.youtube.com/watch?v=8E43DkUQGMM

cxyqqz said:
try : https://www.youtube.com/watch?v=8E43DkUQGMM
Click to expand...
Click to collapse
dc unlocker does not detect my mobile
only DC phoenix detects it
using the tab "update oeminfo" on DC Phoenix 0.0.0.63, I manage to put the mobile in "PHONE UNLOCKED"
from there I take the opportunity to try to flash BOOT, RECOVERY, SYSTEM with ADB commands.
everything goes smoothly and without error but by restarting the mobile always the same screen with the error in red.
message ADB:
Microsoft Windows [version 10.0.17134.407]
(c) 2018 Microsoft Corporation. Tous droits réservés.
C:\Users\José>cd c:/adb
c:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.021s
c:\adb> fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22688 KB)...
OKAY [ 0.539s]
writing 'boot'...
OKAY [ 0.683s]
finished. total time: 1.227s
c:\adb>astboot flash recovery recovery.img
'astboot' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
c:\adb> fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (36166 KB)...
OKAY [ 0.894s]
writing 'recovery'...
OKAY [ 1.079s]
finished. total time: 1.981s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 18.360s]
writing 'system'...
OKAY [ 8.003s]
sending sparse 'system' (442517 KB)...
OKAY [ 20.055s]
writing 'system'...
OKAY [ 7.675s]
sending sparse 'system' (459746 KB)...
OKAY [ 17.637s]
writing 'system'...
OKAY [ 7.992s]
sending sparse 'system' (444901 KB)...
OKAY [ 18.492s]
writing 'system'...
OKAY [ 7.729s]
sending sparse 'system' (438286 KB)...
OKAY [ 17.082s]
writing 'system'...
OKAY [ 7.612s]
sending sparse 'system' (150611 KB)...
OKAY [ 5.483s]
writing 'system'...
OKAY [ 2.622s]
finished. total time: 138.805s
c:\adb>

I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
EDIT:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
I took the risk and I flashed again with DC Phoenix with the ROM:
* Prague-L31_C432B100_Firmware_Portugal_Switzerland_France_Germany_Spain_Sweden_Austria_Hungary_Greece_Bulgaria_Macedonia_Nonspecific.APP
but the mobile is still NOVA LITE with imei 000000XXXX
the camera does not work, black screen, photo and selfie

iblda said:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
EDIT:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
I took the risk and I flashed again with DC Phoenix with the ROM:
* Prague-L31_C432B100_Firmware_Portugal_Switzerland_France_Germany_Spain_Sweden_Austria_Hungary_Greece_Bulgaria_Macedonia_Nonspecific.APP
but the mobile is still NOVA LITE with imei 000000XXXX
the camera does not work, black screen, photo and selfie
Click to expand...
Click to collapse
Boot into eRecovery (Volume up whilw connected to PC, or when it shows "bootloader unlocked" warning, hold volume up.) Update to lates firmware
also if you get opportunity to update via HiSuite or from phone settings update it. Try as many times as you can to succed. It will aventually flash latest and greatest firmware.
Another method is to use update.app for servicing phones. Downlaod it from here, http://androidhost.ru/K5, place the update.app on external_sdcard inside of a "dload" folder. IN the phone app type *#*#2846579#*#* and select sdcard upgrade. It should work
Wish you luck

aciupapa said:
Another method is to use update.app for servicing phones. Downlaod it from here, http://androidhost.ru/K5, place the update.app on external_sdcard inside of a "dload" folder. IN the phone app type *#*#2846579#*#* and select sdcard upgrade. It should work
Wish you luck
Click to expand...
Click to collapse
this method does not work
the mobile does not exceed 5% and then displays SOFTWARE INSTALL FAILED

Try using HurUpdater. Flash twrp, the download all these files.
1. http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1727/g1647/v146015/f1/full/update.zip dont change name
2.For dualsim
http://update.hicloud.com:8180/TDS/...l/PRA-L31_hw_eu/update_full_PRA-L31_hw_eu.zip (change filename to update_all_hw.zip)
For single sim http://update.hicloud.com:8180/TDS/...l/PRA-L11_hw_eu/update_full_PRA-L11_hw_eu.zip (change filename to update_all_hw.zip)
3. http://update.hicloud.com:8180/TDS/...15/f1/full/public/update_data_full_public.zip (change filename to update_data_public.zip)
4. http://www.mediafire.com/file/ze5z78dq7zu3sxb/HuRUpdater_0.3.zip dont change filename
put all thesw files in one folder on an external sdcard
.
Flash or boot twrp on your phone, and do a "fornat data" commad. wipe all partitions except for the external sd. Flash the HuRupdater_0.3.zip file and confirm flashing by pressing
volume down. After flashing is complete Reboot your phone. ic everything works, it works. If it does not work, do a wipe data and cache in the stock recovery (hurupdater installs stock recovery from the update package automatically)

aciupapa said:
.
Flash or boot twrp on your phone, and do a "fornat data" commad. wipe all partitions except for the external sd.
Flash the HuRupdater_0.3.zip file and confirm flashing by pressing volume down.
After flashing is complete Reboot your phone. ic everything works, it works.
If it does not work, do a wipe data and cache in the stock recovery (hurupdater installs stock recovery from the update package automatically)
Click to expand...
Click to collapse
I flash how?
with what?
where is trwp?
How do I install it?
sorry, I'm starting to be lost ..
this is what I get with the twrp that I downloaded with ADB:
PS C:\Users\José\Documents\MOBILES\huawei\P8\zzzzzz> fastboot flash recovery TWRP-3.2.1-0.img
target reported max download size of 471859200 bytes
sending 'recovery' (8486 KB)...
OKAY [ 0.226s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.256s
WITH MULTI-TOOL FOR HUAWEI:
target reported max download size of 471859200 bytes
sending 'recovery' (23942 KB)...
OKAY [ 0.637s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.653s

my big problem is the installation of a recovery custom.
I can not install it.
the mobile is good in fastboot with bootloader unlocked
but there is no way to flash the recovery:
c: \ adb> fastboot flash recovery twrp-2.8.7.1-p8.img
target reported download size of 471859200 bytes
sending 'recovery' (25880 KB) ...
OKAY [0.676s]
writing 'recovery' ...
FAILED (remote: image verification error)
finished. total time: 0.707s
this is the message I have for all recovery.
EDIT:
and now I have no access unlocking the bootloader with DC phoenix.
Looking for a device in fastboot mode
Device found: 9DCDU17124012020
05/12/2018 23:00:16 Starting to write device in FASTBOOT mode...
Device found: 9DCDU17124012020
IMEI: 862551034926948
Build number: RA-LX1C432B211
Product model: PRA-LX1
Batery state: 4279mv
Not enough credits
he was talking about 72 hours, the time is over.
it's really stealing this dunking thing. the mobile never finally landed, when it was back again it was blocked again.
really **** these huawei as soon as it's bricked.

RIP​
[emoji34][emoji35][emoji34][emoji35][emoji34][emoji35]
​
thanks anyway for your help, even if it did not work ..
Envoyé de mon MHA-L29 en utilisant Tapatalk

iblda said:
I flash how?
with what?
where is trwp?
How do I install it?
sorry, I'm starting to be lost ..
this is what I get with the twrp that I downloaded with ADB:
PS C:\Users\José\Documents\MOBILES\huawei\P8\zzzzzz> fastboot flash recovery TWRP-3.2.1-0.img
target reported max download size of 471859200 bytes
sending 'recovery' (8486 KB)...
OKAY [ 0.226s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.256s
WITH MULTI-TOOL FOR HUAWEI:
target reported max download size of 471859200 bytes
sending 'recovery' (23942 KB)...
OKAY [ 0.637s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.653s
Click to expand...
Click to collapse
------------------------
In your command line you write: fastboot flash recovery TWRP-3.2.1-0.img
just write: fastboot boot TWRP-3.2.1.0.img.. Then TWRP will open.
Now in TWRP you can install TWRP recovery, after reboot you will be able yo use it.
I hope this help you.

Issue with TWRP

Hello,
I have unlock my Mi 9 with MiFlash Unlock
I install lastest vendor image. 9.8.1 and flash latest Pixel Experience Cepheu in TWRP.
I want to restore original MIUI rom.
So, I downloaded fw+vendor_cepheus_xiaomi.eu_multi_9.9.6_v10-10 and miui_CEPHEUSGlobal_V10.2.13.0.PFAMIXM_b529c3de07_9.0.
But I unable to restart into TWRP.
I try :
-adb devices : I see my devices
- fastboot reboot-bootlaoder : my phone reboot into fastboot mode
- fastboot flash recovery twrp.img : target reported max download size of 536870912 bytes
sending 'recovery' (55676 KB)...
OKAY [ 1.210s]
writing 'recovery'...
OKAY [ 0.134s]
But unable to restart into TWRP with Vol + and Power. My phone reboot normally.
Need some help to restore original MIUI ROM Global thanks

[ROM][UNOFFICIAL] LineageOS 17.1 for Xperia 10 II [OTA][SODP]

Lineage 17.1 for the Sony Xperia 10 II
Please note this is currently for the dual-sim model ONLY. When you need a single-sim variant leave a comment, so we can work an that...​
Code:
/*
* Disclaimer - your warranty may be void.
*
* I'm not responsible for bricked devices, dead OTGs 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 me for messing up your device, I will laugh at you.
*/
Features
OTA updates - always delayed for 1 day (to prevent broken rollouts); when you want it immediately, checkout my GitLab pipelines
Increased volume steps to 25
Over-provisioned system image (580MiB), to allow install of OpenGApps and other stuff
Open Source (it is based on SODP, you can view all my patches and ci scripts here or here)
Package signature spoofing (needed by MicroG)
What does not work?
Stock camera app with wide and zoom cameras, you may use Open Camera to circumvent that.
Notification LED blinking - kernel driver bug (see here)
LiveDisplay
You tell me...
Download
There you have multiple options:
To get the complete package (both including the ota and imgparts; only needed for the initial setup) visit...
AndroidFileHost
GitLab (make sure to download the artifacts from the master branch)
To get ONLY the OTA package to update your system later on, visit (or open up the LineageOS Updater) ota.simonmicro.de - please note that only the last recent 14 days are accessible there.
Changelog
2021-02-28
Fixed wifi hotspot.
2020-12-18
Fixed cameras.
2020-11-27
Fixed ADB security.
2020-11-25
Added SELinux support.
2020-11-20
Added OpenGApps support.
2020-11-17
Initial release.
How to install your system
The following guide assumes, you have setup adb and fastboot already (make sure to always use the latest version of the toolkit, otherwise you'll may get problems during flashing) - for that take a look into the internet. Also you should already downloaded the complete package from above!
Unlock the bootloader - a "how to" is here...
Download the oem binaries from here, make sure to use exactly that version!
Boot into the bootloader (hold "Volume up + Insert the USB cable" until led lights blue) and then update the oem partition:
Code:
fastboot flash oem_a [EXTRACTED_OEM_IMAGE_FILE]
fastboot flash oem_b [EXTRACTED_OEM_IMAGE_FILE]
Flash now the Lineage recovery partition as well as the dtbo partition (they are inside the img folder of the complete package):
Code:
fastboot flash recovery [EXTRACTED_RECOVERY_IMAGE_FILE]
fastboot flash dtbo [EXTRACTED_DTBO_IMAGE_FILE]
Disable the verity checks for now, as your new recovery violates the Sony verity profiles of the Stock ROM:
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
Okay, you are now ready to boot the first time into the Lineage recovery, unplug the phone NOW!
To boot into recovery: Hold "Volume down + Power" until it vibrates...
You should now be booted into the recovery. We now clean any old data from Sonys Stock ROM - this is just to make sure you have a really clean install: Choose the "Factory reset" option.
The phone is now clean and ready to accept the new system. You now can either install just the OTA package and be done or flash every .img from the full package manually - the coice is yours. When you plan to flash the images manually, make sure to include boot, system, product, vendor, vbmeta_system, as these are normally part of the OTA update (I extracted the payload.bin to verify this!). For the latter approach you may orient yourself on my flashall.sh. I'll choose the simpler OTA-sideload approach for now.
Select "Apply update -> Apply from ADB" (now make sure the adb server runs as root - may use adb kill-server && sudo adb start-server to fix that) and execute (the OTA zip is inside the ota subdir):
Code:
adb sideload [OTA_SYSTEM_UPDATE_ZIP_FILENAME]
Something went wrong - help!
(Step 7-8) When you now see a device corrupt error
Don't panic!
You messed up the verity disable step from before - try again.
Try to switch the current boot slot (get current fastboot getvar current-slot and set new fastboot --set-active=, you can choose between a and b) and retry disableing verity disable again!
When your device fails to boot too many times (and crashes) the current slot could also get marked as corrupt. To reset that counter you'll need to reflash the boot partition - to see what is going on, try fastboot getvar all and look out for something like a unbootable flag.
(Step 9) When you get Operation not permitted during flashing
This is commonly caused by relocking and then reunlocking the bootloader (yay - buggy firmware). You'll need to relock, restore (and boot) the device with Flashtool using Sonys original ROM and start from fresh.
(Step 10) When you get the kDownloadPayloadPubKeyVerificationError error
Well, that's caused by using an other recovery than the provided one, as I use my own private keys to sign the build the recovery must also know them. Using an other recovery than the one from
the img folder of the complete package will most likely not include them (and when they do - I am in big trouble), and therefore fail. But you are in luck: It seems that the recovery writes
the data to the currently inactive slot and then fails. You could simply switch the system slot like described above!
Want to install Magisk?
Install the Magisk zip like the OTA system update by using adb sideload [MAGISK_FILE_NAME].
Want to install OpenGApps?
Make sure to use the pico-variant, as the system partition is even with over-provisioning really small (as the installer extracts some more stuff on the first boot) - then install the OpenGApps zip like the OTA system update by using adb sideload [OPENGAPPS_FILE_NAME].
Credits
As much I would like, I can't do everything by myself. A huge thank you to...
@MartinX3 for the used local_manifests and his device tree from his LineageOS organization
...the team behind @sonyxperiadev, for their great work (and their kernel sources)!
XDA:DevDB Information
LineageOS 17.1 for pdx201, ROM for the Sony Xperia 10 II
Contributors
Simonmicro, MartinX3
Source Code: https://gitlab.simonmicro.de/android/lineage/lineage-pdx201
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Sony OEM Package
Based On: AOSP
Version Information
Status: Beta

Hey,
as you guys may have already noted, I have stopped the active development phase for this LOS port a while ago. This was caused by me just not having enough time to do everything and additionally maintain a LOS port.
Today I'll upload the last maintenance build to the OTA server and mirrors. Of course I somehow included a little bug, which causes the system to complain about "an internal problem", which seem to be caused by some interaction with the OpenGApps package installer. Now, it is a feature. I'll may post one more update, if I figure this one out.
Nevertheless, I'll shut down the OTA service at 2022-06-01 (see https://status.simonmicro.de) and will then archive all project data. It was a great time to learn many (new/nasty) things about Android and how everything works. I have to say "thank you" to everyone, who supported me and was on board with this project.
See you next time,
simonmicro
-> https://forum.xda-developers.com/t/...r-xperia-10-ii-ota-sodp.4191601/post-86352693 <-

Reserved

First

At last The guide, source code looks great! Will install, check it next

hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.

bamdadkhan said:
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
Click to expand...
Click to collapse
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!

Simonmicro said:
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Click to expand...
Click to collapse
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.

bamdadkhan said:
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
Click to expand...
Click to collapse
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:

Simonmicro said:
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Click to expand...
Click to collapse
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?

Thapsus-cz said:
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Click to expand...
Click to collapse
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).

Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Click to expand...
Click to collapse
See full log for flashing images:
sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
[sudo] пароль для :
Sending 'boot_b' (65536 KB) OKAY [ 2.441s]
Writing 'boot_b' OKAY [ 0.358s]
Finished. Total time: 2.812s
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'product' (432072 KB) OKAY [ 16.440s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vendor' (48084 KB) OKAY [ 1.725s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta_system' (4 KB) OKAY [ 0.005s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.016s
❯ sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
❯ sudo fastboot flash boot boot.img
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash product product.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash super_empty super_empty.img
sudo fastboot flash system system.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash vbmeta_system vbmeta_system.img
sudo fastboot flash vendor vendor.img
Sending 'boot_b' (65536 KB) OKAY [ 2.438s]
Writing 'boot_b' OKAY [ 0.378s]
Finished. Total time: 2.831s
Sending 'dtbo' (8192 KB) OKAY [ 0.302s]
Writing 'dtbo' OKAY [ 0.046s]
Finished. Total time: 0.357s
Sending 'product' (432072 KB) OKAY [ 16.212s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.699s]
Writing 'recovery' OKAY [ 0.557s]
Finished. Total time: 4.265s
Sending 'super_empty' (4 KB) OKAY [ 0.011s]
Writing 'super_empty' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.755s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.021s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.004s]
Finished. Total time: 0.014s
Sending 'vendor' (48084 KB) OKAY [ 1.770s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Click to expand...
Click to collapse

xdauserart said:
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
See full log for flashing images:
Click to expand...
Click to collapse
I had the same problem yesterday with the same results. I struggled with it until morning. Eventually I downloaded the latest version of adb, flashed the stock rom again and started over. It was done in twenty minutes. Try the latest version of adb (I guess version 35 for Windows)

xdauserart said:
Done till the step 9.
Click to expand...
Click to collapse
...
Code:
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
This indicates you tried to use the bootloader (which also has fastboot support) to flash the images. I made sure to write the guide the way that it states you should use the fastbootd service of the recovery. I have the dumb feeling that many more will go your way and fail. Damn it.
Code:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Is fine, as you just erased all data - this also kills the partion so it cant be mounted anymore (that's the errors). This is indeed intentional as the system is now forced to really start fresh!
xdauserart said:
Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds"
Click to expand...
Click to collapse
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).

Two PR to fix back triple cam. But front cam is still broken.
https://github.com/sonyxperiadev/device-sony-seine/pull/29
https://github.com/sonyxperiadev/device-sony-pdx201/pull/15
--------------EDIT-----------------
Switch to CAF powerhal, better performance we have.
https://github.com/sjllls/device-sony-common/commit/de3b2bbbc33130891263d9e81ea2178a0f6783c4
https://github.com/sjllls/device-sony-sepolicy/commit/72059258eb0ff2c854996a05a5a23a8b73b55459
--------------EDIT-----------------
Renmember to let users flash with latest platform-tools, or they could not boot because of logical partition is not resized.
https://developer.android.com/studio/releases/platform-tools

Simonmicro said:
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Click to expand...
Click to collapse
I can confirm that Opengapps pico can now be installed without a bootloop. I'm at work and I don't have adb. I installed them directly as an update from the sd card using recovery. Everything works fine.

Can we get OpenGapps Nano support?
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?

KriiXOne said:
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
Click to expand...
Click to collapse
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!

Simonmicro said:
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Click to expand...
Click to collapse
I'll try tomorrow after the math test that i'm studying for today, and will let ya know ^^'

Simonmicro said:
...
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Click to expand...
Click to collapse
Fixed it Just repeated the steps from the first one and used OTA on step 9. Thanks!

[HELP FİNDİNG TWRP]P SMART FİG-LX1 C432

I am trying to install lineageos for 2 days now twrp keeps giving error would anyone could send me hak86's twrp image I couldnt find on telegram sourceforge and github thanks and it is now stuck on formatting data

there is (now) a functioning link in the "main" topic forum:
see https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3980019/post-84237985
@haky 86 : thnx for that

Bokkahontas said:
there is (now) a functioning link in the "main" topic forum:
see https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3980019/post-84237985
@haky 86 : thnx for that
Click to expand...
Click to collapse
I can remake it, but I need some testers as I don't have the device right now.

@haky 86 : that would be nice, since installing the twrp failed:
$ fastboot flash recovery twrp-3.4.0.0-v1-figo-haky86.img
> Sending 'recovery' (10734 KB) OKAY [ 0.382s]
> Writing 'recovery' FAILED (remote: 'partition length get error')
> fastboot: error: Command failed
device is properly connected, I also doublechecked that bootloader is still unlocked after upgrade from emui 8 to 9.1 (Build is 9.1.0.216(C432E22R1P5))
Can we merge this topic with the following, so there is no parallel discussion in two different topics within the forum?! ;-)
=> https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3980019/post-84237985

switch recovery with recovery_ramdisk

twrp installation succeded with _ramdisk, thanks for the fast reply!
I followed then instructions from official lineage 16 wiki (https://wiki.lineageos.org/devices/figo/install) to install lineageOS 16. Sideload of the actual zip (lineage-16.0-20210115-nightly-figo-signed) in twrp also worked perfectly and I eagerly tipped on "reboot" in twrp hoping to see my new OS booting for the the first time... BUT:
Unfortunately I got stuck at a probably similar point as Capybar (see https://forum.xda-developers.com/t/...k-recovery-and-cant-boot-into-system.4126357/):
Phone stopped being able to enter any recovery at all. The system itself does not boot. The HUawei start screen "Your device has been unlocked and cannot be trustet (...) only tells me (...) "Your device is booting now...", the recovery option never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now").
Then it shows me the Teamwin Logo and at that point freezes.
I cannot acces the phone with adb oder fastboot from host machine..
=> Does anybody knows if there is a possibility to gain acces to recovery?

if stuck on Huawei splash screen, just run factory reset with stock recovery.
to boot into recovery on this crap;
* Keep pressing on vol up + vol down + power.
* Leave vol down button only and keep pressing other 2 buttons once huawei splash screen appears .
* you should able to boot into recovery.

thnx again haky !!!
Nevertheless feeling stupid now (or rather like my mum when I first modified our home-PC autoexec.bat on a 386DX machine in MS DOS to make the PC wish her a good morning on the VGA display) .Back to topic:
I managed to get the the phone start in recovery boot mode asking me
(1) Press Power key to continue
(2) Press Volume Uo key (...) to enter erecovery to restore aour device
(3) Vour device will continue to booot (...)
=> all options result in the same(?) everlasting bootloop
so I succesfully tried fastboot boot mode (error 64 message on screen) and flashed your stock recovery:
$ fastboot devices -l
> XEDDU*********** fastboot usb:2-2
$ fastboot flash recovery_ramdisk 9.1_stock_rec.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.156s]
writing 'recovery_ramdisk'...
OKAY [ 0.269s]
finished. total time: 1.425s
Rebooting phone again leads to bootloop
Edit: Not the very same bootloop since twrp-logo does not appear anymore but phone message is "Your device is booting now ... " and that's it
Got some ideas?
Edit#2 [SOLVED]: put fastboot option -w into command for flashing stock recovery => phone resurrected to stock software (at least)

Thanks for the update!
Im was stuck in the same situation. If you succeed in flashing LineageOS I would love to hear how.
Good luck!

without a phone I can't do a sh*t, try this recovery (3.5.0) and tell me if boots or not.

haky 86 said:
without a phone I can't do a sh*t, try this recovery (3.5.0) and tell me if boots or not.
Click to expand...
Click to collapse
While flashing it I get the following log:
.\fastboot flash recovery_ramdisk .\recovery.img -w
target reported max download size of 471859200 bytes
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
sending 'recovery_ramdisk' (13452 KB)...
OKAY [ 0.376s]
writing 'recovery_ramdisk'...
OKAY [ 0.102s]
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.068s]
finished. total time: 0.546s
I can boot into the recovery. My issue is, when I use wipe -> format data, it formats, says "done", but dosn't give me an option to proceed or go back. So I'm stuck there. After a hard reset I tried to boot into recovery again, but it gets stuck on the teamwin screen.
After flashing it again with the -w option, it works again.
An other issue I have is, when I try to wipe eg. cache, it works, but while trying to update the partition details, it "failed to mount '/data' (Invalid argument)". The same happens, when I install something.

Zet24 said:
While flashing it I get the following log:
.\fastboot flash recovery_ramdisk .\recovery.img -w
target reported max download size of 471859200 bytes
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
sending 'recovery_ramdisk' (13452 KB)...
OKAY [ 0.376s]
writing 'recovery_ramdisk'...
OKAY [ 0.102s]
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.068s]
finished. total time: 0.546s
I can boot into the recovery. My issue is, when I use wipe -> format data, it formats, says "done", but dosn't give me an option to proceed or go back. So I'm stuck there. After a hard reset I tried to boot into recovery again, but it gets stuck on the teamwin screen.
After flashing it again with the -w option, it works again.
An other issue I have is, when I try to wipe eg. cache, it works, but while trying to update the partition details, it "failed to mount '/data' (Invalid argument)". The same happens, when I install something.
[/QUOT]
can you pm me a screenshot?
Click to expand...
Click to collapse

1) @haky 86 : I can also boot into the (3.5.0) recovery
EDIT (fyi): could boot into that recovery, but after installation of stock rom (and likewise in official linage rom) my SIM Card was not detected.
Using "old" stock recovery [9.1_stock_rec.img] and SIM Card works fine. Still that Wifi-Password-Problem...
Zet24 said:
(...)
My issue is, when I use wipe -> format data, it formats, says "done", but dosn't give me an option to proceed or go back. So I'm stuck there. After a hard reset I tried to boot into recovery again, but it gets stuck on the teamwin screen.
(...)
Click to expand...
Click to collapse
2) @Zet24 : this looks rather to a twrp 3.4.0.0 error (?) because previously I got the same which finally ended in stucked teamwin screen and bootloop (see above)
3) @Zet24 : I managed to flash and boot into official figo lineage 16 ROM (lineage-16.0-20210122-nightly-figo-signed) by copying the zip file on sd card and install it directly in twrp (install >> from zip file) -- actually I don't know why sideload method doesn't work..
Unfortunately I couldn't not connect to wifi (see discussion in main topic Forum: https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3975303/post-83896865) even after wiping data and cache with stock recovery, but that is for another time/topic

I posted a tutorial on how to flash Lineage OS on this phone on the other Thread... the Lineage OS thread.

Bokkahontas said:
twrp installation succeded with _ramdisk, thanks for the fast reply!
I followed then instructions from official lineage 16 wiki (https://wiki.lineageos.org/devices/figo/install) to install lineageOS 16. Sideload of the actual zip (lineage-16.0-20210115-nightly-figo-signed) in twrp also worked perfectly and I eagerly tipped on "reboot" in twrp hoping to see my new OS booting for the the first time... BUT:
Unfortunately I got stuck at a probably similar point as Capybar (see https://forum.xda-developers.com/t/...k-recovery-and-cant-boot-into-system.4126357/):
Phone stopped being able to enter any recovery at all. The system itself does not boot. The HUawei start screen "Your device has been unlocked and cannot be trustet (...) only tells me (...) "Your device is booting now...", the recovery option never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now").
Then it shows me the Teamwin Logo and at that point freezes.
I cannot acces the phone with adb oder fastboot from host machine..
=> Does anybody knows if there is a possibility to gain acces to recovery?
Click to expand...
Click to collapse
Hi, How did you manage to unlock bootloader?