Related
Hello,
I write to tell you about my problem with a rear camera of my Huawei Y6 [SCL-l01][C432B140] and ask for any possible help. I really like to use it and i tried to get it back, but even after back to my firmware and stock recovery my camera doesn't work anymore[You cannot connect to the camera] after first rom flash.
Let's start from begining:
Once i decided to install custom rom on my phone, i done everything like it was on tutorials. I unlocked bootloader, i backup my data and i flash TWRP 3.1.2. Of course, TWRP didn't shown any error or issues, but my backup after restore, cause bootloop of my device and after second reboot startin recovery[not even bootloader of OS].
I tried many fixes to get my camera working on Custom Roms like AOSP, DARKNESS, CM,[ and few from HUAWEI Y6 thread] and I always fails. After few tries i gave up. My problem was that my backup was broken and my recovery was flashed by TWRP. Lucly i found stock recovery for my phone and flashed it.
Stock recovery gave my chance to install my stock rom from UPDATE.app, but after i install my stock lolipop 5.1 - my camera won't work anymore.[Can't connect to the camera, flashlight doesn't work too].
I tought to myself "hell, it could be problem that my original soft is modificated", but luckly i had two smartphnoes of my type SCL-l01[not mine ]. I took copy of working one by TWRP and flash it to my doesn't working... It gave the same result [I used TWRP by fastboot boot twrp.img for survive of my stock recovery] - camera simply wasn't work anymore even after flash the same firmware [once from update.app and second from another scl-l01]
And there is my question - Is it possible to get this camera working again?
Just pls - don't write to my about basics like clear cache or force stop etc , becouse i tried it all.
Thanks for every answer - and sry for my mistakes in my statement.
have the same problem for quite some time, I tried to return to stock with the update.app and the camera no longer worked, and I did not find a way to make the camera work. In stock it does not work, and in ROMS as LineageOS either, eh done the same thing to reinstall the update.app and neither, I think it could be a hardware problem
I clarify, I have a SCL-L03
link plzz
i ccant find the oficial room for scl-l01 cen you guys give me the link:cyclops::crying::crying::crying::crying::crying:
WantedG said:
i ccant find the oficial room for scl-l01 cen you guys give me the link:cyclops::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
http://huawei-firmware.com/rom/huawei-y6/scll01/1194
If you want to flash it, use huawei updater extractor and extract the system.img and boot.img from the update.app and flash it from fastboot.
Or if you have stock recovery make an folder Dload in sdcard and put the update.app here. After that, press power button and volume up and down (your phone needs to be shutdowned)
That's it.
Thanks button works well if I helped
Camera and sensors all work well on MIUI 10 beta 8.11.15 Pie, as well as Lineage OS 16.
But when downgrade to MIUI 9 or 10 Oero via official MiFlashTool(fastboot) , or Lineage OS 15.1 via TWRP, it says "CANNOT connect to camera". What's more, all sensors do not work in CIT mode (of course they do not work in normal situation).
I think flash MIUI Oreo via official MiFlashTool(fastboot) should over-write all files about Pie, Isn't it?
Any ideas to this strange bug?
My poco has the same symptoms.
I installed the B-S-G camera and it did not work well, so I uninstalled it.
Then, I woke up original camera application, "CANNOT connect to camera" happened.
This phenomenon is similar to Pixel 3, but this one is more serious, coz it will not get better after reboot.
I have another twice try to flash MIUI stable 9.6.18 and beta 8.9.13 (both of them are Oero) via FASTBOOT from beta 8.11.15 (Pie), but camera app still says it " cannot connect to camera ", so can't google camera apps.
Did I forget something important? How to Downgrade from Pie to Oreo? Have any one succeeded in downgrading?
I think it's not hardware broken. Please help me. Thanks
succeeded in downgrading. need flash back a persist.img backup from 8.1 (not persist.img from official .tga fastboot package)
kumoilain said:
succeeded in downgrading. need flash back a persist.img backup from 8.1 (not persist.img from official .tga fastboot package)
Click to expand...
Click to collapse
How did you create your persist.img backup?
MikelFuchs said:
How did you create your persist.img backup?
Click to expand...
Click to collapse
ask your friends for a backup, or you can try mine. make a backup before flash my persist.img.
persist and a twrp(cn default and have English)which can flash persist easily:drive.google
kumoilain said:
"CANNOT connect to camera".
Click to expand...
Click to collapse
have you solved it somehow?
because I have the same problem
onairda said:
have you solved it somehow?
because I have the same problem
Click to expand...
Click to collapse
Try flashing persist partition. See my posts on 2018.11.25 and 2018.11.27
kumoilain said:
Try flashing persist partition. See my posts on 2018.11.25 and 2018.11.27
Click to expand...
Click to collapse
I just flashed version 9.6.18.0 from fastboot, then after installing the recovery "recovery-TWRP-3.2.3-1010-POCO_F1-CN-wzsx150.img" I flashed the file pocopersist8.img in the "persist" partition, despite this the cameras do not work and neither do the gyroscope and accelerometer sensors.
However after trying several persist files a few days ago I found one that runs 3 cameras (except the IR) even though it takes about 15 seconds to boot up, and in any case the sensors still don't work, anyway thanks for trying, I had already tried but I said to myself I try one last time.
Project Treble For Xperia XBased on Sony Open DevicesThanks to Pavel's KernelI am not responsible for bricked devices, dead SD cards,.Suitable for F5121 and F5122Reboot after your first boot please!
请中文用户遵守XDA规则，使用双语留言
If Your Camera doesn't work, see #141 please
Required files:
Our treble file could support Erfans's Android Q GSI, You need to flash this fix.
If you meet crash, you need to delete vendor/overlay.
If you meet endless bootanimite, Try to force reboot.
[New SODP Kernel version]
V20190812:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.zip
V20190811:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.zip
[Pavel's Kernel versions]
V20190702:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.zip
V20190503:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_loire.zip
V20190501:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_loire.zip
[Old SODP Kernel versions]
V20190429:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_loire.zip
V20190323:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v7_loire.zip
V20190210:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v5_loire.zip
[OEM-File]
DownloadLink
[TWRP-Q]
DownloadLink
How to go Treble?
First: Flash Twrp I built which supports a Vendor Partition
Code:
fastboot flash recovery < Path of recovery.img >
Second:Wipe Data and Cache, then flash Treble-X-sjll-XXX.zip in Twrp .
Notice:If you failed when flashing Treble-X-sjll-XXX.zip in Twrp or can't boot into desktop. Please do follwing command:
Code:
fastboot flash boot < Path of boot.img >
Code:
fastboot flash cache < Path of vendor.img >
Third: flash SW_binaries provided by Sony.
You can download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Optional step If treble file without system
Fourth: Flash a GSI compatible System image and boot!
Code:
fastboot flash system < Path of GSI-System.img >
Google Camera Guide:
1.Gcam must work with Google play services.
2. Suzu doesn't support raw Format Raw10, we should set raw Format to Raw Sensor .
3.We should set Viewfinder Format to YUV_420_888
4.Please enable: Buffer Fix to Fix viewfinder lags.
5. Suzu only support Init SlowMo at 120 FPS
Recommend Gcam Version:
ARNOVA8G2 Link
Gcam_6.1.021_Advanced_V1.7beta3.190707.0105.apk
Gcam_6.2.030_Advanced_V2.2beta5.190704.1015.apk
Update and known BUG:
20190812:
Update:
1. Thermal back, you will not hot in this summer.
2. CPU quiet back, suzu will be cold as ice.
3. F2FS support for cache(Qnovo) and userdata partitions.
20190811:
Update:
1. Go back to SODP kernel.
2. Performance and stability improve.
3. A lot of Fixes of SODP.
20190716:
Update:
1. New twrp-Q uploaded.
V20190702:
Fixes:
1. Cancel OverClock.
2.New CAF imported in kernel.
3.Forcecryptable canceled. If you upgrade from old version, you need to format userdata and use new TWRP-Q.
Bugs:
Need feedback.
V20190503:
Fixes:
1. New PowerHAL.
Bugs:
Need feedback.
V20190501:
Fixes:
1. Use Pavel's kernel source codes.
2. Quick Charge 3.0 works fine.
Bugs:
Need feedback.
V20190210:
Bugs:
1. Quick Charge is broken, you can use computer USB port charge.
2. Camera doesn't work on first boot, you need to reboot.
Source Codes
Sjll
Kernel
Contributors
Sjll @Cubbins
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Paypal
I am very happy to receive your donation.
Version Information
Status: Testing
Created 2019-02-10
Last Updated 2019-08-12
Hi! And it is possible to flash system.img via TWRP?
Since the latest TWRP (3.2.2.2) can flash those partitions, can we flash through it?
realthrash said:
Since the latest TWRP (3.2.2.2) can flash those partitions, can we flash through it?
Click to expand...
Click to collapse
no, I tried
Is it A Only or A/B type?
sebasrock156 said:
Is it A Only or A/B type?
Click to expand...
Click to collapse
A only.
[email protected] said:
Hi! And it is possible to flash system.img via TWRP?
Click to expand...
Click to collapse
realthrash said:
Since the latest TWRP (3.2.2.2) can flash those partitions, can we flash through it?
Click to expand...
Click to collapse
Use the twrp provided by me, it can flash these partition with an img file.
After install this ROM..I dont have root acces and how to enter the treble twrp because I cant enter it after flashed this ROM:crying:
So I just installed the ROM.
On my first try, it just did not boot. Stuck at Sony logo. I then flashed the latests stock .ftf, did the installation again and managed it to boot. Seems that I did not have the latest bootloader
After the initial boot, I wanted to enter recovery again, but could not get into it. I then flashed TWRP 3.2.3.2 and could install the gapps from there. The system also runs with this recovery.
What I already tested:
- camera shows only up to 17,1 Megapixels, but works
- front camera works
- camera button works
- WIFI works
- mobile data wiht LTE work, but I had to type in the APN manually
- phone calls work
- fingerprint works
- bluetooth works, but I cannot pair with my Garmin watch (have the same problem when using lineage OS)
Overall the system looks and feels really great! Added some screenshots too!
Well done, @Sjll ; Thank you very much!
Thelooks14 said:
After install this ROM..I dont have root acces and how to enter the treble twrp because I cant enter it after flashed this ROM:crying:
Click to expand...
Click to collapse
Just using fastboot flash a GSI in system partition.
Please use the twrp I privide for treble.
If you want to go to recovery, just shutdown and hold power and Vol-.
sessions04 said:
So I just installed the ROM.
On my first try, it just did not boot. Stuck at Sony logo. I then flashed the latests stock .ftf, did the installation again and managed it to boot. Seems that I did not have the latest bootloader
After the initial boot, I wanted to enter recovery again, but could not get into it. I then flashed TWRP 3.2.3.2 and could install the gapps from there. The system also runs with this recovery.
What I already tested:
- camera shows only up to 17,1 Megapixels, but works
- front camera works
- camera button works
- WIFI works
- mobile data wiht LTE work, but I had to type in the APN manually
- phone calls work
- fingerprint works
- bluetooth works, but I cannot pair with my Garmin watch (have the same problem when using lineage OS)
Overall the system looks and feels really great! Added some screenshots too!
Well done, @Sjll ; Thank you very much!
Click to expand...
Click to collapse
You can flash a GSI to get better experience. Thanks for your feedback!
Sjll said:
Just using fastboot flash a GSI in system partition.
Please use the twrp I privide for treble.
If you want to go to recovery, just shutdown and hold power and Vol-.
Click to expand...
Click to collapse
Where I can download GSI?
sessions04 said:
So I just installed the ROM.
On my first try, it just did not boot. Stuck at Sony logo. I then flashed the latests stock .ftf, did the installation again and managed it to boot. Seems that I did not have the latest bootloader
After the initial boot, I wanted to enter recovery again, but could not get into it. I then flashed TWRP 3.2.3.2 and could install the gapps from there. The system also runs with this recovery.
What I already tested:
- camera shows only up to 17,1 Megapixels, but works
- front camera works
- camera button works
- WIFI works
- mobile data wiht LTE work, but I had to type in the APN manually
- phone calls work
- fingerprint works
- bluetooth works, but I cannot pair with my Garmin watch (have the same problem when using lineage OS)
Overall the system looks and feels really great! Added some screenshots too!
Well done, @Sjll ; Thank you very much!
Click to expand...
Click to collapse
can you still enter recovery mode now?
I could only enter recovery with TWRP 3.2.3.2!
So I jused Sjll's recovery vor initial installation and then changed to 3.2.3.2
But I am not sure, if the Treble updates will work with this TWRP...
I used your guide to install another treble ROM
Thanks
One question:
I can root without any problem, but if I reboot the phone the data partition gets encrypted, ¿what can I do to solve this?
Today I made a lot of pictures with the front camera and with the back camera. . AF just doesn't get a sharp picture. Front camera is totaly useless for selfies, even with perfect light conditions.
I downloaded Google Camera app, which makes it a little bit better, but still not comparable to the stock Sony Camera App. Oh, and it just shows 13 MPx max res.
Too bad!
Anyone here with better results?
sessions04 said:
Today I made a lot of pictures with the front camera and with the back camera. . AF just doesn't get a sharp picture. Front camera is totaly useless for selfies, even with perfect light conditions.
I downloaded Google Camera app, which makes it a little bit better, but still not comparable to the stock Sony Camera App. Oh, and it just shows 13 MPx max res.
Too bad!
Anyone here with better results?
Click to expand...
Click to collapse
These are bugs of SODP. only waitting for their fix.
where to get boot.img?I can't flash zip
There is a Link in the first post, next to
"[Tested]
V20190210 Link... "
You find the "twrp-Q.img" there.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup.
Notes
The idea of this project treble is to separate the device-dependent part and the system.
The project treble requires a separate /vendor partition for device-dependent part. But unfortunately we do not have it. But we have a /cache partition, which takes about 200mb and there is a /hidden partition, which takes 50-60mb. 200mb is not enough for us, our vendor is about 450mb.
In the first edition I maded for the 825 tablet, I implement an original solution using separate files for the system and the vendor. But this solution was very difficult to understand. Now my good friend @bonuzzz suggested an idea to me using a compressed partition (squashfs with lz4 compression). With this method, our vendor takes 190-195mb and it is possible to write it to the /cache partition. And use the /hidden partition as a /cache.
Now the installation has become much easier, almost like installing the usual lineage.
Installation
1. install twrp version with treble support (this is my special twrp, based on 9.0 with my latest caf kernel with squashfs support)
2. download treble zip and flash it as usual zip. It will flash boot.img and /vendor partition (in /cache)
3. download any treble system (64bit System A-only) image from: https://forum.xda-developers.com/project-treble
extract, you should get .img file, then copy to sdcard/extsd card and then flash image as system_image in twrp (Install - switch to Install Image and flash as System Image)
4. if you wanna back to stock firmware or lineage - you need flash normal twrp version and make full wipe or just flash stock firmware via odin
Links
Firmware
[SM-T820]
1. 20190404: https://drive.google.com/file/d/1hOPdO9UajY7AlJ5lE859Tr6Y7sEpwhTf/view?usp=sharing
[SM-T825]
1. 20190408: https://drive.google.com/file/d/1DokV37D8f2s9OtoAJTCURfdx88tNW788/view?usp=sharing
TWRP
[SM-T820]
1. 20190404: https://drive.google.com/file/d/1gJ50Sg75Vh7PKyiWfejiCPSD0SYCL5p2/view?usp=sharing
[SM-T825]
1. 20190408: https://drive.google.com/file/d/1x_MKQ1PDM6eEbSPsDyFk0DABjXnZfyB4/view?usp=sharing
System images
You can use almost any system image from https://forum.xda-developers.com/project-treble
Our version is: arm64 and a-only image
Magisk
You should use only latest 19.0 beta version from: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Do not use 18.1 or early version - it's dnw, it will corrupt firmware or may be even corrupt recovery (need flash recovery again via odin)
Almost all firmware say about wrong vendor version. This is normal, just press OK.
let's experiment together!
Version for SM-T825 hope will come soon too. I have some ril issues.
Update boot.img
Wow! Thank you for the amazing work. I seriously can't believe no one hasn't gone crazy over this already.
How would I go about adding some libraries to my /vendor partiton now? I want to try a Samsung OneUI GSI image on my tablet but it requires additional libraries.
The files I want to add are in here: https://mega.nz/#!oi52TSTY!2Qy3WU7DjVmafs4zENPF6dlOsbY06JG5NuvsNeDTRn4
How did you build this file in the first place?
EDIT: I noticed that video playback does not work. I see the video starts to buffer, then some ghosting appears, and finally the app crashes (both YouTube and Vimeo). Also, camera apps seem to crash.
cephasara said:
EDIT: I noticed that video playback does not work. I see the video starts to buffer, then some ghosting appears, and finally the app crashes (both YouTube and Vimeo). Also, camera apps seem to crash.
Click to expand...
Click to collapse
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
GSIs
rainman74 said:
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
Click to expand...
Click to collapse
Maybe my /hidden & /cache partitions got corrupt somehow. I tried several GSIs and had the same issue. Thanks for confirming though.
Have you tried an GSIs from non AOSP-based images? Like OneUI or Xperia? I had trouble with those.
rainman74 said:
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
Click to expand...
Click to collapse
Could you let us know which treble rom you used, as I have the same issues with video playback on youtube.
I also want to throw out there I was on the Nougat bootloader when I tried this and had video playback issues. I have not tried it out on Oreo. I would imagine that could make a big difference.
deleted (it sucks none of the sensors function properly)
just installed RR but i think gps not working
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
This is great!
Hey everyone, this project is big news! I am so happy that we can use Treble GSI, using the cache partition via squashfs is a really elegant way for this.
Almost everything works on my T820! I am using Phh-Treble AOSP 9.0 v112, MindTheGapps and Magisk. Even adoptable storage works, I have 256GB for internal storage now (it displays as 256/512 used when empty, but whatever).
The device is certified with magisk and custom prop value.
Contrary to the old Lineage OS from last year, there is no crazy wifi jitter, so Steam Link just works fine. I did not try out the recent Lineage 20190331, so I don't know if it was due to Lineage.
The rotation sensors are not working, for now I am using "Rotation Quick Setting" app from Play Store. Also, the camera app crashes, but I am not using it anyway.
Thank you so much @bonuzzz and @Valera1978 for making this possible! It is stable enough for daily use for me.
BTW, I came from Oreo bootloader, and have no problems regarding video playback (but I use MX Player, not stock)
Mhh.. I get constantly soft reboots if i try to install third party apps or restore my titanium backup on Havoc for treble. Fingerprint is also not working. Seems to be very unstable...
How could I go about adding files to this treblized /vendor partition? Presumably through the zip? If this is the case, how could I do that?
Fair warning to those wanting to try this: treble roms do install and run, but sensor support appears to be lacking. I can't get any input from gps, accelerometer, gyro, or light sensor.
@Valera1978 If anybody has any idea on how to add support for these to the (I'm assuming) vendor partition, I'd love any hint or direction.
usb otg not working
alegru said:
Hey everyone, this project is big news! I am so happy that we can use Treble GSI, using the cache partition via squashfs is a really elegant way for this.
Almost everything works on my T820! I am using Phh-Treble AOSP 9.0 v112, MindTheGapps and Magisk. Even adoptable storage works, I have 256GB for internal storage now (it displays as 256/512 used when empty, but whatever).
The device is certified with magisk and custom prop value.
Contrary to the old Lineage OS from last year, there is no crazy wifi jitter, so Steam Link just works fine. I did not try out the recent Lineage 20190331, so I don't know if it was due to Lineage.
The rotation sensors are not working, for now I am using "Rotation Quick Setting" app from Play Store. Also, the camera app crashes, but I am not using it anyway.
Thank you so much @bonuzzz and @Valera1978 for making this possible! It is stable enough for daily use for me.
BTW, I came from Oreo bootloader, and have no problems regarding video playback (but I use MX Player, not stock)
Click to expand...
Click to collapse
Does Netflix work?
I get a bootloop after installing image and reboot to system. I have followed the instructions and got an error "Updater process ended with ERROR:7" installing the treble-16.0.zip. I flashed the custom TWRP using odin and using stock Pie. Did I do something wrong?
Hey all. Flashed all the relevant files in the relevant order and currently have a tablet sitting on the Tab S3 splash screen. How long does this normally take?
I flashed the custom TWRP,
Rebooted into Recovery,
Flashed the Treble .zip file,
Rebooted into Recovery,
Flashed the latest Havoc OS, then Magisk v20.3
then rebooted and it's stuck here.
Strange thing is, Windows has flashed up saying that it is "setting up Samsung_Android" while it's on the splash screen.
I come from the tweaked T825 ROM.
Anyone else had this issue? Should I have flashed stock first?
ianrobbie said:
Hey all. Flashed all the relevant files in the relevant order and currently have a tablet sitting on the Tab S3 splash screen. How long does this normally take?
I flashed the custom TWRP,
Rebooted into Recovery,
Flashed the Treble .zip file,
Rebooted into Recovery,
Flashed the latest Havoc OS, then Magisk v20.3
then rebooted and it's stuck here.
Strange thing is, Windows has flashed up saying that it is "setting up Samsung_Android" while it's on the splash screen.
I come from the tweaked T825 ROM.
Anyone else had this issue? Should I have flashed stock first?
Click to expand...
Click to collapse
Well I've hard-bricked my tab by flashing the Treble zip so consider yourself lucky. I think you should flash ODIN stock and start from scratch. Flash ashyx's TWRP, follow the instructions there. DO NOT FLASH MAGISK. Then flash Treble TWRP, flash zip, reboot recovery, DO A WIPE DATA / FACTORY RESET, NOT FORMAT, Then flash Havoc OS a only or whatever. After that wipe cache/dalvik and let it boot to ROM, AND THEN flash magisk and stuff.
I hard bricked my tab because Magisk was installed on the device while I flashed Treble. So yeah DON'T DO THAT EITHER
By the way im so sorry for being 2 months late i saw this just now
Looking dangerous. I'd like to try it but uncertain procedures
NullCode said:
Well I've hard-bricked my tab by flashing the Treble zip so consider yourself lucky. I think you should flash ODIN stock and start from scratch. Flash ashyx's TWRP, follow the instructions there. DO NOT FLASH MAGISK. Then flash Treble TWRP, flash zip, reboot recovery, DO A WIPE DATA / FACTORY RESET, NOT FORMAT, Then flash Havoc OS a only or whatever. After that wipe cache/dalvik and let it boot to ROM, AND THEN flash magisk and stuff.
I hard bricked my tab because Magisk was installed on the device while I flashed Treble. So yeah DON'T DO THAT EITHER
By the way im so sorry for being 2 months late i saw this just now
Click to expand...
Click to collapse
would some of the issues seen by others be fixed if one started with non-rooted stock 9.0 and 9.0 bootloader (if it is different from that for Oreo)? thanks anyone
Tested on my Mi Pad 5 Pro 12.4"(dagu) using elish's ROM.
Step to install:
1. Download FastbootEnhance.
2. Download ArrowOS ROM (Xiaomi/elish), and unzip it. There should be a payload.bin inside.
As elish (Mi Pad 5 Pro) and dagu (Mi Pad 5 Pro 12.4") uses the same SoC, it should be fine. But still, unverified if further problems occurs.
3. Either backup the boot and vendor_boot, or download a stock firmware and extract from it.
小米社区
web.vip.miui.com
4. Under fastbootd (fastboot boot fastboot), use FastbootEnhance to flash the payload.bin.
5. Re-enter to fastbootd, use
Code:
fastboot flash boot boot_stock.img
to flash the boot img back to the vendor one.
6. fastboot reboot, and then unplug the cable.
Then, fastboot reboot. And the ArrowOS should boot.
Current issue:
camera not working
NOTE:
not sure if
fastboot --disable-verity --disable-verification flash vbmeta_ab vbmeta.img
is needed
What do you think are the major changes now with the ArrowOS?
CauAguiar said:
What do you think are the major changes now with the ArrowOS?
Click to expand...
Click to collapse
I just found that the UI and overall experience is better than LineageOS.
And also the Pad is on the official support list of ArrowOS.
I have flashed on my mipad 5 pro 12.4 , however, sound is missing from the system.
spacezmonkey said:
I have flashed on my mipad 5 pro 12.4 , however, sound is missing from the system.
Click to expand...
Click to collapse
Same for me. Tried TrebleApp, using
Code:
am start -n me.phh.treble.app/.TopLevelSettingsActivity
to call at adb shell, but still not working.
does this work for enuma as well?
Does the Xiaomi Pen work on this Rom?
niveZz said:
does this work for enuma as well?
Click to expand...
Click to collapse
I am also very much interested using this on my: Mi Pad 5 Pro 5G "Enuma".
@All If this doens´t work on "Enuma" - can this be adapted?
@kokomicat
Really interested in this. Any news? Also I dont quiete understand, "no system sounds" means no notification sounds etc. or no sound at all like from youtube spotify etc...?
Thx
FastbootEnhance can be used to flash stock firmware of recovery version. The recovery one is more updated then the fastboot one. So more benefits on fixing firmware issues.
For those who have problems with sound issues, try disable the sound effect by following these steps:
1. Go to Settings
2. Enter Phh Treble Settings
3. Under Qualcomm features, click off all the audio and sound related functions.
4. Under Misc features, click off Disable audio effects.
The above solutions work for uncompatible features of the firmware being used by the ROM system.
Hope this helps.
Thank you for the nice tutorial of how to flash GSI ROM with FastbootEnhance.
I Tried the steps, No Errors, but after Last fastbook reboot it just Boots to normal MIUI?
Any Tips?
siamese007 said:
FastbootEnhance can be used to flash stock firmware of recovery version. The recovery one is more updated then the fastboot one. So more benefits on fixing firmware issues.
For those who have problems with sound issues, try disable the sound effect by following these steps:
1. Go to Settings
2. Enter Phh Treble Settings
3. Under Qualcomm features, click off all the audio and sound related functions.
4. Under Misc features, click off Disable audio effects.
The above solutions work for uncompatible features of the firmware being used by the ROM system.
Hope this helps.
Thank you for the nice tutorial of how to flash GSI ROM with FastbootEnhance.
Click to expand...
Click to collapse
Hello, I wasn't able to find the setting for "Phh Treble Setting". there is no such option in my "setting". Anyway i have flashed Gapp version of Arrow OS.
spacezmonkey said:
Hello, I wasn't able to find the setting for "Phh Treble Setting". there is no such option in my "setting". Anyway i have flashed Gapp version of Arrow OS.
Click to expand...
Click to collapse
It means this ROM is modified to suit elish device. So you need to use some apps to modify the system settings manually to fix the audio effects that are not compatible with the stock firmware.
I am using A13 Arrow GSI ROM. Everything works fine after disabling all the audio effect features of the ROM system. Except Xiaomi peripherals are not compatible.
update on my attempt..
i tried quite a few GSI rom with phh treble setting, after i disable the audio effects, it is still not working.
spacezmonkey said:
update on my attempt..
i tried quite a few GSI rom with phh treble setting, after i disable the audio effects, it is still not working.
Click to expand...
Click to collapse
You may try to flash the new Stock ROM that is compatible with the custom ROM. It seems the firmware you installed has sound conflicts with the installed firmware. Try the stable version of the firmware. The dev versions are still under development.
If the sound issues persist, I think you may wanna try the new custom ROM.