All CM13 and RR releases we have so far are using pretty old China Dev MIUI v.6.6.30 as base not even listed on Xiaomi Downloads anymore. This as some of us know is the cause of all bugs we've had with these custom ROMs and were fixed by replacing vendor files from newer MIUI versions. On top of that some helium users cannot reboot to recovery from Android, phone doesn't power off... things like that... which most likely is due to using the wrong hydrogen kernel in this builds. Some users including me are experiencing no data going thru on good connection... Not gonna even mention VoLTE etc. So we still have bugs...
The vendor files and kernel that comes from MIUI as base are the main part that makes the hardware working flawlessly with the Android OS. These files are proprietary files with closed code, we can't change them so we have to rely on whatever Xiaomi do to optimize device performance. But we can choose which version to use and that is my goal here... Test and find the best set that works with custom ROMs.
Here we go... I have been testing the latest Global MIUI as base for two days now and so far haven't seen any issues at all. That doesn't mean no bugs... More time and testing is needed. But at least they are not any worst than what we are using now.
The common sense and logic is(fixed bugs proved that) vendor files and kernel from latest stable Global MIUI for the particular device should have more bug fixes and optimizations for the world out of China(I hope)... So using the best of my knowledge I compiled these two sets for:
HYDROGEN:
Based on latest Mi Max official Global MIUI v.8.0.1 (miui_MIMAXGlobal_V8.0.1.0.MBCMIDG_3657fef420_6.0.zip)
Download: vendor-base801MG_update-HYDROGEN.zip
HELIUM:
Based on latest Mi Max Prime official Global MIUI v.8.0.3 (miui_MIMAX652Global_V8.0.3.0.MBDMIDG_2da4c7e9db_6.0.zip)
Download: vendor-base803MG_update-HELIUM.zip
These packages are not recovery flashable zips!!! Keep reading for install instructions!
The install will get all vendor proprietary files I know of, firmware and kernel properly updated for the device code. Let's hope we get the better and latest from Xiaomi...
INSTALL INSTRUCTIONS:
MAKE TWRP BACKUP OF SYSTEM AND BOOT PARTITIONS BEFORE ANYTHING TO REVERS CHANGES IF YOU NEED TO!!!
The installation process is a little bit involving due to replacing the kernel in the actual installed boot.img in your device. I can't supply universal updated boot.img because they might be different from one release to another. I want to update what you already have. Did my best to make it user-friendly as I can without coding special app or something. Thanks to this guy whoever he is for the boot.img tools https://github.com/xiaolu/mkbootimg_tools.
Follow the steps and you should be fine:
1. Download the appropriate zip for your device code and unzip it to the root of your internal storage. You should end up with /sdcard/vendor_update folder;
2. Open your favorite terminal emulator app and execute the following commands one at a time pressing ENTER after each line:
Code:
su
hit ENTER
Code:
cp /sdcard/vendor_update/vendor-updater.sh /data/local/tmp/
hit ENTER
Code:
chmod 777 /data/local/tmp/vendor-updater.sh
hit ENTER
Code:
sh /data/local/tmp/vendor-updater.sh
hit ENTER
Alternatively you can USB connect your phone to computer and run the same commands from adb shell.
For HYDROGEN users:
That's all you have to do. The script will update your kernel and automatically will reboot phone to recovery and update vendor files so save your work before running the commands!
For HELIUM users:
Due to that can't reboot recovery bug you have to reboot manually by holding POWER and VOLUME+ buttons or fastboot method... The vendor zip will be flashed automatically and phone reboots back to system. If not, install /sdcard/vendor_update/vendor_update-HELIUM.zip manually and that's it.
Simple stuff if you decide to test these packages...
To verify update you should see kernel and baseband versions in About Phone changed like in the attached hydrogen screenshot. I can't test helium so they might be a little different. Check WiFi also... If you can turn it on and works all is good...
Helium users see if you can reboot to recovery from Advanced Power Menu, check if you can Power OFF your phone etc... the usual bugs.
Let see if these updates change anything for good or bad.
Happy testing!:good:
EDIT: Looks like 3G bug is still present in latest MIUI modem files. Flash CM_3G_fix.zip and keep the rest of the update if 3G bug is back.
Thanks a lot.
You are welcome!
Please guys lets not quote the whole OP... It takes so much screen...
No success
Maybe my fault on terminal.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
No success
Maybe my fault on terminal.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Maybe not... Give me a mnute...
That's what happens when you code unix script on windows and forget to convert it.
@JulianJenner
EDIT: FIXED(i think)...Try now and let me know it works or not!? Helium feedback appreciated...
I'm enthusiastic.
But I do not understand it.
I did what you said.
I used a terminal emulator from Play Store I just copied your text.
JulianJenner said:
I'm enthusiastic.
But I do not understand it.
I did what you said.
I used a terminal emulator from Play Store I just copied your text.
Click to expand...
Click to collapse
Did you redownload the fixed zip? Do you have the "/sdcard/vendor_update" folder with the files in it?
Make sure you copy text line by line hitting ENTER after each one!!! That's 4 lines... su... cp... chmod... sh...
Hydrogen works for me... Can't test helium unfortunately...
Terminal running successfully.
Phone reboot.
But my BB and Kernel version did not changed...
Yours Mon Aug 29
Mine Wed Jun 29
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
No. I will download again. A.S.A.P.
---------- Post added at 11:18 PM ---------- Previous post was at 11:01 PM ----------
Working.
It was my fault.
"...line by line hitting ENTER after each one..."
Firstly I did not understand it.
I pressed Enter after at the end once...
Click to expand...
Click to collapse
Phew... I thought I screwed up again...
Run this in terminal emulator:
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Upload /sdcard/boot.img somewhere... I will update kernel and you will flash it... Let see if version changes. Maybe Xiaomi haven't updated helium kernel yet!? But it is definitely different from the hydrogen latest one byte by byte...
Baseband was probably already updated if you are running ajsmsg78's RR.
I did.
Upload...
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
I did.
And now?
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Go to sdcard and you will find boot.img in there, upload it somewhere and give me the link...
Ok. I see. Upload.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
Ok. I see. Upload.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Just checked helium kernel with hex editor and the date is Fri Sep 2 23:22:31 CST...
Have no idea why it didn't update since script did not throw any error, right? Did the phone reboot to recovery and flashed the vendor zip?
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
Did the phone reboot to recovery and flashed the vendor zip?
Click to expand...
Click to collapse
NOPE!
OK. I think solved.
Ran script again in adb shell.
And when phone try to reboot recovery.
Stopped it.
Reboot in Fastboot mode.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
JulianJenner said:
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
NOPE!
Where is this vendor zip ( okay, I find it. vendor_update-HELIUM.zip)? Can I flash it from TWRP?
I have stock recovery, I used TWRP from Fastboot mode 'fastboot boot recovery.img' command...
Click to expand...
Click to collapse
Yes you can but first kernel has to get updated or wifi won't work.
And thats not the point... I want to see why script did not do the job but I will debug it with someone else...
Here is updated kernel link removed
Download it to /sdcard/boot_updated.img and run this in terminal:
Code:
su
hit enter
Code:
dd if=/sdcard/boot_updated.img of=/dev/block/bootdevice/by-name/boot
hit enter
After that reboot to recovery and flash that vendor_update-HELIUM.zip
Post versions, please...
OK. I think solved by myself.
Ran script again in adb shell.
And when phone tried to reboot recovery.
I stopped it with buttons.
Reboot in Fastboot mode with buttons.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
JulianJenner said:
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
NOPE!
OK. I think solved.
Ran script again in adb shell.
And when phone try to reboot recovery.
Stopped it.
Reboot in Fastboot mode.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
Click to expand...
Click to collapse
Aaah, I got it... that can't reboot recovery bug for helium ... I will change script to not boot automatically and let helium users boot to TWRP manually and it will flash vendor zip automatically. Didn't get that bug under consideration.
Thank you for opening my eyes Hate when I can't test things...
This is mine, helium, seems it has been success, I use the one you posted at the first.
@nijel8... your work is a hard work!
I am proud to be working with you.
laolang_cool said:
This is mine, helium, seems it has been success, I use the one you posted at the first.
Click to expand...
Click to collapse
Great...:good: Seems like you don't suffer from hydrogen kernel.
Related
Here are the 2.3.2 .img's compiled from aosp source for crespo (Nexus S)
We don't have a pure 2.3 ROM compiled from aosp source yet, so I decided build one, and here are the .img's from my build.
These can be used to restore Nexus S back to aosp, or flash all images for a pure aosp experience.
HOWEVER: These are NOT the official Google factory images for Nexus S, only compiled from source.
Attached are: system.img boot.img recovery.img userdata.img
Installation:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
All images being provided work 100%, as I have it installed on my nexus S currently and flashed via fastboot.
disclaimer: WARNING! I am in no way shape or form responsible for ANY DAMAGE you may do to your phone. I am simply providing the files, however you decide to flash on your own, not me.
These images also do not contain any proprietary apps such as the Google apps (Maps, Market, Gmail, etc)
Clear? ok then, proceed to download
system .img link: http://www.mediafire.com/file/k2jopya0o416m8j/system.img
others are attached below.
UPDATE: these .img's are for 2.3.2
Attached bcm4329.ko module to fix wifi for users who flashed my boot.img on a non-aosp ROM (push to /system/modules)
2.3.2 OTA package
Here is the 2.3.2 ota update package for those of you who don't like/wanna use fastboot for whatever reason.
Rename as update.zip, place on sdcard and flash as usual.
http://www.mediafire.com/file/fl1nxdpleitd392/2.3.2_full_crespo-ota-eng-signed.zip
WARNING! This ota update package is fully stock, has NO ROOT or Google proprietary applications, and will revert you to the stock recovery.
Google Applications archive can be found here: http://goo-inside.me/gapps/
Atached below are the files needed to manually root: SuperUser.apk, su, busybox.
Code:
adb push SuperUser.apk /system/app
adb push su /system/xbin
adb push busybox /system/xbin
chmod 6775 /system/xbin/su
chmod 6775 /system/xbin/busybox
adb shell reboot
If terminal doesn't let you remount in adb you may have to do it through the phone. Place all root files on sdcard:
Code:
mount -o rw,remount /dev/block/mmcblk0p2 /system
cp /sdcard/SuperUser.apk /system/app/
cp /sdcard/su /system/xbin/
cp /sdcard/busybox /system/xbin/
chmod 6775 /system/xbin/su
chmod 6775 /system/xbin/busybox
Reboot with a battery pull.
reserved again. You Never know
Thanks alot I've been looking for the stock recovery img
Sent from my Nexus S using Tapatalk
brian6685 said:
Thanks alot I've been looking for the stock recovery img
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
The recovery image from this post sadly still does not allow to flash the update from Google.
Getting signature verification error and yes i reverted back to the boot.img posted here as well.
EDIT: the boot.img here is also breaking wifi.
thanks for the effort though
clubtech said:
The recovery image from this post sadly still does not allow to flash the update from Google.
Getting signature verification error and yes i reverted back to the boot.img posted here as well.
EDIT: the boot.img here is also breaking wifi.
thanks for the effort though
Click to expand...
Click to collapse
Why wouldn't the ota work if you were using the stock recovery? That's weird
Sent from my Nexus S using Tapatalk
clubtech said:
The recovery image from this post sadly still does not allow to flash the update from Google.
Getting signature verification error and yes i reverted back to the boot.img posted here as well.
EDIT: the boot.img here is also breaking wifi.
thanks for the effort though
Click to expand...
Click to collapse
??? I flashed everything before posting and all was working perfect. I flashed all .img's though, maybe wifi broke for having a different system image and different wifi modules than aosp.. I just flashed paul's rom and reverted to stock recovery.img without a hitch with the one I posted.
brian6685 said:
Why wouldn't the ota work if you were using the stock recovery? That's weird
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
That's because it is not really stock recovery, it is a recovery built from source.
I guess it does not have google's signature.
Do you know of anywhere I can get the stock recovery? Or does fastboot oem lock bring back stock recovery?
Sent from my Nexus S using Tapatalk
jroid said:
??? I flashed everything before posting and all was working perfect. I flashed all .img's though, maybe wifi broke for having a different system image and different wifi modules than aosp.. I just flashed paul's rom and reverted to stock recovery.img without a hitch with the one I posted.
Click to expand...
Click to collapse
I can install your recovery, no problem. but i am not able to use the update.zip from Google with your stock recovery (signature verification failed).
I also tried with you stock recovery and boot.img - same issue.
When i booted the device with you stock recovery + boot.img but my original (stock) system.img - wifi could not start.
clubtech said:
When i booted the device with you stock recovery + boot.img but my original (stock) system.img - wifi could not start.
Click to expand...
Click to collapse
That's probably where the problem lies. I flashed all .img's including my system.img and wifi worked perfectly
Does this include gapps?
Anderdroid said:
Does this include gapps?
Click to expand...
Click to collapse
no, they're aosp images built from source.
clubtech said:
When i booted the device with you stock recovery + boot.img but my original (stock) system.img - wifi could not start.
Click to expand...
Click to collapse
Issue fixed. Please see the OP.
Hi jroid,
I tried to compile the 2.3.1 sources from AOSP today and ran into hundrets of warnings (no errors though so I might be OK). I did some coding for linux before but have no experience building Android from source. Can you provide the steps required to build?
As far as I can tell my environment is setup properly: I did a fresk Debian 64bit, JDK 6 and all the packages listed on sources.android.com - even if the information listed there is outdated. I installed Eclipse as well but didn't use it so far because I want to get the unchanged AOSP build correctly first.
To build I ran env_setup.sh, then lunch and picked crespo, then make... that's where I'm stuck right now.
I want to get the base build correctly before starting any changes. I'd love to get this setup in a way that allows me to test the build in the emulator first and then flash to the NS... Not sure if that's the best way or using fastboot boot instead of flash to see if it's working properly directly on the device (all new to me, sorry if these are dumb questions).
I searched the forum and the wiki but didn't find general or NS specific documentation for AOSP builds...
ToSa2 said:
Hi jroid,
I tried to compile the 2.3.1 sources from AOSP today and ran into hundrets of warnings (no errors though so I might be OK). I did some coding for linux before but have no experience building Android from source. Can you provide the steps required to build?
As far as I can tell my environment is setup properly: I did a fresk Debian 64bit, JDK 6 and all the packages listed on sources.android.com - even if the information listed there is outdated. I installed Eclipse as well but didn't use it so far because I want to get the unchanged AOSP build correctly first.
To build I ran env_setup.sh, then lunch and picked crespo, then make... that's where I'm stuck right now.
I want to get the base build correctly before starting any changes. I'd love to get this setup in a way that allows me to test the build in the emulator first and then flash to the NS... Not sure if that's the best way or using fastboot boot instead of flash to see if it's working properly directly on the device (all new to me, sorry if these are dumb questions).
I searched the forum and the wiki but didn't find general or NS specific documentation for AOSP builds...
Click to expand...
Click to collapse
I'm away from my laptop right now, but get adb installed first. Repo sync then cd to /crespo and run extract-files.sh
.Build env_setup.sh
Lunch full_crespo-userdebug
Make
Warnings should be fine, I got them too and it compiled perfectly. If you get errors, u will know. The compile with stop
Sent from my Nexus S
Thanks!
I did the extract-files.sh now which I missed before - running make over night so I'll see tomorrow if I get any errors...
Any advice how to test minimizing the risk (emulator / fastboot boot)?
ToSa2 said:
Thanks!
I did the extract-files.sh now which I missed before - running make over night so I'll see tomorrow if I get any errors...
Any advice how to test minimizing the risk (emulator / fastboot boot)?
Click to expand...
Click to collapse
yea you can use the fastboot boot command to test. I personally just flashed all the images through fastboot and it booted fine. aosp 2.3.1 (which I compiled) is in my experience FASTER and more smooth than the stock rom that shipped with the NS. Call audio quality is MUCH more rich robust than it is on the factory builds. have no idea why but it is
Since the Google apps aren't included, I'm guessing they all may be downloaded/installed from the Market... is that correct?
Thanks,
jankyboy said:
Since the Google apps aren't included, I'm guessing they all may be downloaded/installed from the Market... is that correct?
Thanks,
Click to expand...
Click to collapse
no, not all. Only some, but this doesn't even include the market so you couldn't even do that. I'm compiling from source again and probably release an AOSP rom in a day or 2, maybe even today..
Official nightlies are up for our device's:
Scorpion (LTE): http://download.cyanogenmod.org/?device=scorpion
Scorpion (Wifi): http://download.cyanogenmod.org/?device=scorpion_windy
TWRP Installation:
You can install TWRP through ADB or Terminal Emulator app. Thanks to ejdan for finding this!
ADB:
Before you begin:
- Download TWRP:
Code:
[URL="http://qzerno.troxit.nl/android/misc/TWRP/Sony%20Xperia%20Z3%20Tablet%20Compact/WiFi%20-%20SGP61x/twrp.img"]WiFi - SGP61x[/URL]
[URL="http://qzerno.troxit.nl/android/misc/TWRP/Sony%20Xperia%20Z3%20Tablet%20Compact/LTE%20-%20SGP62x//twrp.img"]LTE - SGP62x[/URL] (Credits to [B]der_bert[/B] for making this)
- set Root access to "Apps and ADB" in Developer options.
- set USB Debugging Mode to "ON" in Developer options.
Instructions:
1. Put twrp.img in the root of your Z3TC.
2. Open command prompt and go to the location where ADB.exe is.
3. Start an ADB shell:
Code:
adb shell
4. Gain root access:
Code:
su
5. Flash TWRP on FOTAKernel partition
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
6. Reboot to recovery and you would see TWRP.
Terminal Emulator:
Before you begin:
- Download TWRP:
Code:
[URL="http://qzerno.troxit.nl/android/misc/TWRP/Sony%20Xperia%20Z3%20Tablet%20Compact/WiFi%20-%20SGP61x/twrp.img"]WiFi - SGP61x[/URL]
[URL="http://qzerno.troxit.nl/android/misc/TWRP/Sony%20Xperia%20Z3%20Tablet%20Compact/LTE%20-%20SGP62x//twrp.img"]LTE - SGP62x[/URL] (Credits to [B]der_bert[/B] for making this)
- set Root access to "Apps" in Developer options.
- set Local terminal to "ON" in Developer options. (If you don't have this option download then Terminal Emulator from the Play Store)
Instructions:
1. Put twrp.img in the root of your Z3TC.
2. Open the app Terminal or Terminal Emulator
3. Gain root access:
Code:
su
4. Flash TWRP on FOTAKernel partition
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
5. Reboot to recovery and you would see TWRP.
Version Information:
Status: Discontinued
Created 2014-12-24
Last Updated 2015-03-25
Nice? any plans for LTE model?
Lte model is merged into cm sources so it should work
Will try to get up an simple kernel with intelliplug and so on
moritz31 said:
Lte model is merged into cm sources so it should work
Will try to get up an simple kernel with intelliplug and so on
Click to expand...
Click to collapse
I'd be interested and thanks!
chaostimmy said:
Nice? any plans for LTE model?
Click to expand...
Click to collapse
I'm building right now for LTE but I can't test this builds.
EDIT: LTE Build is up!
I have tried the Wifi version and it seems to work fine.
First I had a few restarts when locking the screen but it seems to have fixed itself now. Maybe because I disabled double tap to sleep/wake?
SD card is not mounted. Is there a way to fix it? The card is listed in /proc/partitions so it should be possible to fix with a proper fstab.
ejdan said:
SD card is not mounted. Is there a way to fix it? The card is listed in /proc/partitions so it should be possible to fix with a proper fstab.
Click to expand...
Click to collapse
I compared fstab.qcom in CM12 with the stock kernel and found a difference. The stock kernel has /devices/msm_sdcc.3/mmc_host for sdcard1 but CM12 has /devices/msm_sdcc.2/mmc_host
I changed '2' to '3' in the ramdisk and now SD card works. I have attached my modified kernel image. Unpack the zip file and flash cm12-sdcard1-fix.img using fastboot. This kernel is taken from cm-12-20141225-0800-UNOFFICIAL-scorpion_windy.zip
Qzerno said:
I'm building right now for LTE but I can't test this builds.
EDIT: LTE Build is up!
Click to expand...
Click to collapse
Great, thank you but I could not install it. In TWRP it says:
"This package is for device: SGP621, SGP641, SGP651, scorpio; this device is scorpion_windy."
It's not. I have the LTE version, SGP621 aka Scorpion.
Thanks for the builds! What has everyone flashed?
Home Launcher
Is Trebuchet included in these builds? Ive flashed todays (26th) build and am I'm just getting the options for Google Now and Nova Launcher.
---------- Post added at 08:09 PM ---------- Previous post was at 07:55 PM ----------
Any chance of making the kernel flashable?
BUG REPORT: double tap to wake is not working
ejdan said:
I compared fstab.qcom in CM12 with the stock kernel and found a difference. The stock kernel has /devices/msm_sdcc.3/mmc_host for sdcard1 but CM12 has /devices/msm_sdcc.2/mmc_host
I changed '2' to '3' in the ramdisk and now SD card works. I have attached my modified kernel image. Unpack the zip file and flash cm12-sdcard1-fix.img using fastboot. This kernel is taken from cm-12-20141225-0800-UNOFFICIAL-scorpion_windy.zip
Click to expand...
Click to collapse
Nice, thanks for fixing this. Do you maybe know which file in the source need to edit to get this works? then I can commit it to CyanogenMod.
Noe_S said:
Great, thank you but I could not install it. In TWRP it says:
"This package is for device: SGP621, SGP641, SGP651, scorpio; this device is scorpion_windy."
It's not. I have the LTE version, SGP621 aka Scorpion.
Click to expand...
Click to collapse
The recovery (TWRP) need to get a build separately for the scorpion (SGP621), then it should work.
I will search for a alternative installation method for the scorpion.
xan_asmodi said:
Is Trebuchet included in these builds? Ive flashed todays (26th) build and am I'm just getting the options for Google Now and Nova Launcher.
---------- Post added at 08:09 PM ---------- Previous post was at 07:55 PM ----------
Any chance of making the kernel flashable?
Click to expand...
Click to collapse
Yes, Trebuchet is included in these build, PA Gapps remove Trebuchet I can upload Trebuchet separately if you want.
I want to make the kernel flashable but that has not yet succeeded.
xan_asmodi said:
BUG REPORT: double tap to wake is not working
Click to expand...
Click to collapse
Thanks for the bug report. I also noticed this. I will add this in the OP.
Qzerno said:
Nice, thanks for fixing this. Do you maybe know which file in the source need to edit to get this works? then I can commit it to CyanogenMod.
Click to expand...
Click to collapse
I made a pull request on Github. Not sure if it is the correct way to do it
https://github.com/CyanogenMod/android_device_sony_scorpion_windy/pull/1
The file fstab.qcom is in rootdir. Because of the overlay (scorpion is based on shinano common) I had to add a new file. I have not built from source so I have not checked that it is working but manually updating the ramdisk did work.
ejdan said:
I made a pull request on Github. Not sure if it is the correct way to do it
https://github.com/CyanogenMod/android_device_sony_scorpion_windy/pull/1
The file fstab.qcom is in rootdir. Because of the overlay (scorpion is based on shinano common) I had to add a new file. I have not built from source so I have not checked that it is working but manually updating the ramdisk did work.
Click to expand...
Click to collapse
Ahh that's why I can't find that file. I have add the file local and building right now.
EDIT: Yeah I have 10 posts!
Qzerno said:
Ahh that's why I can't find that file. I have add the file local and building right now.
Click to expand...
Click to collapse
You may have to add the file to a makefile somewhere but lets see how it goes.
Qzerno said:
Thanks for the bug report. I also noticed this. I will add this in the OP.
Click to expand...
Click to collapse
Your welcome Should I post stuff as I find them or PM you so you can update the OP?
Could you post trebuchet separately? That'd be a great help. I think the PA guys need to incorporate Aroma installer, because I don't think Google Now Launcher is as good as Trebuchet.
Keep up the good work, hopefully we'll get the camera drivers soon. I'll look to see if the camera module is the same as the Z2 tab, if so we may not need to wait, just take them from the other repository.
Oh, one more thing...
Xposed doesn't install through a combination of crap cyanogenmod recovery and other stuff which I can't profess to understand
Edit: I now understand that this is because of the shift from Dalvik runtime to ART. Getting CM12 to run Xposed will either require reverting to Dalvik (is this possible?) or waiting for the Xposed devs to rewrite Xposed.
When updating to a new nightly, you can flash over the previous build. When you do you need to reflash the ram disk/kernel update.
BUG REPORT: Rebooting into recovery from power menu doesn't work. Requires manual intervention at 'Sony screen'/purple LED.
Intalled it and works fine as far as i can tell. Can´t move Apps to he sd card thogh (not enough space error) but that might be because of that known sd issue. I have general access to the sd though.
Cheers and thanks
Chris
MasterTRL said:
Intalled it and works fine as far as i can tell. Can´t move Apps to he sd card thogh (not enough space error) but that might be because of that known sd issue. I have general access to the sd though.
Cheers and thanks
Chris
Click to expand...
Click to collapse
What nightly are you using and did you flash the sd card fix?
CTR Recovery for Galaxy A5
Hi all,
I've ported CTR Recovery from the developer carliv (now bluefirebird) on our Galaxy A5.
This recovery is based on the old CWM, by koush, with some features you can find in the original post HERE, so if you are tired of the TWRP recovery and u are looking for something similar to the old CWM, don't hesitate to download this
NOTE: It should work in any A500 variant, but it's tested only on SM-A500FU variant, so flash on other variants at your own risk!
Desclaimer:
Code:
echo "I'm not responsable for bricked phones, overheat phones, for global warming, for phones that want to suicide without a reason and for imminent explosions"
DOWNLOADS: You can download the recovery here: https://www.androidfilehost.com/?w=files&flid=82499
HOW TO FLASH:
ON WINDOWS (Odin method)
1) Download Odin
2) Download the recovery (with .tar extension)
3) Go in download mode by pressing Power Button + Vol - + Home Button
4) Connect your smartphone to the PC
5) Open odin version 3.9 or 3.10
6) Select AP button and open the recovery file
7) Press start
8) Enjoy
ON LINUX (Heimdall method):
1) Extract tar file with:
$ tar xvf recovery_file.tar
You will find a recovery.img file
2) Open Heimdall Frontend
3) Select pit file (you can find it on sammobile)
4) Select recovery partition
5) Load the recovery.img file and flash
6 Enjoy
ON ANDROID (Need Root)
1) Download flashify or rashr
2) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
3) Open flashify or rashr and select recovery file
4) Flash it
5) Enjoy
ON RECOVERY
IF YOU ARE ON TWRP:
1) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
2) Reboot to recovery
3) Go to install zip menu
4) Select "Install Image" box
5) Select recovery.img file and flash in recovery partition
6) Reboot to recovery
6) Enjoy
ON TERMINAL
If you are on Android (any rom, TWRP, or CTR) (Need Root)
1) Open terminal. If you are on CTR you need Aroma FileManager
2) run:
$ dd if=/path/to/recovery.img of=/dev/block/bootdevice/by-name/recovery
If you are on adb run:
$ adb shell dd=/path/to/recovery.img (inside the phone, not the path of the recovery.img stored in the pc) of=/dev/block/bootdevice/by/name/recovery
3) Enjoy
[NEW] CTR with CWM graphics section
Well, since CWM support ended with cm-11.0, and no one resurrected it, I've decided to give my contributo to the best recovery (in my opinion) which written the begin of android customization, for flashing zip roms, take nandroid backups... So, as I said, since no one resurrected it, I've decided to modify ctr sources, which are based on CWM recovery and which are compilable in cm-12.1 and cm-13.0, for creating a recovery which has, CTR features, but which really like the old CWM.
-So, what does this version offer?
~If you want to know what does it include, please see read this (green highlighted text)
NOTE: If you want to compile with cwm recovery you need my fork which you can find here:
https://github.com/DeadSquirrel01/carliv_touch_recovery_new only cm-12.1 branch for the moment
Then you need to add in BoardConfig.mk (in the device tree) the following flag:
USE_CWM_GRAPHICS := true
otherwise it will compile standard CTR
Flashing instuctions:
Look at "HOW TO FLASH" section
Download Link: Same as CTR recovery link, but you have to download the ones wich have a name which begins with "[CWM]"
OTHER NOTE: Since I've compiled CTR with CWM graphich with an half crapped cm-12.1 source tree, and adb doesn't work (except in sideload), I couldn't take screenshot, so, I've uploaded some photos, instead, which are taken with my ~4 years ago Samsung Galaxy Pocket, so don't flame me for bad quality , and since I tried to upload in attachments, but it doen't show the photo when clicking on the attachment, I've upload a zip with 4 screenshots
HERE (Google Drive Link)
Credits:
@bluefirebird for recovery sources
@TheWhisp for device tree
Me (DeadSquirrel01) for porting the recovery , adding CWM graphics, editing images and adding some cwm features
Sources:
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5-common
CTR: https://github.com/carliv/carliv_touch_recovery_new
CTR with CWM graphics: https://github.com/DeadSquirrel01/carliv_touch_recovery_new branch cm-12.1 only for the moment and you need to add "USE_CWM_GRAPHICS := true" in BoardConfig.mk
Changelog
03/09/2016 (update N2):
_ Add menu color change: you can now change highligh+text color to 3 different colors: blue (default), green or orange.
See my github commit for info, I wrote some awesome comments
06/10/2017 (Update N3):
_Save menu color setting to /sdcard/clockworkmod/cwm_config, so that it's not lost on reboot, resulting a recovery which has always the blue color, even if the user has chosen orange or green.
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
oss_mosis said:
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Click to expand...
Click to collapse
Yes you can install roms
meemb said:
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
Click to expand...
Click to collapse
Thanks for the support
you welcome brother
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
Thanks bro
Nice Recovery.. Succesfully rooted my stock 6.0.1 by flashing supersu (you can flash this file to root on any android which have custom recoveries) on this recovery. It is like stock recovery but with a lot of features.
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
corsicanu said:
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
Click to expand...
Click to collapse
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
DeadSquirrel01 said:
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
Click to expand...
Click to collapse
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
corsicanu said:
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
Click to expand...
Click to collapse
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
DeadSquirrel01 said:
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
Click to expand...
Click to collapse
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Cheers!
So i rebooted in linux and here`s the output:
Code:
[email protected] ~ $ adb devices
List of devices attached
???????????? no permissions
[email protected] ~ $ adb shell
error: insufficient permissions for device
And when tryin` to Mount USB Mass storage this is the output:
Code:
Error mounting /dev/sr1 at /media/hades/671D-12F5: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,utf8=1,showexec,flush" "/dev/sr1" "/media/hades/671D-12F5"' exited with non-zero exit status 32: mount: /dev/sr1 is write-protected, mounting read-only
mount: /dev/sr1: can't read superblock
I have 32gb class 10 sdcard formatted as fat32.. And from what i see it tries to mount as vfat, this for sure is from the fstab..
Any ideas?
corsicanu said:
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Will edit this post in a minute. Cheers!
Click to expand...
Click to collapse
Since it's a recovery it works with any a500xx variant (same chipset ) and also it's the same thing with roms for example on my pac-rom rom noone said it doesn't boot on a500xx. Regarding adb, bad drivers i think
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Qcraft said:
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Click to expand...
Click to collapse
So use thiz
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
akil777 said:
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
Click to expand...
Click to collapse
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
DeadSquirrel01 said:
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
Click to expand...
Click to collapse
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
akil777 said:
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
Click to expand...
Click to collapse
Yes, the commands of any linux distro, but they are less... only indispensable commands
What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit
@pl_blaze brother always thank you for the contributions that you do without coming to the light .and thanks for you @op to post working twrp for stock
this twrp will work on 7.1.2 ? i'm now on aex rom
Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.
I reshare this twrp img on Telegram group,I tested it, works without problem
Flash of permaent twrp not tested by me
It's a good twrp!
CosmicDan said:
What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit
Click to expand...
Click to collapse
what does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
View attachment 4438212
teacapan said:
Fastboot boot (hotboot) anwhat does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
Click to expand...
Click to collapse
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.
alkesh95 said:
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.
Click to expand...
Click to collapse
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same
It's possible to make password for twrp
DELETED.
lef7er1s said:
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same
Click to expand...
Click to collapse
1-yes
2-yes
3-yes
Anyway thanks for try help me.
Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553
Polluktus said:
this twrp will work on 7.1.2 ? i'm now on aex rom
Click to expand...
Click to collapse
Not sure, I've only tested on stock Oreo. Try and and let us know!
atttoush said:
Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.
Click to expand...
Click to collapse
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Sounds like you just need to learn more about how to use console tools. You need to make sure the "fastboot boot filename.img" command will have a "filename.img" that matches the img filename in the current directory. This is just an example - substitute "filename.img" for the real filename. Use the CD command to change directory to where the img is.
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553
Click to expand...
Click to collapse
Try renaming the img file to something simpler like oreo_twrp.img
Edit: ah yes, the file you are pointing to has to be in the same directory where you opened cmd window, as cosmicdan stated above
CosmicDan said:
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
Click to expand...
Click to collapse
Glad you open this thread. I'll wait for your compiled version to give it a try
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.
silv3rfox said:
Glad you open this thread. I'll wait for your compiled version to give it a try
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.
Click to expand...
Click to collapse
Thanks, i will.
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
Before flashing recovery
CD C:\Users\YOUR_USERNAME\Desktop\Adb
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
The name of the file is ending with .img, delete ending " .img ", see below that patched_boot without .img in the end
Thanks for this. I checked out the differences between this and the flashable zip I was using (twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester) and found this:
Code:
# write the new boot image to boot block
write_boot() {
print "Writing new boot image to memory..."
cd "$tmp"
if $use_dd; then
dd if=boot-new-a.img of="$boot_block"_a
[ $? = 0 ] || abort "Failed to write boot image A! You may need to restore your boot partition"
dd if=boot-new-b.img of="$boot_block"_b
[ $? = 0 ] || abort "Failed to write boot image B! You may need to restore your boot partition"
else
flash_image "$boot_block" boot-new.img
fi
[ $? = 0 ] || abort "Failed to write boot image! You may need to restore your boot partition"
}
This also flashes it into boot_a and boot_b correct?
What other differences does this have over that?
Hi all:
Here is a LineageOS 19.1 ROM for Z5 compact (suzuran).
New: ROM with microG apk's included in priv-app:
Download 2023-06-11
Please pay attention: microG can't coexist with GApps! So decide whether to install microG OR GApps!
If you want to remove microG, enter these commands line by line in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm /system/priv-app/DroidGuard/DroidGuard.apk
rm /system/priv-app/FakeStore/FakeStore.apk
rm /system/priv-app/GmsCore/GmsCore.apk
rm /system/priv-app/GsfProxy/GsfProxy.apk
exit
Reboot!
Or flash this microG-remover.
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 12 (S)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 June 2023
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.7.0!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Audio
Bluetooth
New: Camera fully working! (with the restriction to 8 MP)
Enforced SELinux support
Fingerprint (sometimes crashes)
FM-Radio (maybe it needs a few restarts before it's working)
GApps
German App AusweisApp2
GPS
Headset
LiveDisplay
Location services
Network Traffic Monitoring
NFC
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
Sensors
Signed build
SMS
Sounds
Torch
WiFi
...please tell me...
These things are NOT (or badly) working:
Encryption
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working. Please tell me...
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Benefits:
Added Aurora-Store, F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.
Which GApps would you suggest?
I've tested NikGApps, but they are not working stable. Other GApps aren't available for Android 12 as far as I know. So, I suggest none.
Update: NikGApps works after its self-updated service bibliothek and a manual restart of the device flawlessly.
It's a little bit choppy, but I can live with that.
I've set the state of the development to BETA due to quite good overall performance.
After installing this TWRP was changed to the one from Lineage. It no longer picks up my mounts. Must I use ADB to recover from this? How do I revert to TWRP? I can no longer use fastboot.
I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:
Berni-0815 said:
I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:
Click to expand...
Click to collapse
Thanks. I got fastboot working and installed TWRP again. How did the Lineage loader install though? I did not see any prompts for it.
I performed a cache/dalvik/system and data wipe and installed the latest 19.1 release but it never boots up past the swirling animation. It does not reboot either. I added a zip containing pmsg-ramoops-0
I'll take a look into it asap. Please be patient.
I can't find any reason for the crash; I'm sorry.
New version out; see 1st post.
New values for vibration strengths set.
Fixed Fingerprint location hint animation while enrolling.
Screen density reduced because all of the UI elements of Android 12L (Lineage 19.1) are too large for our little screen.
New version out; see 1st post.
Updated from android-12.1.0_r1 to android-12.1.0_r2
Berni-0815 said:
I'll take a look into it asap. Please be patient.
Click to expand...
Click to collapse
Thanks for looking. I flashed with the currently build and my device is working again.
New version out; see 1st post.
Updated from android-12.1.0_r2 to android-12.1.0_r4
Android security patch level: 5 April 2022
Hey friends,
New z5c, had sony stock on it.
I installed TWRP latest using adb/fastboot on ubuntu 20.04
All good
I flashed Lineage 19
On reboot I just get a boot loop, going between Sony logo and swirly android animation
adb recgnises the device but says "offline"
No commands work
I have tried every button combo I could find suggested everywhere, including above
But the phone will not boot into TWRP
Any suggestions, please?
kaivalyam said:
z5c, had sony stock on it
Click to expand...
Click to collapse
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
kaivalyam said:
I installed TWRP latest using adb/fastboot on ubuntu 20.04
Click to expand...
Click to collapse
How have you flashed TWRP?
Berni-0815 said:
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
Click to expand...
Click to collapse
Ok, that's probably why it wont boot then, I didnt know that, and didnt check
Berni-0815 said:
How have you flashed TWRP
Click to expand...
Click to collapse
Downloaded latest and used fastboot
fastboot flash recovery twrp.img
If I can just get TWRP to load, I can flash a different ROM and all will be good ..
Ok. Which version of TWRP have you flashed? My own?
You can flash the latest stock ROM with the flashtool. If you're installing this tool at windows, you can use the integrated XPeriFirm tool to download the latest stock ROM.
Or you install this XPeriFirm version.
If you're not in a hurry: In a few minutes my upload of my latest LineageOS 19.1 boot and system image will be completed.