So i saw this video of a guy having ubuntu 12.04(pc version) on his phone,he was running the linux server on his phone and at the same time accessing it, using androidVNC . BTW i have a samsung galaxy S 4 (sprint Version ,without knox) Running cyanogenmod 11.0 , android version 4.4.2, the kernel version is [email protected] #1 Thu Jan 9 21:12:16 PST 2014 .
I checked if my phone is loop compatible using, the following in terminal emulator : zcat /proc/config.gz | grep CONFIG_BLK_DEV_LOOP , i found it on a webpage , and i got y, that means it is a loop device, but when i ran CompleteLinuxInstaller i got into the following problem
Checking loop device ... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed : Invalid Argument
ERROR: Unable to mount the loop device
but when i did modprobe loop
it didn't find anything
so if you can help, me i am not a genius, just tell me the simplest way to fix this.
btw i want to install unbuntu 13.10 i have everything downloaded(Terminal emulator, Complete linux installer, AndroidVNC, and the 3.72gb image file)
Thank's in advance,
GGgamer16
Answer
GGgamer16 said:
So i saw this video of a guy having ubuntu 12.04(pc version) on his phone,he was running the linux server on his phone and at the same time accessing it, using androidVNC . BTW i have a samsung galaxy S 4 (sprint Version ,without knox) Running cyanogenmod 11.0 , android version 4.4.2, the kernel version is [email protected] #1 Thu Jan 9 21:12:16 PST 2014 .
I checked if my phone is loop compatible using, the following in terminal emulator : zcat /proc/config.gz | grep CONFIG_BLK_DEV_LOOP , i found it on a webpage , and i got y, that means it is a loop device, but when i ran CompleteLinuxInstaller i got into the following problem
Checking loop device ... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed : Invalid Argument
ERROR: Unable to mount the loop device
but when i did modprobe loop
it didn't find anything
so if you can help, me i am not a genius, just tell me the simplest way to fix this.
btw i want to install unbuntu 13.10 i have everything downloaded(Terminal emulator, Complete linux installer, AndroidVNC, and the 3.72gb image file)
Thank's in advance,
GGgamer16
Click to expand...
Click to collapse
I don't own that phone. And so I cannot say much about it.
But my personal advice is to take backup of everything before you proceed with any changes to your phone.
I found the following links give you an idea:
http://android.stackexchange.com/questions/25396/how-to-find-out-if-my-devices-kernel-has-loop-device-support
http://ubuntuforums.org/showthread.php?t=2189642
http://ubuntuforums.org/showthread.php?t=2193699
Keep searching Google.
Hi All,
Wondering if you could help me please... I keep getting this message from time to time, but not constantly.... My setup is as follows...
Device: Samsung Galaxy S2 (i9100 standard, not P or G model)
OS: BeanStalk 5.0.2 (Android Lollipop 5.0.2) and BeanStalk 4.4.4 (Android KitKat 4.4.4) / dualboot
Kernel: Kernel_Dorimanx-V10.44-_18-28_-_26-01_-KK-b2-SGII-I9100.zip (running Build #2, as build #3 was slower and unstable for me)
PIT: 4GB /Data partition on primary OS (Lollipop). When dualbooting, second rom seems to see/work like stock layout of 2GB /Data
Setup: BeanStalk 5.0.2 is primary rom, BeanStalk 4.4.4 is secondary rom. It's the secondary rom I get the errors on.
Should I be concerned about this error message, will it cause long term data corruption and kill my phone...?? Or is this normal under the S2 and dualbooting...? And just need to run a util once in a while...? Could this lead to eMMC BrickBug issue, like on the N7000... as it has a similar chip.
Many thanks, Lister
ERRORS IN PARTITIONS DETECTED
Sun Feb 1 12:54:48 GMT 2015
Version of binaries used:
Segmentation fault
tune2fs 1.42.8 (20-Jun-2013)
Tunning partitions begins...
Device /mnt/tmp/.secondrom/data.img already have has_journal in features.
Device /mnt/tmp/.secondrom/data.img already have dir_index in features.
Device /mnt/tmp/.secondrom/data.img already have journal_data_writeback in default mount options
Device /mnt/tmp/.secondrom/data.img already have 256 Inode size
Tunning partitions ends.
Checking if device has errors...
DEVICE /mnt/tmp/.secondrom/data.img NEEDS DO BE FIX
Sun Feb 1 12:54:48 GMT 2015
Version of binaries used:
Segmentation fault
tune2fs 1.42.8 (20-Jun-2013)
Checking if device has errors...
DEVICE /mnt/tmp/.secondrom/cache.img NEEDS DO BE FIX
Sun Feb 1 12:54:48 GMT 2015
Version of binaries used:
Segmentation fault
tune2fs 1.42.8 (20-Jun-2013)
Tunning partitions begins...
Device /res/dev/system already have has_journal in features.
Device /res/dev/system already have dir_index in features.
Device /res/dev/system already have journal_data_writeback in default mount options
Device /res/dev/system already have 256 Inode size
Tunning partitions ends.
Checking if device has errors...
DEVICE /res/dev/system NEEDS DO BE FIX
Sun Feb 1 12:54:48 GMT 2015
Version of binaries used:
Segmentation fault
tune2fs 1.42.8 (20-Jun-2013)
Checking if device has errors...
DEVICE /dev/block/mmcblk0p1 NEEDS DO BE FIX
Please use Stweaks "FIX DATA ON or OFF" option in the other tab to avoid annoying issues or use "Check and repair file system on every boot" to always check and repair partitions.
It is advised to perform a nandroid or Titanium Backup similar app before fixing corrupt partitions.
Data of app and/or app may be delected if damaged too much!!!
Click to expand...
Click to collapse
Lister Of Smeg said:
Hi All,
Wondering if you could help me please... I keep getting this message from time to time, but not constantly.... My setup is as follows...
Device: Samsung Galaxy S2 (i9100 standard, not P or G model)
OS: BeanStalk 5.0.2 (Android Lollipop 5.0.2) and BeanStalk 4.4.4 (Android KitKat 4.4.4) / dualboot
Kernel: Kernel_Dorimanx-V10.44-_18-28_-_26-01_-KK-b2-SGII-I9100.zip (running Build #2, as build #3 was slower and unstable for me)
PIT: 4GB /Data partition on primary OS (Lollipop). When dualbooting, second rom seems to see/work like stock layout of 2GB /Data
Setup: BeanStalk 5.0.2 is primary rom, BeanStalk 4.4.4 is secondary rom. It's the secondary rom I get the errors on.
Should I be concerned about this error message, will it cause long term data corruption and kill my phone...?? Or is this normal under the S2 and dualbooting...? And just need to run a util once in a while...? Could this lead to eMMC BrickBug issue, like on the N7000... as it has a similar chip.
Many thanks, Lister
Click to expand...
Click to collapse
If there's no problems now, it should be fine to ignore this issue. You could enable fix data and see if this removes this message (it should) but there's really no need to enable it unless you start to see some issues.
I need help to root my Aligator S5065 Duo phone. It ha Andoid 7.0 and the chipset is Mediatek MT6580.
Here is some info from the phone:
BB Chip : mt6580
MS Board. : ALIGATORS5065
Build Time : Tue Jan 23 15:35:41 CST 2018
Krenel Ver. : 3.18.35+ ([email protected]) (gcc version 4.8 (GCC)) #2 SMP PREEMPT Tue Jan 23 16:11:14 CST 2018
Android Ver. : 7.0
SW Ver. : alps-mp-n0.mp2-V1-droi6580.weg.n
Custom Build Verno. : unknown
IMEI1 : XXX
IMEI2 : XXX
Modem Ver. ALIGATOR_S5065_OS_1.1_2018 0123
Bar code : 010901MT000000000000003891_155648
The idea was:
1) make a full backup using MTK Droid Tool
2) flash TWRP using SP Flash Tool
3) boot TWRP and install Magisk
Problems:
1) MTK Droid Tool v2.5.3. doesn't support this chipset and I didn't found a newer version - so no full backup
I've tried to download a stock ROM or a full backup.
I have found MT6580__ALIGATOR__ALIGATOR_S5065__alps-mp-n0.mp2-V1_droi6580.weg.n__Android_7.0.ispff but it seems to need Infinity CM2 Dongle for flashing, which I don't own.
I have also found ALIGATOR S5065 – 7.0_MT6580_WL581M.LG.ALIG.HB.N.F.S12.B18.0927.V3.02_OS_1.1_20170927.zip which seems to be usable but not exactly the same as I have in my phone, at least it contains a scatter file. With the help of this scatter file I have I've read back my phone but the read imgs are considerably bigger, than the original ones in the zip - that doesn't seem right?
2) I have downloaded TWRP_3.2.3-0_20180803_UNOFFICIAL_MT6580_N.zip which should be a TWRP recovery for my chipset and the same kernel version, so I hoped it could work. But when trying to flash it with SP Flash Tool I get "PMT changed for the ROM" error message. The suggested solution for this error seem to be very risky (formating the phone, atc.), so I didn't dare to try ...
Now I'm stuck and I don't know how to proceed.
Any help would be really appreciated
Some progress:
I got a custom TWRP recovery image from Matty1993 <- thank you very much
I flashed it using adb and fastboot:
adb devices - successfully listed my device
adb reboot bootloader
fastboot flash recovery c:\adb\recovery.img - got this error message: "FAILED (remote: 'not allowedin locked state')"
Locked bootloader, unlocking ...
fastboot flashing unlock
- (bootloader) Start unlock flow
- OKAY [ 18.800s]
- Finished. Total time: 18.816s
Flashing the recovery.img
fastboot flash recovery c:\adb\recovery.img
Sending 'recovery' (10226 KB) OKAY [ 0.359s]
Writing 'recovery' OKAY [ 0.640s]
Finished. Total time: 1.030s
Success
fastboot reboot-bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.016s
fastboot erase cache (I don't know if it was a good idea but it was in the tutorial, I was following)
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.109s]
Finished. Total time: 0.125s
fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.016s
Now when booting the phone complains:
Orange state
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
In 5 second it starts to boot but it stays forever on the "POWERED BY android" logo
I can boot to TWRP recovery (also fastboot), so I did and flashed magisk (because the main goal was to root my phone) and selected to delete cache/dalvik.
I'm not able to switch off the phone, it reboots. I had tu pull the battery (luckily it's removable).
The phone info changed
BB Chip : mt6580
MS Board. : ALIGATORS5065
Build Time : Tue Jan 23 15:35:41 CST 2018
Krenel Ver. : 3.18.35+ ([email protected]) (gcc version 4.8 (GCC)) #2 SMP PREEMPT Tue Jan 23 16:11:14 CST 2018
Android Ver. : 7.0
SW Ver. : alps-mp-n0.mp2-V1-droi6580.weg.n
Custom Build Verno. : unknown
IMEI1 : unknown
IMEI2 : unknown
Modem Ver. ALIGATOR_S5065_OS_1.1_2018 0123
Bar code : unknown
The IMEIs and Bar code are now "uknown".
What did I wrong and what to do, to fix it?
forget MTK Droid Tool it is outdated and does not support scatter for devices > 4 GB. you can use SP Flash Tool for full ROM dump. First thing you should do is backup your nvram partition, hopefully it is not too late...
https://www.getdroidtips.com/backup-restore-imei-nvram-data-mediatek
If you already have backup of stock boot.img:
- copy file to /external_sd/TWRP/BACKUPS folder
- rename it to boot.emmc.win
- create a backup of current boot (just in case)
- restore renamed stock boot.emmc.win from TWRP
regarding boot stuck:
- Format Data and Wipe Cache from TWRP, reboot recovery, wipe again (Wipe -> Format Data -> type yes)
- reboot TWRP, check if /system /data and /cache is mounted/mountable (you should see folders or files inside)
- reboot system and wait 5 minutes, first boot may take a while because the data partition is forced encrypt
- if android is completely booted, check IMEI
Now, if your device is in good condition, reboot recovery and make a full TWRP backup.
Thank you very much for your help.
I did a dump before, using the SP Flash Tool and the scatter from the downloaded ALIGATOR S5065 – 7.0_MT6580_WL581M.LG.ALIG.HB.N.F.S12.B18.0927.V3.0 2_OS_1.1_20170927.zip file.
So I have a sort of a "backup"
Now I'm going to read and I'll report back how it went.
blakegriplingph said:
NVRAM data must have been wiped off somehow, as that's one reason as to why your serial numbers have gone kaput.
Click to expand...
Click to collapse
If this is the case, you can "download" (=flash) your backup files from SP Flash Tool. In scatter file change entries to "is_download: true". Open the edited scatter file with SP Flash Tool. Make sure you uncheck all checkboxes, except nvram, nvdata (and cache, if you still have problems with this partition). Double click on file name and select the file for each partition. Make sure EMMC_USER is selected. The file sizes must fit partition size. Do NEVER flash PRELOADER! Press start, then connect phone, then insert battery.
nvram.bin 5120 KiB (0x00500000)
nvdata.bin 32768 KiB (0x02000000)
cache.img 409600 KiB (0x19000000)
If done, hold Volume Up key while unplug + plug in USB cable, this will boot into recovery. Wipe Cache and Data
My sizes of the backup files:
nvram.bin 5 242 880 seems OK
nvdata.bin 33 554 432 seems OK
cache.img 419 430 400 bigger
Is there a way I can check the integrity of them before flashing?
And what when I get the "PMT changed for the ROM" error message?
I've attached the used scatter file
Should be fine if you use same scatter file used for read back. If you got "PMT changed" (probably wrong scatter file), you must restore all partitions (except preloader) with the exactly same scatter file you have created your backup. Then your phone should be restored to its original state no matter if scatter file was wrong. Once you get your phone in good condition, you can create your own scatter file with current partition layout from WwR MTK v2.30
Matty1993 said:
All good mate yeah orange state is because you unlocked bootloader and didnt factory reset [...]
If you still get dramas with orange state let me know ill manually patch the dm-verity out of your boot.img for you
Click to expand...
Click to collapse
Orange state just mean unlocked bootloader, you can't get rid of. Do not lock the bootloader again, just leave it orange state is fine...
I thought so and it doesn't really bother me
Matty1993 said:
Your device comes with out of the box encryption in your boot.img fstab your system path will be /dev/block/platform/mtk-msdc/******/msdc/by-name/system /system ext4 ro wait, "verify"
Click to expand...
Click to collapse
Zdendav said:
I did all the steps:
- wipe, format
- factory reset
hangs on the "POWERED BY android" logo, when trying to boot
- flashed boot.img in fastboot
- reboot
I was not fast enough to go onto TWRP, it tried to boot, hangs on the "POWERED BY android" logo
-reboot into TWRP
- wipe, format
- factory reset
still hangs on the "POWERED BY android" logo, when trying to boot
I can borrow exactly the same phone from a relative (fully working) - maybe I should do a full backup of it, then I'll have "clean" images of boot, recovery etc.
Meanwhile I did another full backup and this time I used WwR MTK v2.30 to create a correct scatter.
I attach both scatter files.
Click to expand...
Click to collapse
as @Matty1993 already figured out, your phone seems fine, just dm-verity prevents to boot because of recovery checksum mismatch. You have to disable dm-verity.
Install Disable_Dm-Verity_ForceEncrypt.zip from TWRP. This will patch your boot.img and modify fstab entries. Format Data, then use "Copy Log" option and upload recovery.log here
aIecxs said:
Should be fine if you use same scatter file used for read back. If you got "PMT changed" (probably wrong scatter file), you must restore all partitions (except preloader) with the exactly same scatter file you have created your backup. Then your phone should be restored to its original state no matter if scatter file was wrong. Once you get your phone in good condition, you can create your own scatter file with current partition layout from WwR MTK v2.30
Click to expand...
Click to collapse
I did try and I got the "PMT changed" even when I selected all partitons except preloader ..
I did borrow exactly the same phone from a relative and created a full backup and from it a proper scatter file. I compared both scatter files and there are differences (as expected)
I attach both scatter files
I don't know how to proceed.
1) Lock the bootloader?
2) Flash parts from the borrowed phone? Which parts?
PS I have also a backup of userdata taken in factory mode.
don't flash anything with SP flash tool, just see my previous post. boot + recovery + nvram are identical, but tee1 + tee2 + teeinfo missing, and metadata + userdata have different size. keep the backup created with scatter file from WwR_MTK this seems to be the right one
aIecxs said:
Install Disable_Dm-Verity_ForceEncrypt.zip from TWRP. This will patch your boot.img and modify fstab entries. Format Data, then use "Copy Log" option and upload recovery.log here
Click to expand...
Click to collapse
Done. Did it all in one go (without any reboot), then powered off.
Log is attached
aIecxs said:
don't flash anything with SP flash tool, just see my previous post. boot + recovery + nvram are identical, but tee1 + tee2 + teeinfo missing, and metadata + userdata have different size. keep the backup created with scatter file from WwR_MTK this seems to be the right one
Click to expand...
Click to collapse
Sorry I missed your post until I posted mine ...
I'll keep all backups until it's sorted out.
And thank you very much aIecxs and Matty1993 for all your help
thanks for the log. seems there is something wrong, maybe with TWRP or maybe with phone.
Code:
E:Primary block device '/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata' for mount point '/data' is not present!
Failed to mount '/cache' (Invalid argument)
Error installing zip file '/external_sd/Disable_Dm-Verity_ForceEncrypt_04.03.19.zip'
Flash stock boot.img and stock recovery.img from fastboot. reboot into stock recovery. Wipe Data + Cache. reboot to bootloader. boot into TWRP from fastboot. copy log to sdcard and upload again. reboot your phone and wait 5 minutes.
I flashed the stock recovery and boot in fastboot in one go.
Then rebooted to recovery but there is only "Supported API: 3" in the lower left corner of the display and that's all.
What to do next?
Edit: It's even worse, I'm not able to enter fastboot, recovery etc., the phone doesn't react to the volume button and always show the orange message a boot to the Supported API: 3 screen.
This indicates something is wrong with cache partition. Usually a normal system boot from stock boot.img will fix this. If you can't enter fastboot mode, flash recovery from SP Flash Tool. Try this version it has changed fstab. This should fix the /data mount. Then you should be able to enter fastboot again.
Code:
[strike]/data ext4 /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata flags=encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata[/strike]
/data ext4 /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata flags=encryptable=/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/metadata
Regarding /cache try following from fastboot:
Code:
fastboot format:ext4 cache
after this wipe cache again from stock recovery (you can boot stock recovery from fastboot without flashing it). if cache still not mounted in TWRP, your only choice left is flash backup of cache partition from your friends phone from SP Flash Tool
edit: attachment deleted
Flashed your recovery, now it always boots into twrp, volume buttons still seem to not work, I'm still not able to enter fastboot.
Edit: I was able to enter fastboot by "adb reboot bootloader" when in TWRP, strangely "adb reboot fastboot" booted into TWRP.
I formatted the cache, rebooted into stock recovery, formatted the cache again.
Rebooted into TWRP, in file manager the cache is empty, in the mount menu I'm not able to tick any of the listed partitions to mount it ...
I'm not able to post the new log, it copies it to /data/media but in the file manager the location is empty ...
i have added some mount points, please download and flash again. you can copy recovery.log from adb
Code:
adb pull /tmp/recovery.log C:\adb\recovery.log
please post output of df and mount
Code:
adb shell
mount
busybox df -aT
/ # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/ # busybox df -aT
Filesystem Type 1K-blocks Used Available Use% Mounted on
tmpfs tmpfs 463204 44 463160 0% /dev
devpts devpts 0 0 0 0% /dev/pts
proc proc 0 0 0 0% /proc
sysfs sysfs 0 0 0 0% /sys
selinuxfs selinuxfs 0 0 0 0% /sys/fs/selinux
tmpfs tmpfs 463204 32 463172 0% /tmp
adb functionfs 0 0 0 0% /dev/usb-ffs/adb
Hi there
I had some problems booting into Recovery and ERecovery. It would always stay endless in the Warning screen where it says that the Device is unlocked.
I run into it because of TWRP not Formating Data properly.
https://dl.twrp.me/anne/
twrp-3.5.1_9-0-anne.img14.6M 2021-03-13 15:27:54 ESTtwrp-3.5.0_9-0-anne.img13.2M 2020-12-27 21:03:29 EST
This Versions get stuck at:
Code:
Formatting Data using mkfs.f2fs...
Done
After it beeing stuck I could usually reach erecovery and wipe . But at one point it wouldn't work and I couldn't reacht the two and also couldn't stop the device from endless starting after shutting down.
I tried to flash several images from this one: https://androidhost.ru/1nfK
After flashing odm.img I could access the reflashed Stock Recovery and E-Recovery.
Update: Erasing Data with fastboot also works.
Note: It would show Google instead of Huawei at startup and in fastboot FRP:Unlocked doesn't show anymore after flashing odm.img
Else:To reach erecovery or twrp recovery I retried often to hold power and volume up when the device is turned off. It then vibrates two times when it works. I hat sometimes to try for 10 Minutes to reach one of the to.
I unlocked with PotatoNV. The phone can be opened quite comfortable with a straight package plastic like from a cabel or electric device and a hairdrier.
Update: I can actually not format Data with any of these TWRPs. This was working before flashing the odm or maybe an other image.
twrp-3.5.1_9-0-anne.img14.6M 2021-03-13 15:27:54 ESTtwrp-3.5.0_9-0-anne.img13.2M 2020-12-27 21:03:29 ESTtwrp-3.4.0-1-anne.img13.2M 2020-09-26 14:58:13 EDTtwrp-3.4.0-0-anne.img13.2M 2020-08-21 17:03:57 EDT
I could format with adb shell:
anne:/etc # mkfs.f2fs /dev/block/mmcblk0pXX
F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is enabled
Info: No support kernel version!
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 106086400 (51800 MB)
Info: zone aligned segment0 blkaddr: 512
Info: [/dev/block/mmcblk0p57] Discarding device
Info: Secure Discarded 0 MB
Info: Overprovision ratio = 0.880%
Info: Overprovision segments = 459 (GC reserved = 235)
Info: format successful
benaep said:
I can actually not format Data with any of these TWRPs.
Click to expand...
Click to collapse
Yes, you have installed wrong TWRP (version 3.4.0.x and 3.5.0.x is not fully compatible with our device and it's strongly NOT recommended do 'wipe data' runnig stock ROM , it may brick the phone).
Use recommended TWRP:
Recommended and tested TWRP Recovery
EMUI 8 Stock ROMs: 3.2.1-0 by pretoriano80 (with data decryption on Android 8 ) https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw EMUI 8 Custom ROMs: 3.2.1.0 by Catuva21...
forum.xda-developers.com
-Alf- said:
Yes, you have installed wrong TWRP (version 3.4.0.x and 3.5.0.x is not fully compatible with our device and it's strongly NOT recommended do 'wipe data' runnig stock ROM , it may brick the phone).
Use recommended TWRP:
Recommended and tested TWRP Recovery
EMUI 8 Stock ROMs: 3.2.1-0 by pretoriano80 (with data decryption on Android 8 ) https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw EMUI 8 Custom ROMs: 3.2.1.0 by Catuva21...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the direction Alf. So for the Newest Linage OS build that would be:
Pie Custom ROMs:
3.4.0-0-emui9_eR
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
right?
benaep said:
Thanks for the direction Alf. So for the Newest Linage OS build that would be:
Pie Custom ROMs:
3.4.0-0-emui9_eR
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
right?
Click to expand...
Click to collapse
If you want to flash LOS from TWRP (idk why, but it's your choice), use 3.2.1 by pretoriano80 (wiping etc.) After installing custom ROM, you can replace 3.2.1. with 3.4.0.0-emui9_eR.
-Alf- said:
If you want to flash LOS from TWRP (idk why, but it's your choice), use 3.2.1 by pretoriano80 (wiping etc.) After installing custom ROM, you can replace 3.2.1. with 3.4.0.0-emui9_eR.
Click to expand...
Click to collapse
Hi Alf
Thanks for the reply. Very gratefull for this. I'm trying since Weeks to get this running.
I just want a phone with minimal Google. I had /e/ but I didn't find a build and back in the days linage would be fine.
You think there is something which makes more sense?
benaep said:
I just want a phone with minimal Google
Click to expand...
Click to collapse
Then install "v" variant , e.g.
LOS 17.1-unoff.
https://sourceforge.net/projects/treblerom/files/LOSQ/2020.10.17/losq-v224-201017-arm64-bvN.img.xz/download
LOS 18.1-unoff.
https://sourceforge.net/projects/treblerom/files/LiR/2021.03.18/lir-v302-210318-arm64-bvZ.img.xz/download
and install opengapps - pico, nano, micro... , what suits you.
-Alf- said:
Then install "v" variant , e.g.
LOS 17.1-unoff.
https://sourceforge.net/projects/treblerom/files/LOSQ/2020.10.17/losq-v224-201017-arm64-bvN.img.xz/download
LOS 18.1-unoff.
https://sourceforge.net/projects/treblerom/files/LiR/2021.03.18/lir-v302-210318-arm64-bvZ.img.xz/download
and install opengapps - pico, nano, micro... , what suits you.
Click to expand...
Click to collapse
Yo Alf
Thanks for the Links to the Image files. I would never have found them myself. I tried now a few hours to make them run.
Formating and Wiping works with 3.2.1 by pretoriano80
I tried both images, but am not shure. I get an invalid zip file error when I copy it on the device. Sideload doesn't work. No connection or Success or Success 00.00 X.
I make it a zip on linux with --> unxz --> img2simg --> Create Zip Directory wit xarchiver.
I tried different combinations of this. First I forgot about simg and just made a zip out of the img.
Code:
/tmp/recovery.log: 1 f...57322 bytes in 0.010s)
~ >>> adb sideload /home/bni/Downloads/losq17.zip
adb: failed to read command: Success
~ >>> adb sideload /home/bni/Downloads/losq17.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
~ >>> adb pull /tmp/recovery.log /home/bni/Downloads/recovery.log
/tmp/recovery.log: 1 f...59228 bytes in 0.007s)
Code:
~ # twrp install /image/LOS17_SIMG.zip
Installing zip file '/image/LOS17_SIMG.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Invalid zip file format!
Error installing zip file '/image/LOS17_SIMG.zip'
Done processing script file
benaep said:
I get an invalid zip file error when I copy it on the device.
Click to expand...
Click to collapse
Of course, it is not a flashable .zip file.
You have to install it as image file, unpack .zip package, transfer exctracted .img file to the SD card. In TWRP go to Install , select Install image, choose lineage .img file , mark "system image" and flash.
If you need to do a factory reset , first replace TWRP with stock recovery and perform factory reset in recovery.
Or, flash Lineage.img in fastboot,without TWRP, wipes, errors etc. (make sure to have the stock recovery flash) - https://forum.xda-developers.com/t/losq-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543